01-13 Configuring Advanced Mobile Service Data(1)

HUAWEI MSOFTX3000 Configuration Guide Contents

Issue 01 (2007-07-30) Huawei Technologies Proprietary i

Contents

13 Configuring Advanced Mobile Service Data ...................................................................13-1 13.1 MSC POOL management..........................................................................................................................13-2

13.1.1 Overview of Configuration ..............................................................................................................13-2 13.1.2 Set MSC Pool Function Information................................................................................................13-2 13.1.3 Add NRI Information .......................................................................................................................13-4 13.1.4 Set Offload Control Mode................................................................................................................13-5 13.1.5 Set MSC Pool Backup Configuration ..............................................................................................13-7 13.1.6 Add MSC POOL Backup Route.......................................................................................................13-8 13.1.7 Set MSC POOL Broadcast Timer Parameter ...................................................................................13-9

13.2 Configuring Service Configuration Data.................................................................................................13-10 13.2.1 Add GSM Service Configuration ...................................................................................................13-10 13.2.2 Add Color Ring Service Configuration..........................................................................................13-12 13.2.3 Add USSD Service Configuration .................................................................................................13-16 13.2.4 Add Emergency Service Configuration..........................................................................................13-18 13.2.5 Add Equivalent PLMN Information...............................................................................................13-19

13.3 Configuring eMLPP Service Data...........................................................................................................13-20 13.3.1 Background Information ................................................................................................................13-20 13.3.2 Overview of Configuration ............................................................................................................13-21 13.3.3 Modify MSC Default Priority ........................................................................................................13-21 13.3.4 Add General Priority Capability.....................................................................................................13-23

13.4 Configuring SNA Service Data ...............................................................................................................13-25 13.4.1 Background Information ................................................................................................................13-25 13.4.2 Overview of Configuration ............................................................................................................13-26 13.4.3 Add Mapping Between Location Number and LAI Number .........................................................13-27 13.4.4 Add Mapping Between Location Number and SNA Number ........................................................13-28 13.4.5 Add Mapping Between SNA Group Number and SNA Code........................................................13-29 13.4.6 Add Mapping Between IMSI Prefix and SNA Group Number ......................................................13-30

13.5 Configuring MVNO Service Data...........................................................................................................13-33 13.5.1 Background Information ................................................................................................................13-33 13.5.2 Overview of Configuration ............................................................................................................13-34 13.5.3 Set MVNO Limited Model ............................................................................................................13-35 13.5.4 Add MVNO Permit Configuration.................................................................................................13-37

Contents HUAWEI MSOFTX3000

Configuration Guide

ii Huawei Technologies Proprietary Issue 01 (2007-07-30)

13.5.5 Add MVNO IMSI Prefix................................................................................................................13-37 13.6 Configuring ADD Feature Data ..............................................................................................................13-38

13.6.1 Background Information ................................................................................................................13-38 13.6.2 Set ADD Default Configuration.....................................................................................................13-38 13.6.3 Add ADD Support HLR List..........................................................................................................13-39

13.7 Configuring Cell Billing Feature.............................................................................................................13-40 13.7.1 Background Information ................................................................................................................13-40 13.7.2 Add USSD Notice Configuration...................................................................................................13-40 13.7.3 Add USSD Notice Content ............................................................................................................13-41

13.8 Configuring Call Failure Short Message Indication Feature...................................................................13-43 13.8.1 Background Information ................................................................................................................13-43 13.8.2 Overview of Configuration ............................................................................................................13-44 13.8.3 Set MAP Feature Parameter...........................................................................................................13-45 13.8.4 Add A Call Failure SM Content .....................................................................................................13-46 13.8.5 Add A Call Failed SMS Process Entry ...........................................................................................13-47

HUAWEI MSOFTX3000 Configuration Guide Figures

Issue 01 (2007-07-30) Huawei Technologies Proprietary iii

Figures

Figure 13-1 Parameter referencing relationship .............................................................................................13-27



Tables HUAWEI MSOFTX3000

Configuration Guide

iv Huawei Technologies Proprietary Issue 01 (2007-07-30)

Tables

Table 13-1 Input parameters for the eMLPP feature analysis data .................................................................13-21

Table 13-2 Configuration steps.......................................................................................................................13-21

Table 13-3 Input parameter required by the SNA service data .......................................................................13-26


Table 13-5 Preparations ..................................................................................................................................13-34

Table 13-6 Configuration Steps ......................................................................................................................13-35

Table 13-7 Preparations ..................................................................................................................................13-44


HUAWEI MSOFTX3000 Configuration Guide 13 Configuring Advanced Mobile Service Data

Issue 01 (2007-07-30) Huawei Technologies Proprietary 13-1

13 Configuring Advanced Mobile Service Data

About This Chapter

The following table lists the contents of this chapter.

Section Describes

13.1 MSC POOL management How to configure the MSC POOL management data

13.2 Configuring Service Configuration Data

How to configure the service configuration data.

13.3 Configuring eMLPP Service Data

How to configure the eMLPP service data.

13.4 Configuring SNA Service Data

How to configure the SMA service data.

13.5 Configuring MVNO Service Data

How to configure the MVNO service data.

13.6 Configuring ADD Feature Data

How to configure the ADD feature data.

13.7 Configuring Cell Billing Feature

How to configure the cell billing feature data.

13.8 Configuring Call Failure Short Message Indication Feature

How to configure the call failure short message indication feature data.

13 Configuring Advanced Mobile Service Data HUAWEI MSOFTX3000

Configuration Guide

13-2 Huawei Technologies Proprietary Issue 01 (2007-07-30)

13.1 MSC POOL management 13.1.1 Overview of Configuration

This section describes how to configure the parameter of MSC Pool.

13.1.2 Set MSC Pool Function Information

Related Commands

Command Function

SET POOLINFO To set an MSC Pool function information data record in the configuration database.

LST POOLINFO To list the information of the MSC Pool function information data record in the configuration database.

Configuration Description z The parameter Length of NRI bit must be consistent with that set in the ADD

NRIMSC. z The flag of independent backup office is valid only in the Pool networking mode. z In the Pool networking mode, if local office is transformed to an independent backup

office from a non-independent backup office, or is transformed to a non-independent backup office from an independent backup office, VDB board must be reset.

z After you run this command, you can not roll back to the previous configuration.

Parameter Description Function flag of MSC Pool

It specifies whether the local office supports the MSC Pool function.

Default value: No

To set this parameter to Yes, do as follows:

z Disable the dual-homing backup function by using SET DHWM. z Add the NULL-NRI by using ADD NRIMSC. z Add none broadcast LAI by using ADD LAIGCI or ADD LAISAI.

To set this parameter to No, do as follows:

z Disable the offload function by using SET OFFLDCTRL. z Disable the MSC Pool backup function by using SET POOLBKPCTRL.

Flag of MGW providing MSC Pool function

It specifies whether the MGW providing MSC Pool function is supported in the local office.



Default value: No

To set this parameter to Yes, do as follows:

z Disable the dual-homing backup function by using SET DHWM. z Add the NULL-NRI by using ADD NRIMSC. z Add none broadcast LAI by using ADD LAIGCI or ADD LAISAI.

To set this parameter to No, do as follows:

z Disable the offload function by using SET OFFLDCTRL. z Disable the MSC Pool backup function by using SET POOLBKPCTRL.

MSC Identity in MSC Pool

It is a parameter for interworking between the MSOFTX3000 and the peer MGW. The parameter is valid only when Flag of MGW providing MSC Pool function is set to Yes. This parameter specifies the MSC Identity in MSC Pool.

Value range: 0-31

Default value: 0

Flag of independent backup office

It specifies whether the local office is an independent backup office in the configuration database. The rules for setting the parameter are as follows:

z When the local office is an MSC/VLR used for centralized backup, set this parameter to Yes. The local office is only a backup office of the MSC Pool without service processing.

z When the local office is not an MSC/VLR used for centralized backup, set this parameter to No. The local office is a backup office of the MSC Pool which also processes services.

Design capability in MSC Pool

It specifies the design capability in MSC Pool in the configuration database.

Value range: 0-3200 (k)

The MSC in MSC Pool can serve the service area of the RNC/BSC outside the MSC Pool. However, this design capability does not include the subscribers in the service area of the RNC/BSC outside the MSC Pool.

Length of NRI bit

It specifies the length of NRI bit in MSC Pool in the configuration database.

Value range: 0-10

Default value: 6

The maximum value of the NRI depends on the length of NRI bit. For example, if the length of NRI bit is 4, the value of the NRI is 2 4-1=15; if the length of NRI bit is 10 (maximum), the value of the NRI is 210-1=1023 (maximum). The parameter Length of NRI bit must be consistent with that set in the ADD NRIMSC.


Configuration Guide


13.1.3 Add NRI Information

Related Commands

Command Function

ADD NRIMSC To add NRI information

RMV NRIMSC To remove NRI information

MOD NRIMSC To modify NRI information

LST NRIMSC To list NRI information

Configuration Description z Run ADD NRIMSC to set the NRI data only when the MSOFTX3000 requires the MSC

pool or Server pool networking function. z The NRI is used to identify the CN node to which an RAN node belongs. When the UE

sends a service access request, the RAN determines the MSC that the subscriber belongs to based on the NRI in the TMSI. The NRI is unique in a pool or a cross pool. One NRI corresponds to only one CN node, but one CN node can correspond to multiple NRIs.

Parameter Description Description

It describes a specific NRI for identification. The value is a string.

NRI value

It specifies the value of the NRI field in the TMSI.

Value range: 0-1023

The NRI value must be set based on the length of the NRI mask. For example, if the length of the NRI mask is four bits, the maximum value of the NRI is 24- 1 = 15; if the length of the NRI mask is 10 (the maximum NRI bit length), the maximum value of the NRI is 210- 1 = 1023 (the maximum NRI value).

MSC number

It specifies the MSC number corresponding to the NRI. That is, the MSC number is used to identify the CN node (MSC) to which an RAN node belongs. The principle for setting the parameter is as follows:

z The MSC number can be of the local office, or of the other offices. z One NRI corresponds to only one CN node, but one CN node can correspond to multiple

NRIs.

VLR number

It specifies the VLR number corresponding to the NRI. That is, the MSC number is used to identify the CN node (VLR) to which an RAN node belongs. The principle for setting the parameter is as follows:



z The VLR number can be of the local office, or of the other offices. z One NRI corresponds to only one CN node, but one CN node can correspond to multiple

NRIs.

MSC name

It specifies the name of the MSC represented by the MSC number.

Local MSC flag

It specifies whether the RAN node corresponding to the NRI is under the control of the local MSC. The meanings of the options are as follows:

z True: The RAN node is under the control of the local MSC. In this case, the MSOFTX3000 uses the TMSI generated by the NRI.

z False: The RAN node is under the control of the other MSCs. In this case, the MSOFTX3000 does not use the TMSI generated by the NRI.

Same area flag

It specifies whether the RAN nodes corresponding to the NRI belong to the same pool of the local office. The NRI is unique in a pool or a cross pool.

Null NRI flag

It specifies whether the NRI is a Null-NRI. You can configure only one Null-NRI in a pool.

13.1.4 Set Offload Control Mode

Related Commands

Command Function

SET OFFLDCTRL To set the offload control mode in the configuration database when the local office offloads the users.

LST OFFLDCTRL To list the offload control mode data record in the configuration database.

Configuration Description z Offload can be activated only when you set both Allocate TMSI upon location update

and Allocate TMSI upon service access to Yes in SET MAPACCFG. z Before using SET OFFLDCTRL to modify the offload control mode, you must first set

Offload type to Not Offload Or Offload Stop to stop the current offloading operation unless Offload type is already set to Not Offload Or Offload Stop. After that, you can start the new offloading.

Parameter Description Offload type

It specifies the offloading type of the local office.

Values:


Configuration Guide


z Not Offload Or Offload Stop: It indicates that the system does not start the offloading operation or the system stops the current offloading operation.

z Offload All User: It indicates that the system offloads all users it serves. z Offload Part User: It indicates that the system offloads part of users it serves. z Offload Percent User: It indicates that the system offloads users it serves based on the

specified percent. z Offload User By BSC: It indicates that the system offloads users based on the specified

BSC. z Offload User By RNC: It indicates that the system offloads users based on the specified

RNC. z Offload User By LAI: It indicates that the system offloads users based on the specified

LAI. z Offload User By IMSI: It indicates that the system offloads users based on the specified

IMSI. z Offload User By MSISDN: It indicates that the system offloads users based on the

specified MSISDN.

Default value: Not Offload Or Offload Stop. The MSC in the MSC pool can also serve RNC/BSC service areas outside the MSC pool. Users to be offloaded in this command, however, refer to those in the MSC pool only.

User number

The parameter is valid only when Offload type is set to Offload Part User. It specifies the number of users that the local office must offload.

Percent

The parameter is valid only when Offload type is set to Offload Percent User. It specifies the percentage of users that the local office must offload to the total users.

RNC1 name~RNC10 name

The parameter is valid only when Offload type is set to Offload User By RNC. It specifies the RNC. Users accessed through this RNC must be offloaded by the local office. You can configure up to 10 RNCs for offload at a time. That is, the system can offload users on the service areas of at most 10 RNCs at a time. This parameter must be defined by using ADD RNC before being referenced here. In addition, Support IU Flex or Support MGW Proxy Iu Flex in the RNC Capability List must be selected.

BSC1 name~BSC10 name

The parameter is valid only when Offload type is set to Offload User By BSC. It specifies the BSC. Users accessed through this BSC must be offloaded by the local office. You can configure up to 10 BSCs for offload at a time. That is, the system can offload users on the service areas of up to 10 BSCs at the same time. This parameter must be defined by using ADD BSC before being referenced here. In addition, Support A Flex or Support MGW Proxy A Flex in the List of BSC Capability must be selected.

LAI1~ LAI10

The parameter is valid only when Offload type is set to Offload User By LAI. It specifies the LA, on which the users must be offloaded by the local office. You can configure up to 10 LAIs for offload at a time. That is, the system can offload users on up to 10 LAs at the same time.

MSC1 name~MSC31 name



It specifies the destination MSC, to which the system offloads the user information.

MSC1 percent~ MSC31 percent

It specifies the percentage, based on which the system offloads the user information to the corresponding destination MSC.

The sum of all effective MSC percents must be equal to 100. In addition, you must ensure that MSC percent and the corresponding MSC name are consistent throughout the MSC pool.

IMSI1~IMSI10

The parameter is valid only when Offload type is set to Offload User By IMSI. It specifies the IMSI of the user to be offloaded.

MSISDN1~ MSISDN10

The parameter is valid only when Offload type is set to Offload User By MSISDN. It specifies the MSISDN of the user to be offloaded.

Rate

It specifies the offloading rate. You can set the offloading rate to prevent congestion caused by heavy offloading traffic. The rules for setting the parameter are as follows:

z To disable the offloading traffic control, select 100%. z To control the offloading traffic, select 50% or 25% as needed. z The offloading rates corresponding to 100%, 50%, and 25% are respectively HIGH,

MID, and LOW.

13.1.5 Set MSC Pool Backup Configuration

Related Commands

Command Function

SET POOLBKPCTRL To set an MSC Pool backup configuration data record in the configuration database.

LST POOLBKPCTRL To list the information of the MSC pool backup configuration data record in the configuration database.

Parameter Description Support backup

It specifies whether the MSOFTX3000 supports MSC Pool backup. The rules for setting the parameter are as follows:

z If the parameter is set to Yes, MSC Pool backup is enabled and the MSOFTX3000 supports MSC Pool backup.

z If the parameter is set to No, MSC Pool backup is disabled and the MSOFTX3000 does not support MSC Pool backup.

Backup MSC num


Configuration Guide


It is valid only when Support backup is set to Yes. It specifies the number of MSCs, which is backed up in the MSOFTX3000.

Value range: 1-32

Default value: 1

Backup rate

It is valid only when Support backup is set to Yes. It specifies the backup rate of the MSOFTX3000.

Value range: 10-1500

The rules for setting the parameter are as follows:

z The parameter specifies the number of subscribers that the MSOFTX3000 can back up in 100 ms.

z The default value of the parameter is 40, indicating that the MSOFTX3000 backs up 40 subscribers every 100 ms by default.

Support fix time backup

It is valid only when Support backup is set to Yes. It specifies whether the MSOFTX3000 supports timed backup. If the MSOFTX3000 supports timed backup, you can set the backup period, backup start date, and backup start time.

Fix backup period

It is valid only when Support backup is set to Yes. It specifies the timed backup period. The rules for setting the parameter are as follows:

z If the parameter is set to Daily, the MSOFTX3000 backs up data every day. z If the parameter is set to Only one, the MSOFTX3000 backs up data for one time only.

Backup start date

It is valid only when Support backup is set to Yes. It specifies the backup start date.

Backup start time

It is valid only when Support backup is set to Yes. It specifies the backup start time.

13.1.6 Add MSC POOL Backup Route

Related Commands

Command Function

ADD POOLBKPRT To add an MSC pool backup route data record to the configuration database.

RMV POOLBKPRT To remove a MSC pool backup route data record from the configuration database.

LIST PLLOBKPRT To list he information of the MSC pool backup route data record in the configuration database.



Configuration Description z When the local office serves as a standalone standby office, the number of configured

backup routes must not be greater than the maximum number of standby MSCs supported by the local office. To query the maximum number of backup MSCs supported by the local office, run LST POOLBKPCTRL.

z For the same peer MSC, the role of the local office can serve as an active office or a standby office, that is, the local office and peer office are in the mutual backup relation. When the local office and peer office are in the mutual assistant relation, the M3UA route name must be the same.

z For the MSC POOL backup, the M3UA routes to be used must be direct routes. When multiple routes are configured, you need to specify the direct routes to support the upper-layer subscriber VDB by using ADD M3DS.

Parameter Description MSC name opposite

It specifies the peer MSC name that should be configured with the route entity with the local MSC. The parameter must be defined by using ADD NRIMSC before being referenced here. To query the defined MSC names, run LST NRIMSC.

Home MSC role

It specifies whether the local MSC serves as the home MSC or backup MSC. The rules for setting the parameter are as follows:

z If the parameter is set to Home MSC, it indicates that the local office serves as the home MSC, and the peer MSC is the backup MSC. The local MSC backs up data to the peer MSC.

z If the parameter is set to Backup MSC, it indicates that the local office serves as the backup MSC, and the peer MSC is the home MSC. The peer MSC backs up data to the local MSC.

M3UA route name

It specifies the M3UA route name used by the backup route. The destination entity name, link set name, and local entity name can be located based on the M3UA route name. The parameter must be defined by using ADD M3RT before being referenced here. To query the defined M3UA route names, run LST M3RT.

13.1.7 Set MSC POOL Broadcast Timer Parameter

Related Commands

Command Function

SET POOLBC To set the period and startup time of the broadcast timer. LST POOLBC To list the period and startup time of the broadcast timer in the

configuration database. DSP POOLBC To display the MSC POOL broadcast timer parameter.


Configuration Guide


Configuration Description z You can configure the period and startup time of the broadcast timer by using SET

POOLBC only when the MSOFTX3000 is required to provide the MSC POOL function.

z A broadcast message can be delivered only when you enable the software parameter that controls whether to deliver a broadcast message by using MOD MSFP.

z To send a broadcast message to the BSC/RNC, the MSC POOL function for the BSC/RNC must be enabled and the Iu/A-Flex function must be supported.

z To send a broadcast message to the UMG, the MSC POOL function for the UMG must be enabled and the agent Iu/A-Flex function must be supported.

Parameter Description Timer value

It specifies the duration of the timer in the configuration database of the MSOFTX3000.

Unit: minute

Startup time

It specifies the startup time of the timer. The startup time is in the 24-hour format. The format of the parameter is HH&MM, in which "HH" represents hour and "MM" represents minute.

If the specified time is later than the current time, the correct startup time is the specified startup time; if the specified time is earlier than the current time, the timer starts up in the coming next period. After the broadcast timer starts up, the MSC broadcasts a message every one period. For example, if Timer value is set to 70 and Startup time to 16:00 and the current time is 17:00, the timer starts up in the coming next period, that is, 17:10.

13.2 Configuring Service Configuration Data 13.2.1 Add GSM Service Configuration

Related Commands

Command Function

ADD GSMSRV To add GSM service configuration

RMV GSMSRV To remove GSM service configuration

MOD GSMSRV To modify GSM service configuration

LST GSMSRV To list GSM service configuration

Configuration Description When a local mobile subscriber uses a GSM service, the MSOFTX3000 queries the GSM Service Configuration table (set by ADD GSMSRV) based on Service category and Service code of the GSM service. Through this the MSOFTX3000 determines whether it supports the



service and the support capability for the service. If the MSOFTX3000 does not support the service or the transfer capability requested by the mobile subscriber, the MSOFTX3000 rejects the service.

For example, when an MS originates the request for the MOC service, the MS sends the information, such as Service category, Service code, and Transfer capability to the MSOFTX3000 through the Setup message. After receiving the information, the MSOFTX3000 determines whether it supports the MOC service based on the GSM Service Configuration table. If yes, the MSOFTX3000 checks whether it supports the transfer capability requested by the MS.

By default, during system initialization, the data of all standard GSM services is preset by the system. In normal conditions, do not set the GSM service data by ADD GSMSRV. Run ADD GSMSRV to set the GSM service data only when a carrier needs to add certain customized GSM services. If supplementary services are added by ADD GSMSRV, reset the WVDB module to validate the configuration.

Parameter Description Service category

It specifies the GSM service data that is set in the MSOFTX3000. The value is Bearer Service by default.

The meanings of the options are as follows:

z Teleservice: includes the telephone service, the emergency call service, and the SMS. z Bearer Service: includes the unrestricted digital service, the G3 fax service, the 3.1 kHz

audio service, and the restricted digital service. z Supplementary Service: includes the call forwarding service, the call identification

service, the call restriction service, and the ODB.

Service code

It specifies a service code for the GSM service defined by Service category. The principles for setting the parameter are as follows:

z For standard GSM services defined by the 3rd Generation Partnership Project (3GPP), the service code must be consistent with that of the GSM service defined by 3GPP.

z For GSM services customized by a carrier, the carrier must plan the service code globally and ensure the service code to be consistent with that set in the HLR.

Provision

It specifies whether the MSOFTX3000 provides the GSM service. The value is No by default. When the MSOFTX3000 is required to provide the GSM service, set Provision to Yes.

Transfer capability

It specifies the transfer capability supported by the GSM service. The principles for setting the parameter are as follows:

z For standard GSM services defined by the 3GPP, set the parameter based on the standard transfer capabilities as suggested by the 3GPP.

z For GSM services customized by a carrier, set the parameter based on the carrier's requirements.

Rate adaptation type


Configuration Guide


It is valid only when Service category is set to Bearer Service. The parameter specifies the rate adaptation type supported by the bearer service.

Connection element

It is valid only when Service category is set to Bearer Service. The parameter specifies the type of transparent transfer supported by the bearer service.

Layer-2 protocol

It is valid only when Service category is set to Bearer Service. The parameter specifies the layer-2 protocol (that is, the protocol on the data link layer) supported by the bearer service.

Signaling access protocol

It is valid only when Service category is set to Bearer Service. The parameter specifies the signaling access protocol supported by the bearer service.

Support compression

It is valid only when Service category is set to Bearer Service. The parameter specifies whether the bearer service supports data compression. The value is No, by default, which means that the bearer service does not support data compression.

13.2.2 Add Color Ring Service Configuration

Related Commands

Command Function

ADD RBTCTRL To add color ring service configuration

RMV RBTCTRL To remove color ring service configuration

MOD RBTCTRL To modify color ring service configuration

LST RBTCTRL To list color ring service configuration

Configuration Description z To enable the ring back tone service through the MSOFTX3000, run ADD RBTCTRL

to configure the related data. z Ring back tone service is a value-added service customized by subscribers. When the

subscriber who registers this service is called, the MSC plays music or sends some greeting words instead of playing normal ring back tone for the callers. If the terminal of the caller can play a video clip and the callee subscribes the video ring back service, the MSC plays a video for the caller.

Parameter Description Ring back tone service type

It specifies the type of the ring back tone service, including the speech ring back service and the video ring back service.

Ring back trigger type



It specifies how the ring back tone service is triggered in the MSOFTX3000. The meanings of the options are as follows:

z GMSC NPI: Subscriber A has registered the ring back tone service in the HLR. When others call A, the MSOFTX3000 sends an SRI message to the HLR to request the routing information of the callee if the MSOFTX3000 serves as the GMSC. The HLR then returns an SRI ack message containing the numbering plan identity (NPI) to the MSOFTX3000. After receiving the SRI ack message, the MSOFTX3000 triggers the ring back tone service based on the NPI.

z GMSC SS_CODE: Subscriber A has registered the ring back tone service in the HLR. When others call A, the MSOFTX3000 sends an SRI message to the HLR to request the routing information of the callee if the MSOFTX3000 serves as the GMSC. The HLR then returns an SRI ack message containing the SS_CODE to the MSOFTX3000. The SS_CODE is defined by the carrier and stands for the ring back tone service. After receiving the SRI ack message, the MSOFTX3000 triggers the ring back tone service based on the SS_CODE.

z VTMSC SS_CODE: Subscriber A has registered the ring back tone service in the HLR. When subscriber A is a roaming subscriber in the area served by the MSOFTX3000, during the location update, the HLR sends the SS_CODE to the VLR of that area through the MAP protocol. The SS_CODE is defined by the carrier and stands for the ring back tone service. When others call A, if the MSOFTX3000 serves as the VMSC during the call, it obtains the SS_CODE of A from the VLR and triggers the ring back tone service based on the SS_CODE.

z GMSC prefix: If the MSOFTX3000 serves as the GMSC and another MSC/SSP routes a call to the MSOFTX3000 in WIN Connect mode, The MSC/SSP sends the AIP prefix contained in the called number parameter of the incoming signaling message (for example, the IAM message) to the MSOFTX3000. The MSOFTX3000 then triggers the ring back tone service based on the AIP prefix.

z IN ringing: An intelligent network (IN) subscriber registers the ring back tone service in the HLR. When other subscribers call the IN subscriber, the MSOFTX3000 triggers the IN service for the callee if the MSOFTX3000 serves as the SSP during the call, that is, the MSOFTX3000 sends an IDP operation to the SCP. The SCP then sends a Connect operation containing AlertingPattern to the MSOFTX3000. The MSOFTX3000 triggers the ring back tone service based on AlertingPattern.

The WIN Connect mode means that when others call the IN subscriber who registers the ring back tone service in the HLR, the SSP triggers the IN service for the callee. If the DRA (route prefix + MSRN) is in the Connect operation message sent by the SCP to the SSP, the SSP adds the route prefix that is in the DRA to the called number, and then routes the call to the AIP. The AIP triggers the ring back tone service based on the route prefix.

Ring back trigger value

It is a parameter used for the MSOFTX3000 to interwork with the HLR/SCP in the ring back tone service. This parameter specifies the key parameter based on which the MSOFTX3000 triggers the ring back tone service. This parameter is used together with Ring back trigger type. The principles for setting the parameter are as follows:

z If Ring back trigger type is set to GMSC NPI, the trigger value is the NPI contained in the SRI ack message sent by the HLR.

z If Ring back trigger type is set to GMSC SS_CODE or VTMSC SS_CODE, the trigger value is the SS_CODE contained in the MAP message sent by the HLR to the VLR.

z If Ring back trigger type is set to IN ringing, the trigger value is the AlertingPattern contained in the Connect operation message sent by the SCP to the MSOFTX3000.


Configuration Guide


Ring back trigger value with AIP prefix

It is a parameter used for the MSOFTX3000 to interwork with the MSC/SSP in the ring back tone service. This parameter is valid only when Ring back trigger type is set to GMSC prefix. This parameter specifies the AIP prefix contained in the called number in the incoming signaling message of a call triggered by another MSC/SSP when the ring back tone service is activated. During number analysis, the MSOFTX3000 matches the called number according to the best match rule.

Ring back processing type

It specifies how the MSOFTX3000 processes a call during the ring back tone service. The meanings of the options are as follows:

z Trigger in local MSC: The MSOFTX3000 triggers the ring back tone service based on Ring back trigger value defined in this command. That is, the MSOFTX3000 calls the ring back tone service center that is connected to the MSOFTX3000 with a direct route.

z Route to ring back tone service center: It is reserved by the system. z Route to outgoing direction: The MSOFTX3000 routes the call to a GMSC where the

ring back tone service is triggered. The MSOFTX3000 does not trigger the ring back tone service. In this case, no direct route is available between the MSOFTX3000 and the ring back tone service center.

z Trigger HKRBT: When the MSOFTX3000 routes the call to another MSC through the IAM message, it first plays the ring back tone or customized ring back tone of the local office to the caller and then plays the corresponding local office tone to the caller after checking the PA request signaling sent by the backward MSC.

Ring back tone service center access code

It is a parameter used for the MSOFTX3000 to interwork with the ring back tone service center. It specifies the access code added to the called number by the MSOFTX3000. This parameter is used to identify the ring back tone service center.

When the MSOFTX3000 triggers the ring back tone service or routes the call to other GMSCs, the MSOFTX3000 adds an access code to the called number to identify the ring back tone service center. The MSOFTX3000 then calls the ring back tone service center or other GMSCs through the outgoing call signaling message (for example, the IAM message). The MSOFTX3000 routes the call to the ring back tone service center or other GMSCs based on the access code defined by this parameter.

If Called number format is set to Ring back tone service center access code, the system does not add the access code of the ring back tone service center to the called number.

Called number format

When the MSOFTX3000 triggers the ring back tone service or route the call to other GMSCs, the MSOFTX3000 needs to call the ring back tone service center or other GMSCs. This parameter specifies the format of the called number in the outgoing call signaling message (for example, the IAM message). It is configured based on the requirement of the ring back tone service center.


z Called number not changed: The called number is in the format of MSISDN. If you want to route the call to the ring back tone service center or to other GMSCs by adding the ring back tone service center access code to the called number, do not use this value.



z Ring back prefix and called MSISDN and called MSRN: The called number consists of the ring back prefix (ring back tone service center access code), the MSISDN of the callee, and the MSRN of the callee.

z Ring back prefix and called MSISDN: The called number consists of the ring back prefix (ring back tone service center access code) and the MSISDN of the callee.

z Ring back prefix and called MSRN: The called number consists of the ring back prefix (ring back tone service center access code) and the MSRN of the callee.

z Ring back tone service center access code: The called number is the value of Ring back tone service center access code defined in this command.

z Unused: The outgoing call signaling message (for example, the IAM message) does not contain a valid called number.

Original called number format

When the MSOFTX3000 triggers the ring back tone service or routes the call to other GMSCs, the MSOFTX3000 needs to call the ring back tone service center or other GMSCs. This parameter specifies the format of the original called number contained in the outgoing call signaling message (for example, the IAM message). This parameter is configured based on the requirement of the ring back tone service center.


z Original called number not changed: If Ring back trigger type is not set to GMSC prefix, the called number is the number dialed by the caller who originates the ring back tone call. If Ring back trigger type is set to GMSC prefix, the called number is the number contained in the incoming call signaling message (for example, the IAM message) when the call is originated. In a forwarding call, for example, A calls B, and B forwards the call to C who subscribes to the ring back tone service, the called number is the number of B.

z Original called MSISDN: If a call is not forwarded, for example, A calls B, this option indicates that the MSISDN of B is used as the original called number. If a call is forwarded, for example, A calls B, and then the call is forwarded to C (C subscribers to the ring back tone service), the option indicates that the MSISDN of C is used as the original called number.

z Original called MSRN: If a call is not forwarded, for example, A calls B, the option indicates that the MSRN of B is used as the original called number. If a call is forwarded, for example, A calls B, and the call is forwarded to C (C subscribers to the ring back tone service), the option indicates that the MSRN of C is used as the original called number.

z Original called redirecting number: If the call is not forwarded, Original called number format is null. If A calls B and B forwards the call to C (C subscribers to the ring back tone service), Original called number format is set to the MSISDN of B.

z Unused: It indicates that the outgoing call signaling message (for example, the IAM message) does not contain a valid original called number.

Ring back tone service center establishment type

It is a parameter used for the MSOFTX3000 to interwork with the ring back tone service center. This parameter is valid only when Ring back processing type is set to Trigger in local MSC. This parameter specifies the mode that the MSOFTX3000 uses in setting up connection to the ring back tone service center.


z Serial: For an outgoing call, the MSOFTX3000 first sends the IAM message to the VMSC. Upon receiving the ACM message returned from the VMSC, the MSOFTX3000


Configuration Guide


sends the IAM message to the ring back tone service center. For an intra-office call, the MSOFTX3000 first sends the Setup message to the callee. Upon receiving the Alerting message from the callee, the MSOFTX3000 sends the IAM message to the ring back tone service center.

z Parallel: For an outgoing call, the MSOFTX3000 sends the IAM message to both the VMSC and the ring back tone service center. Upon receiving the ACM message from the VMSC, the MSOFTX3000 sends the CPG message to the ring back tone service center. For an intra-office call, the MSOFTX3000 sends the Setup message to both the callee and the ring back tone service center. Upon receiving the Alerting message from the callee, the MSOFTX3000 sends the CPG message to the ring back tone service center.

z CRBT: It is similar to the parallel mode except the following difference: For an outgoing call, the MSOFTX3000 plays the customized ring back tone without

receiving the ACM message sent by the VMSC. For an intra-office call, the MSOFTX3000 plays the customized ring back tone

without receiving the Alerting message sent by the called terminal. Create ring back ticket

It is valid only when Ring back processing type is set to Trigger in local MSC. This parameter specifies whether the MSOFTX3000 generates the ring back tone bill. The default value of this parameter is False. The carriers determine whether to generate the ring back tone bill.

Setup time for ring back ticket

It is valid only when Create ring back ticket is set to True. This parameter specifies the time to generate the ring back tone bill after the MSOFTX3000 sends the IAM message to the ring back tone service center.


z ANM/ANC: The MSOFTX3000 generates the ring back tone bill when it receives the ANM or ANC message from the ring back tone service center.

z CPG: The MSOFTX3000 generates the ring back tone bill when it receives the ACM message from the ring back tone service center.

13.2.3 Add USSD Service Configuration

Related Commands

Command Function

ADD USSDCTRL To add USSD service configuration

RMV USSDCTRL To remove USSD service configuration

MOD USSDCTRL To modify USSD service configuration

LST USSDCTRL To list USSD service configuration

Configuration Description z You are required to configure the USSD service data through ADD USSDCTRL only

when the USSD service must be activated through the MSOFTX3000.



z The USSD service enables an MS to originate a specific service request for a supplementary service by sending non-standard operation commands that comply with the USSD format (defined by ADD USSDCTRL) to the MSOFTX3000. The USSD service also enables the MSOFTX3000 to send a USSD command to the MS to implement a specific service. Compared with the short message service, the USSD service enables an MS to interact with the MSOFTX3000 in real time. For example, subscribers can query the stock, weather report, and flight information by using the USSD service.

Parameter Description Service code

It specifies the service code that an MS is used to originate the USSD service. The service code is started with * or #. The maximum length is six characters. For example, both *#101# and *7# can be the service code for the USSD service.

Function

It specifies how the MSOFTX3000 processes the USSD request sent by an MS. The default value is Forwarding through HLR.


z Forwarding through HLR: It indicates that the MSOFTX3000 forwards the USSD request to the HLR to which the MS belongs. The HLR then processes the USSD request.

z Forwarding through WAP: It indicates that the MSOFTX3000 forwards the USSD request to the WAP site by using the MSISDN of the MS as the destination address of the TCAP. The WAP site then processes the USSD request. When this value is selected, enter the GT address of the USSD gateway that forwards the USSD request to the WAP site. The GT address is defined by Forward address in this command.

z Forwarding through GSM: It indicates that the MSOFTX3000 forwards the USSD request to other MSCs by using the IMSI of the MS as the destination address of the TCAP. The other MSCs then process the USSD request. When this value is selected, enter the GT address of the MSC. The GT address is defined by Forward address in this command.

z Query MSISDN: It indicates that the MSOFTX3000 first queries the MSISDN of the MS from the local VLR by using the IMSI of the MS. The MSOFTX3000 then returns the query result to the MS, for example, "MSISDN:13912345678". The value enables subscribers to obtain the MSISDN corresponding to their SIM cards from the network side.

z ECT service request: It indicates that the MSOFTX3000 implements the explicit call transfer (ECT) through the USSD operation. If subscriber A is on the phone with B and C at the same time, the ECT service enables A to connect the call between B and C before hanging up, that is, B can talk with C. Subscribers can activate the ECT service through the USSD request.

z Local function 3 to Local function 10: They are reserved by the system at present.

Forward address

The parameter is valid only when Function is set to Forwarding through WAP or Forwarding through GSM. If the MSOFTX3000 needs to forward the USSD service request to a specified external node, this parameter specifies the GT address of the external node, that is, to which the USSD request is forwarded. The GT is the address of a physical device.


Configuration Guide


13.2.4 Add Emergency Service Configuration

Related Commands

Command Function

ADD ESRVCAT To add emergency service configuration

RMV ESRVCAT To remove emergency service configuration

MOD ESRVCAT To modify emergency service configuration

LST ESRVCAT To list emergency service configuration

Configuration Description z Run ADD ESRVCAT to set emergence service data only when the MSOFTX3000 is

required to provide the 3G services. In the 2G environment, this command is not required.

z According to the specification of the 3rd Generation Partnership Project (3GPP), when a subscriber needs to send an emergency service request to the network, the subscriber can select the type of the emergency service on the operation menu of the MS instead of dialing the number of the emergency service. In this case, the Setup message sent by the MS includes only Emergency Services. The Setup message does not include Emergency Number.

z To connect such emergency calls originated by 3G subscribers, run ADD ESRVCAT to set mapping data between the emergency service type and the emergency service number on the MSOFTX3000 side. When receiving an emergency call, the MSOFTX3000 translates the emergency service type carried in the Setup message into the emergency service number and then queries the Call Prefix table (defined by ADD CNACLD ) for subsequent analysis.

Parameter Description Emergency services

It specifies the type of the emergency services. To originate an emergency service request through a 3G terminal, the MS sends the Setup message containing Emergency services to the MSOFTX3000 side.

Emergency number

It specifies the number of the emergency service, which is specified by the telecom administration department in each country. For example, in China, the number of the police emergency call is 110, and that of the fire emergency call and the ambulance emergency are 119 and 120 respectively.



13.2.5 Add Equivalent PLMN Information

Related Commands

Command Function

ADD EPLMN To add equivalent PLMN information

RMV EPLMN To remove equivalent PLMN information

MOD EPLMN To modify equivalent PLMN information

LST EPLMN To list equivalent PLMN information

Configuration Description z Run ADD EPLMN to set the equivalent PLMN information only when the

MSOFTX3000 is required to provide the equivalent public land mobile network (ePLMN) service.

z The ePLMN service enables the subscriber residence and roaming policy which helps share network resources between the shared network and the original network. That is, ePLMN enables a subscriber to enjoy services by using resources of other networks. The subscriber is not restricted by the resources provided only by the home network.

z The MSOFTX3000 supports up to five ePLMN IDs. During location update, the MSOFTX3000 sends the Location Updating Accept message containing the relevant ePLMN lists to the MS. The MS then stores the ePLMN lists and the current network ID into the SIM/USIM card. Thus, the MS can choose resources of other networks based on the ePLMN lists in the SIM/USIM card.

z If the equivalent PLMN information is not set, the PLMN ID in the Location Updating Accept message sent by the MSOFTX3000 to the MS is determined by Mobile country code and Mobile network code in the Local Mobile Office Information table (set by SET INOFFMSC /ADD INOFFMSC).

Parameter Description IMSI prefix

It specifies an IMSI prefix of a mobile subscriber who uses the ePLMN service. The value range is 0-9. The MSI prefix contains up to 15 digits. eeeeeeee is a wildcard, indicating all mobile subscribers. The IMSI prefix is a string of consecutive digits starting from the first digit of the IMSI. It can be the first digit, first several digits or all digits of an IMSI. When analyzing the IMSI, the MSOFTX3000 matches the IMSI with the IMSI prefix based on the best match rule.

The value of the parameter must consist of one or more of the following:

z Digits: 0-9 z Upper case letters: A-Z z Lower case letters: a-z z Hyphen: - z Dot: . z Chinese characters


Configuration Guide


Cell group name

It specifies the ID name of the cell group where a mobile subscriber originates the location update request. The parameter supports the keyword All (a wildcard representing all cell group IDs). If it is set to another cell group name, the parameter must be defined by ADD LAIGCI or ADD LAISAI before being referenced here.

PLMN list 1~ PLMN list 5

They specify the ePLMN ID list contained in the Location Updating Accept message sent by the MSOFTX3000 to the MS when the location update is successful.

The MSOFTX3000 supports up to five ePLMN IDs. An ePLMN ID consists of a mobile country code (MCC) and a mobile network code (MNC). An ePLMN ID contains up to six digits. For example, both 46001 and 46002 are valid ePLMN IDs.


z Digits: 0-9 z Upper case letters: A-Z z Lower case letters: a-z z Hyphen: - z Dot: . z Chinese characters

13.3 Configuring eMLPP Service Data 13.3.1 Background Information

Basic Concepts The enhanced multi level precedence and preemption service (eMLPP) divides calls into calls of multiple priorities. Calls of higher priority have more advantages, such as channel preemption and fast setup. The eMLPP enables the carriers to segment the user group in operation strategy, and provide leveled services for different users.

In the eMLPP service, each user is assigned a specific priority authority. A user can only start calls of specific priority based on the authority setting. Calls with different priorities use different network resources. In addition, calls with different priorities can be connected in different call establishment modes.

eMLPP Service Components The eMLPP service contains the following parts:

z Fast setup: This call mode can be selected for calls of all priorities. In this mode, the authentication, encryption and TMSI reassignment are omitted. Thus, the connection duration is reduced.

z Queue and preemption: When the network resources (including trunk circuits, signaling channels, and service channels) are not enough, a call of higher priority is not released. Instead, it can have priority when queuing and even preempt the resource of calls with lower priority.



13.3.2 Overview of Configuration

Configuration Relationship As one of the service data of the MSOFTX3000, the eMLPP service data is used to configure the priority data (such as priority of the common call, special call, and general priority) of the MSOFTX3000.

During the configuration, the cell group name defined in the mobile service is referenced in the general priority data. Table 13-1 lists the details.

Table 13-1 Input parameters for the eMLPP feature analysis data

Parameter Defined in Source Data Category

Referenced in

Cell group name

ADD LAIGCI/ADD LAISAI

Mobile service data

ADD GEPRI

When you configure other data in the MSOFTX3000, you need not reference any parameter defined in the eMLPP service data.

Configuration Steps Table 13-2 lists the steps for configuring the eMLPP service data.

Table 13-2 Configuration steps

Step Description Command

1 Modify the eMLPP priority of the MSC. MOD MSCEMLPP

2 Add general priority capability. ADD GEPRI

13.3.3 Modify MSC Default Priority

Related Commands

Command Function

MOD MSCEMLPP To modify MSC default priority

LST MSCEMLPP To list MSC default priority

Configuration Description During call connection, the MSOFTX3000 can read the related eMLPP priority information through one of the following ways:


Configuration Guide


z Read the subscribed eMLPP priority information from the local VLR. z Read the subscriber's eMLPP priority information from the call signaling of the mobile

terminal. z Read the MSC default eMLPP priority information from the local configuration database

of the MSOFTX3000.

In the following situations, the MSOFTX3000 adopts the MSC default eMLPP priority information in the local configuration database as the basis to preempt and queue the resources later:

z If the call is urgent (that is emergent call), the MSOFTX3000 adopts the MSC default eMLPP priority information whether the user subscribes to the eMLPP priority or not.

z If the call is normal and the user does not subscribe to the eMLPP priority, or the subscribed eMLPP priority (if available) is higher than the MSC default eMLPP priority, the MSOFTX3000 adopts the MSC default eMLPP priority information.

The MSOFTX3000 supports seven levels of the eMLPP priority. They are 4, 3, 2, 1, 0, B and A in an ascending order. That is, level 4 is the lowest while level A is the highest. Levels A and B are provided for the vendor while the other five levels are for the user. By default, the system presets the eMLPP priority for all calls during the initialization.

z Normal call priority: EMLPP_1 z Special call priority: EMLPP_A z Limit call priority: EMLPP_2 z Handover priority: EMLPP_B z Location updating priority: EMLPP_0 z Outgoing SMS priority: EMLPP_2 z Terminating SMS priority: EMLPP_2 z LCS from network priority: EMLPP_3 z Send identification priority: EMLPP_4 z Supplementary service priority: EMLPP_3

Do not configure the default configuration set by the system unless required by the carrier. If the vendor requires redefining the eMLPP priority, run MOD MSCEMLPP to modify the MSC default value.

The mentioned initialized value refers to the value that is obtained by running LST MSCEMLPP if the initialized configuration is not changed.

Parameter Description Normal call priority

It is used to reconfigure the eMLPP priority of a normal call. The initial value is priority 1.

Special call priority

It is used to reconfigure the eMLPP priority of a special call. The initial value is priority A. In general, the priority of a special call is higher than that of a normal call.

Handover priority

It is used to reconfigure the eMLPP priority of the handover. The initial value is priority B.

Location updating priority



It is used to reconfigure the eMLPP priority of the location update. The initial value is priority 0.

Outgoing SMS priority

It is used to reconfigure the eMLPP priority of the outgoing SMS. The initial value is priority 2.

Terminating SMS priority

It is used to reconfigure the eMLPP priority of the terminating SMS. The initial value is priority 2.

LCS from network priority

It is used to reconfigure the eMLPP priority of the LCS from the network. The initial value is priority 3.

Send identification priority

It is used to reconfigure the eMLPP priority of the sending identification. The initial value is priority 4.

Supplementary service priority

It is used to reconfigure the eMLPP priority of a supplementary service. The initial value is priority 3.

13.3.4 Add General Priority Capability

Related Commands

Command Function

ADD GEPRI To add general priority capability

RMV GEPRI To remove general priority capability

MOD GEPRI To modify general priority capability

LST GEPRI To list general priority capability

Configuration Description Run ADD GEPRI to add the general priority capability data only when the MSOFTX3000 is required to provide the differentiated service (including the eMLPP service). When the MSOFTX3000 analyzes the differentiated service, the table query flow is as follows:

1. During location update, based on the data of Category, E-Category, CARP, or eMLPP stored in the HLR, the local VLR queries the User Priority Configuration table set by ADD USRPRI to obtain the priority information of the mobile subscriber. The local VLR then adds the priority information to the subscriber data in the local database.

2. During service processing of an intra-office call, the local MSC uses the user priority information stored in the local VLR, the eMLPP priority information sent from the MS to the network through call signaling, or the default eMLPP priority information of the MSC as the user priority information of the call according to certain rules. Based on the user priority


Configuration Guide


information, the system queries the General Priority Capability table set by ADD GEPRI to obtain the new general priority information of the subscriber. Enable or disable the fast setup function for the call by running ADD GEPRI.

3. During service processing of an incoming call, the local MSC queries the Trunk Priority Configuration table set by ADD TKPRI to obtain the new general priority information of the incoming call based on the MLPP information in the incoming signaling.

4. The system uses the general priority information obtained in step 2 or 3 to query the Call Authority Check table set by ADD CALLPRI. If the query is successful after the match checking, the system uses the new general priority information set by ADD CALLPRI as the output. If the query fails, the system uses the new general priority set by ADD GEPRI as the output.

5. The system uses the new general priority information obtained in step 4 to query the Radio Priority Configuration table set by using ADD RDIOPRI. Specify whether a corresponding call has such functions as preemption, queue, radio rate adaptation, and radio AMR rate adaptation through ADD RDIOPRI.

Parameter Description User Priority

It is a condition for determining the general priority capability. It specifies the user priority of a call.

During call connection, the MSOFTX3000 can use multiple modes to obtain the user priority information of the call. For example, the MSOFTX3000 can:

z Obtain the user priority information from the local VLR. z Obtain the eMLPP priority information of a subscriber from the call signaling of an MS. z Obtain the default eMLPP priority information of the MSC from the local configuration

database of the MSOFTX3000.

The MSOFTX3000 uses the following rules to determine the priority to be used as the user priority of the call:

z For an emergency call, the MSOFTX3000 uses the default eMLPP priority information of the MSC no matter whether the user priority information is referenced in the VLR.

z For an ordinary call, if no eMLPP priority information is referenced in the VLR, the MSOFTX3000 uses the default eMLPP priority information of the MSC.

z The MSOFTX3000 uses the user priority information configured in the VLR if the MS does not send the eMLPP priority information to the network when initiating a call, the subscriber priority information can be referenced in the VLR and the subscription data is valid.

z The MSOFTX3000 uses the user priority information configured in the VLR if the MS sends the eMLPP priority information to the network when initiating a call, the subscriber priority information can be referenced in the VLR and the eMLPP priority sent from the MS is higher than that in the VLR. Otherwise, the MSOFTX3000 uses the eMLPP priority sent from the MS.

Call Type

It is a condition for determining the general priority capability. It specifies the call type. The value is All by default.

Cell Group ID Name



It is a condition for determining the general priority capability. It specifies the location area or the cell where the mobile subscriber initiates or receives a call. The parameter supports the keyword All (a wildcard representing all cell group ID names). If it is set to a cell group ID name other than ALL, the parameter must be defined by ADD LAIGCI or ADD LAISAI before being referenced here. The principles for setting the parameter are as follows:

z When the system analyzes the general priority of a call, the wildcard All indicates the lowest priority if Cell Group ID Name of several pieces (generally two) of the general priority capability data matches the call. That is, the system matches the call with other cell group ID name first.

z When you enter a string through the LMT, the system first converts all lower-case letters of the string into upper-case letters and deletes the spaces at the extreme left and extreme right of the string. For example, the string " Area abc " entered through the LMT is converted into "AREA ABC" before it is further processed in the BAM database.

New General Priority

It specifies the general priority of a call when the parameters of the call match the preceding conditions.

During the analysis of the differentiated service, the system uses New General Priority to continue the query of the Call Authority Check table set by ADD CALLPRI or the Radio Priority Configuration table set by ADD RDIOPRI.

Fast Setup Indication

It specifies whether a call supports the fast setup function when the parameters of the call match the preceding conditions. The value is No by default. If it is set to Yes, the system can shorten the setup duration by omitting the authentication, encryption, and TMSI reassignment during the call setup.

If a mobile subscriber subscribes to the E-category information, the MSOFTX3000 does not support the fast setup function.

13.4 Configuring SNA Service Data 13.4.1 Background Information

Shared network area (SNA) provides the function to restrict the handover of a mobile subscriber in conversation in a 3G network. The function needs the cooperation of the MSOFTX3000 and the RNC. The information related to the SNA and the access of the subscriber is configured on the MSOFTX3000; the control of the access restriction is implemented on the RNC.

Currently, for an idle subscriber, the MSOFTX3000 provides ZC and enhanced roaming restrictions. The control of the access restriction is implemented on the MSOFTX3000.

As described earlier, the data related to the access of a subscriber in conversation is configured on the MSOFTX3000, although the access restriction is implemented on the RNC. Therefore, by configuring data on the MSOFTX3000, roaming restriction on both the idle subscriber and the subscriber in conversation can be implemented.


Configuration Guide


13.4.2 Overview of Configuration

Configuration Relationship SNA service data is related to:

z Mapping between the location areas and the SNAs z Mapping between an SNA group number and SNA codes z Mapping between IMSI prefixes and SNA group numbers

SNA service data references the following parameter defined by the mobile service data. Table 13-3 describes the referencing relationship of the parameter.

Table 13-3 Input parameter required by the SNA service data

Parameter Defined in Source Data Category

Referenced in

Location number name

ADD LAISAI. Mobile service data

ADD LOCSNA

Other configuration data of MSOFTX3000 need not reference the parameters defined by the SNA service data.

Configuration Steps Table 13-4 describes the steps for configuring SNA service data.

Table 13-4 Configuration steps

Step Description Command

1 Add mapping between location numbers and SNA number.

ADD LOCSNA

2 Add mapping between SNA group numbers and SNA numbers.

ADD SNAGRPCODE

3 Add mapping between IMSI prefixes and SNA group numbers.

ADD IMSIGRP

Parameter Referencing Relationship Figure 13-1 shows the referencing relation between the key fields of the data tables.



Figure 13-1 Parameter referencing relationship

ADD LOCSNALocation number

SNA name

ADD SNAGRPCODE

SNA name

ADD IMSIGRP

IMSI prefix

PLMN n

SNA group name

SNA group name

name

13.4.3 Add Mapping Between Location Number and LAI Number

Related Commands

Command Function

ADD LOCNOLAI To add a mapping between location name and location area identification (LAI) number data record to the configuration database.

RMV LOCNOLAI To remove a mapping between location name and LAI number data record from the configuration database.

LST LOCNOLAI To query the information of the mapping between location name and location area identification (LAI) number data record in the configuration database.

Configuration Description The MSOFTX3000 supports establishing the mapping between location name and LAI and restricting the roaming area of a subscriber in the connection mode based on the mapping between LAI and shared network area. You can configure the mapping between location number and LAI by using ADD LOCNOLAI. A location name has a one-to-one relationship with a LAI (local location area or neighboring location area).

Parameter Description Location name

It specifies a location name in the configuration database. The parameter does not support key words. It is used to identify the grouping indicator of the sharing function in the connection


Configuration Guide


mode. Multiple location areas or service areas can be divided into different groups to support sharing of the connection mode.

Value range: a string of up to 32 characters

The parameter is to be referenced in ADD LOCSNA.

z A location name must be numbered in the local MSOFTX3000 on a unified basis. z When you enter a string through the LMT, the system converts all lower-case letters into

upper-case letters and deletes the spaces on the extreme left and extreme right (if any) before performing further operations on the BAM database. For example, when you enter " Area abc ", the system converts it into "AREA ABC".

LAI

It specifies the location area (local location area or neighboring location area) that matches a location name. The parameter does not support key words. It must be defined by using ADD LAISAI before being referenced here.

13.4.4 Add Mapping Between Location Number and SNA Number

Related Commands

Command Function

ADD LOCSNA To add mapping between location number and SNA number

RMV LOCSNA To remove mapping between location number and SNA number

LST LOCSNA List mapping between location number and SNA number

Configuration Description z A location number name is in a one-to-one relationship with a location area that includes

the local location area and adjacent location areas. z A SNA code identifies a shared network area, to which subscribers are allowed to roam. z A SNA consists of one or multiple location areas. The mapping between a location

number name and an SNA code is defined by using ADD LOCSNA. The MSOFTX3000 sends the mapping information to the RNC by the information transfer process, so that the RNC can control the handover of a subscriber in connection mode based on the list of the permitted SNA codes by the subscriber.

Parameter Description Location number name

It specifies the number name of a location area, including a local location area or an adjacent location area that can provide the SNA service. The parameter must be defined by ADD LAISAI before being referenced here. The principles for setting the parameter are as follows:

z When you enter a string through the LMT, the system first converts all lower-case letters of the string into upper-case letters and deletes the spaces at the extreme left and extreme



right of the string. For example, the string " Area abc " entered through the LMT is converted into "AREA ABC" before it is further processed in the BAM database.

z The parameter supports the keyword INVALID (indicating that the parameter is invalid). z Uniformly name a location number name in the local office. z The location number name must map the LAI.

SNA code

It specifies the number that identifies an SNA.

Value range: 0-65535

It is referenced in the ADD SNAGRPCODE command. An SNA number can map to multiple location numbers. The RNC controls the handover of a subscriber in conversation based on the list of permitted handover-to SNA codes.

SNA codes must be uniformly allocated for all the offices so that the peer office can identify the location areas that map to an SNA code when a handover occurs. All the location areas that map to an SNA must be within the same PLMN.

13.4.5 Add Mapping Between SNA Group Number and SNA Code

Related Commands

Command Function

ADD SNAGRPCODE To add mapping between SNA group number and SNA code

RMV SNAGRPCODE To remove mapping between SNA group number and SNA code

LST SNAGRPCODE To list mapping between SNA group number and SNA code

Configuration Description One SNA group name can map many SNA codes and one SNA code can map many SNA group names. You can configure the mapping between SNA group name and the SNA code by ADD SNAGRPCODE.

Parameter Description SNA group name

It specifies an SNA group name in the configuration database of the MSOFTX3000. The value is a string of up to 32 characters. It is referenced in ADD IMSIGRP. The principles for setting the parameter are as follows:


z It supports the keyword INVALID, which indicates that the parameter is invalid.


Configuration Guide


z The value of the parameter must consist of one or more of the following: Digits: 0-9 Upper case letters: A-Z Lower case letters: a-z Hyphen: - Dot: . Chinese characters

SNA code

It specifies an SNA code that maps to an SNA group name. The parameter must be defined by using ADD LOCSNA before being referenced here. The SNA codes that map to an SNA group name must belong to the same PLMN.

13.4.6 Add Mapping Between IMSI Prefix and SNA Group Number

Related Commands

Command Function

ADD IMSIGRP To add mapping between IMSI prefix and SNA group number

RMV IMSIGRP To remove mapping between IMSI prefix and SNA group number

MOD IMSIGRP To modify mapping between IMSI prefix and SNA group number

LST IMSIGRP To list mapping between IMSI prefix and SNA group number

Configuration Description The MSOFTX3000 can restrict the roaming area of a subscriber in connection mode based on the mapping between an IMSI prefix and an SNA group name. In addition, the MSOFTX3000 can also restrict the inter-network roaming of a subscriber in connection mode based on the PLMN number. Run ADD IMSIGRP to set the mapping between an IMSI prefix and an SNA group name. One IMSI prefix corresponds to multiple SNA group names.

Parameter Description IMSI prefix

It specifies the IMSI prefix used by a 3G subscriber to which the MSOFTX3000 restricts the handover in connection mode. It is a number of up to 15 digits. The IMSI prefix is a string of consecutive digits starting from the first digit of the IMSI. It is either the first digit or several digits, or all digits of the IMSI. When analyzing the IMSI, the MSOFTX3000 matches the IMSI with the IMSI prefix based on the best match rule, to determine the handover area allowed for the subscriber during a call.


z Digits: 0-9 z Upper case letters: A-Z



z Lower case letters: a-z z Hyphen: - z Dot: . z Chinese characters

PLMN 1

It specifies the PLMN to which a 3G subscriber can be switched in connection mode. A PLMN number consists of a mobile country code (MCC) and a mobile network code (MNC). For example, 46001 and 46002 are valid PLMN numbers. It is up to six digits. The principles for setting the parameter are as follows:

z PLMN 1 is mandatory. Other parameters are optional. z To restrict the handover range of a subscriber based on a PLMN, set only PLMN

1-PLMN 4. To restrict the handover range of a subscriber based on an SNA, set PLMN 1-PLMN 4 and SNA group number 1-SNA group number 4 simultaneously. Moreover, SNA group number 1-SNA group number 4 must be the SNAs within PLMN 1-PLMN 4.


SNA group name 1

It specifies the SNA group name of an SNA to which a 3G subscriber can be switched. The parameter supports the keyword INVALID (indicating that the parameter is invalid). If another valid SNA group name is set, the parameter must be defined by ADD SNAGRPCODE before being referenced here. The principles for setting the parameter are as follows:

z The SNA group name must be within an SNA within the PLMN. That is, SNA group number 1-SNA group number 4 must be the SNAs within PLMN 1-PLMN 4.


PLMN 2

It specifies the PLMN to which a 3G subscriber can be switched in connection mode. A PLMN number consists of a mobile country code (MCC) and a mobile network code (MNC). For example, 46001 and 46002 are valid PLMN numbers. It contains up to six digits. The principles for setting the parameter are as follows:




Configuration Guide



SNA group name 2




PLMN 3





SNA group name 3






PLMN 4


z PLMN 1 is mandatory. Other parameters are optional. z To restrict the handover range

Documents

01-13 Configuring Advanced Mobile Service Data(1)