The Mobile Originating Call Traffic Data

7/27/2019 The Mobile Originating Call Traffic Data

1/106

The Mobile Originating Call (MOC) traffic data Siemens

MN2537EU01MN_0001 2003 Siemens AG

1

Contents

1 The mobile originating call 31.1 The arriving of the service request to the MSC 41.2 The authentication procedure 61.3 The ciphering procedure 61.4 The IMEI check procedure 81.5 The TMSI reallocation procedure 81.6 The arrival of the setup message 101.7 The digit translation 121.8 The SN seizure and the arriving of the call to the G-MSC 141.9 The G-MSC SN seizure and the routing of the call to the partner

network 161.10 The traffic channel assignment 181.11 The call setup termination 201.12 The ANSWER by the B party 221.13 The normal release of the call 242 What may go wrong on a MOC 312.1 Error detected with/after the CM SERVICE REQUEST message 322.2 Technical or MS error detected during authentication 482.3 Error at (or before) the reception of the SETUP message 542.4 Error during the call routing on the MORTR traffic type 662.5 Error with the call routing on the MOUT NOT PLMN traffic type 722.6 Error on a subsequent MSC during the PLMN's routing of the call 802.7 Error after the TCH ASSIGNMENT phase 882.8 Error due to call terminated by a upper network element 942.9 Error due to call terminated by a lower/upper network element 962.10 Error due to call terminated by the A party before ALERT 982.11 Error due to call terminated by the A party during ALERT or due to

TIME OUT 1002.12 Call terminated during SETUP due to radio problems 102

The Mobile Originating Call (MOC) traffic

data


2/106

Siemens The Mobile Originating Call (MOC) traffic data

MN2537EU01MN_0001

2003 Siemens AG

2

2.13 Abnormal release of the call after the ANSWER message 104


3/106



3

1 The mobile originating call

On this chapter only MSC, VLR and INTCELL (INTCREL) traffic data will beanalyzed.

The INTCELL traffic data is the last "core" measurement to be analyzed, during asuspicious or error situation, before the handover to the BSS team. Can be also usedfor the construction of cell based traffic data at the MSC.


4/106


MN2537EU01MN_0001

2003 Siemens AG

4

1.1 The arriving of the service request to the MSC

The message CM_SERVICE_REQUEST will trigger the processing of the call at theMSC. The bellow mentioned counters will be triggered.

At the VMSC

CALL_ATTEMPTS for MORTR [NR]

Indicates how many call attempts have taken place, independently of thereceived BS or TS

Trigger: upon receipt of each CM SERVICE REQUEST with SERVICE

TYPE = mobile originating call or establishment of all emergency callattempts (Short Message Service and SS activation are not included)

EMERGENCY_TS12_ATTEMPTS [NR]

Indicates the number of emergency call attempts (TS12) for MORTR

Trigger: each time CM SERVICE REQUEST indicating an emergency callis received

TRAFFIC_VOLUME for MORTR [sec]

Indicates the sum of all holding timesTrigger:

starts: each time CM SERVICE REQUEST is received

stops: each time RELEASE COMPLETE is received

Finally the following INTCELL counter is also incremented: one independent counter,with independent values, will be "generated" for each monitored cell.

At the VMSC and for each measured cell

ORIG_CALL_ATTEMPTS [NR]

indicates the number of attempted calls for originating calls

Trigger: upon receipt of CM SERVICE REQUEST with the CM servicetype:

- mobile originating call

- emergency call

Short message service and SS activation are not included


5/106



5

MOC (Part 1 of 4)

MS BSS MSC / VLR G-MSC / VLRCHN_REQ(Service, Reas on,...)

CHN_ASSIG

CM_SERV_REQ

(Service Type, CKSN,

TMSI,...)

CC

(Con. Co nfirmed)

AUTH_RE Q

(CKSN, RAND)

AUTH_RE SP

(SRES)

CIPHER_MODE_CMD

(K5, A5x)

CIPHER_MOD_CMD

(A5x)

CIPHER_MODE_COM

(---)

CIPHER_MOD_COM

(---)

CM_SERV_REQ


TMSI,...)

->MSC: CALL_ATTEMPTS f or MORTR

->MSC: EMERGENCY_TS12_ATTEMPTS

->MSC: TRAFFIC_VOLUME for MORTR

S t a r t Po i nt

->INTCRE L: ORIG_CA LL_A TTEMPTS

Fig. 1 The arriving of the service request to the MSC


6/106


MN2537EU01MN_0001

2003 Siemens AG

6

1.2 The authentication procedure

As has been discussed on the Location Registration/Update procedure, one singlecounter at the VLR monitors the Authentication procedure.

At the VVLR

AUTH_REQ [NR]

indicates the number of authentication requests

Trigger: each time AUTHENTICATION REQUEST is sent to the MS

1.3 The ciphering procedure

Ciphering is one of the security procedures involved on the GSM service. The VLRcounters presented bellow are responsible for the collection of the Ciphering trafficdata.

At the VVLR:

CIPHERING_REQ [NR]

indicates the number of ciphering requests

Trigger: each time CIPHERING COMMAND is sent to the MS

SUCC_CIPH_MODE_CTRL_PROC [NR]

indicates the number of successful ciphering mode control procedures

Trigger: each time CIPHERING MODE COMPLETE is received from

MS/BSC


7/106



7

MOC (Part 1 of 4)


CHN_ASSIG

CM_SERV_REQ


TMSI,...)

CC

(Con. Co nfirmed)

AUTH_RE Q

(CKSN, RAND)

AUTH_RE SP

(SRES)

CIPHER_MODE_CMD

(K5, A5x)

CIPHER_MOD_CMD

(A5x)

CIPHER_MODE_COM

(---)

CIPHER_MOD_COM

(---)

CM_SERV_REQ


TMSI,...)




S t a r t Po i nt

->VLR: AUTH_REQ

->VLR: CIPHERING_RE Q

->VLR: SUCC_ CIPH_MODE_ CTRL_PROC


Fig. 2 The Authentication procedure and the Ciphering procedure


8/106


MN2537EU01MN_0001

2003 Siemens AG

8

1.4 The IMEI check procedure

The IMEI Check procedure is used for mobile equipment (ME) network accessauthorization.

From the quite complete set of counters available for it's monitoring we will analyzeonly the one bellow.

At the VMSC:

CALL_WHITE_LIST for MORTR [NR]

indicates the number of successful calls with white listed equipment

Trigger: each time TC-RESULT (white list IMEI) is received from the EIR inresponse to check IMEI at call setup

1.5 The TMSI reallocation procedure

The counters, which may be used for the TMSI reallocation monitoring, are presenton the VLR set:

At the VVLR:

ATTEMPTED_TMSI_REALLOCATIONS [NR]

indicates the number of attempted TMSI reallocations

Trigger: each time TMSI REALLOCATION COMMAND or LOC UPD ACCcontaining a TMSI reallocation request is sent to BSC/MS

SUCCESSFUL_TMSI_REALLOC [NR]

indicates the number of successful TMSI reallocations

Trigger: each time TMSI REALLOCATION COMPLETE is received fromMS/BSC


9/106



9

MOC (Part 2 of 4)

MS BSS MSC / VLR HLR / AC G-MSC / VLR

IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP

(MSISDN, Bearer ServiceI)

DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation

->MSC: CALL_WHITE_LIST fo r MORTR

->VLR: ATTEMPTED_TMSI_R EALLOCATIONS

->VLR: SUCCESS FUL_TMSI_REALLOC

Fig. 3 The IMEI Check procedure and the TMSI reallocation procedure


10/106


MN2537EU01MN_0001

2003 Siemens AG

10

1.6 The arrival of the setup message

The arrival of the SETUP message with the identity of the service and with the Bnumber will trigger the CALL SETUP traffic volume counter:

At the VMSC:

TIME_CALL_SET_U_SERV [sec]

is the average time to provide the call setup service

Trigger:

starts: each time SET UP is received (MOC) or sent (MTC)

stops: each time ASSIGNMENT COMPLETE is received

The STOP point is always the arrival of the TCH allocation message. It will take placeand will be present on a later stage of the MOC procedure.


11/106



11

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation


->MSC: TIME_CALL_SET_U_ SERV for MOC

Start Po int



Fig. 4 The arrival of the Setup message


12/106


MN2537EU01MN_0001

2003 Siemens AG

12

1.7 The digit translation

The B number Digit Translation will normally result on the seizure of the calldestination, route, TGRP and time slot. From the traffic measurement point of view a"MSC Traffic Type" change will occur.

On a typical MOC the new traffic type will be the MOUT_NOT_PLMN and thefollowing counters may be incremented:

At the VMSC:

CALL_ATTEMPTS for MOUT_NOT_PLMN [NR]

indicates how many call attempts have taken place

Trigger: upon receipt of SET UP and digit analysis results in this traffic type(speech call attempts only)

DATACDA_ANA_ATTEMPTS for MOUT_NOT_PLMN [NR]

DATACDA_DIG_ATTEMPTS for MOUT_NOT_PLMN [NR]

ALTFAXSP_CALL_ATTEMPTS for MOUT_NOT_PLMN [NR]

DATACDS_ANA_ATTEMPTS for MOUT_NOT_PLMN [NR]

DATACDS_DIG_ATTEMPTS for MOUT_NOT_PLMN [NR]

ALT_SPEECH_DATA_ATTEMPTS for MOUT_NOT_PLMN [NR]

indicates the number of call attempts for alternate speech/data or speechfollowed by data services

Trigger: each time the digit analysis after interrogation results in theMOUT_NOT_PLMN traffic type

DED_PAD_ATTEMPTS [NR]

indicates how many call attempts to a foreign network for dedicated PADaccess services have taken place for MOUT_NOT_PLMN

Trigger: each time the digit analysis after interrogation results in theMOUT_NOT_PLMN traffic type

TRAFFIC_VOLUME for MOUT_NOT_PLMN [sec]

indicates the sum of all holding times

Trigger:

starts: with the end of the final digit translation, where the finaldestination is achieved.

stops: when RELEASE COMPLETE is sent or received, or with anunsuccessful call attempt before IAM is sent


13/106



13

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation


->MSC: CALL_ATTEMPTS fo r MOUT_NOT_PLMN

- >M S C : D A TA C D A _ A N A _ A TTEM PTS fo r M O U T_ N O T_ PLM N,

->MSC: DATACDA_DIG_ATTEMPTS for MOUT_NOT_PLMN

->MSC: ALTFAXSP_CALL_ATTEMPTS for MOUT_NOT_PLMN

- >M S C : D A TA C D S _ A N A _ A TTEM PTS fo r M O U T_ N O T_ PLM N

->MSC: DATACDS_ DIG_ATTEMPTS for MOUT_NOT_P LMN

->MSC: ALT_SPEECH_DATA_ ATTEMPTS for MOUT_NOT_PLMN

->MSC: FAX3_ CALL_ATTEMPTS for MOUT_NOT_PLMN

->MSC: DED_PAD_ATTEMPTS


Start Po int

->MSC: TRAFFIC_VOLUME for MOUT_NOT_PLMN

S t a r t Po i nt



Fig. 5 The Digit Translation


14/106


MN2537EU01MN_0001

2003 Siemens AG

14

1.8 The SN seizure and the arriving of the call to theG-MSC

The ISUP message IAM (Initial Address Message) will trigger counters on both sidesof the VMSC/GMSC logical interface:

At the VMSC:

SN_THROUGH_CONNECTIONS for MOUT_NOT_PLMN [NR]

indicates the number of successful call attempts

Trigger: each IAM is sent to the next exchange (after the seizure of the SNand the performing of the COC)

At the GMSC:

CALL_ATTEMPTS for MICTR [NR]

indicates how many call attempts have taken place, independently of thereceived BS or TS

Trigger: each time IAM is received (all call attempts)

TRAFFIC_VOLUME for MICTR [sec]


Trigger:

starts: each time IAM is received



15/106



15

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation

->MSC: SN_ THROUGH_CONNECTIONS fo r MOUT_NOT_PLMN











->MSC: CALL_ATTEMPTS for MICTR


Start Po int

->MSC: TRAFFIC_VOLUME for MICTR

Start Po int


S t a r t Po i nt



Fig. 6 The SN seizure and the GMSC first contact


16/106


MN2537EU01MN_0001

2003 Siemens AG

16

1.9 The G-MSC SN seizure and the routing of the callto the partner network

The GMSC will process the arrived call and a new traffic type change will happen.The incoming MICTR call will "leave" the network element as MTRAN.

The following counters may be used to control the successful seizure and routing ofthe incoming call:

At the GMSC

SN_THROUGH_CONNECTIONS for MTRAN [NR]indicates the number of successful call attempts

Trigger: each IAM is sent to the next exchange (after the seizure of the SNand the performing of the COC)

CALL_ATTEMPTS for MTRAN [NR]

indicates how many call attempts have taken place

Trigger: each time IAM is received and digit analysis results in outgoingtraffic (all call attempts)

TRAFFIC_VOLUME for MTRAN [sec]


Trigger:

starts: with proper result of the digit analysis.

stops: when RELEASE COMPLETE is received


17/106



17

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation


->MSC: SN_ THROUGH_CONNECTIONS for MTRAN












->MSC: CALL_ATTEMPTS fo r MTRAN


Start Po int


Start Po int


S t a r t Po i nt

->MSC: TRAFFIC_VOLUME for MTRAN

S t a r t Po i nt



->MSC: TRA FFIC_VOLUME for

M TR A N

Fig. 7 The G-MSC SN seizure and call treatment


18/106


MN2537EU01MN_0001

2003 Siemens AG

18

1.10 The traffic channel assignment

The counters involved on the traffic channel assignment procedure:

At the GMSC

GEN_TRAFF_CHAN_REQ for MORTR [NR]

indicates the number of generated traffic channel requests

Trigger: each time ASSIGNMENT REQUEST is sent to the BSC

For MORTR: after the last CM SERVICE REQUEST message

CALL_TCH_ALLOCATION for MORTR [NR]

indicates the number of calls with successfully completed traffic channel(TCH) allocation

Trigger: each time ASSIGNMENT COMPLETE is received

TS11_EMERG_CALL_TCH_ALL [NR]

indicates the number of outgoing emergency calls with successfullycompleted traffic channel allocation for emergency calling (TS11)

Trigger: each time ASSIGNMENT COMPLETE is received for TS11 calls

TS12_EMERG_CALL_TCH_ALL [NR]

indicates the number of outgoing emergency calls with successfullycompleted traffic channel allocation for emergency calling (TS12)

Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls

The INTCELL counters involved on the traffic channel assignment procedure:

At the MSC and for each cell

ORIG_CALL_ATT_TCH_REQ [NR]

indicates the number of attempted originating calls with traffic channelrequest

Trigger: with an originating call, each time ASSIGNMENT REQUEST issent to the BSC

ORIG_CALL_SUCC_TCH_ALLOC [NR]

indicates the number of mobile originating calls with successful traffic

channel allocation


19/106



19

Trigger: each time ASSIGNMENT COMPLETE is received withoutprevious queuing.

It is also (internally) triggered for technical reasons without receipt of

ASSIGNMENT COMPLETE on the A-Interface for the second, parallel,call in case of the call hold function

MOC (Part 3 of 4)


ALERT / P ROG RES S

ASS IGNMENT _RE QUEST

(Channel on the Air Interface)

ASS IGNMEN T_C OMP LETE


ACM

ANM

ACM

ANM

->MSC: CALL_TCH_ALLOCATION for MORTR

->MSC: TS11_EMERG_ CALL_TCH_ALL

->MSC: TS12_ EMERG_CALL_TCH_ALL

->INTCREL: ORIG_CALL_SU CC_TCH_ALLOC

->MSC: GEN_TRAFF_C HAN_REQ for MORTR

->INTCREL: ORIG_CALL_ATT_TC H_REQ

Fig. 8 The Traffic Channel assignment


20/106


MN2537EU01MN_0001

2003 Siemens AG

20

1.11 The call setup termination

The ASSIGNMENT COMPLETE message marks also the CALL SETUP end from thetraffic measurement point of view. So, the following "CALL SETUP" counters will alsobe incremented:

At the VMSC:

TIME_CALL_SET_U_SERV [sec]

is the average time to provide the call setup service

Trigger:

starts: each time SET UP is received (MOC)

stops: each time ASSIGNMENT COMPLETE is received

NUM_CALL_SET_UP_CONTRIB [NR]

indicates the number of calls contributing to call setup time

Trigger: each time ASSIGNMENT COMPLETE is received (for thecalculation of the average setup time)


21/106



21

MOC (Part 3 of 4)


ALERT / P ROG RES S





ACM

ANM

ACM

ANM







->MSC: TIME_CA LL_SET_ U_S ERV for MOC

S t o p P o i nt

->MSC: NUM_ CALL_SET_ UP_CONTRIB

Fig. 9 The Call Setup termination


22/106


MN2537EU01MN_0001

2003 Siemens AG

22

1.12 The ANSWER by the B party

The answer to the call by the B party will trigger the traffic volume with answer(TV_WA) counter although the "Calls With Answer" counters aren't involved on thisstage. The TV_WA counters will run until the call has been drop or normally releasedby any of the subscribers involved.

At the VMSC:

DUR_OF_CONV_SPEECH_SERV for MOUT_NOT_PLMN [sec]

indicates duration of conversation for speech services

Trigger:

starts: each time ANSWER is received

stops: each time call is released

DUR_OF_CONV_FAX3 for MOUT_NOT_PLMN [sec]

indicates the duration of conversation for the automatic facsimile group 3service

Trigger:



At the GMSC:

DUR_OF_CONVERSATION [sec]

indicates duration of conversation for MTRAN

Trigger:




23/106



23

MOC (Part 3 of 4)


ALERT / P ROG RES S





ACM

ANM

ACM

ANM








S t o p P o i nt


- >M S C : D U R _ O F_ C O N V _ S PEEC H_ S ER V f o r M O U T_ N O T_ PLM N

- >M S C : D U R _ O F_ C O N V _ FA X 3 fo r M O U T_ N O T_ PLM N

S t a r t Po i nt

->MSC: DUR_ OF_CONVERS ATION

Start Po int

Fig. 10 The call ANSWER


24/106


MN2537EU01MN_0001

2003 Siemens AG

24

1.13 The normal release of the call

With the normal release of an active call both the TV counters and the "Call withAnswer" counters will be incremented.

At the VMSC:

SPEECH_CALLS_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates how many speech calls are answered

DATACDA_ANA_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered data calls for CDA analog services

ALTFAXSP_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered data calls with alternation from speech tofacsimile

FAX3_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered data calls for automatic facsimile group 3

DATACDS_ANA_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered data calls for CDS analog services

DATACDS_DIG_WITH_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered data calls for CDS digital services

ALT_SPEECH_DATA_ANSWER for MOUT_NOT_PLMN [NR]

Indicates the number of answered alternate speech/data or speech followedby data calls

DED_PAD_WITH_ANSWER [NR]

Indicates the number of answered calls for dedicated PAD CDA services

TS11_EMERG_WITH_ANSWER [NR]

Indicates the number of answered emergency calls (TS11)

TS12_EMERG_WITH_ANSWER [NR]

Indicates the number of answered emergency calls (TS12)

Trigger: each time the connection has actually been released in reply to thereceipt of ANM

At the GMSC:

CALLS_WITH_ANSWER [NR]

Indicates the number of answered calls for MTRAN

Trigger: each time the connection has actually been released in reply to thereceipt of ANM


25/106


26/106


27/106



27

FORWARD RELEASE


REL

RLC

DISCONNE CT

(Reason)

RELEASE

(Reason)

RELEASE_COMP LETE

(Reason)

Release of Resources



S t o p Po i nt



S t o p Po i nt

RLC

- >MS C : D U R _ O F_ C O N V _ S PEEC H _ S ER V fo r MO U T_ N O T_ PLMN

- >MS C : D U R _ O F_ C O N V _ FA X 3 fo r MO U T_ N O T_ PLMN

S t o p p o i nt

REL

->MSC: DUR_OF_CONVERSATION

S t o p Po i nt

Fig. 12 The normal call release forward release


28/106


MN2537EU01MN_0001

2003 Siemens AG

28

And now the TV counters:

At the VMSC:

TRAFFIC_VOLUME for MORTR [sec]


Trigger:

starts: each time CM SERVICE REQUEST is received


TRAFFIC_VOLUME for MOUT_NOT_PLMN [sec]


Trigger:

starts: with the end of the final digit translation, where the finaldestination is achieved.

stops: when RELEASE COMPLETE is sent or received, or with anunsuccessful call attempt before IAM is sent

At the GMSC:

TRAFFIC_VOLUME for MICTR [sec]


Trigger:

starts: each time IAM is received


TRAFFIC_VOLUME for MTRAN [sec]


Trigger:

starts: with proper result of the digit analysis.

stops: when RELEASE COMPLETE is received


29/106



29

BACKWARD RELEASE


REL

RLC

RELEASE

(Reason)

RELEASE_COMP LETE

(Reason)

Release of Resources



S t o p Po i nt

->MSC: TRAFFIC_VOLUME fo r MICTR


S t o p P o i nt

RLC

- >MS C : D U R _ O F_ C O N V _ S PEEC H _ S ER V fo r MO U T_ N O T_ PLMN

- >MS C : D U R _ O F_ C O N V _ FA X 3 fo r MO U T_ N O T_ PLMN

S t o p p o i nt

->MSC: DUR_ OF_CONVERS ATION

S t o p Po i nt

Fig. 13 The normal call release backward release


30/106


MN2537EU01MN_0001

2003 Siemens AG

30


31/106



31

2 What may go wrong on a MOC


32/106


MN2537EU01MN_0001

2003 Siemens AG

32

2.1 Error detected with/after the CM SERVICEREQUEST message

Counters that may be incremented:

at the AMSC

UNS_REQ_DEST_ERR for MORTR [NR]

UNS_TECHN_FAULT for MORTR [NR]

UNS_SERV_CHECK for MORTR [NR]

UNS_CONGESTION for MORTR [NR]

UNS_PROTO_ERROR for MORTR [NR]

UNS_OVERLOAD for MORTR [NR]

UNS_SECURITY_FAIL for MORTR [NR],

Whose precise, relevant, trigger points will be presented on the next pictures.


33/106



33

MOC (Part 1 of 4)


CHN_ASSIG

CM_SERV_REQ


TMSI,...)

CC

(Con. Co nfirmed)

AUTH_RE Q

(CKSN, RAND)

AUTH_RE SP

(SRES)

CIPHER_MODE_CMD

(K5, A5x)

CIPHER_MOD_CMD

(A5x)

CIPHER_MODE_COM

(---)

CIPHER_MOD_COM

(---)

CM_SERV_REQ


TMSI,...)




S t a r t Po i nt

- >M S C : U N S _ R EQ _ D ES T_ ER R fo r M O R TR

->MSC: UNS_TECHN_FAULT for MORTR

->MSC: UNS_ SERV_ CHECK for MORTR

->MSC: UNS_ CONGESTION for MORTR

->MSC: UNS_PROTO_ERROR for MORTR

->MSC: UNS_OVERLOAD for MORTR


Fig. 14 Error detected with/after the CM SERVICE REQUEST message


34/106


MN2537EU01MN_0001

2003 Siemens AG

34

2.1.1 UNS_REQ_DEST_ERR for MORTR [NR]

Indicates how many calls are terminated because the requested destination wasunknown, blocked or could not be charged

General Trigger Description: the counter is incremented upon receiving a messageindicating an internal release (CP):

- after a failed operation

- after a failed digit analysis

Trigger 1: result from INV SUB ID: subscriber is unknown in the VLR

UNS_REQ_DEST_ERR for MORTR

Trigger 1: result from INV SUB ID: subscriber is unknown in the VLR

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS

CR(COMPL L3 INFO[CM SERV REQ])

LTG selectionNRELAY:[CR(COMPL L3 INFO /

CM SERV REQ)]

CR(SERV_REQ)

CREF(CM SERV REJ)

CREF(CM SERV REJ)

|||

->MSC: UNS_REQ_DEST_ERR for MORTR

Fig. 15 UNS_REQ_DEST_ERR for MORTR: trigger 1


35/106


36/106


37/106



37

Trigger 2: The message CC(SERV_DATA) was not successfully sent from MSC toA-LTG BSSAP after receiving the message RES_SUB_DATA. Encoding errors inthe MSC caused this error state.

For Normal and Emergency call with or without a SIM card.A network failure occurred after receiving the message RES_SUB_DATA

UNS_TECHN_FAULT for MORTR

Trigger 2: The message CC(SERV_DATA) was not successfully sent from MSC to A-LTG

BSSAP after receiving the message RES_SUB_DATA. Encoding errors in the MSC

caused this error state. For Normal and Emergency call with or without a SIM card.

A network failure occurred after receiving the message RES_SUB_DATA

INV SUB ID

RES SUB ID

N E

E X

X C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C |

|VLR

|

|

|

|

MSC

CPMS

BS



CM SERV REQ)]

CR(SERV_REQ)

INV SUB DATA

RES SUB DATA

CREF

CREF* encoding error or network failure


Fig. 18 UNS_TECHN_FAULT for MORTR: trigger 2


38/106


MN2537EU01MN_0001

2003 Siemens AG

38

Trigger 3: while sending INV SUB ID to the VLR, an internal failure occurs in theMSC


Trigger 3: while sending INV SUB ID to the VLR, an internal failure

occurs in the MSC

INV SUB ID

N E

E X

X C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C|

|VLR

|

|

|

|

MSC

CPMS

BS


LTG selectionNRELAY:[CR(COMPL L3 INFO / CM

SERV REQ)]

CR(SERV_REQ)

* INTERNAL ERROR

CREF

CREF


Fig. 19 UNS_TECHN_FAULT for MORTR: trigger 3


39/106


40/106


MN2537EU01MN_0001

2003 Siemens AG

40

2.1.4 UNS_CONGESTION for MORTR [NR]

indicates how many calls are terminated due to (trunk) congestion in the home MSC

General Trigger Description: each time a BSS trunk seizure is not successful dueto congestion

Trigger 1: getting LTG data not successful because no trunk available due tocongestion

UNS_CONGESTION for MORTR

Trigger 1: getting LTG data not successful because no trunk available due

to congestion

MS

BS

N E

E X

X C

T H

S

C

P| |CCF SSF TCAP

|

||

B-LTG

ISUP

C C| |

SSPVLR

|

||

MSC

A-LTG

BSSAPCP


CREF

->MSC: UNS_CONGESTION for MORTR

Fig. 21 UNS_CONGESTION for MORTR: trigger 1


41/106



41

2.1.5 UNS_PROTO_ERROR for MORTR [NR]

indicates how many calls are terminated due to protocol errors

General Trigger Description: each time a protocol error was detected but the callcould be identified

Trigger 1: receipt of CR (COMPL L3 INFO) containing a protocol error

UNS_PROTO_ERROR for MORTR

Trigger 1: receipt of CR (COMPL L3 INFO) containing a protocol error

N E

E XX C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C |

|VLR

||

|

|

MSC

CPMS

BS


CREF

* info invalid


Fig. 22 UNS_PROTO_ERROR for MORTR: trigger 1


42/106


MN2537EU01MN_0001

2003 Siemens AG

42

Trigger 2: upon receiving CR(SERV REQ)

unsuccessful message decoding,

invalid operation type included (i.e. no MOC, no emergency call, no

SCI, ...).

invalid mobile station identity included


Trigger 2: upon receiving CR(SERV REQ)

- unsuccessful message decoding,

- invalid operation type included (i.e. no

MOC, no emergency call, no SCI, ...).

- invalid mobile station identity included

N E

E X

X C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C |

|VLR

|

|

|

|

MSC

CPMS

BS



CM SERV REQ)]

CR(SERV_REQ)

* not successfully decoded

or info invalid


Fig. 23 UNS_PROTO_ERROR for MORTR: trigger 2

Trigger 7: The message RES_SUB_ID from the VLR is not successfully receiveddue to a protocol error


43/106



43

2.1.6 UNS_OVERLOAD for MORTR [NR]

indicates how many calls/transactions are terminated due to overload prevention

General Trigger Description: each time a call is internally released due to anoverload situation

Trigger 1: after relaying CR (COMPL L3 INFO), the LTG answers with OVERLOAD

UNS_OVERLOAD for MORTR

Trigger 1: after relaying CR (COMPL L3 INFO), the LTG answers with

OVERLOAD

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

|||

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS


LTG selectionNRELAY:[CR(COMPL L3 INFO /CM SERV REQ)]

CR(L3 REJ)

CREF(CM SERV REJ)

CREF(CM SERV REJ)

->MSC:UNS_OVERLOAD for MORTR

Fig. 24 UNS_OVERLOAD for MORTR: trigger 1


44/106


MN2537EU01MN_0001

2003 Siemens AG

44

Trigger 2: overload detected in the CP

UNS_OVERLOAD for MORTR

Trigger 2: overload detected in the CP

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

|||

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS


overload

CREF(CM SERV REJ)

->MSC: UNS_OVERLOAD for MORTR

Fig. 25 UNS_OVERLOAD for MORTR: trigger 2


45/106


46/106


MN2537EU01MN_0001

2003 Siemens AG

46

Trigger 2: result of INV SUB DATA not successful

* security failure

UNS_SECURITY_FAIL for MORTR

Trigger 2: result of INV SUB DATA not successful

INV SUB ID

RES SUB ID

N E

E X

X C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C |

|VLR

|

|

|

|

MSC

CPMS

BS



CM SERV REQ)]

CR(SERV_REQ)

INV SUB DATA

RES SUB DATA

CREF

CREF

->MSC:


Fig. 27 UNS_SECURITY_FAIL for MORTR: trigger 2


47/106



47

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


48/106


49/106



49

MOC (Part 1 of 4)


CHN_ASSIG

CM_SERV_REQ


TMSI,...)

CC

(Con. Co nfirmed)

AUTH_RE Q

(CKSN, RAND)

AUTH_RE SP

(SRES)

CIPHER_MODE_CMD

(K5, A5x)

CIPHER_MOD_CMD

(A5x)

CIPHER_MODE_COM

(---)

CIPHER_MOD_COM

(---)

CM_SERV_REQ


TMSI,...)




S t a r t Po i nt

- >M S C : U N S _ R EQ _ D ES T_ ER R fo r M O R TR

->MSC: UNS_ SECURITY_FAIL for MORTR

->VLR: AUTH_REQ


AUTH__REJ

->VLR: AUTH_WITH_ILLEGAL_S UB

Fig. 28 Technical or MS error detected during Authentication


50/106


51/106


52/106


MN2537EU01MN_0001

2003 Siemens AG

52

Trigger 4: the outcome of AUTH RES indicates an illegal mobile station


Trigger 4: the outcome of AUTH RES indicates an illegal mobile station

N E

E X

X C

T H|

|

|

|

A-LTG

BSSAP

RR MM CC

|

|

|

|

B-LTG

ISUP

C C |

|VLR

|

|

|

|

MSC

CPMS

BS



CM SERV REQ)]

CR(SERV_REQ)

INV SUB ID

RES SUB ID

DT1(SEC ERROR)

CC(SERV_DATA)

CC (AUTH REQ)

DT1 (AUTH RES)

RES AUTHCREF

CREF

* illegal MS

->MSC: UNS_SECURITY_FAIL for MORTR

Fig. 31 UNS_SECURITY_FAIL for MORTR: trigger 4


53/106



53

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


54/106


MN2537EU01MN_0001

2003 Siemens AG

54

2.3 Error at (or before) the reception of the SETUPmessage

The counters involved on the error detection may be:

at the VMSC

UNS_BS_REASON for MORTR


UNS_SERV_CHECK for MORTR

UNS_MS_BLOCKED for MORTR

UNS_LACK_IWE for MORTR


UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN


55/106



55

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation



Start Po int

- >M S C : U N S _ B S _ R EA S O N fo r M O R TR

->MSC: UNS_ TECHN_FA ULT for MORTR

->MSC: UNS_ SERV_ CHECK for MORTR

->MSC: UNS_ MS_ BLOCKED for MORTR

->MSC: UNS_ LACK_IWE for MORTR

- >M S C : U N S _ PR O TO _ ER R O R fo r M O R TR

->MSC: UNS _NETW_ MANAGEMENT for MOUT_NOT_ PLMN



Fig. 32 Error at (or before) the reception of the SETUP message


56/106


MN2537EU01MN_0001

2003 Siemens AG

56

2.3.1 UNS_BS_REASON for MORTR [NR]

Indicates how many calls are terminated during setup due to BSS/radio-relatedreasons

General Trigger Description: each time RELEASE COMPLETE/CLEAR REQUESTor SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received from the BSSbefore digit analysis is performed

The condition for the UNS_BS_REASON for MORTR increment is the occurrence ofa BSS error before the SETUP message digits could be translated.

UNS_BS_REASON for MORTR [NR]

indicates how many calls are terminated during setup due to BSS/radio-related

reasons

Trigger: each time RELEASE COMPLETE/CLEAR REQUEST orSUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received

from the BSS before digit analysis is performed

Fig. 33 UNS_BS_REASON for MORTR


57/106


58/106


MN2537EU01MN_0001

2003 Siemens AG

58

2.3.3 UNS_SERV_CHECK for MORTR [NR]

Indicates how many calls are terminated due to negative service facility checks ornegative compatibility checks

General Trigger Description: RELEASE COMPLETE (with the proper reason) issent to the BSS

Trigger 4: error in BC-check for emergency call


Trigger 4: error in BC-check for emergency call

DT1(TERMINATE)

DT1(REL COM)DT1(REL TRANSACTION)

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

|||

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS



CR(SERV_REQ)

CC(SERV_DATA)

CC (CIPH CMD)

DT1 (CIPH COM)

DT1EMERGENCY (SET UP)

DT1(EMERGENCY SET UP)

->MSC: UNS_SERV_CHECKfor MORTR

Fig. 35 UNS_SERV_CHECK for MORTR: trigger 4


59/106



59

Trigger 5: service is not provisioned, or CLIR is not allowed


Trigger 5: service is not provisioned, or CLIR is not allowed

DT1(TERMINATE)

DT1(REL COM)DT1(REL TRANSACTION)

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

|||

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS



CR(SERV_REQ)

CC(SERV_DATA)

CC (CIPH CMD)

DT1 (CIPH COM)

DT (SET UP)

DT1(SET UP)CLIR INVOCATION CLIR not allowed

Service notprovisioned

->MSC: UNS_SERV_CHECKfor MORTR

Fig. 36 UNS_SERV_CHECK for MORTR: trigger 5


60/106


61/106


62/106


63/106


64/106


65/106


66/106


67/106



67

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation



->MSC: DATACDA_ANA_ ATTEMPTS for MOUT_NOT_PLMN,


->MSC: ALTFAXSP_CALL_ATTEMPTS for MOUT_NOT_ PLMN


->MSC: DATACDS_D IG_ATTEMPTS for MOUT_NOT_PLMN


->MSC: FAX3_ CALL_ATTEMPTS fo r MOUT_NOT_ PLMN

->MSC: DED_PAD_ ATTEMPTS


Start Po int


S t a r t Po i nt

->MSC: UNS_ CONGESTION for MORTR

->MSC: UNS_ OVERLOAD for MORTR

->VLR: ATTEMPTED_TMSI_REALLOCATIONS


Fig. 43 Error during the call routing on the MORTR traffic type


68/106


69/106


70/106


71/106


72/106


73/106



73

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP(MSISDN, Bearer ServiceI)

DigitTranslation

IAM

CALL_P R OC

(---)

IMEI_CHECK

IAM

Digit

Translation



- >M S C : D A TA C D A _ A N A _ A TTEM PTS fo r M O U T_ N O T_ PLMN ,


->MSC: ALTFAXSP_CALL_ATTEMPTS for MOUT_NOT_P LMN

->MSC: DATACDS_ANA_ATTEMPTS for MOUT_NOT_PLMN

->MSC: DATACDS_ DIG_ATTEMPTS for MOUT_NOT_PLMN


->MSC: FAX3_ CALL_ATTEMPTS fo r MOUT_NOT_ PLMN

->MSC: DED_PAD_ ATTEMPTS


Start Po int


Start Po int

->MSC: UNS_ TECHN_FAULT for MOUT_NOT_ PLMN

- >M S C : U N S _ R EQ _ D ES T_ ER R fo r M O U T_ N O T_ PLM N

->MSC: UNS_NETW_ MANAGEMENT for MOUT_NOT_PLMN

- >M S C : U N S _ B S _ R EA S O N fo r M O U T_ N O T_ PLM N

->VLR: ATTEMPTED_TMSI_REALLOCATIONS


Fig. 47 Error with the call routing on the MOUT NOT PLMN traffic type


74/106


75/106



75

2.5.2 UNS_REQ_DEST_ERR for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated because the requested destination wasunknown, blocked or could not be charged for MOUT_NOT_PLMN. The destinationcouldnt be found due to several reasons

General Trigger Description: The destination couldnt be found due to severalreasons:

No route found

Not enough digits

Destination not connected

Length of the number incorrect

UNS_REQ_DEST_ERR for MOUT_NOT_PLMN

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

B-LTG

ISUP

C C | VLR

|||

MSC

CPMS

BS



CR(SERV_REQ)

CC(SERV DATA)

CC(CIPH CMD)

|||

DT1(SETUP)

DT1(TERMINATE)

* ERROR

DT1(CIPH COM)

DT1(SETUP)

->MSC: UNS_REQ_DEST_ERR for MOUT_NOT_PLMN

Fig. 49 UNS_REQ_DEST_ERR for MOUT_NOT_PLMN


76/106


77/106


78/106


79/106



79

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


80/106


81/106



81

MOC (Part 2 of 4)


IDENT_REQ

(IMEI?...)

IDENT_RESP

(IMEI)

TMSI_REAL_CMD

(---)

TMSI_REAL_COM

(---)

SETUP


DigitTranslation

IAM

CALL_P ROC

(---)

IMEI_CHECK

IAM

Digit

Translation














Start Po int


Start Po int


S t a r t Po i nt


S t a r t Po i nt

->MSC: REL_BEFORE_ACM

->MSC: UNS_TECHN_FAULT for MTRAN

->MSC: UNS_CONGESTION for MTRAN

- >M S C : U N S _ S N _ C O N G ES TION fo r M TR A N

- >M S C : U N S _ N ETW _ M A N A G EM EN T fo r M TR A N

- >M S C : U N S _ R EQ _ D ES T_ ER R fo r M TR A N



Fig. 53 Error on a subsequent MSC during the PLMN's routing of the call


82/106


MN2537EU01MN_0001

2003 Siemens AG

82

2.6.1 REL_BEFORE_ACM [NR]

Indicates how many calls are released in the forward direction before ACM is sent forMICTR

General Trigger Description: upon each release in forward direction

GMSC: before ACM is sent and after receipt of IAM

The call is incoming from PSTN or from another MSC (traffic type MICTR) and thenumber is not correct.

REL_BEFORE_ACM [NR]

indicates how many calls are released in the forward direction before ACM is

sent for MICTR

Trigger: upon each release in forward direction

GMSC: before ACM is sent and after receipt of IAM

The call is incoming from PSTN or from another MSC (traffic type

MICTR) and the number is not correct.

Fig. 54 REL_BEFORE_ACM: at the GMSC


83/106


84/106


85/106



85

2.6.4 UNS_SN_CONGESTION for MTRAN [NR]

Indicates how many calls are terminated due to switching network (SN) congestion.

General Trigger Description: each time a failure during SN through-connectionoccurs

UNS_SN_CONGESTION for MTRAN [NR]

indicates how many calls are terminated due to switching network

(SN) congestion.

Trigger: each time a failure during SN through-connection occurs

Fig. 57 UNS_SN_CONGESTION for MTRAN


86/106


MN2537EU01MN_0001

2003 Siemens AG

86

2.6.5 UNS_NETW_MANAGEMENT for MTRAN [NR]

indicates how many calls are terminated due to network management activities

General Trigger Description: outgoing trunk for transit traffic cannot be selectedand seized due to a network management failure.

UNS_NETW_MANAGEMENT for MTRAN

A-LTG B-LTG

|

|

MSC

CP

|

|

O:SEIZ

M: SEIZURE CA

HLRvisited

VLR

next

Exchange

O:ADDI DIG

* Seize trunk not successfulTERMINATE C

GMSC

M: DIG BLOCK C->MSC: UNS_NETW_MANAGEMENT for MTRAN

Fig. 58 UNS_NETW_MANAGEMENT for MTRAN


87/106



87

2.6.6 UNS_REQ_DEST_ERR for MTRAN [NR]

Indicates how many calls are terminated because the requested destination wasunknown, blocked or could not be charged for MTRAN. The destination couldnt befound due to several reasons

General Trigger Description: The destination couldnt be found due to severalreasons:

No route found

Not enough digits

Destination not connected

Length of the number incorrect

UNS_REQ_DEST_ERR for MTRAN

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

B-LTG

ISUP

C C|

VLR

|||

MSC

CPMS

BS



CR(SERV_REQ)

CC(SERV DATA)

CC(CIPH CMD)

|||

DT1(SETUP)

DT1(TERMINATE)* ERROR

DT1(CIPH COM)

DT1(SETUP)

->MSC: UNS_REQ_DEST_ERR for MTRAN

Fig. 59 UNS_REQ_DEST_ERR for MTRAN


88/106


89/106


90/106


MN2537EU01MN_0001

2003 Siemens AG

90

2.7.1 UNS_CONGESTION for MOUT_NOT_PLMN [NR]

indicates how many calls are terminated due to (trunk) congestion in the home MSC

General Trigger Description: each time a trunk (at B side) seizure is not successfuldue to congestion (No outgoing traffic trunk can be selected or seized)

UNS_CONGESTION

for

MOUT_NOT_PLMN

DT1(SEIZURE A BSSAP)

DT1(ASS REQ)

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

||

|

B-LTG

ISUP

C C|

VLR

||

|

CPMS

BS



CM SERV REQ)]

CR(SERV_REQ)

CC(SERV_DATA)

CC (CIPH CMD)

DT1 (CIPH COM)

DT1(SET UP)

DT1(SET UP)

DT1(CALL PROC)

DT1(ASS COM)

ASS COM

TERMINATE C* Seizing trunk is not successful

MSC

Call setup is terminated

->MSC:UNS_CONGESTION for

MOUT_NOT_PLMN

Fig. 61 UNS_CONGESTION for MOUT_NOT_PLMN


91/106



91

2.7.2 UNS_SN_CONGESTION for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated due to switching network (SN) congestion

General Trigger Description: each time a failure during SN through-connectionoccurs

Trigger 1: SN path selection is not successful

UNS_SN_CONGESTION

for MOUT_NOT_PLMN

Trigger 1:

SN path selection is not

successful

DT1(SEIZURE A BSSAP)

DT1(ASS REQ)

INV SUB ID

RES SUB ID

N E

E X

X C

T H| |

A-LTG

BSSAP

RR MM CC

|

||

B-LTG

ISUP

C C | VLR

|||

CPMS

BS



CR(SERV_REQ)

CC(SERV_DATA)

CC (CIPH CMD)

DT1 (CIPH COM)

DT1(SET UP)

DT1(SET UP)

* SN path selection not successfull

DT1(CALL PROC)

DT1(ASS COM)

ASS COM

TERMINATE

MSC

->MSC: UNS_SN_CONGESTION

for MOUT_NOT_PLMN

Fig. 62 UNS_SN_CONGESTION for MOUT_NOT_PLMN: trigger 1


92/106


93/106



93

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


94/106


95/106


96/106


97/106



97

MOC (Part 3 of 4)


ALERT / P ROG RES S





ACM

ANM

ACM

ANM





REL

(error)

->MSC: CALL_REL_EXCHANGE for MTRA N




S t o p P o i nt


Fig. 65 Error due to call terminated by a lower/upper network element


98/106


99/106



99

MOC (Part 3 of 4)


ALERT / P ROG RES S





ACM

ANM

ACM

ANM





->MSC: CALL_REL_BEF_ A_ALERT for MOUT_NOT_PLMN

RELEASE COMPLETE

REL

(error)

->MSC: CALL_REL_BEF_ ALERT for MTRAN




S t o p P o i nt


Fig. 66 Error due to call terminated by the A party before ALERT


100/106


101/106



101

MOC (Part 3 of 4)


ALERT / P ROG RES S





ACM

ANM

ACM

ANM





->MSC: CALL_REL_A_ ALERT for MOUT_NOT_PLMN

->MSC: CALL_TIOUT_ALERT for M OUT_NOT_PLMM

RELEASE COMPLETE

REL

(error)

->MSC: CALL_REL_ALERT for MTRA N




S t o p P o i nt


Fig. 67 Error due to call terminated by the A party during ALERT or due to TIME OUT


102/106


103/106



103

MOC (Part 4 of 4)


Act ivity Ph as e o f the C all

CONNECT

CONNECT_ACKNOWLEDGE

->INTCREL: REL_CALL_BS_ REASONRESET

(Error)

Fig. 68 Call terminated during SETUP due to radio problems


104/106


105/106



105

MOC (Part 4 of 4)


Act ivity Ph as e o f the C all

CONNECT

CONNECT_ACKNOWLEDGE

->MSC: BS_ REL_WITH_ANS WER for MOUT_NOT_PLMN

->INTCREL: REL_ANSW_ CALL_BS _REAS ONRESET

(Error)

Fig. 69 Abnormal release of the call after the ANSWER message


106/106

The Mobile Originating Call Traffic Data

Documents

Transcript of The Mobile Originating Call Traffic Data