gu hlr9820 maintenance manual - basic and multi-msisdn services.doc

Huawei Technologies Co. Ltd.Product VersionConfidentiality Level

V1.0.1INTERNAL

Product Name: HLR9820Total Page: 32

HLR9820 Maintenance Manual - Basic and Multi-MSISDN ServicesVersion:1.0.1

2009-7-8

Huawei Technologies CO., LTD.

All Rights ReservedChange HistoryDateRevised VersionRevised Chapter and SectionDescriptionPrepared By

2009-7-81.0.0Draft completedHLR service maintenance group

2009-7-241.0.1Modified according to the review commentsHLR service maintenance group

Contents51 Service Introduction

51.1 Teleservice

61.2 Bearer Service

81.3 Multi-MSISDN Service

81.3.1 Single-MSISDN and Multi-MSISDN

81.3.2 Single-MSISDN Scheme

81.3.3 Multi-MSISDN Scheme

91.3.4 ALS Service

91.3.5 VVDN Service

91.3.6 MULTISDN

102 Service Implementation

102.1 Teleservice

102.2 Bearer Service

122.2.1 Implementation of Bearer Services in a Call Process

132.2.2 Processing of Bearer Services in a Call Process

162.2.3 Bearer Service Implementation of Huawei HLR


172.3.1 ALS Service

192.3.2 VVDN Service

202.3.3 MULTISDN

213 Service Configuration

213.1 Teleservice

213.1.1 Subscription

223.1.2 Configuration Example for the Live Network

223.2 Bearer Service

223.2.1 BS20

223.2.2 BS30



253.3.1 VVDN

253.3.2 ALS

263.3.3 MULTISDN

274 Troubleshooting

274.1 Scenario 1

274.1.1 Symptom

274.1.2 Impact and Solution

274.2 Scenario 2

274.2.1 Symptom


314.3 Scenario 3

314.3.1 Symptom


314.4 Scenario 4

314.4.1 Symptom


325 References

325.1 Case

325.2 FAQ

325.3 Protocol

325.4 Acronyms and Abbreviations

1 Service Introduction

According to the 3GPP protocol, the basic services consist of the teleservice and the bearer service. Figure 1-1 describes the scope of the two services. Figure 1-1 Scope of the bearer service and teleservice

1.2 Teleservice

Teleservices include the speech transmission service, data service, and short message service. Each service contains different sub-services, as shown in Table 1-1.

Table 1-1 Types of teleservice

TypeSub-services

Speech transmission serviceTS11: Telephony service

TS12: Emergency call

Data serviceTS61: Alternate speech and facsimile group 3

TS62: Automatic facsimile service group 3

Short message serviceTS21: Mobile-terminated point-to-point (MT-PP) short message service

TS22: Mobile-originated point-to-point (MO-PP) short message service

1.3 Bearer Service

Bearer services provide the capability for information transfer between terminal access points. They are characterized by a set of lower layer attributes in reference to Layer 1 to Layer 3 in the Open System Interconnection (OSI) reference model. Bearer services are prerequisites for a mobile telecommunication system to provide data services.

The bear service comprises a series of independent services. Subscribers can subscribe to one or several of them. Each bearer service has a service code.

The bearer services consist of the data circuit duplex synchronous (CDS) and data circuit duplex asynchronous (CDA) services. The maximum rate of bearer services can be 64 kbit/s. The bearer services are widely used, for example, they are used for data transfer and video conference.

The bearer services can be divided into the GSM bearer service and UMTS bearer service.

The GSM bearer services supported by the HLR9820 consist of BS21 to BS26, BS31 to BS34, BS40 to BS46, BS50 to BS53, BS61, and BS 81. The UMTS bear services supported by the HLR9820 include BS20 and BS30.

BS2X (BS20-26) services support the circuit-switched, full-duplex, and asynchronous data transmission. These services can be transparent or non-transparent. They are used for the communication between data terminals and provide the 3.1 kHz audio connection or 64 kbits/s unrestricted digital connections. BS3X (BS30-34) services support the circuit-switched, full-duplex, and synchronous (bit-based) data transmission. These services are used for the basic packet access. BS4X (BS40-46) services support the circuit-switched, full-duplex, and asynchronous data transmission. These services allow terminals that do not support the complicated bearer services to communicate with the X25-compliant terminals through the X28 protocol. The BS4X services connect the packet assembler/disassembler (PAD) to the packet switched public data network (PSPDN) directly, instead of through the integrated services digital network (ISDN) and the public switched telephone network (PSTN). BS5X services support full-duplex and synchronous data transmission, and also support the synchronous terminals to gain access to the packet PSPDN in packet mode. Table 1-2 lists the service groups and categories of the bearer services.

Table 1-2 Service groups and categories that the bearer services comprise

Bearer service categoryDescription

BS20Bearer Service 20, general high-speed asynchronous bearer service, defined independently of the data transmission rate of the mobile station (MS)

Data CDA serviceBS21Bearer service 21, data circuit duplex asynchronous (CDA)-300 bit/s

BS22Bearer service 22, data CDA-1200 bit/s

BS23Bearer service 23, data CDA-1200-75 bit/s




BS30Bearer Service 30, general high-speed asynchronous bearer service, defined independently of the data transmission rate of the MS

Data CDS serviceBS31Bearer service 31, data circuit duplex synchronous (CDS)-1200 bit/s

BS32Bearer service 32, data CDS-2400 bit/s



PAD access CA serviceBS41Bearer service 41, PAD Access CA-300 bit/s

BS42Bearer service 42, PAD Access CA-1200-75 bit/s

BS43Bearer service 43, PAD Access CA-1200 bit/s




Data packet duplex synchronous (PDS) serviceBS51Bearer service 51, data PDS-2400 bit/s

BS52Bearer service 52, data PDS-4800 bit/s

BS53Bearer service 53, data PDS-9600 bit/s

Alternate speech/data serviceBS61Bearer service 61, Alternate Speech/Data

Telephony data service BS81Bearer service 81, speech followed by data (it can be any data service)

The data transmission rate "1200-75 bit/s" indicates that the uplink data rate is 75 bit/s and the downlink data rate is 1200 bit/s. The data is exchanged between the MS and the base transceiver station (BTS). The data is transmitted from the MS to the BTS at a rate of 75 bit/s and form the BTS to the MS at a rate of 1200 bit/s.


1.4.1 Single-MSISDN and Multi-MSISDN

When a subscriber originates a data call, the system must inform the called subscriber of the service type in a certain manner. In an MOC, the bearer capabilities included in the Setup message indicate the service requirements of the calling subscriber. The GMSC sends an SRI message that includes the bearer capabilities to the HLR. Based on the received bearer capabilities and the bearer capabilities defined by the called subscriber, the HLR negotiates the bearer capabilities that the called MS/UE supports. Then, the HLR sends a PRN message that includes the negotiated bearer capabilities to the MSC/VLR. If an inter-office message, such as a PSTN subscriber calling a PLMN subscriber, does not include any bearer capabilities, bearer capabilities must be transferred by using appropriate methods. The multi-MSISDN function is implemented for provision of different services. The multi-MSISDN scheme facilitates transferring of bearer capabilities.1.4.2 Single-MSISDN Scheme

The single-MSISDN service allows the home PLMN to allocates one MSISDN to one subscriber who can use all services. If the information contained in the SRI received by the HLR cannot be converted into GSM BC, the PRN request message sent by the HLR to the VLR does not contain the GSM BC.

No GSM BC information element (IE) is contained in the Setup message sent to the MS of the called subscriber, because no GSM BC is associated with the MSRN in the MSC server/VLR. Therefore, the MS returns one or two complete GSM BC IEs in the Call Confirmed message containing the information of the service required by the MS. The VMSC checks whether the GSM BC IE satisfies. If yes, the VMSC establishes the call connection. Otherwise, the call is released. For details about the single-MSISDN procedure, see 2.2.1 "Implementation of Bearer Services in a Call Process."1.4.3 Multi-MSISDN Scheme

The multi-MSISDN service allows the HLR to provide different data services for different MSISDNs of a subscriber. When a subscriber makes a call of a certain service type to a multi-MSISDN subscriber, the subscriber can dial the MSISDN corresponding to that service type. On receiving the SRI message sent from the GMSC, the HLR detects that the SRI message does not contain any bearer capability. It then obtains the bearer capability associated with the MSISDN from the database, and sends the PRN request that contains the queried bearer capability to the VMSC or VLR. Then, the called subscriber is informed of the service requested by the calling subscriber. For details about the multi-MSISDN service procedure, see 2.2.1 "Implementation of Bearer Services in a Call Process."The HLR9820 supports several multi-MSISDN applications, such as ALS and VVDN. The following describes the detailed service implementation.

1.4.4 ALS Service

The Alternative Line Service (ALS) has two alternative lines that allow a subscriber to have two different MSISDNs with one MS and one SIM. The two MSISDNs are charged separately, which brings convenience for users. The ALS requires support of the MSC and VLR, and two alternative lines (line 1 and line 2) from the MS.

Most GSM MSs provide dedicated settings for the line 1 and line 2. When different lines (line 1 or line 2) are used, the BC contained in the Setup message is different and the number displayed to the called subscriber is different. Therefore, the number is charged separately based on the MSISDN. A subscriber with two MSISDNs can be presented with the calling numbers in different ways and can set CF, CB, and CW services differently for the two MSISDNs. The MSISDN of line 2 can be used for the voice services, supplementary services, and ODB services only. If a subscriber has subscribed to the ODB service, the service is provided for the MSISDNs of both the line 1 and line 2. The MSISDN of line 2 can only receive short messages. You cannot send short messages or perform USSD operations through the MSISDN of line 2.Subscribers of SUNDAY 2G network can send messages and perform USSD operations through the MSISDN of line 2. However, the MSISDN of line 1 and line 2 cannot be charged separately, and the line 1 CDR is generated for messages and USSD operations.1.4.5 VVDN Service

The Voice&Videophone Dual Number (VVDN) service allows a subscriber to set different MSISDNs for the voice service and videophone service. When the subscriber makes calls, the MSISDN displayed to the called party varies according to the call type. If the subscriber makes a voice call, the MSISDN for the voice service is presented to the called subscriber. If the subscriber makes a VP call, the MSISDN for the VP service is presented to the called subscriber.

The VVDN service can be provided only when the MSC/VLR supports the VVDN service and the MS supports the bearer service BS20 or BS30. Only subscribers whose NAM is OnlyMSC or Both can use the VVDN service.

If a subscriber is provided with the ALS and VVDN services, the subscriber has three MSISDNs:

Basic MSISDN (MSISDN 1)

Line 2 MSISDN for the ALS service (MSISDN 2)

MSISDN for the VVDN service (MSISDN 3)

The HLR uses different indicators (default call) to identify MSISDN 2 and MSISDN 3. The two numbers do not conflict with each other.

1.4.6 MULTISDN

The SET MULTISDN command is used to set the default call process or the bearer capability for a specific multi-MSISDN service, such as VVDN. The MSISDN parameter can either be the main MSISDN or the auxiliary MSISDN. You can use it to add an auxiliary MSISDN associated with a data service and the bearer capability. You can also use it to modify the bearer capability of a specific subscriber or the default call process.

This service is used to specify the bearer capability for a specific multi-MSISDN or add an auxiliary MSISDN with a specific bearer capability.

2 Service Implementation

2.1 Teleservice

The HLR9820 supports all teleservices. When a subscriber has subscribed to multiple services, some services may fail to be provided in some scenarios.

For example, a subscriber has subscribed to the speech service and facsimile service but has not subscribed to multi-MSISDN services, the fax from a fixed subscriber may fail to be sent to a mobile subscriber. For details, see 4.2

REF _Ref344716944 \h Scenario 2. For details about the teleservice process, such as call process and Send Routing Info for SM process, see the related process description.

The call initiated by an ISDN subscriber or a mobile subscriber carries the ISDN-BC. However, the call initiated by a PSTN subscriber does not carry the ISDN-BC. If the ISDN-BC is carried in the call, the HLR converts the ISDN-BC to the PLMN-BC, inserts the PLMN-BC into the NetworkSingalinfo IE of the PRN message, and sends the message to the VLR. If the ISDN-BC is not carried, the HLR sends the PLMN-BC for the calling subscriber based on the DEFAULTCALL value. Therefore, if the settings of the default call are incorrect, the call fails. The default call is set during the registration. The default value is TS11. You are advised not to change this value. In a multi-MSISDN scheme, the SET MULTISDN command is used to set the default call. In an ALS multi-MSISDN scheme, you do not need to set the default call for the auxiliary MSISDN.

2.2 Bearer Service

Bearer services provide the capability for information transfer between access points without changing the contents of the messages. They are characterized by a set of lower layer attributes in the Open System Interconnection (OSI) reference model. The MS/UE integrates the transmission function and the information processing function to provide the functions of both the lower-layer and higher-layer OSI reference model. The bear service defines the requirements for network that provides the bear services. The MS/UE provides both the terminal service and the networking capabilities. The bear service and terminal service can be provided together with the supplementary service or provided separately. However, the supplementary service must be provided with one or multiple bearer services or terminal services.

The attributes describing the bearer services in the OSI reference model are as follows:

Information transfer attributes: Defines the information transferring capabilities, such as model, rate, how to establish the transfer, and whether the information is compressed. It focuses on the network transferring capabilities between two access points. Access attributes: Defines the features of subscribers' devices on the access points. Interworking attributes: Defines the termination network type, and the features of access points for terminals and the termination network. General attributes, including operational and commercial attributes: Defines the technical features of a bearer service on access points. The bearer service is described by the first three attributes at present. To enable different terminals to access PLMN to provide various teleservices, the service access point is pre-defined. In the GSM PLMN reference configuration, as shown in Figure 2-2, the bearer service is provided on R and S reference points, and only lower layers (layer 1 to layer 3 in the OSI reference model) are involved. The position of the terminal services is indicated by the dotted line highlighted in red.

Figure 2-2 GSM PLMN reference configuration

TE1: ISDN terminalTE2: V- or X-type terminalTA: Terminal AdapterBSS: Base Station System CenterMSC: Mobile Switching

2.2.2 Implementation of Bearer Services in a Call ProcessFigure 2-3 Call process

The following describes how to process the bearer capability in a call flow.

In a mobile terminated (MT) call, if a calling subscriber defines the bearer capability required by the service, this bearer capability is used to establish the call connection on the network. If no bearer capability is carried, the HLR uses the following schemes to determine the bearer capability required for the call.

2. Multi-MSISDN scheme: In multi-MSISDN schemes, each MSISDN of the called subscriber has a bearer capability. In an MOC, the required bearer capability is determined by the MSISDN of the called subscriber.

3. Single-MSISDN scheme: In single-MSISDN schemes, the network elements process a call as follows: The HLR does not include the bearer capability in PRN messages. In the MSC/VLR, no GSM BC IE is contained in the Setup message of the MS during the call connection process, because no GSM BC is associated with the MSRN. Therefore, the MS returns one or two complete GSM BC IEs in the Call Confirmed message containing the information of the service required by the MS. The VMSC checks whether the GSM BC IE satisfies. If yes, the VMSC establishes the call connection. Otherwise, the call is released.

The multi-MSISDN scheme and the single-MSISDN scheme can coexist. For details about the two schemes, see 1.2 "Bearer Service."In a MO flow, the calling subscriber can send messages containing the bearer capability to the network, the network establishes the call connection based on the bearer capability.

2.2.3 Processing of Bearer Services in a Call Process

There are two service processing methods for bearer services: PSTN to PLMN and ISDN to PLMN.

PSTNPLMNFor a PSTN to PLMN call, the SRI message does not carry bearer capacity and then the HLR adds the bearer capacity after it receives the SRI message. The PSTN to PLMN call consists of single-MSISDN and multi-MSISDN calls based on the message processing methods of the HLR.

Figure 2-4 Multi-MSISDN PSTN to PLMN call flow

In a multi-MSISDN PSTN to PLMN call, the HLR sends the default PLMN-BC (GSM-BC) contained in the PRN request message to the VLR, the VMSC extracts the PLMN-BC from the VLR based on the MSRN and sends the PLMN-BC to the MS. The MS compares the parameters sent from the VLR with the parameters stored on the MS to determine whether to receive or reject the call. Figure 2-3 shows the multi-MSISDN PSTN to PLMN call flow

Figure 2-4 shows the GSM-BC IE.Figure 2-5 GSM-BC IE

Figure 2-6 Single-MSISDN PSTN to PLMN call flow

In a single-MSISDN scheme, the HLR does not send the PLMN-BC to the VLR. The Setup message sent by the MSC does not contain the PLMN-BC. The PLMN-BC is carried in the message for call connection, and the VMSC compares the parameters sent from the message for call connection with the parameters stored on the VMSC to determine whether to receive or reject the call, as shown in Figure 2-5.

The single-MSISDN scheme of Huawei HLR is optimized by configuring a default call for subscribers. If the SRI request sent by the GMSC to the HLR does not contain network singling information, the HLR sends the default PLMN-BC (GSM-BC) to the VLR based on the PRN request message of the default call.

ISDNPLMNFor an ISDN to PLMN call, the SRI message may carry a complete ISDN-BC IE that provides information about the call type. The HLR converts the ISDN-BC into a PLMN-BC and sends it to the VLR.

If the SRI request message does not carry an ISDN-BC IE, or the HLR cannot determine the call type based on the ISDN-BC IE, the HLR processes the call in the same way as a PSTN to PLMN call.

If the SRI message carries the ISDN-BC, the ISDN-BC is carried in the NetworkSingalinfo IE, as shown in Figure 2-6. Figure 2-7 NetworkSingalinfo IE in the SRI message

The NetworkSingalinfo IE consists of the ISDN-BC, HLC, and LLC. Figure 2-8 NetworkSingalinfo IE structure

In a NetworkSingalinfo IE the ISDN-BC starts with 0x04, the HLC starts with 0x7D, and the LLC starts with 0x7C. The HLC and LLC are used in ISDN to PLMN calls.

2.2.4 Bearer Service Implementation of Huawei HLR

Huawei HLR implements bearer services by integrating the single-MSISDN and multi-MSISDN schemes. The MSISDN in the single-MSISDN scheme is the main MSISDN and that in the multi-MSISDN scheme is the auxiliary MSISDN.

To enable the single-MSISDN scheme to provide more functions, Huawei HLR defines a default call. When a subscriber makes a call with a certain type of data service:

The HLR9820 extracts the information about the basic services from the ISDN-BC, converts the ISDN-BC to the PLMN-BC, and sends it to the VLR if the ISDN-BC is carried.

The HLR9820 sends a PLMN-BC with the main MSISDN if no ISDN-BC is carried. The HLR9820 regards the basic services of the default call as the basic services of the calling subscriber. The HLR9820 also checks whether the basic services have the required bearer capability. If yes, the HLR9820 sends the bearer capability to the VLR. Otherwise, the bearer capability is not carried in a PRN message.


2.3.1 ALS Service

Service Implementation

1. The extended teleservice code 0xD1 (plmn specific TS-1) defined in the GSM/3GPP protocol is used for the ALS service.2. The HLR inserts the MSISDN1 (the main MSISDN of the line 1 for the ALS service), MSISDN2 (the auxiliary MSISDN of the line 2 for the ALS service), and the extended IE in the ISD_REQ message to be used by the MSISDN2 in the ISD_REQ message.

3. In a UE to CN call, if the value of the ITC is 110 in the BC_IE carried by the SETUP message, the SRI_REQ message sent by the MSC to the HLR do not contain the network signaling information. The basic service code carried in the SRI_RSP response message is 0xD1 (a5|03|83|01|d1|), indicating the PLMN-specific TS-1.4. The value of the ITC is 110 in the GSM_BC carried by the PRN message sent by the HLR and in the BC_IE carried by the Setup message sent on the A/Iu interface if the called number is the MSISDN if the line 2 in a voice call.

5. The basic service is 0xD1 when you register or activate supplementary services, such as CF and CB services for the MSISDN of the line 2.

6. The service code in the CDR is 0xD1 for the voice all initiated by the MSISDN of the line 2.

ALS Service Procedure

1. Subscription

Subscribers, including IN subscribers, can subscribe to Huawei ALS services. However, IN subscribers can subscribe to the ALS service only when the same CSI data is used by the MSISDNs of the line 1 and line 2. Besides the ALS service, the MSISDN of the line 1 can also subscribe to voice, VP, SMS, and other supplementary services. The MSISDN of the line 2 can subscribe to the user-defined auxiliary speech services and other supplementary services, including the FU, CFB, CFNRy, CFNRc, CW, CH, Multiparty, CLIP/CLIR, COLP/COLR, BAOC, BOIC, BAIC, BOICexHC, and BICROAM services. Only the MSISDN of the line 1 can subscribe to the Facsimile service and other data services. Generally speaking, only the MSISDN of the line 1 can subscribe to the short message services. However, according to SUNDAY's feedbacks, the MSISDN of the line 1 is displayed for the called subscriber no matter the MSISDN of the line 1 or line 2 is used to send the messages. This indicates that the MSISDN of line 2 can also subscribe to the short message services. The SMS CDRs of the line 2 are generated for the short messages sent by the MSISDN of the line 1, without requirements for the MSC.

Only subscribers whose NAM is MSC or BOTH can subscribe to the ALS services.

2. Location update

When the VLR sends the location update request to the HLR, the VLR determines whether ALS is supported based on the MAP configuration and AC information. If the ALS is configured to be not supported, the VLR sends a common location update message, and the extended IEs do not contain the vlr-Capability. If the ALS is configured to be supported, the VLR must use the vlr-Capability extended IE in the location update message to specify the capability of the ALS supported by the local office so that the HLR determines whether to send the subscription data about the ALS.

If the VLR detects that the extended IE is included in the vlr-Capability after the HLR receives the location update message, it decodes the message based on the following format. If the first bit indicating whether the MSC/VLR supports the ALS capability is set to 1 and the subscriber has subscribed to the ALS services, the HLR MAP must carry the basic voice service code 0x11 and the auxiliary voice service code 0xD1, and the MSISDN1 and MSISDN2 in the ISD_REQ message. According to SUNDAY's feedbacks, the auxiliary MSISDN of the line 2 must be encoded using the extended IE (the tag if the IE is AE) defined in the ISD_REQ message. If subscribers also subscribed to the supplementary services, such as the CF and CB services, the HLR also need to send data about the supplementary services to the VLR.

The VLR decodes the received ISD_REQ message sent from the HLR. If the VLR detects that the teleservice code 0xD1 and the extended IE whose tag is AE and extension ID is 2a 86 48 86 f6 7d 0e 48 are included in the message, the MSISDN of the line 2 that subscribes to the ALS service can be obtained from the extended IE. Otherwise, it is regarded that the subscriber does not subscribe to the ALS service or the HLR do not support the ALS. After the MSISDN of line 2 for the ALS service and information about other services to which the MSISDN has subscribed are obtained, the VLR needs to determine whether the ALS is supported based on the MAP configuration and AC information.

3. Mobile originated call

When the MSISDN of the line 2 is used to make a call, the ITC in the BC_IE is 110 in the Setup message sent by the MS/UE. After the MSC receives the Setup message sent by the MS, the call is an auxiliary voice call whose service code is 0xD1 (plmn specific TS-1), and the MSIDSN of the line 2 is charged.

4. Mobile terminated call

After receiving the SRI_REQ message from the VLR, the HLR checks the MSISDN of the called subscriber. If the called subscriber has subscribed to the ALS service and the MSISDN of the line 2 is included in the message, the PRN_REQ message carries the MSISDN of the line 2 and the GSM_BC in the following format:

After receiving the PRN_REQ message, the VMSC decodes the GSM_BC. If the service code is 0xD1 (ITC=110), the following operations should be performed:

If the local office supports the ALS, the MSC sends the BC_IE that is inserted in the Setup message, to the MS of the called subscriber. Then the MS displays different ringback tones. If the local office does not support the ALS, the VMSC returns the PRN_RSP message to the HLR with an error cause "facilityNotSupported". The HLR sends the SRI_RSP message with this error cause, and the GMSC rejects the call again.

5. Mobile-terminated short message (SM MT)

The short message processing flow of the MSISND of the line 2 is the same as that of the line 1. If the MSISDN of the line 2 is carried in the request, the IMSI and location information are returned.

6. Location service (LCS)

The Sending Route Infor for LCS flow of the MSISND of the line 2 is the same as that of the line 1. If the MSISDN of the line 2 is carried in the request, the IMSI and location information are returned.

7. Impact on supplementary services

The MSISNDs of line 1 and line 2 can subscribe to different supplementary services, such as CF, CB, and CW services based on the basic service groups. The service group of the telephony services is allSpeechTransmissionServices. The service group of the plmn-specificTS-1 is TSDX (allPLMN-specificTS).

For other supplementary services, the MSC/VLR controls whether the service is available to the MSISDNs of line 1 and line 2 or only the MSISDN of the line 1.

2.3.2 VVDN Service

Perform the following configurations before using the VVDN services:

8. Set the VP_CODE. Set the bear service code of the VP using the VP_BSCODE parameter in the SET MAPSERV command. The bear service code is determined by the policies of carriers. The following is an example command for set the code:

SET MAPSERV: VP_BSCODE=0X1f_BS30;9. Add the bearer capability alias. Run the ADD BCALIAS command to add a bear capability alias. The parameter DSCODE of the data service code must be consistent with the VP_CODE. Set the ITC to 3.1 kHz Audio or UDI according to the actual condition. Use the default value of other parameters. You can also refer to the data configuration of the BS30 to set parameters for adding a bear capability alias. The following is an example command for adding a bear capability alias:

ADD BCALIAS: HLRSN=1, ALIASNAME="BS30", DSCODE=BS30, ITC=Unrestricted Digital Info, TM=CM, RCR=Full Rate Support only MS, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=Other, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, NICRX=FALSE, NICTX=FALSE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent, FNUR=64.0 Kbit/s Recommendation X.1 7 &V.110, WAIUR=9.6 Kbit/s, CS=GSM Standardized Coding, DM=Full Duplex, CFG=Point to Point, NIRR=No Meaning, ESTD=Demand, OITC=Restricted Digital Information, ORA=H.223 & H.245, UL1P=Default Layer 1 Protocol, OMT=Not Other Modem Type Specified, ACC=TCH/F14.4 Acceptable, UIMI=User Initiated Modification Not Allowed/Required/Applicable;10. Provide the VVDN service for subscribers. Run the MOD VVDN command to provide the VVDN service for subscribers. The following is an example command for providing the VVDN service for subscribers whose IMSI is 111111111111111:

MOD VVDN: IMSI="111111111111111", PROV=TRUE;11. Associate a bear capability with an auxiliary MSISDN. Run the SET MULTISDN command to provide an auxiliary MSISDN for a subscriber. The value of DEFAULTCALL in the command must be consistent with that of the VP_CODE. The bear capability and its alias are optional parameters. If the bear capability alias is required, keep the alias consistent with the one added in the previous step. The following is an example command for associating a bear capability with an auxiliary MSISDN 222222222222222:

SET MULTISDN: IMSI="111111111111111", ISDN="222222222222222", DEFAULTCALL=BS30, BCALIAS="BS30";

The MSISDNs for the ALS and the VVDN are all auxiliary MSISDNs and are stored in the ISDN_DATA table. They are distinguished from each other by their second field (BC_IE and DEL_CALL) in the ISDN_DATA table. The CiTC of the BC_IE of the MNISDN for the ALS service is 6. The first byte of the DEL_CALL field indicates the service type that can be TS or BS. The second byte of the DEL_CALL field indicates the service code. (The service code of the ALS service is plmn_specficTS_1, and it is indicated by the PROVISINTS field in the SUB_DATA table.) The DEL_CALL field uniquely identifies the MSISDN for the VVDN service. The service code in the DEL_CALL field is mandatory because the service code is used to determine the service type. The SET MAPSERV command is used to set the service code for the VP service. If the query results sent by the DS contain multiple records that meet the requirements, the HLR9820 uses the first one for the VVDN service. Only subscribers whose NAM is MSC or BOTH can subscribe to the VVDN services. The requests for adding or deleting a subscriber who has subscribed to the VVDN service are sent to only the VLR. The request for deleting a subscriber does not carry the MSISDN for the VVDN service.

The MAP procedure for the VVDN service includes the location update, data restoration, and SRI.

To implement the location update, the MSISDN for the VVDN service must meet the following requirements: 12. The MAP version is MAP 3.

13. The VLR supports the VVDN service. (You can check the carried extended IE to see whether the VLR supports the VVDN service.)

14. The MSISDN of the VVDN service supports the BS20 or BS30 service.

15. The default call type of the auxiliary MSISDN is consistent with that configured in the VP_BSCODE.

After the requirements are met, the VVDN service is provided using the extended IE. The process of the location update is the same as that of the data restoration.

In a SRI procedure, the HLR checks whether the subscriber exists and whether the MSISDN is for the ALS service or the VVDN service. If the MSISDN is for the VVDN service, and the call type is different from the default one, the error code BEARER_SERVICE_NOT_PROVISIONED is displayed. If the call type is neither TS nor BS, the error code UNEXPECTED_DATA_VALUE is displayed. If the call type is the default one, the bearer capability of the service is inserted into the PRN request. After the VLR receives the PRN messages, the error code facilityNotSupported is returned to the HLR if the VLR does not support the VP number service. Then the HLR returns the error code to the GMSC.

2.3.3 MULTISDN

Implementation

To implement the multi-MSISDN function, the HLR must store the PLMN-BC for the MSISDNs. Therefore, carriers must run the ADD BCALIAS command on the SMU client to define the bearer capabilities for the basic services.

After a bearer service is provided, the SET MULTISDN can be used to set the default call process for a specific multi-MSISDN. The setting of Default call process must be consistent with the setting of Basic service corresponding to the bearer capability. Otherwise, the multi-MSISDN service cannot be provided.

The multi-MSISDN service is unavailable if the subscriber is not provided with the bearer service required for enabling the multi-MSISDN service. If the HLR does not define the bear capability when subscribers subscribe to multi-MSISDN service, the HLR processes the MSISDN based on the single-MSISDN scheme.The services supported by the HLR9820 include TS61 and TS62, BS20 to BS26, and BS30 to BS34.

3 Service Configuration

3.1 Teleservice

3.1.1 Subscription

To provide teleservices for subscribers who use multi-MSISDN schemes and the Facsimile service, the bear capability needs to be configured for the subscribers. You can run the ADD BCALIAS command to add, the MOD BCALIAS command to modify, the RMV BCALIAS command to delete, and the LST BCALIAS command to query the bearer capability alias.

For details about the parameter of the bearer capability alias, see the Help of the SMU. When STRUCT is set to SDUI, CE must be set to NON TRANSPARENT. When STRUCT is set to UNSTR, CE must be TRANSPARENT.

You can configure the data for the HLR to provide TS61 and TS62 services based on the parameters provided by the carriers. The following is only the recommended data configuration for your reference.

To add a bearer capability alias for the TS61 service, you can specify the HLRSN based on the actual condition, set DSCODE to TS61 and ITC to Alternate Speech/Facsimile Group 3, and use the default values for other parameters. For example, you can run the following command to add the bear capability alias for the TS61 service:

ADD BCALIAS: HLRSN=1, ALIASNAME="TS61", DSCODE=TS61, ITC=Alternate Speech/Facsimile Group 3;To add a bearer capability alias for the TS62 service, you can specify the HLRSN based on the actual condition, set DSCODE to TS62 and ITC to Facsimile Group 3, and use the default values for other parameters. For example, you can run the following command to add the bear capability alias for the TS62 service:

ADD BCALIAS: HLRSN=1, ALIASNAME="TS62", DSCODE=TS62, ITC= Facsimile Group 3;The TS61 and TS62 support multiple values for the bearer capability. You can manually enter values to configure the desired bearer capability. However, restrictions exist among parameters of the bearer capability, and some values maybe not supported by a specific bearer capability. For details about the restrictions, see 3GPP 27.001. Therefore, you are advised to use the default values for configuring the bearer capabilities for the TS61 and TS62 services.

Different carriers may use different coding format to process messages. Therefore, if subscribers cannot receive faxes, you can modify the value of STRUCT of the bearer capability to rectify the faults.

After the bearer capability alias is added, you can run the SET MULTISDN command to provide the desired auxiliary MSISDN for subscribers. The settings of the DEFAULTCALL parameter in the SET MULTISDN command must be consistent with that of the DSCODE parameter for the bearer capability alias.


The following is the example configurations for adding a bearer capability alias, and they are for your reference only.

ADD BCALIAS: HLRSN=1, ALIASNAME="92", DSCODE=TS62, ITC=Facsimile Group 3, STRUCT=UNSTR, COMP=FALSE, RA=No Rate Adaption, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="91", DSCODE=TS61, ITC=Alternate Speech/Facsimile Group 3, STRUCT=UNSTR, COMP=FALSE, RA=No Rate Adaption, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;3.2 Bearer Service

The following describes the parameter configurations of the BS20 and BS30 services.

3.2.1 BS20

BS20 is a circuit duplex asynchronous data service. The provisioning of the BS20 service is similar to that of the TS61 service. To provide the BS20 service, you need to specify the basic service code of a certain bearer capability, the ITC, and the RA. The ITC can be set to the Unrestricted Digital Info, 3.1 kHz Audio, or Restricted Digital Information. If the ITC is set to UDI, the RA can be V.110 I.460/X.30 Rate Adaption, ITU-T X.31 Flag Stuffing, or PIAFS. If the ITC is set to 3.1 kHz Audio, the RA must be set to No Rate Adaption. If the ITC is set to RDI, the RA must be V.120. The BS20 is a common bearer service and supports multiple rates ranging from 0.3 kbit/s to 56 kbit/s. Therefore, the BS20 service can replace the BS21, BS22, BS24, BS25, and BS26 services. Default values are used for other parameters.

The BS21 to BS26 services are the dedicated bearer services, and each service support only one rate. To provide the dedicated bearer services, you only need to specify the basic service code and the ITC. The ITC of the BS20 to BS26 services can be UDI, 3.1 kHz Audio, or RDI. 3.2.2 BS30

BS30 is a circuit duplex synchronous data service that supports the rates ranging from 1.2 kbit/s to 64 kbit/s except 33.6 kbit/s. Therefore, the BS30 service can replace the BS31 BS32, BS33, and BS34 services. To provide the BS30 service, you need to specify the basic service code of a certain bearer capability and the ITC. The ITC supported by the BS30 are UDI and 3.1 kHz Audio. You can select the default values of the other parameters.

The BS31 to BS34 services are the dedicated bearer services, and each service support only one rate. To provide the dedicated bearer services, you only need to specify the basic service code of a certain bearer capability and the ITC. The ITC of the BS30 to BS34 services can be UDI or 3.1 kHz Audio. 3.2.3 Configuration Example for the Live Network

ADD BCALIAS: HLRSN=1, ALIASNAME="BS20", DSCODE=BS20, ITC=3.1KHz Audio, TM=CM, RCR=Full Rate Support only MS, STRUCT=SDUI, COMP=FALSE, ASYNC=TRUE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, NICRX=FALSE, NICTX=FALSE, INTRAT=16 Kbit/s, MT=Autobauding Type 1, CE=Non Transparent, FNUR=28.8 Kbit/s Recommendation X.1 & V.110, DM=Full Duplex, NIRR=No Meaning, OMT=Not Other Modem Type Specified, ACC=TCH/F14.4 and 9.6 Acceptable, NOTC=1TCH, UIMI=User Initiated Modification Not Allowed/Required/Applicable;ADD BCALIAS: HLRSN=3, ALIASNAME="31", DSCODE=BS21, ITC=Unrestricted Digital Info, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=TRUE, UR=0.3Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="30", DSCODE=BS21, ITC=3.1KHz Audio, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=TRUE, UR=0.3Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.21, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="121", DSCODE=BS22, ITC=Unrestricted Digital Info, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=TRUE, UR=1.2Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="120", DSCODE=BS22, ITC=3.1KHz Audio, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=TRUE, UR=1.2Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.22, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="240", DSCODE=BS24, ITC=3.1KHz Audio, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=TRUE, UR=2.4Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.22 Bis, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="241", DSCODE=BS24, ITC=Unrestricted Digital Info, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=TRUE, UR=2.4Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="480", DSCODE=BS25, ITC=3.1KHz Audio, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=TRUE, UR=4.8Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.32, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="481", DSCODE=BS25, ITC=Unrestricted Digital Info, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=TRUE, UR=4.8Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="961", DSCODE=BS26, ITC=Unrestricted Digital Info, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=TRUE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="960", DSCODE=BS26, ITC=3.1KHz Audio, STRUCT=SDUI, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=TRUE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.32, CE=Both Non Transparent Preferred;ADD BCALIAS: HLRSN=1, ALIASNAME="BS30", DSCODE=BS30, ITC=Unrestricted Digital Info, TM=CM, RCR=Full Rate Support only MS, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=Other, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, NICRX=FALSE, NICTX=FALSE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent, FNUR=64.0 Kbit/s Recommendation X.1 7 &V.110, WAIUR=9.6 Kbit/s, CS=GSM Standardized Coding, DM=Full Duplex, CFG=Point to Point, NIRR=No Meaning, ESTD=Demand, OITC=Restricted Digital Information, ORA=H.223 & H.245, UL1P=Default Layer 1 Protocol, OMT=Not Other Modem Type Specified, ACC=TCH/F14.4 Acceptable, UIMI=User Initiated Modification Not Allowed/Required/Applicable;ADD BCALIAS: HLRSN=1, ALIASNAME="127", DSCODE=BS31, ITC=Unrestricted Digital Info, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=FALSE, UR=1.2Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="125", DSCODE=BS31, ITC=3.1KHz Audio, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=FALSE, UR=1.2Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=V.22, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="247", DSCODE=BS32, ITC=Unrestricted Digital Info, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=FALSE, UR=2.4Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="245", DSCODE=BS32, ITC=3.1KHz Audio, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=FALSE, UR=2.4Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=V.22 Bis, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="485", DSCODE=BS33, ITC=3.1KHz Audio, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=FALSE, UR=4.8Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=V.32, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="487", DSCODE=BS33, ITC=Unrestricted Digital Info, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=FALSE, UR=4.8Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=8 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="967", DSCODE=BS34, ITC=Unrestricted Digital Info, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=V.110 I.460/X.30 Rate Adaption, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent;ADD BCALIAS: HLRSN=1, ALIASNAME="965", DSCODE=BS34, ITC=3.1KHz Audio, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=No Rate Adaption, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, INTRAT=16 Kbit/s, MT=V.32, CE=Transparent;3.3 Multi-MSISDN Service

The following sections describe the provisioning of multi-MSISDN services.

3.3.1 VVDN

For details about how to provide the VVDN service for subscribers, see 2.3.2 "VVDN Service."To provide the VVDN service, specify VP_CODE. You can obtain the value of VP_CODE from the carrier. For details about the functions of VP_CODE, see 2 "Service Implementation."To set VP_CODE to BS20, run the following command:

SET MAPSERV: VP_BSCODE=0X17_BS20;To set VP_CODE to BS30, run the following command:

SET MAPSERV: VP_BSCODE=0X1f_BS30;3.3.2 ALS

You can run the MOD ALS commands to provide or withdraw the ALS service.

MOD ALS: IMSI="111111111111111", PROV=TRUE, LINE2NUM="222222222222222";MOD ALS: IMSI="111111111111111", PROV=FALSE;To enable the HLR to provide the ALS service, run the ADD NCCTPL command with ALS to set to SR to enable the HLR to deliver ALS service data to the VLR.

ADD NCCTPL: HLRSN=1, TPLID=1, ALS=NR;ADD NCCTPL: HLRSN=1, TPLID=1, ALS=SR;MOD NCCTPL: HLRSN=1, TPLID=1, ALS=NR;MOD NCCTPL: HLRSN=1, TPLID=1, ALS=SR;For details about the NCC configuration and how to use NCC service, see HLR9823 Maintenance Manual - NCC Service.The service, such as the CF and CB used by the auxiliary MSISDN is based on TSDX. Therefore, you must set BSG to TSDX to activate the services. The following is an example command:ACT BAOC: IMSI="111111111111111", BSG=TSDX;REG CFU: IMSI="111111111111111", FTN="075512345678", PROPERTY=INTERNATIONAL, BSG=TSDX;3.3.3 MULTISDN

No global data configuration is required for the HLR to provide the Multi-MSISDN service. To provide the multi-MSISDN service for subscribers, configure the default call process and the bearer capability alias for the MSISDN. For details about how to configure the bearer capability alias, see 3.1 "Teleservice" and 3.2 "Bearer Service."The following example shows how to provide the MULTISDN service for subscribers. The BS30 service is used in this example.

1. Run the following command to add the bearer capability alias:

ADD BCALIAS: HLRSN=1, ALIASNAME="BS30", DSCODE=BS30, ITC=Unrestricted Digital Info, TM=CM, RCR=Full Rate Support only MS, STRUCT=UNSTR, COMP=FALSE, SAP=I.440/450, RA=Other, ASYNC=FALSE, UR=9.6Kbit/s Recommendation X.1 and V.110, NDB=8 Bits, NSB=1 Bit, PARITY=NONE, NICRX=FALSE, NICTX=FALSE, INTRAT=16 Kbit/s, MT=NONE, CE=Transparent, FNUR=64.0 Kbit/s Recommendation X.1 7 &V.110, WAIUR=9.6 Kbit/s, CS=GSM Standardized Coding, DM=Full Duplex, CFG=Point to Point, NIRR=No Meaning, ESTD=Demand, OITC=Restricted Digital Information, ORA=H.223 & H.245, UL1P=Default Layer 1 Protocol, OMT=Not Other Modem Type Specified, ACC=TCH/F14.4 Acceptable, UIMI=User Initiated Modification Not Allowed/Required/Applicable;2. Run the following command to add an auxiliary MSISDN for the subscriber.

SET MULTISDN: IMSI="111111111111111", ISDN="222222222222222", DEFAULTCALL=BS30, BCALIAS="BS30";To delete a Multi-MSISDN subscriber, run the following command. The value of the ISDN is the auxiliary MSISDN to be deleted.

RMV SUB: ISDN="222222222222222", RMVKI=FALSE;

If the value of the ISDN is set to the IMSI, this subscriber will be deleted.

4 Troubleshooting

4.1 Scenario 1

4.1.1 Symptom

A mobile subscriber who can properly make calls cannot receive calls from fixed subscribers. The HLR receives SRI messages for both calls, and the signaling configuration is correct.


This problem is caused by incorrect bearer capabilities. When a mobile subscriber initiates a call, the bearer capability is carried in the SRI message to indicate the call type. When a fixed subscriber initiates a call, the IAM message cannot carry the bearer capability. Therefore, the SRI message cannot indicate the call type. If the HLR receives the SRI message that cannot indicate the call type, the HLR processes the call based on the default call information of the subscriber. The HLR sends the PRN, carrying an identifier indicating that the call is a default call, to the VLR to which the called subscriber belongs. If the identifier of the default call is incorrect, the call fails. For example, if the fixed subscriber initiates a voice call, but the related setting of the default call is TS61, then the call fails. The solution is to modify the settings of the default call based on the actual condition. You call run the SET MULTISDN command to modify the settings of the default call. Set IMSI to IMSI number, ISDN to ISDN number, DEFAULTCALL to TS11, and leave BCALIAS empty.

4.2 Scenario 2

4.2.1 Symptom

A mobile subscriber who can properly make calls cannot receive faxes from fixed subscribers.


If the DEFAULTCALL of the subscriber is set to TS11, the subscriber can make or receive calls. When a mobile phone sends a fax, the phone carries a bearer capability. When the HLR receives a fax service request, it processes the request based on the bearer capability carried in the request. When a fixed phone sends a fax, the SRI sent by the GMSC to the HLR does not carry the bearer capability. The HLR considers that the service is a TS11 service based on the value of DEFAULTCALL. If DEFAULTCALL is set to TS61 or TS62, the fax can be sent to the subscriber. However, voice call initiated by a fixed subscriber will fail. The multi-MSISDN scheme can be used to solve the problem. You can use the SET MULTISDN command to add an auxiliary NSISDN for the subscriber and associate the MSISDN with the Facsimile service and the bearer capability. For details, see 3 "Service Configuration".

The following are the screenshots of the SRI and PRN messages generated when a mobile phone sends a fax and a fax machine sends a fax. The screenshots show that the GSM-BC exists in both of the PRN messages. However, the networksignalinfo IE is only contained in the PRN message generated when a mobile phone sends a fax. Figure 4-9 SRI message generated when a mobile phone sends a fax

Figure 4-10 PRN message sent by the HLR

Figure 4-11 SRI message generated when a fax machine sends a fax

Figure 4-12 PRN message sent by the HLR

4.3 Scenario 3

4.3.1 Symptom

A subscriber who has subscribed to the multi-MSISDN service (MULTISDN subscriber), and the DEFAULTCALL of the auxiliary MSISDN is set to TS61. The subscriber can be the calling subscriber but cannot receive the TS61 fax sent from a fixed-network subscriber.


You can run the SET MULTISDN command to provide multi-MSISDN services for the subscriber. The DEFAULTCALL and BCALIAS need to be specified. The specified bearer capability must bearer capability of the service defined by the default call. To solve this problem, you run the ADD BCALIAS command to add the bear capability alias of the TS61 service and run the SET MULTISDN command to specify the bearer capability alias for the auxiliary MSISDN of the subscriber.

4.4 Scenario 4

4.4.1 Symptom

A subscriber who has subscribed to the multi-MSISDN service (MULTISDN subscriber), the DEFAULTCALL of the auxiliary MSISDN is set to TS61, and the bearer capability alias for the TS61 service is specified. The subscriber can make or receive calls. However, the subscriber cannot receive the TS61 fax sent from a PSTN subscriber.


The codec of a fax can be structured or unstructured. If the structured codec is used but we set the value of the related parameter to unstructured, the fax will fail to be sent. You can change the data structure of the bearer capability alias to rectify the faults.

5 References

5.1 Case

5.2 FAQ

5.3 Protocol

For details about bearer services, see 22.002, 22.003, 23.018, 24.008, 27.001, 29.002, and 29.007 in the 3GPP protocol.

5.4 Acronyms and Abbreviations

IAM: Initial Address MessagePSPDN: Public Switching Packet Data Network

HLC: High Layer CompatibilityLLC: Low Layer Compatibility

gu hlr9820 maintenance manual - basic and multi-msisdn services.doc

Documents

bearer service bearer

als service

vvdn service

service configuration

bear service

service code

telephony service ts12

processing of bearer