Professional Documents
Culture Documents
Workshop
Paging Optimization
Mohsin Ismail
27-04-2016
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
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:
PSR%
VLR_M82
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
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.
28 Nokia 2016 For Internal Use
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.
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 Paging
Analysis
CM serv request
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
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))
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.
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
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.
Multiple Paging
log
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
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.
Monitoring conditions
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))
51 Nokia 2016 For Internal Use
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%
0012 no_paging_response 2 2131 2.00% 0000 normal_end_of_the_call 1 1 598 0.10%
0012 no_paging_response 3 36974 34.70% 0000 normal_end_of_the_call 2 1 49 0.01%
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%
030A cl_a_onhook_set_up_phase 1 9 0.01% 0000 normal_end_of_the_call 3 2 287 0.05%
030A cl_a_onhook_set_up_phase 2 10 0.01% 0000 normal_end_of_the_call 0 3 62 0.01%
030A cl_a_onhook_set_up_phase 3 7 0.01% 0000 normal_end_of_the_call 3 3 159 0.03%
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
monitoring example;
ZOECN:VLRU:SR:OFAM=512
ZOECN:SIGU:SR:OFAM=127
External Probes Tekelec, Astelia etc. Traffica for Probe is able to work with those probes.