MSOFTX3000 Unified Maintenance Manual - Baic Call Service-V3.1.0

383578998.
doc Internal
Product Version Confidentiality Level

V3.1.0 INTERNAL
Huawei Technologies Co. Ltd.
Product Name Total pages
MSOFTX3000 68
MSOFTX3000 Unified Maintenance

Manual
Basic Call Service
Version: 3.1.0
2010-03-15
Huawei Proprietary and Confidential

2018-4-7 Copyright © Huawei Technologies Co., Page 1 of 68
Ltd.
383578998.doc Internal
Huawei Technologies Co., Ltd

Ltd.
Revision Record
Date Revision Description

version
2007-4-28 1.0.0 Initial draft

2007-11-26 1.0.1 Modifying the Unbuild processing part and the NACODE table
2007-11-27 1.0.2 Changing authentication set to RAND in the Authentication part
2007-11-28 1.0.3 Adding comments to identify the parts that cannot be released.
2007-11-30 2.0.0 Being updated to V2.0
2009-5-27 2.1.1 Detailing the UNBUILD processing and adding a new processing scenario,
as well as failure handling method.
Moving the methods for avoiding UNBUILD processing part to section
10.6.
Adding the descriptions of avoiding nested dialing of dual-homing network
in section 10.4
2010-3-15 3.1.0 Release whit no RMS

Ltd.
Contents
1 Introduction to Protocols 7
1.1 Protocols Related to the Basic Call Service 7
2 Basic Intra-office Call 8

2.1 Basic Intra-office Call Flow 8
2.2 Basic Intra-office IN Call Flow 11
2.3 Description of the Basic Intra-office Call Flow 15
2.3.1 Service Access Request 15
2.3.2 Authentication 16
2.3.3 Encryption 16
2.3.4 Called-Number Analysis 16
2.3.5 Requesting Routing Information (SRI) 17
2.3.6 MSRN Analysis 18
2.3.7 Paging the Callee 18
2.3.8 MGW Selection 19
2.3.9 Bearer Setup and Traffic Channel Assignment for the Caller 20
2.3.10 Service Access Request of the Callee 23
2.3.11 Callee Bearer Setup 24
2.3.12 Alerting and Connection 24
2.3.13 Disconnection 24
3 Mobile-Originated Outgoing Trunk Call 26

3.1 Mobile-Originated Outgoing Trunk Call (Called Number: MSISDN) 26
3.2 Mobile-Originated Outgoing Trunk Call ( Called number: PSTN) 29
3.3 Routing Flow of a Mobile-Originated Outgoing Trunk Call 30
4 Mobile-Terminated Incoming Trunk Call 32

4.1 Mobile-Terminated Incoming Trunk Call Flow (Called number: MSISDN) 32
5 Trunk Tandem Call 37

5.1 Trunk Tandem Call Flow (Called Number: MSISDN) 37
5.2 Trunk Tandem Call Flow (Called Number: PSTN) 39
5.3 Routing Flow of Tandem Outgoing ISUP Trunk Call 39

Ltd.
6 Call Forwarding 41
6.1 Call Forwarding Unconditional 41
6.2 Call Forwarding-Busy 42
6.3 Call Forwarding no Reply 44
6.4 Call Forwarding on Mobile Subscriber Not Reachable 45
6.5 MF Flow 47
7 Call Waiting and Call Holding 49

7.1 Call Waiting and Call Hold 49
8 Multi-Party Service 52
8.1 Multi-Party Service 52
9 Number Analysis 55
9.1 Definitions 55
9.1.1 Call Source and Call Source Code 55
9.1.2 Call prefix 55
9.1.3 DN Set 55
9.1.4 Route Selection Source Code and Route Selection Code 56
9.1.5 Failure Source Code and Failure Processing 56
9.1.6 Wildcard 56
9.1.7 Second-Time Number Analysis 56
9.1.8 EARLY ACM 57
9.1.9 Forward-to Number, Original Called Party Number and Redirected Number 57
9.2 General Process of Number Analysis 57
9.3 Adjusting Number Format 60
10 Methods for Handling Failures 62

10.1 Methods for Obtaining Information 62
10.2 Clues and Methods for Finding out Problems 62
10.3 Precautions for Problem Handling 63
11 FAQs for Basic Call Service 64

11.1 Functions of Call Source Code and IN Set 64
11.2 How to Determine that a Subscriber Is in International Roaming? What Does it Mean by MAP IN set 9? 65
11.3 How to Configure the Service Check Table to Enable an Owing-Fee Subscriber to Call 13800138000? 65
11.4 Data Configuration for Avoiding Nested Dialing 66
11.5 Dose Number Change Affect the Calling and Called Number in the CDR? 66
11.6 Methods for Avoiding the Default Normalizaiton on Different Numbers 66

Ltd.
Acronyms and Abbreviations
Acronyms Full spelling
3GPP 3rd Generation Partnership Project

UMTS Universal Mobile Telecommunications System
ITU International Telecommunication Union
ISUP ISDN User Part
MSISDN Mobile Station International ISDN Number
MSRN Mobile Station Roaming Number
BSSAP Base Station System Application Part
MAP Mobile Application Part
CAMEL Customized Applications for Mobile Network Enhanced Logic
OCSI/TCSI CAMEL Subscription Information
Abbreviations Full spelling
REQ Request
RSP Response
ACK Acknowledge
COMP Complete
SRI Send Routing Information
DB OFC HUNT DataBase Office Direction Trunk circuit Hunting
Func Function
Auth Authentication

Ltd.
1 Introduction to Protocols
1.1 Protocols Related to the Basic Call Service

The basic call service is related to the following specifications: the radio interface layer 3
specification defined in the 3GPP Release 4, basic call processing specifications, and the
ISUP basic call control signaling procedure described in the ITU-T Q protocols. The
following provides a brief introduction to these specifications:
 3GPP TS 24 008
− This specification describes the flows of radio resource management, mobility
management, and circuit-switched call control. It defines the processing of various
events, messages receipt for example, in different states, and state shifts.
− This specification also provides the definitions, contents and formats of the messages
on the A/lu interface and the coding of the message elements.
 3GPP TS 23 018
− Message flow and message processing between NEs in basic call service
− Messages on the B, C, D, F, Gs interfaces, and the definitions, contents and formats
of the messages.
 3GPP TS 22 082:
Call forwarding service flow
 3GPP TS 22 083:
Call waiting and Call hold service flows
 3GPP TS 22 084:
Multi-party service flow
 ITU-T Q 931:
Description of the ISUP signaling message at basic call control layer 3
 ITU-T Q 763:
The definitions, contents, and format of ISUP signaling messages and the codes of
message elements.
 ITU-T Q 764:
ISUP signaling flow in basic call control

Ltd.
2 Basic Intra-office Call
2.1 Basic Intra-office Call Flow

Figure 1.1 shows the flow of a basic intra-office call
Figure 1.1 Basic intra-office call flow

Ltd.
BSC-A MSC VLR BSC-B HLR

BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-C/D
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Auth Func Configuration
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Send Info For

Outgoing Call (OCS)
Complete Call
Call Proceeding
Called Number Analysis Process
Send Routing Information REQ
Provide Roaming Number REQ
Provide Roaming Number ACK
Send Routing Information ACK
Roaming Number Analysis Process
Send Info For

Incoming Call (ICS)
Page MS

Ltd.
BSC-A MSC VLR BSC-B MGW

BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A Mc
Paging Control Configuration
Page MS
MGW Selection Process
Prepare Bearer Process
ADD REQ (Build Termination of Calling Party)
ADD REPLY
Assignment REQ
Assignment COMP
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security Procedures
Security Procedures COMP
SETUP
Call Confirm
ADD REQ (Build Termination of Called Party)
ADD REPLY

Ltd.
BSC-A MSC VLR BSC-B MGW

BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A Mc
Assignment REQ
Assignment COMP
Alerting
Bearer Operation: Play Ring Tone
MOD REQ (Send Ring Tone to Termination of Caling Party )
MOD REPLY
Alerting
Connect
Bearer Operation: Stop Ring Tone

& Connect Calling and Called Party
MOD REQ (Stop Ring Tone to Termination of Caling Party )
MOD REPLY
Connect
Connect ACK
Connect ACK
Conversation
Disconnect
Disconnect
Release
Release
Release COMP
Release COMP
Clear Command
Clear COMP
SUB REQ (Release Termination of Calling Party)
SUB REPLY
Clear Command
Clear COMP
SUB REQ (Release Termination of Called Party)
SUB REPLY
2.2 Basic Intra-office IN Call Flow

Figure 1.2 shows the flow of a basic intra-office IN call

Ltd.
Figure 1.2 Basic intra-office IN call flow

BSC-A MSC VLR BSC-B HLR SCP
BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-C/D CAP
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security
Procedures
Security Procedures
COMP
SETUP
Send Info For

Outgoing Call
Complete Call
( OCSI Flag = 1 )
Get CAMEL Data REQ
Get CAMEL Data RSP

( OCSI Data )
Call Proceeding
Initial DP ( DP2 )
Report BCSM Event REQ
Apply Charging
Call Information REQ
Connect
PSI PAGING OFF

Send Routing Information ACK ( TCSI Data )

Ltd.

Initial DP ( DP12 )
Apply Charging
Connect
Send Routing Information REQ ( Suppress TCSI )
Send Routing Information ACK ( MSRN )
Send Info For

Incoming Call (ICS)
Page MS
Page MS
Assignment REQ
Assignment COMP
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP

Ltd.

Authentication RSP
Start security
procedures
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
Alerting
Connect

Connect
Connect ACK
Connect ACK
Conversation

Ltd.

Disconnect
Apply Charging Report
Call Information Report
Report BCSM Event Report ( DP9 )
Release Call
Apply Charging Report
Call Information Report
Report BCSM Event Report ( DP17 )
Release Call
Disconnect
Release
Release
Release COMP
Release COMP
Clear Command Clear Command
Clear COMP Clear COMP
In the IN call flow, the messages sent to the MSC by the SCP and the EDP events are subject to the data
configuration of the SCP. The preceding figure shows only the common messages.
2.3 Description of the Basic Intra-office Call Flow

2.3.1 Service Access Request
When a mobile subscriber initiates a call, the MS sends a CM Service Request to the BSS
through radio channel. The message carries the service type, GCI of the current cell and IMSI
or TMSI of the subscriber.
Service Access Request

When a mobile subscriber initiates a call, the MS sends a CM Service Request to the BSS
through radio channel. The message carries the service type, GCI of the current cell and IMSI
or TMSI of the subscriber. On receiving the CM Service Request, the MSC sends a Process
Access Request to the VLR. The VLR verifies the subscriber data and determines whether the
subscriber has authority on the requested service. If authentication on the SIM is required, the
VLR sends the authentication information to the MSC for initiating an authentication flow.

Ltd.
Data configuration related to the service access request

The MSOFTX3000 queries the 2G LAI or GCI Information table to verify the GCI carried in
the CM Service Request. If the GCI is invalid, the MSOFTX3000 sends a CM Service Reject
to release the call. You can run ADD LAIGCI to configure the 2G LAI or GCI Information
table.
You can run MOD VLRCFG to modify the basic data configuration of the VLR. After the
VLR verifies the subscriber data, the MSC initiates a location update process if the desired
subscriber data is unavailable. For data configuration related to the location update, see the
MSOFTX3000 Unified Maintenance Manual -Location Update VolumeV2.0.0.
2.3.2 Authentication
On receiving the authentication request from the VLR, the MSC queries the authentication
data configuration and then sends an Authentication Request carrying the RAND to the BSS.
The SIM uses the A3 authentication algorithm to calculate the SRES with the RAND and its
Ki. The VLR is performing the same calculation at the same time, and then checks whether
the SRES is the same as that obtained by the SIM after the calculation is complete.
Data configuration related to authentication:
You can run MOD AUTHCFG to configure the authentication policy of the MSOFTX3000.
You can also configure the service request type and authentication frequency through this
command. For details, see the MSOFTX3000 Unified Maintenance Manual - Authentication
and EncryptionVolumeV2.0.0.
2.3.3 Encryption
1. On receiving the encryption request from the VLR, the MSC queries the MAPACCFG
and then sends a CIPHER MODE COMMAND carrying the Kc and encryption
algorithm list to the BSS.
2. On switching to cipher mode, the SIM sends a CIPHER MODE COMPLETE to inform
the MSC of its mode and provides the encryption algorithm that has been used.
If the encryption process is started, it indicates that the MSC accepts the service access
request. Therefore the MSC does not need to send the CM Service Accept.
If the encryption process is not started, the MSC sends a CM Service Accept to notify the
BSC that the service access request has been accepted.
Data configuration related to encryption:
You can run SET MAPACCFG to configure the encryption data. You can determine whether
to support encryption or not when configuring the MAP function or the AC cache
configuration table. For details, see the MSOFTX3000 Unified Maintenance Manual -
Authentication and EncryptionVolumeV2.0.0.
2.3.4 Called-Number Analysis

3. On completing the encryption process or receiving a CM Service Accept, the calling MS
sends to the MSC a SETUP carrying its bearer capability and the called number.
4. The MSC sends a Send Info for Outgoing Call (OCS) to the Virtue VLR verifies the
bearer capability of the calling MS and then provides its subscriber data to the MSC.

Ltd.
5. The MSC first sends a Call Proceeding to the caller indicating that the call is being
connected, and then starts the called number analysis process.
6. The called number analysis aims to obtain the type of the called number, namely,
MSISD, MSRN/HON or PSTN, because the type of the called number makes direct
impact on the subsequent call flow.
 If the callee is a mobile subscriber, configure the type of the called number as MSISDN;
in this way, the MSC identifies this callee as a mobile subscriber and queries the
SCCPGT table to obtain location of the HLR where the callee is registered, and then
sends an SRI to request the MSRN.
 If the callee is not a mobile subscriber, configure the type of the called number as PSTN
and also configure the route selection code.
7. The MSC performs route analysis and routing based on the route selection code and
route selection source code, finally obtaining the CIC of the outgoing circuit.
Configure the roaming number and handover number of the callee in both local office and
other offices as MSRN/HON. For other offices, Configure the MSRN/HON with a route
selection code for routing outgoing calls.
The called-number analysis is performed for:
 Called number type analysis, route analysis and routing
 Call restriction or connection
 Number normalization and number change
In the called-number analysis process, an OCSI DP2 IN flow may be triggered as follows:
1. On receiving of the SETUP message, the MSC sends a Send Info For Outgoing Call
(OCS) to the VLR.
2. The VLR responds with the subscriber data of the caller.
3. If the caller is an IN subscriber, the subscriber data contains the OCSI tag. The MSC
sends a Get Camel Data to the VLR to obtain the OCSI of the caller.
4. The VLR sends the IN subscription information of the caller to the MSC.
5. After obtaining the caller's OCSI information, the MSC triggers an OCSI DP2 IN flow.
For details about the flow, see the MSOFTX3000 Unified Maintenance Manual – IN
ServiceVolumeV2.0.0.
Data configuration related to the called-number analysis flow
For table query flow of the called-number analysis, see 38Table 1.1
2.3.5 Requesting Routing Information (SRI)

If the callee is a mobile subscriber, configure the type of the called number as MSISDN. The
message flow is as follows:
6. The MSC identifies this callee as a mobile subscriber and queries the SCCPGT table to
obtain the location of the HLR where the callee is registered, and then sends an SRI
message to the HLR for an MSRN.
7. The HLR sends a Provide Roaming Number to the VLR of the VMSC to request an
MSRN.
8. The VLR of the VMSC allocates an MSRN and returns a PRN ACK.
9. The HLR sends the MSRN to the originating MSC.

Ltd.
If the callee and the caller are in the same office, the flow is the same as the preceding one,
where the MSC/VLR of the calling office and that of the called office are the same.
During the SRI message flow, if the callee is a TCSI IN subscriber, the TCSI DP12 IN flow is
triggered as follows:
1. On receiving the SRI message, the HLR provides the TCSI IN subscription data of the
callee to the originating MSC.
2. The originating MSC immediately triggers the IN service and sends an SRI message
again.
3. Different from the first SRI message, the second SRI carries an IN information
suppression tag.
4. The HLR sends a Provide Roaming Number to the VLR on the callee side and then
provides the MSRN to the originating MSC.
For details of the IN flow, see the MSOFTX3000 Unified Maintenance Manual – IN
ServiceVolumeV2.0.0.
Data configuration related to the SRI flow
 The SCCPGT data configuration to the called HLR
The MSISDN numbers with different prefixes can be mapped to the HLRs where they
are registered by configuring the SCCPGT table. Run ADD SCCPGT and MOD
SCCPGT to add or modify the SCCPGT data. GT + SPC and SPC are two of the
methods to translate the GT to the peer end. Contact the technical support of the peer end
and STPs to determine a method to ensure that the two ends use the same addressing
method.
 For the data configure of the HLR, see the MSOFTX3000 Configuration Guide- 01-07
Configuring Signaling Control Data.
 For data configuration related to triggering an IN IDP flow for number change, see
9.2General Process of Number Analysis.
2.3.6 MSRN Analysis

After the HLR provides the MSRN, the MSC analyze the MSRN, which is called second
number analysis. The table query flow of this number analysis is similar to that of the called
number analysis except that some of the tables are not processed. For example, the call
authority is checked only in the called-number analysis but not in the second number analysis.
The MSRN analysis aims to determine whether the MSRN is assigned by the local MSC.
 If the MSRN is assigned by the local MSC, the MSC requests the subscriber data and
current location area of the callee from the VLR and then starts paging.
 If the MSRN is assigned by other offices, the MSC performs route analysis and routing,
and finally obtains the CIC of the outgoing circuit.
For a local PLMN network subscriber who is in international roaming, the MSC changes
the DN set to 9 forcibly upon receipt of the MSRN from a foreign country (the DN set 9
is configured through software parameter P97).
Data configuration related to MSRN analysis
For data configuration of MSRN analysis, see 9.2General Process of Number Analysis.

Ltd.
2.3.7 Paging the Callee

If the called number is an MSRN assigned by the local office, the paging flow is as follows:
5. The MSC sends a Send Info For Incoming Call (ICS) to the VLR to request the
subscriber data and current LAI.
6. The VLR returns a Page MS instructing the MSC to start paging.
7. The MSC queries the paging configuration, and then sends a PAGING to the BSC
identified by the LAI of the callee.
Data configuration related to the paging the callee flow:
Run MOD PGCTRL to configure the data relate to paging; for example, paging type, paging
times, paging duration, and IMSI/TMSI paging. Configure paging policies and configure
paging control tables based on the actual conditions of the BSS radio side in the current
network to achieve the best performance.
2.3.8 MGW Selection

While paging the callee, the MSC selects the MGW and sets up bearer for the caller. The time
for setting up a call is reduced in this way. An MSC controls multiple MGWs, so the MSC has
to select an MGW for this call based on the information of the caller and callee before setting
up the bearer.
 Early selection of the MGW
In an intra-office call, the LAI of the callee is carried in the response to Send Info For
Incoming Call (ICS). If the software parameter for early selection is enabled, the MSC
uses the early selected MGW.
 Late selection of the MGW: The MSC selects an MGW after receiving the CALL
CONFIRM from the callee. In that case, the MSC selects the MGW based on the latest
location area of the callee and the SPC of the BSC carried in the PAGING RSP. As a
result, this mode achieves a higher success rate.
The MSC implements early MGW selection when waiting for the callee's response to the
paging. In that way, the bearer can be set up for the caller at the same time and thus the time
for call setup is reduced greatly. The location area of the callee used in early selection of the
MGW is the location area stored in the VLR and it may be different from the actual location
area; if the actual area is different, selection of the MGW fails. If early selection of the MGW
fails, the MSOFTX3000 will initiate a late selection of the MGW process after reviving the
CALL CONFIRM from the callee, so that call bearer is successfully setup.
The calling MGW can be specified in the MGW index carried by the service access request of
the caller. The called MGW is obtained as follows: The MSC, based on the LAI of the callee,
queries the LAIGCI table to get the SPC of the BSC. Then the MSC uses the SPC of the BSC
to query the office direction table for called office direction. Finally, the called office queries
the Radio Access Network Media Gateway (RANMGW information based on the called
office to obtain the index of the called MGW.
If the LAI of the callee registered in the VLR is incorrect, the PAGING RSP will carry the
latest LAI of the callee and the SPC of the BSC. If the LAI or the SPC has changed, the MSC
reselects an MGW for the callee after receiving the CALL CONFIRM from the callee.
Data configuration related to the MGW selection process:
Early or late selection of the MGW can be specified by BIT12 of software parameter P150:

Ltd.
 Value 1 indicates early selection

 Value 0 indicates late selection.
 By default, early selection is enabled.
According to the table query flow, data configuration related to the MGW selection is as
follows:
 The MSOFTX3000 queries the LAIGCI table based on the LAI to obtain the SPC of the
BSC. You can run ADD LAIGCI to add or MOD LAIGCI to modify the LAI and the
corresponding SPC.
 The MSOFTX3000 queries the office direction table based on the SPC of the BSC to
obtain the called office direction. You can run ADD OFC to add or MOD OFC to
modify the SPC of the BSC and the corresponding office direction information.
 The MSOFTX3000 queries the RANMGW information based on the called office to
obtain the index of the called MGW. You can run ADD RANMGW to add or MOD
RANMGW to modify the mapping between the office direction and the MGW index.
2.3.9 Bearer Setup and Traffic Channel Assignment for the Caller
After completing MGW selection for both caller and callee, the MSC starts bearer setup and
assignment flow for the caller. The bearer setup mainly concerns A-interface trunk selection,
that is, selection of an A-interface trunk circuit from the MGW to the BSC.
To select an A-interface trunk circuit, the MSC queries the A-interface trunk group table and
the trunk circuit table with the SPC of the BSC. The WCSU/WCCU module preferably
queries the internal database for the A-interface trunk circuit destined to the BSC. If no circuit
is available, the MSC queries the BSC table for home modules to implement across-board
query and routing. The circuit in the module is preferably used as the A interface trunk circuit.
Across-board query results in intense usage of the CPU. Therefore, when configuring the link
between the MSC and the BSC, you are advised to configure the processing module
(identified by the Handle module number) with the A interface circuit of the corresponding
BSC. In this way, the management of the A interface signaling and circuit can be implemented
on the same module and thus across-module selection of A-interface circuit is avoided.
After the Prepare Bearer process is complete, the MSC sends a request for traffic channel
assignment. The assignment is classified into early assignment and late assignment.
 On the caller side:
− Early assignment
During the call setup process, after sending to the caller a Call PROCEEDING, the
MSC assigns a traffic channel to the caller before the callee is alerted.

Ltd.

CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
CM_SERVICE_ACC
SETUP
Send Info For

Outgoing Call (OCS)
Complete Call
Call Proceeding
Send Info For

Incoming Call (ICS)
Assignment REQ
Assignment COMP
− Late assignment
In the call setup process, after sending to the caller a Call PROCEEDING, the MSC
assigns a traffic channel to the caller after the callee is alerted.
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Alerting
Alerting
Assignment REQ
Assignment COMP

Ltd.
 On the callee side:

− Early assignment
The MSC assigns a traffic channel after receiving a CALL CONFIRMED from the
callee.
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Assignment REQ
Assignment COMP
− Late assignment
The MSC informs the callee of late assignment through the SETUP message. The
callee responds with an ALERTING immediately after the CALL CONFIRMED. The
MSC assigns a traffic channel for the callee. Late assignment usually occurs after the
MSC receives the CONNECT message from the callee.

Ltd.

Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Alerting
Alerting
Connect
Assignment REQ
Assignment COMP
Early assignment tag is configured in the LAIGCI table. When early assignment is enabled,
the MSC can assign a channel for the caller while waiting for the callee to be connected. In
this way, the time required for call setup and the occupation time of SDCCH channels of the
BSC are reduced. Therefore, the BSC signaling congestion is effectively relieved.
If early assignment is configured, the call flow is as follows:
8. After completing bearer setup for the caller, the MSC sends an Assignment REQ to
instruct the BSC to set up a radio carrier for the caller.
9. After the assignment is complete, the BSC sends an Assignment COMP to the MSC.
Data configuration related to the caller bearer and assignment process
 You can run ADD BSC to add or MOD BSC to modify the data of the module
associated with the circuit of the BSC.
If no A-interface circuit corresponding to the BSC is available in the board, the
MSOFTX3000 queries the BSC table for corresponding module to implement across-
board check. Therefore, ensure that all the modules corresponding to the A-interface
circuits of the BSC are configured when running the ADD BSC command.
 You can run ADD N7LNK to add or MOD N7LNK to modify the information of the
BSC links.
You are advised to configure the A-interface circuits of the BSC on the processing
module (identified by Handle module number).
 You can run ADD AIETG, ADD AIETKCMOD TG to add, or MOD TKC to modify
the information related to trunk group and trunk circuits on the A interface.
 You can run MOD LAIGCI to modify the early assignment flag of the cell.

Ltd.
2.3.10 Service Access Request of the Callee

Upon receiving a PAGING from the MSC, the MS responds with a PAGING RESPONSE
carrying the latest LAI/GCI of the callee to indicate an access request for a Mobile
Terminated call (MT). The MSC processes the access request of the MTC in the same way as
the access request of the MOC as follows:
10. The MSC sends a Process Access Request to the VLR.
11. The VLR checks the subscriber data to determine whether the call has the authority on
the requested service, and then initiates an authentication and encryption flow.
For the authentication and encryption flow, see 2.3.2Authentication and 2.3.3Encryption.
Data configuration related to the service access request on the callee side
None
2.3.11 Callee Bearer Setup

After the authentication and encryption to the caller is complete, the MSC starts the caller
bearer setup process for the callee:
12. The MSC sends to the callee a SETUP carrying BEARER CAPABILITY and the calling
number.
The bearer capability is for coordination with the callee on bearer capability and the
calling number is for CLIP (Calling Line Identification Presentation).
13. On receiving the SETUP, the MS selects the bearer capability and then returns a CALL
CONFIRM carrying the selected bearer capability.
14. On receiving the bearer capability of the callee, the MSC initiates a bearer setup and
traffic channel assignment flow.
The bearer setup process for the callee is quite similar to that of the caller with only one
difference; that is, there is no MGW selection in bearer setup for the callee. For details,
see 2.3.9Bearer Setup and Traffic Channel Assignment for the Caller process for the
caller.
Data configuration related to the bearer setup process for the callee
None
2.3.12 Alerting and Connection

15. After the traffic channel assignment is complete on the callee side, the called MS rings
and sends an ALERTING to the MSC.
16. The MSC transparently transfers the message to the caller and at the same time plays a
ringback tone.
17. The called MS answers the call, and then sends a CONNECT to the MSC.
18. The MSC transparently transfers the CONNECT to the calling MS and stops playing the
ringback tone (or customized ringback tone).
19. The calling MS sends a CONNECT ACK back to the MSC for acknowledgement.
20. The MSC connects the caller and callee and a conversation begins.
Data configuration related to alerting and connection
None

Ltd.
2.3.13 Disconnection
When one party ends the conversation, the disconnection flow is as follows:
21. The MS sends a DTAP DISCONNECT to the MSC.
22. The MSC stops all call control timers and sends a RELEASE to instruct the BSC that
initiates the disconnection to release the MM connection at layer 3 and at the same time
sends a DISCONNECT to the other party.
23. After the MM connection is released, the BSC sends a RELEASE COMPLETE to the
MSC.
24. The MSC returns a CLEAR COMMAND through the SCCP link to instruct the BSC to
release related A-interface terrestrial circuits and radio resources.
25. The BSC sends a CLEAR COMPLETE to the MSC.
Data configuration related to call disconnection:
None

Ltd.
3 Mobile-Originated Outgoing Trunk Call
3.1 Mobile-Originated Outgoing Trunk Call (Called

Number: MSISDN)
Figure 25.1 shows the flow of mobile-originated outgoing trunk call when the called number
is an MSISDN.

Ltd.
Figure 25.1 Mobile-originated outgoing trunk call (called number: MSISDN)

BSC-A MSC-A VLR MSC-B HLR
BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-B/C MAP-C/D
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security
Procedures
Security Procedures
COMP
SETUP
Send Info For

Outgoing Call (OCS)
Complete Call
Call Proceeding
DB OFC HUNT
Prepare Bearer Process - A Party
Assignment REQ
Prepare Bearer Process - B Party
Assignment COMP

Ltd.

IAM
ACM
Alerting
ANM

Connect
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP
The service access request flow and the MSRN request flow of the mobile-originated
outgoing trunk call are the same as that of an intra-office call. For details of the flow, see 2.

Ltd.
3.2 Mobile-Originated Outgoing Trunk Call ( Called

number: PSTN)
Figure 25.2 shows the mobile-originated outgoing trunk call flow when the called number is a
PSTN number.
Figure 25.2 mobile-originated outgoing trunk call flow (the called number is a PSTN number)
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security
Procedures
Security Procedures
COMP
SETUP
Send Info For

Outgoing Call (OCS)
Complete Call
Call Proceeding
DB OFC HUNT
Assignment REQ
Assignment COMP
IAM
ACM
Alerting
ANM

Ltd.


Connect
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP
3.3 Routing Flow of a Mobile-Originated Outgoing Trunk

Call
After receiving an MSRN from the HLR, the MSC analyzes the MSRN, which is called the
second-time number analysis. The analysis on the MSRN aims to check whether the MSRN is
allocated by the local MSC.
If the MSRN is allocated by any other MSC, the local MSC performs route analysis based on
the route selection code and route selection source code obtained through analysis of the
MSRN and finally obtains the circuit identification code (CIC) of the outgoing circuit.
Figure 25.3 shows the routing flow of a mobile-originated outgoing ISUP trunk call.

Ltd.
Figure 25.3 Routing flow of a mobile-originated outgoing ISUP trunk call

Ltd.
4 Mobile-Terminated Incoming Trunk Call
4.1 Mobile-Terminated Incoming Trunk Call Flow (Called

number: MSISDN)
Figure 25.4 shows the mobile-terminated incoming trunk call flow (the called number is an
incoming MSISDN).

Ltd.
Figure 25.4 Mobile-terminated incoming trunk call (called number: incoming MSISDN)
MSC-A VLR-B MSC-B HLR BSC-A
BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-B/C MAP-C/D BSSAP-A
IAM(MSISDN)

ACM (Early ACM)
SRI REQ
PRN REQ
PRN ACK
SRI ACK
Send Info For

Incoming Call (ICS)
Page MS
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures

Ltd.

SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
ACM
Connect

ANM
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP

Ltd.

IAM(MSRN)
ACM (Early ACM)
Send Info For

Incoming Call (ICS)
Page MS
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
SETUP
Call Confirm

Ltd.

Assignment REQ
Assignment COMP
Alerting
ACM
Connect

ANM
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP
The service access request flow and the MSRN request flow of the mobile-terminated
incoming trunk call are the same as that of an intra-office call. So for details of the flow, see
the 2.

Ltd.
5 Trunk Tandem Call
5.1 Trunk Tandem Call Flow (Called Number: MSISDN)

Figure 25.5 shows the trunk tandem call flow when the called number is an MSISDN.
Figure 25.5 Trunk tandem call flow (called number: MSISDN)

Ltd.
MSC-A VLR-B MSC-B MSC-C HLR

BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-B/C MAP-C/D
IAM(MSISDN)
Provide Roaming
Number REQ
Provide Roaming
Number ACK
DB OFC HUNT
IAM
ACM
ACM
ANM
ANM
Conversation
REL
REL
RLC
RLC

Ltd.
5.2 Trunk Tandem Call Flow (Called Number: PSTN)

Figure 25.6 shows the trunk tandem call flow when the called number is a PSTN number.
Figure 25.6 Trunk tandem call flow (called number: PSTN)

MSC-A VLR-B MSC-B HLR MSC-C
IAM(PSTN)
DB OFC HUNT
IAM
ACM
ACM
ANM
ANM
Conversation
REL
REL
RLC
RLC
5.3 Routing Flow of Tandem Outgoing ISUP Trunk Call

After receiving an MSRN from the HLR, the MSC analyzes the MSRN, which is called the
second-time number analysis. The analysis aims to check whether the MSRN is allocated by
the local MSC.
If the MSRN is allocated by any other MSC, the local MSC analyzes the MSRN and obtains
the route selection code and source code based on which the local MSC performs route
analysis and routing; finally obtaining the CIC (Circuit Identification Code) of the outgoing
circuit.
Figure 25.7 shows the routing flow of a tandem outgoing ISUP trunk call.

Ltd.
Figure 25.7 Routing flow of a tandem outgoing ISUP trunk call

Ltd.
6 Call Forwarding
When a called GSM or UMTS user who has subscribed the forwarding service cannot
currently answer a call for a certain reason, the call forwarding service is used to forward the
call to a third party. Call forwarding (CW) services are divided into the following types
according to the requirements of the carriers, the network, and the subscribers:
 Call Forwarding Unconditional (CFU)
 Call Forwarded Because the Line Is Busy (CFB)
 Call Forwarding no Reply (CFNRy)
 Call Forwarding on Mobile Subscriber Not Reachable (CFNRc)
The MSOFTX3000 can forward a call for multiple times consecutively. The maximum
number of times a call can be forwarded is controlled by software parameters. Parameter P71
the maximum times the same call forwarding service can be performed and parameter P72
controls the maximum times a call can be forwarded.
The following describes the call forwarding services:
6.1 Call Forwarding Unconditional

All the calls to a mobile subscriber are forwarded unconditionally to a third party. If
subscriber B subscribes to and activates the CFU service, all the calls to B are forwarded to a
third party or a voice mailbox regardless of the state of B. If B also subscribes to the CF
notification service, when B is called, a message is sent to the calling MS to inform the call
forwarding.
When the caller A calls a CFU subscriber, an SRI message from the MSC is sent to the HLR
of the callee. The HLR sends back an SRI ACK for response, in which the registered forward-
to number (FTN) in the HLR is carried instead of the MSRN. On receiving the SRI ACK
message, the MSC analyzes the FTN and then connects the call to the forwarded-to
subscriber.
Figure 25.8 shows the service flow when an incoming trunk call is forwarded to a PSTN
subscriber unconditionally.

Ltd.
Figure 25.8 An incoming trunk call forwarded to a PSTN subscriber unconditionally

MSC-A MSC-B VLR MSC-C HLR - B
IAM( MSISDN )
Send Routing Information ACK ( Forwarding Data: PSTN - C )
MF OCSI DP2 Triger Process
Forwarding Number
Analysis Process
DB OFC HUNT
Prepare Bearer Process - C Party
IAM ( PSTN C )
6.2 Call Forwarding-Busy

If the call forwarding busy (CFB) service is activated, calls destined to a CFB service
subscriber are forwarded to a third party when the subscriber is busy or after the subscribers
denies the call. The CFB is further divided into network determined user busy (NDUB) and
user determined user busy (UDUB).
 NDUB: The MSC determines that the subscriber is busy and forwards the call to the
third party.
 UDUB: The MSC forwards the call to the third party after the subscriber is alerted but
denies the call.
The difference between NDUB and UDUB is the time when the MSC obtains the FTN.
In the case of NDUB, the call is forwarded as follows:
26. The MSC requests the subscriber data from the VLR.
27. The VLR determines the callee busy and provides the FTN in the response message.
In the case of UDUB, the MSC requests the FTN from the HLR after receiving a Disconnect
from the callee.
Figure 27.1 shows the NDUB service flow.

Ltd.
Figure 27.1 NDUB service flow

MSC-A VLR-B MSC-B HLR MSC-C
IAM(MSISDN)
ACM (Early ACM)

SRI REQ
PRN REQ
PRN ACK
SRI ACK
Send Info For

Incoming Call (ICS)
Subscriber Busy
Forwarding Data
( PSTN - C )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
Figure 27.2 shows the UDUB service flow.

Ltd.
Figure 27.2 UDUB service flow

MSC-A VLR-B MSC-B MSC BSC-A
BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-B/C BSSAP-A
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
ACM
Disconnect
(Cause = Subscriber Busy)
Subscriber Busy
Release
Forwarding Data
( PSTN - C )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
6.3 Call Forwarding no Reply

The calls to a mobile subscriber are forwarded to a third party if the no reply timer expires.
On receipt of an ALERTING, the MSC starts the ring tone timer. The value of the timer is set
when the CFNRy service is registered in The HLR. Having not received the CONNECT
message from the callee when the no reply timer expires, the MSC requests the FTN from the
VLR and then connects the call to the FTN.
Figure 27.3 shows the CFNRy service flow.

Ltd.
Figure 27.3 CFNRy service flow

MSC-A VLR-B MSC-B MSC BSC-A
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
ACM
Alerting Timer : Time Out
Subscriber No Reply Disconnect

(Cause = Alerting No Answer)
Forwarding Data
( PSTN - C )
Release
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
6.4 Call Forwarding on Mobile Subscriber Not Reachable

The calls to a mobile subscriber are forwarded to a third party if the wireless connection
between the callee and the network fails. The triggering causes of the call forwarding on
mobile subscriber not reachable (CFNRc) service are as follows:
 The MS is powered off.
 The mobile subscriber does not respond to the call.
 The subscriber data of the callee is lost.
 The network is in congestion.
 The MSRN is unavailable.
The CFNRc service can be further divided into:

Ltd.
 The HLR determines the callee unreachable when the callee is powered off.
 The MSC determines the callee busy when the callee does not respond.
Figure 27.4 shows the CFNRc service flow when the callee is powered off.
Figure 27.4 CFNRc service flow (the callee powered off)

MSC-A MSC-B VLR MSC-C HLR - B
IAM( MSISDN )
Subscriber Status : IMSI Detach
Send Routing Information ACK ( Forwarding Data: PSTN - C )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
Figure 27.5 shows the CFNR service flow when the callee does not respond.

Ltd.
Figure 27.5 CFNR service flow (callee not respond)

MSC-A VLR-B MSC-B BSC-A MSC-C
IAM(MSRN)
ACM (Early ACM)
Send Info For

Incoming Call (ICS)
Page MS
Paging Control Configuration :

3 Times
Page MS
Page MS
Page MS
Page No Response
Forwarding Data
( PSTN - C )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
6.5 MF Flow
An intelligent MF flow is triggered when a call to an IN subscriber is forwarded. That is, upon
triggering the forwarding process, the MSC triggers the CAMEL Subscription Information
(OCSI) of the subscriber before connecting the call to the FTN. Take CFU for example:
28. After the Terminating CAMEL Subscription Information (TCSI) of subscriber B (the
CFU subscriber) is triggered, the HLR provides the FTN and the OCSI of subscriber B in
the SRI ACK.
29. Upon receiving the SRI ACK, the MSC triggers the MF-OCSI of subscriber B and then
proceeds with the call forwarding.

Ltd.
For details about the MF flow, see the MSOFTX3000 Unified Maintenance Manual-IN
Service Volume 2.0.0.
Figure 29.1 shows the MF flow of the CFU service when the third party is a subscriber of the
PLMN network.
Figure 29.1 MF flow of the CFU service (the third party is a PLMN subscriber)
MSC-A HLR MSC-B MSC-C SCP
BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-B/C CAP
IAM(MSISDN)

ACM (Early ACM)
Send Routing
Information REQ
Send Routing
Information ACK
( TCSI Data )
Initial DP ( DP12 )
Apply Charging
Connect
Send Routing
Information REQ
( Suppress TCSI )
Send Routing
Information ACK
( Forwarding Data:
PSTN - C
& OCSI )
Initial DP ( DP2 )
Apply Charging
Connect
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )

Ltd.

Ltd.
7 Call Waiting and Call Holding
7.1 Call Waiting and Call Hold

If a called subscriber who has registered the call waiting service is busy and unable to answer
a second call, the MSC does not release the call but plays an announcement or a ringback tone
to make the call waiting to be answered.
Either the caller or the callee can initiate a CH service request during a conversation. The
party who initiates the call hold keeps the other party on hold and starts a new call or answers
an incoming call in waiting.
Figure 29.2 shows the CW service flow and CH service flow.

Ltd.
Figure 29.2 CW and CH service flow

BSC-A MSC VLR BSC-B HLR BSC-C
BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-C/D BSSAP-A
Subscriber B and C is in Conversation
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security
Procedures
Security Procedures
COMP
SETUP
Called Party Num : B
Send Info For
Outgoing Call (OCS)
Complete Call
Call Proceeding
Send Routing Information REQ ( MSISDN : B )
Send Info For

Incoming Call (ICS)
Subscriber B is Busy
RR Connection : 1
Pseudo Page

Ltd.

Assignment REQ
Assignment COMP
SETUP
Call Confirm
Call Proceeding
Alerting
Bearer Operation: Play Ring Tone or

Call Waiting Tone
Alerting
Call is Waiting
Hold (Subscriber B is Holding C)
Hold ACK
Bearer Operation: Play Call Holding

Tone
Facility( Holding IND )
Connect
Bearer Operation: Stop Call

WaitingTone
& Connect A and B Party
Connect
Connect ACK
Connect ACK
Subscriber B and A is in Conversation
Hold (Subscriber B is Holding A )
Hold ACK

Tone

Retrieve

HoldingTone
& Connect B and C Party
Retrieve ACK

Ltd.
8 Multi-Party Service
8.1 Multi-Party Service

The MPTY (Multi-Party) service enables a user to make a multi-connection call. That is, three
or more users can communicate at the same time.
When the served mobile subscriber has an activated call and a held call and both the calls are
answered, the subscriber can invoke the MPTY resource to combine the two calls as an
MPTY call to communicate with the remote parties. The MSOFTX3000 supports an MPTY
call with up to 5+1 parties. That is, the served subscriber (who invokes the MPTY service)
and the five remote parties can communicate with each other at the same time.
The MTPY service process is as follows:
30. User A has a call on hold (A-B) and an active call (A-C), and both calls are answered.
User A invokes the MPTY resources.
31. MS B sends a FACILITY to the serving MSC to instruct user A to invoke the MPTY
resources.
32. Then the MSC sends the Process Access Request to the VLR for the subscription data of
user B. If the MTPY resource is available, the VLR informs the MSC through the
Process Access Request Ack and instructs the MSC to process the MTPY service.
33. The MSC applies for the conference call resources and uses the resources to connect user
A, B, and C.
34. The MSC sends a message to user B and C to establish an MPTY call.
35. MS B sends a Facility (MultiParty Service) to the MSC, and the multi-party conversation
is hold.
Figure 35.1 shows the MPTY service flow.

Ltd.
Figure 35.1 MPTY service flow

CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
Start Security
Procedures
Security Procedures
COMP
SETUP
Called Party Num : B
Send Info For
Outgoing Call (OCS)
Complete Call
Call Proceeding
Send Routing Information REQ ( MSISDN : B )
Send Info For

Incoming Call (ICS)
Subscriber B is Busy
RR Connection : 1
Pseudo Page

Ltd.

Assignment REQ
Assignment COMP
SETUP
Call Confirm
Call Proceeding
Alerting
Bearer Operation: Play Ring Tone or

Call Waiting Tone
Alerting
Call is Waiting
Hold (Subscriber B is Holding C)
Hold ACK

Tone
Connect

WaitingTone
& Connect A and B Party
Connect
Connect ACK
Connect ACK
Subscriber B and A is in Conversation
Facility(MultiParty Service)
Bearer Operation: Build MultiParty

Audio Mixing Resource for A/B/C
Facility
(MultiParty Service IND)
Facility(MultiParty Service IND)
Subscriber A, B and C is in MultiParty Conversation
Facility(Hold MultiParty Service)

Facility
(Hold MultiParty IND)
Facility(Hold MultiParty IND)
Subscriber B is Holding MultiParty Conversation

Ltd.
9 Number Analysis
9.1 Definitions
9.1.1 Call Source and Call Source Code
A call source refers to the MS/UE or incoming trunk that originates a call. The call source
code is an integral code that identifies a call source. For the calls originated from the
MSOFTX3000, call sources are classified into A interface, Iu interface, and incoming trunk.
Call source analysis refers to querying the call source code based on the physical ports of
incoming devices. The analysis process is as follows:
 If the call comes from the A or Iu interface (that is, the call is from a local mobile
subscriber), the MSC queries the Location Area/Cell data by using the LAIGCI of the
subscriber to obtain the call source code.
 If the call comes from the trunk side (that is, from a fixed network subscriber or a
subscriber of other MSCs), the local MSC queries the trunk group data to obtain the call
source code.
A call source code specifies the source of a call. The MSC processes a call according to the
specific call source.
9.1.2 Call prefix

A call prefix is a segment stripped out from a called number. The stripped digit starts from the
first digit of the called number. A callee prefix is equal to or shorter than the called number in
length.
The MSOFTX3000 matches a called number with a call prefix following the maximum match
rule. That is, the MSOFTX3000 searches a list of call prefixes for the called prefix that best
matches the current called number. Based on the matching called prefix, the MSOFTX3000
checks a data table for call attributes such as the service category and route selection code.
Assume that call prefixes 139, 13900278 are configured; if the called number is
13900278310, the system automatically matches the number with the call prefix 13900278.

Ltd.
9.1.3 DN Set
A DN set is a collection of prefixes. It is first used for differentiated analysis on the same
called prefix, and with the passage of time it is steadily recognized as a flexible means of
called prefix analysis. One call source maps only one DN set, but one DN set can be shared
by multiple call sources.
9.1.4 Route Selection Source Code and Route Selection Code

A route selection source code identifies an outgoing route selection policy adopted by a
specific call source. A route selection source code maps a call source. When different
outgoing route selection policies are configured for different subscribers of an MSC, different
route selection source codes can be defined for different call sources.
A route selection code identifies a route selection policy adopted by a call to a called number
with a special prefix. During route analysis, a route selection name and a route selection
source code jointly determines an outgoing route.
The route selection source code is set for callers, and the route selection name is set for
callees.
9.1.5 Failure Source Code and Failure Processing

The failure source code identifies a failure processing method for call failures from a specific
call source.
A specific failure processing method is adopted based on the failure cause, for example,
reselecting a route, playing an announcement, or triggering NCSI DP4.
9.1.6 Wildcard
The number analysis process is roughly divided into three phases:
36. The MSOFTX3000 matches a number with a call prefix following the maximum match
rule.
37. The MSOFTX3000 queries the number analysis table by the matching call prefix.
38. The MSOFTX3000 performs related analysis and processing based on the query result.
A wildcarding mechanism is adopted throughout the number analysis process.
In number analysis, the most frequently used wildcards are 65534 and eeeeeeee. 65534 is
often used as a wildcard for call source code, eeeeeeee as a wildcard for call prefix, and 254
as a wildcard for call source, number type, and service attribute.
A wildcard is matched to a call source code or a prefix in the MSOFTX3000 as follows:
The MSOFTX3000 queries number analysis data tables by a specific field, such as a call
prefix or call source code. If no match is found, the MSOFTX3000 replaces the field with the
corresponding wildcard by sequence and starts over the query.
9.1.7 Second-Time Number Analysis

If the called number changes in the number analysis process, the MSOFTX3000 performs the
second-time number analysis to determine an outgoing route. The second-time number
analysis occurs in the following conditions:

Ltd.
 If the HLR returns a national MSRN or a forwarded-to number, the MSOFTX3000 starts
a second-time number analysis (analysis on the returned number) to obtain an outgoing
route.
 If the HLR returns an international MSRN, the MSOFTX3000 changes the DN set into 9
forcibly. Whether to change a DN set to 9 is specified by the software parameter P97.
Assume that the called number has been changed during prefix processing and the prefix
processing result is to reanalyze the number. In this case, the MSOFTX3000 performs a
second-time number analysis on the new called number to obtain an outgoing route.
9.1.8 EARLY ACM

If signaling transmission is slow in a call flow, the previous-hop MSC is very likely to release
a call when the wait for the ACM message is too long. In the EARLY ACM procedure, the
local MSC checks whether the callee's address is complete after receiving the IAM message
from the previous-hop MSC. If the callee's address is complete, the local MSC returns the
ACM message to the previous-hop MSC before receiving a response from the callee.
The EARLY ACM function is mainly implemented by the call control module. When the call
control module determines that the callee address is complete, it sends an ACM to notify the
trunk module of the initiation of an EARLY ACM process. The trunk module then sends the
ACM to the previous-hop MSC.
9.1.9 Forward-to Number, Original Called Party Number and

Redirected Number
 The forward-to number (also known as the redirection number) is set by the subscriber
who has registered the forwarding service. The local MSC serves as the MSC where the
call is forwarded to a third party instead of the original called number. The third party is
the redirection number.
 The original called party number is the original called party of a call that is forwarded.
 The redirected number is the ultimate number the call is directed to. The local MSC A
serves as the originating MSC. The forwarding occurs in the MSC B where the call is
forwarded to MSC C. MSC B provides the ultimate called number in MSC C to MSC B.
The format of the redirected number is controlled by the originating MSC or tandem
MSC, whereas the format of the redirection number is controlled by the MSC that
initiates call forwarding.
9.2 General Process of Number Analysis

To address the need for complex and flexible number normalization, the MSOFTX3000
divides the number analysis process into three phases: incoming number pre-processing,
number analysis, outgoing call pre-processing.
Figure 38.1shows the general process of MSOFTX3000 number analysis. For details about
functions of each table, see the MSOFTX3000 User Manual Configuration Guide-Data
Configuration of Number Analysis.

Ltd.
Figure 38.1 General process of number analysis
Table 1.1 lists tables required for number analysis and number processing, and the common
functions.

Ltd.
Table 1.1 Tables required for number analysis and number processing, and common functions of
the tables.
Name Function
Called No Pre-analysis Defines rules for called number normalization and failure
Table processing for calls from different sources.
IMSI Bit Analysis Table For mobile originated calls, defines rules for DN set change,
number change, and failure processing based on IMSI number
segments of local, remote, and international subscribers.
User Integration Service For mobile originated calls, changes calling/called number
Process Table and suppresses IN services based on the service type of the
caller or the PLMN SSCODE.
Incoming Number Process Changes calling or called number for calls from different
Table sources.
Incoming Calling Number Changes calling or called number based on the calling
Association Table number.
Incoming Original Called Changes calling or called number based on the original called
Number Association Table number.
Special Service Number Suppresses the trigger of IN services for emergency calls such
Table as 110, 120.
IDP Number Process Changes and normalizes the format of numbers in the IDP
Table message.
Called NO Analysis Table Defines the type, service attribute, and route selection code of
a called number.
Enhanced Route Analysis Reconfigures the route selection code based on the length of
the called number.
Call Rights Check Table Defines rules for data configuration to bar calls flexibly.
Service Check Table Defines rules for data configuration to bar or connect calls
flexibly based on the attributes of the calls.
Caller character analysis Changes calling or called number, triggers NCSI DP12 based
Table on the features of the calling/called number.
Calling No Analysis Table Changes calling or called number, triggers NCSI DP12 based
on the calling number.
Prefix Special Process Changes calling or called number, triggers NCSI DP12based
Table on the called number, processes call failures, re-analyzes
called number.
Outgoing Number Changes calling or called number, triggers NCSI DP12.
Analysis Table
Outgoing Calling Number Changes calling or called number based on the calling number
Association Table before the numbers are sent to another office.

Ltd.
Name Function
Outgoing Original Called Changes calling or called number based on the original called
Number Association Table number before the numbers are sent to another office.
9.3 Adjusting Number Format

UNBUILD processing focuses on called number normalization. Bit 12 of software parameter
P144 determines whether to enable the UNBULID processing. By default, UNBUILD
processing is enabled. UNBUILD processing is mainly used to serve the following purposes:
1) To record GenericNum, RedirectingNum, Called Party Number, Original Called Party
Number that are international numbers and sent through the CONNECT message. The
cause value for release upon the called number normalization failure is 45
(CV_INVALID_CODE_FORM). If the normalization of other numbers fails, the system
does not release the call.
2) To record SSPIPAddr (which is an international number) of the assisting SSP involved in
the ETC service in compression mode.
3) To control the function together with bit 15 of P60 during recording of the MSRN
returned by the MAP module. The cause value for call release upon normalization failure
is 224 (CV_NECESSARY_IE_LOST).
4) To normalize the forwarded-to number during recording of the forwarded-to number
returned by the MAP module (the normalization is not performed in the MCN
procedure).
5) To construct the information element, that is, calling number, by using “area code of the
calling number + MSC number”.
6) To determine whether the called number in the CONNECT message sent by the SCP
during an intelligent call is changed or not.
7) To apply UNBUILD processing before querying the Special Service Number Table in the
event that the called party number is an international number.
8) To record the original called party number carried in PAGE_CONNECT_ACK. The
cause value for release upon normalization failure is 224
(CV_NECESSARY_IE_LOST).
9) To query the VDB to determine whether the number is an MSRN allocated by the local
office if the number is an MSRN or a HON. If the query result shows that the MSISDN
number is an original called number (while the called number is an MSRN), the
MSOFTX3000 starts the MSISDN processing.
The following is the procedure of UNBUILD processing:
39. The MSOFTX3000 queries the NCODE table to check if the called number is a home
country code.
 If the query result shows that the country code belongs to a foreign country, the
MSOFTX3000 adds the international toll prefix 00 before the called number.

Ltd.
 If the query returns no match, the MSOFTX3000 is unable to normalize the called
number.
 If the query result shows that the country code belongs to the home country, the
MSOFTX3000 deletes the country code from the called number.
40. The MSOFTX3000 queries the NACODE table.
 If a match is found, it indicates that the number is a national mobile number. Change the
attribute of the number to national number accordingly. The normalization is complete.
 If a match is not found, it indicates that the number is not a mobile number.
41. The MSOFTX3000 queries the Called Number Analysis table.
 If the match is found and the number is an MSRN or MSISDN, the attribute of the
MSRN or MSISDN is changed to national number. If the attribute is OVERLAY, change
it to UNKNOW. Then the normalization is complete.
42. If none of the preceding conditions are met, the MSOFTX3000 queries the ACODE
table.
 If the match is found, the prefix belongs to the local area and the value of bit 0 of P17 is
1 (default value), the MSOFTX3000 removes the local area code.
 If the query result shows that the area code does not belong to the local area, the
MSOFTX3000 adds a national prefix and changes the attribute of number to
UNKNOWN. Then the UNBUILD processing is complete.
In preceding scenarios 1), 3), and 8), a number normalization failure leads to call release. In
remaining scenarios, a number normalization failure forces the MSOFTX3000 to select the
original number (the number that is not normalized) in subsequent phases of the call
procedure.
Note: In the Unbuild processing, to check whether the number is a local number, the
MSOFTX3000 queries the local area code in the information table of local office. For the
called number analysis, to check whether the incoming or outgoing number is a local number,
the MSOFTX3000 firstly queries the national area code in the call source table. If the national
area code is not available in the call source table, the MSOFTX3000 queries the local area
code in the information table of the local office.

Ltd.
10 Methods for Handling Failures
10.1 Methods for Obtaining Information

You can collect basic information about the network structure, service feature and data
configuration of the office.
 For basic call problems in a specific scenario, register user message tracing and call logs
collecting on the LMT for the caller and callee and then make some test calls. Find out
the problems based on the traced information and call logs.
 For problems with difficulty in messages tracing or without specific scenarios, register
performance measurement tasks on the LMT, and collect the alarms generated on the
MSOFTX3000, DEVICE ALARM database, MML commands operations performed
before and after the fault occurs, CDRs and serial port printout information.
 In the equipment interconnection process, use a signaling trace instrument to collect the
signaling of the equipment supplied by other vendors. In this way, the message coding
stream for successful service trigger is obtained.
10.2 Clues and Methods for Finding out Problems

Number change in the CDR is performed through the Code Processing table. The CDR is
filled in with the changed number only when BIT1of the software parameter P129 is set to 0.
If you have collected complete traced messages and call logs, you can determine the phase in
which the call release occurs, what data needs to be configured for that phase based on the
specific scenario and the message flow figure. Then check whether the data configuration is
correct or not by referring to the failure cause value.
For example, the MSC fails to send the SRI message. The failure may be caused by improper
data configuration on the HLR. Check the following items:
 Whether the link on the HLR is normal.
 Whether the signaling point is accessible.
 Whether the SCCP subsystem and GT are configured properly.
 Whether the MAP version is correct.

Ltd.
If the call scenario is not specific or it is hard to collect the traced messages, analyze the
problem based on the performance measurement results, alarms and CDRs to find out rules,
and finally identify the cause of the failure.
For example, if the call completion rate in a certain office direction is low, you can identify
the failure cause in this way:
43. Check the traffic measurement results and alarms related to the failures in this office
direction.
44. Collect information about call attempts, call completion rate, failure cause values, and
status and usage of the trunk circuits.
45. Analyze the collected information to determine whether the failure is caused by one of
the following causes:
− The traffic in this office direction is too heavy.
− The status of the trunk circuit is abnormal.
− The configuration of timeslots on the main control board is improper.
− The peer end frequently reset the circuit.
46. In the equipment interconnection process, use a signaling trace instrument to collect the
messages indicating successful service trigger.
47. Compare the message elements with that of the messages unsuccessful service trigger to
find out the cause for the failure.
10.3 Precautions for Problem Handling

If you need to modify the data configuration after identifying the cause of the failure, pay
attention to the following points:
 Confirm the operations to be performed in addition to data modification, for example,
patch installation and board restart.
 Perform the modification only during low traffic hours, in the early morning for
example.
 Prepare the data configuration script and rollback script. If an error occurs, you can
immediately roll back the configuration.
 Get familiar with the existing data configuration. Ensure that the added data
configuration does not affect the original service process.
 Adopt methods with small configuration volume and slight impacts but high efficiency.
Try not to use wild codes.
 Get familiar with specifications of the carriers.
Check whether the data configuration changes the network specifications made by the
carriers; for example, data configurations for paging, authentication policies, and
signaling adaptation specifications.

Ltd.
11 FAQs for Basic Call Service
11.1 Functions of Call Source Code and IN Set

A call source is a combination of callers with the same call attributes. The current concept of
call source is defined based on location of the incoming trunk or the location area or cell
where the call is originated. It is a geographical concept. Generally, multiple trunk groups
share one call source or all the location areas and cells share one call source. A call source
code refers to the integer code of each call source.
Call source is defined as follows:
Calls are categorized into two types: local office originated call and incoming call. The source
code of a local office originated call is defined in the LAI Information table. The source code
of an incoming call is defined in the Trunk Group table.
The following provides an example to explain the call source from local access for the
emergency call:
When a mobile subscriber in Kejiyuan (a district of Shenzhen) dials a special service number,
110 for example, the system should connect the call to the nearest 110 service center in
Kejiyuan; while if a mobile subscriber in Shekou (a district of Shenzhen) dials 110, the
system should connect the call to the nearest 110 service center in Shekou. Assume that the
Kejiyuan district and Shekou district belong to two different location areas but share the same
MSC.
In that case, the MSC needs to perform the following operations:
 When the subscriber in Kejiyuan dials 110, the MSC changes the calling number to
6532001 that represents the LAI of the caller and then connects the call to the 110
service center in Kejiyuan.
 When the subscriber in Shekou dials 110, the MSC changes the calling number to
6662002 that represents the LAI of the caller in Shekou and then connects the call to the
110 service center in Shekou .
To solve the problem, the MSC needs to identify from which location area the emergency call
is originated.
48. The MSC specifies the call source code for each of the two location areas through data
configuration in the LAI Information table.

Ltd.
49. Then the MSC converts the called number based on the call source code and call prefix
in the Call Prefix Processing table and routes the call to 110 service center.
DN set is related to called number analysis. DN set and called number prefix can be
referenced in the Called number analysis table. The DN set can be used for called number
analysis when the called number prefix is confusing. The DN set helps to perform the called
number analysis with independent number segment.
The range of a DN set includes that of a call source. That is, a call source belongs to only one DN set
whereas a DN set can be shared by multiple call sources. Generally, the DN set is not further divided.
Otherwise, all the tables referenced by the DN set need to be configured with multiple sets of numbers,
that is, the same number needs to be configured in different tables and this can causes a soaring in the
data volume.
11.2 How to Determine that a Subscriber Is in

International Roaming? What Does it Mean by MAP IN
set 9?
If a called party is roaming abroad, the MSC obtains the MSRN from the HLR and the MSRN
belongs to a foreign country in international format. The MSC compares the prefix of the
number with the home country code and changes the DN set to 9 forcibly. (DN set 9 is
configured by using the software parameter P97).
11.3 How to Configure the Service Check Table to Enable

an Owing-Fee Subscriber to Call 13800138000?
A subscriber who registers with the BAOC and ODB_BAOC services and can still dial
13800138000 to query the account balance, that is, the subscriber is free from restriction of
the BAOC and ODB_BAOC service when calling 13800138000.
To fulfill the preceding requirement, configure the called number prefix to 13800138000 in
the Called Number Analysis table; configure a service check reference and specify the
reference as ODB_BAOC service is not enabled in the Service Check table. The following
table lists the service types for checking and the corresponding methods
Service Check Service Check Meaning

Type Mode
0 1 The service is checked in usual way.

0 1 The service is not checked. In this way,
even if the ODB_BAOC service is
enabled, the call can be connected.
1 0 The corresponding attributes are invalid.
1 1 The corresponding attributes are
essential.

Ltd.
11.4 Data Configuration for Avoiding Nested Dialing

How to avoid nested dialing of area codes and NDC like 0755010, 0755029, 0755139 and
0100755 through data configuration? And how to avoid nested dialing of country codes like
008600852?
You can avoid nested dealings by running ADD CNACLD to configure the following
parameters:
Call prefix Service Service Whether to Query Length of the

Category Attribute National Area Code National Area
Table or Not Code Prefix
0 Basic National toll Yes 1

Services
00 Basic International Yes 2
Services toll
To avoid the nested dialing like 0755130, configure all the parameters when running the ADD
NACODE command.
In the National Area Code Table, the DN set is 0 by default and cannot be set. In multi-area
and dual-homing networks where there are multiple DN sets, how to avoid nested dialing?
Though the DN set in the National Area Code Table is 0 by default and cannot be set, the
internal table query mechanism determines that configuring the avoiding nested dialing
function for the DN set that is not 0 in the dual-homing office does not affect the table query.
11.5 Dose Number Change Affect the Calling and Called

Number in the CDR?
When bit 1 of P129 is set to the default value 1, number change does not affect the calling and
called numbers in the CDR. The calling and called numbers in the CDR can only be changed
through the CDR number processing table. Only when bit 1 of P129 is set to 0, the CDR is
filled in with the changed numbers. You are advised to set bit 1 of P129 to the default value 1.
11.6 Methods for Avoiding the Default Normalizaiton on

Different Numbers
The default number normalization is mostly controlled by software parameters. However, if
the number format does not meet the requirements, it is recommended that you solve the
problem through data configuration.

Ltd.
The problem causes are as follows:

50. Before applying number normalization, the MSOFTX3000 queries the table. If matched
records are found, the MSOFTX3000 does not start the number normalization.
UNBUILD processing and IDP processing apply to this situation.
In this case, you need to use the number before normalization to configure the
corresponding table, so that the normalization is skipped if matched records are found.
For UNBUILD processing, you need to configure the Called No Pre-analysis Table; for
IDP processing, you need to configure the IDP Number Process Table.
51. Before applying number normalization, the MSOFTX3000 does not query the table, but
you can modify the number format to a desired one through changing the table query.
Unlike the preceding mode, you need to use the number after normalization to configure
the tables.
This mode is applicable to incoming and outgoing normalization of calling numbers. For
the incoming number normalization, the number can be changed according to the IMSI
BIT after normalization and the Incoming No Pre-process Table and other tables. For the
outgoing number processing, the Outgoing No Pre-process Table must be configured.

Ltd.

MSOFTX3000 Unified Maintenance Manual - Baic Call Service-V3.1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSOFTX3000 Unified Maintenance Manual - Baic Call Service-V3.1.0

Uploaded by

Copyright:

Available Formats

383578998.

Product Version Confidentiality Level

MSOFTX3000 Unified Maintenance

Basic Call Service

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd

Huawei Proprietary and Confidential

Date Revision Description

2007-4-28 1.0.0 Initial draft

Huawei Proprietary and Confidential

2 Basic Intra-office Call 8

3 Mobile-Originated Outgoing Trunk Call 26

4 Mobile-Terminated Incoming Trunk Call 32

5 Trunk Tandem Call 37

Huawei Proprietary and Confidential

7 Call Waiting and Call Holding 49

10 Methods for Handling Failures 62

11 FAQs for Basic Call Service 64

Huawei Proprietary and Confidential

Acronyms and Abbreviations

Acronyms Full spelling

3GPP 3rd Generation Partnership Project

Abbreviations Full spelling

Huawei Proprietary and Confidential

1.1 Protocols Related to the Basic Call Service

Huawei Proprietary and Confidential

2 Basic Intra-office Call

2.1 Basic Intra-office Call Flow

Figure 1.1 Basic intra-office call flow

Huawei Proprietary and Confidential

BSC-A MSC VLR BSC-B HLR

Auth Func Configuration

Send Info For

Called Number Analysis Process

Send Routing Information REQ

Provide Roaming Number REQ

Provide Roaming Number ACK

Send Routing Information ACK

Roaming Number Analysis Process

Send Info For

Huawei Proprietary and Confidential

BSC-A MSC VLR BSC-B MGW

Paging Control Configuration

MGW Selection Process

Prepare Bearer Process

ADD REQ (Build Termination of Calling Party)

Auth Func Configuration

Start Security Procedures

Security Procedures COMP

Prepare Bearer Process

ADD REQ (Build Termination of Called Party)

Huawei Proprietary and Confidential

BSC-A MSC VLR BSC-B MGW

Bearer Operation: Play Ring Tone

MOD REQ (Send Ring Tone to Termination of Caling Party )

Bearer Operation: Stop Ring Tone

MOD REQ (Stop Ring Tone to Termination of Caling Party )

SUB REQ (Release Termination of Called Party)

2.2 Basic Intra-office IN Call Flow

Huawei Proprietary and Confidential

Figure 1.2 Basic intra-office IN call flow

Auth Func Configuration

Send Info For

Get CAMEL Data REQ