Professional Documents
Culture Documents
MSOFTX3000 Unified Maintenance Manual - Baic Call Service-V3.1.0
MSOFTX3000 Unified Maintenance Manual - Baic Call Service-V3.1.0
doc Internal
Version: 3.1.0
2010-03-15
Revision Record
Contents
1 Introduction to Protocols 7
1.1 Protocols Related to the Basic Call Service 7
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
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
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
1 Introduction to Protocols
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Complete Call
Call Proceeding
Page MS
Page MS
ADD REPLY
Assignment REQ
Assignment COMP
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
SETUP
Call Confirm
ADD REPLY
Assignment REQ
Assignment COMP
Alerting
MOD REPLY
Alerting
Connect
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 REPLY
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Complete Call
( OCSI Flag = 1 )
Initial DP ( DP2 )
Apply Charging
Connect
Initial DP ( DP12 )
Apply Charging
Connect
Page MS
Page MS
Assignment REQ
Assignment COMP
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
Alerting
Connect
Connect
Connect ACK
Connect ACK
Conversation
Disconnect
Release Call
Release Call
Disconnect
Release
Release
Release COMP
Release 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.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.
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
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.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.
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
CM_SERVICE_ACC
SETUP
Complete Call
Call Proceeding
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.
BSC-A MSC VLR BSC-B HLR
BSSAP-A BSSAP-A MAP-B/C MAP-B/D BSSAP-A MAP-C/D
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Alerting
Alerting
Assignment REQ
Assignment COMP
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.
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.
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
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Complete Call
Call Proceeding
DB OFC HUNT
Assignment REQ
Assignment COMP
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.
Figure 25.2 mobile-originated outgoing trunk call flow (the called number is a PSTN number)
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
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Complete Call
Call Proceeding
DB OFC HUNT
Assignment REQ
Assignment COMP
IAM
ACM
Alerting
ANM
Connect
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP
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)
PRN REQ
PRN ACK
SRI ACK
Page MS
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
ACM
Connect
ANM
Connect ACK
Conversation
REL
Disconnect
Release
RLC
Release COMP
Clear Command
Clear COMP
IAM(MSRN)
Page MS
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
SETUP
Call Confirm
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.
IAM(MSISDN)
Provide Roaming
Number REQ
Provide Roaming
Number ACK
DB OFC HUNT
IAM
ACM
ACM
ANM
ANM
Conversation
REL
REL
RLC
RLC
IAM(PSTN)
DB OFC HUNT
IAM
ACM
ACM
ANM
ANM
Conversation
REL
REL
RLC
RLC
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:
IAM( MSISDN )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
IAM(MSISDN)
PRN REQ
PRN ACK
SRI ACK
Subscriber Busy
Forwarding Data
( PSTN - C )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
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 )
SETUP
Call Confirm
Assignment REQ
Assignment COMP
Alerting
ACM
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
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.
IAM( MSISDN )
Forwarding Number
Analysis Process
DB OFC HUNT
IAM ( PSTN C )
Figure 27.5 shows the CFNR service flow when the callee does not respond.
IAM(MSRN)
Page MS
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.
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)
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 )
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Called Party Num : B
Send Info For
Outgoing Call (OCS)
Complete Call
Call Proceeding
Subscriber B is Busy
RR Connection : 1
Pseudo Page
Assignment REQ
Assignment COMP
SETUP
Call Confirm
Call Proceeding
Alerting
Call is Waiting
Hold ACK
Connect
Connect
Connect ACK
Connect ACK
Hold ACK
Retrieve
Retrieve ACK
8 Multi-Party Service
CM_SERVICE_REQ
Process Access
Request
Process Access
Request Ack
Authentication REQ
Authentication RSP
Authentication RSP
Start security
procedures
CIPHER Configuration
Start Security
Procedures
Security Procedures
COMP
SETUP
Called Party Num : B
Send Info For
Outgoing Call (OCS)
Complete Call
Call Proceeding
Subscriber B is Busy
RR Connection : 1
Pseudo Page
Assignment REQ
Assignment COMP
SETUP
Call Confirm
Call Proceeding
Alerting
Call is Waiting
Hold ACK
Connect
Connect
Connect ACK
Connect ACK
Facility(MultiParty Service)
Facility
(MultiParty Service IND)
Facility(MultiParty Service IND)
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.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.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.
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.
Table 1.1 lists tables required for number analysis and number processing, and the common
functions.
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.
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.
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.
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.
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.
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.