Professional Documents
Culture Documents
Ltd.
Product Version
Confidentiality Level
V1.0.1
INTERNAL
Product Name:
HLR9820
Total Page: 32
Version:1.0.1
2009-7-8
INTERNAL
Change History
Date
Revised
Version
Revised
Chapter and
Section
2009-7-8
1.0.0
Draft completed
2009-7-24
1.0.1
2015-04-10
Description
Prepared By
Page 2 of 32
INTERNAL
Contents
1 Service Introduction......................................................................5
1.1 Teleservice.........................................................................................................................................................5
1.2 Bearer Service....................................................................................................................................................6
1.3 Multi-MSISDN Service.....................................................................................................................................8
1.3.1 Single-MSISDN and Multi-MSISDN......................................................................................................8
1.3.2 Single-MSISDN Scheme..........................................................................................................................8
1.3.3 Multi-MSISDN Scheme...........................................................................................................................8
1.3.4 ALS Service..............................................................................................................................................9
1.3.5 VVDN Service..........................................................................................................................................9
1.3.6 MULTISDN..............................................................................................................................................9
2 Service Implementation...............................................................10
2.1 Teleservice.......................................................................................................................................................10
2.2 Bearer Service..................................................................................................................................................10
2.2.1 Implementation of Bearer Services in a Call Process.............................................................................12
2.2.2 Processing of Bearer Services in a Call Process.....................................................................................13
2.2.3 Bearer Service Implementation of Huawei HLR...................................................................................16
2.3 Multi-MSISDN Service...................................................................................................................................17
2.3.1 ALS Service............................................................................................................................................17
2.3.2 VVDN Service........................................................................................................................................19
2.3.3 MULTISDN............................................................................................................................................20
3 Service Configuration..................................................................21
3.1 Teleservice.......................................................................................................................................................21
3.1.1 Subscription............................................................................................................................................21
3.1.2 Configuration Example for the Live Network........................................................................................22
3.2 Bearer Service..................................................................................................................................................22
3.2.1 BS20.......................................................................................................................................................22
3.2.2 BS30.......................................................................................................................................................22
3.2.3 Configuration Example for the Live Network........................................................................................23
3.3 Multi-MSISDN Service...................................................................................................................................25
3.3.1 VVDN.....................................................................................................................................................25
3.3.2 ALS.........................................................................................................................................................25
3.3.3 MULTISDN............................................................................................................................................26
2015-04-10
Page 3 of 32
INTERNAL
4 Troubleshooting..........................................................................27
4.1 Scenario 1........................................................................................................................................................27
4.1.1 Symptom.................................................................................................................................................27
4.1.2 Impact and Solution................................................................................................................................27
4.2 Scenario 2........................................................................................................................................................27
4.2.1 Symptom.................................................................................................................................................27
4.2.2 Impact and Solution................................................................................................................................27
4.3 Scenario 3........................................................................................................................................................31
4.3.1 Symptom.................................................................................................................................................31
4.3.2 Impact and Solution................................................................................................................................31
4.4 Scenario 4........................................................................................................................................................31
4.4.1 Symptom.................................................................................................................................................31
4.4.2 Impact and Solution................................................................................................................................31
5 References.................................................................................32
5.1 Case..................................................................................................................................................................32
5.2 FAQ..................................................................................................................................................................32
5.3 Protocol............................................................................................................................................................32
5.4 Acronyms and Abbreviations...........................................................................................................................32
2015-04-10
Page 4 of 32
INTERNAL
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.1 Teleservice
Teleservices include the speech transmission service, data service, and short message service.
Each service contains different sub-services, as shown in Figure 1.1.
Figure 1.1 Types of teleservice
Type
Sub-services
Data service
2015-04-10
Page 5 of 32
INTERNAL
Type
Sub-services
2015-04-10
Page 6 of 32
INTERNAL
Figure 1.1 Service groups and categories that the bearer services comprise
Bearer service
category
BS20
BS21
BS22
BS23
BS24
BS25
BS26
BS30
BS31
BS32
BS33
BS34
BS41
BS42
BS43
BS44
BS45
BS46
BS51
BS52
BS53
Alternate
speech/data service
BS61
Telephony data
service
BS81
PAD access CA
service
2015-04-10
Description
Page 7 of 32
INTERNAL
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.
2015-04-10
Page 8 of 32
INTERNAL
The HLR uses different indicators (default call) to identify MSISDN 2 and MSISDN 3. The
two numbers do not conflict with each other.
1.3.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.
2015-04-10
Page 9 of 32
INTERNAL
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.2Scenario 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 ISDNBC 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.
2015-04-10
Page 10 of 32
INTERNAL
The attributes describing the bearer services in the OSI reference model are as follows:
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
1.1, 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 1.1 GSM PLMN reference configuration
2015-04-10
Page 11 of 32
INTERNAL
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.
1.
2.
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.
2015-04-10
Page 12 of 32
INTERNAL
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 1.1 shows the multi-MSISDN PSTN to PLMN call flow
2015-04-10
Page 13 of 32
INTERNAL
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 1.3.
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
2015-04-10
Page 14 of 32
INTERNAL
singling information, the HLR sends the default PLMN-BC (GSM-BC) to the VLR based on
the PRN request message of the default call.
ISDN<->PLMN
For 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 1.4.
Figure 1.4 NetworkSingalinfo IE in the SRI message
2015-04-10
Page 15 of 32
INTERNAL
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.
2015-04-10
Page 16 of 32
INTERNAL
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.
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.
2015-04-10
Page 17 of 32
INTERNAL
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.
4.
5.
6.
7.
2015-04-10
Page 18 of 32
INTERNAL
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.
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;
2.
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;
3.
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;
4.
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.
2015-04-10
Page 19 of 32
INTERNAL
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:
1.
2.
The VLR supports the VVDN service. (You can check the carried extended IE to see
whether the VLR supports the VVDN service.)
3.
The MSISDN of the VVDN service supports the BS20 or BS30 service.
4.
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 multiMSISDN 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 singleMSISDN scheme.
The services supported by the HLR9820 include TS61 and TS62, BS20 to BS26, and BS30 to
BS34.
2015-04-10
Page 20 of 32
INTERNAL
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.
2015-04-10
Page 21 of 32
INTERNAL
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.
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, ITUT 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.
2015-04-10
Page 22 of 32
INTERNAL
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.
2015-04-10
Page 23 of 32
INTERNAL
2015-04-10
Page 24 of 32
INTERNAL
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;
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
ADD
MOD
MOD
NCCTPL:
NCCTPL:
NCCTPL:
NCCTPL:
HLRSN=1,
HLRSN=1,
HLRSN=1,
HLRSN=1,
TPLID=1,
TPLID=1,
TPLID=1,
TPLID=1,
ALS=NR;
ALS=SR;
ALS=NR;
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;
2015-04-10
Page 25 of 32
INTERNAL
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.
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.
2015-04-10
Page 26 of 32
INTERNAL
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.
4.2 Scenario 2
4.2.1 Symptom
A mobile subscriber who can properly make calls cannot receive faxes from fixed subscribers.
2015-04-10
Page 27 of 32
INTERNAL
2015-04-10
Page 28 of 32
INTERNAL
2015-04-10
Page 29 of 32
INTERNAL
Figure 1.3 SRI message generated when a fax machine sends a fax
2015-04-10
Page 30 of 32
INTERNAL
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.
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.
2015-04-10
Page 31 of 32
INTERNAL
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.
2015-04-10
Page 32 of 32