VoLTE Product Documentation (NFV) V500R018C00

KPI
Contents
9.1 KPI
9.1.1 VoLTE Network KPIs
9.1.2 Service Accessibility KPIs
9.1.2.1 Registration
9.1.2.1.1 Number of Defined Subscribers
9.1.2.1.2 Number of Registered Subscribers
9.1.2.1.3 Number of Registered VoLTE Subscribers Through an LTE Network
9.1.2.1.4 Number of VoLTE Roaming Subscribers on an LTE Network
9.1.2.1.5 Number of Registered VoBB Subscribers
9.1.2.1.6 Number of Registered IN Subscribers
9.1.2.1.7 Initial Registration Success Rate
9.1.2.1.8 VoLTE Initial Registration Success Rate on an LTE Network
9.1.2.1.9 Re-registration Success Rate
9.1.2.1.10 VoLTE Re-registration Success Rate on an LTE Network
9.1.2.1.11 Authentication Success Rate
9.1.2.1.12 Number of Registered VoWiFi Subscribers
9.1.2.1.13 Number of Registered VoWiFi Auxiliary Devices
9.1.2.1.14 VoWiFi Initial Registration Success Rate
9.1.2.1.15 VoWiFi Re-registration Success Rate
9.1.2.2 Session
9.1.2.2.1 Session Connection Delay
9.1.2.2.2 MO Session Connection Rate on an LTE Network
9.1.2.2.3 MT Session Connection Rate on an LTE Network
9.1.2.2.4 MO Session Answer Rate on an LTE Network
9.1.2.2.5 MT Session Answer Rate on an LTE Network
9.1.2.2.6 MO Session Connection Rate (Subscriber Cause)
9.1.2.2.7 MT Session Connection Rate (Subscriber Cause)
9.1.2.2.8 MO Short Message Success Rate
9.1.2.2.9 MT Short Message Success Rate
9.1.2.2.10 VoWiFi MO Session Connection Rate
9.1.2.2.11 VoWiFi MT Session Connection Rate
9.1.2.2.12 VoWiFi MO Session Answer Rate
9.1.2.2.13 VoWiFi MT Session Answer Rate
9.1.3 Service Retainability KPI
9.1.3.1 Handover
9.1.3.1.1 Success Rate of LTE-to-GSM eSRVCC Handovers
9.1.3.1.2 Success Rate of LTE-to-UMTS eSRVCC Handovers
9.1.3.1.3 Interruption Duration During an eSRVCC Handover
9.1.3.1.4 Number of Handovers from Wi-Fi to LTE
9.1.3.1.5 Number of Handovers from LTE to Wi-Fi
9.1.3.2 Call Drop Rate
9.1.3.2.1 VoLTE Call Drop Rate
9.1.3.2.2 Rate of Abnormally Released Bearers on the eNodeB
9.1.3.2.3 VoWiFi Call Drop Rate
9.1.4 Service Integrity KPIs
9.1.4.1 Voice Quality
9.1.4.1.1 Voice Quality of Voice Calls
9.1.4.1.2 Voice Quality of Video Calls
9.1.4.1.3 Voice Quality of VoWiFi Voice Calls
9.1.4.1.4 IP QoS Lost Rate of VoWiFi Access Network
9.1.5 Traffic Model KPIs
9.1.5.1 Traffic
9.1.5.1.1 Traffic of Answered VoLTE Sessions
9.1.5.1.2 Traffic of Answered VoWiFi Sessions
9.1.5.2 Average Session Duration
9.1.5.2.1 Average VoLTE Session Duration
9.1.5.2.2 Average VoWiFi Session Duration
9.1.5.3 Service Times
9.1.5.3.1 VoLTE Subscriber BHCA
9.1.5.3.2 Number of Initial Registrations
9.1.5.3.3 Number of Re-registrations
9.1.5.4 Traffic Model Per Subscriber
9.1.5.4.1 Average Traffic of Answered Sessions Per Subscriber
9.1.5.4.2 Average BHCA Per Subscriber
9.1.5.4.3 BHCA of VoWiFi Session Per Subscriber
9.1.5.4.4 BHCA of VoWiFi Initial Registration Per Subscriber
9.1.5.4.5 BHCA of VoWiFi Re-Registration Per Subscriber
9.1.6 References of Related NE Counters
9.1.6.1 CSC3300
9.1.6.1.1 335555337 S-CSCF MO Oxx Responses Measurement
9.1.6.1.2 335555339 S-CSCF MT Oxx Responses Measurement
9.1.6.1.3 335655491 Number of S-CSCF Initial Registration Attempts
9.1.6.1.4 335655492 Number of S-CSCF Successful Initial Registrations
9.1.6.1.5 335655519 Number of S-CSCF Re-registration Attempts
9.1.6.1.6 335655520 Number of S-CSCF Successful Re-registrations
9.1.6.1.7 335655576 Number of S-CSCF MO Session Attempts
9.1.6.1.8 335655578 Number of S-CSCF Answered MO Sessions
9.1.6.1.9 335655581 Number of S-CSCF MT Session Attempts
9.1.6.1.10 335655583 Number of S-CSCF Answered MT Sessions
9.1.6.1.11 335664321 Number of S-CSCF MO Sessions Released Before Ringing
9.1.6.1.12 335664322 Number of S-CSCF MT Sessions Released Before Ringing
9.1.6.1.13 335664324 Number of S-CSCF MO Sessions Released After Ringing
9.1.6.1.14 335664325 Number of S-CSCF MT Sessions Released After Ringing
9.1.6.1.15 335672421 Number of S-CSCF Registered Users
9.1.6.1.16 335672443 Number of S-CSCF Using AKA Authentication Attempts
9.1.6.1.17 335672444 Number of S-CSCF Successful Using AKA Authentication Attempts
9.1.6.2 ATS9900
9.1.6.2.1 478155820 MO Short Message Attempts
9.1.6.2.2 478155821 MO Short Message Success Times
9.1.6.2.3 478155823 MT Short Message Attempts
9.1.6.2.4 478155824 MT Short Message Success Times
9.1.6.2.5 478155988 Number of CCU Subscribers
9.1.6.2.6 478156521 Number of Registered IN Subscribers on the ATS
9.1.6.2.7 478156717 Number of Successfully Registered Wi-Fi Subscribers
9.1.6.2.8 478156718 Number of Switches from Wi-Fi to LTE
9.1.6.2.9 478156719 Number of Switches from LTE to Wi-Fi
9.1.6.2.10 478156721 Number of Auxiliary Devices Registering over Wi-Fi
9.1.6.3 HSS9860
9.1.6.3.1 352324100 Number of Provisioned IMS Subscriptions Stored in an HSS
9.1.6.4 SE2900
9.1.6.4.1 1907465347 Number of ABCF Initial Registration Attempts
9.1.6.4.2 1907465348 Number of ABCF Successful Initial Registrations
9.1.6.4.3 1907465350 Number of ABCF Re-registration Attempts
9.1.6.4.4 1907465351 Number of ABCF Successful Re-registrations
9.1.6.4.5 1907465358 Number of Users in The Access Network
9.1.6.4.6 1907466045 Number of ABCF MO Session Attempts
9.1.6.4.7 1907466046 Number of ABCF MO Connected Sessions
9.1.6.4.8 1907466047 Number of ABCF MO Answered Sessions
9.1.6.4.9 1907466048 Number of ABCF MT Session Attempts
9.1.6.4.10 1907466049 Number of ABCF MT Connected Sessions
9.1.6.4.11 1907466050 Number of ABCF MT Answered Sessions
9.1.6.4.12 1907466085 Traffic of ABCF MO Answered Sessions
9.1.6.4.13 1907466086 Traffic of ABCF MT Answered Sessions
9.1.6.4.14 1907466105 Mean Duration from Answering to Release of ABCF Sessions
9.1.6.4.15 1907466106 Mean Duration from Originating to Ringing of ABCF MO Sessions
9.1.6.4.16 1907466107 Mean Duration from Originating to Ringing of ABCF MT Sessions
9.1.6.4.17 1907466118 Number of ABCF MO Session Interruptions
9.1.6.4.18 1907466119 Number of ABCF MT Session Interruptions
9.1.6.4.19 1907466549 Number of ABCF Roaming Subscribers in The Access Network
9.1.6.4.20 1907466568 ABCF Access Network IP QoS Mos Average
9.1.6.4.21 1907467000 Number of Session Interruptions Triggered by Wireless Network on
MO-Side A-BCF
9.1.6.4.22 1907467001 Number of Session Interruptions Triggered by Wireless Network on
MT-Side A-BCF
9.1.6.4.23 1907467809 Number of ABCF Registered VoWiFi Users
9.1.6.4.24 1907467810 Number of ABCF VoWiFi Initial Registration Attempts
9.1.6.4.25 1907467811 Number of ABCF VoWiFi Successful Initial Registrations
9.1.6.4.26 1907467813 Number of ABCF VoWiFi Re-registration Attempts
9.1.6.4.27 1907467814 Number of ABCF VoWiFi Successful Re-registrations
9.1.6.4.28 1907467816 Number of ABCF MO-Side VoWiFi Session Interruptions
9.1.6.4.29 1907467817 Number of ABCF MT-Side VoWiFi Session Interruptions
9.1.6.4.30 1907467819 Number of ABCF MO-Side VoWiFi Session Interruptions Triggered
by Wireless Network
9.1.6.4.31 1907467820 Number of ABCF MT-Side VoWiFi Session Interruptions Triggered
by Wireless Network
9.1.6.4.32 1907468093 Number of ABCF MO-Side VoWiFi Session Attempts
9.1.6.4.33 1907468094 Number of ABCF MO-Side VoWiFi Connected Sessions
9.1.6.4.34 1907468095 Number of ABCF MO-Side VoWiFi Answered Sessions
9.1.6.4.35 1907468105 Traffic of ABCF MO-Side VoWiFi Answered Sessions
9.1.6.4.36 1907468110 Number of ABCF MT-Side VoWiFi Session Attempts
9.1.6.4.37 1907468111 Number of ABCF MT-Side VoWiFi Connected Sessions
9.1.6.4.38 1907468112 Number of ABCF MT-Side VoWiFi Answered Sessions
9.1.6.4.39 1907468122 Traffic of ABCF MT-Side VoWiFi Answered Sessions
9.1.6.4.40 1907468135 ABCF VoWiFi Access Network IP QoS LosRate Average
9.1.6.4.41 1907468153 ABCF VoWiFi Access Network IP QoS Mos Average
9.1.6.5 MSOFTX3000
9.1.6.5.1 84164965 Number of Requested 2G Intra-MSC eSRVCC Handovers
9.1.6.5.2 84164967 Number of Requested 2G Inter-MSC eSRVCC Handovers
9.1.6.5.3 84164975 Number of Requested 3G Intra-MSC eSRVCC Handovers
9.1.6.5.4 84164977 Number of Requested 3G Inter-MSC eSRVCC Handovers
9.1.6.5.5 84175689 Number of 2G eSRVCC Service Alerting Request
9.1.6.5.6 84175691 Number of 3G eSRVCC Service Alerting Request
9.1.6.5.7 84176435 Number of 2G eSRVCC Service Pre-Alerting Request Times
9.1.6.5.8 84176438 Number of 3G eSRVCC Service Pre-Alerting Request Times
9.1.6.5.9 84176698 Number of Successful Times During 2G eSRVCC Handovers
9.1.6.5.10 84176700 Number of Successful Times During 3G eSRVCC Handovers
9.1 KPI
VoLTE Network KPIs
Service Accessibility KPIs
Service Retainability KPI
Service Integrity KPIs
Traffic Model KPIs
References of Related NE Counters
Parent Topic: User Manuals

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
Next topic >
9.1.1 VoLTE Network KPIs

NOTE:
Key performance indicators (KPIs) differ depending on networks. The KPIs described in this section are only
for reference and do not constitute a warranty of any kind, express or implied.
KPIs describe service running status and device operating status. The KPI system helps
maintenance personnel to learn the performance measurement system of communications
devices, customize a performance measurement system, and maintain devices and optimize
services based on performance measurement results.
Compared with the traditional CS solution, the VoLTE solution changes greatly in terms of
network architectures and services. The KPI system of traditional CS networks cannot meet
requirements of VoLTE networks. Therefore, the VoLTE KPI system must be set up for
routine monitoring and identifying network performance.
Figure 1 shows the VoLTE network KPI model.
Figure 1 VoLTE network KPI model
Table 1 describes KPIs supported in VoLTE V500R018C00.
NOTE:
KPIs listed in Table 1 apply only to VoLTE networks deployed on VoBB or VoWiFi networks, but do not
apply to VoBB networks deployed on RCS-e/RCS, UC, or CaaS networks.
Table 1 VoLTE Network KPIs

Category Sub- KPI Basic Measurement Measurement NE Applicable
category Entity Unit Network
Service Registration Number of 352324100 Number Provisioning IMS-HSS VoLTE

accessibility Defined of Provisioned IMS Related (HSS9860) network
Subscribers
Subscriptions Stored Measurement
in an HSS
Number of 335672421 Number S-CSCF S-CSCF VoLTE

Registered of S-CSCF Access Type (CSC3300) network
Subscribers
Registered Users User
Measurement
Number of 1907465358 Number ABCF Access ABCF VoLTE

Registered of Users in The Network User (SE2900) network
VoLTE
Subscribers Access Network Measurement
Through an
LTE Network
Number of 1907466549 Number ABCF Access ABCF VoLTE

VoLTE of ABCF Roaming Type Register (SE2900) network
Roaming
Subscribers Subscribers in The Related
on an LTE Access Network Measurement
Network
Number of 478155988 Number ATS CPU ATS VoBB

Registered of CCU Subscribers Usage (ATS9900) network
VoBB
Subscribers Measurement
Number of 478156521 Number ATS Register IM-SSF VoLTE

Registered IN of Registered IN Data (ATS9900) network
Subscribers
Subscribers on the Measurement
ATS
Initial  335655491 S-CSCF S-CSCF VoLTE

Registration Session (CSC3300) network
Success Rate Number of S-
CSCF Initial Unrelated
Registration Measurement
Attempts
 335655492
Number of S-
CSCF Successful
Initial
Registrations
VoLTE Initial  1907465347 ABCF SIP ABCF VoLTE
Registration
Success Rate Number of ABCF Access (SE2900) network

on an LTE Initial Network

Network Registration
Attempts
 1907465348
Number of ABCF
Successful Initial
Registrations
Re-  335655519 S-CSCF S-CSCF VoLTE
registration Session (CSC3300) network
Success Rate Number of S-
CSCF Re- Unrelated
registration Measurement
Attempts
 335655520
Number of S-
CSCF Successful
Re-registrations
VoLTE Re-  1907465350 ABCF Access ABCF VoLTE
registration Type Register (SE2900) network
Success Rate Number of ABCF
on an LTE Re-registration Related
Network Attempts Measurement
 1907465351
Number of ABCF
Successful Re-
registrations
Authentication  335672443 S-CSCF S-CSCF VoLTE
Success Rate Session (CSC3300) network
Number of S-
CSCF Using Unrelated
AKA Measurement
Authentication
Attempts
 335672444
Number of S-
CSCF Successful
Using AKA
Authentication
Attempts
Number of  1907467809  ABCF  ABCF VoLTE
Registered
VoWiFi Number of ABCF Session (SE2900) and
Subscribers Registered Unrelated  ATS VoWiFi

VoWiFi Users Measurem (ATS990 networks

 478156717 ent 0)
Number of  VoWiFi
Successfully Basic
Registered Wi-Fi Measurem
Subscribers ent
Number of 478156721 Number VoWiFi ATS VoLTE
Registered of Auxiliary Devices Basic (ATS9900) and
VoWiFi
Auxiliary Registering over Wi- Measurement VoWiFi
Devices Fi networks
VoWiFi Initial  1907467810 ABCF ABCF VoLTE
Registration Session (SE2900) and
VoWiFi Initial Unrelated VoWiFi
Registration Measurement networks
Attempts
 1907467811
Number of ABCF
VoWiFi
Successful Initial
Registrations
VoWiFi Re-  1907467813 ABCF ABCF VoLTE
registration Session (SE2900) and
VoWiFi Re- Unrelated VoWiFi
registration Measurement networks
Attempts
 1907467814
Number of ABCF
VoWiFi
Successful Re-
registrations
Session Session  Single-session  Single-  Single- VoLTE

Connection network
Delay connection delay: session session
drive test connection connectio
 Average session delay: n delay:
connection delay drive test drive test
 1907466106  Average  Average
Mean session session
Duration of connection connectio
ABCF MO delay: n delay:
ABCF ABCF

Session Session (SE2900)

 1907466107 Related
Mean Measurem
Duration of ent
ABCF MT
Session
MO Session  1907466045 ABCF ABCF VoLTE
Connection Session (SE2900) network
Rate on an Number of ABCF
LTE Network MO Session Related
Attempts Measurement
 1907466046
Number of ABCF
MO Connected
Sessions
MT Session  1907466048 ABCF ABCF VoLTE
Connection Session (SE2900) network
Rate on an Number of ABCF
LTE Network MT Session Related
 1907466049
Number of ABCF
MT Connected
Sessions
MO Session  1907466045 ABCF ABCF VoLTE
Answer Rate Session (SE2900) network
on an LTE Number of ABCF
Network MO Session Related
 1907466047
Number of ABCF
MO Answered
Sessions
MT Session  1907466048 ABCF ABCF VoLTE
Answer Rate Session (SE2900) network
on an LTE Number of ABCF
Network MT Session Related
 1907466050
Number of ABCF
MT Answered
Sessions

MO Session  335655576  S-CSCF S-CSCF VoLTE

Connection (CSC3300) network
Rate Number of S- Session
(Subscriber CSCF MO Related
Cause) Session Attempts Measurem
 335655578 ent
Number of S-  S-CSCF
CSCF Answered MO Oxx
MO Sessions Responses
 335664321 Measurem
Number of S- ent
CSCF MO
Sessions
Released Before
Ringing
 335664324
Number of S-
CSCF MO
Sessions
Released After
Ringing
 335675329 403
Forbidden
 335675330 404
Not Found
 335675334 408
Request Timeout
 335675347 480
Temporarily
Unavailable
 335675351 484
Address
Incomplete
 335675353 486
Busy Here
 335675354 487
Request
Terminated
 335675372 600
Busy Everywhere
 335675373 603
Decline

 335675374 604
Does Not Exist
Anywhere
MT Session  335655581  S-CSCF S-CSCF VoLTE
Connection (CSC3300) network
Rate Number of S- Session
(Subscriber CSCF MT Related
Cause) Session Attempts Measurem
 335655583 ent
Number of S-  S-CSCF
CSCF Answered MT Oxx
MT Sessions Responses
 335664322 Measurem
Number of S- ent
CSCF MT
Sessions
Released Before
Ringing
 335664325
Number of S-
CSCF MT
Sessions
Released After
Ringing
 335677329 403
Forbidden
 335677330 404
Not Found
 335677334 408
Request Timeout
 335677347 480
Temporarily
Unavailable
 335677351 484
Address
Incomplete
 335677353 486
Busy Here
 335677354 487
Request
Terminated
 335677372 600

Busy Everywhere
 335677373 603
Decline
 335677374 604
Does Not Exist
Anywhere
MO Short  478155820 MO IP-SM-GW IP-SM-GW VoLTE
Message Measurement (ATS9900) network
Success Rate Short Message
Attempts
 478155821 MO
Short Message
Success Times
MT Short  478155823 MT IP-SM-GW IP-SM-GW VoLTE
Message Measurement (ATS9900) network
Success Rate Short Message
Attempts
 478155824 MT
Short Message
Success Times
VoWiFi MO  1907468093 ABCF ABCF VoLTE
Session Session (SE2900) and
Connection Number of ABCF
Rate MO-Side VoWiFi Related VoWiFi
Session Attempts Measurement networks
 1907468094
Number of ABCF
MO-Side VoWiFi
Connected
Sessions
VoWiFi MT  1907468110 ABCF ABCF VoLTE
Connection Number of ABCF
Rate MT-Side VoWiFi Related VoWiFi
 1907468111
Number of ABCF
MT-Side VoWiFi
Connected
Sessions
VoWiFi MO  1907468093 ABCF ABCF VoLTE
Session
Answer Rate Number of ABCF Session (SE2900) and

MO-Side VoWiFi Related VoWiFi

 1907468095
Number of ABCF
MO-Side VoWiFi
Answered
Sessions
VoWiFi MT  1907468110 ABCF ABCF VoLTE
Answer Rate Number of ABCF
MT-Side VoWiFi Related VoWiFi
 1907468112
Number of ABCF
MT-Side VoWiFi
Answered
Sessions
Service Handover Success Rate  84164965 2G eSRVCC GTP Peer VoLTE

retainability of LTE-to- Service Entity Name network
GSM Number of
eSRVCC Requested 2G Measurement
Handovers Intra-MSC
eSRVCC
Handovers
 84164967
Number of
Requested 2G
Inter-MSC
eSRVCC
Handovers
 84175689
Number of 2G
eSRVCC Service
Alerting Request
 84176698
Number of
Successful Times
During 2G
eSRVCC
Handovers
Success Rate  84164975 3G eSRVCC GTP Peer VoLTE
of LTE-to- Service Entity Name network
UMTS Number of

eSRVCC Requested 3G Measurement

Handovers Intra-MSC
eSRVCC
Handovers
 84164977
Number of
Requested 3G
Inter-MSC
eSRVCC
Handovers
 84175691
Number of 3G
eSRVCC Service
Alerting Request
 84176700
Number of
Successful Times
During 3G
eSRVCC
Handovers
Interruption Drive test N/A Drive test VoLTE
Duration network
During an
eSRVCC
Handover
Handovers of Switches from Basic (ATS9900) and
from Wi-Fi to
LTE Wi-Fi to LTE Measurement VoWiFi
networks
Handovers of Switches from Basic (ATS9900) and
from LTE to
Wi-Fi LTE to Wi-Fi Measurement VoWiFi
networks
Call drop VoLTE Call  1907466047  ABCF ABCF VoLTE
rate Drop Rate (SE2900) network
Number of ABCF MO
MO Answered Access
Sessions Type
 1907466050 Measurem
Number of ABCF ent
MT Answered  ABCF MT
Sessions Access

 1907466118 Type
Number of ABCF Measurem
MO Session ent
Interruptions  ABCF
 1907466119 Session
Number of ABCF Related
MT Session Measurem
Interruptions ent
 1907467000
Number of
Session
Interruptions
Triggered by
Wireless Network
on MO-Side A-
BCF
 1907467001
Number of
Session
Interruptions
Triggered by
Wireless Network
on MT-Side A-
BCF
Rate of  1526726686 E-RAB eNodeB VoLTE
Abnormally Release (eRAN) network
Released Number of
Bearers on abnormal releases Measurement
the eNodeB of activated E-
RABs for
services with the
QCI of 1 in a cell
 1526726688
Number of
abnormal releases
of activated E-
RABs for
services with the
QCI of 2 in a cell
 1526726668
Number of E-
RAB setup
attempts initiated

by UEs for
services with the
QCI of 1 in a cell
 1526726670
Number of E-
RAB setup
attempts initiated
by UEs for
services with the
QCI of 2 in a cell
VoWiFi Call  1907467816 ABCF ABCF VoLTE
Drop Rate Session (SE2900) and
Number of ABCF
MO-Side VoWiFi Related VoWiFi
Session Measurement networks
Interruptions
 1907467817
Number of ABCF
MT-Side VoWiFi
Session
Interruptions
 1907467819
Number of ABCF
MO-Side VoWiFi
Session
Interruptions
Triggered by
Wireless Network
 1907467820
Number of ABCF
MT-Side VoWiFi
Session
Interruptions
Triggered by
Wireless Network
 1907468095
Number of ABCF
MO-Side VoWiFi
Answered
Sessions
 1907468112
Number of ABCF
MT-Side VoWiFi

Answered
Sessions
Service Voice Voice Quality  Drive test ABCF Access  Drive test VoLTE
integrity quality of Voice Calls Network IP  network
 NE-specific NE-
measurement QoS specific
Measurement measure
1907466568
ABCF Access ment:
Network IP QoS ABCF
Mos Average (SE2900)
Voice Quality  Drive test ABCF Access  Drive test VoLTE

of Video Calls Network IP  network
 NE-specific NE-
measurement QoS specific
Measurement measure
1907466568
ABCF Access ment:
Network IP QoS ABCF
Mos Average (SE2900)
Voice Quality  Drive test ABCF  Drive test VoLTE

of VoWiFi VoWiFi and
Voice Calls  NE-specific  NE-
measurement Access specific VoWiFi
Network IP measure networks
1907468153 QoS
ABCF VoWiFi ment:
Measurement ABCF
Access Network
IP QoS Mos (SE2900)
Average
IP QoS Lost 1907468135 ABCF ABCF ABCF VoLTE
Rate of VoWiFi Access VoWiFi (SE2900) and
VoWiFi
Access Network IP QoS Access VoWiFi
Network LosRate Average Network IP networks
QoS
Measurement
Traffic Traffic Traffic of  1907466085 ABCF ABCF VoLTE
model Answered Session (SE2900) network
VoLTE Traffic of ABCF
Sessions MO Answered Related
Sessions Measurement
 1907466086
Traffic of ABCF
MT Answered
Sessions

Traffic of  1907468105 ABCF ABCF VoLTE

Answered Session (SE2900) and
VoWiFi Traffic of ABCF
Sessions MO-Side VoWiFi Related VoWiFi
Answered Measurement networks
Sessions
 1907468122
Traffic of ABCF
MT-Side VoWiFi
Answered
Sessions
Average Average 1907466105 Mean ABCF ABCF VoLTE

session VoLTE Duration from Session (SE2900) network
Session
duration Duration Answering to Related
Release of ABCF Measurement
Sessions
Average  1907468095 ABCF ABCF VoLTE
VoWiFi Session (SE2900) and
Session Number of ABCF
Duration MO-Side VoWiFi Related VoWiFi
Answered Measurement networks
Sessions
 1907468105
Traffic of ABCF
MO-Side VoWiFi
Answered
Sessions
Service VoLTE  1907466045 ABCF ABCF VoLTE

times Subscriber Session (SE2900) network
BHCA Number of ABCF
MO Session Related
 1907466048
Number of ABCF
MT Session
Attempts
Initial of S-CSCF Initial Session (CSC3300) network
Registrations
Registration Unrelated
Re- of S-CSCF Re- Session (CSC3300) network
registrations

registration Attempts Unrelated

Measurement
Traffic Average  1907466085  ABCF ABCF VoLTE
model per Traffic of (SE2900) network
Answered Traffic of ABCF Session
subscriber Sessions Per MO Answered Related
Subscriber Sessions Measurem
 1907466086 ent
Traffic of ABCF  ABCF
MT Answered Access
Sessions Network
 1907465358 User
Number of Users Measurem
in The Access ent
Network
Average  1907466045  ABCF ABCF VoLTE
BHCA Per (SE2900) network
Subscriber Number of ABCF Session
MO Session Related
Attempts Measurem
 1907466048 ent
Number of ABCF  ABCF
MT Session Access
Attempts Network
 1907465358 User
Number of Users Measurem
in The Access ent
Network
BHCA of  1907467809  ABCF ABCF VoLTE
VoWiFi (SE2900) and
Session Per Number of ABCF Session
Subscriber Registered Related VoWiFi
VoWiFi Users Measurem networks
 1907468093 ent
Number of ABCF  ABCF
MO-Side VoWiFi Session
Session Attempts Unrelated
 1907468110 Measurem
Number of ABCF ent
MT-Side VoWiFi
Session Attempts
BHCA of  1907467809 ABCF ABCF VoLTE
VoWiFi Initial

Registration Number of ABCF Session (SE2900) and

Per Registered Unrelated VoWiFi
Subscriber
VoWiFi Users Measurement networks
 1907467810
Number of ABCF
VoWiFi Initial
Registration
Attempts
BHCA of  1907467809 ABCF ABCF VoLTE
VoWiFi Re- Session (SE2900) and
Registration Number of ABCF
Per Registered Unrelated VoWiFi
Subscriber VoWiFi Users Measurement networks
 1907467813
Number of ABCF
VoWiFi Re-
registration
Attempts
Parent Topic: KPI

Next topic >
9.1.2 Service Accessibility KPIs

Registration
Session
Parent Topic: KPI

< Previous topic Next topic >
9.1.2.1 Registration
Number of Defined Subscribers
Number of Registered Subscribers
Number of Registered VoLTE Subscribers Through an LTE Network
Number of VoLTE Roaming Subscribers on an LTE Network
Number of Registered VoBB Subscribers
Number of Registered IN Subscribers
Initial Registration Success Rate
VoLTE Initial Registration Success Rate on an LTE Network
Re-registration Success Rate
VoLTE Re-registration Success Rate on an LTE Network
Authentication Success Rate
Number of Registered VoWiFi Subscribers
Number of Registered VoWiFi Auxiliary Devices
VoWiFi Initial Registration Success Rate
VoWiFi Re-registration Success Rate
Parent Topic: Service Accessibility KPIs

Next topic >
9.1.2.1.1 Number of Defined Subscribers

 Description
 Unit
 Formula
 Measurement Objects
 Reference Value Range
 Related Notes
Description
This measurement entity counts the number of subscribers who have subscribed to VoLTE
services and are stored in the HSS.
In overlay networking, this measurement entity counts the number of all subscribers
defined on the IMS network. The number of defined VoLTE subscribers cannot be counted
separately.
Unit
Integer
Formula
The value of this measurement entity is equal to the value of the following basic
measurement entity:
 352324100 Number of Provisioned IMS Subscriptions Stored in an HSS
NOTE:
The preceding measurement entity is included in the measurement unit Provisioning Related Measurement,
which belongs to the measurement set IMS-HSS Measurement.
Measurement Objects
IMS-HSS
Reference Value Range
None
Related Notes
None
Parent Topic: Registration
Next topic >
9.1.2.1.2 Number of Registered

Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoLTE subscribers registered with an IMS
network (including VoLTE subscribers roaming to a CS network who are anchored in the
IMS network when receiving calls).
In overlay networking, this measurement entity counts the number of all registered
subscribers on the IMS network. The number of registered VoLTE subscribers cannot be
counted separately.
Unit
Integer
Formula
measurement entity:
 335672421 Number of S-CSCF Registered Users
NOTE:
The preceding measurement entity is included in the measurement unit S-CSCF Session Unrelated
Measurement, which belongs to the measurement set S-CSCF.
Measurement Objects
S-CSCF
None
Related Notes
None
9.1.2.1.3 Number of Registered VoLTE

Subscribers Through an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoLTE subscribers registered with an IMS
network through an LTE network.
In VoLTE+VoWiFi networking, this measurement entity counts the number of registered
VoLTE and VoWiFi subscribers. The number of registered VoLTE subscribers cannot be
counted separately.
Unit
Integer
Formula
measurement entity:
 1907465358 Number of Users in The Access Network
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Access Network User
Measurement, which belongs to the measurement set ABCF SIP Access Network.
Measurement Objects
ABCF
None
Related Notes
None
9.1.2.1.4 Number of VoLTE Roaming

Subscribers on an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of registered VoLTE subscribers who do not
belong to the local IMS network, including the number of national roaming subscribers and
subscribers roaming from other IMS networks.
Unit
Integer
Formula
measurement entity:
 1907466549 Number of ABCF Roaming Subscribers in The Access Network
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Access Type Register Related
Measurement Objects
ABCF
None
Related Notes
None
9.1.2.1.5 Number of Registered VoBB

Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoBB subscribers if the CCU process on the
ATS serves VoBB subscribers when a VoLTE network is deployed on a VoBB network.
When a VoLTE network and a VoBB network are newly deployed and the VCU process on
the ATS serves VoBB subscribers, this measurement entity cannot be used to count the
number of registered VoBB subscribers.
Unit
Integer
Formula
measurement entity:
 478155988 Number of CCU Subscribers
NOTE:
The preceding measurement entity is included in the measurement unit CPU Usage Measurement, which
belongs to the measurement set ATS MODULE.
Measurement Objects
ATS
None
Related Notes
None
9.1.2.1.6 Number of Registered IN

Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoLTE intelligent network (IN) subscribers
registered on the ATS.
In overlay networking, this measurement entity counts the number of all IN subscribers
registered on the ATS. The number of VoLTE IN subscribers cannot be counted separately.
Unit
Integer
Formula
measurement entity:
 478156521 Number of Registered IN Subscribers on the ATS
NOTE:
The preceding measurement entity is included in the measurement unit ATS Register Data Measurement,
which belongs to the measurement set ATS BASIC SERVICE.
Measurement Objects
IM-SSF
None
Related Notes
None
9.1.2.1.7 Initial Registration Success Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of successful initial registrations to initial
registration requests of VoLTE subscribers on an IMS network in a measurement period.
By analyzing the value of this measurement entity, you can obtain the information about
VoLTE initial registrations.
When the S-CSCF receives a REGISTER message from the I-CSCF and the subscriber data
is not stored in the S-CSCF, the S-CSCF determines that this is an initial registration. If the
S-CSCF responds a 200 message to an initial registration request, the initial registration is
successful. The re-registration success rate is excluded from this measurement entity.
In overlay networking, this measurement entity measures the initial registration success rate
for all subscribers. The initial registration success rate for VoLTE subscribers cannot be
measured separately.
Unit
Percentage (%)
Formula
where:
 A: 335655491 Number of S-CSCF Initial Registration Attempts
 B: 335655492 Number of S-CSCF Successful Initial Registrations
NOTE:
The preceding measurement entities are included in the measurement unit S-CSCF Session Unrelated
Measurement Objects
S-CSCF
None
If the value of this measurement entity decreases, more UEs' registrations fail.
Related Notes
If this measurement entity is abnormal, identify the fault as follows:

 Check whether DNS data is correct. If DNS data is incorrect, configure it correctly.
 Check whether S-CSCF data is correct and complete. If S-CSCF data is incorrect or
incomplete, configure it correctly and completely.
 Check whether subscriber creation data is correct and complete. If subscriber creation
data is incorrect or incomplete, configure it correctly and completely.
 Check whether the packet loss rate of the LTE network and IP bearer network is too
high. If the packet loss rate is too high, take measures to ensure that the packet loss rate
does not exceed the maximum allowed value.
9.1.2.1.8 VoLTE Initial Registration

Success Rate on an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
registration requests initiated by VoLTE subscribers who access an LTE network in a
measurement period. By analyzing the value of this measurement entity, you can obtain the
information about VoLTE initial registrations.
When the ABCF receives a 200 message responded to an initial registration request
initiated by a UE, the initial registration is successful. The re-registration success rate is
excluded from this measurement entity.
In VoLTE+VoWiFi networking, this measurement entity measures the initial registration
success rate for VoLTE and VoWiFi subscribers. The initial registration success rate for
VoLTE subscribers cannot be measured separately.
Unit
Percentage (%)
Formula
where:
 A: 1907465347 Number of ABCF Initial Registration Attempts
 B: 1907465348 Number of ABCF Successful Initial Registrations
NOTE:
The preceding measurement entities are included in the measurement unit ABCF Access Type Register
Related Measurement, which belongs to the measurement set ABCF SIP Access Network.
Measurement Objects
ABCF
None
Related Notes

9.1.2.1.9 Re-registration Success Rate

 Description
 Unit
 Formula

 Related Notes
Description
This measurement entity measures the ratio of successful re-registrations to re-registration

requests of VoLTE subscribers on an IMS network in a measurement period. By analyzing
the value of this measurement entity, you can obtain the information about VoLTE re-
registrations.
After a UE successfully initiates an initial registration, it periodically initiates re-
registrations by sending REGISTER messages to keep the network connection alive. If the
S-CSCF responds a 200 message to a re-registration request, the re-registration is
successful. The initial registration success rate is excluded from this measurement entity.
In overlay networking, this measurement entity measures the re-registration success rate for
all subscribers. The re-registration success rate for VoLTE subscribers cannot be measured
separately.
Unit
Percentage (%)
Formula
where:
 A: 335655519 Number of S-CSCF Re-registration Attempts
 B: 335655520 Number of S-CSCF Successful Re-registrations
NOTE:
Measurement Objects
S-CSCF
None
If the value of this measurement entity decreases, more UEs go offline.
Related Notes

9.1.2.1.10 VoLTE Re-registration Success

Rate on an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description

requests initiated by VoLTE subscribers who access an LTE network in a measurement
period. By analyzing the value of this measurement entity, you can obtain the information
about VoLTE re-registrations.
registrations by sending REGISTER messages to keep the network connection alive. When
the ABCF receives a 200 message responded to a re-registration request initiated by a UE,
the re-registration is successful. The initial registration success rate is excluded from this
measurement entity.
In VoLTE+VoWiFi networking, this measurement entity measures the re-registration
success rate for VoLTE and VoWiFi subscribers. The re-registration success rate for
Unit
Percentage (%)
Formula
where:
 A: 1907465350 Number of ABCF Re-registration Attempts
 B: 1907465351 Number of ABCF Successful Re-registrations
NOTE:
The preceding measurement entities are included in the measurement unit ABCF Access Type Register
Related Measurement, which belongs to the measurement set ABCF SIP Access Network.
Measurement Objects
ABCF
None
Related Notes

9.1.2.1.11 Authentication Success Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of successful authentications to authentication

requests after receiving initial registration requests using AKA authentication from UEs in
a measurement period.
In overlay networking, this measurement entity measures the success rate of authentications
for all subscribers. The authentication success rate of VoLTE subscribers cannot be
Unit
Percentage (%)
Formula
where:
 A: 335672443 Number of S-CSCF Using AKA Authentication Attempts
 B: 335672444 Number of S-CSCF Successful Using AKA Authentication Attempts
NOTE:
Measurement Objects
S-CSCF
None
Related Notes

 Check whether the authentication response timer is set to a small value. If the timer
value is too small, set it to a proper value.
 Check whether subscriber creation data is correct. If subscriber creation data is incorrect,
configure it correctly.
9.1.2.1.12 Number of Registered VoWiFi

Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoWiFi subscribers registered with an IMS
network through a Wi-Fi network.
Unit
Integer
Formula
measurement entity:
NOTE:
When the ABCF is not the Huawei device, you can use the ATS's measurements to observe the number of
registered VoWiFi subscribers.
 ABCF measurement
 1907467809 Number of ABCF Registered VoWiFi Users
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Session Unrelated
Measurement, which belongs to the measurement set ABCF.
 ATS measurement
 478156717 Number of Successfully Registered Wi-Fi Subscribers
NOTE:
The preceding measurement entity is included in the measurement unit VoWiFi Basic Measurement,
which belongs to the measurement set ATS BASIC SERVICE.
Measurement Objects
ABCF/ATS
None
Related Notes
None
9.1.2.1.13 Number of Registered VoWiFi

Auxiliary Devices
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoWiFi secondary UEs registered with an
IMS network.
Unit
Integer
Formula
measurement entity:
 478156721 Number of Auxiliary Devices Registering over Wi-Fi
NOTE:
The preceding measurement entity is included in the measurement unit VoWiFi Basic Measurement, which
belongs to the measurement set ATS BASIC SERVICE.
Measurement Objects
ATS
None
Related Notes
None
9.1.2.1.14 VoWiFi Initial Registration

Success Rate
 Description
 Unit
 Formula
 Related Notes
Description
registration requests initiated by VoWiFi subscribers who access a Wi-Fi network in a
information about VoWiFi initial registrations.
When the ABCF receives a 200 message responded to an initial registration request
initiated by a UE, the initial registration is successful. The re-registration success rate is
excluded from this measurement entity.
Unit
Percentage (%)
Formula
where:
 A: 1907467810 Number of ABCF VoWiFi Initial Registration Attempts
 B: 1907467811 Number of ABCF VoWiFi Successful Initial Registrations
NOTE:
The preceding measurement entities are included in the measurement unit ABCF Session Unrelated
Measurement Objects
ABCF
None
Related Notes

 Check whether the packet loss rate of the Wi-Fi network and IP bearer network is too
9.1.2.1.15 VoWiFi Re-registration Success

Rate
 Description
 Unit
 Formula
 Related Notes
Description

requests initiated by VoWiFi subscribers who access an Wi-Fi network in a measurement
period. By analyzing the value of this measurement entity, you can obtain the information
about VoWiFi re-registrations.
registrations by sending REGISTER messages to keep the network connection alive. When
the ABCF receives a 200 message responded to a re-registration request initiated by a UE,
the re-registration is successful. The initial registration success rate is excluded from this
measurement entity.
Unit
Percentage (%)
Formula
where:
 A: 1907467813 Number of ABCF VoWiFi Re-registration Attempts
 B: 1907467814 Number of ABCF VoWiFi Successful Re-registrations
NOTE:
Measurement Objects
ABCF
None
Related Notes

 Check whether the packet loss rate of the Wi-Fi network and IP bearer network is too
< Previous topic
9.1.2.2 Session
Session Connection Delay
MO Session Connection Rate on an LTE Network
MT Session Connection Rate on an LTE Network
MO Session Answer Rate on an LTE Network
MT Session Answer Rate on an LTE Network
MO Session Connection Rate (Subscriber Cause)
MT Session Connection Rate (Subscriber Cause)
MO Short Message Success Rate
MT Short Message Success Rate
VoWiFi MO Session Connection Rate
VoWiFi MT Session Connection Rate
VoWiFi MO Session Answer Rate
VoWiFi MT Session Answer Rate
Parent Topic: Service Accessibility KPIs

< Previous topic
9.1.2.2.1 Session Connection Delay

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the duration from receiving an INVITE message from a
VoLTE subscriber to receiving a 180 or 200 message from the peer end. By analyzing the
value of this measurement entity, you can obtain VoLTE service accessibility, which is
important from user experience.
In VoLTE+VoWiFi networking, this measurement entity measures the session connection
delay for VoLTE and VoWiFi subscribers. The session connection delay for VoLTE
subscribers cannot be measured separately.
Unit
Seconds
Formula
Single-session connection delay

The connection delay of a single session is measured using the drive test and cannot be
measured on service NEs. In the message tracing result of the ABCF, the value of this
measurement entity is the duration from receiving an INVITE message to receiving a 180
or 200 message.
For example, an NE receives an INVITE message at T1 and receives a 180 or 200 message
at T2. The value of this measurement entity is calculated using the following formula:
Session Connection Delay = T2 – T1
Average session connection delay
Average MO session connection delay
measurement entity:
 1907466106 Mean Duration of ABCF MO Session
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Session Related Measurement,
which belongs to the measurement set ABCF.
Measurement Objects
ABCF
None
Related Notes

 Check whether network data is correct and complete. If network data is incorrect or
Parent Topic: Session
Next topic >
9.1.2.2.2 MO Session Connection Rate on

an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of 180 messages to INVITE messages sent
from the originating UE on an LTE network in a measurement period.
When the originating ABCF/P-CSCF receives a 180 or 200 message from the called party,
the session is connected.
In VoLTE+VoWiFi networking, this measurement entity measures the MO session
connection rate for VoLTE and VoWiFi subscribers. The MO session connection rate for
Unit
Percentage (%)
Formula
where:
 A: 1907466045 Number of ABCF MO Session Attempts
 B: 1907466046 Number of ABCF MO Connected Sessions
NOTE:
The preceding measurement entities are included in the measurement unit ABCF Session Related
Measurement Objects
ABCF
None
If the value of this measurement entity decreases, more calls fail.
Related Notes

 Check whether routing data on the network side is correct and complete. If routing data
on the network side is incorrect or incomplete, configure it correctly and completely.
 Check whether dedicated bearers are successfully allocated. If dedicated bearers fail to
be allocated, take measures to ensure that the LTE network meets service requirements.
 Check whether CS network resources are sufficient when calls are routed to a CS
network. If CS network resources are insufficient, take measures to ensure that CS
network resources are sufficient.
9.1.2.2.3 MT Session Connection Rate on

an LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of 180 messages received from the terminating
UE on an LTE network to INVITE messages sent by the terminating P-CSCF in a
measurement period.
When the terminating ABCF/P-CSCF receives a 180 or 200 message from the called party,
In VoLTE+VoWiFi networking, this measurement entity measures the MT session
connection rate for VoLTE and VoWiFi subscribers. The MT session connection rate for
Unit
Percentage (%)
Formula
where:
 A: 1907466048 Number of ABCF MT Session Attempts
 B: 1907466049 Number of ABCF MT Connected Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

9.1.2.2.4 MO Session Answer Rate on an

LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
from the originating UE on an LTE network in a measurement period.
When the originating ABCF/P-CSCF receives a 200 (to INVITE) message, the session is
answered.
In VoLTE+VoWiFi networking, this measurement entity measures the MO session answer
rate for VoLTE and VoWiFi subscribers. The MO session answer rate for VoLTE
Unit
Percentage (%)
Formula
where:
 B: 1907466047 Number of ABCF MO Answered Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

 Check whether the UE or network response timer is set to a proper value. If the response
timer is set to an improper value, set it to a proper value.
9.1.2.2.5 MT Session Answer Rate on an

LTE Network
 Description
 Unit
 Formula
 Related Notes
Description
UE on an LTE network to INVITE messages sent by the terminating P-CSCF in a
measurement period.
When the terminating ABCF/P-CSCF receives a 200 (to INVITE) message, the session is
answered.
In VoLTE+VoWiFi networking, this measurement entity measures the MT session answer
rate for VoLTE and VoWiFi subscribers. The MT session answer rate for VoLTE
Unit
Percentage (%)
Formula
where:
 A: 1907466048 Number of ABCF MT Session Attempts
 B: 1907466050 Number of ABCF MT Answered Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

9.1.2.2.6 MO Session Connection Rate

(Subscriber Cause)
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of MO session responses with subscriber
causes to session attempts in a measurement period. This measurement entity applies to
MO sessions of the original called party when the Communication Diversion (CDIV)
services, including the Call Forwarding Unconditional to Voice Mailbox (CFUVM)
service, are triggered.
In overlay networking, this measurement entity measures the MO session connection rate
for all subscribers. The MO session connection rate for VoLTE subscribers cannot be
Unit
Percentage (%)
Formula
where:
 E1: 335655576 Number of S-CSCF MO Session Attempts
 E2: 335655578 Number of S-CSCF Answered MO Sessions
 E3: 335664321 Number of S-CSCF MO Sessions Released Before Ringing
 E4: 335664324 Number of S-CSCF MO Sessions Released After Ringing
NOTE:
The preceding measurement entities are included in the measurement unit S-CSCF Session Related
 E5: 335675329 403 Forbidden

 E6: 335675330 404 Not Found
 E7: 335675334 408 Request Timeout
 E8: 335675347 480 Temporarily Unavailable
 E9: 335675351 484 Address Incomplete
 E10: 335675353 486 Busy Here
 E11: 335675354 487 Request Terminated
 E12: 335675372 600 Busy Everywhere
 E13: 335675373 603 Decline
 E14: 335675374 604 Does Not Exist Anywhere
NOTE:
The preceding measurement entities are included in the measurement unit S-CSCF MO Oxx Responses
Measurement Objects
S-CSCF
None
Related Notes

9.1.2.2.7 MT Session Connection Rate

(Subscriber Cause)
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of MT session responses with subscriber causes
to session attempts in a measurement period. This measurement entity applies when a
VoLTE subscriber roaming to a CS network is anchored in the IMS network and receives a
call.
In overlay networking, this measurement entity measures the MT session connection rate
for all subscribers. The MT session connection rate for VoLTE subscribers cannot be
Unit
Percentage (%)
Formula
where:
 E1: 335655581 Number of S-CSCF MT Session Attempts
 E2: 335655583 Number of S-CSCF Answered MT Sessions
 E3: 335664322 Number of S-CSCF MT Sessions Released Before Ringing
 E4: 335664325 Number of S-CSCF MT Sessions Released After Ringing
NOTE:
The preceding measurement entities are included in the measurement unit S-CSCF Session Related
 E5: 335677329 403 Forbidden

 E6: 335677330 404 Not Found
 E7: 335677334 408 Request Timeout
 E8: 335677347 480 Temporarily Unavailable
 E9: 335677351 484 Address Incomplete
 E10: 335677353 486 Busy Here
 E11: 335677354 487 Request Terminated
 E12: 335677372 600 Busy Everywhere
 E13: 335677373 603 Decline
 E14: 335677374 604 Does Not Exist Anywhere
NOTE:
The preceding measurement entities are included in the measurement unit S-CSCF MT Oxx Responses
Measurement Objects
S-CSCF
None
Related Notes

9.1.2.2.8 MO Short Message Success Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of

MAP_MO_FORWARD_SHORT_MESSAGE_ACK messages to
MAP_MO_FORWARD_SHORT_MESSAGE messages received by the IP-SM-GW in a
success rate of MO short messages sent by the IP-SM-GW in a measurement period.
In VoLTE+VoWiFi networking, this measurement entity measures the MO short message
success rate for VoLTE and VoWiFi subscribers. The MO short message success rate for
Unit
Percentage (%)
Formula
where:
 A: 478155820 MO Short Message Attempts
 B: 478155821 MO Short Message Success Times
NOTE:
The preceding measurement entities are included in the measurement unit IP-SM-GW Measurement, which
Measurement Objects
IP-SM-GW
None
If the value of this measurement entity decreases, more short messages fail.
Related Notes

 Check whether the IP-SM-GW interworks with the SMSC properly. If no, take measures
to ensure that data configuration is correct and network transmission is proper.
 Check whether the SMSC address carried by the UE is correct and in a valid format. If
the SMSC address is incorrect or in an invalid format, configure it correctly.
 Check whether there are a large number of short messages. If yes, ensure that network
resources are sufficient.
9.1.2.2.9 MT Short Message Success Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of 200 (to MESSAGE) messages to
MESSAGE messages received by the IP-SM-GW in a measurement period. By analyzing
the value of this measurement entity, you can obtain the success rate of MT short messages
sent by the IP-SM-GW in a measurement period.
In VoLTE+VoWiFi networking, this measurement entity measures the MT short message
success rate for VoLTE and VoWiFi subscribers. The MT short message success rate for
Unit
Percentage (%)
Formula
where:
 A: 478155823 MT Short Message Attempts
 B: 478155824 MT Short Message Success Times
NOTE:
The preceding measurement entities are included in the measurement unit IP-SM-GW Measurement, which
Measurement Objects
IP-SM-GW
None
If the value of this measurement entity decreases, more short messages fail.
Related Notes

 Check whether the IP-SM-GW interworks with the SMSC properly. If no, take measures
to ensure that data configuration is correct and network transmission is proper.
 Check whether there are a large number of short messages. If yes, ensure that network
resources are sufficient.
9.1.2.2.10 VoWiFi MO Session Connection

Rate
 Description
 Unit
 Formula
 Related Notes
Description
from the originating UE on an Wi-Fi network in a measurement period.
When the originating ABCF/P-CSCF receives a 180 or 200 message from the called party,
Unit
Percentage (%)
Formula
where:
 A: 1907468093 Number of ABCF MO-Side VoWiFi Session Attempts
 B: 1907468094 Number of ABCF MO-Side VoWiFi Connected Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

be allocated, take measures to ensure that the Wi-Fi network meets service requirements.
9.1.2.2.11 VoWiFi MT Session Connection

Rate
 Description
 Unit
 Formula
 Related Notes
Description
UE on an Wi-Fi network to INVITE messages sent by the terminating P-CSCF in a
measurement period.
When the terminating ABCF/P-CSCF receives a 180 or 200 message from the called party,
Unit
Percentage (%)
Formula
where:
 A: 1907468110 Number of ABCF MT-Side VoWiFi Session Attempts
 B: 1907468111 Number of ABCF MT-Side VoWiFi Connected Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

9.1.2.2.12 VoWiFi MO Session Answer

Rate
 Description
 Unit
 Formula
 Related Notes
Description
from the originating UE on an Wi-Fi network in a measurement period.
When the originating ABCF/P-CSCF receives a 200 (to INVITE) message, the session is
answered.
Unit
Percentage (%)
Formula
where:
 A: 1907468093 Number of ABCF MO-Side VoWiFi Session Attempts
 B: 1907468095 Number of ABCF MO-Side VoWiFi Answered Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

9.1.2.2.13 VoWiFi MT Session Answer

Rate
 Description
 Unit
 Formula
 Related Notes
Description
UE on an Wi-Fi network to INVITE messages sent by the terminating P-CSCF in a
measurement period.
When the terminating ABCF/P-CSCF receives a 200 (to INVITE) message, the session is
answered.
Unit
Percentage (%)
Formula
where:
 A: 1907468110 Number of ABCF MT-Side VoWiFi Session Attempts
 B: 1907468112 Number of ABCF MT-Side VoWiFi Answered Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes

< Previous topic
9.1.3 Service Retainability KPI

Handover
Call Drop Rate
Parent Topic: KPI

9.1.3.1 Handover
Success Rate of LTE-to-GSM eSRVCC Handovers
Success Rate of LTE-to-UMTS eSRVCC Handovers
Interruption Duration During an eSRVCC Handover
Number of Handovers from Wi-Fi to LTE
Number of Handovers from LTE to Wi-Fi
Parent Topic: Service Retainability KPI

Next topic >
9.1.3.1.1 Success Rate of LTE-to-GSM

eSRVCC Handovers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the success rate of LTE-to-GSM eSRVCC handovers
during VoLTE calls in a measurement period.
When the SRVCC IWF sends an SRVCC PS to CS Complete Notify message to the MME,
an eSRVCC handover is successful. For calculation of eSRVCC handovers, canceled
handover requests are not counted as call attempts.
Unit
Percentage (%)
Formula
where:
 E1: 84175689 Number of 2G eSRVCC Service Alerting Request
 E2: 84176698 Number of Successful Times During 2G eSRVCC Handovers
 E3: 84176435 Number of 2G eSRVCC Service Pre-Alerting Request Times
 E4: 84164965 Number of Requested 2G Intra-MSC eSRVCC Handovers
 E5: 84164967 Number of Requested 2G Inter-MSC eSRVCC Handovers
NOTE:
 The preceding measurement entities are included in the measurement unit 2G eSRVCC Service
Measurement, which belongs to the measurement set MSC Basic Services.
 The entity 84176435 Number of 2G eSRVCC Service Pre-Alerting Request Times does not need to be
counted in 84176698 Number of Successful Times During 2G eSRVCC Handovers for the given formula.
Set bit 6 of P1053 to 1 in this case.
Measurement Objects
SRVCC IWF
None
If the value of this measurement entity decreases, more handovers fail and the call drop rate
increases.
Related Notes
If this measurement entity is abnormal, perform the following operations to identify the
fault:
 Check whether the SRVCC IWF interworks with the VMSC properly. If the SRVCC
IWF fails to interwork with the VMSC, check handover data and ensure that the
configuration is correct.
 Check whether GSM radio resources on the target side are successfully established. If
the radio resources fail, take measures to ensure that access to the target GSM network is
normal.
 Check whether DNS data is correct and complete. If eSRVCC-related DNS data is
incorrect or incomplete, configure it correctly.
Parent Topic: Handover
Next topic >
9.1.3.1.2 Success Rate of LTE-to-UMTS

eSRVCC Handovers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the success rate of LTE-to-UMTS eSRVCC handovers
during VoLTE calls in a measurement period.
When the SRVCC IWF sends an SRVCC PS to CS Complete Notify message to the MME,
an eSRVCC handover is successful. For calculation of eSRVCC handovers, canceled
handover requests are not counted as call attempts.
Unit
Percentage (%)
Formula
where:
 E1: 84175691 Number of 3G eSRVCC Service Alerting Request
 E2: 84176700 Number of Successful Times During 3G eSRVCC Handovers
 E3: 84176438 Number of 3G eSRVCC Service Pre-Alerting Request Times
 E4: 84164975 Number of Requested 3G Intra-MSC eSRVCC Handovers
 E5: 84164977 Number of Requested 3G Inter-MSC eSRVCC Handovers
NOTE:
 The preceding measurement entities are included in the measurement unit 3G eSRVCC Service
Measurement, which belongs to the measurement set MSC Basic Services.
 The entity 84176438 Number of 3G eSRVCC Service Pre-Alerting Request Times does not need to be
counted in 84176700 Number of Successful Times During 3G eSRVCC Handovers for the given formula.
Set bit 6 of P1053 to 1 in this case.
Measurement Objects
SRVCC IWF
None
If the value of this measurement entity decreases, more handovers fail and the call drop rate
increases.
Related Notes
If this measurement entity is abnormal, perform the following operations to identify the
fault:
 Check whether the SRVCC IWF interworks with the VMSC properly. If the SRVCC
IWF fails to interwork with the VMSC, check handover data and ensure that the
configuration is correct.
 Check whether UMTS radio resources on the target side are successfully established. If
the radio resources fail, take measures to ensure that access to the target UMTS network
is normal.
 Check whether DNS data is correct and complete. If eSRVCC-related DNS data is
incorrect or incomplete, configure it correctly.
9.1.3.1.3 Interruption Duration During an

eSRVCC Handover
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the duration for interrupting voice services during an
eSRVCC handover.
Unit
Millisecond
Formula
This measurement entity is measured using the drive test and cannot be measured on
service NEs. You can create a message tracing task on the SRVCC IWF during eSRVCC
handovers to calculate the value of this measurement entity.
During an E2E eSRVCC handover, handover preparation requires a short period of time.
The value of this measurement entity is the difference between the time when the SRVCC
IWF receives a MOD REPLY message and the time when the SRVCC IWF sends a PS to
CS Response message, as shown in Figure 1.
Figure 1 Message flow of an eSRVCC handover
where:
 T1: The SRVCC IWF sends a PS to CS Response message to the MME.
 T2: The SRVCC IWF receives a MOD REPLY message from the MGW.
Measurement Objects
None
None
Related Notes

 Check whether network data is correct and complete. If network data is incorrect or
 Check whether the packet loss rate is too high. If the packet loss rate is too high, take
measures to ensure that the packet loss rate does not exceed the maximum allowed
value.
 Check radio network performance is good. If radio network performance is poor,
optimize the radio network.
9.1.3.1.4 Number of Handovers from Wi-Fi

to LTE
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the number of handovers from Wi-Fi networks to LTE
networks during VoWiFi calls in a measurement period.
Unit
Integer
Formula
measurement entity:
 478156718 Number of Switches from Wi-Fi to LTE
NOTE:
Measurement Objects
ATS
None
Related Notes
None
9.1.3.1.5 Number of Handovers from LTE

to Wi-Fi
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the number of handovers from LTE networks to Wi-Fi
networks during VoWiFi calls in a measurement period.
Unit
Integer
Formula
measurement entity:
 478156719 Number of Switches from LTE to Wi-Fi
NOTE:
Measurement Objects
ATS
None
Related Notes
None
< Previous topic
9.1.3.2 Call Drop Rate

VoLTE Call Drop Rate
Rate of Abnormally Released Bearers on the eNodeB
VoWiFi Call Drop Rate
Parent Topic: Service Retainability KPI

< Previous topic
9.1.3.2.1 VoLTE Call Drop Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of session interruptions due to abnormal
reasons to answered sessions in a measurement period. By analyzing the value of this
measurement entity, you can obtain VoLTE network retainability.
In VoLTE+VoWiFi networking, this measurement entity measures the call drop rate for
VoLTE and VoWiFi subscribers. The call drop rate for VoLTE subscribers cannot be
Unit
Percentage (%)
Formula
where:
 E1: 1907466047 Number of ABCF MO Answered Sessions
 E2: 1907466050 Number of ABCF MT Answered Sessions
 E3: 1907466118 Number of ABCF MO Session Interruptions
 E4: 1907466119 Number of ABCF MT Session Interruptions
NOTE:
 E5: 1907467000 Number of Session Interruptions Triggered by Wireless Network on MO-Side A-BCF
NOTE:
The preceding measurement entity is included in the measurement unit ABCF MO Access Type
 E6: 1907467001 Number of Session Interruptions Triggered by Wireless Network on MT-Side A-BCF
NOTE:
The preceding measurement entity is included in the measurement unit ABCF MT Access Type
Measurement Objects
ABCF
None
If the value of this measurement entity increases, more calls are interrupted.
Related Notes

 Check whether radio network performance is good. If radio network performance is
poor, optimize the radio network.
 Check whether the eSRVCC success rate and ensure it is within the specified range.
value.
Parent Topic: Call Drop Rate
Next topic >
9.1.3.2.2 Rate of Abnormally Released

Bearers on the eNodeB
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of abnormally released bearers to bearer setup
attempts on the eNodeB in a measurement period. By analyzing the value of this
measurement entity, you can obtain the radio-side causes of VoLTE call drop rate.
Bearers with QCIs of 1 and 2 are dedicated for VoLTE voice and video services.
Unit
Percentage (%)
Formula
where:
 E1: Number of abnormal releases of activated E-RABs for services with the QCI of 1 in
a cell, indicating the number of abnormal releases of dedicated bearers (QCI=1) used for
VoLTE voice services on the eNodeB
 E2: Number of abnormal releases of activated E-RABs for services with the QCI of 2 in
a cell, indicating the number of abnormal releases of dedicated bearers (QCI=2) used for
VoLTE video services on the eNodeB
NOTE:
The preceding measurement entities are included in the measurement unit Measurement related to E-RAB
release, which belongs to the measurement set Measurement of Cell performance (Cell).
 E3: Number of E-RAB setup attempts initiated by UEs for services with the QCI of 1 in
a cell, indicating the number of attempts to set up dedicated bearers (QCI=1) used for
VoLTE voice services on the eNodeB
 E3: Number of E-RAB setup attempts initiated by UEs for services with the QCI of 2 in
a cell, indicating the number of attempts to set up dedicated bearers (QCI=2) used for
VoLTE video services on the eNodeB
NOTE:
The preceding measurement entities are included in the measurement unit Measurement related to E-RAB
establish, which belongs to the measurement set Measurement of Cell performance (Cell).
Measurement Objects
eNodeB cell
None
If the value of this measurement entity increases, the LTE radio network performance
becomes poor.
Related Notes

 Check whether the eSRVCC function is enabled. If the eSRVCC function has not been
enabled, configure it on the network side.
9.1.3.2.3 VoWiFi Call Drop Rate

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the ratio of session interruptions due to abnormal
reasons to answered sessions in a measurement period. By analyzing the value of this
measurement entity, you can obtain VoWiFi network retainability.
Unit
Percentage (%)
Formula
where:
 E1: 1907467816 Number of ABCF MO-Side VoWiFi Session Interruptions
 E2: 1907467817 Number of ABCF MT-Side VoWiFi Session Interruptions
 E3: 1907467819 Number of ABCF MO-Side VoWiFi Session Interruptions Triggered by Wireless Network
 E4: 1907467820 Number of ABCF MT-Side VoWiFi Session Interruptions Triggered by Wireless Network
 E5: 1907468095 Number of ABCF MO-Side VoWiFi Answered Sessions
 E6: 1907468112 Number of ABCF MT-Side VoWiFi Answered Sessions
NOTE:
Measurement Objects
ABCF
None
If the value of this measurement entity increases, more calls are interrupted.
Related Notes

 Check whether the Wi-Fi network performance is good. If the Wi-Fi network
performance is poor, optimize the Wi-Fi network.
value.
< Previous topic
9.1.4 Service Integrity KPIs

Voice Quality
Parent Topic: KPI

9.1.4.1 Voice Quality

Voice Quality of Voice Calls
Voice Quality of Video Calls
Voice Quality of VoWiFi Voice Calls
IP QoS Lost Rate of VoWiFi Access Network
Parent Topic: Service Integrity KPIs

9.1.4.1.1 Voice Quality of Voice Calls

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the voice quality of E2E VoLTE voice calls.
In VoLTE+VoWiFi networking, this measurement entity measures the voice quality for
VoLTE and VoWiFi calls. The voice quality for VoLTE calls cannot be measured
separately.
Unit
None
Formula
Drive test
In most cases, subjective assessment is used to determine the fidelity and intelligibility of
voice packages after transmission on networks.
The voice quality of voice calls is measured using mean opinion score (MOS). Voice
signals passing through the test system are scored, and mapping between scores and voice
quality is as follows: 5-excellent, 4-good, 3-average, 2-relatively poor, 1-poor. The average
of all scores is used as the MOS.
where:
 Xn indicates the sum of all scores.
 n indicates the number of test users. To ensure that the result is trusted, a minimum of
16 test users participate in the test in a quite environment.
NE-specific measurement
measurement entity:
 1907466568 ABCF Access Network IP QoS Mos Average
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Access Network IP QoS
Measurement, which belongs to the measurement set IP QoS.
Measurement Objects
ABCF
None
If the value of this measurement entity decreases, the voice quality becomes poor.
Related Notes

 Check whether the packet loss rate or jitter is too high. If the packet loss rate or jitter is
too high, take measures to ensure that the packet loss rate and jitter do not exceed the
maximum allowed values.
 Check whether codecs change during calls. If codecs change during calls, check codec
configuration.
Parent Topic: Voice Quality
Next topic >
9.1.4.1.2 Voice Quality of Video Calls

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the voice quality of E2E VoLTE video calls.
In VoLTE+VoWiFi networking, this measurement entity measures the voice quality for
VoLTE and VoWiFi calls. The voice quality for VoLTE calls cannot be measured
separately.
Unit
None
Formula
The voice quality of video calls is measured using mean opinion score (MOS). Voice
where:
measurement entity:
 1907466568 ABCF Access Network IP QoS Mos Average
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Access Network IP QoS
Measurement, which belongs to the measurement set IP QoS.
Measurement Objects
ABCF
None
Related Notes

configuration.
9.1.4.1.3 Voice Quality of VoWiFi Voice

Calls
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the voice quality of E2E VoWiFi voice calls.
Unit
None
Formula
Drive test
The voice quality of voice calls is measured using mean opinion score (MOS). Voice
where:
measurement entity:
 1907468153 ABCF VoWiFi Access Network IP QoS Mos Average
NOTE:
The preceding measurement entity is included in the measurement unit ABCF VoWiFi Access Network IP
QoS Measurement, which belongs to the measurement set IP QoS.
Measurement Objects
ABCF
None
Related Notes

 Check whether the Wi-Fi network performance is good. If the Wi-Fi network
performance is poor, optimize the Wi-Fi network.
configuration.
9.1.4.1.4 IP QoS Lost Rate of VoWiFi

Access Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the packet loss rate of IP bearer network between the
SE2900 and UEs during VoWiFi calls in a measurement period.
Unit
Percentage (%)
Formula
measurement entity:
 1907468135 ABCF VoWiFi Access Network IP QoS LosRate Average
NOTE:
The preceding measurement entity is included in the measurement unit ABCF VoWiFi Access Network IP
QoS Measurement, which belongs to the measurement set IP QoS.
Measurement Objects
ABCF
None
If the value of this measurement entity increases, the IP bearer network quality becomes
poor.
Related Notes
None
< Previous topic
9.1.5 Traffic Model KPIs

Traffic
Average Session Duration
Service Times
Traffic Model Per Subscriber
Parent Topic: KPI

9.1.5.1 Traffic
Traffic of Answered VoLTE Sessions
Traffic of Answered VoWiFi Sessions
Parent Topic: Traffic Model KPIs

Next topic >
9.1.5.1.1 Traffic of Answered VoLTE

Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the traffic of MO and MT answered sessions initiated
through an LTE network in a measurement period.
In VoLTE+VoWiFi networking, this measurement entity measures the traffic of answered
sessions for VoLTE and VoWiFi subscribers. The traffic of answered sessions for VoLTE
Unit
Erlang
Formula
where:
 A: 1907466085 Traffic of ABCF MO Answered Sessions
 B: 1907466086 Traffic of ABCF MT Answered Sessions
NOTE:
Measurement Objects
ABCF
None
If the value of this measurement entity increases, more subscribers use call services.
Related Notes
None
Parent Topic: Traffic
Next topic >
9.1.5.1.2 Traffic of Answered VoWiFi

Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the traffic of MO and MT answered sessions initiated
through an Wi-Fi network in a measurement period.
Unit
Erlang
Formula
where:
 A: 1907468105 Traffic of ABCF MO-Side VoWiFi Answered Sessions
 B: 1907468122 Traffic of ABCF MT-Side VoWiFi Answered Sessions
NOTE:
Measurement Objects
ABCF
None
If the value of this measurement entity increases, more subscribers use call services.
Related Notes
None
Parent Topic: Traffic
< Previous topic
9.1.5.2 Average Session Duration

Average VoLTE Session Duration
Average VoWiFi Session Duration

9.1.5.2.1 Average VoLTE Session Duration

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average duration of sessions initiated or received
through an LTE network in a measurement period.
The session duration is the difference between the time when the ABCF receives a 2xx (to
BYE) message and the time when the ABCF receives a 2xx (to INVITE) message.
In VoLTE+VoWiFi networking, this measurement entity measures the average session
duration for VoLTE and VoWiFi subscribers. The average session duration for VoLTE
Unit
Seconds
Formula
measurement entity:
 1907466105 Mean Duration from Answering to Release of ABCF Sessions
NOTE:
The preceding measurement entity is included in the measurement unit ABCF Session Related Measurement,
which belongs to the measurement set ABCF.
Measurement Objects
ABCF
None
Related Notes
None
Parent Topic: Average Session Duration
Next topic >
9.1.5.2.2 Average VoWiFi Session Duration

 Description
 Unit
 Formula

 Related Notes
Description
This measurement entity measures the average duration of sessions initiated through an Wi-
Fi network in a measurement period.
The session duration is the difference between the time when the ABCF receives a 2xx (to
BYE) message and the time when the ABCF receives a 2xx (to INVITE) message.
Unit
Seconds
Formula
where:
 A: 1907468095 Number of ABCF MO-Side VoWiFi Answered Sessions
 B: 1907468105 Traffic of ABCF MO-Side VoWiFi Answered Sessions
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
Parent Topic: Average Session Duration
< Previous topic
9.1.5.3 Service Times

VoLTE Subscriber BHCA
Number of Initial Registrations
Number of Re-registrations
9.1.5.3.1 VoLTE Subscriber BHCA

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of call attempts initiated on an IMS network by
VoLTE subscribers through an LTE network in a measurement period. By analyzing the
value of this measurement entity, you can obtain VoLTE service busy status.
In VoLTE+VoWiFi networking, this measurement entity counts the call attempts for
VoLTE and VoWiFi subscribers. The number of call attempts for VoLTE subscribers
cannot be counted separately.
Unit
Integer
Formula
where:
 B: 1907466048 Number of ABCF MT Session Attempts
NOTE:
Measurement Objects
ABCF

None
If the value of this measurement entity increases, more subscribers initiate service requests.
Related Notes
None
Parent Topic: Service Times
Next topic >
9.1.5.3.2 Number of Initial Registrations

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of initial registration requests received by the
S-CSCF from UEs in a measurement period. By analyzing the value of this measurement
entity, you can obtain the information about VoLTE subscribers requesting services.
In overlay networking, this measurement entity counts the number of initial registration
requests initiated by all subscribers. The number of initial registration requests initiated by
VoLTE subscribers cannot be counted separately.
Unit
Integer
Formula
measurement entity:
 335655491 Number of S-CSCF Initial Registration Attempts
NOTE:
Measurement Objects
S-CSCF
None
Related Notes
None
9.1.5.3.3 Number of Re-registrations

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of re-registration requests received by the S-
CSCF from UEs in a measurement period. By analyzing the value of this measurement
entity, you can obtain the information about VoLTE subscribers retaining the active state.
In overlay networking, this measurement entity counts the number of re-registration
requests initiated by all subscribers. The number of re-registration requests initiated by
VoLTE subscribers cannot be counted separately.
Unit
Integer
Formula
measurement entity:
 335655519 Number of S-CSCF Re-registration Attempts
NOTE:
Measurement Objects
S-CSCF
None
Related Notes
None
< Previous topic
9.1.5.4 Traffic Model Per Subscriber

Average Traffic of Answered Sessions Per Subscriber
Average BHCA Per Subscriber
BHCA of VoWiFi Session Per Subscriber
BHCA of VoWiFi Initial Registration Per Subscriber
BHCA of VoWiFi Re-Registration Per Subscriber

< Previous topic
9.1.5.4.1 Average Traffic of Answered

Sessions Per Subscriber
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average traffic of answered sessions per subscriber
who accesses an LTE network in a measurement period.
In VoLTE+VoWiFi networking, this measurement entity measures the average traffic of
answered sessions for VoLTE and VoWiFi subscribers. The average traffic of answered
sessions for VoLTE subscribers cannot be measured separately.
Unit
Erlang
Formula
where:
 A: 1907466085 Traffic of ABCF MO Answered Sessions
 B: 1907466086 Traffic of ABCF MT Answered Sessions
NOTE:
 C: 1907465358 Number of Users in The Access Network
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
Parent Topic: Traffic Model Per Subscriber
Next topic >
9.1.5.4.2 Average BHCA Per Subscriber

 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average BHCA per subscriber who accesses an LTE
network in a measurement period. By analyzing the value of this measurement entity, you
can obtain the information about service busy status on a VoLTE network.
In VoLTE+VoWiFi networking, this measurement entity measures the average BHCA for
VoLTE and VoWiFi subscribers. The average BHCA for VoLTE subscribers cannot be
Unit
Integer
Formula
where:
 B: 1907466048 Number of ABCF MT Session Attempts
NOTE:
 C: 1907465358 Number of Users in The Access Network
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
9.1.5.4.3 BHCA of VoWiFi Session Per

Subscriber
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average MO and MT session times of each VoWiFi
subscriber in a measurement period, indicating the service busy status.
Unit
Integer
Formula
where:
 A: 1907467809 Number of ABCF Registered VoWiFi Users
NOTE:
 B: 1907468093 Number of ABCF MO-Side VoWiFi Session Attempts

 C: 1907468110 Number of ABCF MT-Side VoWiFi Session Attempts
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
9.1.5.4.4 BHCA of VoWiFi Initial

Registration Per Subscriber
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average initial registration times of each VoWiFi
subscriber in a measurement period, indicating the frequency of accessing to the IMS
network.
Unit
Integer
Formula
where:
 B: 1907467810 Number of ABCF VoWiFi Initial Registration Attempts
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
9.1.5.4.5 BHCA of VoWiFi Re-Registration

Per Subscriber
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average re-registration times of each VoWiFi
subscriber in a measurement period.
Unit
Integer
Formula
where:
 B: 1907467813 Number of ABCF VoWiFi Re-registration Attempts
NOTE:
Measurement Objects
ABCF
None
Related Notes
None
< Previous topic
9.1.6 References of Related NE Counters

CSC3300
ATS9900
HSS9860
SE2900
MSOFTX3000
Parent Topic: KPI

< Previous topic
9.1.6.1 CSC3300
335555337 S-CSCF MO Oxx Responses Measurement
335555339 S-CSCF MT Oxx Responses Measurement
335655491 Number of S-CSCF Initial Registration Attempts
335655492 Number of S-CSCF Successful Initial Registrations
335655519 Number of S-CSCF Re-registration Attempts
335655520 Number of S-CSCF Successful Re-registrations
335655576 Number of S-CSCF MO Session Attempts
335655578 Number of S-CSCF Answered MO Sessions
335655581 Number of S-CSCF MT Session Attempts
335655583 Number of S-CSCF Answered MT Sessions
335664321 Number of S-CSCF MO Sessions Released Before Ringing
335664322 Number of S-CSCF MT Sessions Released Before Ringing
335664324 Number of S-CSCF MO Sessions Released After Ringing
335664325 Number of S-CSCF MT Sessions Released After Ringing
335672421 Number of S-CSCF Registered Users
335672443 Number of S-CSCF Using AKA Authentication Attempts
335672444 Number of S-CSCF Successful Using AKA Authentication Attempts
Parent Topic: References of Related NE Counters

Next topic >
9.1.6.1.1 335555337 S-CSCF MO Oxx

Responses Measurement
 Description
 Application Scenario
 Unit
 Measurement Point
 Formula
 Related Notes
Description
This measurement entity counts the number of SIP response codes for each SCU module
generated or transited by the originating S-CSCF in a measurement period. The SIP
response codes range from 300 to 699, including 603 and 486.
Application Scenario
Create a measurement task with this measurement entity when you need to obtain the
number of times the originating S-CSCF generates or transmits an Oxx response code.
Table 1 Information about response codes and application scenario analysis
ID on the Response Description Application Scenario Analysis

EMS Code

EMS Code
335675320 300 Multiple Choices The address in the request resolved to several choices,
each with its own specific location, and the user (or
UA) can select a preferred communication end point
and redirect its request to that location. This status
response is appropriate if the callee can be reached at
several different locations and the server cannot or
prefers not to proxy the request.
335675321 301 Moved This response can be used to send the new address to
Permanently the requester when the user cannot be found by using
the address specified in the Request-URI. The new
address is provided in the Contact header. The
requester uses the new address to send requests and
updates the local directory, address book, and user
address cache. Moreover, subsequent requests are
sent to the new address.
335675322 302 Moved This response is similar to response 301. However,

Temporarily the duration of the validity of the Contact URI can be
indicated through an Expires header field or an
expired parameter in the Contact header field. Both
proxies and UAs MAY cache this URI for the
duration of the expiration time. If there is no explicit
expiration time, the address is only valid once for
recursing, and MUST NOT be cached for future
transactions.
335675323 305 Use Proxy 305 (Use Proxy) responses MUST only be generated
by UASs. The requested resource MUST be accessed
through the proxy given by the Contact field. The
Contact field gives the URI of the proxy. The
recipient is expected to repeat this single request via
the proxy.
335675324 380 Alternative When the call is not successful, but alternative
Service services are possible, the response can be sent to the
caller. The alternative services are described in the
message body of the response.
335675325 Other 3xx response These response codes are sent in redirection scenarios
3xx codes except for except for the previously mentioned redirection
the previously scenarios.
listed 3xx
response codes

EMS Code
335675326 400 Bad Request When the request could not be understood due to
malformed syntax, the response is used to reject the
request from the caller. The Reason-Phrase SHOULD
identify the syntax problem in more detail, for
example, "Missing Call-ID header field".
335675327 401 Unauthorized When request requires user authentication, the

response is issued by UASs and registrars.
335675329 403 Forbidden The server understands the request but refuses to
fulfill it. The server sends the 403 response to
requests such as undefined user initiated register
requests, undefined user initiated de-registration
requests, and user authentication failure or requests
from an untrusted domain.
335675330 404 Not Found The server has definitive information that the user
does not exist at the domain specified in the Request-
URI. This status is also returned if the domain in the
Request-URI does not match any of the domains
handled by the recipient of the request.
335675331 405 Method Not The method specified in the Request-Line is

Allowed understood, but not allowed for the address identified
by the Request-URI. The response MUST include an
Allow header field containing a list of valid methods
for the indicated address.
335675332 406 Not Acceptable The resource identified by the request is only capable
of generating response entities that have content
characteristics not acceptable according to the Accept
header field sent in the request.
335675334 408 Request Timeout The server could not produce a response within a
suitable amount of time.
335675335 410 Gone The requested resource is no longer available at the

server and no forwarding address is known.
335675336 412 Precondition If there is no matching event state at the ESC, for
Failed example, the event state to be modified has already
expired, the EPA receives a 412 response to the
PUBLISH request.

EMS Code
335675337 413 Request Entity The server is refusing to process a request because the
Too Large request entity-body is larger than the server is willing
or able to process.
335675338 414 Request-URI Too The server is refusing to service the request because
Large the Request-URI is larger than the server is willing to
interpret.
335675339 415 Unsupported The server is refusing to service the request because
Media Type the message body of the request is in a format not
supported by the server for the requested method. The
server MUST return a list of acceptable formats using
the Accept, Accept-Encoding, or Accept-Language
header field, depending on the specific problem with
the content.
335675340 416 Unsupported URI The server cannot process the request because the
Scheme scheme of the URI in the Request-URI is unknown to
the server.
335675341 420 Bad Extension The server did not understand the protocol extension
specified in a Proxy-Require or Require header field.
335675342 421 Extension The UAS needs a particular extension to process the
Required request, but this extension is not listed in a Supported
header field in the request. Responses with this status
code MUST contain a Require header field listing the
required extensions.
335675343 422 Session Expires The server performs a SessionTimer check for the
Too Small message. If the UAC supports SessionTimer but the
Session Expires parameter in the message is smaller
than the value configured on the local server, the
server returns a 422 response.
335675344 423 Interval Too The server is rejecting the request because the
Brief expiration time of the resource refreshed by the
request is too short.
335675345 429 Provide Referrer if the refer target requires a valid Referred-By token
Identity to accept the request. This can occur when either no
token is provided or a provided token is invalid.
335675346 433 Anonymity When the From header in the request is anonymous

EMS Code
Disallowed but the network does not allow an anonymous value,

the server returns a 433 response.
335675347 480 Temporarily The callee's end system was contacted successfully
Unavailable but the callee is currently unavailable.
335675348 481 Call This status indicates that the UAS received a request
Leg/Transaction that does not match any existing dialog or transaction.
Does Not Exist
335675349 482 Loop Detected The server has detected a loop.
335675350 483 Too Many Hops The server received a request that contains a Max-
Forwards header field with the value zero.
335675351 484 Address The server received a request with a Request-URI that
Incomplete was incomplete.
335675352 485 Ambiguous The Request-URI was ambiguous. In such a case,

several records match the Request-URI.
335675353 486 Busy Here The callee's end system was contacted successfully,
but the callee is currently not willing or able to take
additional calls at this end system. The user could
also be available elsewhere, such as through a voice
mail service.
335675354 487 Request The request was terminated by a BYE or CANCEL

Terminated request.
335675355 488 Not Acceptable The media resource carried in the request is
Here unacceptable. The reasons may be the following:
 The caller carries an unsubscribed media resource.
 The local policy does not allow the media
resource.
335675356 489 Bad Event Checking the Event header in the subscription
message fails. The reasons may be the following: The
Subscribe and Notify requests must carry the Event
header. The server returns a 489 response if the
header is not available or the Event header is not the
supported type.
335675357 491 Request Pending The request was received by a UAS that had a

EMS Code
pending request within the same dialog.
335675359 493 Undecipherable The request was received by a UAS that contained an
encrypted MIME body for which the recipient does
not possess or will not provide an appropriate
decryption key.
335675360 494 Security An unprotected request that contains a Require or

Agreement Proxy-Require header field with the value "sec-
Required agree".
335675361 Other 4xx response These response codes are sent in client error scenarios
4xx codes except for except for the previously mentioned client error
listed 4xx
response codes
335675362 500 Server Internal The server encountered an unexpected condition that
Error prevented it from fulfilling the request. Usually, this
error is an internal error.
335675363 501 Not Implemented The server does not support the functionality required
to fulfill the request.
335675364 502 Bad Gateway The server, while acting as a gateway or proxy,
received an invalid response from the downstream
server it accessed in attempting to fulfill the request.
335675365 503 Service The server is temporarily unable to process the

Unavailable request due to a temporary overloading or
maintenance of the server.
335675366 504 Server Time-out The server did not receive a timely response from an
external server it accessed in attempting to process
the request.
335675367 505 SIP Version not The server does not support, or refuses to support, the
supported SIP protocol version that was used in the request.
335675368 513 Message Too The server was unable to process the request since the
Large message length exceeded its capabilities.
335675369 533 Service Lost If the user data cannot be found in the local database
and the redundancy policy configuration is set to 533,

EMS Code
335675370 580 Precondition When a UAS, acting as an answerer, cannot or is not

Failure willing to meet the preconditions in the offer, it
rejects the offer by returning a 580 response.
335675371 Other 5xx response These response codes are sent in server error
5xx codes except for scenarios except for the previously mentioned server
the previously error scenarios.
listed 5xx
response codes
335675372 600 Busy Everywhere The callee's end system was contacted successfully
but the callee is busy and does not wish to take the
call at this time. This status response is returned only
if the client knows that no other end point (such as a
voice mail system) will answer the request.
335675373 603 Decline The callee's machine was successfully contacted but
the user explicitly does not wish to or cannot
participate.
335675374 604 Does Not Exist The server has authoritative information that the user
Anywhere indicated in the Request-URI does not exist
anywhere.
335675375 606 Not Acceptable The user's agent was contacted successfully but some
aspects of the session description such as the
requested media, bandwidth, or addressing style were
not acceptable.
335675376 Other 6xx response These response codes are sent in global failure
6xx codes except for scenarios except for the previously mentioned global
the previously failure scenarios.
listed 6xx
response codes
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the MO S-CSCF generates or
transits an Oxx response to the INVITE message. For details, see point A in Figure 1.
Figure 1 Measurement point of S-CSCF MO Oxx Responses Measurement
Formula
None
Related Notes
Carriers can use this measurement entity on the network management system to calculate
the ratio that the originating S-CSCF generates or transits Oxx responses. Refer to the S-
CSCF Session Completion Rate measurement entity.
Parent Topic: CSC3300

Next topic >
9.1.6.1.2 335555339 S-CSCF MT Oxx

Responses Measurement
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of SIP response codes for each SCU module
generated or transited by the terminating S-CSCF in a measurement period. The SIP
response codes range from 300 to 699, including 603 and 486.
Create a measurement task with this measurement entity when you need to obtain the
number of times the terminating S-CSCF generates or transits an Oxx response code.

EMS Code
335677320 300 Multiple Choices The address in the request resolved to several choices,
each with its own specific location, and the user (or
UA) can select a preferred communication end point
and redirect its request to that location. This status
response is appropriate if the callee can be reached at
several different locations and the server cannot or
prefers not to proxy the request.
335677321 301 Moved This response can be used to send the new address to
Permanently the requester when the user cannot be found by using
the address specified in the Request-URI. The new
address is provided in the Contact header. The
requester uses the new address to send requests and
updates the local directory, address book, and user
address cache. Moreover, subsequent requests are sent
to the new address.
335677322 302 Moved This response is similar to response 301. However, the
Temporarily duration of the validity of the Contact URI can be
indicated through an Expires header field or an expired
parameter in the Contact header field. Both proxies
and UAs MAY cache this URI for the duration of the
expiration time. If there is no explicit expiration time,
the address is only valid once for recursing, and

EMS Code
MUST NOT be cached for future transactions.
335677323 305 Use Proxy 305 (Use Proxy) responses MUST only be generated
by UASs. The requested resource MUST be accessed
through the proxy given by the Contact field. The
Contact field gives the URI of the proxy. The recipient
is expected to repeat this single request via the proxy.
335677324 380 Alternative When the call is not successful, but alternative services
Service are possible, the response can be sent to the caller. The
alternative services are described in the message body
of the response.
335677325 Other 3xx response These response codes are sent in redirection scenarios
3xx codes except for except for the previously mentioned redirection
listed 3xx
response codes
335677326 400 Bad Request When the request could not be understood due to
malformed syntax, the response is used to reject the
request from the caller. The Reason-Phrase SHOULD
identify the syntax problem in more detail, for
example, "Missing Call-ID header field".
335677327 401 Unauthorized When request requires user authentication, the

response is issued by UASs and registrars.
335677329 403 Forbidden The server understands the request but refuses to fulfill
it. The server sends the 403 response to requests such
as undefined user initiated register requests, undefined
user initiated de-registration requests, and user
authentication failure or requests from an untrust
domain.
335677330 404 Not Found The server has definitive information that the user does
not exist at the domain specified in the Request-URI.
This status is also returned if the domain in the
Request-URI does not match any of the domains
handled by the recipient of the request.
335677331 405 Method Not The method specified in the Request-Line is

Allowed understood, but not allowed for the address identified
by the Request-URI. The response MUST include an
Allow header field containing a list of valid methods

EMS Code
for the indicated address.
335677332 406 Not Acceptable The resource identified by the request is only capable
of generating response entities that have content
characteristics not acceptable according to the Accept
header field sent in the request.
335677334 408 Request Timeout The server could not produce a response within a
suitable amount of time.
335677335 410 Gone The requested resource is no longer available at the

server and no forwarding address is known.
335677336 412 Precondition If there is no matching event state at the ESC, for
Failed example, the event state to be modified has already
expired, the EPA receives a 412 response to the
PUBLISH request.
335677337 413 Request Entity The server is refusing to process a request because the
Too Large request entity-body is larger than the server is willing
or able to process.
335677338 414 Request-URI Too The server is refusing to service the request because
Large the Request-URI is larger than the server is willing to
interpret.
335677339 415 Unsupported The server is refusing to service the request because
Media Type the message body of the request is in a format not
supported by the server for the requested method. The
server MUST return a list of acceptable formats using
the Accept, Accept-Encoding, or Accept-Language
header field, depending on the specific problem with
the content.
335677340 416 Unsupported URI The server cannot process the request because the
Scheme scheme of the URI in the Request-URI is unknown to
the server.
335677341 420 Bad Extension The server did not understand the protocol extension
specified in a Proxy-Require or Require header field.
335677342 421 Extension The UAS needs a particular extension to process the
Required request, but this extension is not listed in a Supported
header field in the request. Responses with this status
code MUST contain a Require header field listing the

EMS Code
required extensions.
335677343 422 Session Expires The server performs a SessionTimer check for the
Too Small message. If the UAC supports SessionTimer but the
Session Expires parameter in the message is smaller
than the value configured on the local server, the
335677344 423 Interval Too The server is rejecting the request because the
Brief expiration time of the resource refreshed by the request
is too short.
335677345 429 Provide Referrer if the refer target requires a valid Referred-By token to
Identity accept the request. This can occur when either no
token is provided or a provided token is invalid.
335677346 433 Anonymity When the From header in the request is anonymous but
Disallowed the network does not allow an anonymous value, the
335677347 480 Temporarily The callee's end system was contacted successfully but
Unavailable the callee is currently unavailable.
335677348 481 Call This status indicates that the UAS received a request
Leg/Transaction that does not match any existing dialog or transaction.
Does Not Exist
335677349 482 Loop Detected The server has detected a loop.
335677350 483 Too Many Hops The server received a request that contains a Max-
Forwards header field with the value zero.
335677351 484 Address The server received a request with a Request-URI that
Incomplete was incomplete.
335677352 485 Ambiguous The Request-URI was ambiguous. In such a case,

several records match the Request-URI.
335677353 486 Busy Here The callee's end system was contacted successfully,
but the callee is currently not willing or able to take
additional calls at this end system. The user could also
be available elsewhere, such as through a voice mail
service.

EMS Code
335677354 487 Request The request was terminated by a BYE or CANCEL

Terminated request.
335677355 488 Not Acceptable The media resource carried in the request is
Here unacceptable. The reasons may be the following:
 The caller carries an unsubscribed media resource.
 The local policy does not allow the media resource.
335677356 489 Bad Event Checking the Event header in the subscription message
fails. The reasons may be the following: The Subscribe
and Notify requests must carry the Event header. The
server returns a 489 response if the header is not
available or the Event header is not the supported type.
335677357 491 Request Pending The request was received by a UAS that had a pending
request within the same dialog.
335677359 493 Undecipherable The request was received by a UAS that contained an
encrypted MIME body for which the recipient does not
possess or will not provide an appropriate decryption
key.
335677360 494 Security An unprotected request that contains a Require or

Agreement Proxy-Require header field with the value "sec-agree".
Required
335677361 Other 4xx response These response codes are sent in client error scenarios
4xx codes except for except for the previously mentioned client error
listed 4xx
response codes
335677362 500 Server Internal The server encountered an unexpected condition that
Error prevented it from fulfilling the request. Usually, this
error is an internal error.
335677363 501 Not Implemented The server does not support the functionality required
to fulfill the request.
335677364 502 Bad Gateway The server, while acting as a gateway or proxy,
received an invalid response from the downstream
server it accessed in attempting to fulfill the request.
335677365 503 Service The server is temporarily unable to process the request

EMS Code
Unavailable due to a temporary overloading or maintenance of the

server.
335677366 504 Server Time-out The server did not receive a timely response from an
external server it accessed in attempting to process the
request.
335677367 505 SIP Version not The server does not support, or refuses to support, the
supported SIP protocol version that was used in the request.
335677368 513 Message Too The server was unable to process the request since the
Large message length exceeded its capabilities.
335677369 533 Service Lost If the user data cannot be found in the local database
and the redundancy policy configuration is set to 533,
335677370 580 Precondition When a UAS, acting as an answerer, cannot or is not

Failure willing to meet the preconditions in the offer, it rejects
the offer by returning a 580 response.
335677371 Other 5xx response These response codes are sent in server error scenarios
5xx codes except for except for the previously mentioned server error
listed 5xx
response codes
335677372 600 Busy Everywhere The callee's end system was contacted successfully but
the callee is busy and does not wish to take the call at
this time. This status response is returned only if the
client knows that no other end point (such as a voice
mail system) will answer the request.
335677373 603 Decline The callee's machine was successfully contacted but
the user explicitly does not wish to or cannot
participate.
335677374 604 Does Not Exist The server has authoritative information that the user
Anywhere indicated in the Request-URI does not exist anywhere.
335677375 606 Not Acceptable The user's agent was contacted successfully but some
aspects of the session description such as the requested
media, bandwidth, or addressing style were not
acceptable.

EMS Code
335677376 Other 6xx response These response codes are sent in global failure
6xx codes except for scenarios except for the previously mentioned global
the previously failure scenarios.
listed 6xx
response codes
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the MT S-CSCF generates or
transits an Oxx response to the INVITE message. For details, see point A in Figure 1.
Figure 1 Measurement point of S-CSCF MT Oxx Responses Measurement
Formula
None
Related Notes
Carriers can use this measurement entity on the network management system to calculate
the ratio that the terminating S-CSCF generates or transits Oxx responses. Refer to the S-
CSCF Session Completion Rate measurement entity.

9.1.6.1.3 335655491 Number of S-CSCF

Initial Registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of initial registration requests received by the
S-CSCF from UEs in a measurement period. Re-registration requests and second
registration requests (responding to authentication challenges) from UEs are excluded from
the measurement.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by 1 when the S-CSCF receives an
initial REGISTER request from a UE and the value of the Expires header field in the
request is not 0. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF Initial Registration Attempts
Formula
None
Related Notes
None

9.1.6.1.4 335655492 Number of S-CSCF

Successful Initial Registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 responses sent by the S-CSCF to initial
registration requests of UEs in a measurement period. The successful re-registration
requests of UEs are excluded from the measurement.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by 1 when the S-CSCF sends a 200
response to an initial registration request of a UE. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF Successful Initial Registrations
Formula
None
Related Notes
None

9.1.6.1.5 335655519 Number of S-CSCF

Re-registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of re-registration requests received by the S-
CSCF from UEs in a measurement period.
A UE can request re-registration by sending a new REGISTER request to the network at
any time. For example, when registration expires and must be updated, a UE can request re-
registration.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by 1 when the S-CSCF receives a re-
registration request from a UE and the value of the Expires header field in the request is not
0. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF Re-registration Attempts
Formula
None
Related Notes
None

9.1.6.1.6 335655520 Number of S-CSCF

Successful Re-registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 responses that the S-CSCF sends after
receiving the re-registration requests from UEs in a measurement period.
A UE can request re-registration by sending a new REGISTER request to the network at
any time. For example, when registration expires and must be updated, a UE can request re-
registration.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by 1 when the S-CSCF sends a 200
response after receiving a re-registration request from a UE and the value of the Expires
header field in the request is not 0. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF Successful Re-registrations
Formula
None
Related Notes
None

9.1.6.1.7 335655576 Number of S-CSCF

MO Session Attempts
 Description
 Measurement Object
 Entity Type
 Unit
 Formula
Description
This measurement entity counts the number of INVITE requests received by the S-CSCF at
the MO side in a measurement period.
Measurement Object
S-CSCF
Entity Type
Cumulative
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the S-CSCF at the MO side
receives an INVITE request. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF MO Session Attempts
Formula
None
9.1.6.1.8 335655578 Number of S-CSCF

Answered MO Sessions
 Description
 Entity Type
 Unit
 Formula
Description
This measurement entity counts the number of answered sessions originated to the S-CSCF
at the MO side in a measurement period.
Measurement Object
S-CSCF
Entity Type
Cumulative
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the S-CSCF at the MO side
receives a 200 (to INVITE) response. For details, see point C in Figure 1.
Figure 1 Measurement point of Number of S-CSCF MO Answered Sessions
Formula
None

9.1.6.1.9 335655581 Number of S-CSCF

MT Session Attempts
 Description
 Entity Type
 Unit
 Formula
Description
This measurement entity counts the number of INVITE requests received by the S-CSCF at
the MT side in a measurement period.
Measurement Object
S-CSCF
Entity Type
Cumulative
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the S-CSCF at the MT side
receives an INVITE request. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF MT Session Attempts
Formula
None

9.1.6.1.10 335655583 Number of S-CSCF

Answered MT Sessions
 Description
 Entity Type
 Unit
 Formula
Description
This measurement entity counts the number of answered sessions originated to the S-CSCF
at the MT side in a measurement period.
Measurement Object
S-CSCF
Entity Type
Cumulative
Unit
None
Measurement Point
The value of this measurement entity increases by 1 when the S-CSCF at the MT side
receives a 200 (to INVITE) response. For details, see point C in Figure 1.
Figure 1 Measurement point of Number of S-CSCF MT Answered Sessions
Formula
None

9.1.6.1.11 335664321 Number of S-CSCF

MO Sessions Released Before Ringing
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of times the originating S-CSCF receives a
CANCEL request from the calling party before receiving a 180 (to INVITE) response from
the called party in a measurement period.
An IMS subscriber originates a call. The originating S-CSCF receives a CANCEL request
instead of a 180 response.
Unit
None
Measurement Point
For details, see point A in Figure 1.

Figure 1 Measurement point of Number of S-CSCF MO Sessions Released Before Ringing
Formula
None
Related Notes
This measurement entity is used to analyze the behavior of the calling party.

9.1.6.1.12 335664322 Number of S-CSCF
MT Sessions Released Before Ringing
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of times the terminating S-CSCF receives a
CANCEL request from the calling party before receiving a 180 (to INVITE) response from
An IMS subscriber originates a call. The terminating S-CSCF receives a CANCEL request
after receiving a 180 response.
Unit
None
Measurement Point

Figure 1 Measurement point of Number of S-CSCF MT Sessions Released Before Ringing
Formula
None
Related Notes
This measurement entity is used to analyze the behavior of the calling party.

9.1.6.1.13 335664324 Number of S-CSCF

MO Sessions Released After Ringing
 Description
 Unit
 Formula
 Related Notes
Description
CANCEL request from the calling party after receiving a 180 (to INVITE) response from
Unit
None
Measurement Point

Figure 1 Measurement point of Number of S-CSCF MO Sessions Released After Ringing
Formula
None
Related Notes
This measurement entity is used to calculate the number of successful session attempts.
Carriers can use this measurement entity to develop a formula for calculating the call
completion rate.

9.1.6.1.14 335664325 Number of S-CSCF

MT Sessions Released After Ringing
 Description
 Unit
 Formula
 Related Notes
Description
CANCEL request from the calling party after receiving a 180 (to INVITE) response from
Unit
None
Measurement Point

Figure 1 Measurement point of Number of S-CSCF MT Sessions Released After Ringing
Formula
None
Related Notes
This measurement entity is used to calculate the number of successful session attempts.
Carriers can use this measurement entity to develop a formula for calculating the call
completion rate.

9.1.6.1.15 335672421 Number of S-CSCF
Registered Users
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of subscribers registered with the S-CSCF in a
measurement period.
Unit
None
Measurement Point
Each RDB module obtains the number of subscribers registered with the S-CSCF and
reports the number to the performance measurement module at the end of a measurement
period. Then, the performance measurement module sums up the number of subscribers
reported by different RDB modules.
Formula
Number of S-CSCF Registered Users = Larger value between the total number of IMPIs
and half of the total number of IMPUs
Related Notes
None
9.1.6.1.16 335672443 Number of S-CSCF

Using AKA Authentication Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 401 messages the S-CSCF returns in
response to REGISTER messages sent by UEs that use the AKA authentication in a
measurement period. The REGISTER message is used for initial registration, re-
registration, or deregistration.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by 1 when the S-CSCF returns a 401
message after receiving a REGISTER message that needs to be authenticated using AKA
authentication from a UE. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of S-CSCF Using AKA Authentication Attempts
Formula
None
Related Notes
None
9.1.6.1.17 335672444 Number of S-CSCF
Successful Using AKA Authentication
Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of times the S-CSCF successfully authenticates
REGISTER messages sent by UEs that use the AKA authentication in a measurement
period. The REGISTER message is used for initial registration, re-registration, or
deregistration.
Unit
Integer
Measurement Point
After receiving a REGISTER message that uses AKA authentication from a UE, the S-
CSCF returns a 401 message. The UE then sends a second REGISTER message. If the S-
CSCF successfully authenticates the message, it returns a 200 or Oxx message. An Oxx
message indicates an authentication success but the registration fails. The value of this
measurement entity is incremented by 1 when the S-CSCF returns a 200 or Oxx message.
Figure 1 Measurement point of Number of S-CSCF Successful Using AKA Authentication
Attempts
Formula
None
Related Notes
None
< Previous topic
9.1.6.2 ATS9900
478155820 MO Short Message Attempts
478155821 MO Short Message Success Times
478155823 MT Short Message Attempts
478155824 MT Short Message Success Times
478155988 Number of CCU Subscribers
478156521 Number of Registered IN Subscribers on the ATS
478156717 Number of Successfully Registered Wi-Fi Subscribers
478156718 Number of Switches from Wi-Fi to LTE
478156719 Number of Switches from LTE to Wi-Fi
478156721 Number of Auxiliary Devices Registering over Wi-Fi

9.1.6.2.1 478155820 MO Short Message

Attempts
 Description
 Unit
 Formula
Description
This measurement entity counts the number of MESSAGE messages received by the IP-
SM-GW from the S-CSCF. By analyzing the value of this measurement entity, you can
obtain the number of MO short messages sent by the user in a measurement period.
This measurement entity applies only to FMC networks.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when the IP-SM-GW receives a
MESSAGE message from the S-CSCF. For details, see point A in Figure 1.
Figure 1 Measurement point of MO Short Message Attempts
Formula
None
Parent Topic: ATS9900
Next topic >
9.1.6.2.2 478155821 MO Short Message

Success Times
 Description
 Unit
 Formula
Description
This measurement entity counts the number of the IP-SM-GW receives the success
responses to the MAP_MO_FORWARD_SHORT_MESSAGE_REQ messages. By
analyzing the value of this measurement entity, you can obtain the number of times MO
short messages are successfully sent by the IP-SM-GW in a measurement period.
Unit
Integer
Measurement Point
success response to the MAP_MO_FORWARD_SHORT_MESSAGE_REQ message. For
details, see point A in Figure 1.
Figure 1 Measurement point of MO Short Message Success Times
Formula
None
9.1.6.2.3 478155823 MT Short Message

Attempts
 Description
 Unit
 Formula
Description
This measurement entity counts the number of

MAP_MT_FORWARD_SHORT_MASSAGE messages received by the IP-SM-GW from
the SMSC. By analyzing the value of this measurement entity, you can obtain the number
of MT short messages received by the IP-SM-GW in a measurement period.
Unit
Integer
Measurement Point
MAP_MT_FORWARD_SHORT_MASSAGE message from the SMSC. For details, see
point A in Figure 1.
Figure 1 Measurement point of MT Short Message Attempts
Formula
None
9.1.6.2.4 478155824 MT Short Message

Success Times
 Description
 Unit
 Formula
Description
This measurement entity counts the number of times the IP-SM-GW successfully sends the
MAP_MT_FORWARD_SHORT_MASSAGE_ACK messages to the SMSC after the IP-
SM-GW receives the 200 (to MESSAGE) responses or receives the
MAP_MT_FORWARD_SHORT_MASSAGE_ACK from VMSC. By analyzing the value
of this measurement entity, you can obtain the times the MT short messages is successfully
sent by the IP-SM-GW in a measurement period.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when the IP-SM-GW sends a
MAP_MT_FORWARD_SHORT_MASSAGE_ACK message to the SMSC after the IP-
SM-GW receives a 200 (to MESSAGE) response. For details, see point A in Figure 1.
The value of this measurement entity increases by 1 when the IP-SM-GW sends a
MAP_MT_FORWARD_SHORT_MASSAGE_ACK message to the SMSC after the IP-
SM-GW receives a successfully MAP_MT_FORWARD_SHORT_MASSAGE_ACK from
VMSC. For details, see point A in Figure 2.
Figure 1 Measurement point of MT Short Message Success Times(1)
Figure 2 Measurement point of MT Short Message Success Times(2)
Formula
None
9.1.6.2.5 478155988 Number of CCU

Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
The ATS9900 dynamically records the number of subscribers on the CCU module in a
measurement period. When the number of subscribers changes, the ATS9900 records this
measurement entity. The final record in a measurement period is viewed as the
measurement result.
This measurement entity is reserved for future use.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when the CCU module receives a
REGISTER message and successfully downloads subscriber data. For details, see point A
in Figure 1.
Figure 1 Number of CCU Subscribers
The value of this measurement entity increases by 1 when the CCU module receives an
INVITE message and successfully downloads subscriber data. For details, see point B in
Figure 2.
For subscribers who need to register with the ATS9900, the value of this measurement
entity decreases by 1 when the CCU module receives a DEREGISTER message and deletes
subscriber data. For details, see point C in Figure 3.
For subscribers who do not need to register with the ATS9900, the value of this
measurement entity decreases by 1 when the CCU module receives a TIMEOUT message
when subscribers are in the idle state. For details, see point D in Figure 4.
Formula
None
Related Notes
None
9.1.6.2.6 478156521 Number of Registered

IN Subscribers on the ATS
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of intelligent subscribers registered
successfully with the ATS9900 in a measurement period.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when the ATS9900 downloads the data
of an intelligent subscriber from the HSS upon receipt of a REGISTER message. The value
of this measurement entity decreases by 1 when the ATS9900 deletes the data of an
intelligent subscriber from the HSS upon receipt of a DEREGISTER message. For details,
see point A in Figure 1.
Figure 1 Measurement point of Number of Registered IN Subscribers on the ATS
Formula
N/A
Related Notes
N/A
9.1.6.2.7 478156717 Number of

Successfully Registered Wi-Fi Subscribers
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoWiFi subscribers who successfully
register with the ATS9900 in a measurement period. The ATS9900 uses the implicitly
registered set (IRS) to measure this entity.
Unit
None
Measurement Point
When the ATS9900 determines that a VoWiFi subscriber sends a registration or

deregistration request and the IMPU has not been registered before, the ATS9900 responds
the CSCF with a 200 message.
 The value of this measurement entity is incremented by 1 when the ATS9900 sends a
200 message as a response to a registration request.
 The value of this measurement entity is decremented by 1 when the ATS9900 sends a
200 message as a response to a deregistration request. For VoWiFi subscribers who have
subscribed to the apple-multi-SIM service, the value of this measurement is decremented
by 1 only when all devices of the subscriber are not registered using VoWiFi.
NOTE:
The measurement entity does not count in the number of registered subscribers whose calls are barred due to a
lack of the Multi-Device license. This is because the Multi-Device license does not limit registration but does
not allow calls of Multi-Device subscribers when their registration information does not match the license
control item.
Figure 1 Measurement point of Number of Successfully Registered Wi-Fi Subscribers
Formula
None
Related Notes
None
9.1.6.2.8 478156718 Number of Switches

from Wi-Fi to LTE
 Description
 Unit
 Formula
Description
When subscribers access LTE networks from Wi-Fi networks, regardless of whether the
subscribers in sessions or not , the ATS9900 receives reregistration requests from the
access side. This measurement entity counts the number of switches from Wi-Fi networks
to LTE networks in a measurement period.
Unit
Integer
Measurement Point
On receiving a reregistration request, the ATS9900 determines the type of the access
network based on the parameters in the received PANI and Contact header fields. The value
of this measurement entity increases by 1 when the ATS9900 determines that the
reregistration request is used for a switch from a Wi-Fi network to an LTE network. For
Figure 1 Measurement point of Number of Switches from Wi-Fi to LTE
Formula
None
9.1.6.2.9 478156719 Number of Switches

from LTE to Wi-Fi
 Description
 Unit
 Formula
Description
When subscribers access Wi-Fi networks from LTE networks, the ATS9900 receives
reregistration requests from the access side. This measurement entity counts the number of
switches from LTE networks to Wi-Fi networks in a measurement period.
Unit
Integer
Measurement Point
On receiving a reregistration request, the ATS9900 determines the type of the access
network based on the parameters in the received PANI and Contact header fields. The value
of this measurement entity increases by 1 when the ATS9900 determines that the
reregistration request is used for a switch from an LTE network to a Wi-Fi network. For
Figure 1 Measurement point of Number of Switches from LTE to Wi-Fi
Formula
None
9.1.6.2.10 478156721 Number of Auxiliary

Devices Registering over Wi-Fi
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of REGISTER messages that the ATS9900
receives from auxiliary devices of Multi-Device subscribers.
Unit
None
Measurement Point
The value of this measurement entity is incremented by 1 when the ATS9900 detects that
the received REGISTER message is sent by an auxiliary device of a Multi-Device
subscriber for registration. The value of this measurement entity is decremented by 1 when
the ATS9900 detects that the auxiliary device sends the REGISTER message for
deregistration. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of Auxiliary Devices Registering over Wi-Fi
Formula
None
Related Notes
None
< Previous topic
9.1.6.3 HSS9860
352324100 Number of Provisioned IMS Subscriptions Stored in an HSS

9.1.6.3.1 352324100 Number of Provisioned

IMS Subscriptions Stored in an HSS
 Description
 Unit
 Measurement Types
 Formula
 Related Notes
Description
This measurement entity counts the number of provisioned IMS subscriptions stored in an
HSS.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when an IMS subscription is added in
the HSS and decreases by 1 when an IMS subscription is removed from the HSS.
Measurement Types
State
Formula
None
Related Notes
None
Parent Topic: HSS9860
9.1.6.4 SE2900
1907465347 Number of ABCF Initial Registration Attempts
1907465348 Number of ABCF Successful Initial Registrations
1907465350 Number of ABCF Re-registration Attempts
1907465351 Number of ABCF Successful Re-registrations
1907465358 Number of Users in The Access Network
1907466045 Number of ABCF MO Session Attempts
1907466046 Number of ABCF MO Connected Sessions
1907466047 Number of ABCF MO Answered Sessions
1907466048 Number of ABCF MT Session Attempts
1907466049 Number of ABCF MT Connected Sessions
1907466050 Number of ABCF MT Answered Sessions
1907466085 Traffic of ABCF MO Answered Sessions
1907466086 Traffic of ABCF MT Answered Sessions
1907466105 Mean Duration from Answering to Release of ABCF Sessions
1907466106 Mean Duration from Originating to Ringing of ABCF MO Sessions
1907466107 Mean Duration from Originating to Ringing of ABCF MT Sessions
1907466118 Number of ABCF MO Session Interruptions
1907466119 Number of ABCF MT Session Interruptions
1907466549 Number of ABCF Roaming Subscribers in The Access Network
1907466568 ABCF Access Network IP QoS Mos Average
1907467000 Number of Session Interruptions Triggered by Wireless Network on MO-Side A-BCF
1907467001 Number of Session Interruptions Triggered by Wireless Network on MT-Side A-BCF
1907467809 Number of ABCF Registered VoWiFi Users
1907467810 Number of ABCF VoWiFi Initial Registration Attempts
1907467811 Number of ABCF VoWiFi Successful Initial Registrations
1907467813 Number of ABCF VoWiFi Re-registration Attempts
1907467814 Number of ABCF VoWiFi Successful Re-registrations
1907467816 Number of ABCF MO-Side VoWiFi Session Interruptions
1907467817 Number of ABCF MT-Side VoWiFi Session Interruptions
1907467819 Number of ABCF MO-Side VoWiFi Session Interruptions Triggered by Wireless Network
1907467820 Number of ABCF MT-Side VoWiFi Session Interruptions Triggered by Wireless Network
1907468093 Number of ABCF MO-Side VoWiFi Session Attempts
1907468094 Number of ABCF MO-Side VoWiFi Connected Sessions
1907468095 Number of ABCF MO-Side VoWiFi Answered Sessions
1907468105 Traffic of ABCF MO-Side VoWiFi Answered Sessions
1907468110 Number of ABCF MT-Side VoWiFi Session Attempts
1907468111 Number of ABCF MT-Side VoWiFi Connected Sessions
1907468112 Number of ABCF MT-Side VoWiFi Answered Sessions
1907468122 Traffic of ABCF MT-Side VoWiFi Answered Sessions
1907468135 ABCF VoWiFi Access Network IP QoS LosRate Average
1907468153 ABCF VoWiFi Access Network IP QoS Mos Average

9.1.6.4.1 1907465347 Number of ABCF

Initial Registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of initial REGISTER requests received by the
A-BCF from a UE on an access network in a measurement period (5 minutes by default).
NOTE:
UE-originated re-REGISTER requests and second REGISTER requests (responding to authentication
challenges) are excluded from the measurement.
Unit
None
Measurement Point
The value of this measurement entity increases by one when the A-BCF receives a
REGISTER request from a UE on an access network and the value of the Expires header in
the request is not 0. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF Initial Registration Attempts
Formula
None
Related Notes
None
Parent Topic: SE2900
Next topic >
9.1.6.4.2 1907465348 Number of ABCF

Successful Initial Registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 OK responses (to initial REGISTER
requests from a UE on an access network) received by the A-BCF in a measurement period
(5 minutes by default).
NOTE:
The 200 OK responses to UE-originated re-REGISTER requests are excluded from the measurement.
Unit
None
Measurement Point
The value of this measurement entity increases by one when the A-BCF receives a 200 OK
response (to an initial REGISTER request from a UE on an access network) from the core
network. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF Successful Initial Registrations
Formula
None
Related Notes
None
9.1.6.4.3 1907465350 Number of ABCF Re-

registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of re-REGISTER requests received by the A-
BCF from a UE on an access network in a measurement period (5 minutes by default).
A UE can initiate reregistration by sending a new REGISTER request to the network at any
time. For example, when a registration is about to expire, a UE initiates reregistration.
Unit
None
Measurement Point
The value of this measurement entity increases by one when the A-BCF receives a re-
REGISTER request from a UE on an access network and the value of the Expires header in
the request is not 0. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF Re-registration Attempts
Formula
None
Related Notes
None
9.1.6.4.4 1907465351 Number of ABCF

Successful Re-registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 OK responses (to re-REGISTER
requests from a UE on an access network) sent by the A-BCF in a measurement period (5
minutes by default).
Unit
None
Measurement Point
The value of this measurement entity increases by one when the A-BCF sends a 200 OK
response to a re-REGISTER request from a UE on an access network. For details, see point
A in Figure 1.
Figure 1 Measurement point of Number of ABCF Successful Re-registrations
Formula
None
Related Notes
None
9.1.6.4.5 1907465358 Number of Users in
The Access Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of subscribers registered with each AN on the
A-BCF. The subscriber number is counted based on the IMPI.
Unit
times
Measurement Point
Each SCU module obtains the number of subscribers registered with each AN on the A-
BCF and reports the number to the performance measurement module at the end of a
measurement period. Then the performance measurement module calculates the number of
subscribers on the same AN from different SCU modules to obtain the total number of
subscribers from this AN.
Formula
None
Related Notes
None
9.1.6.4.6 1907466045 Number of ABCF

MO Session Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of INVITE requests received by the MO-side
A-BCF in a measurement period (5 minutes by default).
Unit
Number
Measurement Point
The value of this measurement entity increases by one when the MO-side A-BCF receives
an INVITE request. For details, see point A in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, an INVITE request is received
in a measurement period, and an ACK message is received in the next period), the value of this measurement
entity is counted in the next period.
Figure 1 Measurement point of Number of ABCF MO Session Attempts
Formula
None
Related Notes
None
9.1.6.4.7 1907466046 Number of ABCF

MO Connected Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of connected sessions originated from the MO-
side A-BCF in a measurement period (5 minutes by default).
Unit
None
Measurement Point
The value of this measurement entity increases by one when the MO-side A-BCF receives a
180 (Ringing) response to an INVITE request. For details, see point A in Figure 1. If
multiple 180 (Ringing) responses to an INVITE request are received, only the first one is
counted. If no 180 (Ringing) response is received, the value of this measurement entity is
measured when the A-BCF receives a corresponding 200 OK response. For details, see
point B in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, a 180 or 200 OK response is
received in a measurement period, and an ACK message is received in the next period), the value of this
measurement entity is counted in the next period.
Figure 1 Measurement points of Number of ABCF MO Connected Sessions
Formula
None
Related Notes
None
9.1.6.4.8 1907466047 Number of ABCF

MO Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of answered sessions originated to the MO-side
Unit
None
Measurement Point
200 OK response to an INVITE request. For details, see point A in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, a 200 OK response is received
Figure 1 Measurement point of Number of ABCF MO Answered Sessions
Formula
None
Related Notes
None
9.1.6.4.9 1907466048 Number of ABCF MT

Session Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of INVITE requests received by the MT-side
Unit
None
Measurement Point
The value of this measurement entity increases by one when the MT-side A-BCF receives
an INVITE request. For details, see point A in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, an INVITE request is received
Figure 1 Measurement point of Number of ABCF MT Session Attempts
Formula
None
Related Notes
None
9.1.6.4.10 1907466049 Number of ABCF

MT Connected Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of connected sessions received by the MT-side
Unit
None
Measurement Point
The value of this measurement entity increases by one when the MT-side A-BCF receives a
180 (Ringing) response to an INVITE request. For details, see point A in Figure 1. If no 180
(Ringing) response is received, the value of this measurement entity is measured when the
A-BCF receives a corresponding 2XX response. For details, see point B in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, a 180 or 200 OK response is
received in a measurement period, and an ACK message is received in the next period), the value of this
measurement entity is counted in the next period.
Figure 1 Measurement point of Number of ABCF MT Connected Sessions
Formula
None
Related Notes
None
9.1.6.4.11 1907466050 Number of ABCF

MT Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of answered sessions received by the MT-side
Unit
None
Measurement Point
2XX response to an INVITE request. For details, see point A in Figure 1.
NOTE:
When the call setup process spans different measurement periods (specifically, a 200 OK response is received
Figure 1 Measurement point of Number of ABCF MT Answered Sessions
Formula
None
Related Notes
None
9.1.6.4.12 1907466085 Traffic of ABCF MO

Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the total traffic of calls that the MO-side A-BCF
answers in a measurement period (5 minutes by default).
Unit
Erlang
Measurement Point
The A-BCF calculates the total answering duration by summing up the answering duration
of each call, and then measures the value of this measurement entity based on the total
answering duration and measurement period. For details, see points A and B in Figure 1.
Figure 1 Measurement points of a call answering duration
Formula
Related Notes
None
9.1.6.4.13 1907466086 Traffic of ABCF MT

Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the total traffic of calls that the MT-side A-BCF answers
in a measurement period (5 minutes by default).
Unit
Erlang
Measurement Point
The A-BCF calculates the total answering duration by summing up the answering duration
of each call, and then measures the value of this measurement entity based on the total
answering duration and measurement period. For details, see points A and B in Figure 1.
Figure 1 Measurement points of a call answering duration
Formula
Related Notes
None
9.1.6.4.14 1907466105 Mean Duration
from Answering to Release of ABCF
Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average duration from call answering to releasing on
the A-BCF in a measurement period (5 minutes by default).
Unit
SECOND
Measurement Point
To obtain the value of this measurement entity, you must create a measurement task to
obtain the duration from call answering to releasing of each call so that the A-BCF can
calculate the total duration from call answering to releasing, and create a measurement task
to obtain the value of 1907466044 Number of ABCF Answered Sessions. The duration
from call answering to releasing is the period between receiving the 2XX response to the
INVITE request and the 2XX response to the BYE request. For details, see points A and B
in Figure 1.
Figure 1 Measurement points of the duration from call answering to releasing on the ABCF
Formula
Related Notes
None
9.1.6.4.15 1907466106 Mean Duration
from Originating to Ringing of ABCF MO
Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average duration from call originating to ringing on
the MO-side A-BCF in a measurement period (5 minutes by default).
Unit
Milliseconds
Measurement Point
The MO-side A-BCF calculates the total duration from call originating to ringing by
summing up each duration from call originating to ringing, and then measures the value of
this measurement entity based on the total duration from call originating to ringing and the
value of 1907466046 Number of ABCF MO Connected Sessions. The duration from call originating
to ringing varies in different scenarios:
 Scenario 1: The duration from call originating to ringing is the period between receiving
the INVITE request and 180 response. For details, see points A and B in Figure 1.
the INVITE request and 2XX response (with no 180 response received). For details, see
points A and B in Figure 2.
Figure 1 Measurement points of the duration from call originating to ringing (scenario 1)
Figure 2 Measurement points of the duration from call originating to ringing (scenario 2)
Formula
Related Notes
None
9.1.6.4.16 1907466107 Mean Duration
from Originating to Ringing of ABCF MT
Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average duration from call originating to ringing on
the MT-side A-BCF in a measurement period (5 minutes by default).
Unit
Milliseconds
Measurement Point
The MT-side A-BCF calculates the total duration from call originating to ringing by
summing up each duration from call originating to ringing, and then measures the value of
this measurement entity based on the total duration from call originating to ringing and the
value of 1907466049 Number of ABCF MT Connected Sessions. The duration from call originating
to ringing varies in different scenarios:
the INVITE request and 180 response. For details, see points A and B in Figure 1.
the INVITE request and 2XX response (with no 180 response received). For details, see
Figure 1 Measurement points of the duration from call originating to ringing on the MT-side ABCF
(scenario 1)
Figure 2 Measurement points of the duration from call originating to ringing on the MT-side ABCF
(scenario 2)
Formula
Mean Duration from Originating to Ringing of ABCF MT Sessions = Duration from
Originating to Ringing of ABCF MT Sessions / 1907466049 Number of ABCF MT Connected
Sessions
Related Notes
None
9.1.6.4.17 1907466118 Number of ABCF
MO Session Interruptions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of interrupted sessions because of session timer
expiration or failure to detect media streams on the MO-side A-BCF in a measurement
period (5 minutes by default).
Unit
Number
Measurement Point
The value of this measurement entity increases by one when a session is interrupted
because of session timer expiration or failure to detect media streams on the MO-side A-
BCF. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF MO Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.18 1907466119 Number of ABCF

MT Session Interruptions
 Description
 Unit
 Formula
 Related Notes
Description
expiration or failure to detect media streams on the MT-side A-BCF in a measurement
period (5 minutes by default).
Unit
None
Measurement Point
because of session timer expiration or failure to detect media streams on the MT-side A-
BCF. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF MT Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.19 1907466549 Number of ABCF

Roaming Subscribers in The Access
Network
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the numbers of roaming UEs registered with every SIP AN
on the A-BCF in a measurement period (5 minutes by default).
Unit
number
Measurement Point
Each SCU module regularly reports the numbers of roaming UEs registered with every SIP
AN on the A-BCF to the call statistics module. The call statistics module then calculates
the value of this measurement entity by summing up the number of roaming UEs registered
with every SIP AN reported by each SCU module.
Formula
None
Related Notes
None
9.1.6.4.20 1907466568 ABCF Access

Network IP QoS Mos Average
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average MOS value obtained by the SE2900 during
each measurement period in access-network-based QoS measurement. This measurement
entity indicates network conditions from the access networks to the SE2900.
Unit
none
Measurement Point
The MOS value at each measurement point is collected and accumulated. At the end of the
measurement period, the accumulated value is divided by the number of collected MOS
values to obtain the average MOS value.
Formula
Average MOS value = Accumulated MOS value on the access side/Number of MOS values
collected on the access side
Related Notes
Table 1 describes impacts on network quality based on this measurement entity.
Table 1 Impacts on network quality based on the access network average MOS value
Value or Impact on Network Quality

Value Range
[0.0, 3.0) Communications during a call are interrupted severely. Call quality is greatly
affected and unacceptable.
[3.0, 3.5) Communications during a call are interrupted significantly. Call quality is affected
but acceptable.
[3.5, 4.0) Communications during a call are interrupted frequently but call quality is slightly
affected.
[4.0, 5.0) Communications during a call are interrupted occasionally but call quality is not
affected.

9.1.6.4.21 1907467000 Number of Session

Interruptions Triggered by Wireless
Network on MO-Side A-BCF
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of Rx bearer-triggered session interruptions on

the MO-side A-BCF in a measurement period (5 minutes by default).
Unit
N/A
Measurement Point
The value of this measurement entity increases by one when an Rx bearer-triggered session
interruption occurs on the MO-side A-BCF. For details, see point A in Figure 1. A video
session is interrupted when the SBC fails to apply for bearer resources (indicated by the
negative AAA message), receives an RAR message reporting a bearer release event, or
receives an ASR message where the Abort-Cause value is not PS_TO_CS_HANDOVER.
Figure 1 Number of Session Interruptions Triggered by Wireless Network on MO-Side A-BCF
Formula
None
Related Notes
None
9.1.6.4.22 1907467001 Number of Session
Interruptions Triggered by Wireless
Network on MT-Side A-BCF
 Description
 Unit
 Formula
 Related Notes
Description

the MT-side A-BCF in a measurement period (5 minutes by default).
Unit
N/A
Measurement Point
interruption occurs on the MT-side A-BCF. For details, see point A in Figure 1. A video
Figure 1 Number of Session Interruptions Triggered by Wireless Network on MT-Side A-BCF
Formula
None
Related Notes
None
9.1.6.4.23 1907467809 Number of ABCF

Registered VoWiFi Users
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of VoWiFi UEs registered with the A-BCF in a
measurement period (5 minutes by default).
Unit
TIMES
Measurement Point
Each SCU module reports the number of VoWiFi UEs registered with the A-BCF to the
call statistics module at the end of a measurement period. The call statistics module then
calculates the value of this measurement entity by summing up the number of registered
VoWiFi UEs reported by each SCU module. This measurement excludes statistics about
the VoWiFi UE that is deregistered in the measurement period.
Formula
NOTE:
The ABCF supports the traffic model where one IMPI corresponds to three IMPUs.
Related Notes
None
9.1.6.4.24 1907467810 Number of ABCF

VoWiFi Initial Registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of UE-originated VoWiFi initial REGISTER
requests received by the A-BCF in a measurement period (5 minutes by default).
Unit
None
Measurement Point
The value of this measurement entity varies in the following scenarios:

 Scenario 1: If bit 14 of BCFPARA12 is set to 0, the value of this measurement entity
increases by one when the A-BCF receives a UE-originated VoWiFi initial REGISTER
request carrying a non-0 expires parameter value. For details, see point A in Figure 1.
increases by one when the A-BCF receives a UE-originated VoWiFi initial REGISTER
request carrying a non-0 expires parameter value before receiving or after forwarding a
401 response. The REGISTER requests are counted once. For details, see point A or B
in Figure 2.
Figure 1 Measurement point of Number of ABCF VoWiFi Initial Registration Attempts (scenario
1)
Figure 2 Measurement point of Number of ABCF VoWiFi Initial Registration Attempts (scenario
2)
Formula
None
Related Notes
None
9.1.6.4.25 1907467811 Number of ABCF

VoWiFi Successful Initial Registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 OK responses (to UE-originated
VoWiFi initial REGISTER requests) received by the A-BCF in a measurement period (5
NOTE:
The 200 OK responses to UE-originated re-REGISTER requests are excluded from the measurement.
Unit
None
Measurement Point
response (to a UE-originated VoWiFi initial REGISTER request) from the core network.
Figure 1 Measurement point of Number of ABCF VoWiFi Successful Initial Registrations
Formula
None
Related Notes
None
9.1.6.4.26 1907467813 Number of ABCF

VoWiFi Re-registration Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of UE-originated VoWiFi re-REGISTER
requests received by the A-BCF in a measurement period (5 minutes by default).
A UE can initiate reregistration by sending a new REGISTER request to the network at any
time. For example, when a registration is about to expire, a UE initiates reregistration.
Unit
None
Measurement Point
The value of this measurement entity varies in the following scenarios:

increases by one when the A-BCF receives a UE-originated VoWiFi REGISTER request
carrying a non-0 expires parameter value. For details, see point A in Figure 1.
increases by one when the A-BCF receives a UE-originated VoWiFi REGISTER request
carrying a non-0 expires parameter value before receiving or after forwarding a 401
response. The REGISTER requests are counted once. For details, see point A or B in
Figure 2.
Figure 1 Measurement point of Number of ABCF VoWiFi Re-registration Attempts (scenario 1)
Figure 2 Measurement point of Number of ABCF VoWiFi Re-registration Attempts (scenario 2)
Formula
None
Related Notes
None
9.1.6.4.27 1907467814 Number of ABCF

VoWiFi Successful Re-registrations
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of 200 OK responses (to UE-originated
VoWiFi re-REGISTER requests) received by the A-BCF in a measurement period (5
Unit
None
Measurement Point
response to a VoWiFi re-REGISTER request. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF VoWiFi Successful Re-registrations
Formula
None
Related Notes
None
9.1.6.4.28 1907467816 Number of ABCF

MO-Side VoWiFi Session Interruptions
 Description
 Unit
 Formula
 Related Notes
Description
expiration or no media stream detection on the MO-side A-BCF in the VoWiFi call service
Unit
N/A
Measurement Point
because of session timer expiration or no media stream detection on the MO-side A-BCF.
Figure 1 Measurement point of Number of A-BCF MO-Side VoWiFi Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.29 1907467817 Number of ABCF

MT-Side VoWiFi Session Interruptions
 Description
 Unit
 Formula
 Related Notes
Description
expiration or no media stream detection on the MT-side A-BCF in the VoWiFi call service
Unit
N/A
Measurement Point
because of session timer expiration or no media stream detection on the MT-side A-BCF.
Figure 1 Measurement point of Number of A-BCF MT-Side VoWiFi Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.30 1907467819 Number of ABCF

MO-Side VoWiFi Session Interruptions
Triggered by Wireless Network
 Description
 Unit
 Formula
 Related Notes
Description
the MO-side A-BCF in the VoWiFi call service in a measurement period (5 minutes by
default).
Unit
N/A
Measurement Point
interruption occurs on the MO-side A-BCF. For details, see point A in Figure 1. A video
Figure 1 Measurement point of Number of A-BCF MO-Side VoWiFi Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.31 1907467820 Number of ABCF
MT-Side VoWiFi Session Interruptions
 Description
 Unit
 Formula
 Related Notes
Description

the MT-side A-BCF in the VoWiFi call service in a measurement period (5 minutes by
default).
Unit
N/A
Measurement Point
interruption occurs on the MT-side A-BCF. For details, see point A in Figure 1. A video
Figure 1 Measurement point of Number of A-BCF MT-Side VoWiFi Session Interruptions
Formula
None
Related Notes
None
9.1.6.4.32 1907468093 Number of ABCF

MO-Side VoWiFi Session Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of INVITE requests received by the MO-side
A-BCF in the VoWiFi scenario in a measurement period (5 minutes by default).
Unit
Integer
Measurement Point
The value of this measurement entity increases by one when the MO-side A-BCF receives
an INVITE request from a VoWiFi UE. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF MO-Side VoWiFi Session Attempts
Formula
None
Related Notes
None
9.1.6.4.33 1907468094 Number of ABCF

MO-Side VoWiFi Connected Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of connected sessions on the MO-side A-BCF
in the VoWiFi scenario in a measurement period (5 minutes by default).
Unit
Integer
Measurement Point
180 (Ringing) response to an INVITE request from a VoWiFi UE. For details, see point A
in Figure 1. If multiple 180 (Ringing) responses to an INVITE request from a VoWiFi UE
are received, only the first one is counted. If no 180 response is received, the value of this
measurement entity increases by one when the MO-side A-BCF receives a 200 OK
response to the INVITE request. For details, see point B in Figure 1.
Figure 1 Measurement point of Number of ABCF MO-Side VoWiFi Connected Sessions
Formula
None
Related Notes
None
9.1.6.4.34 1907468095 Number of ABCF

MO-Side VoWiFi Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of answered sessions on the MO-side A-BCF
in a VoWiFi scenario in a measurement period (5 minutes by default).
Unit
Integer
Measurement Point
200 OK response to the INVITE request from a VoWiFi UE. For details, see point A in
Figure 1.
Figure 1 Measurement point of Number of ABCF MO-Side VoWiFi Answered Sessions
Formula
None
Related Notes
None
9.1.6.4.35 1907468105 Traffic of ABCF

MO-Side VoWiFi Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the total traffic of all VoWiFi calls that the MO-side A-
BCF answers in a measurement period (5 minutes by default).
Unit
Erlang
Measurement Point
The A-BCF calculates the total answering duration of all VoWiFi calls by summing up the
answering duration of each VoWiFi call, and then measures the value of this measurement
entity based on the total answering duration and measurement periods. For details, see
Figure 1 Measurement point for the answering duration of a VoWiFi call
Formula
Related Notes
None
9.1.6.4.36 1907468110 Number of ABCF

MT-Side VoWiFi Session Attempts
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of INVITE requests received by the MT-side
Unit
Integer
Measurement Point
The value of this measurement entity increases by one when the MT-side A-BCF receives
an INVITE request from a VoWiFi UE. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of ABCF MT-Side VoWiFi Session Attempts
Formula
None
Related Notes
None
9.1.6.4.37 1907468111 Number of ABCF

MT-Side VoWiFi Connected Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of connected sessions on the MT-side A-BCF
in the VoWiFi scenario in a measurement period (5 minutes by default).
Unit
Integer
Measurement Point
180 (Ringing) response to an INVITE request from a VoWiFi UE. For details, see point A
in Figure 1. If no 180 response is received, the value of this measurement entity increases by
one when the MT-side A-BCF receives a 200 OK response to the INVITE request
originated from a VoWiFi UE. For details, see point B in Figure 1.
Figure 1 Measurement point of Number of ABCF MT-Side VoWiFi Connected Sessions
Formula
None
Related Notes
None
9.1.6.4.38 1907468112 Number of ABCF

MT-Side VoWiFi Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity counts the number of answered sessions received by the MT-side
Unit
Integer
Measurement Point
200 OK response to an INVITE request originated from a VoWiFi UE. For details, see
point A in Figure 1.
Figure 1 Measurement point of Number of ABCF MT-Side VoWiFi Answered Sessions
Formula
None
Related Notes
None
9.1.6.4.39 1907468122 Traffic of ABCF

MT-Side VoWiFi Answered Sessions
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the total traffic of all VoWiFi calls that the MT-side A-
BCF answers in a measurement period (5 minutes by default).
Unit
Erlang
Measurement Point
The A-BCF calculates the total answering duration of all VoWiFi calls by summing up the
answering duration of each VoWiFi call, and then measures the value of this measurement
entity based on the total answering duration and measurement periods. For details, see
Figure 1 Measurement point for the answering duration of a VoWiFi call
Formula
Related Notes
None
9.1.6.4.40 1907468135 ABCF VoWiFi

Access Network IP QoS LosRate Average
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average loss rate of the RTP packets sent from IP
trunks to the SE2900 during each measurement period in IP-trunk-based QoS measurement.
This measurement entity indicates network conditions from the IP trunks to the SE2900.
Unit
Measurement Point
None
Formula
Related Notes
Table 1 Impacts on network quality based on the access network average RTP packet
loss rate

Value Range
[0%, 1%) Communications during a call are interrupted occasionally but call quality is not
loss rate

Value Range
affected.
[1%, 5%) Communications during a call are interrupted frequently but call quality is slightly
affected.
[5%, 10%) Communications during a call are interrupted significantly. Call quality is affected
but acceptable.
[10%,100%] Communications during a call are interrupted severely. Call quality is greatly

9.1.6.4.41 1907468153 ABCF VoWiFi

Access Network IP QoS Mos Average
 Description
 Unit
 Formula
 Related Notes
Description
This measurement entity measures the average MOS value obtained by the SE2900 during
each measurement period in IP-trunk-based QoS measurement. This measurement entity
indicates network conditions from the IP trunks to the SE2900.
Unit
none
Measurement Point
The MOS value at each measurement point is collected and accumulated. At the end of the
measurement period, the accumulated value is divided by the number of collected MOS
values to obtain the average MOS value.
Formula
ABCF VoWiFi Access Network IP QoS Mos Average = Accumulated MOS value on the
access-side A-BCF in the VoWiFi scenario in a measurement period/Number of MOS
values collected on the access-side A-BCF in the VoWiFi scenario in a measurement period
Related Notes
loss rate

Value Range
[0.0, 3.0) Communications during a call are interrupted severely. Call quality is greatly
[3.0, 3.5) Communications during a call are interrupted significantly. Call quality is affected
but acceptable.
[3.5, 4.0) Communications during a call are interrupted frequently but call quality is slightly
affected.
[4.0, 5.0) Communications during a call are interrupted occasionally but call quality is not
affected.

< Previous topic
9.1.6.5 MSOFTX3000
84164965 Number of Requested 2G Intra-MSC eSRVCC Handovers
84164967 Number of Requested 2G Inter-MSC eSRVCC Handovers
84164975 Number of Requested 3G Intra-MSC eSRVCC Handovers
84164977 Number of Requested 3G Inter-MSC eSRVCC Handovers
84175689 Number of 2G eSRVCC Service Alerting Request
84175691 Number of 3G eSRVCC Service Alerting Request
84176435 Number of 2G eSRVCC Service Pre-Alerting Request Times
84176438 Number of 3G eSRVCC Service Pre-Alerting Request Times
84176698 Number of Successful Times During 2G eSRVCC Handovers
84176700 Number of Successful Times During 3G eSRVCC Handovers
< Previous topic
9.1.6.5.1 84164965 Number of Requested

2G Intra-MSC eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of SRVCC PS to CS Request messages sent
from a mobility management entity (MME) to the single radio voice call continuity
(SRVCC) interworking function (IWF) when subscribers are being handed over from a
Long Term Evolution (LTE) network to a circuit switched (CS) network and the target cell
is in the coverage of the SRVCC IWF. The SRVCC IWF is implemented by a mobile
switching center (MSC) server.
Create a measurement task with this measurement entity when you need to learn the
number of times handover from an LTE network to a CS cell in the coverage of the
SRVCC IWF is requested during calls.
Unit
Integer
Measurement Point
The value of this measurement entity increases by 1 when the SRVCC IWF receives an
SRVCC PS to CS Request message from an MME and determines that the target cell is in
its coverage. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of Requested 2G Intra-MSC eSRVCC Handovers
Formula
None
Reference
None
Parent Topic: MSOFTX3000

Next topic >

2G Inter-MSC eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
Long Term Evolution (LTE) network to a circuit switched (CS) network and the target cell
is in the coverage of an adjacent mobile switching center (MSC) server. The SRVCC IWF
is implemented by an MSC server.
number of times handover from an LTE network to a CS cell in the coverage of an adjacent
MSC server is requested during calls.
Unit
Integer
Measurement Point
SRVCC PS to CS Request message from an MME and determines that the target cell is in
the coverage of an adjacent MSC server. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of Requested 2G Inter-MSC eSRVCC Handovers
Formula
None
Reference
None


3G Intra-MSC eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
Long Term Evolution (LTE) network to a circuit switched (CS) network and the target
radio network controller (RNC) is in the coverage of the SRVCC IWF. The SRVCC IWF is
implemented by a mobile switching center (MSC) server.
number of times handover from an LTE network to a CS RNC in the coverage of the
SRVCC IWF is requested during calls.
Unit
Integer
Measurement Point
SRVCC PS to CS Request message from an MME and determines that the target RNC is in
its coverage. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of Requested 3G Intra-MSC eSRVCC Handovers
Formula
None.
Reference
None


3G Inter-MSC eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
Long Term Evolution (LTE) network to a circuit switched (CS) network and the target
radio network controller (RNC) is in the coverage of an adjacent mobile switching center
(MSC) server. The SRVCC IWF is implemented by an MSC server.
number of times handover from an LTE network to a CS RNC in the coverage of an
adjacent MSC server is requested during calls.
Unit
Integer
Measurement Point
SRVCC PS to CS Request message from an MME and determines that the target RNC is in
the coverage of an adjacent MSC server. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of Requested 3G Inter-MSC eSRVCC Handovers
Formula
None
Reference
None

9.1.6.5.5 84175689 Number of 2G eSRVCC

Service Alerting Request
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of eSRVCC handover requests for Alerting-
Call sessions to be handed over to a 2G network.
When you need to obtain the number of eSRVCC handover requests for Alerting-Call
sessions in the following scenarios, you can create a measurement task with this
measurement entity:
 A subscriber, who is on an Alerting-Call on an LTE network, roams to a 2G network.
The SRVCC IWF initiates an initial session transfer (IST) procedure to the IMS to hand
over the Alerting-Call.
 A subscriber, who is on an active or held call as well as an Alerting-Call on an LTE
network, roams to a 2G network. After handing over the active or held call of the
subscriber, the SRVCC IWF initiates an IST procedure to the IMS to hand over the
Alerting-Call.
Unit
Integer
Measurement Point
 An Alerting-Call of a subscriber is to be handed over to a 2G network. The value of this

measurement entity increases by one when the SRVCC IWF receives an INFO message
from the IMS, indicating that the call is an Alerting-Call session. For details, see point A
in Figure 1.
Figure 1 Measurement point of Number of 2G eSRVCC Service Alerting Request when a
subscriber has only an Alerting-Call
 The SRVCC IWF hands over the Alerting-Call after the active or held call has been
handed over to a 2G network. The value of this measurement entity increases by one
when the SRVCC IWF receives an REFER message from the IMS, indicating that the
Alerting-Call is to be handed over. For details, see point A in Figure 2.
subscriber has an active or held call and an Alerting-Call
Formula
None
Reference
None

Service Alerting Request
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of eSRVCC handover requests for Alerting-
Call sessions to be handed over to a 3G network.
When you need to obtain the number of eSRVCC handover requests for Alerting-Call
sessions in the following scenarios, you can create a measurement task with this
measurement entity:
 A subscriber, who is on an Alerting-Call on an LTE network, roams to a 3G network.
The SRVCC IWF initiates an initial session transfer (IST) procedure to the IMS to hand
over the Alerting-Call.
 A subscriber, who is on an active or held call as well as an Alerting-Call on an LTE
network, roams to a 3G network. After handing over the active or held call of the
subscriber, the SRVCC IWF initiates an IST procedure to the IMS to hand over the
Alerting-Call.
Unit
Integer
Measurement Point
 An Alerting-Call of a subscriber is to be handed over to a 3G network. The value of this

measurement entity increases by one when the SRVCC IWF receives an INFO message
from the IMS, indicating that the call is an Alerting-Call session. For details, see point A
in Figure 1.
subscriber has only an Alerting-Call
 The SRVCC IWF hands over the Alerting-Call after the active or held call has been
handed over to a 3G network. The value of this measurement entity increases by one
when the SRVCC IWF receives an REFER message from the IMS, indicating that the
Alerting-Call is to be handed over. For details, see point A in Figure 2.
subscriber has an active or held call and an Alerting-Call
Formula
None
Reference
None

Service Pre-Alerting Request Times
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of requests for enhanced single radio voice call
continuity (eSRVCC) handovers to 2G networks during Pre-Alerting call sessions.
Unit
Integer
Measurement Point
After a calling party who is on an Originating Pre-Alerting call session roams from a 4G
network to a 2G network, the SRVCC interworking function (IWF) triggers an eSRVCC
handover and sends an INVITE message, instructing the IMS network to update the remote
leg information. The IMS network sends 183 and INFO messages to the SRVCC IWF. The
INFO message contains the XML body, indicating that the call is in the Originating Pre-
Alerting state. The value of this measurement entity is incremented by 1 after the SRVCC
IWF receives the INFO message from the IMS network. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of 2G eSRVCC Service Pre-Alerting Request Times
Formula
None
Reference
None


Service Pre-Alerting Request Times
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of requests for enhanced single radio voice call
continuity (eSRVCC) handovers to 3G networks during Pre-Alerting call sessions.
Unit
Integer
Measurement Point
After a calling party who is on an Originating Pre-Alerting call session roams from a 4G
network to a 3G network, the SRVCC interworking function (IWF) triggers an eSRVCC
handover and sends an INVITE message, instructing the IMS network to update the remote
leg information. The IMS network sends 183 and INFO messages to the SRVCC IWF. The
INFO message contains the XML body, indicating that the call is in the Originating Pre-
Alerting state. The value of this measurement entity is incremented by 1 after the SRVCC
IWF receives the INFO message from the IMS network. For details, see point A in Figure 1.
Figure 1 Measurement point of Number of 3G eSRVCC Service Pre-Alerting Request Times
Formula
None
Reference
None

9.1.6.5.9 84176698 Number of Successful

Times During 2G eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of enhanced single radio voice call continuity
(eSRVCC) handovers to a target base station controller (BSC) during which radio
handovers are successful and initial session transfer (IST) flows are complete. This
measurement entity applies to the handover of a call in either Active state or Mid-call state
only.
NOTE:
 When bit 1 of P1053 is set to 0, the SRVCC IWF uses this entity to collect statistics about eSRVCC
handovers during alerting call sessions. Bit 3 of P1053 determines when the SRVCC IWF starts the
measurement.
handovers during call sessions that are in the originating pre-alerting state.
successful 2G eSRVCC handover times.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by one immediately after both of the
following conditions are met:
 The radio handover succeeds, that is, the SRVCC interworking function (IWF) sends an
SRVCC PS to CS Complete Notification message to the mobility management entity
(MME).
 The IST flow is complete, that is, the eSRVCC receives a 200 OK message from the
IMS.
Figure 1 Measurement point of Number of Successful Times During 2G eSRVCC Handovers
Formula
None
Reference
The MSC server functioning as an SRVCC IWF increments the value of this entity for an
eSRVCC handover if both of the following conditions are met:
 Bit 4 of P1030 is set to 0.
 The MSC server receives a 410 message in which the Q.850 release cause code
contained in the Reason header field is 41 from the IMS domain during the IST flow in
the eSRVCC handover.

9.1.6.5.10 84176700 Number of Successful

Times During 3G eSRVCC Handovers
 Description
 Unit
 Formula
 Reference
Description
This measurement entity counts the number of enhanced single radio voice call continuity
(eSRVCC) handovers to a target radio network controller (RNC) during which radio
handovers are successful and initial session transfer (IST) flows are complete. This
measurement entity applies to the handover of a call in either Active state or Mid-call state
only.
NOTE:
handovers during alerting call sessions. Bit 3 of P1053 determines when the SRVCC IWF starts the
measurement.
handovers during call sessions that are in the originating pre-alerting state.
successful 3G eSRVCC handover times.
Unit
Integer
Measurement Point
The value of this measurement entity is incremented by one immediately after both of the
following conditions are met:
 The radio handover succeeds, that is, the SRVCC interworking function (IWF) sends an
SRVCC PS to CS Complete Notification message to the mobility management entity
(MME).
 The IST flow is complete, that is, the eSRVCC receives a 200 OK message from the
IMS.
Figure 1 Measurement point of Number of Successful Times During 3G eSRVCC Handovers
Formula
None
Reference
The MSC server functioning as an SRVCC IWF increments the value of this entity for an
eSRVCC handover if both of the following conditions are met:
 Bit 4 of P1030 is set to 0.
 The MSC server receives a 410 message in which the Q.850 release cause code
contained in the Reason header field is 41 from the IMS domain during the IST flow in
the eSRVCC handover.

< Previous topic

VoLTE Product Documentation (NFV) V500R018C00

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

VoLTE Product Documentation (NFV) V500R018C00

Загружено:

Авторское право:

Доступные форматы

KPI

Parent Topic: User Manuals

9.1.1 VoLTE Network KPIs

Table 1 describes KPIs supported in VoLTE V500R018C00.

Table 1 VoLTE Network KPIs

Service Registration Number of 352324100 Number Provisioning IMS-HSS VoLTE

Number of 335672421 Number S-CSCF S-CSCF VoLTE

Number of 1907465358 Number ABCF Access ABCF VoLTE

Number of 1907466549 Number ABCF Access ABCF VoLTE

Number of 478155988 Number ATS CPU ATS VoBB

Number of 478156521 Number ATS Register IM-SSF VoLTE

Initial  335655491 S-CSCF S-CSCF VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

on an LTE Initial Network

Category Sub- KPI Basic Measurement Measurement NE Applicable

VoWiFi Users Measurem (ATS990 networks

Session Session  Single-session  Single-  Single- VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

Session Session (SE2900)

Category Sub- KPI Basic Measurement Measurement NE Applicable

MO Session  335655576  S-CSCF S-CSCF VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

Category Sub- KPI Basic Measurement Measurement NE Applicable

Category Sub- KPI Basic Measurement Measurement NE Applicable

MO-Side VoWiFi Related VoWiFi

Service Handover Success Rate  84164965 2G eSRVCC GTP Peer VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

eSRVCC Requested 3G Measurement

Category Sub- KPI Basic Measurement Measurement NE Applicable

Category Sub- KPI Basic Measurement Measurement NE Applicable

Category Sub- KPI Basic Measurement Measurement NE Applicable

Voice Quality  Drive test ABCF Access  Drive test VoLTE

Voice Quality  Drive test ABCF  Drive test VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

Traffic of  1907468105 ABCF ABCF VoLTE

Average Average 1907466105 Mean ABCF ABCF VoLTE

Service VoLTE  1907466045 ABCF ABCF VoLTE

Category Sub- KPI Basic Measurement Measurement NE Applicable

registration Attempts Unrelated

Category Sub- KPI Basic Measurement Measurement NE Applicable

Registration Number of ABCF Session (SE2900) and

Parent Topic: KPI

9.1.2 Service Accessibility KPIs

Parent Topic: KPI

Parent Topic: Service Accessibility KPIs

9.1.2.1.1 Number of Defined Subscribers

 Reference Value Range

Reference Value Range

9.1.2.1.2 Number of Registered

 Reference Value Range

Reference Value Range

9.1.2.1.3 Number of Registered VoLTE

 Reference Value Range

Reference Value Range

9.1.2.1.4 Number of VoLTE Roaming

 Reference Value Range

Reference Value Range

9.1.2.1.5 Number of Registered VoBB

 Reference Value Range

Reference Value Range

9.1.2.1.6 Number of Registered IN

 Reference Value Range

Reference Value Range

9.1.2.1.7 Initial Registration Success Rate