Sunteți pe pagina 1din 0

The Mobile Originating Call (MOC) traffic data Siemens

MN2537EU01MN_0001
2003 Siemens AG
1
Contents
1 The mobile originating call 3
1.1 The arriving of the service request to the MSC 4
1.2 The authentication procedure 6
1.3 The ciphering procedure 6
1.4 The IMEI check procedure 8
1.5 The TMSI reallocation procedure 8
1.6 The arrival of the setup message 10
1.7 The digit translation 12
1.8 The SN seizure and the arriving of the call to the G-MSC 14
1.9 The G-MSC SN seizure and the routing of the call to the partner
network 16
1.10 The traffic channel assignment 18
1.11 The call setup termination 20
1.12 The ANSWER by the B party 22
1.13 The normal release of the call 24
2 What may go wrong on a MOC 31
2.1 Error detected with/after the CM SERVICE REQUEST message 32
2.2 Technical or MS error detected during authentication 48
2.3 Error at (or before) the reception of the SETUP message 54
2.4 Error during the call routing on the MORTR traffic type 66
2.5 Error with the call routing on the MOUT NOT PLMN traffic type 72
2.6 Error on a subsequent MSC during the PLMN's routing of the call 80
2.7 Error after the TCH ASSIGNMENT phase 88
2.8 Error due to call terminated by a upper network element 94
2.9 Error due to call terminated by a lower/upper network element 96
2.10 Error due to call terminated by the A party before ALERT 98
2.11 Error due to call terminated by the A party during ALERT or due to
TIME OUT 100
2.12 Call terminated during SETUP due to radio problems 102
The Mobile Originating Call (MOC) traffic
data
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


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
3
1 The mobile originating call

On this chapter only MSC, VLR and INTCELL (INTCREL) traffic data will be
analyzed.
The INTCELL traffic data is the last "core" measurement to be analyzed, during a
suspicious or error situation, before the handover to the BSS team. Can be also used
for the construction of cell based traffic data at the MSC.
Siemens The Mobile Originating Call (MOC) traffic data


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 the
MSC. 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 the
received BS or TS
Trigger: upon receipt of each CM SERVICE REQUEST with SERVICE
TYPE = mobile originating call or establishment of all emergency call
attempts (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 call
is received

TRAFFIC_VOLUME for MORTR [sec]
Indicates the sum of all holding times
Trigger:
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 service
type:
- mobile originating call
- emergency call

Short message service and SS activation are not included

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
5

MOC (Part 1 of 4)
MS BSS MSC / VLR G-MSC / VLR CHN_REQ
(Se rvice , Re as o n,...)
CHN_ASSIG
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
CC
(Co n. Co nfirme d)
AUTH_REQ
(CKSN, RAND)
AUTH_RESP
(SRES)
CIP HER_MODE_CMD
(K5, A5x)
CIP HER_MOD_CMD
(A5x)
CIP HER_MODE_COM
(---)
CIP HER_MOD_COM
(---)
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
- >MS C: CALL_ ATTEMPTS f o r MORTR
- >MS C: EMERGENCY_ TS 12 _ ATTEMPTS
- >MS C: TRAFFIC_ VOLUME f o r MORTR
S t art Po i nt
- >INTCREL: ORIG_ CALL_ ATTEMPTS

Fig. 1 The arriving of the service request to the MSC
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
6

1.2 The authentication procedure

As has been discussed on the Location Registration/Update procedure, one single
counter 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 VLR
counters presented bellow are responsible for the collection of the Ciphering traffic
data.

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

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
7

MOC (Part 1 of 4)
MS BSS MSC / VLR G-MSC / VLR CHN_REQ
(Se rvice , Re as o n,...)
CHN_ASSIG
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
CC
(Co n. Co nfirme d)
AUTH_REQ
(CKSN, RAND)
AUTH_RESP
(SRES)
CIP HER_MODE_CMD
(K5, A5x)
CIP HER_MOD_CMD
(A5x)
CIP HER_MODE_COM
(---)
CIP HER_MOD_COM
(---)
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
- >MS C: CALL_ ATTEMPTS f o r MORTR
- >MS C: EMERGENCY_ TS 12 _ ATTEMPTS
- >MS C: TRAFFIC_ VOLUME f o r MORTR
S t art Po i nt
- >VLR: AUTH_ REQ
- >VLR: CIPHERING_ REQ
- >VLR: S UCC_ CIPH_ MODE_ CTRL_ PROC
- >INTCREL: ORIG_ CALL_ ATTEMPTS

Fig. 2 The Authentication procedure and the Ciphering procedure
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
8

1.4 The IMEI check procedure

The IMEI Check procedure is used for mobile equipment (ME) network access
authorization.
From the quite complete set of counters available for it's monitoring we will analyze
only 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 in
response to check IMEI at call setup


1.5 The TMSI reallocation procedure

The counters, which may be used for the TMSI reallocation monitoring, are present
on 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 ACC
containing 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 from
MS/BSC




The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 3 The IMEI Check procedure and the TMSI reallocation procedure
Siemens The Mobile Originating Call (MOC) traffic data


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 B
number 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 place
and will be present on a later stage of the MOC procedure.



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
11

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 4 The arrival of the Setup message
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
12

1.7 The digit translation

The B number Digit Translation will normally result on the seizure of the call
destination, 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 the
following 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 speech
followed by data services
Trigger: each time the digit analysis after interrogation results in the
MOUT_NOT_PLMN traffic type

DED_PAD_ATTEMPTS [NR]
indicates how many call attempts to a foreign network for dedicated PAD
access services have taken place for MOUT_NOT_PLMN
Trigger: each time the digit analysis after interrogation results in the
MOUT_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 final
destination is achieved.
stops: when RELEASE COMPLETE is sent or received, or with an
unsuccessful call attempt before IAM is sent

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
13

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 5 The Digit Translation
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
14

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

The ISUP message IAM (Initial Address Message) will trigger counters on both sides
of 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 SN
and the performing of the COC)

At the GMSC:

CALL_ATTEMPTS for MICTR [NR]
indicates how many call attempts have taken place, independently of the
received BS or TS
Trigger: each time IAM is received (all call attempts)

TRAFFIC_VOLUME for MICTR [sec]
indicates the sum of all holding times
Trigger:
starts: each time IAM is received
stops: each time RELEASE COMPLETE is received

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
15

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: S N_ THROUGH_ CONNECTIONS f o r MOUT_ NOT_ PLMN
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: CALL_ ATTEMPTS f o r MICTR
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MICTR
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 6 The SN seizure and the GMSC first contact

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
16

1.9 The G-MSC SN seizure and the routing of the call
to 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 of
the 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 SN
and 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 outgoing
traffic (all call attempts)

TRAFFIC_VOLUME for MTRAN [sec]
indicates the sum of all holding times
Trigger:
starts: with proper result of the digit analysis.
stops: when RELEASE COMPLETE is received

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
17

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: S N_ THROUGH_ CONNECTIONS f o r MOUT_ NOT_ PLMN
- >MS C: S N_ THROUGH_ CONNECTIONS f o r MTRAN
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: CALL_ ATTEMPTS f o r MICTR
- >MS C: CALL_ ATTEMPTS f o r MTRAN
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MICTR
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MTRAN
S t art Po i nt
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC
- >MS C: TRAFFIC_ VOLUME f o r
MTRAN

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


Siemens The Mobile Originating Call (MOC) traffic data


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 successfully
completed 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 successfully
completed 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 channel
request
Trigger: with an originating call, each time ASSIGNMENT REQUEST is
sent to the BSC

ORIG_CALL_SUCC_TCH_ALLOC [NR]
indicates the number of mobile originating calls with successful traffic
channel allocation

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
19

Trigger: each time ASSIGNMENT COMPLETE is received without
previous 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)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ

Fig. 8 The Traffic Channel assignment

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
20

1.11 The call setup termination

The ASSIGNMENT COMPLETE message marks also the CALL SETUP end from the
traffic measurement point of view. So, the following "CALL SETUP" counters will also
be 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 the
calculation of the average setup time)


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
21

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB

Fig. 9 The Call Setup termination
Siemens The Mobile Originating Call (MOC) traffic data


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 this
stage. The TV_WA counters will run until the call has been drop or normally released
by 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 3
service
Trigger:
starts: each time ANSWER is received
stops: each time call is released

At the GMSC:

DUR_OF_CONVERSATION [sec]
indicates duration of conversation for MTRAN
Trigger:
starts: each time ANSWER is received
stops: each time call is released

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
23

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB
- >MS C: DUR_ OF_ CONV_ S PEECH_ S ERV f o r MOUT_ NOT_ PLMN
- >MS C: DUR_ OF_ CONV_ FAX3 f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >MS C: DUR_ OF_ CONVERS ATION
S t art Po i nt

Fig. 10 The call ANSWER
Siemens The Mobile Originating Call (MOC) traffic data


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 with
Answer" 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 to
facsimile
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 followed
by 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 the
receipt 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 the
receipt of ANM

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
25

The following counter allows the acquisition of the number of answered calls These
are part of the total number of initiated calls by the MSUB of the measured cell. As for
the previously seen MSC counter, the "answer without error" INTCELL counters are
only incremented with the "normal release of the call".

At the VMSC and for each cell

ANSW_ORIG_CALL [NR]
indicates the number of answered calls for MORTR
Trigger: release of call when previous CONNECT ACK is received

MOC (Part 4 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
Activity P has e o f the Call
CONNECT
CONNECT_ACKNOWLEDGE
DIS CONNECT
(Nor ma l)
RELEAS E
(Nor mal)
- >MS C: S PEECH_ CALLS _ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: TS 11_ EMERG_ WITH_ ANS WER
- >MS C: TS 12 _ EMERG_ WITH_ ANS WER
- >MS C: DATACDA_ ANA_ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ANS WER f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ WITH_ ANS WER
- >INTCREL: ANS W_ ORIG_ CALL
DIS CONNECT
(Nor ma l)
RELEAS E
(Nor mal)
- >MS C: CALLS _ WITH_ ANS WER
REL
REL

Fig. 11 The normal call release

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
26

Both the normal and the abnormal release of the active call will have as a direct
consequence the running stop of all the TV previously involved on the traffic
measurement. It will happen in both the "Forward Release" and "Backward Release"
situations.

First the TV_WA counters:

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 3
service
Trigger:
starts: each time ANSWER is received
stops: each time call is released

At the GMSC:

DUR_OF_CONVERSATION [sec]
indicates duration of conversation for MTRAN
Trigger:
starts: each time ANSWER is received
stops: each time call is released

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
27

FORWARD RELEASE
MS BSS MSC / VLR HLR / AC G-MSC / VLR
REL
RLC
DISCONNE CT
(Re as o n)
RELEASE
(Re as o n)
RELEASE_COMP LETE
(Re as o n)
Re le as e o f Re s o urce s
- >MS C: TRAFFIC_ VOLUME f o r MORTR
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t o p Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MICTR
- >MS C: TRAFFIC_ VOLUME f o r MTRAN
S t o p Po i nt
RLC
- >MS C: DUR_ OF_ CONV_ S PEECH_ S ERV f o r MOUT_ NOT_ PLMN
- >MS C: DUR_ OF_ CONV_ FAX3 f o r MOUT_ NOT_ PLMN
S t o p p o i nt
REL
- >MS C: DUR_ OF_ CONVERS ATION
S t o p Po i nt

Fig. 12 The normal call release forward release

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
28

And now the TV counters:

At the VMSC:

TRAFFIC_VOLUME for MORTR [sec]
indicates the sum of all holding times
Trigger:
starts: each time CM SERVICE REQUEST is received
stops: each time RELEASE COMPLETE is received

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 final
destination is achieved.
stops: when RELEASE COMPLETE is sent or received, or with an
unsuccessful call attempt before IAM is sent

At the GMSC:

TRAFFIC_VOLUME for MICTR [sec]
indicates the sum of all holding times
Trigger:
starts: each time IAM is received
stops: each time RELEASE COMPLETE is received

TRAFFIC_VOLUME for MTRAN [sec]
indicates the sum of all holding times
Trigger:
starts: with proper result of the digit analysis.
stops: when RELEASE COMPLETE is received

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
29

BACKWARD RELEASE
MS BSS MSC / VLR HLR / AC G-MSC / VLR
REL
RLC
RELEASE
(Re as o n)
RELEASE_COMP LETE
(Re as o n)
Re le as e o f Re s o urce s
- >MS C: TRAFFIC_ VOLUME f o r MORTR
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t o p Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MICTR
- >MS C: TRAFFIC_ VOLUME f o r MTRAN
S t o p Po i nt
RLC
- >MS C: DUR_ OF_ CONV_ S PEECH_ S ERV f o r MOUT_ NOT_ PLMN
- >MS C: DUR_ OF_ CONV_ FAX3 f o r MOUT_ NOT_ PLMN
S t o p p o i nt
- >MS C: DUR_ OF_ CONVERS ATION
S t o p Po i nt

Fig. 13 The normal call release backward release
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
30


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
31

2 What may go wrong on a MOC
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
32

2.1 Error detected with/after the CM SERVICE
REQUEST 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.

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
33

MOC (Part 1 of 4)
MS BSS MSC / VLR G-MSC / VLR CHN_REQ
(Se rvice , Re as o n,...)
CHN_ASSIG
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
CC
(Co n. Co nfirme d)
AUTH_REQ
(CKSN, RAND)
AUTH_RESP
(SRES)
CIP HER_MODE_CMD
(K5, A5x)
CIP HER_MOD_CMD
(A5x)
CIP HER_MODE_COM
(---)
CIP HER_MOD_COM
(---)
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
- >MS C: CALL_ ATTEMPTS f o r MORTR
- >MS C: EMERGENCY_ TS 12 _ ATTEMPTS
- >MS C: TRAFFIC_ VOLUME f o r MORTR
S t art Po i nt
- >MS C: UNS _ REQ_ DES T_ ERR f o r MORTR
- >MS C: UNS _ TECHN_ FAULT f o r MORTR
- >MS C: UNS _ S ERV_ CHECK f o r MORTR
- >MS C: UNS _ CONGES TION f o r MORTR
- >MS C: UNS _ PROTO_ ERROR f o r MORTR
- >MS C: UNS _ OVERLOAD f o r MORTR
- >INTCREL: ORIG_ CALL_ ATTEMPTS

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

Siemens The Mobile Originating Call (MOC) traffic data


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 was
unknown, blocked or could not be charged
General Trigger Description: the counter is incremented upon receiving a message
indicating 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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection
NRELAY:[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


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
35

Trigger 2: result from INV SUB DATA is not successful: IMSI (MSUB) is unknown

UNS_REQ_DEST_ERR for MORTR
Trigger 2: result from INV SUB DATA is not successful: IMSI (MSUB) is
unknown
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection
NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
DT1(CM SERV REJ)
DT1(CM SERV REJ)
|
|
|
RES SUB DATA
INV SUB DATA
* ERROR: IMSI unknown
->MSC: UNS_REQ_DEST_ERR for MORTR

Fig. 16 UNS_REQ_DEST_ERR for MORTR: trigger 2
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
36

2.1.2 UNS_TECHN_FAULT for MORTR [NR]

This counter registers the number of calls that are released because of technical
faults in the measured MSC (e.g. software fault, plausibility check, hardware fault).
The call is released before the digit translation.
General Trigger Description: each time the MSC causes a technical fault (e.g.
software fault, plausibility check, hardware fault). Each time a forced release occurs
without any specific reason

Trigger 1: The message CC(SERV_DATA) was not successfully sent from MSC to
A-LTG BSSAP after receiving the message RES_SUB_ID.
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_ID

UNS_TECHN_FAULT for MORTR
Trigger 1: The message CC(SERV_DATA) was not successfully sent from
MSC to A-LTG BSSAP after receiving the message RES_SUB_ID.
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_ID
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CREF
CREF
* encoding error or network failure
->MSC: UNS_TECHN_FAULT for MORTR

Fig. 17 UNS_TECHN_FAULT for MORTR: trigger 1


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
37

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

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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
INV SUB DATA
RES SUB DATA
CREF
CREF
* encoding error or network failure
->MSC: UNS_TECHN_FAULT for MORTR

Fig. 18 UNS_TECHN_FAULT for MORTR: trigger 2
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
38

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

UNS_TECHN_FAULT for MORTR
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO / CM
SERV REQ)]
CR(SERV_REQ)
* INTERNAL ERROR
CREF
CREF
->MSC: UNS_TECHN_FAULT for MORTR

Fig. 19 UNS_TECHN_FAULT for MORTR: trigger 3


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
39

2.1.3 UNS_SERV_CHECK for MORTR [NR]

indicates how many calls are terminated due to negative service facility checks or
negative compatibility checks
General Trigger Description: RELEASE COMPLETE (with the proper reason) is
sent to the BSS

Trigger 1:
a transaction with IMEI is not allowed,
a transaction with IMEI is not allowed for an SIM-less emergency call,
roaming is not allowed

UNS_SERV_CHECK for MORTR
Trigger 1: - a transaction with IMEI is not allowed,
- a transaction with IMEI is not allowed for an SIM-less emergency
call,
- roaming is not allowed
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CREF(CM_SERV_REJ)
CREF (CM_SERV_REJ)
->MSC: UNS_SERV_CHECK for MORTR

Fig. 20 UNS_SERV_CHECK for MORTR: trigger 1
Siemens The Mobile Originating Call (MOC) traffic data


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 due
to congestion

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

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
|
|
|
|
SSP VLR
|
|
|
MSC
A-LTG
BSSAP
CP
CR(COMPL L3 INFO[CM SERV REQ])
CREF
->MSC: UNS_CONGESTION for MORTR

Fig. 21 UNS_CONGESTION for MORTR: trigger 1


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
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 call
could 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 X
X C
T H
|
|
|
|
A-LTG
BSSAP
RR MM CC
|
|
|
|
B-LTG
ISUP
C C
|
|
VLR
|
|
|
|
MSC
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
CREF
* info invalid
->MSC: UNS_PROTO_ERROR for MORTR

Fig. 22 UNS_PROTO_ERROR for MORTR: trigger 1
Siemens The Mobile Originating Call (MOC) traffic data


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

UNS_PROTO_ERROR for MORTR
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
* not successfully decoded
or info invalid
->MSC: UNS_PROTO_ERROR for MORTR

Fig. 23 UNS_PROTO_ERROR for MORTR: trigger 2

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




The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
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 an
overload 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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[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
Siemens The Mobile Originating Call (MOC) traffic data


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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
overload
CREF(CM SERV REJ)
->MSC: UNS_OVERLOAD for MORTR

Fig. 25 UNS_OVERLOAD for MORTR: trigger 2


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
45

2.1.7 UNS_SECURITY_FAIL for MORTR [NR]

indicates how many calls are terminated due to authentication/security failure
General Trigger Description: each time AUTHENTICATION REJECT is sent to the
BSS

Trigger 1: result of INV SUB ID not successful

* security failure
UNS_SECURITY_FAIL for MORTR
Trigger 1: result of INV SUB ID 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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CREF
CREF
->MSC: UNS_SECURITY_FAIL for MORTR

Fig. 26 UNS_SECURITY_FAIL for MORTR: trigger 1
Siemens The Mobile Originating Call (MOC) traffic data


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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
INV SUB DATA
RES SUB DATA
CREF
CREF
->MSC: UNS_SECURITY_FAIL for MORTR

Fig. 27 UNS_SECURITY_FAIL for MORTR: trigger 2


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
47

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
48

2.2 Technical or MS error detected during
authentication

Counters that may be involved on an error situation:

At the VMSC

UNS_REQ_DEST_ERR for MORTR [NR]
UNS_SECURITY_FAIL for MORTR [NR]

At the VVLR

AUTH_WITH_ILLEGAL_SUB [NR]
indicates the number of authentications with outcome illegal subscriber
Trigger: each time AUTHENTICATION REJECT indicating illegal MS is
sent to BSC/MS

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

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
49

MOC (Part 1 of 4)
MS BSS MSC / VLR G-MSC / VLR CHN_REQ
(Se rvice , Re as o n,...)
CHN_ASSIG
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
CC
(Co n. Co nfirme d)
AUTH_REQ
(CKSN, RAND)
AUTH_RESP
(SRES)
CIP HER_MODE_CMD
(K5, A5x)
CIP HER_MOD_CMD
(A5x)
CIP HER_MODE_COM
(---)
CIP HER_MOD_COM
(---)
CM_SERV_REQ
(Se rvice Type , CKSN,
TMSI,...)
- >MS C: CALL_ ATTEMPTS f o r MORTR
- >MS C: EMERGENCY_ TS 12 _ ATTEMPTS
- >MS C: TRAFFIC_ VOLUME f o r MORTR
S t art Po i nt
- >MS C: UNS _ REQ_ DES T_ ERR f o r MORTR
- >MS C: UNS _ S ECURITY_ FAIL f o r MORTR
- >VLR: AUTH_ REQ
- >INTCREL: ORIG_ CALL_ ATTEMPTS
AUTH__REJ
- >VLR: AUTH_ WITH_ ILLEGAL_ S UB

Fig. 28 Technical or MS error detected during Authentication

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
50

2.2.1 UNS_REQ_DEST_ERR for MORTR [NR]

Indicates how many calls are terminated because the requested destination was
unknown, blocked or could not be charged
General Trigger Description: the counter is incremented upon receiving a message
indicating an internal release (CP):
- after a failed operation
- after a failed digit analysis

Trigger 3: the authentication retry procedure is unsuccessful due to unknown
subscriber

UNS_REQ_DEST_ERR for MORTR
Trigger 3: the authentication retry procedure is unsuccessful due to
unknown subscriber
N E
E X
X C
T H
|
|
|
|
A-LTG
BSSAP
RR MM CC
|
|
|
B-LTG
ISUP
C C
|
|
VLR
|
|
|
MSC
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
INV SUB ID
RES SUB ID
DT1(SEC ERROR)
CC(SERV_DATA)
CC (AUTH REQ)
DT1 (AUTH RES)
DT1(ID REQ)
DT1(ID REQ)
DT1(ID RES) DT1(ID RES)
DT1(AUTH REQ)
DT1(AUTH REQ)
DT1(AUTH RES) DT1(AUTH RES)
RES AUTH CREF
CREF
* unknown subscriber
->MSC: UNS_REQ_DEST_ERR for MORTR

Fig. 29 UNS_REQ_DEST_ERR for MORTR: trigger 3




The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
51

2.2.2 UNS_SECURITY_FAIL for MORTR [NR]

indicates how many calls are terminated due to authentication/security failure
General Trigger Description: each time AUTHENTICATION REJECT is sent to the
BSS

Trigger 3: authentication retry failure

UNS_SECURITY
_FAIL for
MORTR
Trigger 3:
authentication retry
failure
N E
E X
X C
T H
|
|
|
|
A-LTG
BSSAP
RR MM CC
|
|
|
|
B-LTG
ISUP
C C
|
|
VLR
|
|
|
|
MSC
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
INV SUB ID
RES SUB ID
DT1(SEC ERROR)
CC(SERV_DATA)
CC (AUTH REQ)
DT1 (AUTH RES)
DT1(ID REQ) DT1(ID REQ)
DT1(ID RES)
DT1(ID RES)
DT1(AUTH REQ)
DT1(AUTH REQ)
DT1(AUTH RES)
DT1(AUTH RES)
RES AUTH
CREF
CREF
* security failure
->MSC: UNS_SECURITY_FAIL for MORTR

Fig. 30 UNS_SECURITY_FAIL for MORTR: trigger 3
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
52

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

UNS_SECURITY_FAIL for MORTR
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
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 AUTH
CREF
CREF
* illegal MS
->MSC: UNS_SECURITY_FAIL for MORTR

Fig. 31 UNS_SECURITY_FAIL for MORTR: trigger 4


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
53

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
54

2.3 Error at (or before) the reception of the SETUP
message

The counters involved on the error detection may be:

at the VMSC

UNS_BS_REASON for MORTR
UNS_TECHN_FAULT for MORTR
UNS_SERV_CHECK for MORTR
UNS_MS_BLOCKED for MORTR
UNS_LACK_IWE for MORTR
UNS_PROTO_ERROR for MORTR
UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
55

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: UNS _ B S _ REAS ON f o r MORTR
- >MS C: UNS _ TECHN_ FAULT f o r MORTR
- >MS C: UNS _ S ERV_ CHECK f o r MORTR
- >MS C: UNS _ MS _ BLOCKED f o r MORTR
- >MS C: UNS _ LACK_ IWE f o r MORTR
- >MS C: UNS _ PROTO_ ERROR f o r MORTR
- >MS C: UNS _ NETW_ MANAGEMENT f o r MOUT_ NOT_ PLMN
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 32 Error at (or before) the reception of the SETUP message
Siemens The Mobile Originating Call (MOC) traffic data


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-related
reasons
General Trigger Description: each time RELEASE COMPLETE/CLEAR REQUEST
or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received from the BSS
before digit analysis is performed

The condition for the UNS_BS_REASON for MORTR increment is the occurrence of
a 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 or
SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received
from the BSS before digit analysis is performed

Fig. 33 UNS_BS_REASON for MORTR


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
57

2.3.2 UNS_TECHN_FAULT for MORTR [NR]

This counter registers the number of calls that are released because of technical
faults in the measured MSC (e.g. software fault, plausibility check, hardware fault).
The call is released before the digit translation.
General Trigger Description: each time the MSC causes a technical fault (e.g.
software fault, plausibility check, hardware fault). Each time a forced release occurs
without any specific reason

Trigger 4: the CP detects an error in DT1 (SET UP) from the A-LTG during a normal
call or during an emergency call

UNS_TECHN_FAULT for MORTR
Trigger 4: the CP detects an error in DT1(SET UP) from the A-LTG during a normal
call or during an emergency call
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC: UNS_TECHN_FAULT for MORTR

Fig. 34 UNS_TECHN_FAULT for MORTR: trigger 4


Siemens The Mobile Originating Call (MOC) traffic data


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 or
negative compatibility checks
General Trigger Description: RELEASE COMPLETE (with the proper reason) is
sent to the BSS

Trigger 4: error in BC-check for emergency call

UNS_SERV_CHECK for MORTR
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
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


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
59

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

UNS_SERV_CHECK for MORTR
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT (SET UP)
DT1(SET UP)
CLIR INVOCATION CLIR not allowed
Service not
provisioned
->MSC: UNS_SERV_CHECKfor MORTR

Fig. 36 UNS_SERV_CHECK for MORTR: trigger 5
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
60

2.3.4 UNS_MS_BLOCKED for MORTR [NR]

Number of calls terminated because the subscriber was blocked by ODB, by
administration or by SS. Because there are unblockable destinations, the destination
must be determined if the described barring conditions are fulfilled
General Trigger Description: MSUB has barring of outgoing calls (calling
subscriber) or barring incoming calls (called subscriber)

WARNING
When after digit translation the mobile traffic type is changed to MOUT_PLMN or
MOUT_NOT_PLMN, the counter is also updated for MORTR

Trigger 1: When digit analysis results in an IN-SERVICE, the call can be rejected
due to call barring

UNS_MS_BLOCKED for MORTR
Trigger 1: When digit_analysis results in an IN-SERVICE, the call can
be rejected due to call barring
MS
BS
N E
E X
X C
T H
S
C
P
|
|
|
|
CCF SSF TCAP
|
|
|
B-LTG
ISUP
C C
|
|
|
|
SSP VLR
|
|
|
MSC
A-LTG
BSSAP
CP
CC (CIPH CMD)
DT1 (CIPH COM)
INV SUB ID
RES SUB ID
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
DT1(SET UP)
DT1(SET UP)
Digit Analysis
Result = IN_Service
Call is barred
Read SUB DATA
DT1(ASSIGN_INTERCEPT)
->MSC: UNS_MS_BLOCKED for MORTR

Fig. 37 UNS_MS_BLOCKED for MORTR: trigger 1



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
61

Trigger 2: After digit translation is checked if this call has to be barred (SS barring for
outgoing calls or ODB)

UNS_MS_BLOCKED for MORTR
Trigger 2: After digit translation is checked if this call has to be barred
(SS barring for outgoing calls or ODB)
MS
BS
N E
E X
X C
T H
S
C
P
|
|
|
|
CCF SSF TCAP
|
|
|
B-LTG
ISUP
C C
|
|
|
|
SSP VLR
|
|
|
MSC
A-LTG
BSSAP
CP
CC (CIPH CMD)
DT1 (CIPH COM)
INV SUB ID
RES SUB ID
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
DT1(SET UP)
DT1(SET UP)
Digit Analysis
Read SUB DATA
DT1(TERMINATE)
->MSC: UNS_MS_BLOCKED for MORTR

Fig. 38 UNS_MS_BLOCKED for MORTR: trigger 2
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
62

2.3.5 UNS_LACK_IWE for MORTR [NR]

Indicates how many calls are terminated due to lack of IWE
General Trigger Description: a mobile originating data call is terminated because
an IWE cannot be selected (unavailable IWE)

UNS_LACK_IWE for MORTR
* IWE availability check negative
INV SUB ID
RES SUB ID
N E
E X
X C
T H
|
|
|
|
A-LTG
RR MM CC
|
|
|
B-LTG
TRUNK
C C
|
|
VLR
|
|
|
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
DT1(TERMINATE)
MSC
|
|
|
IWF
LTG
->MSC: UNS_LACK_IWE for MORTR

Fig. 39 UNS_LACK_IWE for MORTR


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
63

2.3.6 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 call
could be identified

Trigger 3:
- unsuccessful decoding of DT1(SET UP)
- Internal (software) errors encountered with digit handling

UNS_PROTO_ERROR
for MORTR
Trigger 3:
- unsuccessful decoding of
DT1(SET UP)
-Internal (software) errors
encountered with digit handling
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC: UNS_PROTO_ERROR for MORTR

Fig. 40 UNS_PROTO_ERROR for MORTR: trigger 3

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
64


Trigger 4: with respect to emergency calls:
- Unsuccessful decoding of DT1 (EMERGENCY SET UP)
- Internal (software) errors encountered with digit handling

UNS_PROTO_ERROR
for MORTR
Trigger 4:
with respect to emergency
calls
-unsuccessful decoding of
DT1(EMERGENCY SET
UP)
- internal (software) errors
encountered with digit
handling
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(EMERGENCYSET UP)
DT1(EMERGENCY SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC: UNS_PROTO_ERROR for MORTR

Fig. 41 UNS_PROTO_ERROR for MORTR: trigger 4




The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
65

2.3.7 UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated due to network management activities
General Trigger Description: each time trunk resource management detects a
network management event

Trigger 1: the message DT1 (EMERGENCY_SET_UP) was received and no
emergency number was found

UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN
Trigger 1:
The message
DT1(EMERGENCY_SET_UP)
was received and no
emergency number was found
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(EMERGENCY SET UP)
DT1(EMERGENCY SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC UNS_NETW_MANAGEMENT
for MOUT_NOT_PLMN

Fig. 42 UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN: trigger 1


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
66

2.4 Error during the call routing on the MORTR traffic
type

Counters that may be involved on errors detection:

at the VMSC

UNS_CONGESTION for MORTR
UNS_OVERLOAD for MORTR

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
67

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)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >MS C: UNS _ CONGES TION f o r MORTR
- >MS C: UNS _ OVERLOAD f o r MORTR
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

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

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
68

2.4.1 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 due
to congestion

Trigger 2: BSSAP trunk for a MOC cannot be allocated due to congestion

Trigger 3: BSSAP trunk for an originating emergency cannot be allocated due to
congestion

UNS_CONGESTION for MORTR
Trigger 2: BSSAP trunk for a MOC cannot be allocated due to congestion
Trigger 3: BSSAP trunk for an originating emergency cannot be allocated due to
congestion
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
* Seizure trunk not successfull
->MSC: UNS_CONGESTION for MORTR

Fig. 44 UNS_CONGESTION for MORTR: trigger 2 and trigger 3



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
69

Trigger 4: while performing a new call attempt, after a failing COC no trunk can be
allocated due to congestion

UNS_CONGESTION
for MORTR
Trigger 4:
while performing a new call
attempt, after a failing COC
no trunk can be allocated due
to congestion
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
|
|
|
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
* Seizure trunk not successfull
DT1(CALL PROC)
DT1(ASS COM)
ASS COM
FAILURE C
SET UP C
SEIZURE CBT
COC FAILURE
CLEAR ACK
CLEAR
RELEASE C
REROUTE BSSAP
DT1(REL COM)
TERMINATE
MSC
->MSC: UNS_CONGESTION for MORTR

Fig. 45 UNS_CONGESTION for MORTR: trigger 4
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
70

2.4.2 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 an
overload situation

Trigger 3: CCNC overload initiation when routing during setup

UNS_OVERLOAD for MORTR
Trigger 3: CCNC overload initiation when routing during setup
MS
BS
N E
E X
X C
T H
S
C
P
|
|
|
|
CCF SSF TCAP
|
|
|
|
B-LTG
ISUP
C C
|
|
|
|
SSP VLR
|
|
|
|
MSC
A-LTG
BSSAP
CP
CC (CIPH CMD)
DT1 (CIPH COM)
INV SUB ID
RES SUB ID
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
DT1(SET UP)
DT1(SET UP)
overload
DT1(TERMINATE)
DT1(REL_COM)
->MSC: UNS_OVERLOAD for MORTR

Fig. 46 UNS_OVERLOAD for MORTR: trigger 3


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
71

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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



Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
72

2.5 Error with the call routing on the MOUT NOT
PLMN traffic type

The counters involved on the error detection may be:

at the VMSC

UNS_TECHN_FAULT for MOUT_NOT_PLMN
UNS_REQ_DEST_ERR for MOUT_NOT_PLMN
UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN
UNS_BS_REASON for MOUT_NOT_PLMN



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
73

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, Be are r Se rviceI)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >MS C: UNS _ TECHN_ FAULT f o r MOUT_ NOT_ PLMN
- >MS C: UNS _ REQ_ DES T_ ERR f o r MOUT_ NOT_ PLMN
- >MS C: UNS _ NETW_ MANAGEMENT f o r MOUT_ NOT_ PLMN
- >MS C: UNS _ B S _ REAS ON f o r MOUT_ NOT_ PLMN
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

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

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
74

2.5.1 UNS_TECHN_FAULT for MOUT_NOT_PLMN [NR]

This counter registers the number of calls that are released after the digit translation
because of technical faults in the measured MSC (e.g. software fault, plausibility
check, hardware fault)
General Trigger Description: each time the MSC causes a technical fault (e.g.
software fault, plausibility check, hardware fault). Each time a forced release occurs
without any specific reason

Trigger 1: on a normal and on a emergency call DT1(SEIZURE A BSSAP) cannot be
sent due to lack of resources or an encoding error

Trigger 2: speech channel allocation was unsuccessful due to internal software
problems

* SEIZURE_A_BSSAP impossible
due to encoding/resource problems
Trigger 1:
On a normal and on a
emergency call
DT1(SEIZURE A BSSAP)
cannot be sent due to lack
of resources or an
encoding error
Trigger 2:
Speech chanell allocation
was unsuccessful due to
internal software problems
UNS_TECHN_FAULT for MOUT_NOT_PLMN
->MSC: UNS_TECHN_FAULT for MOUT_NOT_PLMN

Fig. 48 UNS_TECHN_FAULT for MOUT_NOT_PLMN: trigger 1; trigger 2


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
75

2.5.2 UNS_REQ_DEST_ERR for MOUT_NOT_PLMN [NR]

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

General Trigger Description: The destination couldnt be found due to several
reasons:
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
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
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
76

2.5.3 UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated due to network management activities
General Trigger Description: each time trunk resource management detects a
network management event

Trigger 1: the message DT1 (EMERGENCY_SET_UP) was received and no
emergency number was found

UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN
Trigger 1:
The message
DT1(EMERGENCY_SET_UP)
was received and no
emergency number was found
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(EMERGENCY SET UP)
DT1(EMERGENCY SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC UNS_NETW_MANAGEMENT
for MOUT_NOT_PLMN

Fig. 50 UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN: trigger 1



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
77

Trigger 2:
Impossible to allocate a BSSAP trunk
Trunk selection or trunk reservation not successful
Digit translation unsuccessful after SET UP due to network management activities

Trigger 2:
-impossible to allocate a
BSSAP trunk
- trunk selection or trunk
reservation not successful
- digit translation unsuccessful
after SET UP due to network
management activities
UNS_NETW_MANAGEMENT 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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
CR(SERV_REQ)
CC(SERV_DATA)
CC (CIPH CMD)
DT1 (CIPH COM)
DT1(SET UP)
DT1(SET UP)
DT1(TERMINATE)
DT1(REL COM)
DT1(REL TRANSACTION)
->MSC UNS_NETW_MANAGEMENT
for MOUT_NOT_PLMN

Fig. 51 UNS_NETW_MANAGEMENT for MOUT_NOT_PLMN: trigger 2
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
78

2.5.4 UNS_BS_REASON for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated during setup due to BSS/radio-related
reasons
General Trigger Description: each time RELEASE COMPLETE/CLEAR REQUEST
or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received from the BSS
after digit analysis is performed

The condition for the UNS_BS_REASON for MOUT_NOT_PLMN increment is the
occurrence of a BSS error after the SETUP message digits could be translated.

UNS_BS_REASON for MOUT_NOT_PLMN [NR]
indicates how many calls are terminated during setup due to BSS/radio-related
reasons
Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or
SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received
after digit analysis has been performed

Fig. 52 UNS_BS_REASON for MOUT_NOT_PLMN


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
79

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
80

2.6 Error on a subsequent MSC during the PLMN's
routing of the call

The counters involved on a possible error detection may be:

at the GMSC

REL_BEFORE_ACM
UNS_TECHN_FAULT for MTRAN
UNS_CONGESTION for MTRAN
UNS_SN_CONGESTION for MTRAN
UNS_NETW_MANAGEMENT for MTRAN
UNS_REQ_DEST_ERR for MTRAN



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
81

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, Be are r Se rvice I)
Digit
Trans latio n
IAM
CALL_P ROC
(---)
IMEI_CHECK
IAM
Digit
Trans latio n
- >MS C: S N_ THROUGH_ CONNECTIONS f o r MOUT_ NOT_ PLMN
- >MS C: CALL_ WHITE_ LIS T f o r MORTR
- >MS C: CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDA_ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN,
- >MS C: DATACDA_ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALTFAXS P_ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ ANA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DATACDS _ DIG_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: ALT_ S PEECH_ DATA_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: FAX3 _ CALL_ ATTEMPTS f o r MOUT_ NOT_ PLMN
- >MS C: DED_ PAD_ ATTEMPTS
- >MS C: CALL_ ATTEMPTS f o r MICTR
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MICTR
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MOUT_ NOT_ PLMN
S t art Po i nt
- >MS C: TRAFFIC_ VOLUME f o r MTRAN
S t art Po i nt
- >MS C: REL_ BEFORE_ ACM
- >MS C: UNS _ TECHN_ FAULT f o r MTRAN
- >MS C: UNS _ CONGES TION f o r MTRAN
- >MS C: UNS _ S N_ CONGES TION f o r MTRAN
- >MS C: UNS _ NETW_ MANAGEMENT f o r MTRAN
- >MS C: UNS _ REQ_ DES T_ ERR f o r MTRAN
- >VLR: ATTEMPTED_ TMS I_ REALLOCATIONS
- >VLR: S UCCES S FUL_ TMS I_ REALLOC

Fig. 53 Error on a subsequent MSC during the PLMN's routing of the call
Siemens The Mobile Originating Call (MOC) traffic data


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 for
MICTR
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 the
number 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




The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
83

2.6.2 UNS_TECHN_FAULT for MTRAN [NR]

This counter registers the number of calls that are released after the digit translation
because of technical faults in the measured MSC (e.g. software fault, plausibility
check, hardware fault)
General Trigger Description: each time the MSC causes a technical fault (e.g.
software fault, plausibility check, hardware fault). Each time a forced release occurs
without any specific reason

UNS_TECHN_FAULT for MTRAN [NR]
this counter registers the number of calls that are released after the digit
translation because of technical faults in the measured MSC (e.g. software
fault, plausibility check, hardware fault)
Trigger: each time the MSC causes a technical fault (e.g. software fault,
plausibility check, hardware fault).
Each time a forced release occurs without any specific reason

Fig. 55 UNS_TECHN_FAULT for MTRAN

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
84

2.6.3 UNS_CONGESTION for MTRAN [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 successful
due to congestion (no outgoing traffic trunk can be selected or seized)

UNS_CONGESTION for MTRAN
A-LTG
B-LTG
|
|
|
MSC
CP
|
|
|
O:SEIZ
M: SEIZURE CA
HLR
visited
VLR
next
Exchange
O:ADDI DIG
* Seize trunk not successful
TERMINATE C
GMSC
M: DIG BLOCK C
->MSC: UNS_CONGESTION for MTRAN

Fig. 56 UNS_CONGESTION for MTRAN


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
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-connection
occurs

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

Siemens The Mobile Originating Call (MOC) traffic data


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 selected
and seized due to a network management failure.

UNS_NETW_MANAGEMENT for MTRAN
A-LTG
B-LTG
|
|
|
MSC
CP
|
|
|
O:SEIZ
M: SEIZURE CA
HLR
visited
VLR
next
Exchange
O:ADDI DIG
* Seize trunk not successful
TERMINATE C
GMSC
M: DIG BLOCK C
->MSC: UNS_NETW_MANAGEMENT for MTRAN

Fig. 58 UNS_NETW_MANAGEMENT for MTRAN


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
87

2.6.6 UNS_REQ_DEST_ERR for MTRAN [NR]

Indicates how many calls are terminated because the requested destination was
unknown, blocked or could not be charged for MTRAN. The destination couldnt be
found due to several reasons
General Trigger Description: The destination couldnt be found due to several
reasons:
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
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
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


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
88

2.7 Error after the TCH ASSIGNMENT phase

Counters that may be involved on error detection:

at the VMSC

UNS_CONGESTION for MOUT_NOT_PLMN
UNS_SN_CONGESTION for MOUT_NOT_PLMN
UNS_LACK_IWE for MOUT_NOT_PLMN

These counters will be incremented on the specified stage of the CALL SETUP if the
defined trigger conditions would occur.

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
89

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channel o n the Air Interface)
ASSIGNMENT_COMP LETE
(Channel o n the Air Interface)
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB
- >MS C: UNS _ CONGES TION f o r MOUT_ NOT_ PLMN
- >MS C: UNS _ S N_ CONGES TION f o r MOUT_ NOT_ PLMN
- >MS C: UNS _ LACK_ IWE f o r MOUT_ NOT_ PLMN

Fig. 60 Error after the TCH ASSIGNMENT phase
Siemens The Mobile Originating Call (MOC) traffic data


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 successful
due 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
|
|
|
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
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



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
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-connection
occurs

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
|
|
|
|
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
CM SERV REQ)]
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

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
92

2.7.3 UNS_LACK_IWE for MOUT_NOT_PLMN [NR]

Indicates how many calls are terminated due to lack of IWE
General Trigger Description: selection of an IWE not successful

Trigger 1: selecting of IWE is not successful

UNS_LACK_IWE for
MOUT_NOT_PLMN
Trigger 1:
selecting of IWE 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
TRUNK
C C
|
|
VLR
|
|
|
CP
MS
BS
CR(COMPL L3 INFO[CM SERV REQ])
LTG selection NRELAY:[CR(COMPL L3 INFO /
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
* IWE selection failure
MSC
Call setup is terminated
|
|
|
IWF
LTG
* IWE availability check
->MSC: UNS_LACK_IWE for MOUT_NOT_PLMN
IAM

Fig. 63 UNS_LACK_IWE for MOUT_NOT_PLMN: trigger 1





The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
93

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
94

2.8 Error due to call terminated by a upper network
element

Counter that my be involved on the error detection:

at the VMSC

CALL_REL_EXCHANGE for MOUT_NOT_PLMN [NR]
Indicates how many calls are terminated by the following exchange
Trigger: each time RELEASE is received indicating clear backward or UBM
with causes different from busy, CUG reject, destination error.

This counter may be incremented in any period of the call between the seizure of the
B LTG and the ANSWER message.

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
95

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channel o n the Air Interface)
ASSIGNMENT_COMP LETE
(Channel o n the Air Interface)
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
REL
(erro r)
- >MS C: CALL_ REL_ EXCHANGE f o r MOUT_ NOT_ PLMN
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB

Fig. 64 Error due to call terminated by a upper network element


Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
96

2.9 Error due to call terminated by a lower/upper
network element

The counter involved on the error detection is:

at the GMSC

CALL_REL_EXCHANGE for MTRAN [NR]
Indicates how many calls are terminated by the previous/following exchange
for MTRAN
Trigger: each time RELEASE is received indicating clear forward or clear
backward

This counter may be incremented in any period of the call between the seizure of the
B LTG and the ANSWER message.


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
97

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
REL
(e rro r)
- >MS C: CALL_ REL_ EXCHANGE f o r MTRAN
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB

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

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
98

2.10 Error due to call terminated by the A party before
ALERT

Counters that may be involved on the error detection:

at the VMSC

CALL_REL_BEF_A_ALERT for MOUT_NOT_PLMN [NR]
indicates how many calls are released by the A-subscriber before alerting
Trigger: each time RELEASE COMPLETE is received before alert with
relevant reason(s)

at the GMSC

CALL_REL_BEF_ALERT for MTRAN [NR]
indicates how many calls are released before alerting the destination
Trigger: each time upon receipt of RELEASE (clear backward or clear
forward) before alert signal is received

Like the previous ones, these may be incremented in any period of the call between
the seizure of the B LTG and the ANSWER message.

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
99

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: CALL_ REL_ B EF_ A_ ALERT f o r MOUT_ NOT_ PLMN
RELEAS ECOMPLETE
REL
(e rro r)
- >MS C: CALL_ REL_ BEF_ ALERT f o r MTRAN
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB

Fig. 66 Error due to call terminated by the A party before ALERT
Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
100

2.11 Error due to call terminated by the A party during
ALERT or due to TIME OUT

The counters involved on the error detection are:

at the VMSC

CALL_REL_A_ALERT for MOUT_NOT_PLMN [NR]
Indicates how many calls are released by the A-subscriber during alerting
Trigger: each time RELEASE COMPLETE is received after alert and before
CONNECT with relevant reason(s)

CALL_TIOUT_ALERT for MOUT_NOT_PLMM [NR]
Indicates how many calls are released by alert supervision time-out
Trigger: each time RELEASE COMPLETE is received due to alert
supervision time-out (internal event in MSC)

at the GMSC

CALL_REL_ALERT for MTRAN [NR]
Indicates how many calls are released before connect is received
Trigger: each time upon receipt of RELEASE (clear backward or clear
forward) before receipt of ANSWER and after receipt of ACM

These may be incremented in any period of the call between the ALERT and the
ANSWER message.

The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
101

MOC (Part 3 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
ALERT / P ROGRESS
ASSIGNMENT_REQUEST
(Channe l o n the Air Inte rface )
ASSIGNMENT_COMP LETE
(Channe l o n the Air Inte rface )
ACM
ANM
ACM
ANM
- >MS C: CALL_ TCH_ ALLOCATION f o r MORTR
- >MS C: TS 11_ EMERG_ CALL_ TCH_ ALL
- >MS C: TS 12 _ EMERG_ CALL_ TCH_ ALL
- >INTCREL: ORIG_ CALL_ S UCC_ TCH_ ALLOC
- >MS C: CALL_ REL_ A_ ALERT f o r MOUT_ NOT_ PLMN
- >MS C: CALL_ TIOUT_ ALERT f o r MOUT_ NOT_ PLMM
RELEAS ECOMPLETE
REL
(e rro r)
- >MS C: CALL_ REL_ ALERT f o r MTRAN
- >MS C: GEN_ TRAFF_ CHAN_ REQ f o r MORTR
- >INTCREL: ORIG_ CALL_ ATT_ TCH_ REQ
- >MS C: TIME_ CALL_ S ET_ U_ S ERV f o r MOC
S t o p Po i nt
- >MS C: NUM_ CALL_ S ET_ UP_ CONTRIB

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

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
102

2.12 Call terminated during SETUP due to radio
problems

If a radio problem occurs during the CALL SETUP phase and if due to that the call is
released the INTCELL counter bellow is incremented. The concrete error origin
should afterwards be searched on the BSS performance indicators.

At the MSC and for each cell

REL_CALL_BS_REASON [NR]
indicates the number of calls that were terminated during setup for base
station/radio related reasons
Trigger: during call setup, prior to CONNECT, each time SUBSYSTEM
PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMMAND/CLEAR
REQUEST are received


The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
103

MOC (Part 4 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
Activity P has e o f the Call
CONNECT
CONNECT_ACKNOWLEDGE
- >INTCREL: REL_ CALL_ BS _ REAS ON
RESET
( Err or)

Fig. 68 Call terminated during SETUP due to radio problems

Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
104

2.13 Abnormal release of the call after the ANSWER
message

Although the call is abruptly terminated if a radio error occurs after answer, from the
commercial point of view we can "assume" it as "a successful call" because it could
be charged. However, a technical problem indeed occurred and its origin should once
more be searched on the BSS measurements.

Counters that may be involved on the error detection:

at the VMSC

BS_REL_WITH_ANSWER for MOUT_NOT_PLMN [NR]
indicates the number of answered calls terminated due to BSS/radio-related
reasons (e.g. loss of connection)
Trigger: upon each receipt of CONNECT ACK when SUBSYSTEM
PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR
REQ for particular reason(s) were received

This particular counter will be incremented if one of the specified errors would occur
on the originating MSC.

Finally from the INTCELL side:

At the VMSC and for each cell

REL_ANSW_CALL_BS_REASON [NR]
indicates the number of answered calls that are terminated for base
station/radio related reasons
Trigger: after CONNECT ACK, each time SUBSYSTEM PROHIBITED,
RESET, RESET CIRCUIT, RELEASE COMMAND/CLEAR REQUEST are
received



The Mobile Originating Call (MOC) traffic data Siemens


MN2537EU01MN_0001
2003 Siemens AG
105

MOC (Part 4 of 4)
MS BSS MSC / VLR HLR / AC G-MSC / VLR
Activity P has e o f the Call
CONNECT
CONNECT_ACKNOWLEDGE
- >MS C: BS _ REL_ WITH_ ANS WER f o r MOUT_ NOT_ PLMN
- >INTCREL: REL_ ANS W_ CALL_ BS _ REAS ON
RES ET
(Er ror )

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



Siemens The Mobile Originating Call (MOC) traffic data


MN2537EU01MN_0001
2003 Siemens AG
106

S-ar putea să vă placă și