Major Parameters [DPC Index]

It is used to identify a remote DSP. This index must be the unique one identifying a remote DSP among all remote DSPs.

[NI]

For HLR, set this parameter to "NAT (National Network)".

[DPC]

It refers to destination signaling point code. Here set it to the DPC of the peer HLR. The DPC of the HLR is the national reserved 24-bit SPC. This parameter is the same as that set in the ADD N7DSP command.

[OPC]

It refers to the local office's SPC in the same network indicator. You can query it with the LST OFI command. For HLR, the OPC is the national network SPC of record No. 0 in the OFI table.

See Table 7-3 for the commands related to SCCP DSP configuration.

Table 7-3 List of commands related to SCCP DSP configuration

Command Description

ADD SCCPDSP To add an SCCP DSP

RMV SCCPDSP To remove an existing SCCP DSP MOD SCCPDSP To modify an existing SCCP DSP

LST SCCPDSP To list the information of all configured SCCP DSPs DSP SCCPDSP To display the information of all configured SCCP DSPs

7.4.3 Adding SCCP Subsystem

I. Background Information

This following command ADD SCCPSSN is used to add SCCP subsystems in MSOFTX3000 (local end) and the HLR (remote end). Subsystem number (SSN) is the local addressing information used by SCCP to identify the SCCP users under a SP.

Local MSC and VLR subsystems are already added in the local office information.

z The network indicator of MSOFTX3000 is "National Network", and the configured SSN is SCCP management subsystem (SCMG).

z The SSN to be configured at the HLR side includes SCMG and HLR.

Since the local MSC, VLR, and SCMG subsystems have been configured in the local office information, execute the LST SCCPSSN command to have a check to avoid repeated configuration. For any entity (local end or remote end), it may be required to run this command repeatedly to configure multiple SCCP subsystems.

II. Command ADD SCCPSSN III. Major Parameters

[SSN Index]

It is used to identify the SCCP subsystem, and it is unique in the system.

[NI]

It is used to set the indicator of the network to which the SCCP subsystem belongs. The devices to be interconnected should be in the same signaling network. For the subsystem interworking with HLR, set it to "National Network".

[SSN]

[SPC]

It is used to specify the destination SPC of the corresponding subsystem, that is, the recipient of SCCP messages. You need to set HLR SPC and OPC here. The HLR SPC must be correlated with that defined in the command ADD SCCPDSP.

[OPC]

Enter the national reserved network SPC of the local office. It is associated with the parameter “OPC” in the SET OFI command.

[Local Concerned SSN1]–[Local Concerned SSN5]

It is used to define the index of a subsystem which is related to a specified subsystem and has the same DPC as the subsystem. You can define a maximum of 5 indexes. If there is no related subsystem, use the default option “Undefined”.

[Backup SSN Index]

It is used to specify the index of the backup subsystem of a specified subsystem. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. If there is no subsystem, use the default value “65535”.

IV. Related Commands

See Table 7-4 for the commands related to SCCP subsystem configuration.

Table 7-4 List of commands related to SCCP subsystem configuration

Command Description

ADD SCCPSSN To add an SCCP subsystem

RMV SCCPSSN To remove an existing SCCP subsystem MOD SCCPSSN To modify an existing SCCP subsystem LST SCCPSSN To list SCCP subsystems

SET SCCPSSN To set SCCP subsystem status. This command is used during maintenance.

DSP SCCPSSN To display SCCP subsystems in the host

7.4.4 Adding SCCP GT

I. Background Information

When MSOFTX3000 is directly connected to HLR, it is required to configure the following global title (GT) data for the three cases:

z IMSI GT and HLR-NUMBER GT for location update.

z Ordinary GT (HLR-MSISDN GT) when the subscriber is called.

z Local MSC GT to be queried when the local office performs second-stage number

The following gives detailed description:

5) IMSI GT and HLR-NUMBER GT for location update

z IMSI GT configuration: It is performed for location update to find the corresponding HLR according to the GT translation code of the HLR obtained through the IMSI number.

When a mobile station initiates location update request, it sends the IMSI number.

Because IMSI number cannot build GT, it is required to use the ADD IMSIGT command to translate GT. For example, use the command ADD IMSIGT: MCCMNC="46000", CCNDC="86139" to translate 46000×××××××× into 86139××××××××. (note:

86139×××××××× is not a phone number).

Then use the following command (supposing that the SP of the HLR is 12345):

ADD SCCPGT: GTX=1, GTNAME="IMSI-GT", NI=NAT, NUMPLAN=ISDNMOV, ADDR=K'86139××××××××, RESULTT=STP1, SPC="12345";

Where, the length of the parameter “ADDR” can be set according to the actual condition, and the parameter “NUMPLAN” must be mobile numbering plan “ISDNMOV”.

z HLR-NUMBER GT configuration: It is performed for location update when VLR inserts subscriber information response to HLR to find corresponding HLR.

According to the analysis in 1), MSC/VLR can find HLR. However, the location update has not yet completed after those two commands are executed, because VLR needs to insert subscriber response PRN-ACK to HLR. In the last step, VLR obtains the HLR destination address through analyzing HLR number, which is carried in the called number on SCCP layer when HLR inserts subscriber data message. Supposing the HLR number is 8613907551234, it is required to execute the following command:

ADD SCCPGT: GTX=2, GTNAME="HLR-GT", ADDR=K'8613907551234, RESULTT=STP1, SPC="12345";

The numbering plan here is the telephone numbering plan.

After the above IMSI GT and HLR-NUMBER GT configurations, the GT configuration related to location update has been completed.

1) HLR-MSIDSN GT configuration: It is performed for the routing information fetching process to find the corresponding HLR according to the GT translation code of the HLR obtained through the MSISDN of the called number.

When a subscriber is called, MSC needs to get his/her roaming number in the HLR and gets the HLR SPC through analyzing the MSISDN of the called number.

Assuming that IMSI 46000×××××××× in the HLR is assigned with MSISDN 861390755×××××, it is required to execute the following command:

ADD SCCPGT: GTX=3, GTNAME="HLR NUMBER", ADDR=K'861390755, RESULTT=STP1, SPC="12345";

After getting the roaming number, the HLR sends SRI-RSP message with MSC GT address information to MSC, which checks whether it is the local MSC GT. If yes, MSC will initiate paging.

The GT translation code of the local MSC has been described in local office information configuration, so it is not necessary to configure it here.

II. Command