01-02 MSC Basic Functions

HUAWEI MSOFTX3000 Performance Metrics Reference Contents

Issue 09 (2007-05-20) Huawei Technologies Proprietary i

Contents

2 MSC Basic Functions.................................................................................................................2-1 2.1 Overview of Measurement Set ......................................................................................................................2-2 2.2 MSC Basic Table...........................................................................................................................................2-2

2.2.1 Overview of MS_BASIC_TABLE_TRAF ..........................................................................................2-2 2.2.2 Count of Level Updates .......................................................................................................................2-3 2.2.3 Count of Ciphering Mode Setting Requests.........................................................................................2-4 2.2.4 Count of Ciphering Mode Setting Successes .......................................................................................2-5 2.2.5 Count of Routing Information Requests ..............................................................................................2-7 2.2.6 Count of Successes in Receiving Roaming Numbers ..........................................................................2-7 2.2.7 Count of Successes in Receiving Forwarded-to Numbers ...................................................................2-8 2.2.8 Count of Sent MO Short Messages......................................................................................................2-9 2.2.9 Count of Successful MO Short Messages (Sent) ...............................................................................2-10 2.2.10 Count of Received MT Short Messages...........................................................................................2-12 2.2.11 Count of Successful MT Short Messages (Received) ......................................................................2-12 2.2.12 Count of Use of TMSI at MM Layer ...............................................................................................2-13 2.2.13 Count of Use of IMSI at MM Layer ................................................................................................2-22 2.2.14 Count of TMSI Reallocation Requests.............................................................................................2-32 2.2.15 Count of TMSI Reallocation Successes ...........................................................................................2-34 2.2.16 Count of IMSI Detachments ............................................................................................................2-36 2.2.17 Count of IMSI Attachments .............................................................................................................2-38 2.2.18 Count of Pagings..............................................................................................................................2-39 2.2.19 Count of Paging Responses..............................................................................................................2-40 2.2.20 Count of SOR Basic Call Requests..................................................................................................2-41 2.2.21 Count of Successes of Basic SOR Call ............................................................................................2-42 2.2.22 Count of SOR Early Forward Call Requests....................................................................................2-43 2.2.23 Count of Successes of SOR Early Forward Call..............................................................................2-44 2.2.24 Count of SOR Late Forward Call Requests .....................................................................................2-45 2.2.25 Count of Successes of SOR Late Forward Call ...............................................................................2-46 2.2.26 Count of SOR Requests for Routing................................................................................................2-47 2.2.27 Count of SOR Requests for MSRN .................................................................................................2-48 2.2.28 Count of Receiving MSRN During SOR Routing ...........................................................................2-49 2.2.29 Count of Successes of SOR for MSRN............................................................................................2-50

Contents HUAWEI MSOFTX3000

Performance Metrics Reference

ii Huawei Technologies Proprietary Issue 09 (2007-05-20)

2.3 Authentication .............................................................................................................................................2-51 2.3.1 Overview of MS_TYPE_AUTH........................................................................................................2-51 2.3.2 Count of Authentication Set Requests to HLR...................................................................................2-52 2.3.3 Count of Authentication Set Receipts from HLR...............................................................................2-52 2.3.4 Count of Empty Authentication Set Receipts from HLR ...................................................................2-53 2.3.5 Count of Authentication Set Requests to PVLR ................................................................................2-54 2.3.6 Count of Authentication Set Receipts from PVLR ............................................................................2-55 2.3.7 Count of Authentication Requests......................................................................................................2-55 2.3.8 Count of Successful Authentications .................................................................................................2-56 2.3.9 Count of Authentication Failures Due to Illegal SRES......................................................................2-57 2.3.10 Count of Authentication Requests with TMSI .................................................................................2-58 2.3.11 Count of Authentication Failures Due to Illegal SRES (with TMSI) ...............................................2-58 2.3.12 Count of Successful Authentications After IMSI Being Identified ..................................................2-59 2.3.13 Count of Failures in Responding to Authentication Requests..........................................................2-60 2.3.14 Count of Failure Responses to Authenication Requests...................................................................2-61

2.4 Location Update ..........................................................................................................................................2-62 2.4.1 Overview of MS_TYPE_LOC_UP....................................................................................................2-62 2.4.2 Count of Location Update Requests ..................................................................................................2-63 2.4.3 Count of Location Update Rejections ................................................................................................2-63 2.4.4 Count of IMSI Detachments ..............................................................................................................2-64 2.4.5 Count of IMSI Attachments ...............................................................................................................2-64 2.4.6 Count of Location Update Requests in VLR......................................................................................2-65 2.4.7 Count of Location Update Successes in VLR....................................................................................2-66 2.4.8 Count of Location Update Requests Due to Subsriber Roaming .......................................................2-67 2.4.9 Count of Location Update Successes Due to Subsriber Roaming .....................................................2-67 2.4.10 Count of Location Update Successes Due to National Roaming .....................................................2-68 2.4.11 Count of Location Update Successes Due to International Roaming............................................2-69 2.4.12 Count of Location Update Failures Due to Unknown User in HLR ................................................2-69 2.4.13 Count of Location Update Failures Due to Illegal MS ....................................................................2-70 2.4.14 Count of Location Update Failures Due to IMEI Check Failure .....................................................2-71 2.4.15 Count of Location Update Failures Due to PLMN Denying Access................................................2-71 2.4.16 Count of Location Update Failures Due to Prohibition of Location Area........................................2-72 2.4.17 Count of Location Update Failures Due to Roaming Prohibition....................................................2-73 2.4.18 Count of Location Update Failures Due to Protocol Failure............................................................2-73 2.4.19 Count of Location Update Failures Due to Network Failure ...........................................................2-74 2.4.20 Count of Location Update Failures Due to Prohibition of Location Area in PLMN........................2-75 2.4.21 Count of Location Update Failures Due to Prohibition of Location Area Cell ................................2-75 2.4.22 Count of Location Update Failures Due to Other Causes ................................................................2-76 2.4.23 Count of Attempts to Insert User Data .............................................................................................2-77 2.4.24 Count of Sucesses in Inserting User Data ........................................................................................2-78 2.4.25 Count of Location Update Failures Due to ARD .............................................................................2-78

HUAWEI MSOFTX3000 Performance Metrics Reference 2 MSC Basic Functions

Issue 09 (2007-05-20) Huawei Technologies Proprietary 2-1

2 MSC Basic Functions

About This Chapter

The following table lists the contents of this chapter.

Section Describes

2.1 Overview of Measurement Set

This section introduces the measurement set of the MSC mobility management.

2.2 MSC Basic Table This section introduces measurement metrics contained in the MSC basic table measurement.

2.3 Authentication This section introduces measurement metrics contained in authentication measurement.

2.4 Location Update This section introduces measurement metrics contained in location update measurement.

2 MSC Basic Functions HUAWEI MSOFTX3000


2-2 Huawei Technologies Proprietary Issue 09 (2007-05-20)

2.1 Overview of Measurement Set The measurement set is used to measure the MSC mobility management, such as authentication and location management.

The measurement units are listed in the following table.

Name Description

MS_BASIC_TABLE_TRAF MSC basic table

MS_TYPE_AUTH Authentication

MS_TYPE_LOC_UP Location update

2.2 MSC Basic Table 2.2.1 Overview of MS_BASIC_TABLE_TRAF

The names and meanings of the measurement metrics are listed in the following table.

Name Description

NCU134 Count of level updates

ACMCP134 Count of ciphering mode setting requests

SCMCP134 Count of ciphering mode setting successes

AIHLRR134 Count of routing information requests

SIHLR134 Count of successes in receiving roaming numbers

SIHLRC134 Count of successes in receiving forwarded-to numbers

AOMOPP134 Count of sent MO short messages

SOMOPP134 Count of successful MO short messages (sent)

AOMTPP134 Count of received MT short messages

SOMTPP134 Count of successful MT short messages (received)

TMMSIT134 Count of use of TMSI at MM layer

TMMSII134 Count of use of IMSI at MM layer

ATRA134 Count of TMSI reallocation requests

STRA134 Count of TMSI reallocation successes

IDP134 Count of IMSI detachments



Name Description

IAP134 Count of IMSI attachments

PG134 Count of pagings

PGRSP134 Count of paging responses

SORBQ Count of SOR basic call requests

SORBS Count of successes of SOR basic call

SOREFQ Count of SOR early forward call requests

SOREFS Count of successes of SOR early forward call

SORLFQ Count of SOR late forward call requests

SORLFS Count of successes of SOR late forward call

ISR134 Count of SOR requests for routing

AMSR134 Count of SOR requests for MSRN

ISM134 Count of receiving MSRN during SOR routing

AMSS134 Count of successes of SOR for MSRN

2.2.2 Count of Level Updates

Metrics Name NCU134

Description It is the count of level updates initiated by MSs or the count of queries on MS level by the MSC in the dedicated mode.

Measurement Point It is measured when the MSC receives the message BSSMAP CLASSMARK_UPDATE from the BSC. See point A in the following figure.




BSSMAPCLASSMARK_UPDATE

BSC MSC Server

A

Formula None

2.2.3 Count of Ciphering Mode Setting Requests

Metrics Name ACMCP134

Description It is the count of ciphering procedures enabled by the MSC/VLR.

Measurement Point It is measured when the MSC sends the message RN_SECURITY_MODE_COMMAND or Cipher_Mode_Command. See point A in the following figure.

In 2G networks:



LOCATION_UPD_REQ/CM_Service_Request

BSC MSC Server

A

Cipher_Mode_Command

In 3G networks:

RN_MM_LOCATION_UPDATION_REQUEST/

RN_MM_CM_SERVICE_REQUEST

RNC MSC Server

ARN_SECURITY_MODE_COMMAND

Formula None

2.2.4 Count of Ciphering Mode Setting Successes

Metrics Name SCMCP134




Description It is the count of successes in implementing the ciphering procedures enabled by the MSC/VLR.

Measurement Point It is measured when the MSC receives the message SECURITY_MODE_COMPLETE or Cipher_Mode_Complete. See point A in the following figure.

In 2G networks:

Cipher_Mode_Complete

BSC MSC Server

ARelease/CM_Service_Accept

In 3G networks:

SECURITY_MODE_COMPLETE

RNC MSC Server

AIU_RELEASE_COMMAND/RN_MM_CM_SERVICE_A

CCEPT



Formula None

2.2.5 Count of Routing Information Requests

Metrics Name AIHLRR134

Description It is the count of routing information requests sent by the MSC to the HLR.

Measurement Point It is measured when the MSC sends the message SEND_ROUTING_INFORMATION_REQ to the HLR. See point A in the following figure.

MSC Server

A

HLR

SEND_ROUTING_INFORMATION_RSP

SEND_ROUTING_INFORMATION_REQ

B

Formula None

2.2.6 Count of Successes in Receiving Roaming Numbers

Metrics Name SIHLR134

Description It is the count of receipts of MSRNs from the HLR after the MSC sends the message SEND_ROUTING_INFORMATION_REQ.




Measurement Point It is measured when the MSC receives the message SEND_ROUTING_INFORMATION_RSP (including MSRN) from the HLR. See point B in the following figure.

MSC Server

A

HLR



B

Formula None

2.2.7 Count of Successes in Receiving Forwarded-to Numbers

Metrics Name SIHLRC134

Description It is the count of receipts of forwarded-to numbers from the HLR after the MSC sends the message SEND_ROUTING_INFORMATION_REQ.

Measurement Point It is measured when the MSC receives the message SEND_ROUTING_INFORMATION_RSP (including the forwarded-to number) from the HLR. See point B in the following figure.



MSC Server

A

HLR



B

Formula None

2.2.8 Count of Sent MO Short Messages

Metrics Name AOMOPP134

Description It is the count of short messages originated by mobile callers.

Measurement Point It is measured when the MSC receives the message CM_SERVICE_REQUEST, and confirms that the service type is short message service. See point A in the following figure.




RNC MSC Server

A

SMC

B

CM_SERVICE_REQUEST

Authentication/Ciphering

CP_DATA

CP_ACK

MO_FORWARD_SM_REQ

MO_FORWARD_SM_RSP

CP_DATA

CP_ACK

Formula None

2.2.9 Count of Successful MO Short Messages (Sent)

Metrics Name SOMOPP134

Description It is the count of successful short messages originated by mobile callers.

Measurement Point It is measured when the MSC receives the message MO_FORWARD_SM_RSP from the

IWMSC, and sends the message CP_DATA to a mobile caller. See point B in the following figure.



RNC MSC Server

A

SMC

B

CM_SERVICE_REQUEST


CP_DATA

CP_ACK

MO_FORWARD_SM_REQ

MO_FORWARD_SM_RSP

CP_DATA

CP_ACK

It is measured when the MSC sends the message READY_FORSM_REQ to the HLR, and receives the correct message READY_FORSM_RSP. See point B in the following figure.

RNC MSC Serv er

A

HLR

B

CM_SERVICE_REQUEST


CP_DATA

CP_ACK

READY_FORSM_REQ

READY_FORSM_RSP

CP_DATA

CP_ACK




Formula None

2.2.10 Count of Received MT Short Messages

Metrics Name AOMTPP134

Description It is the count of short messages received by mobile terminating callees.

Measurement Point It is measured when the MSC sends the message CP_DATA to a mobile terminating callee. See point A in the following figure.

RNC MSC Server

A

SMC

B

CP_DATA

CP_ACK

MT_FORWARD_SM_RSP

CP_DATA

CP_ACK

Access of paging

MT_FORWARD_SM_IND

Formula None

2.2.11 Count of Successful MT Short Messages (Received)

Metrics Name SOMTPP134



Description It is the count of successful short messages received by mobile terminating callees.

Measurement Point It is measured when the MSC receives the message CP_ACK returned from a mobile terminating callee. See point B in the following figure.

Formula None

2.2.12 Count of Use of TMSI at MM Layer

Metrics Name TMMSIT134

Description It is the count of TMSIs used in transaction processing at the MM layer.

Measurement Point The monitored service flows include:

CM_Re-Establishment CM_Service Request Identity Response IMSI detach Indication Location Update Accept Location updating request TMSI re-allocation command PAGING RESPONSE

See point A in the following figures.

CM_Re-Establishment

In 2G networks:




CM_Reestablishment_Request

BSC MSC Server

A

Assignment_Request

In 3G networks:

RN_MM_CM_RE_ESATABLISHMENT_REQUEST

RNC MSC Server

ARAB_ASSIGNMENT_REQUE

ST

CM_Service Request

In 2G networks:



CM_Service_Request

BSC MSC Server

A

Authentication_Request

In 3G networks:


RNC MSC Server

ARN_MM_AUTHENTICATION

_REQUEST

Identity Response

In 2G networks:




Identity_Response

BSC MSC Server

ALocation_Updating_Ac

cept

In 3G networks:

RN_MM_IDENTITY_RESPONSE

RNC MSC Server

ARN_MM_LOCATION_UPDATI

NG_ACCEPT

IMSI detach Indication

In 2G networks:



Imsi_Detach_Indication

BSC MSC Server

A

Clear_Command

In 3G networks:

RN_MM_IMSI_DETACH_INDICATION

RNC MSC Server

A

IU_RELEASE_COMMAND

Location updating request

In 2G networks:




Location_Updating_Request

BSC MSC Server

A


In 3G networks:

RN_MM_LOCATION_UPDATION_REQUEST

RNC MSC Server

ARN_MM_AUTHENTICATION_

REQUEST

TMSI re-allocation command

In 2G networks:



CM_Service_Request

BSC MSC Server

ATmsi_Reallocation_Command

Tmsi_Reallocation_Complete

In 3G networks:


RNC MSC Server

ARN_MM_TMSI_REALLOCATI

ON_COMMAND

RN_MM_TMSI_REALLOCATION_COMPLETE


In 2G networks:





BSC MSC Server

ALocation_Updating_Accept


In 3G networks:


RNC MSC Server


NG_ACCEPT


PAGING RESPONSE

In 2G networks:



Paging_Response

BSC MSC Server

A

Classmark_Request

In 3G networks:

RN_RR_PAGING_RESPONSE

RNC MSC Server


REQUEST


In 2G networks:





BSC MSC Server

ARelease/

CM_Service_Accept

In 3G networks:

RN_MM_SECURITY_MODE_COMPLETE

RNC MSC Server

AIU_RELEASE_REQUEST/RN_MM_CM_SERVICE_ACC

EPT

Formula None

2.2.13 Count of Use of IMSI at MM Layer

Metrics Name TMMSII134

Description It is the count of IMSIs used in transaction processing at the MM layer.



Measurement Point The monitored service flows include:

CM_Re-Establishment CM_Service Request Identity Response IMSI detach Indication Location Update Accept Location updating request TMSI re-allocation command PAGING RESPONSE

See point A in the following figures.

CM_Re-Establishment

In 2G networks:

CM_Reestablishment_Request

BSC MSC Server

A

Assignment_Request

In 3G networks:




RN_MM_CM_RE_ESATABLISHMENT_REQUEST

RNC MSC Server

ARAB_ASSIGNMENT_REQUE

ST

CM_Service Request

In 2G networks:

CM_Service_Request

BSC MSC Server

A


In 3G networks:




RNC MSC Server

ARN_MM_AUTHENTICATION

_REQUEST

Identity Response

In 2G networks:

Identity_Response

BSC MSC Server


cept

In 3G networks:




RN_MM_IDENTITY_RESPONSE

RNC MSC Server


NG_ACCEPT

IMSI detach Indication

In 2G networks:


BSC MSC Server

A

Clear_Command

In 3G networks:




RNC MSC Server

A

IU_RELEASE_COMMAND

Location updating request

In 2G networks:


BSC MSC Server

A


In 3G networks:





RNC MSC Server


REQUEST


In 2G networks:

CM_Service_Request

BSC MSC Server

ATmsi_Reallocation_Command


In 3G networks:




RNC MSC Server

ARN_MM_TMSI_REALLOCATI

ON_COMMAND




BSC MSC Server

ALocation_Updating_Accept


In 3G networks:





RNC MSC Server


NG_ACCEPT


PAGING RESPONSE

In 2G networks:

Paging_Response

BSC MSC Server

A

Classmark_Request

In 3G networks:



RN_RR_PAGING_RESPONSE

RNC MSC Server


REQUEST


In 2G networks:


BSC MSC Server

ARelease/

CM_Service_Accept

In 3G networks:




RN_MM_SECURITY_MODE_COMPLETE

RNC MSC Server

AIU_RELEASE_REQUEST/RN_MM_CM_SERVICE_ACC

EPT

Formula None

2.2.14 Count of TMSI Reallocation Requests

Metrics Name ATRA134

Description It is the count of requests for TMSI reallocation initiated in the MM common procedure.

Measurement Point It is measured when the MSC sends the message Location_Updating_Accept to the MS,

that is, the location update procedure contains TMSI reallocation. See point A in the following figures.

In 2G networks:




BSC MSC Server


cept


In 3G networks:

RN_MM_LOCATION_UPDATION_REQUES

T

RNC MSC Server

ARN_MM_LOCATION_UPDATING_ACCEPT

RN_MM_TMSI_REALLOCATION_COMPLE

TE

It is measured when the MSC sends the message Tmsi_Reallocation_Command to the MS. See point A in the following figures.

In 2G networks:




CM_Service_Request

BSC MSC Server

A

Tmsi_Reallocation_Command


In 3G networks:


RNC MSC Server

A

RN_MM_TMSI_REALLOCATION_COMMA

ND


TE

Formula None

2.2.15 Count of TMSI Reallocation Successes

Metrics Name STRA134

Description It is the count of successful TMSI reallocations initiated in the MM common procedure.



Measurement Point It is measured when the MSC receives the message Tmsi_Reallocation_Complete from the MS. See point A in the following figures.

During a location update

In 2G networks:


BSC MSC Server

A

Release

In 3G networks:


TE

RNC MSC Server

AIU_RELEASE_COMMAND

During a service request

In 2G networks:





BSC MSC Server

ACM_Service_Accept

In 3G networks:


TE

RNC MSC Server

ARN_MM_CM_SERVICE_ACCEPT

Formula None

2.2.16 Count of IMSI Detachments

Metrics Name IDP134

Description It is the count of IMSI detachments due to power-off.



Measurement Point It is measured when the MSC receives the message IMSI DETACH IND from the MS. See point A in the following figures.

In 2G networks:


BSC MSC Server

A

Release

In 3G networks:

RNC MSC Server

A

IU_RELEASE_COMMAND


Formula None




2.2.17 Count of IMSI Attachments

Metrics Name IAP134

Description It is the count of IMSI attachments due to power-on, SIM card insertion, and access to service coverage areas.

Measurement Point It is measured when the MSC receives from the MS the message LOCATION_UPDATE_REQUEST, which indicates the IMSI is activated (IMSI_ATTACH_UPDATE). See point A in the following figures.

In 2G networks:


BSC MSC Server

A


In 3G networks:



RNC MSC Server

ARN_MM_AUTHENTICATI

ON_REQUEST


Formula None

2.2.18 Count of Pagings

Metrics Name PG134

Description It is the count of pagings sent from the MSC, and it is measured once for multiple pagings of a call.

Measurement Point It is measured when the MSC sends the PAGING message. See point A in the following figure.




PAGING

RNS MSC Server

APAGING

……

PAGING RESPONSE

Formula None

2.2.19 Count of Paging Responses

Metrics Name PGRSP134

Description It is the count of PAGING RESPONSE messages received by the MSC from callees after the MSC sends the PAGING message.

Measurement Point It is measured when the MSC receives the message Paging Response. See point A in the following figure.



RNS MSC Server

A

PAGING

PAGING RESPONSE

AUTHENTICATION REQUEST

Formula None

2.2.20 Count of SOR Basic Call Requests

Metrics Name SORBQ

Description It is the count of roaming queries during basic SOR calls.

Measurement Point It is measured when the GMSCA initiates the SOR queries. See point A in the following figure.




GMSCA HLRB

SRIA

Formula None

2.2.21 Count of Successes of Basic SOR Call

Metrics Name SORBS

Description It is the count of successful basic SOR calls.

Measurement Point It is measured when MSRN is returned and the outgoing call is made during the SOR query in the GMSCA. See point A in the following figure.



GMSCA HLRB

SRI ack

A

VMSCB

IAM

Formula None

2.2.22 Count of SOR Early Forward Call Requests

Metrics Name SOREFQ

Description It is the count of requests for SOR early forwarded calls.

Measurement Point It is measured in course of supplementary service call forwarding or call forwarding controlled by SCP during the SOR query in the GMSCA. See point A in the following figure.




GMSCA HLRB

SRIA

Formula None

2.2.23 Count of Successes of SOR Early Forward Call

Metrics Name SOREFS

Description It is the count of successes in the early forwarded call.

Measurement Point It is measured when the supplementary service or the IN call is forwarded on the condition that they satisfy the early forward charging principle during the SOR query in the GMSCA. See point A in the following figure.



GMSCA HLRB

SRI ack(FTN)

A

LEC

IAM

Formula None

2.2.24 Count of SOR Late Forward Call Requests

Metrics Name SORLFQ

Description It is the count of SOR requests for late forwarded calls.

Measurement Point It is measured when the GMSCA receives resume call handling (RCH) requests from the VMSCB. See point A in the following figure.




GMSCA VMSCB

RCH

A

Formula None

2.2.25 Count of Successes of SOR Late Forward Call

Metrics Name SORLFS

Description It is the successes in the late forwarded call.

Measurement Point It is measured when the GMSCA returns the message RCH ACK to the VMSCB after receiving the RCH request from the VMSCB and ensuring that the SOR late forwarded conditions are satisfied. See point A in the following figure.



GMSCA VMSCB

RCH

A

RCH ACK

Formula None

2.2.26 Count of SOR Requests for Routing

Metrics Name ISR134

Description It is the count of SOR requests for routing.

Measurement Point It is measured if the optimal routing (OR) indication is TRUE when the MSC sends the routing request. See point A in the following figure.




A

D

C

B

PRN Req

PRN Rsp

SRI Req

With OR flag bit

SRI Rsp

HLR VLRGMSC

With OR flag bit

Formula None

2.2.27 Count of SOR Requests for MSRN

Metrics Name AMSR134

Description It is the count of SOR requests for MSRN.

Measurement Point It is measured if the OR indication is TRUE when the called MAP sends the request for MSRN to the VDB. See point B in the following figure.



A

D

C

B

PRN Req

PRN Rsp

SRI Req

With OR flag bit

SRI Rsp

HLR VLRGMSC

With OR flag bit

Formula None

2.2.28 Count of Receiving MSRN During SOR Routing

Metrics Name ISM134

Description It is the count of received messages containing MSRN during SOR routing.

Measurement Point It is measured if the routing response message contains MSRN when the OR indication is TRUE. See point C in the following figure.




A

D

C

B

PRN Req

PRN Rsp

SRI Req

With OR flag bit

SRI Rsp

HLR VLRGMSC

With OR flag bit

Formula None

2.2.29 Count of Successes of SOR for MSRN

Metrics Name AMSS134

Description It is the count of successes of SOR applying for MSRN.

Measurement Point It is measured when the OR indication is TRUE and the MAP succeeds in requesting MSRN. See point D in the following figure.



A

D

C

B

PRN Req

PRN Rsp

SRI Req

With OR flag bit

SRI Rsp

HLR VLRGMSC

With OR flag bit

Formula None

2.3 Authentication 2.3.1 Overview of MS_TYPE_AUTH


Name Description

SAIHT20 Count of authentication set requests to HLR

SRASH20 Count of authentication set receipts from HLR

REASHT20 Count of empty authentication set receipts from HLR

SIPT20 Count of authentication set requests to PVLR

SRASPT20 Count of authentication set receipts from PVL

ART20 Count of authentication requests

ST20 Count of successful authentications

IST20 Count of authentication failures due to illegal SRES

ARTT20 Count of authentication requests with TMSI

ISATT20 Count of authentication failures due to illegal SRES (with TMSI)

SAIIT20 Count of successful authentications after IMSI being identified




Name Description

ANRSP20 Count of failures in responding to authentication requests

SRFDA20 Count of failure responses to authentication requests

2.3.2 Count of Authentication Set Requests to HLR

Metrics Name SAIHT20

Description It is the count of requests for authentication sets sent by the VLR to the HLR.

Measurement Point It is measured when the MSC sends to the HLR the message SEND_AUTHENTICATION_ INFO_REQ. See point A in the following figure.

MSC Server

A

HLR

SEND_AUTHENTICATION_INFO_REQ

B

SEND_AUTHENTICATION_INFO_RSP

Formula None

2.3.3 Count of Authentication Set Receipts from HLR

Metrics Name SRASH20

Description It is the count of authentication sets received by the VLR from the HLR.



Measurement Point It is measured when the MSC/VLR receives from the HLR the message SEND_AUTHENTICATION_INFO_RSP (if an authenciation set is contained). See point B in the following figure.

MSC Server

A

HLR


B


Formula None

2.3.4 Count of Empty Authentication Set Receipts from HLR

Metrics Name REASHT20

Description It is the count of empty authentication sets received by the VLR from the HLR.

Measurement Point It is measured when the MSC/VLR receives from the HLR the message SEND_AUTHENTICATION_INFO_RSP (if an empty authentication set is contained). See point B in the following figure.




MSC Server

A

HLR


B


Formula None

2.3.5 Count of Authentication Set Requests to PVLR

Metrics Name SIPT20

Description It is the count of requests for authentication sets from the VLR to the PVLR. When MSs register in the new VLR with TMSIs allocated in the previous VLR (PVLR), the new VLR receives the IMSIs and authentication parameter from PVLR before sending the update requests to the HLR.

Measurement Point The VLR sends the message MAP/G MAP_SEND_IDENTIFICATION to the PVLR. See point A in the following figure.

MSC Server

A

PVLR

SEND_IDENTIFICATION_REQ

B

SEND_IDENTIFICATION_RSP



Formula None

2.3.6 Count of Authentication Set Receipts from PVLR

Metrics Name SRASPT20

Description It is the count of successes in receiving authentication sets from the PVLR (that is, the authentication sets received from the PVLR are not empty). When MSs register in the new VLR with TMSIs allocated in the previous VLR (PVLR), the new VLR receives the IMSIs and authentication parameter from PVLR before sending the update request to the HLR.

Measurement Point It is measured when the VLR receives the message MAP/G MAP_SEND_IDENTIFICATION ACK from the PVLR. See point B in the following figure.

MSC Server

A

PVLR

SEND_IDENTIFICATION_REQ

B

SEND_IDENTIFICATION_RSP

Formula None

2.3.7 Count of Authentication Requests

Metrics Name ART20

Description It is the count of authentication requests from the VLR. Either TMSI or IMSI can be used in the requests.




Measurement Point It is measured when the MSC sends the message AUTHENTICATION_REQUEST to the UE (MS) after receiving the message MAP/B AUTHENTICATION_REQUEST from the VLR. See point A in the following figure.

UE MSC Server

A

B

AUTHENTICATION_REQUEST

AUTHENTICATION_RESPONSE

Formula None

2.3.8 Count of Successful Authentications

Metrics Name ST20

Description It is the count of successful XRES and SRES authentications in the VLR after the MSC receives the message Authentication Response (including XRES and SRES) from the MS and forwards it to the VLR. Either IMSI or TMSI can be used in the authentications.

Measurement Point It is measured when the MSC sends the message MAP/B AUTHENTICATION_RESPONSE to the VLR, and the VLR returns the related MAP message after it succeeds in SRES authentication. See point B in the following figure.



UE MSC Server

A

B



Formula None

2.3.9 Count of Authentication Failures Due to Illegal SRES

Metrics Name IST20

Description It is the count of authentication failures due to the illegal message Authentication Response from mobile subscribers.

Measurement Point It is measured when the MSC fails to check the message AUTHENTICATION_RESPONSE after receiving it. See point B in the following figure.

UE MSC Server

A

B



Formula None




2.3.10 Count of Authentication Requests with TMSI

Metrics Name ARTT20

Description It is the count of authentication requests by the VLR after MSs send the service requests with TMSIs.

Measurement Point It is measured when the MSC sends the message Authentication Request to an MS (using TMSI authentication) after receiving the message MAP/B AUTHENTICATION_REQUEST from the VLR. See point A in the following figure.

UE MSC Server

A

B



Formula None

2.3.11 Count of Authentication Failures Due to Illegal SRES (with TMSI)

Metrics Name ISATT20

Description It is the count of failures of SRES authentication in the VLR after the MSC receives the message Authentication Response (including SRES) from MSs and sends it to the VLR. TMSIs are used for the authentications.



Measurement Point It is measured when the VLR returns the message Provide IMSI to the MSC after receiving the message MAP/B AUTHENTICATION_RESPONSE and detecting the illegal SRES. See point B in the following figure.

UE MSC Server

A

B



Formula None

2.3.12 Count of Successful Authentications After IMSI Being Identified

Metrics Name SAIIT20

Description It is the count of successful authentications with IMSIs after the TMSI authentication fails.

Measurement Point It is measured when the MSC sends the message MAP/B AUTHENTICATION_RESPONSE to the VLR, and the VLR returns the related MAP message (for legal subscribers, service is accepted; for illegal subscribers, service is rejected) after it succeeds in SRES authentication. The premise is that the authentication is just performed.

It is measured when the message Authentication Response received by the MSC is sent from a legal subscriber, that is, when the IMSI authentication succeeds. See point B in the following figure.




UE MSC Server

B





IDENTITY_REQUEST

IDENTITY_RESPONSE

A

Formula None

2.3.13 Count of Failures in Responding to Authentication Requests

Metrics Name ANRSP20

Description It is the count of failures in receiving the message Authentication Response from UEs in the specified time.

Measurement Point It is measured when the MSC times out in waiting for the message Authentication Response from a UE. See point A in the following figure.



A

UE MSC Server


Formula None

2.3.14 Count of Failure Responses to Authenication Requests

Metrics Name SRFDA20

Description It is the count of the AUTHENTICATION_FAILURE messages returned from UEs during authentication.

Measurement Point It is measured when a UE returns the message MAC Failure or Synch Failure. See point A in the following figure.

A

UE MSC Server


AUTHENTICATION_FAILURE

Formula None




2.4 Location Update 2.4.1 Overview of MS_TYPE_LOC_UP


Name Description

NOLUREQ Count of location update requests

NOLUREJ Count of location update rejections

NOID Count of IMSI detachments

NOIA Count of IMSI attachments

LUIVRT19 Count of location update requests in VLR

SLUIVT19 Count of location update successes in VLR

STIVRT19 Count of location update requests due to subscriber roaming

SSLUIVT19 Count of location update successes due to subscriber roaming

MSNRUR19 Count of location update successes due to national roaming

MSIRUR19 Count of location update successes due to international roaming

HUUULF Count of location update failures due to unknown user in HLR

IUULF Count of location update failures due to illegal MS

IEULF Count of location update failures due to IMEI check failure

PPAULF Count of location update failures due to PLMN denying access

LPULF Count of location update failures due to prohibition of location area

RPULF Count of location update failures due to roaming prohibition

PEULF Count of location update failures due to protocol failure

NFULF Count of location update failures due to network failure

NLPULF Count of location update failures due to prohibition of location area in network

NSCULF Count of location update failures due to prohibition of cell in location area

OCULF Count of location update failures due to other causes

ISDT19 Count of attempts to insert user data

SISDT19 Count of successes in inserting user data

ARD Count of location update failures due to ARD



2.4.2 Count of Location Update Requests

Metrics Name NOLUREQ

Description It is the count of requests for location update initiated by mobile subscribers, including general location update and periodic location update.

Measurement Point It is measured when the MSC receives the message LOCATION UPDATE REQUEST from a mobile subscriber. See point A in the following figure.

A

UE MSC Server

LOCATION_UPDATING_REQUEST

LOCATION_UPDATING_ACCEPT

B

Formula None

2.4.3 Count of Location Update Rejections

Metrics Name NOLUREJ

Description It is the count of rejections to location update requests by mobile subscribers.

Measurement Point It is measured when the MSC sends the message LOCATION UPDATE REJECT to a mobile subscriber. See point B in the following figure.




A

UE MSC Server


LOCATION_UPDATING_REJECT

B

Formula None

2.4.4 Count of IMSI Detachments

Metrics Name NOID

Description It is the count of IMSI detachments due to power-off by mobile subscribers.

Measurement Point It is measured when the MSC receives the message IMSI DETACH IND from a mobile subscriber. See point A in the following figure.

A

UE MSC Server

IMSI_DETACH_IND

Formula None

2.4.5 Count of IMSI Attachments

Metrics Name NOIA



Description It is the count of IMSI attachments due to power-on, SIM card insertion, and access to service coverage areas.

Measurement Point It is measured when the MSC receives from a mobile subscriber the message LOCATION UPDATE REQUEST, which indicates that the IMSI is activated (IMSI ATTACH UPDATE). See point A in the following figure.

A

UE MSC Server



B

Formula None

2.4.6 Count of Location Update Requests in VLR

Metrics Name LUIVRT19

Description It is the count of requests for location update after mobile subscribers register in the local VLR.

Measurement Point It is measured when the MSC sends the message MAP_UPDATE_LOCATION_AREA to the VLR, and receives the message LOCATION_UPDATING_REQ from a local mobile subscriber. See point A in the following figure.




A

UE MSC Server



B

Formula None

2.4.7 Count of Location Update Successes in VLR

Metrics Name SLUIVT19

Description It is the count of successful location updates in the VLR.

Measurement Point It is measured when the MSC receives the message MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a roaming subscriber is updated successfully. See point B in the following figure.

A

UE MSC Server



B

Formula None



2.4.8 Count of Location Update Requests Due to Subsriber Roaming

Metrics Name STIVRT19

Description It is the count of requests for location updates when mobile subscribers roam to the local VLR service area (they have not registered in the local VLR for location update).

Measurement Point It is measured when the MSC sends the message MAP_UPDATE_LOCATION_AREA to the VLR, and receives the request for location update from a mobile subscriber, who roams between VLRs. See point A in the following figure.

A

UE MSC Server



B

Formula None

2.4.9 Count of Location Update Successes Due to Subsriber Roaming

Metrics Name SSLUIVT19

Description It is the count of successful location updates when mobile subscribers roam to the local VLR service area.

Measurement Point It is measured when the MSC receives the message MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a mobile subscriber roaming between VLRS is updated successfully. See point B in the following figure.




A

UE MSC Server



B

Formula None

2.4.10 Count of Location Update Successes Due to National Roaming

Metrics Name MSNRUR19

Description It is the count of successful location updates when national mobile subscribers roam to the local VLR.

Measurement Point It is measured when the MSC receives the message MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a roaming subscriber (a national roaming subscriber in different PLMNs) is updated successfully.

See point B in the following figure.

A

UE MSC Server



B

Formula None



2.4.11 Count of Location Update Successes Due to International Roaming

Metrics Name MSIRUR19

Description It is the count of location update successes when international mobile subscribers roam to the local VLR.

Measurement Point It is measured when the MSC receives the message MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a roaming subscriber (an international roaming subscriber in different PLMNs) is updated successfully. See point B in the following figure.

A

UE MSC Server



B

Formula None

2.4.12 Count of Location Update Failures Due to Unknown User in HLR

Metrics Name HUUULF

Description It is the count of location update failures caused when the HLR cannot identify mobile subscribers.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#2, IMSI Unknown In HLR). See point A in the following figure.




A

UE MSC Server UE

LOCATION_UPDATION_REQUESTUPDATE_LOCATION_REQ

UPDATE_LOCATION_RSP


Formula None

2.4.13 Count of Location Update Failures Due to Illegal MS

Metrics Name IUULF

Description It is the count of location update failures due to illegal mobile subscribers.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#3, Illegal MS). See point B in the following figure.

A

UE MSC Server



B

Formula None



2.4.14 Count of Location Update Failures Due to IMEI Check Failure

Metrics Name IEULF

Description It is the count of location update failures due to failure in IMEI authentication.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#6, Illegal IMEI). See point B in the following figure.

A

UE MSC Server



B

Formula None

2.4.15 Count of Location Update Failures Due to PLMN Denying Access

Metrics Name PPAULF

Description It is the count of location update failures caused when the local PLMN denies the access of mobile subscribers.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#11, PLMN not allow). See point B in the following figure.




A

UE MSC Server



B

Formula None

2.4.16 Count of Location Update Failures Due to Prohibition of Location Area

Metrics Name LPULF

Description It is the count of location update failures due to the denial of the location areas.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#12, Local Area not allowed). See point B in the following figure.

A

UE MSC Server



B

Formula None



2.4.17 Count of Location Update Failures Due to Roaming Prohibition

Metrics Name RPULF

Description It is the count of location update failures caused when roaming is restricted in the location area.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#13, Roaming not allowed in this location area). See point B in the following figure.

A

UE MSC Server



B

Formula None

2.4.18 Count of Location Update Failures Due to Protocol Failure

Metrics Name PEULF

Description It is the count of location update failures due to the protocol failure. The protocol failure is caused by the follow reasons:

#96: Mandatory information element error #99: Information element non-existent or not implemented #100: Conditional IE error #111: Protocol error, unspecified




Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause values that entail location update rejection). See point B in the following figure.

A

UE MSC Server



B

Formula None

2.4.19 Count of Location Update Failures Due to Network Failure

Metrics Name NFULF

Description It is the count of location update failures due to the network failure.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#11, Network failure). See point B in the following figure.

A

UE MSC Server



B

Formula None



2.4.20 Count of Location Update Failures Due to Prohibition of Location Area in PLMN

Metrics Name NLPULF

Description It is the count of location update failures due to denial of the location areas in a PLMN.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#13, nation roam not allow). See point B in the following figure.

RNC MSC Server

LOCATION_UPDATE_REQUEST

A

LOCATION_UPDATE_REJECT

BCause:Nation Roam Not Allowed

Formula None

2.4.21 Count of Location Update Failures Due to Prohibition of Location Area Cell

Metrics Name NSCULF




Description It is the count of location update failures due to denial of location area cells.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains cause#15, No suitable cells in location area). See point B in the following figure.

RNC MSC Server

LOCATION_UPDATE_REQUEST

A

LOCATION_UPDATE_REJECT

BCause:No Suitable Cells inLocation Area

Formula None

2.4.22 Count of Location Update Failures Due to Other Causes

Metrics Name OCULF

Description It is the count of location update failures due to other causes.

Measurement Point It is measured when the MSC sends to a mobile subscriber the message LOCATION UPDATE REJECT (it contains other causes). See point B in the following figure.



A

UE MSC Server



B

Formula None

2.4.23 Count of Attempts to Insert User Data

Metrics Name ISDT19

Description It is the count of attempts to insert user data to the VLR indicated by the HLR after the locations of roaming subscribers are updated or the user data in the HLR is modified.

Measurement Point It is measured when the VLR receives the message MAP/D Insert Subscriber data from the HLR, and the MSC sends the message INSERT_SUBSCRIBER_DATA_REQ after receiving UPDATA_LOCATION_CNF from the HLR. See point A in the following figure.

A

UE MSC Server UE


UPDATE_LOCATION_RSP


INSERT_SUBSCRIBER_DATA_REQ

INSERT_SUBSCRIBER_DATA_RSP

B




Formula None

2.4.24 Count of Sucesses in Inserting User Data

Metrics Name SISDT19

Description It is the count of successes in inserting user data to the VLR indicated by the HLR after the locations of roaming subscribers are updated or the user data in the HLR is modified.

Measurement Point It is measured when the VLR receives the message MAP/D Insert Subscriber data from

the HLR, and returns MAP/D Insert Subscriber data ACK. It is measured when the MSC receives the message UPDATA_LOCATION_CNF from

the HLR and returns INSERT_SUBSCRIBER_DATA_REP.

See point B in the following figure.

A

UE MSC Server UE


UPDATE_LOCATION_RSP


INSERT_SUBSCRIBER_DATA_REQ

INSERT_SUBSCRIBER_DATA_RSP

B

Formula None

2.4.25 Count of Location Update Failures Due to ARD

Metrics Name ARD



Description It is the count of location update failures due to the access restriction in updating locations.

Measurement Point It is measured when the MSC sends the message LOCATION UPDATE REJECT to the MS. See point A in the following figure.

Its cause value is determined by the "Cause value of location update reject due to ARD" configured in the Data Configuration. The message contains any one of the following cause values:

Cause#11 Network failure Cause#12 Local Area not allowed Cause#13 Roaming not allowed in this location area Cause#15 No Suitable Cells In Location Area

LOCATION_UPDATE_REQ

RNC MSC Server

A

LOCATION_UPDATE_REJ

Formula None

01-02 MSC Basic Functions

Documents

iureleaserequest

ciphering

sim card insertion

rnmmtmsireal

huawei technologies

locationupdationrequest

mm common

msc server