1.0 Paging Optimization

MSS Optimization
Workshop
Paging Optimization
Mohsin Ismail
27-04-2016
1 Nokia 2016 For Internal use

Topic
1. Paging Basic Analysis Flow

2. Paging Scenario
3. Paging Signaling Flow
4. Paging Measurement and KPI.
5. Paging Features and Parameter
6. Paging Proactive Optimization
2 Nokia 2016 For Internal Use

Topic

2. Paging Scenario

Paging Monitoring Flow

Paging Analysis Flow
1. Check Paging SR% KPI. The paging KPI can be different per
customer.
2. Check detail which LAC contribute the lower pagings.
3. Check parameter setting per LAC.
4. Check subscriber per LAC capacity which can be influence the
paging response
5. Make a recommendation if required,
6. Discuss with RAN engineer for LAC/RAN quality

Topic

2. Paging Scenario

Paging Scenario
GMSS HLR MSS/VLR SGSN MME RNC BSC UE
MAP/C SEND ROUTING INFORMATION

OPT, PRE PAGE
Paging options in CS
MAP/D PROVIDE ROAMING NUMBER
core: PAGING REQUEST PAGING
PAGING SETTINGS
1. Pre Paging. IN MSS
LU ongoing /
MAP/D PROVIDE ROAMING NUMBER ACK PAGING ACK Always to MSS LU Prevented
2. Paging via Gs
Security Functions, Chipher, Authent, TMSI, IMEI ..
interface (SGSN) MAP/C SEND ROUTING INFORMATION ACK
3. Paging via SGs IAM
PAGING REQUEST
interface (EPC, OPT, PAGING ENHANCMENTS PAGING
LTE), CSFB PAGING SETTINGS
4. Paging repetition POSSIBLE RE-PAGINGS
and interval SGsAP SERVICE REQUEST CSFB IF MS WAS IN E
5. Paging busy
subscriber (SMS) PAGING ACK Always to MSS
6. Paging
enhancements
Security Functions, Chipher, Authent, TMSI, IMEI ..
CALL SETUP CONTINUE

Paging Procedures
Paging via 2G-SGSN: (Gs interface). If mobile is combined GSM and GPRS attached it can be pages first in PS
domain (via SGSN) and if PS page fail then optionally via A-interface. If MS answer to packet side page, page reply
come from BSC to MSS.
Paging via 3G-SGSN: (Gs interface). Page message is sent from 3G SGSN to RNC and possible page reply come
from RNC to MSS.
3G (RNC) page: When UE is in cell/URA_PCH state, which means it is attached to PS-core network and it does not
have any data to send/receive then RNC pages UE and it can repeat paging attempts according to two re-paging
timers:
PageRep1stInterv (default 700ms)
PageRep2ndInterv (default 2s)
This will normally make the paging success better in 3G than in 2G.
NSN RNC do not have re-paging for idle UE.
CSFB: If mobile is LTE (EPC) attached and SGs interface exists then CS page (CS call or SMS) can be done via
MME. In CS call case, page response come via MME to MSS and UE make CSFB to 3G or 2G either blind (fast but
success not so good, radio connection quality is not known) or based on measurements (better success, but this will
cause delay to call setup round 1 sec). MT-SMS is delivered via MME id page is successful.

Topic

2. Paging Scenario

Topic

2. Paging Scenario

Paging Measurement
VLR measurement, part 1 (82/52H)

VLR measurement - part n, paging per LAC (353/161H)
VLR measurement, Paging Failure (92/5CH)

VLR Measurement part one (M82) General Counters
The VLR measurement shows the success of the paging through the Circuit Switched (CS) domain (that is, the A and
the Iu interfaces), as well as the success of paging through the Packet Switched (PS) domain (that is, paging through
the SGSN).

VLR Measurement part one (M82), CS Alternate paging
Alternate CS paging is performed when the 2G-SGSN sends a

PAGING REJECT with the following cause codes:
- GPRS IMSI detach (MS-initiated)
- IMSI unknown in SGSN (IMSI is not found in the subscriber
database)
-- No response from SGSN (paging timer expired in the MSC)
- Address error
- The destination point is not available, in other words all the
signalling links to that destination point are not available

VLR Measurement part one (M82)
Standard report (paging part)
Additional paging counters in the ASCII report:

These counters are printed in the report only when the
STA_R4_MIG_PAGING FIFILE parameter is active.
The new counters are printed only for normal subscribers and placed
after the usual paging counters.

VLR Measurement part one (M82), LTE paging counters
The following counters

are also available when
the L.1530 Sales Item is
present:

VLR measurement report, paging per LAC (353/161H)
These counters are printed in the report only

if the PAGING_FOR_VOICE_PER_LAC
FIFILE parameter is active.

Paging per LAC

Paging per LAC
At the end of the paging procedure the MSC is sending a paging report to the VLR the report states the paging success
or failure and the number of TMSI and IMS pagings leading to it. So e.g. B subscriber was paged & repaged by TMSI 3
times unsuccessfully, then by IMSI 2 times (1st unsucc., 2nd succ., finally B party is ringing). In this scenario you will have
following updates:
M353B3C1 PAGING ATTEMPTS PER LAC +1
M353B3C2 SUCCESSFUL PAGINGS PER LAC +1
M353B3C4 PAGING ATTEMPT WITH TMSI PER LAC, SUCCESSFUL +3
M353B3C3 PAGING ATTEMPT WITH IMSI PER LAC, SUCCESSFUL +2
M353B3C6 PAGING ATTEMPT WITH TMSI PER LAC, FAILED +0
M353B3C5 PAGING ATTEMPT WITH IMSI PER LAC, FAILED. +0
So even though the paging with TMSI were unsuccessful as they were leading to a successful paging they are counted in
the TMSI successful paging attempts and not in the failed counter.
The paging time counter is the average paging duration from the last paging message to the successful
paging answer. If one is interested in the overall successful paging procedure duration it will be calculated
as:
{[(M353B3C4 / PAGING ATTEMPT WITH TMSI PER LAC, SUCCESSFUL) +

(M353B3C3 / PAGING ATTEMPT WITH IMSI PER LAC, SUCCESSFUL) 1] / (M353B3C2 / SUCCESSFUL
PAGINGS
18 PER LAC)
Nokia } *(LAC paging timer) + (M353B3C7
2016 / ANSWER TIME)/10
For Internal Use
VLR measurement report, paging failure (92/5CH)
Paging failure counters

When the VLR_MEA_PAGING_FAILURE (009:0165) FIFILE parameter is active the fol-
lowing counters related to paging failures are also available:
PAGING FAILURE REASON
The number of paging failures on clear code level. The counter is updated if paging failed due to one of the following reasons:
no paging response,
paging response is received with a failure (for example the subscriber does not have permission to required radio access,
configuration error, PAGING
RESPONSE contains illegal/incorrect mobile identity),
internal error.
Busy subscribers are not reported.

Paging KPI
Paging Success Rate%

Paging Per LAC Success Rate%
EPS Paging Success Ratio % (CSFB)

Paging Success Rate %
VLR measurement , part one (M82/52H)
KPI Name Paging success ratio (CS only)
Formula 100 * ( PagingThroughAIFSucc /( PagingThroughAIFAttempts )

Paging Success Rate %
VLR measurement M353
KPI Name Paging attempt success ratio, per LAC
Formula 100 * ( PagingSuccPerLA /( PagingAttemptPerLA )

EPS Paging Success Ratio %
VLR measurement , part one (M82/52H)
KPI Name EPS Paging Success Ratio %
Formula 100*( PAGING_EPS_DOMAIN_SUCCESS )/( PAGING_EPS_DOMAIN_ATTEMPT )
Ratio of successful paging procedures using SGs interface (SGsAP-PAGING-REQUEST

message is sent from MSS/VLR to MME).
The following cases are considered as successful pagings:
- CS FallBack case: Paging Response is received over Iu/A interface
- SMS: SGsAP-SERVICE-REQUEST received
- CSFB happens to different MSS: VLR receives Cancel Location message from the HLR
for the paged subscriber

Exercises
Raw Measurement: Light Analysis:
Paging Per LAC Paging Per LAC

raw measurement
PSR%
VLR_M82

Topic

2. Paging Scenario

Paging Related Features
Feature 1682: Paging Enhancement. PRN-based pre-paging
In this case, the VLR initiates paging the subscriber prior to the roaming number allocation, and keeps the radio connection alive,
while the call is being routed to the MSC. When the call arrives, paging is not carried out again, but the result of the pre-paging is
used to complete the call setup.
The process access request (PAR) service (that is authentication, security mode setup, IMEI checking, and so on) and the call
routing are executed simultaneously.
If the subscriber is not registered in the VLR when the PRN request arrives, the restore data procedure is also started parallel to pre-
paging.
As an enhancement, the MSC is able to handle either the PSI, or the PRN request (depending on which implementation is used)
which arrives from the HLR during an ongoing location update (LU)..
Feature 1043: Short Message Services, GSM Phase 2+. With this feature, the SM delivery retry is done by the MSS instead of
the SMSC, therefore the signaling load can be saved in the interface and the SMS-GMSC.
LTE related Features:
Phase 1- SMS over SGs Interface functionality is controlled by FEA1691 license.
Phase 2- Full CS Fallback support in SGs interface functionality is controlled by FEA1935 license.
CS Fallback Rel9 Enhancement- Phase 1 functionality is controlled by FEA3440 license.
CSMT flag support functionality Repaging on A/Iu interface functionality
PSI support for CSFB functionality is controlled by FEA3459 license.

Features Related Parameters
PAGING_FOR_VOICE_PER_LAC (009:0159) FIFILE parameter controls whether the counters ATTEMPTED VOICE
PAGING PER LAC and SUCCESSFUL VOICE PAGING PER LAC appear in the measurement.
VLR_MEA_PAGING_FAILURE (009:0165) FIFILE parameter controls whether the counters DATA MISSING IN
PAGING FAILURE VALUES and PAGING FAILURE REASON appear in the measurement.
STA_R4_MIG_PAGING (009:0153) FIFILE parameter Additional paging counters MTC Paging on AIF/IU
SMS
PRFILE/FIFILE: 002:1580 MT_SM_REPAGING Repaging in case of failed paging for MT-SM
Repaging times and interval.
ZWOA:2,1580,A;
Parameter 031:0073 REPAGING_DELAY_TIME
Parameter 031:0074 REPAGING_DELAY_NUMBER

FN1682: Paging Enhancement related Parameters
GET_LAI_BEF_PAGING_REP (002:1100) This controls the retrieval of the current location area information before
paging repetition. (Only useable when TMSI paging is activated)
HYPO_LAC_USAGE (002:1191) This parameter enables the operator to use location area -specific hypo-LAC paging
towards BSC where the paged MS has recently been located.
DEDICATED_RNC_PAGING (002:1740) This parameter defines whether the dedicated RNC paging is activated for a
location area. If the dedicated RNC paging is activated, the primary paging is performed in the coverage area of the
recent i.e. last active RNC. If the dedicated RNC paging does not succeed, the paging continues as normal LAC-
paging.
SELECTIVE_PAGING (002:1405) This parameter determines whether the operator is allowed to use LAC-based
selective paging parameters to restrict TMSI repagings or not
LAC_SMS_TMSI_REPA_RESTR (002:1406) LAC-based SMS TMSI repaging restricted
LAC_PSI_TMSI_REPA_RESTR (002:1407) LAC-based PSI TMSI repaging restricted
LAC_PRN_TMSI_REPA_RESTR (002:1408) LAC-based PRN TMSI repaging restricted
INTELLIG_SELEC_PAGING (002:1474) intelligent selective paging requires that the hypo-LAC paging is also
activated
GLOBAL_PAGING (002:1794) Global paging (search) after failed paging per LAI.
LTE Feature Paging Related Parameters (1/2)
SS_CODE_IN_LTE_PAGING (002:1802)
The byte value of this PRFILE parameter controls the paging of an MME-associated subscriber by the
MSS on the SGs interface (through MME) for MT-Call Independent Supplementary Service reason. The
value is sent in the SS code information element of the SGsAP-PAGING-REQUEST message.
PAGING_TONE_TSL (007:0433)PRFILE parameter determines whether a tone is connected to a
calling subscriber during paging by the MSS after an SGsAP-SERVICE-REQUEST was received as an
intermediate paging response from the MME. The parameter indicates the timeslot of the
announcement which is connected to the subscriber in case of an MT call.
PAGING_ANN_INDEX (007:0432) PRFILE parameter determines whether an announcement is
connected to a calling subscriber by the MSS after an SGsAP-SERVICE-REQUEST was received as an
intermediate paging response from the MME. The parameter indicates the index of the announcement
which is connected to the subscriber in case of an MT call. Values can be given in decimal and
hexadecimal format.

LTE Feature Paging Related Parameters (2/2)
PAGING_ACCEPT_TIMER (002:1821) PRFILE parameter determines in seconds the duration of the

timer which is used to supervise the final paging response from the UE after an SGsAP-SERVICE-
REQUEST has been received as intermediate paging response in a non-SMS MT event. If the timer
expires in an MT Call case, the call is released. In other non-SMS MT events the operation fails.The
possible value range is 1-180 (0x1-B4).
REPAGE_SGS_CAUSE_LIST (002:1969) PRFILE parameter determines for which SGs cause code
the MSS should execute A/Iu repaging. Each bit in the parameter represents one SGs cause code. If
the value of the bit is 1, the A/Iu repaging is executed for that SGs cause code.
PSI_PAGING_OVER_SGS (002:1975) PRFILE parameter controls the use of the PSI support for
CSFB functionality together with FEA3459 license. The parameter has effect only when also the license
is active.
The following counters are only visible if FEA1935 license is ON:
VOICE_PAGING_SGS SEARCH_ON_A_IU_SGS
VLR_MEA_PAGING_FAILURE (009:0165) FIFILE parameter controls if Cause code ROAMING
RETRY (002A) is visible in the paging failure part of the VLR
PSI-based pre-paging Feature Related Parameters
PSI pre-page time
This UTPFIL parameter defines how long the pre-page resources are left hanging after the PSI page response arrives. If
the provide roaming number (PRN) does not arrive during this time, the paging resources will be removed. The
parameter expresses the time in 0.01 seconds. If the value is zero (0), or the parameter is missing, it means that the
default 5 seconds is used.
PRN pre-page time
This UTPFIL parameter defines how long the pre-page resources are left hanging after the PRN has arrived, and the
pre-page resources exist. If the IAM does not arrive during this time, the paging resources will be removed. The
parameter expresses the time in 0.01 seconds. If the value is zero (0), or the parameter is missing, it means that the
default 5 seconds is used.
PSI search
This UTPFIL parameter can be used to enable the usage of the search procedure, when the LAC found for the
subscriber is zero (0) (the subscriber's location is unknown), or the subscriber is not in the VLR. By default, there is no
search at the PSI. The existing VLR parameter MTCPASS controls whether the PSI is served or not in the case of
passive subscribers.
AGELOC time
this parameter shows the maximum location age for which the PSI-based pre-paging of a subscriber is not started. MXM
MML command. From 0 to 2147483647 seconds.

Long paging timer Parameter
To support the possibility of continuing call setup after

successful long paging, a guard timer is introduced in the
terminating MSS. This timer expires in 114 seconds. The
guard timer expiration starts the bearer establishment in
the network before COT timers expire. The duration of the
timer can be set with the LONG PAGING PREVENTIVE
TIMER (PREVTMR) Incoming Call Control parameter with
the MML command ZCPC:.
The default duration is 10s.

Paging Parameters
Re paging parameter in LACs
MSCi BNXM1 2014-05-23 17:51:16
LOCATION AREA
LA NAME :LAC00001 LAC :00001
MOBILE COUNTRY CODE ...................(MCC)... :302
MOBILE NETWORK CODE ...................(MNC)... :640
REPAGING ATTEMPTS .....................(AT).... :001
REPAGING INTERVAL TIMER 1 .............(INT)... :00520 ( x 10 msec )
MSRN GROUP ............................(RNGP).. :000
ALLOWED MNC IN NATIONAL ROAMING .......(MNC)... : -
INCLUDE IN POOL CONCEPT ...............(INC)... :YES
DAYLIGHT SAVING .......................(DSAV).. : -
TIME ZONE .............................(TZ).... :05:00 (GMT-)
VIRTUAL MSC ADDRESS INDEX .............(VMSC).. : -
VIRTUAL VLR ADDRESS INDEX .............(VVLR).. : -
DEDICATED RNC PAGING ..................(DRP)... :OFF
HANDOVER NUMBER RANGE INDEX FOR LA ....(HONLA). : -
EQUIVALENT PLMN INDEX FOR LA ..........(EQPLMN) :001

Paging Parameter
In practice the paging parameters in MSS are part of the VLR parameters.
The Nokia standard recommended parameters in the NED are:
PAGE AND SEARCH Outputs:
LIMIT FOR SIMULTANEOUS SEARCHES: 100
NUMBER OF SEARCH REPETITIONS: 2 LAC parameters (ZELO):
REPAGING ATTEMPTS .....................(AT).... :01
SEARCH RESPONSE WAITING TIME: 1000 MSEC.
REPAGING INTERVAL TIMER 1 .............(INT)... :00300 ( x 10 msec )
TMSI PAGE REPETITION IN MT CALL: USED
TMSI PAGE REPETITION IN MT SMS: USED ZWOA:2:1191,A; // 2G
TMSI PAGE REPETITION IN MT USSD: USED ZELE:LAC=<lac>:HYPO=ON;
TMSI PAGE REPETITION IN MT LR: USED . ZWOA:2:1740,A; // 2G & 3G
MME SEARCH FOR MME SUBSCRIBERS: USED ZELE:LAC=<lac>:DRP=ON;
PSI PAGING OVER SGS INTERFACE: MTLR ZWOA:2:1474,A;
PSI PAGING ON LOCATION REQUEST: USED ZELE:LAC=<lac>:HYPO=ON,ISP=ON;
Set the parameter value for NBR OF STARTED SEARCH
VLR parameters (ZMXO):
PROCEDURES to 100. If you have overload problems in the radio PAGE AND SEARCH
network after the VLR reset, limit the search procedures. If the LIMIT FOR SIMULTANEOUS SEARCHES: 100
counter value is 0, the MTCs for unknown subscribers do not NUMBER OF SEARCH REPETITIONS: 2
SEARCH RESPONSE WAITING TIME: 1000 MSEC.
go through.
TMSI PAGE REPETITION IN MT CALL: USED
Parameters can be changed with ZMXM MML command TMSI PAGE REPETITION IN MT SMS: USED
TMSI PAGE REPETITION IN MT USSD: USED
TMSI PAGE REPETITION IN MT LR: USED
OBS. TMSI here mean IMSI!

Topic

2. Paging Scenario

Traffica
VLR Reports Fields Paging analysis
TNES Event Add Alternate Answer Attempt Bsc Id Cell Cell Band Dx Cause Event Type
Routing Cat CS Paging Time Success
Indicator
Imei Imsi Isdn Lac Nbr of IMSI Nbr of TMSI Paging Plmn Id Plmn Id Previous Radio
Category Pagings Pagings Reason New Lac Access Info
Report Report Reports Rnc Id Rnc Id Mcc Rnc Id Mnc Roaming Routing Sac SGSN Vlr Unit Id
Number Time Sent Status Category Attached
IHSPA_Indic
ator

Traffica Vlr_Paging_Reason
VLR Reports Fields 0x00 = Mobile terminated call, can be speech or data call, MTC_paging
0x01 = Searching, MAP-Provide-Roaming-Number, PRN_search
0x02 = Call completion to busy subscriber, CCBS
Vlr_Event_Type 0x03 = Location services, LCS
0x04 = Mobile terminated SMS, MT_SMS
0x00000001 = Paging: ms search
0x05 = Mobile terminated USSD, MT_USSD
0x00000002 = Paging: a-if 0x06 = Paging, MAP-Provide-Subscriber-Info, PSI_paging
0x07 = Mobile terminated voice call, MTC_speech
0x00000004 = Paging: sgsn
0x08 = Mobile terminated non-transparent data call, MTC_nt_data
0x20000000 = Subscriber busy after paging 0x09 = Mobile terminated transparent data call, MTC_tp_data
0x0A = Pre-paging, MAP-Provide-Subscriber-Info, PSI_pre_paging
0x80000000 = VLR executes search on A/Iu
0x0B = Searching, MAP-Provide-Subscriber-Info, PSI_search
interface as well as paging on SGs interface
0x0D = paging is initiated after VLR has received the PRN message
(PRN_pre_page)
0x0E = PRN arrives to an unidentified subscriber and the pre-paging
should be started (PRN_pre_search)
0xFF = Not defined
Possible values are defined in section [VLR Paging Reason] in the file
ccd_msc_vlr.conf.

Paging analysis using Traffica
Traffica Paging
Analysis

Paging Monitoring
Message Monitoring (MM)

Paging Monitoring
CM serv request

Paging Monitoring
AIF PRB is getting the paging request from MMC PRB.
MTC_paging, CCBS_recall, LCS, MT-SMS, MT-USSD

Basically these paging are same from MMC's point of view. The differences are:
In LCS the paging, requester is LCFPRB
In MTC paging, requester is OC2PRB
In MT-SMS paging, requester is SMHPRB
In MT-USSD paging, requester is USSDAM
In CCBS paging MMC sets cm_service_type to nimoc before paging/searching
In CCBS paging MMC sets access_connection_status's flags to done there are no PAR sub-operations
and no tmsi reallocation in this case.
The paging is initiated with message 6845 map_page_ms_s MMC -> AIF
If successful the AIF hand is replying with message 6848 map_process_access_req_s AIF -> MMC
If unsuccessful the AIF hand is replying with message 6847 map_page_nack_s AIF -> MMC
Search is initiated with message 6846 map_search_ms_s MMCPRB -> SGAPRB -> AIFPRB

Paging Monitoring
Monitoring conditions
DX200: ZOECN:BSU:SR:
((OFAM=132)AND(NUM=6845,6846,6847))OR((OFAM=126)AND(NUM=6860,BE8B,EA00))
ATCA: ZOECN:GISU:SR:
((OFAM=132)AND(NUM=6845,6846,6847))OR((OFAM=126)AND(NUM=6860,BE8B,EA00))
AIF <> OFAM 132 and MMC <> OFAM 126

AIF <= MMC 6845 map_page_ms_s, received by AIF master
AIF <= SGA 6846 map_search_ms_s, received by AIF master
AIF => MMC 6847 map_page_nack_s, sent by AIF hand
MMC => VSS 6860 vrif_process_access_request_s, sent by MMC hand
MMC => AVS BE8B vlr_send_ident_s, sent by MMC hand
MMC => VSS EA00 vrif_report_paging_result_s, sent by MMC hand
It is also possible to select a given LAC by adding AND(DATW0D=XXXX) to your monitoring command of
message EA00 only as the LAC has an offset of 13 in the message.

Paging Monitoring
Program block
For message monitoring instead of looking at a single paging event the best is to see the overall procedure results in message
EA00 vrif_report_paging_result_s from MMCPRB to VSSQUI that contains information about the paging result. When the paging
is successful it is followed by message
6860 vrif_process_access_request_s from MMC to VEDIGO that is a request for VLR to start possible security procedures required
for handling an access from a mobile subscriber.
Actual paging message is also seen in D331 from SEGPRO and when successful the MMCPRB sends a positive acknowledgement
to Call Control with message E92F subscriber_paging_req_ack_s
MMC -> OC2 MMC -> VNNQUI (PRN-Search, PSI-paging) MMC -> SMHPRB (MT-SMS) MMC -> USSDAM (MT-USSD) MMC ->
CCBSPR (CCBS-Recall).
For LTE the only difference is the new PRB SG7PRB that takes care of the SGs interface SCTP/IP protocol connections towards
MMEs and also handles the SGsAP protocol procedures by mapping SGs interface messages to internal format between AIFPRB
and MME. In principle, SG7PRB just forwards the interface messages to AIFPRB which together with MMCPRB controls the
procedures of SGs interface. Located in BSU unit/GISU unit

Paging Monitoring
DX200: ZOECN:BSU:SR:((OFAM=132)AND(NUM=6845,6846,6847))OR((OFAM=126)AND(NUM=6860,BE8B,EA00))
ATCA: ZOECN:GISU:SR:((OFAM=132)AND(NUM=6845,6846,6847))OR((OFAM=126)AND(NUM=6860,BE8B,EA00))
AIF <> OFAM 132 and MMC <> OFAM 126

It is also possible to select a given LAC by adding AND(DATW0D=XXXX) to your monitoring command of message EA00 only as the
LAC has an offset of 13 in the message.

Paging Monitoring
// Check that monitoring collect data
Tatu hit monitoring macro ZOEIN:BSU
// collect monitorings as long as buffer is full (number of messages is
AIF and MMC paging related messages monitoring example not increasing)
(M14 level):
Look active VLU pairs: ZUSI:BSU; // Stop monitoring

ZOESN:BSU
//Take service terminal session to OMU
ZDDS; // Copy monitoring buffer to files in root of OMU WDU-0, from all
// kill monitorings BSUs
ZOEK ZZZZZZOEGF:1A:W0-/BSU_00.BIN
// reserve buffer for monitoring. To all active BSU pairs. Buffer
size effect to number of reports collected. ZZZZZZOEGF:1D:W0-/BSU_11.BIN
ZOEBRN:BSU:8FFFFF,0
// set monitoring conditions. Messages 6845,6846 and 6847 are
// kill monitorings
collected from 0132 AIF Program Block as well as messages
6860,BE8B and EA00 from 0126 MMC Program Block ZOEK
ZOECN:BSU:SR: // FTP BSU_XX.BIN files to your PC with some FTP client (total
((OFAM=132)AND(NUM=6845,6846,6847))OR((OFAM=126)AN commander, Reflection )
D(NUM=6860,BE8B,EA00)) // delete BSU_XX.BIN file from OMU WDU
// start monitoring ZMD:W0-/BSU*.BIN
ZOEMN:BSU
Paging Monitoring
Log file examples
Here embedded are two log files of paging events,

one single successful TIMSI paging Single paging
and the other with first three unsuccessful TIMSI paging
attempts and then a single successful IMSI paging.
Multiple Paging
log

Paging Monitoring
IDA2

Paging Monitoring
Post process IDA2
Add this .iaf file to: C:\APPS\IDA2\AA\ (IDA2 installation directory:
basic_conversions
.iaf
Take these monitoring files to IDA2 tool and run automated analysis using this .ias file:
V L R - E 9 F F - S T A T . I A S
Location of this file is asked when you run automated analysis.

As result you get comma separated text file, what you can open to excel or some other post processing program.
OBS. Handling big files with IDA2 is slow!
IDA2 software can be downloaded from iSOURCE: https://isource.access.nokiasiemensnetworks.com/frs/?group_id=5194&release_id=7405
EE IDA2 service homepage at:
https://confluence.inside.nokiasiemensnetworks.com/display/EE/EE+IDA2

Paging Monitoring
ESSENCE

Paging Monitoring
Post process Essence
Essence tool is useful to monitoring post processing of several statistical and call trouble shooting cases. It have different
profiles (different monitoring needed) to post process: for example: Analyze AIF and Analyze VED VSS for page and location
update.
Take monitorings to Essence and run: TOOLS/ANALYZE AIF or ANALYZE VED VSS
It will give overview of AIF process activities including paging failures.
An example of Analyze AIF report here from one APAC operator network:
Analyze AIF.txt
An example of Analyze VED VSS report / Statistics here from one APAC operator network:
Analyze VED
VSS.txt
You can also get detailed report as well as detailed (with attempts), these have list of all attempts (long report!). Detailed (with attempts)
have all reported statistical reports, so you can see for example if LU have failed caused by authentication failure.

Essence Paging Analysis
AIF analysis uses following messages for information
AIF => MMC 6842 map_authenticate_nack_s, sent by AIF hand
AIF => MMC 6951 map_update_location_s, sent by AIF hand
AIF <= MMC 6952 map_update_location_ack_s, received by AIF hand
AIF <= MMC 6954 map_update_location_nack_s, received by AIF hand
DX200: ZOECN:BSU:SR:
((OFAM=132)AND(NUM=6842,6845,6846,6847,6951,6952,6954))OR((OF
AM=126)AND(NUM=6860,BE8B,EA00))
ATCA: ZOECN:GISU:SR:
((OFAM=132)AND(NUM=6842,6845,6846,6847,6951,6952,6954))OR((OF
AM=126)AND(NUM=6860,BE8B,EA00))
Essence Paging Analysis Page Stats (6860 & EA00), CC
CC Description Pages, T I Count %
0000 normal_end_of_the_call 0 0 29268 5.06%
Page Fail Stats (6847) 0000 normal_end_of_the_call 1 0 416733 72.05%
CC Description Pages Count % 0000 normal_end_of_the_call 2 0 31920 5.52%
0005 b_subscriber_busy 0 55385 51.98% 0000 normal_end_of_the_call 3 0 4398 0.76%
0012 no_paging_response 1 11896 11.16% 0000 normal_end_of_the_call 0 1 257 0.04%
0015 normal_unspecified 0 1 0.00% 0000 normal_end_of_the_call 3 1 524 0.09%
0015 normal_unspecified 3 2 0.00% 0000 normal_end_of_the_call 0 2 261 0.05%
030A cl_a_onhook_set_up_phase 0 3 0.00% 0000 normal_end_of_the_call 2 2 28 0.00%
030B cl_a_onhook_answer_phase 0 2 0.00% 0005 b_subscriber_busy 0 0 55386 9.58%
0318 terminal_switch_off 0 1 0.00% 0012 no_paging_response 0 0 28722 4.97%
0407 err_answer_from_co_process 0 29 0.03% 0012 no_paging_response 1 0 1223 0.21%
0603 no_response_from_co_proces 0 31 0.03% 0012 no_paging_response 2 0 417 0.07%
0810 facility_not_supported 0 1 0.00% 0012 no_paging_response 3 0 7992 1.38%
0817 n_unallocated_number 0 1 0.00% 0015 normal_unspecified 0 0 2 0.00%
0845 ranap_protocol_error 0 2 0.00% 030A cl_a_onhook_set_up_phase 0 0 13 0.00%
0B13 radio_if_failure 0 48 0.05% 030B cl_a_onhook_answer_phase 0 0 1 0.00%
0B15 ciphering_not_succeeded 0 1 0.00% 0318 terminal_switch_off 0 0 1 0.00%
0B16 remote_equipment_failure 0 17 0.02% 0407 err_answer_from_co_process 0 0 29 0.01%
0B1B radio_if_msg_failure 0 2 0.00% 0810 facility_not_supported 0 0 1 0.00%
0D04 subs_sig_protocol_error 1 2 0.00% 0845 ranap_protocol_error 0 0 2 0.00%
0D07 no_user_responding 0 2 0.00% 0B13 radio_if_failure 0 0 47 0.01%
===================================================== 0B15 ciphering_not_succeeded 0 0 1 0.00%
106557% 0B16 remote_equipment_failure 0 0 17 0.00%
0B1B radio_if_msg_failure 0 0 2 0.00%
0D04 subs_sig_protocol_error 0 0 2 0.00%
========================================================
578402

Page Stats, CC per Service Type (6860 & EA00)
Service Type CC Count int-% all-% Description
4 sm_transfer_c
0005 45691 60.85% 7.90% b_subscriber_busy
0012 29291 39.01% 5.06% no_paging_response
0015 2 0.00% 0.00% normal_unspecified
030A 13 0.02% 0.00% cl_a_onhook_set_up_phase
0318 1 0.00% 0.00% terminal_switch_off
0407 24 0.03% 0.00% err_answer_from_co_process
0810 1 0.00% 0.00% facility_not_supported
0845 2 0.00% 0.00% ranap_protocol_error
0B13 41 0.05% 0.01% radio_if_failure
0B15 1 0.00% 0.00% ciphering_not_succeeded
0B16 16 0.02% 0.00% remote_equipment_failure
0B1B 2 0.00% 0.00% radio_if_msg_failure
0D04 2 0.00% 0.00% subs_sig_protocol_error
5 mt_sm_tr_c
0000 384007 100.00% 66.39% normal_end_of_the_call
8 ss_request_c
9 mt_ss_req_c
10 mtc_c
030B 1 0.00% 0.00% cl_a_onhook_answer_phase
0B13 6 0.01% 0.00% radio_if_failure
0B16 1 0.00% 0.00% remote_equipment_failure
=====================================================================================
578402
MTC Page Success Ratio (6860 & EA00)
94483 (succ) / 113085 (total) = 83.55%
MTC Page Success Ratio - excluding CC 5 (6860 & EA00)

104138 (succ) / 113085 (total) = 92.09%
SMS Page Success Ratio (6860 & EA00)

384007 (succ) / 459094 (total) = 83.64%
SMS Page Success Ratio - excluding CC 5 (6860 & EA00)

429698 (succ) / 459094 (total) = 93.60%
Page Fail Stats, CC per Service Type per LAC

LAC LAC(hex) Service Type CC Count int-% all-% Description
60 003C
4 sm_transfer_c 0005 815 9.28% 0.14% b_subscriber_busy
4 sm_transfer_c 0012 524 5.97% 0.09% no_paging_response
4 sm_transfer_c 0407 3 0.03% 0.00%
err_answer_from_co_process
5 mt_sm_tr_c 0000 5766 65.64% 1.00%
normal_end_of_the_call
8 ss_request_c 0005 2 0.02% 0.00% b_subscriber_busy
8 ss_request_c 0012 3 0.03% 0.00% no_paging_response
9 mt_ss_req_c 0000 81 0.92% 0.01%
10 mtc_c 0000 1352 15.39% 0.23%
10 mtc_c 0005 99 1.13% 0.02% b_subscriber_busy
10 mtc_c 0012 139 1.58% 0.02% no_paging_response
Essence Analyze VED VSS, Statistics
6881 map_user_abort_s 6077
==============================================
VLR analysis uses following messages for information 6077
VSS <= XXX 6881 map_user_abort_s, received by VSS hand MAP Stats, 6881 map_user_abort_s CC
VSS <> XXX E186 ap_abort_s, sent/received by VSS Count

VSS <= XXX E388 ap_operation_nack_s, received by VSS hand 0005 b_subscriber_busy
0012 no_paging_response
28
1
VED <= XXX E390 ap_operation_s, received by VED 0015 normal_unspecified 33
VSS <= XXX E390 ap_operation_s, received by VSS master/hand 0208 re_establishment_failed
030A cl_a_onhook_set_up_phase
1
2251
VSS => XXX E390 ap_operation_s, sent by VSS hand 030B cl_a_onhook_answer_phase 1693
VSS => VTT E9FE vlr_event_hlr_if_report_s, sent by VSS hand 0316 memory_capacity_exceeded
0318 terminal_switch_off
280
37
VSS => VTT E9FF vlr_event_report_s, sent by VSS hand 0405 err_req_from_co_process 136
0603 no_response_from_co_proces 25
080F circuit_congestion 2
0811 network_failure 12
0818 n_line_out_of_service 6
0885 mgw_internal_failure 1
0A04 trunk_circ_protocol_error 2
0B13 radio_if_failure 461
Monitoring conditions 0B14 handover_failure 1
0B16 remote_equipment_failure 2
ZOECN:CMM:R:(OFAM=426)AND(NUM=E390) 0B1A bssmap_protocol_error 51
ZOECN:VLRU:SR: 0B1B radio_if_msg_failure
0D04 subs_sig_protocol_error
6
16
(OFAM=512)AND(NUM=6881,E186,E388,E390,E9FE, 0D08 gsm_erh408_prot_timer_exp 1032
================================================
E9FF) 6077
Done!

Essence Analyze VED VSS, Statistics
Event Stats, CC Count
Event Normal Combined
00000002 paging_aif
0000 normal_end_of_the_call 24227
0012 no_paging_response 2062
0407 err_answer_from_co_process 1
0810 facility_not_supported 2
0B13 radio_if_failure 2
Page Stats, CC per LAC

LAC LAC(hex) Page_Reason CC Description Count %
60 003C
4 MT_SMS 0000 normal_end_of_the_call 188 0.7%
4 MT_SMS 0012 no_paging_response 24 0.1%
5 MT_USSD 0000 normal_end_of_the_call 5 0.0%
7 MTC_speech 0000 normal_end_of_the_call 123 0.5%
7 MTC_speech 0012 no_paging_response 18 0.1%
Successful Page Stats

Page_Reason TMSI-Page IMSI-Page P-time Count
4 MT_SMS 0 0 0.0 828 Unsuccessful Page Stats
4 MT_SMS 1 0 1.3 10125 Page_Reason TMSI-Page IMSI-Page Count
4 MT_SMS 2 0 1.2 1527 4 MT_SMS 0 0 3
4 MT_SMS 3 0 1.3 137 4 MT_SMS 1 0 335
4 MT_SMS 0 1 1.9 11 4 MT_SMS 2 0 62
4 MT_SMS 0 2 1.1 13 4 MT_SMS 3 0 754
4 MT_SMS 0 3 2.0 3 4 MT_SMS 0 1 7
5 MT_USSD 0 0 0.0 27 4 MT_SMS 0 3 33
5 MT_USSD 1 0 0.9 276 5 MT_USSD 0 0 2

Paging Monitoring
Emil

Paging Monitoring in Emil
Emil collect messages related to same call / transaction into one entity, it is mostly
used as trouble shooting, not statistical tool.
Two standard profiles can be used MSS_AIF and MSS_VSS

Also EL made MSS_paging can be used
Monitoring conditions are / should be in profile in description.txt file.
Sacks are same as with IDA2 tool.
Latest Emil tool:

https://workspaces-emea.int.nokia.com/sites/E2EMaintainability/RAN_L3_Data_Collector_and_Analyzer/de
fault.aspx
https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=529257468&objAct
ion=browse&viewType=1
Access rights needed
Emil profiles are:

https://isource.access.nokiasiemensnetworks.com/projects/emilprofiles

Paging Monitoring
EMIL MSS_VSS profile
VSS Profile v1.0 100301
timo.koponen@nsn.com
monitoring example;
ZOECN:VLRU:SR:OFAM=512
ZOECN:SIGU:SR:OFAM=127

EMIL MSS_Paging profile

Paging Monitoring
Post process Emil

Paging Monitoring
SiMo (NetHawk) EXFO

Paging Monitorings with SiMo (NetHawk) EXFO
SiMo (Signaling Monitoring tool) is only tool (except internal monitoring) to monitor all signaling
interfaces of NSN HLR, MSC, MSS, SGSN, MME? without direct physical connection to these
interfaces. Only IP connectivity needed to BDCU (DX) or OMU (ATCA).
So it is really easy to take signaling monitoring.
SiMo is part of M5 3.X monitoring tool, several other options are available for this tool, look:
https://www.nethawk.fi/
Latest tool versions have KPI reporting also, how useful these KPI reports are is not clear.
Limitations and concerns are:

SiMo need feature activation in NW element, activation have been possible by patching up till M14,
this need to be checked in new SW releases.
Filtering one call case (all messages related to this call) have been limited. This have improved over
the years, latest M5 releases need to be checked.
IP bandwidth needed between client and NW element under monitoring, depend on monitored links
traffic.
Also protocol and ports used for SiMo need to be open in IP network

After the IP connectivity is build:
1. Connect to NW element (BDCU or OMU IP address). More than one element can be monitored at
same time. Limitations?
2. Specify the SPCs of monitored traffic (MPT routing info needed), max is 3-5? Need to be
checked, depend on IP bandwidth and client PC specifications. So simultaneous monitoring is
possible. Needed in many call case trouble shooting. For ex simultaneous SGSN / MME (packet
core) and MSS (circuit core) cases.
3. Start monitoring. Signaling can be seen online (some transmission and processing delays)
4. Display monitoring can be filtered (as well as stored monitoring, but this is not recommended,
many times there is need to check some other signaling later on) to show only messages under
interest.
5. Monitoring is saved to client PC. Either ring buffer to see latest messages or all monitoring of
longer period. (normally saved to several files) to further post processing.
6. These saved monitoring can be viewed by free tool: M5 viewer.
7. EXFO support all known signaling protocols.
8. All messages have also NW element time stamp. This is useful if there is need to find some
specific call case in monitoring. For ex observation report time stamp used to find signaling
monitoring.

SiMo / EXFO is not widely used in NSN nor customers.
M5 EXFO tool have also useful Protocol Help. Information of all supported protocols and their
messages in quite good details. OBS: protocol_help.chm file is available in installation package. (at
least v3.7 level)
Other Signaling monitoring tools:

Wireshark: https://www.wireshark.org/
External Probes Tekelec, Astelia etc. Traffica for Probe is able to work with those probes.

WSiMo
Get the tool and other needed SW:
https://share.inside.nokiasiemensnetworks.com/thread/37288?tstart=0
Wsimo is tool to capture and analyze SS7 signaling in DX200 and IPA 2800 platforms, example: MSS,
RNC, MGW, HLR, SGSN etc.
With this tool you can do most of the task of common protocol analyzers and more. Wsimo tool is
designed to be easy to use.
Simply open wsimo.hit macro to HIT and start the macro. Interactive menu will guide you to rest of the
process.
To use the tool you need to have these software installed in your PC:
- Wireshark, minimum version 1.8.4 http://www.wireshark.org/
- HIT, recommended version is 2.10-4
- Microsoft Visual C++ 2010 run-time environment (
http://www.microsoft.com/en-us/download/details.aspx?id=8328 )
For the network element and connectivity you need to have

- MML connection with enough access to use service terminal commands also.
- FTP read access from your PC to network element
- Sigtran signaling links defined and active
Download wsimo signaling monitoring tool from:
https://isource.access.nokiasiemensnetworks.com/projects/hannupirila

1.0 Paging Optimization

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1.0 Paging Optimization

Uploaded by

Copyright:

Available Formats

MSS Optimization

1 Nokia 2016 For Internal use

1. Paging Basic Analysis Flow

2 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

3 Nokia 2016 For Internal Use

4 Nokia 2016 For Internal Use

5 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

6 Nokia 2016 For Internal Use

MAP/C SEND ROUTING INFORMATION

CALL SETUP CONTINUE

7 Nokia 2016 For Internal Use

8 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

9 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

10 Nokia 2016 For Internal Use

VLR measurement, part 1 (82/52H)

11 Nokia 2016 For Internal Use

12 Nokia 2016 For Internal Use

Alternate CS paging is performed when the 2G-SGSN sends a

13 Nokia 2016 For Internal Use

Standard report (paging part)

Additional paging counters in the ASCII report:

14 Nokia 2016 For Internal Use

The following counters

15 Nokia 2016 For Internal Use

These counters are printed in the report only

16 Nokia 2016 For Internal Use

17 Nokia 2016 For Internal Use

{[(M353B3C4 / PAGING ATTEMPT WITH TMSI PER LAC, SUCCESSFUL) +

Paging failure counters

19 Nokia 2016 For Internal Use

Paging Success Rate%

20 Nokia 2016 For Internal Use

KPI Name Paging success ratio (CS only)

Formula 100 * ( PagingThroughAIFSucc /( PagingThroughAIFAttempts )

21 Nokia 2016 For Internal Use

KPI Name Paging attempt success ratio, per LAC

Formula 100 * ( PagingSuccPerLA /( PagingAttemptPerLA )

22 Nokia 2016 For Internal Use

KPI Name EPS Paging Success Ratio %

Formula 100*( PAGING_EPS_DOMAIN_SUCCESS )/( PAGING_EPS_DOMAIN_ATTEMPT )

Ratio of successful paging procedures using SGs interface (SGsAP-PAGING-REQUEST

23 Nokia 2016 For Internal Use

Raw Measurement: Light Analysis:

Paging Per LAC Paging Per LAC

24 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

25 Nokia 2016 For Internal Use

26 Nokia 2016 For Internal Use

27 Nokia 2016 For Internal Use

29 Nokia 2016 For Internal Use

PAGING_ACCEPT_TIMER (002:1821) PRFILE parameter determines in seconds the duration of the

31 Nokia 2016 For Internal Use

To support the possibility of continuing call setup after

32 Nokia 2016 For Internal Use

33 Nokia 2016 For Internal Use

OBS. TMSI here mean IMSI!

34 Nokia 2016 For Internal Use

1. Paging Basic Analysis Flow

35 Nokia 2016 For Internal Use

36 Nokia 2016 For Internal Use