SPS V300R007C10 Part II Operation Guide (Special)

SPS V300R007C10 Operation Guide
Table of Contents
Part II Operation Guide...............................................................................................................1

T14 Topology Hiding................................................................................................................. 1
T14-01 Deleting the Route-Record Field...........................................................................1
T14-02 Deleting the Route-Record Field and Replacing the Host Name and Realm Name
.......................................................................................................................................... 2
T15 Session Binding................................................................................................................. 2
T15-01 PCRF Session Binding Setup...............................................................................2
T15-02 PCRF Session Binding Removal...........................................................................4
T16 Signaling Adaptation.......................................................................................................... 5
T16-01 Signaling Adaptation Based on the Combination of an Application ID, Source
Realm Name, Source Host Name, Destination Realm Name, and Destination Host Name
.......................................................................................................................................... 5
T16-02 Signaling Adaptation Based on the Combination of an Application ID, Source
Realm Name, Source Host Name, Destination Realm Name, Destination Host Name,
Message Type, and Command Code................................................................................7
T17 IPv6.................................................................................................................................... 8
T17-01 Support for IPv6 on TCP Links..............................................................................8
T17-02 Support for IPv6 on STCP Links............................................................................9
T18 SS7 Signaling Management............................................................................................... 9
T18-01 MTP....................................................................................................................... 9
T18-02 SCCP.................................................................................................................. 11
T19 Message Rerouting.......................................................................................................... 11
T19-01 SS7 Message Rerouting.....................................................................................11
T20 NP Function..................................................................................................................... 14
T20-01 IN NP Query for Call-related Service...................................................................14
T20-02 MAP NP Query for Call-related Service..............................................................17
T20-03 IN NP Query for SMS..........................................................................................20
T20-04 NP Subscriber MO-SMS Authentication..............................................................23
T20-05 MAP NP Query for SMS......................................................................................26
T20-06 FNR Function...................................................................................................... 29
T20-07 ATI NP Query...................................................................................................... 30
T20-08 ISUP NP Query................................................................................................... 31
T20-09 NP Routing Loop Prevention...............................................................................32
T21 Address Resolution.......................................................................................................... 33
T21-01 Locating IMS-HSS Based on IMPU.....................................................................33
T21-02 Locating SAE-HSS Based on IMSI......................................................................34
T21-03 Locating PCRF Based on MSISDN.....................................................................35
T21-04 Locating PCRF Based on IMSI............................................................................37
T21-05 Locating Accounting Server Based on MSISDN..................................................38
T21-06 Locating Accounting Server Based on IMSI........................................................39
T21-07 Locating Accounting Server Based on IMPU......................................................40
T22 Virtualized Diameter Routing Agent.................................................................................42
T22-01 Alarm Reporting for Multiple SPSs Sharing One OMU........................................42
T22-02 Performance Management of Multiple SPSs Sharing One OMU........................42
T22-03 Unified M2000 Access of Multiple SPSs Sharing One OMU...............................43
T23 Message Tracing............................................................................................................. 44
T23-01 SS7 User Message Tracing................................................................................44
T24 SS7 Signaling Screening................................................................................................. 45
T24-01 FW Screening...................................................................................................... 45
T25 Message Duplication........................................................................................................ 49
T25-01 Application ID-based Message Duplication.........................................................49
T26 MAP-Diamter Translation.................................................................................................54
T26-01 S6a/Gr Interface Conversion...............................................................................54
SPS V300R007C10 Operation Guide Internal Public
Part II Operation Guide

T14 Topology Hiding
T13-01 Deleting the Route-Record Field
T13-0101 Deleting the Route-Record Field
Objective Verify that the signaling service processing system (SPS) can delete the Route-
Record field carried in a Diameter message to screen certain network
configurations and topology structures from devices on other carrier's networks.
Network Diagram See Figure 1 in Part III Appendix.
Prerequisites  All the link sets and links in Figure 1 are configured and the status of the
links is normal. Peer device 1 has been configured by running ADD
DMPEER on SPS_A with Topology hiding flag set to Yes(YES).
 Messages from Peer device 1 are routed to Peer device 2 through SPS_A.
 The license for the topology hiding function has been activated.
Procedure Expected Results
1. Run ADD RTRESULT on SPS_A to add a 1. The Diameter route result is added.
Diameter route result with Route result name 2. The route is added.
set to rt, and Relay device 1 set to Peer device
2. 6. Topology hiding information is added.
2. Run ADD DMRT on SPS_A to add a route 7. The topology hiding function is enabled.
between SPS_A and Peer device 2 with Realm 8. The message sent from Peer device 1 can
name set to the domain name of Peer device 2, be routed to Peer device 2 through
Local action set to RELAY(RELAY), and SPS_A, and Peer device 1 can receive a
Route result name set to rt. response from Peer device 2. The Route-
3. Run ADD TOPOINFO on SPS_A with Host Record field carried in the message is
name and Realm name set to the host name deleted.
and domain name of Peer device 1, and
Topology hiding type set to
HIDEMODE1(Hide routing information).
4. Run MOD SFP on SPS_A with Parameter
name set to P43, Modification option set to
P0, and Value set to 1.
5. Use Peer device 1 to send a Diameter
message to SPS_A. In the message, the
destination domain name is the domain name
of Peer device 2 and the destination host name
is not carried. Create tracing tasks and trace
the Diameter messages.
Remarks None.
Internal Number T14-0101
All rights reserved Page 1 , Total 61

T13-02 Deleting the Route-Record Field and Replacing the Host Name and
Realm Name
T13-0201 Deleting the Route-Record Field and Replacing the Host Name and Realm
Name
Objective Verify that the SPS can delete the Route-Record field and replace the host name
and realm name carried in a Diameter message to screen certain network
configurations and topology structures from devices on other carrier's networks.
Prerequisites  All the link sets and links in Figure 1 are configured and the status of the
links is normal. Peer device 1 has been configured by running ADD
DMPEER on SPS_A, with Topology hiding flag set to Yes(YES).
 Messages from Peer device 1 are routed to Peer device 2 through SPS_A.
 The license for the topology hiding function has been activated.
Procedure Expected Results
1. Run ADD RTRESULT on SPS_A to add a 1. The Diameter route result is added.
Diameter route result with Route result name 2. The route is added.
set to rt, and Relay device 1 set to Peer device
2. 3. Topology hiding information is added.
2. Run ADD DMRT on SPS_A to add a route 4. The topology hiding function is enabled.
between SPS_A and Peer device 2 with Realm 5. The messages sent from Peer device 1
name set to the domain name of Peer device 2, can be routed to Peer device 2 through
Local action set to RELAY(RELAY), and SPS_A. The Route-Record field carried in
Route result name set to rt. the message is deleted and the origin host
3. Run ADD TOPOINFO on SPS_A with Host and origin realm carried in the message
name and Realm name set to the host name are replaced by a new host name and
and domain name of Peer device 1, and realm name. Peer device 1 can receive a
Topology hiding type set to response from Peer device 2.
HIDEMODE2(Hide routing information and
replace Host and Realm).
4. Run MOD SFP on SPS_A with Parameter
name set to P43, Modification option set to
P0, and Value set to 1.
5. Use Peer device 1 to send a Diameter
message to SPS_A. In the message, the
destination domain name is the domain name
of Peer device 2 and the destination host name
is not carried. Create tracing tasks and trace
the Diameter messages.
Remarks None.
T14 Session Binding

T14-01 PCRF Session Binding Setup
T14-0101 Setting Up Session Binding
Objective Verify that the SPS can address the messages transmitted for the same subscriber

or session from different NEs to the same peer.
Prerequisites  All link sets and links shown in Figure 2 have been configured and are
connected properly.
 The local USCDB databases of SPS_A and SPS_B are running properly.
 Peer device 1 has been configured by running ADD DMPEER on SPS_A,
with Binding flag set to YES(YES) and Binding rule name set to the
default rule of SPS_A.
 The license that supports session binding has been activated on SPS_A. In
addition, P69 has been set to 0 and P54 has been set to 1 on SPS_A.
 Run ADD RTRESULT on SPS_A to add a Diameter route result with Route
result name set to rt, Relay device selection mode set to
MASTER_SLAVE(MASTER SLAVE), Relay device 1 set to the peer name
of Peer device 3, and Relay device 2 set to the peer name of Peer device 4.
 Run ADD DMRT on SPS_A to add a route between SPS_A and Peer device
3 with Realm name set to the domain name of Peer device 3, Application
identifier set to Gx(PCEF-PCRF), Local action set to RELAY(RELAY),
and Route result name set to rt.
 Peer device 2 has been configured by running ADD DMPEER on SPS_B,
default rule of SPS_B.
 The license that supports session binding has been activated on SPS_B. In
addition, P69 has been set to 0 and P54 has been set to 1 on SPS_B.
 Run ADD RTRESULT on SPS_B to add a Diameter route result with Route
result name set to rt2, Relay device selection mode set to
of Peer device 4.
 Run ADD DMRT on SPS_B to add a route between SPS_B and Peer device
and Route result name set to rt2.
Procedure Expected Result
1. Use Peer device 1 to send a CCR-I message to 1. SPS_A forwards the CCR-I message to
SPS_A. The message carries the destination Peer device 3 and receives a CCA-I
realm name (realm name of Peer device 3) and message from Peer device 3. SPS_A then
IPv4 address, but does not carry destination forwards the CCA-I message to Peer
host name. Create tracing tasks and trace device 1.
Diameter messages received and sent by 6. SPS_B forwards the message to Peer
SPS_A. device 3 and receives an AAA message
2. Use Peer device 2 to send an AAR message to from Peer device 3. SPS_B then forwards
SPS_B. The message carries the destination the AAA message to Peer device 2.
realm name (realm name of Peer device 4) and 7. Session binding is disabled.
the same IP adderss as theCCR-I message in
step 1, but does not carry the destination host 8. SPS_A forwards the message to Peer
name. Create tracing tasks and trace Diameter device 3 and receives a CCA-I message
messages received and sent by SPS_B. from Peer device 3. SPS_A then forwards
the CCA-I message to Peer device 1.
3. Disable the function of P54 on SPS_A.
9. SPS_B forwards the message to Peer
4. Use Peer device 1 to send a CCR-I message to device 4 and receives an AAA message
SPS_A. The message carries the destination from Peer device 4. SPS_B then forwards
realm name (realm name of Peer device 3) and the AAA message to Peer device 2.
IPv4 address, but does not carry destination
host name. Create tracing tasks and trace
Diameter messages received and sent by
SPS_A.

5. Use Peer device 2 to send an AAR message to

SPS_B. The message carries the destination
realm name (realm name of Peer device 4) and
step 4, but does not carry the destination host
name. Create tracing tasks and trace Diameter
messages received and sent by SPS_B.
Remarks None
T14-02 PCRF Session Binding Removal
T14-0201 Removing Session Binding
Objective Verify that the SPS allows session binding to be removed.
connected properly.
 The local USCDB databases of SPS_A and SPS_B are running properly.
 Peer device 1 has been configured by running ADD DMPEER on SPS_A,
default rule of SPS_A.
 The license that supports session binding has been activated on SPS_A. In
addition, P69 has been set to 0 and P54 has been set to 1 on SPS_A.
 Run ADD RTRESULT on SPS_A to add a Diameter route result with Route
result name set to rt, Relay device selection mode set to
of Peer device 3, and Relay device 2 set to the peer name of Peer device 4.
 Run ADD DMRT on SPS_A to add a route between SPS_A and Peer device
and Route result name set to rt.
 Peer device 2 has been configured by running ADD DMPEER on SPS_B,
default rule of SPS_B.
 The license that supports session binding has been activated on SPS_B. In
addition, P69 has been set to 0 and P54 has been set to 1 on SPS_B.
 Run ADD RTRESULT on SPS_B to add a Diameter route result with Route
result name set to rt2, Relay device selection mode set to
of Peer device 4.
 Run ADD DMRT on SPS_B to add a route between SPS_B and Peer device
and Route result name set to rt2.
1. Use Peer device 1 to send a CCR-I message to 1. SPS_A forwards the message to Peer
SPS_A. The message carries the destination device 3 and receives a CCA-I message
realm name (realm name of Peer device 3) and from Peer device 3. SPS_A then forwards
IPv4 address, but does not carry destination the CCA-I message to Peer device 1.
host name. Create tracing tasks and trace

Diameter messages received and sent by 6. SPS_B forwards the message to Peer
SPS_A. device 3 and receives an AAA message
2. Use Peer device 2 to send an AAR message to from Peer device 3. SPS_B then forwards
SPS_B. The message carries the destination the AAA message to Peer device 2.
realm name (realm name of Peer device 4) and 7. SPS_A forwards the message to Peer
the same IP adderss as theCCR-I message in device 3 and receives a CCA_T message
step 1, but does not carry the destination host from Peer device 3. SPS_A then forwards
name. Create tracing tasks and trace Diameter the CCA_T message to Peer device 1.
messages received and sent by SPS_B. 8. The binding information about IMSI 1 is not
3. Use Peer device 1 to send a CCR-T message displayed.
to SPS_A. The message carries the destination 9. SPS_B forwards the message to Peer
host name of Peer device 3 and the same IP device 4 and receives an AAA message
adderss as theCCR-I message in step 1. from Peer device 4. SPS_B then forwards
Create tracing tasks and trace Diameter the AAA message to Peer device 2.
messages received and sent by SPS_A.
4. Run LST BINDINFO on the weblmt client of
SPS_A to check whether the binding
information about IMSI 1 is displayed.
5. Use Peer device 2 to send an AAR message to
SPS_B. The message carries the destination
realm name (realm name of Peer device 4) and
step 1, but does not carry the destination host
name. Create tracing tasks and trace Diameter
messages received and sent by SPS_B.
Remarks None
T15 Signaling Adaptation

T15-01 Signaling Adaptation Based on the Combination of an Application
ID, Source Realm Name, Source Host Name, Destination Realm Name, and
Destination Host Name
T15-0101 Adapting Signaling Based on the Combination of an Application ID, Source

Realm Name, Source Host Name, Destination Realm Name, and Destination Host Name
Objective Verify that the SPS can adapt signaling based on the combination of an application
ID, origin realm name, origin host name, destination realm name, and destination
host name.
connected properly.
 The license that supports Diameter signaling adaptation has been activated
for SPS_A. Diameter Mediation control parameter has been set to 1 for
SPS_A.
1. Run ADD MEDACTION on SPS_A, with the 1. The mediation action is added.
parameters specified as follows: 1. The mediation rule is added.

 Set Mediation action name to A. 2. The modification is successful.

 Set Mediation action to ADD_AVP(Add AVP). 3. SPS_A forwards the message to Peer
 Set Layer 1 AVP code to 65535. device 3 and forwards the response from
Peer device 3 to Peer device 1. In the ULR
 Set Layer 1 AVP type to STR(String). message forwarded by SPS_A, AVP
 Set Location for adding AVP to 65535. CODE 493 is added at the end of layer-1
AVPs.
 Set Layer 1 subAVP code to 493.
4. SPS_A forwards the message to Peer
 Set Layer 1 subAVP type to STR(String). device 3 and forwards the response from
 Set New AVP value to cmnet.cmri.com. Peer device 3 to Peer device 2. No AVP is
 Set Filter condition to NO(No). added to the ULR message forwarded by
SPS_A.
2. Run ADD MEDRULE on SPS_A, with the
parameters specified as follows:
 Set Mediation action name to RuleB.
 Set Mediation set to B.
 Set Application ID to
S6a/S6d(MME-HSS/SGSN-HSS).
 Set Original realm to the realm name of Peer
device 1.
 Set Original host to the host name of Peer
device 1.
 Set Destination realm to the realm name of
Peer device 3.
 Set Destination host to the host name of Peer
device 3.
 Set Mediation action name 1 to A.
3. Run MOD DMPEER on SPS_A to change
Send message mediation set to B for Peer
device 3.
4. Use Peer device 1 to send a ULR message to
SPS_A. In the message:
 The origin realm name is the realm name of
Peer device 1.
 The origin host name is the host name of Peer
device 1.
 The destination realm name is the realm name
of Peer device 3.
 The destination host name is the host name of
Peer device 3.
Create tracing tasks and trace Diameter
messages.
Peer device 2.
device 2.
of Peer device 3.
Peer device 3.
Create tracing tasks and trace Diameter
messages.

Remarks None
T15-02 Signaling Adaptation Based on the Combination of an Application

ID, Source Realm Name, Source Host Name, Destination Realm Name,
Destination Host Name, Message Type, and Command Code
T15-0201 Adapting Signaling Based on the Combination of an Application ID, Source

Realm Name, Source Host Name, Destination Realm Name, Destination Host Name,
Message Type, and Command Code
Objective Verify that the SPS can adapt signaling based on the combination of an application
ID, origin realm name, origin host name, destination realm name, destination host
name, message type, and command code.
connected properly.
 The license that supports Diameter signaling adaptation has been activated
for SPS_A. Diameter Mediation control parameter has been set to 1 for
SPS_A.
1. Run ADD MEDACTION on SPS_A, with the 1. Execution of ADD MEDACTION is

parameters specified as follows: successful.
 Set Mediation action name to A. 2. Execution of ADD MEDRULE is
 Set Mediation action to ADD_AVP(Add AVP). successful.
 Set Layer 1 AVP code to 65535. 3. Execution of MOD DMPEER is successful.
 Set Layer 1 AVP type to STR(String). 4. SPS_A forwards the message to Peer
device 3 and forwards the response from
 Set Location for adding AVP to 65535. Peer device 3 to Peer device 1. In the ULA
 Set Layer 1 subAVP code to 493. message forwarded by SPS_A, AVP
CODE 493 is added at the end of layer-1
 Set Layer 1 subAVP type to STR(String). AVPs.
 Set New AVP value to cmnet.cmri.com. 5. SPS_A forwards the message to Peer
 Set Filter condition to NO(No). device 3 and forwards the response from
2. Run ADD MEDRULE on SPS_A, with the Peer device 3 to Peer device 2. No AVP is
parameters specified as follows: added to the ULA message forwarded by
SPS_A.
 Set Mediation action name to RuleB.
 Set Mediation set to B.
 Set Application ID to
S6a/S6d(MME-HSS/SGSN-HSS).
 Set Original realm to the realm name of Peer
device 3.
 Set Original host to the host name of Peer
device 3.
 Set Destination realm to the realm name of
Peer device 1.
 Set Destination host to the host name of Peer
device 1.

 Set Command code to 316.

 Set Message type to RSP(Response).
 Set Mediation action name 1 to A.
3. Run MOD DMPEER on SPS_A to change
Receive message mediation set to B for Peer
device 3.
Peer device 1.
device 1.
of Peer device 3.
Peer device 3. Create tracing tasks and trace
Diameter messages.
Peer device 2.
device 2.
of Peer device 3.
Peer device 3. Create tracing tasks and trace
Diameter messages.
Remarks None
T16 IPv6
T16-01 Support for IPv6 on TCP Links
T16-0101 Supporting IPv6 on TCP Links
Objective Verify that the SPS supports IPv6 on TCP links.
Prerequisites  The DA IP address has been set to an IPv6 address on SPS_A.

 Link sets to Peer device 1 and Peer device 3 have been configured on
SPS_A but links have not been configured.
 The license that supports IPv4/IPv6 Dual Stack Control has been activated
for SPS_A. IPv4/IPv6 Dual Stack Control parameter has been set to 1 for
SPS_A.
1. Run ADD DMLNK on SPS_A to configure the 1. The Diameter links are added.

links to Peer device 1 and Peer device 3, with 3. SPS_A forwards the ULR message to Peer
Transmission protocol type and IP type set device 3 and a response message to Peer
to TCP(TCP) and IPV6(IPv6) respectively. device 1.
SPS_A, with the destination address carried in
the message being Peer device 3. Create
tracing tasks and trace Diameter messages.
Remarks None
T16-02 Support for IPv6 on STCP Links
T16-0201 Support for IPv6 on STCP Links
Objective Verify that the SPS supports IPv6 on STCP links.
Prerequisites  The DA IP address has been set to an IPv6 address on SPS_A.

 Link sets to Peer device 1 and Peer device 3 have been configured on
SPS_A but links have not been configured.
 The license that supports IPv4/IPv6 Dual Stack Control has been activated
for SPS_A. IPv4/IPv6 Dual Stack Control parameter has been set to 1 for
SPS_A.
1. Run ADD DMLNK on SPS_A to configure the 1. Execution of ADD DMLNK is successful.
links to Peer device 1 and Peer device 3, with 3. SPS_A forwards the ULR message to Peer
Transmission protocol type and IP type set device 3 and a response message to Peer
to SCTP(SCTP) and IPV6(IPv6) respectively. device 1.
2. Send a ULR message from Peer device 1 to
SPS_A, with the destination address carried in
the message being Peer device 3. Create
tracing tasks and trace Diameter messages.
Remarks None
T17 SS7 Signaling Management

T17-01 MTP
T17-0101 Inhibiting/Uninhibiting MTP Links
Objective Verify that MTP links can be inhibited or uninhibited by running a related
command.
Prerequisites  SPS_A is running properly.

 The communication between the host and the BAM is normal.

 At least two MTP links have been established and are normal.

1. Run INH N7LNK on SPS_A with Link name 1. The commands are successfully executed.
set to the normal MTP link to be inhibited, and In the command output, Transmission
run DSP N7LNK to query the status of the MTP service is set to No and Local
link. management disabled is set to Yes.
2. Run UIH N7LNK on SPS_A with Link name 2. The commands are successfully executed.
set to the inhibited MTP link, and run DSP In the command output, the queried MTP
N7LNK to query the status of the MTP link. link is normal.
Remarks In actual applications, do not inhibit MTP links when devices are running properly.
T17-0102 Deactivating/Activating MTP Link Sets
Objective Verify that MTP link sets can be deactivated or activated by running a related
command.

 MTP links have been established and are normal.
1. Run DEA N7LKS on SPS_A with Linkset 1. The commands are successfully executed.
name set to the normal MTP link set to be In the command output, Failure state of
deactivated, and run DSP N7LKS to query the the queried MTP link set is set to Yes.
status of the MTP link set. 3. The commands are successfully executed.
2. Run ACT N7LKS on SPS_A with Linkset In the command output, the queried MTP
name set to the deactivated MTP link set, and link set is normal.
run DSP N7LKS to query the status of the MTP
link set.
Remarks In actual applications, do not deactivate MTP link sets when devices are running
properly.
T17-0103 Setting MTP Routes as Offline/Online
Objective Verify that MTP routes can be set to be offline or online by running a related
command.

 MTP links have been established and are normal.

1. Run OFL N7RT on SPS_A with Route name 1. The commands are successfully executed.
set to the MTP route to be offline, and run DSP In the command output, Offline status of
N7RT to query the status of the MTP route. the queried MTP link is set to Yes.
2. Run ONL N7RT on SPS_A with Route name 2. The commands are successfully executed.
set to the MTP route in offline state, and run SP In the command output, Offline status of
N7RT to query the status of the MTP route. the queried MTP link is set to No.
Remarks In actual application, do not set MTP routes as offline when devices are running
properly.
T17-02 SCCP
T17-0201 Setting the SCCP as Busy/Offline
Objective Verify that the SCCP can be set as busy or offline by running a related command.

 The SCCP function has been enabled.
 The SCCP data has been correctly configured.
1. Run OFL SCCPDPC on SPS_A with Signaling 1. The commands are successfully executed.
point code set to the DSP to be offline, and run In the command output, SCCP offline of
DSP SCCPRDSP to query the status of the the DSP is set to Yes.
DSP. 3. The commands are successfully executed.
2. Run RST SCCPDPC on SPS_A with Signaling In the command output, SCCP offline of
point code set to the offline DSP, and run DSP the DSP is set to No.
SCCPRDSP to query the status of the DSP.
Remarks  This function applies only to the SS7 and does not apply to the SIGTRAN.
 If a DSP is in offline state, the SCCP module does not send messages to the
DSP.
T18 Message Rerouting

T18-01 SS7 Message Rerouting
T18-0101 Rerouting Messages Based on the OPC
Objective Verify that the SPS can reroute messages based on the originating point code
(OPC).
Prerequisites  Communication between NEs is normal.

 M3UA links have been configured between the SPS and NEs, and the status
of the links is normal.
1. Run MOD M3LKS to configure the M3LKS data 1. The M3LKS data is successfully
with Service process switchset to configured.
ROSWT(Reroute switch), Reroute policy set 6. The reroute processing rule data is
to AP(All DPC processed), Reroute type set successfully configured.
to RO(Reroute OPC), and Reroute reference
set to 1. 7. The reroute OPC data is successfully
configured.
2. Run ADD RRRULE to configure the reroute
processing rule data with DSP0 name set to 8. The M3UA message tracing task is
HLR2 and Priority0 set to 0. successfully created.
3. Run ADD RROPC to configure the reroute 9. The SPS receives a UDT message and
OPC data with Reroute reference set to 1, sends the message to HLR 2.
Type of next reroute set to RRL(Reroute
rule), Reroute rule name set to that configured
by running ADD RRRULE in step 2, and
Maximum OPC and Minimum OPC set to
those on the MSC server.
4. Create an M3UA message tracing task.
5. Simulate a scenario where the MSC server
sends the SPS a UDT message carrying the
DPC of HLR 1.
Remarks None.
T18-0102 Rerouting Messages Based on the DPC
Objective Verify that the SPS can reroute messages based on the DPC.

with Service process switch set to configured.
to RD(Reroute DPC), and Reroute reference
set to 2. 7. The reroute DPC data is successfully
configured.
3. Run ADD RRDPC to configure the reroute DPC 9. The SPS receives a UDT message and
data with Reroute reference set to 2, Type of sends the message to HLR 2.
next reroute set to RRL(Reroute rule),
Reroute rule name set to that configured by
running ADD RRRULE in step 2, and
Maximum DPC and Minimum DPC to those
on the MSC server.


DPC of HLR 1.
Remarks None.
T18-0103 Rerouting Messages Based on the Called GT
Objective Verify that the SPS can reroute messages based on the called GT.

to RDGT(Reroute called GT), and Reroute
reference set to 6. 7. The reroute called GT data is successfully
configured.
3. Run ADD RRCDGT with Reroute reference 9. The SPS receives a UDT message and
set to 6, Type of next reroute set to sends the message to HLR 2.
RRL(Reroute rule), Reroute rule name to that
configured by running ADD RRRULE in step 2,
and configure the called GT information.
called GT information configured in step 3.
Remarks None.
T18-0104 Rerouting Messages Based on the Calling GT
Objective Verify that the SPS can reroute messages based on the calling GT.


to RGGT(Reroute calling GT), and Reroute
reference set to 7. 7. The reroute calling GT data is successfully
configured.
3. Run ADD RROPC with Reroute reference set 9. The SPS receives a UDT message and
to 7, Type of next reroute set to RRL(Reroute sends the message to HLR 2.
rule), Reroute rule name to that configured by
running ADD RRRULE in step 2, and configure
the calling GT information.
calling GT information configured in step 3.
Remarks None.
T19 NP Function
T19-01 IN NP Query for Call-related Service
T19-0101 Calling Ported-in Subscribers
Objective Verify that the SPS can perform IN query for ported-in subscribers when these
subscribers are called.
Prerequisites  All the link sets and links in Figure 2 have been configured and the status of
all the links is normal.
 You have logged in to the OMU client.
1. Run MOD SFP with Parameter name set to 1. The NP function is enabled.
P207, Modification option set to P0(By 9. The MNP software parameter table is
value), and Value set to 1 to enable the successfully configured.
number portability (NP) function.
10. The RN tables and HLR address tables are
2. Run SET MNPSOFTCFG to configure the MNP successfully configured.
software parameter table with MNP mode set
11. The user attribute table is successfully
to MNPFN, Message type of MNP service
configured.
processing set to CAP, and Multi RN switch
set to Open. 12. The GT data is successfully configured.
3. Run ADD SEMNPROUTENUM and ADD 13. The SS7 signaling message tracing task is
SEMNPHLRADDR to configure the same route created.
number (RN) table and HLR address table for 14. The SPS obtains the called number from
the SPS and PGW, separately. the CAP IDP message, queries the NPDB
4. On the PGW Web LMT, run ADD SERUATTR for the referenced RN, prefixes the called
to configure the user attribute table with number with the RN, and sends the

Number type set to TYPE2(Moved in from message to the SCP.

external network), Route index type set to 15. The CAP IDP and query messages of the
ALL, and HLR address index and Routing SPS are traced, and the messages are
number index set to those configured in step correctly resolved.
3.
5. Run ADD SCCPGT to configure the GT data.
6. Create an SS7 signaling message tracing task.
7. Simulate a scenario where the VMSC sends
the SPS a CAP IDP message in which the
called number is the ported-in subscriber's
number configured in step 4.
8. Check the traced messages in the tracing task
window.
Remarks None.
T19-0102 Calling Ported-out Subscribers
Objective Verify that the SPS can perform IN query for ported-out subscribers when these
1. Run MOD SFP with Parameter name set to P207, 1. The NP function is enabled.
Modification option set to P0(By value), and Value 9. The MNP software parameter table
set to 1 to enable the NP function. is successfully configured.
2. Run SET MNPSOFTCFG to configure the MNP 10. The RN tables are successfully
software parameter table with MNP mode set to configured.
MNPFN and Message type of MNP service
processing set to CAP. 11. The user attribute table is
successfully configured.
3. Run ADD SEMNPROUTENUM to configure the same
RN table for the SPS and PGW, separately. 12. The GT data is successfully
configured.
4. Run ADD SERUATTR to configure the user attribute
table with Number type set to TYPE1(Moved out 13. The SS7 signaling message tracing
of local network), Route index type set to RN, task is created.
and NP route index set to that configured in step 3. 14. The SPS obtains the called number
5. Run ADD SCCPGT to configure the GT data. from the CAP IDP message,
queries the NPDB for the
6. Create an SS7 signaling message tracing task. subscriber's home network RN,
7. Simulate a scenario where the VMSC sends the SPS prefixes the called number with the
a CAP IDP message in which the called number is the RN, and sends the message to the
ported-out subscriber's number configured in step 4. SCP.
8. Check the traced messages in the tracing task 15. The CAP IDP and query messages
window. of the SPS are traced, and the
messages are correctly resolved.
Remarks None.

T19-0103 Calling Foreign Non-NP Subscribers
Objective Verify that the SPS can perform IN query for foreign non-NP subscribers when
these subscribers are called.
value), and Value set to 1 to enable the NP successfully configured.
function.
3. The RN tables are successfully configured.
2. Run SET MNPSOFTCFG to configure the MNP
software parameter table with MNP mode set 4. The foreign network number range table is
to MNPFN and Message type of MNP service successfully configured.
processing set to CAP. 5. The GT data is successfully configured.
3. Run ADD SEMNPROUTENUM to configure the 6. The SS7 signaling message tracing task is
same RN table for the SPS and PGW, created.
separately.
7. The SPS obtains the called number from
4. Run ADD MNPFRGNRNG to configure the the CAP IDP message, detects that the
foreign network number range table with subscriber is a non-NP subscriber from a
Routing number index set to that configured foreign network by querying the NPDB,
in step 3. and sends the message to the SCP.
5. Run ADD SCCPGT to configure the GT data. 8. The CAP IDP and query messages of the
6. Create an SS7 signaling message tracing task. SPS are traced, and the messages are
correctly resolved.
called number is within the foreign network
number range configured in step 4.
window.
Remarks None.
T19-0104 Calling Local Non-NP Subscribers
Objective Verify that the SPS can perform IN query for local non-NP subscribers when these


function. 10. The RN tables and HLR address tables are
software parameter table with MNP mode set 11. The local network number range table is
processing set to CAP.
12. The GT data is successfully configured.
3. Run ADD SEMNPROUTENUM and ADD
SEMNPHLRADDR to configure the same RN 13. The SS7 signaling message tracing task is
table and HLR address table for the SPS and created.
PGW, separately. 14. The SPS obtains the called number from
4. Run ADD MNPLOCNRNG to configure the the CAP IDP message, detects that the
local network number range with HLR address subscriber is a non-NP subscriber on the
index and Routing number index set to those local network by querying the NPDB, and
configured in step 4. sends the message to the SCP.
5. Run ADD SCCPGT to configure the GT data. 15. The CAP IDP and query messages of the
SPS are traced, and the messages are
6. Create an SS7 signaling message tracing task. correctly resolved.
called number is within the local number range
configured in step 4.
window.
Remarks None.
T19-02 MAP NP Query for Call-related Service
T19-0201 Calling Ported-in Subscribers
Objective Verify that the SPS can perform MAP query for ported-in subscribers when these
function.
3. The HLR address tables are successfully
2. Run SET MNPSOFTCFG to configure the MNP configured.
to MNPFN and Message type of MNP service
configured.
processing set to MAP.
3. Run ADD SEMNPHLRADDR to configure the
same HLR address table for the SPS and 6. The SPS obtains the subscriber's number
PGW, separately. from the called GT in the SRI message and
detects that the subscriber is a ported-in
4. Run ADD SERUATTR to configure the user
subscriber by querying the NPDB. Then,
attribute table with Number type set to the SPS obtains the subscriber's HLR GT,

TYPE2(Moved in from external network), replaces the called GT with the HLR GT,
Route index type set to ALL, and HLR and sends the message to the local HLR.
address index and Routing number index 7. The SS7 signaling message tracing task is
set to that configured in step 3. successfully created.
5. Run ADD SCCPGT to configure the GT data. 8. The SRI and query messages of the SPS
6. Create an SS7 signaling message tracing task. are traced, and the messages are correctly
resolved.
the SPS an SRI message in which the called
number is the ported-in subscriber's number
window.
Remarks None.
T19-0202 Calling Ported-out Subscribers
Objective Verify that the SPS can perform MAP query for ported-out subscribers when these
function.
software parameter table with MNP mode set 4. The user attribute table is successfully
to MNPFN and Message type of MNP service configured.
processing set to MAP. 5. The GT data is successfully configured.
separately.
7. The SPS obtains the subscriber's number
4. Run ADD SERUATTR to configure the user from the called GT in the SRI message and
attribute table with Number type set to detects that the subscriber is a ported-out
TYPE1(Moved out of local network), Route subscriber by querying the NPDB. Then,
index type set to RN, and NP route index the SPS obtains the subscriber's RN,
set to that configured in step 3. combines the RN with the called number
into an MSRN, and returns an SRI_ACK
message carrying the MSRN.
8. The SRI, SRI_ACK, and query messages
7. Simulate a scenario where the VMSC sends of the SPS are traced, and the messages
the SPS an SRI message in which the called are correctly resolved.
number is the ported-out subscriber's number
window.
Remarks None.

T19-0203 Calling Foreign Non-NP Subscribers
Objective Verify that the SPS can perform MAP query for foreign non-NP subscribers when
function.
processing set to MAP. 5. The GT data is successfully configured.
3. Run ADD SEMNPROUTENUM to configure the 6. The SPS obtains the subscriber's number
same RN table for the SPS and PGW, from the called GT and detects that the
separately. subscriber is a non-NP subscriber on a
4. Run ADD MNPFRGNRNG to configure the foreign network. Then, the SPS fills the
foreign number range table with Routing MSRN with the MSISDN and returns an
number index set to that configured in step 3. SRI_ACK message carrying the MSRN.
5. Run ADD SCCPGT to configure the GT data. 7. The SRI, SRI_ACK, and query messages
of the SPS are traced, and the messages
6. Create an SS7 signaling message tracing task. are correctly resolved.
the SPS an SRI message in which the called
number is within the foreign network number
range configured in step 4.
window.
Remarks None.
T19-0204 Calling Local Non-NP Subscribers
Objective Verify that the SPS can perform MAP query for local non-NP subscribers when

function. 3. The HLR address tables are successfully
software parameter table with MNP mode set 4. The local network number range table is
processing set to MAP.
same HLR address table for the SPS and 6. The SS7 signaling message tracing task is
PGW, separately. created.
4. Run ADD MNPLOCNRNG to configure the 7. The SPS obtains the subscriber's number
local network number range table with HLR from the called GT in the SRI message,
address index set to that configured in and detects that the subscriber is a non-NP
subscriber on the local network by
step 3. querying the NPDB. Then, the SPS obtains
5. Run ADD SCCPGT to configure the GT data. the subscriber's HLR GT, replaces the
6. Create an SS7 signaling message tracing task. called GT with the HLR GT, and sends the
message to the local HLR.
the SPS an SRI message in which the called 8. The SRI and query messages of the SPS
number is within the local network number are traced, and the messages are
range configured in step 4. resolved.
window.
Remarks None.
T19-03 IN NP Query for SMS
T19-0301 Sending Short Messages to Ported-in Subscribers
Objective Verify that the SPS can perform IN query for ported-in subscribers when short
messages are sent to these subscribers.
function.
configured.
processing set to CAP IDPSMS, and Multi RN
switch set to Open. 4. The GT data is successfully configured.
SEMNPHLRADDR to configure the same RN created.
table and HLR address table for the SPS and 6. The SPS obtains the called number from
PGW, separately. the CAP IDPSMS message, queries the

4. Run ADD SERUATTR to configure the user NPDB for the referenced RN, prefixes the
attribute table with Number type set to called number with the RN, and sends the
TYPE2(Moved in from external network), message to the SCP.
Route index type set to ALL, and HLR 7. The CAP IDPSMS and query messages of
address index and Routing number index the SPS are traced, and the messages are
set to those configured in step 3. correctly resolved.
the SPS a CAP IDPSMS message in which the
called number is the ported-in subscriber's
window.
Remarks None.
T19-0302 Sending Short Messages to Ported-out Subscribers
Objective Verify that the SPS can perform IN query for ported-out subscribers when short
function.
to MNPFN and Message type of MNP service configured.
processing set to CAP IDPSMS. 5. The GT data is successfully configured.
separately.
4. Run ADD SERUATTR to configure the user the CAP IDPSMS message, queries the
attribute table with Number type set to NPDB for the subscriber's home network
TYPE1(Moved out of local network), Route RN, prefixes the called number with the
index type set to RN, and NP route index RN, and sends the message to the SCP.
set to that configured in step 3. 8. The CAP IDPSMS and query messages of
5. Run ADD SCCPGT to configure the GT data. the SPS are traced, and the messages are
correctly resolved.
called number is the ported-out subscriber's
window.

Remarks None.
T19-0303 Sending Short Messages to Foreign Non-NP Subscribers
Objective Verify that the SPS can perform IN query for foreign non-NP subscribers when
short messages are sent to these subscribers.
function.
processing set to CAP IDPSMS. 5. The GT data is successfully configured.
separately.
4. Run ADD MNPFRGNRNG to configure the the CAP IDPSMS message, detects that
foreign network number range table with the subscriber is a non-NP subscriber from
Routing number index set to that configured a foreign network by querying the NPDB,
in step 3. and sends the message to the SCP.
5. Run ADD SCCPGT to configure the GT data. 8. The CAP IDPSMS and query messages of
6. Create an SS7 signaling message tracing task. the SPS are traced, and the messages are
correctly resolved.
called number is within the foreign network
window.
Remarks None.
T19-0304 Sending Short Messages to Local Non-NP Subscribers
Objective Verify that the SPS can perform IN query for local non-NP subscribers when short

function.
to MNPFN and Message type of MNP service 4. The local network number range table is
processing set to CAP IDPSMS. successfully configured.
3. Run ADD SEMNPROUTENUM and ADD 5. The GT data is successfully configured.
SEMNPHLRADDR to configure the same RN 6. The SS7 signaling message tracing task is
table and HLR address table for the SPS and created.
PGW, separately.
4. Run ADD MNPLOCNRNG to configure the the CAP IDPSMS message, detects that
local network number range with HLR address the subscriber is a non-NP subscriber on
index and Routing number index set to those the local network by querying the NPDB,
configured in step 3. and sends the message to the SCP.
5. Run ADD SCCPGT to configure the GT data. 8. The CAP IDPSMS and query messages of
correctly resolved.
called number is within the local network
window.
Remarks None.
T19-04 NP Subscriber MO-SMS Authentication
T19-0401 MO-SMS Authentication for Ported-in Subscribers
Objective Verify that the SPS can have the authentication on ported-in subscribers pass
when these subscribers send short messages.
function.
configured.
processing set to MAP, and SMS process
way in GSM set to BIT0(SMA). 5. The GT data is successfully configured.


table and HLR address table for the SPS and 7. The SPS obtains the calling number from
PGW, separately. the MAP layer in the MO message and
4. Run ADD SERUATTR to configure the user detects that the calling party is a local
attribute table with Number type set to subscriber by querying the NPDB. Then,
TYPE2(Moved in from external network), the SPS has the authentication pass and
Route index type set to ALL, and HLR sends the MO message to the SMSC.
address index and Routing number index 8. The MO and query messages of the SPS
set to those configured in step 3. are traced, and the messages are correctly
5. Run ADD SCCPGT to configure the GT data. resolved.
the SPS an MO message in which the calling
number is the ported-in subscriber's number
window.
Remarks None.
T19-0402 MO-SMS Authentication for Ported-out Subscribers
Objective Verify that the SPS can have the authentication on ported-in subscribers fail when
these subscribers send short messages.
function.
to MNPFN, Message type of MNP service configured.
processing set to MAP, and SMS process 5. The GT data is successfully configured.
way in GSM set to SMA.
6. The SS7 signaling message tracing task is
3. Run ADD SEMNPROUTENUM to configure the created.
same RN table for the SPS and PGW,
separately. 7. The SPS obtains the calling number from
the MAP layer in the MO message and
4. Run ADD SERUATTR to configure the user detects that the calling party is a foreign
attribute table with Number type set to network subscriber by querying the NPDB.
TYPE1(Moved out of local network), Route Then, the SPS has the authentication fail
index type set to RN, and NP route index and returns an MO_ACK message.
set to that configured in step 3. 8. The MO, MO_ACK and query messages of
correctly resolved.

number is the ported-out subscriber's number

window.
Remarks None.
T19-0403 MO-SMS Authentication for Foreign Non-NP Subscribers
Objective Verify that the SPS can have the authentication on foreign non-NP subscribers fail
function.
to MNPFN, Message type of MNP service successfully configured.
way in GSM set to SMA.
separately. 7. The SPS obtains the calling number from
4. Run ADD MNPFRGNRNG to configure the detects that the calling party is a foreign
foreign network number range table with network subscriber by querying the NPDB.
Routing number index set to that configured Then, the SPS has the authentication fail
in step 3. and returns an MO_ACK message.
5. Run ADD SCCPGT to configure the GT data. 8. The MO, MO_ACK and query messages of
correctly resolved.
number is within the foreign network number
window.
Remarks None.
T19-0404 MO-SMS Authentication for Local Non-NP Subscribers
Objective Verify that the SPS can have the authentication on local non-NP subscribers pass

function.
to MNPFN, Message type of MNP service 4. The local network number range table is
processing set to MAP, and SMS process successfully configured.
way in GSM set to SMA. 5. The GT data is successfully configured.
table and HLR address table for the SPS and
PGW, separately. 7. The SPS obtains the calling number from
4. Run ADD MNPLOCNRNG to configure the detects that the calling party is a local
local network number range table with Routing subscriber by querying the NPDB. Then,
number index and HLR address index set the SPS has the authentication pass and
to those configured in step 3. sends the MO message to the SMSC.
5. Run ADD SCCPGT to configure the GT data. 8. The MO and query messages of the SPS
6. Create an SS7 signaling message tracing task. are traced, and the messages are correctly
resolved.
number is within the local network number
window.
Remarks None.
T19-05 MAP NP Query for SMS
T19-0501 Sending Short Messages to Ported-in Subscribers
Objective Verify that the SPS can perform MAP query for ported-in subscribers when short
function.

2. Run SET MNPSOFTCFG to configure the MNP 3. The HLR address tables are successfully
software parameter table with MNP mode set configured.
to MNPFN, Message type of MNP service 4. The user attribute table is successfully
processing set to MAP, and SMS process configured.
way in GSM set to SRI FOR SM.
same HLR address table for the SPS and 6. The SS7 signaling message tracing task is
PGW, separately. created.
4. Run ADD SERUATTR to configure the user 7. The SRI_FOR_SM and query messages of
attribute table with Number type set to the SPS are traced, and the messages are
TYPE2(Moved in from external network), correctly resolved.
Route index type set to HLR, and HLR
address index set to that configured in step
3.
7. Simulate a scenario where the SMSC sends
the SPS an SRI_FOR_SM message in which
the called number is the ported-in subscriber
window.
Remarks None.
T19-0502 Sending Short Messages to Ported-out Subscribers
Objective Verify that the SPS can perform MAP query for ported-out subscribers when short
function.
to MNPFN, Message type of MNP service configured.
way in GSM set to SRI FOR SM.
separately. 7. The SPS obtains the subscriber's number
from the called GT in the SRI_FOR_SM
4. Run ADD SERUATTR to configure the user message and detects that the subscriber is
attribute table with Number type set to a ported-out subscriber by querying the
TYPE1(Moved out of local network), Route NPDB. Then, the SPS obtains the
index type set to RN, and NP route index subscriber's RN, fills the called GT with
combination of the RN and called number,

set to that configured in step 3. and send a message carrying the called
5. Run ADD SCCPGT to configure the GT data. GT to the foreign HLR.
6. Create an SS7 signaling message tracing task. 8. The SRI_FOR_SM and query messages of
the SPS are traced, and the messages are
7. Simulate a scenario where the SMSC sends correctly resolved.
the called number is the ported-out subscriber's
window.
Remarks None.
T19-0503 Sending Short Messages to Foreign Non-NP Subscribers
Objective Verify that the SPS can perform MAP query for foreign non-NP subscribers when
function.
to MNPFN, Message type of MNP service successfully configured.
processing set to MAP, The RN 5. The GT data is successfully configured.
configuration parameter of foreign regular
users set to G3(MAP non-call-related), and 6. The
SMS process way in GSM set to SRI FOR 7. The SPS obtains the subscriber's number
SM. from the called GT in the SRI_FOR_SM
3. Run ADD SEMNPROUTENUM to configure the message and detects that the subscriber is
same RN table for the SPS and PGW, a non-NP subscriber from a foreign
separately. network by querying the NPDB. Then, the
SPS obtains the subscriber's RN, fills the
4. Run ADD MNPFRGNRNG to configure the called GT with combination of the RN and
foreign network number range table with called number, and send a message
Routing number index set to that configured carrying the called GT to the foreign HLR.
in step 3.
8. The SRI_FOR_SM and query messages of
7. Simulate a scenario where the SMSC sends correctly resolved.
the called number is within the foreign network
window.
Remarks None.

T19-0504 Sending Short Messages to Local Non-NP Subscribers
Objective Verify that the SPS can perform MAP query for local non-NP subscribers when
function.
3. The HLR address tables are successfully
to MNPFN, Message type of MNP service 4. The local network number range table is
processing set to MAP, and SMS process successfully configured.
way in GSM set to SRI FOR SM. 5. The GT data is successfully configured.
3. Run ADD SEMNPHLRADDR to configure the 7. The SPS obtains the subscriber's number
same HLR address table for the SPS and from the called GT in the SRI_FOR_SM
PGW, separately. message, and detects that the subscriber
4. Run ADD MNPLOCNRNG to configure the is a non-NP subscriber on the local
local network number range table with HLR network by querying the NPDB. Then, the
address index set to that configured in SPS obtains the subscriber's HLR GT,
replaces the called GT with the HLR GT,
step 3. and sends the message to the local HLR.
8. The SRI_FOR_SM and query messages of
7. Simulate a scenario where the SMSC sends resolved.
the called number is within the local network
window.
Remarks None.
T19-06 FNR Function
T19-0601 FNR Processing on Location Update Messages
Objective Verify that the SPS can perform FNR processing on location update messages.

function.
3. The route number tables and HLR tables
2. Run SET MNPSOFTCFG to configure the MNP are successfully configured.
configured.
processing set to MAP, and FNR IMSI switch
set to SWITCH1(Open). 5. The GT data is successfully configured.
SEMNPHLRADDR to configure the MNP route successfully created.
number table and HLR address table. 7. The SPS obtains the IMSI from the location
4. Run ADD SERUATTR to configure the user update message and detects that the
attribute table with Number type set to subscriber number is a flexible number by
TYPE4(Flexible number), Route index type querying the NPDB. Then, the SPS obtains
the subscriber's HLR GT, replaces the
set to ALL, and HLR address index and
called GT with the HLR GT, and sends the
Routing number index set to those configured
message to the HLR.
in step 3.
8. The location update message and query
message of the SPS are traced, and the
6. Create an SS7 signaling message tracing task. messages are correctly resolved.
the SPS a location update message in which
the IMSI matches the flexible number
window.
Remarks This test also applies to the following messages:

SAI, GPRS_LU, USSD, REG_SS, ERASE_SS, ACT_SS, DEA_SS,
REG_PASSWORD, INTERROGATE_SS, RESTORE_DATA, READY_FOR_SM,
PURGE_MS, BEGIN_SUBSCRIBER_ACTIVITY, and SEND_PARAMETERS
T19-07 ATI NP Query
T19-0701 IN NP Query for ATI Messages
Objective Verify that the SPS can perform IP NP query for ATI messages.
function.
4. The foreign network number range table is

software parameter table with MNP mode set successfully configured.

to MNPFN, Message type of MNP service 5. The GT data is successfully configured.
processing set to MAP, The RN
configuration parameter of foreign regular 6. The SS7 signaling message tracing task is
users set to ATI, and ATI mode set to successfully configured.
MODE1(TC relay). 7. The SPS obtains the subscriber number
3. Run ADD SEMNPROUTENUM to configure the from the MAP layer in the ATI message
same RN table for the SPS and PGW, and detects that the subscriber is a
separately. common foreign subscriber. Then, the SPS
obtains the subscriber's RN and returns
4. Run ADD MNPFRGNRNG to add the foreign the NP status and the RN to the SMSC by
number range table with Routing number sending an ATI_ACK message.
index set to that configured in step 3.
8. The ATI, ATI_ACK and query messages of
6. Create an SS7 signaling message tracing task. correctly resolved.
7. Simulate a scenario where the SMSC sends
the SPS an ATI message in which the
subscriber number is within the foreign network
window.
Remarks None.
T19-08 ISUP NP Query
T19-0801 NP Query for IAM Messages in the ISUP Triggerless Relay Solution
Objective Verify that the SPS can perform NP query for IAM messages.
P207, Modification option set to P0(By 3. The LNP software parameter table is
value), and Value set to 1 to enable the NP configured.
function.
2. Run SET LNPSOFTCFG to configure the LNP
software parameter table with Message type 5. The user attribute table is successfully
set to ISUP, Configuration of caller change configured.
set to ISUP, Configuration of called change 6. The GT data is successfully configured.
set to ISUP, RN configuration of called
number converted to location routing 7. The SS7 signaling message tracing task is
number set to ISUP. created.
3. Run MOD M3LKS to set Service process 8. The SPS obtains the calling and called
switch to LNPSWT(LNP service switch) for numbers from the IAM message and
the link set that connects Peer device 1 to the detects that the calling and called parties
SPS. are local fixed subscribers by querying the
NPDB. In addition, the calling is a physical
4. Run ADD SEMNPROUTENUM to configure the number, and the called number is a logical
same RN table for the SPS and PGW, number. Then, the SPS converts the

separately. calling number in the message into a

5. Run ADD SERUATTR to configure two user logical number and the called number into
a physical number and send the IAM
attribute tables with Number type set to
message to the peer device.
TYPE9(Local fixed network), Route index
type set to RN, and NP route index set to 9. The IAM and query messages of the SPS
that configured in step 4. are traced, and the messages are correctly
resolved.
7. Simulate a scenario where Peer device 1 sends
the SPS an IAM message in which the calling
and called numbers match the fixed subscriber
numbers configured in step 5 and the DSP is
not that of the SPS.
window.
Remarks None
T19-09 NP Routing Loop Prevention
T19-0901 NP Routing Loop Prevention
Objective Verify that the SPS can perform the NP routing loop prevention function.
function.
configured.
processing set to MAP, Local network route 5. The GT data is successfully configured.
number set to a value, and Loop detection 6. The SS7 signaling message tracing task is
switch set to G1. configured.
3. Run ADD SEMNPROUTENUM to configure the 7. The SPS obtains the subscriber's number
same RN table for the SPS and PGW, from the called GT in the SRI message and
separately. detects that the number is prefixed with the
4. Run ADD SERUATTR to configure the user same local network RN configured in step
attribute table with Number type set to 8., indicating that the number is a local
TYPE1(Moved out of local network), Route number and the SRI message is sent from
a foreign network. However, the SPS also
index type set to RN, and NP route index
detects that the number is not a local
set to that configured in step 3.
network. In this case, the NP status is
5. Run ADD SCCPGT to configure the GT data. inconsistent and the SPS returns an error
6. Create an SS7 signaling message tracing task. message.
7. Simulate a scenario where the VMSC sends 8. The SRI and query messages of the SPS
the SPS an SRI message in which the called are traced, and the messages are correctly

number is the subscriber number configured in resolved.

step 4 and is prefixed with the local network RN
window.
Remarks None
T20 Address Resolution

T20-01 Locating IMS-HSS Based on IMPU
T20-0101 Locating IMS-HSS Based on IMPU
Objective Verify that the SPS can query the IMS-HSS address based on the IMPU and
forward responses when multiple IMS-HSSs are deployed.
 The license control item Locating IMS-HSS Based on User Identity has
been activated for SPS_A.
 The P69(FE application type control parameter) parameter has been set to
1, and the setting has taken effect.
1. Run MOD SFP on SPS_A to enable the 1. The function of locating IMS-HSS based on
function of locating IMS-HSS based on user identity is enabled.
user identity with Parameter name set to 2. The route result is successfully added.
P70, Modification option set to P1(By
bit), Bit set to 0, and Bit value set to 1. 3. The realm route is successfully added.
2. Run ADD RTRESULT on SPS_A to add a 4. The server group is successfully added.
route result with Route result name set to 5. The subscriber is successfully defined.
rt and Relay device 1 set to the name of
Peer device 4. 6. After receiving the UAR message, SPS_A
performs address resolution and adds the
3. Run ADD DMRT on SPS_A to add a realm destination-host AVP whose value is the host
route with Realm route name set to test1, name of Peer device 3 in the message. Then,
Realm name set to the realm name of SPS_A sends the message to Peer device 3
Peer device 3, Application identifier set based on the destination-host AVP and
to Cx/Dx, Local action set to forwards the response from Peer device 3 to
RELAY(RELAY), and Route result name Peer device 1.
set to rt.
7. The function of locating IMS-HSS based on
4. Log in to the PGW Web LMT of the user identity is disabled.
USCDB, select SPS SLF Management,
and run ADD SPSSRVGRP to add a 8. SPS_A sends the UAR message to Peer device
server group with Server Group ID set to 4 based on the destination realm and forwards
20, HOST1 set to the host name of Peer the response from Peer device 4 to Peer device
device 3, Priority of Host1 set to 0, 1. In the received and sent UAR messages, the
HOST2 set to the host name of Peer destination-host AVP is not carried.
device 4, and Priority of Host2 set to 1.
5. Log in to the PGW Web LMT of the
USCDB, select SPS SLF Management,

and run ADD SPSSLFUSR to define a

subscriber with USER ID TYPE set to
DIMPU, USER ID set to tel:+
331234567890, and IMS-HSS Group ID
set to 20.
6. Simulate a scenario where Peer device 1
sends SPS_A a UAR message in which
the destination realm name is that of Peer
device 3, {public-identity}AVP set to tel:+
331234567890, and no destination host
name is carried. Then, trace Diameter
messages on SPS_A.
7. Run MOD SFP on SPS_A to disable the
function of locating IMS-HSS based on
user identity with Parameter name set to
P70, Modification option set to P1(By
bit), Bit set to 0, and Bit value set to 0.
8. Simulate a scenario where Peer device 1
sends SPS_A a UAR message in which
the destination realm name is that of Peer
device 3, {public-identity}AVP set to tel:+
331234567890, and no destination host
name is carried. Then, trace Diameter
messages on SPS_A.
Remarks None
T20-02 Locating SAE-HSS Based on IMSI
T20-0201 Locating SAE-HSS Based on IMSI
Objective Verify that the SPS can query the SAE-HSS address based on the IMSI and
forward responses when multiple SAE-HSSs are deployed.
 The license control item Locating SAE-HSS Based on User Identity has
been activated for SPS_A.
1. Run MOD SFP on SPS_A to enable the 1. The function of locating SAE-HSS based
function of locating SAE-HSS based on user on user identity is enabled.
identity with Parameter name set to P70, 2. The route result is successfully added.
Modification option set to P1(By bit), Bit set
to 1, and Bit value set to 1. 3. The realm route is successfully added.
2. Run ADD RTRESULT on SPS_A to add a route 4. The server group is successfully added.
result with Route result name set to rt and 5. The subscriber is successfully defined.
Relay device 1 set to the name of Peer device
4. 6. After receiving the ULR message, SPS_A
3. Run ADD DMRT to add a realm route with destination-host AVP whose value is the

Realm route name set to test1, Realm name host name of Peer device 3 in the
set to the realm name of Peer device 3, message. Then, SPS_A sends the
Application identifier set to S6a/S6d, Local message to Peer device 3 based on the
action set to RELAY(RELAY), and Route destination-host AVP and forwards the
result name set to rt. response from Peer device 3 to Peer
4. Log in to the PGW Web LMT of the USCDB, device 1.
select SPS SLF Management, and run ADD 7. The function of locating SAE-HSS based
SPSSRVGRP to add a server group with on user identity is disabled.
Server Group ID set to 20, HOST1 set to the 8. SPS_A sends the ULR message to Peer
host name of Peer device 3, Priority of Host1 device 4 based on the destination realm
set to 0, HOST2 set to the host name of Peer and forwards the response from Peer
device 4, and Priority of Host2 set to 1. device 4 to Peer device 1. In the received
5. Log in to the PGW Web LMT of the USCDB, and sent ULR messages, the destination-
select SPS SLF Management, and run ADD host AVP is not carried.
SPSSLFUSR to define a subscriber with USER
ID TYPE set to IMSI, USER ID set to 0123456,
and SAE-HSS Group ID set to 20.
SPS_A a ULR message in which the
destination realm name is that of Peer device 3,
user-name AVP set to 0123456, and no
destination host name is carried. Then, trace
Diameter messages on SPS_A.
function of locating SAE-HSS based on user
identity with Parameter name set to P70,
to 1, and Bit value set to 0.
SPS_A a ULR message in which the
user-name AVP set to 0123456, and no
destination host name is carried. Then, trace
Diameter messages on SPS_A.
Remarks None
T20-03 Locating PCRF Based on MSISDN
T20-0301 Locating PCRF Based on MSISDN
Objective Verify that the SPS can query the PCRF address based on the MSISDN and
forward responses when multiple PCRFs are deployed.
 The license control item Locating PCRF Based on User Identity has been
activated for SPS_A.

1. Run MOD SFP on SPS_A to enable the 1. The function of locating PCRF based on
function of locating PCRF based on user user identity is enabled.
identity with Parameter name set to P70, 2. The route result is successfully added.
4. 6. After receiving the CCR message, SPS_A
Application identifier set to Gx, Local action message to Peer device 3 based on the
set to RELAY(RELAY), and Route result destination-host AVP and forwards the
name set to rt. response from Peer device 3 to Peer
select SPS SLF Management, and run ADD 7. The function of locating PCRF based on
SPSSRVGRP to add a server group with user identity is disabled.
Server Group ID set to 20, HOST1 set to the
host name of Peer device 3, Priority of Host1 8. SPS_A sends the CCR message to Peer
set to 0, HOST2 set to the host name of Peer device 4 based on the destination realm
device 4, and Priority of Host2 set to 1. and forwards the response from Peer
device 4 to Peer device 1. In the received
5. Log in to the PGW Web LMT of the USCDB, and sent CCR messages, the destination-
ID TYPE set to MSISDN, USER ID set to
0123456789, and PCRF Group ID set to 20.
SPS_A a CCR message in which the
MSISDN is 0123456789, and no destination
host name is carried. Then, trace Diameter
messages on the SPS.
function of locating PCRF based on user
Remarks None
T20-04 Locating PCRF Based on IMSI
T20-0401 Locating PCRF Based on IMSI
Objective Verify that the SPS can query the PCRF address based on the IMSI when multiple
PCRFs are deployed and can return responses.

 The license control item Locating PCRF Based on User Identity has been
activated for SPS_A.
1. Run MOD SFP on SPS_A to enable the 1. The function of locating PCRF based on
function of locating PCRF based on user user identity is enabled.
identity with Parameter name set to P70, 2. The IMSI-based address resolution for the
Modification option set to P1(By bit), Bit set PCRF is enabled.
3. The route result is successfully added.
2. Run MOD SFP on SPS_A to enable the IMSI-
based address resolution for the PCRF with 4. The realm route is successfully added.
Parameter name set to P70, Modification 5. The server group is successfully added.
option set to P1(By bit), Bit set to 5, and Bit
value set to 1. 6. The subscriber is successfully defined.
3. Run ADD RTRESULT on SPS_A to add a route 7. After receiving the CCR message, SPS_A
result with Route result name set to rt and performs address resolution and adds the
Relay device 1 set to the name of Peer device destination-host AVP whose value is the
4. host name of Peer device 3 in the
message. Then, SPS_A sends the
4. Run ADD DMRT to add a realm route with message to Peer device 3 based on the
Realm route name set to test1, Realm name destination-host AVP and forwards the
set to the realm name of Peer device 4, response from Peer device 3 to Peer
Application identifier set to Gx, Local action device 1.
set to RELAY(RELAY), and Route result
name set to rt. 8. The function of locating PCRF based on
user identity is disabled.
5. Log in to the PGW Web LMT of the USCDB,
select SPS SLF Management, and run ADD 9. SPS_A sends the CCR message to Peer
SPSSRVGRP to add a server group with device 4 based on the destination realm
Server Group ID set to 20, HOST1 set to the and forwards the response from Peer
host name of Peer device 3, Priority of Host1 device 4 to Peer device 1. In the received
set to 0, HOST2 set to the host name of Peer and sent CCR messages, the destination-
device 5, and Priority of Host2 set to 1. host AVP is not carried.

select SPS SLF Management, and run ADD
and PCRF Group ID set to 20.
IMSI is 0123456, and no destination host name
is carried. Then, trace Diameter messages on
the SPS.
function of locating PCRF based on user
the SPS.

Remarks None
T20-05 Locating Accounting Server Based on MSISDN
T20-0501 Locating Accounting Server Based on MSISDN
Objective Verify that the SPS can query the accounting server address based on the
MSISDN and forward responses when multiple accounting servers are deployed.
 The license control item Locating Accounting Server Based on User
Identity has been activated for SPS_A.
1. Run MOD SFP on SPS_A to enable the 1. The function of locating accounting server
function of locating accounting server based on based on user identity is enabled.
user identity with Parameter name set to P70, 2. The route result is successfully added.
4. 6. After receiving the CCR message, SPS_A
Application identifier set to Gy/Ro, Local message to Peer device 3 based on the
action set to RELAY(RELAY), and Route destination-host AVP and forwards the
result name set to rt. response from Peer device 3 to Peer
select SPS SLF Management, and run ADD 7. The function of locating accounting server
SPSSRVGRP to add a server group with based on user identity is disabled.
Server Group ID set to 20, HOST1 set to the
host name of Peer device 3, Priority of Host1 8. SPS_A sends the CCR message to Peer
set to 0, HOST2 set to the host name of Peer device 4 based on the destination realm
device 4, and Priority of Host2 set to 1. and forwards the response from Peer
5. Log in to the PGW Web LMT of the USCDB, and sent CCR messages, the destination-
ID TYPE set to MSISDN, USER ID set to
0123456789, and Accounting Server Group
ID set to 20.

function of locating accounting server based on

user identity with Parameter name set to P70,
Remarks None
T20-06 Locating Accounting Server Based on IMSI
T20-0601 Locating Accounting Server Based on IMSI
Objective Verify that the SPS can query the accounting server address based on the IMSI
and forward responses when multiple accounting servers are deployed.
user identity with Parameter name set to P70, 2. The IMSI-based address resolution for
Modification option set to P1(By bit), Bit set ACCOUNTING SERVER is enabled.
2. Run MOD SFP on SPS_A to enable the IMSI-
based address resolution for accounting server 4. The realm route is successfully added.
with Parameter name set to P70, Modification 5. The server group is successfully added.
option set to P1(By bit), Bit set to 7, and Bit
value set to 1. 6. The subscriber is successfully defined.
message. Then, SPS_A sends the
4. Run ADD DMRT to add a realm route with message to Peer device 3 based on the
Realm route name set to test1, Realm name destination-host AVP and forwards the
set to the realm name of Peer device 4, response from Peer device 3 to Peer
Application identifier set to Gy/Ro, Local device 1.
action set to RELAY(RELAY), and Route
result name set to rt. 8. The function of locating accounting server
based on user identity is disabled.

host name of Peer device 3, Priority of Host1 and sent CCR messages, the destination-
set to 0, HOST2 set to the host name of Peer host AVP is not carried.
device 5, and Priority of Host2 set to 1.
and Accounting Server Group ID set to 20.
the SPS.
the SPS.
Remarks None
T20-07 Locating Accounting Server Based on IMPU
T20-0701 Locating Accounting Server Based on IMPU
Objective Verify that the SPS can query the accounting server address based on the IMPU
and forward responses when multiple accounting servers are deployed.
user identity with Parameter name set to P70, 2. The DIMPU/DPUSI-based address
Modification option set to P1(By bit), Bit set resolution for accounting server is enabled.
2. Run MOD SFP on SPS_A to enable the
DIMPU/DPUSI-based address resolution for 4. The realm route is successfully added.
accounting server with Parameter name set to 5. The server group is successfully added.
P70, Modification option set to P1(By bit), Bit

set to 8, and Bit value set to 1. 6. The subscriber is successfully defined.

4. Run ADD DMRT to add a realm route with message. Then, SPS_A sends the
Realm route name set to test1, Realm name message to Peer device 3 based on the
set to the realm name of Peer device 4, destination-host AVP and forwards the
Application identifier set to Gy/Ro, Local response from Peer device 3 to Peer
action set to RELAY(RELAY), and Route device 1.
result name set to rt. 8. The function of locating accounting server
5. Log in to the PGW Web LMT of the USCDB, based on user identity is disabled.
host name of Peer device 3, Priority of Host1 device 4 to Peer device 1. In the received
set to 0, HOST2 set to the host name of Peer and sent CCR messages, the destination-
device 5, and Priority of Host2 set to 1. host AVP is not carried.
ID TYPE set to DIMPU, USER ID set to
sip:user@host, and Accounting Server
Group ID set to 20.
DIMPU is sip:user@host, and no destination
DIMPU is sip:user@host, and no destination
Remarks None
T21 Virtualized Diameter Routing Agent

T21-01 Alarm Reporting for Multiple SPSs Sharing One OMU
T21-0101 Alarm Reporting for Multiple SPSs Sharing One OMU
Objective Verify that alarms can be generated for a faulty SPS when multiple SPSs share
one OMU, and the alarms can be cleared after the SPS recovers.

Prerequisites  The SPSs sharing one OMU are running properly.

 Diameter links are normal.
1. Log in to the OMU client, and run DEA DMLNK 1. The Diameter link is successfully
to deactivate a Diameter link in the MML deactivated.
command windows of different SPS. 2. Diameter link alarms are generated for
2. Choose Alarm > Browse Alarms to check the related SPSs.
alarm. 3. Alarms are cleared.
3. Run ACT DMLNK to activate the deactivated
link and check the alarms.
Remarks None.
T21-02 Performance Management of Multiple SPSs Sharing One OMU
T21-0201 Performance Management of Multiple SPSs Sharing One OMU
Objective Verify that the Diameter performance measurements of the SPSs sharing one
OMU are independent from each other and can correctly count the number of
received Diameter messages.
Prerequisites  The OMU board runs properly.

 The SPSs sharing one OMU are running properly.
 You have logged in to the Web UI.
 The system is processing messages.
1. In the Address bar, type http://OMU IP 1. The login is successful.

address to open the HUAWEI Operation & 2. The Performance Management System
Maintenance System window. On the login window is opened
page, enter admin in the User name text box,
enter the password in the Password text box, 3. The Diameter message measurement task
select Local for User type, and click Login. with the measurement period set to 5
minutes is created.
2. On the HUAWEI Operation & Maintenance
System window, click Performance 4. The value of the Number of Received
Management System. Diameter Messages measurement entity is
correct.
3. In the navigation tree, choose Site > SPS[ME
Name] > SPS Basic Measurement > 5. The performance measurement of each
Diameter Message Measurement. Right-click SPS is independent and can correctly
Diameter Message Measurement to select count the number of received Diameter
Measurement. On the Measurement page, messages.
check the measurement task.
4. Have a peer device send Diameter messages
to an SPS within the preconfigured period. On
the Performance Management System page,
choose Site > SPS[ME Name] > SPS Basic
Measurement > Diameter Message

Measurement. Right-click Diameter Message

Measurement to select Query. In the
Measurement Unit/Entity area, select only
Number of Received Diameter Messages,
specify Period, and click Submit.
5. Perform steps 3 and 4 for different SPSs and
check whether the number of Diameter
messages is correct.
Remarks None.
T21-03 Unified M2000 Access of Multiple SPSs Sharing One OMU
T21-0301 Unified M2000 Access of Multiple SPSs Sharing One OMU
Objective Verify that multiple SPSs sharing one OMU can be managed by the M2000 in a
unified manner.
Prerequisites  The SPSs sharing one OMU are running properly.

 The M2000 server is running properly.
 The network communication between the M2000 server and the SPSs is
normal.
 The CGP and SPS mediation packages are installed on the M2000.
 The hardware installation, software commissioning, and data configuration
of the SPSs are complete.
1. In the main topology of the M2000, right-click 1. The configuration information about the
an SPS, and choose MIT Browser to open the SPS on the M2000 is correct.
MIT Browser window. Check whether the 2. MML commands can be successfully
configuration information about the SPS on the executed.
M2000 is correct.
3. Detailed information about the alarm can
2. In the main topology of the M2000, right-click be queried. Alarm information queried from
an SPS, and choose MML Command to open the M2000 client is the same as that
the MML Command window. Run a command, queried from the LMT of the SPS.
and check whether the command can be
successfully executed. 4. Performance measurements tasks can be
created, and measurement results can be
3. In the main topology of the M2000, right-click queried. The measurement results are the
an SPS, and choose Query Alarm/Event > same as that queried from the
Alarm List. In the displayed Browse Alarm Performance Measurement System.
List window, double-click an alarm to open the
Detailed Information dialog box and view
detailed information about this alarm
4. On the M2000 client, choose Performance >
Measurement Management to open the
Measurement Management window. In the
navigate tree on the left, choose SPS V3 >
Diameter Link > Diameter Link Measurement
and select an NE to be measured. In the
Measurement Settings window, set the
measurement period to five minutes, select all
measurement entities in the Measurement

Counter area, and select all measurement

objects in the All Measurement Object area.
Five minutes later, query the measurement
results and check whether the measurement
results are the same as that queried from the
Performance Measurement System.
Remarks This test requires the M2000 for cooperation.
T22 Message Tracing

T22-01 SS7 User Message Tracing
T22-0101 SS7 User Message Tracing
Objective Verify that the SPS can perform the SS7 user message tracing.
1. On the OMU client, click Maintenance tab, 1. The SS7 user message tracing task is
choose Service > Tracing, select SPS_A, and successfully created.
double-click SS7 User to open the SS7 User 3. Messages can be traced based on the
Trace window. Enter the MSISDN or IMSI, tracing conditions. The traced message
select a value for Combination, and click OK. can be resolved after you double-click the
2. Use Peer device 1 to send a message message.
matching the traced conditions and view the
message tracing interface.
Remarks None.
T23 SS7 Signaling Screening

T23-01 FW Screening
T23-0101 FWIM-based Message Screening
Objective Verify that the SPS can perform signaling screening based on the FW Initial
Screening table.


1. Run SET FWSOFTCFG to configure the 1. The parameter is configured.

parameter related to the SS7 signaling 2. The FW initial screening data is added.
screening service with C7MTP screen level set
to MTPLEVEL and SS7 Signaling screening 3. The M3UA linkset data is modified.
trace type set to ALL. 4. The SPS receives the UDT message, but
2. Run ADD FWIM to add FW initial screening does not forward it to HLR1. The UDT
data with FW intial screening name set to a messagecan be traced in the message
proper value, Local screening reference tracing list, with Block displayed in the
number set to 0, and Type of next screening Message Direction column.
set to Block.
3. Run MOD M3LKS to modify M3UA linkset data
with Screening function set to ON and
Screening reference set to 0.
4. On the SPS, create an SS7 Message Tracing
Enhancement tracing task, with Location
Parameter Type set to M3UA Linkset,
Location Parameter Value set to the related
link name, and Bussiness Type set to
Message Screening.
DPC of HLR 1.
Remarks None.
T23-0102 OPC-based Message Screening
Objective Verify that the SPS can screen messages based on the setting of the FW OPC
screening table.


parameter related to the SS7 signaling 2. The FW OPC screening data is added.
to MTPLEVEL and SS7 Signaling screening 3. The FW initial screening data is added.
trace type set to ALL. 4. The M3UA linkset data s modified.
2. Run ADD FWOPCBLK to add FW OPC 5. The SPS receives the UDT message, but
screening data with FW intial screening name does not forward it to HLR1. The UDT
set to a proper value, Local screening messagecan be traced in the message
reference number set to 0, Network indicator tracing list, with Block displayed in the
set to the same value (for example NM) as the Message Direction column.
MSC, Start OPC to 000000, End OPC to
FFFFFF, and Type of next screening set to
Block.
3. Run ADD FWIM to add FW initial screening
data with FW intial screening name set to a
proper value, Local screening reference

number set to 0, Type of next screening set

to OPCM, and Next sceening reference
number set to 0.
Message Screening.
DPC of HLR 1.
Remarks None.
T23-0103 DPC-based Message Screening
Objective Verify that the SPS can screen messages based on the setting of the FW DPC
screening table.


parameter related to the SS7 signaling 2. The FW DPC screening data is added.
trace type set to ALL. 4. The M3UA linkset data is added.
2. Run ADD FWDPCBLK to add FW DPC 5. The SPS receives the UDT message, but
screening data with FW intial screening name does not forward it to HLR1. The UDT
set to a proper value, Local screening messagecan be traced in the message
reference number set to 0, Network indicator tracing list, with Block displayed in the
set to the same value (for example NM) as the Message Direction column.
MSC, Start OPC to 000000, End OPC to
FFFFFF, and Type of next screening set to
Block.
3. Run ADD FWIM to add FW initial screening
data with FW intial screening name set to a
proper value, Local screening reference
number set to 0, Type of next screening set
to DPCM, and Next sceening reference
number set to 0.


Message Screening.
DPC of HLR 1.
Remarks None.
T23-0104 Calling GT-based Message Screening
Objective Verify that the SPS can screen messages based on the setting of the FW Calling
GT Screening table.


trace type set to ALL. 4. The M3UA linkset data is modified.
2. Run ADD FWCGGTBLK to configure FW 5. The SPS receives the UDT message, but
calling GT screening data with FW intial does not forward it to HLR1. The UDT
screening name set to a proper value, Local messagecan be traced in the message
screening reference number set to 0, GT tracing list, with Block displayed in the
Type set to the target type (for example GT4), Message Direction column.
and Type of next screening set to Block.
3. Run ADD FWIM to configure FW initial
screening data with FW intial screening name
set to a proper value, Local screening
reference number set to 0, Type of next
screening set to CGGTM, and Next sceening
reference number set to 0.
4. Run MOD M3LKS to configure M3UA linkset
data with Screening function set to ON and
Message Screening.
DPC of HLR 1.
Remarks None.

T23-0105 Called GT-based Message Screening
Objective Verify that the SPS can screen messages based on the setting of the FW Called
GT Screening table.


trace type set to ALL. 4. The M3UA linkset data is modified.
2. Run ADD FWCDGTBLK to configure FW 5. The SPS receives the UDT message, but
called GT screening data with FW intial does not forward it to HLR1. The UDT
screening name set to a proper value, Local messagecan be traced in the message
screening reference number set to 0, GT tracing list, with Block displayed in the
Type set to the target type (for example GT4), Message Direction column.
and Type of next screening set to Block.
3. Run ADD FWIM to configure FW initial
screening data with FW intial screening name
set to a proper value, Local screening
reference number set to 0, Type of next
screening set to CDGTM, and Next sceening
reference number set to 0.
4. Run MOD M3LKS to configure M3UA linkset
data with Screening function set to ON and
Message Screening.
DPC of HLR 1.
Remarks None.
T24 Message Duplication

T24-01 Application ID-based Message Duplication
T24-0101 Application ID-based Message Duplication
Objective Verify that the SPS can duplicate messages to a third-party device based on the

Application ID carried in the messages.
 The license that supports message duplication has been activated on
SPS_A. In addition, the software parameter for the message duplication
function has been enabled.
1. Run ADD MDRESULT on SPS_A to add a 1. The message duplication route result is
message duplication route result with Message added.
duplication result name set to rst, Message 2. The message duplication entrance is
duplication mode set to UNICAST(Unicast), added.
Message duplication device selection mode
set to MASTER_SLAVE(MASTER SLAVE), 3. The application ID message duplication is
and Message duplication device 1 set to Peer added.
device 4. 4. The message duplication exit is added.
2. Run ADD MDENT on SPS_A to add a 5. The peer device configuration is modified.
message duplication entrance with Message
duplication entrance name set to ent, Next 6. The message tracing results show that
rule set to MDAPPID(AppId Message SPS_A can route the message to Peer
Duplication), and Next reference index set to device 3 and receive responses from Peer
0. device 3. SPS_A can also duplicate the
message to Peer device 4 when routing it
3. Run ADD MDAPPID on SPS_A to add an to Peer device 3.
application ID message duplication with
Reference index set to 0, Application
identifier set to S6a/S6d(MME-HSS/SGSN-
HSS), Next rule set to MDEXIT(Message
Duplication Exit), and Next reference index
set to 1.
4. Run ADD MDEXIT on SPS_A to configure a
message duplication exit with Reference index
set to 1 and Message duplication result
name set to rst.
4. Run MOD DMPEER on SPS_A to modify
configuration of Peer device 3 with Peer name
set to Peer device 3 and Outgoing message
duplication entrance name set to ent.
SPS_A. In this message, the destination-host
AVP is the host name of Peer device 3. Create
tracing tasks and trace the Diameter message
over linksets 5 and 6.
Remarks None.
T24-0102 Dest-Realm-based Message Duplication
Dest-Realm carried in the messages.


set to MASTER_SLAVE(MASTER SLAVE), 3. The destination realm message duplication
and Message duplication device 1 set to Peer is added.
rule set to MDDR(Dest Realm Message SPS_A can route the message to Peer
3. Run ADD MDDREALM on SPS_A to add a to Peer device 3.
destination realm message duplication with
Reference index set to 0, Destination realm
set to Peer device 3, Next rule set to
MDEXIT(Message Duplication Exit), and
Next reference index set to 1.
name set to rst.
Remarks None.
T24-0103 Dest-Host-based Message Duplication
Dest-Host carried in the messages.

set to MASTER_SLAVE(MASTER SLAVE), 3. The destination host message duplication
rule set to MDDH(Dest Host Message SPS_A can route the message to Peer
3. Run ADD MDDHOST on SPS_A to add a to Peer device 3.
destination host message duplication with
Reference index set to 0, Destination host
set to Peer device 3, Next rule set to
name set to rst.
Remarks None.
T24-0104 Origin-Realm-based Message Duplication
Origin-Realm carried in the messages.
duplication mode set to UNICAST(Unicast),

Message duplication device selection mode added.

set to MASTER_SLAVE(MASTER SLAVE), 3. The origin realm message duplication is
device 4.
4. The message duplication exit is added.
2. Run ADD MDENT on SPS_A to add a
message duplication entrance with Message 14. The peer device configuration is modified.
rule set to MDOR(Origin Realm Message SPS_A can route the message to Peer
3. Run ADD MDOREALM on SPS_A to add a message to Peer device 4 when routing it
origin realm message duplication with to Peer device 3.
Reference index set to 0, Origin realm set to
Peer device 1, Next rule set to
name set to rst.
Remarks None.
T24-0105 Origin-Host-based Message Duplication
Origin-Host carried in the messages.
set to MASTER_SLAVE(MASTER SLAVE), 3. The origin host message duplication is

message duplication entrance with Message 18. The message tracing results show that
duplication entrance name set to ent, Next SPS_A can route the message to Peer
rule set to MDOH(Origin Host Message device 3 and receive responses from Peer
Duplication), and Next reference index set to device 3. SPS_A can also duplicate the
0. message to Peer device 4 when routing it
3. Run ADD MDOHOST on SPS_A to add a origin to Peer device 3.
host message duplication with Reference
index set to 0, Origin host set to Peer device
1, Next rule set to MDEXIT(Message
Duplication Exit), and Next reference index
set to 1.
name set to rst.
Remarks None.
T24-0106 Command Code-based Message Duplication
command code carried in the messages.
set to MASTER_SLAVE(MASTER SLAVE), 3. The command code message duplication
rule set to MDCMDCODE(Command Code SPS_A can route the message to Peer
Message, and Next reference index set to 0. device 3 and receive responses from Peer
device 3. SPS_A can also duplicate the
3. Run ADD MDCMDCODE on SPS_A to add a message to Peer device 4 when routing it

origin host message duplication with to Peer device 3.

Reference index set to 0, Command code set
to ULR(Update-Location-Request), Next rule
set to MDEXIT(Message Duplication Exit),
and Next reference index set to 1.
name set to rst.
Remarks None.
T25 MAP-Diamter Translation

T25-01 S6a/Gr Interface Conversion
T25-0101 AIR and AIA Message Conversion
Objective Verify that the SPS can perform conversion on AIR and AIA messages.
Prerequisites  The license that supports MAP-Diamter translation has been activated on
the SPS. In addition, the software parameter (P220) for the MAP-Diamter
translation function has been enabled.
 All Diameter links and SS7 links are in the activated state.
 The MAP node has been configured and referenced in the Diameter Route
Result table by running the following commands:
ADD MAPNODE: NODENAME="MAPNODE", GT=GT4, AF="860755",
MAPVERACMETH=Configuration, ISHLR=NO;
ADD RTRESULT: RTRSLTNAME="ATP_TEST", PROTOCOLTYPE=MAP,
NODENAME="MAPNODE";
 The GT mapping data has been configured by running the following
command:
ADD DAGTMAPPING: MAPPINGNAME="DAGTMAPPING",
HN="test.huawei.com", RN="huawei.com", GT=GT4, AF="860756";
 The GT translation data to the HLR has been configured by running the
following command:
ADD SCCPGT: GTNM="SCCPGT", NI=IM, RT=STP1, WM=SGWM,
DT="V_HLR1_MAP1_NAT24", GT=GT4, CP=ISDN, AI=INTER,
AF="860755";
Here, the NI, RT, WM, and DT parameters must be set based on site
requirements.

1. Use the MME to send an AIR message to the 1. The SPS converts the AIR message to a
SPS. The message carries the Requested- SendAuthenticationInfoArg message and
EUTRAN-Authentication-Inf and User-Name sends it to the HLR. The
AVPs, but not the Requested-UTRAN-GERAN- SendAuthenticationInfoArg messqage
Authentication-Info AVP. The Requested- carries the number-Of-Requested-Vectors,
EUTRAN-Authentication-Inf AVP contains the Immediate-Response-Preferred, and Re-
Number-Of-Requested-Vectors, Immediate- synchronization-Info IEs. The values of
Response-Preferred, and Re-synchronization- these IEs are extracted from the
Info sub-AVPs. Requested-EUTRAN-Authentication-Info
2. Have the HLR return a AVP, and requestingNodeType is set to
SendAuthenticationInfoRes message to the MME. The SendAuthenticationInfoArg
SPS. The message carries message does not carriy the
AuthenticationSetList.QuintupletList.Authenticat numberOfRequestedAdditional-Vectors
ionQuintuplet sub-AVP, with rand, sres, ck, ik, and additionalVectorsAreForEPS IEs.
and autn included. 2. The SPS converts the
SendAuthenticationInfoRes message to an
AIA message and sends it to the MME.
The AIA message carries Result-
Code=DIAMETER_SUCCESS and
authentication-info. In the authentication-
info IE, e-utran-vector indluces rand, sres,
autn, and kasme.
Remarks None.
T25-0102 ULR and ULA Message Conversion (1)
Objective Verify that the SPS can perform conversion on ULR and ULA messages.
NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.

1. Have the MME send a ULR message to the 3. The SPS converts the ULR message to an
SPS. The message carries User-Name=A, UpdateGprsLocationArg message and
SGSN-Number=B, and other mandatory AVPs. sends it to the HLR. The
2. Have the HLR return an UpdateGprsLocationArg carries imsi=A,
UpdateGprsLocationRes message to the SPS. sgsn-Number=B, and sgsn-Address.
The message carries the hlr-Number IE. 4. The SPS converts the
UpdateGprsLocationRes message to a
ULA message and sends it to the MME.
The UpdateGprsLocationRes message
carries Result-
Code=DIAMETER_SUCCESS and Auth-
Session-State=NO_STATE_MAINTAINED
(0).
Remarks None.
T25-0103 ULR and ULA Message Conversion (2)
Objective Verify that the SPS can perform conversion on ULR and ULA messages.
NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.
1. Have the MME send a ULR message to the 4. The SPS converts the ULR message to an
SPS. The message carries User-Name=A, UpdateGprsLocationArg message and
SGSN-Number=B, and other mandatory AVPs. sends it to the HLR. The
2. Have the HLR send an UpdateGprsLocationArg carries imsi=A,
InsertSubscriberDataArg message to the SPS. sgsn-Number=B, and sgsn-Address.
3. Have the HLR return an 5. The SPS sends an

InsertSubscriberDataRes message to the

UpdateGprsLocationRes message to the SPS. HLR without carrying any MAP IE.
The message carries the hlr-Number IE. 6. The SPS converts the
UpdateGprsLocationRes and
InsertSubscriberDataArg messages to a
ULA message and sends it to the MME.
The UpdateGprsLocationRes message
carries Result-
Code=DIAMETER_SUCCESS and Auth-
Session-State=NO_STATE_MAINTAINED
(0).
Remarks None.
T25-0104 PUR and PUA Message Conversion
Objective Verify that the SPS can perform conversion on PUR and PUA messages.
NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.
1. Have the MME send a PUR message to the 1. The SPS converts the PUR message to a
SPS. The message carries the optional AVPs PurgeMS message and sends it to the
AVP PUR-Flags, Supported-Features, and HLR. The UpdateGprsLocationArg carries
EPS-Location-Information, and other only the sgsn-Number IE whose value is
mandatory AVPs. the GT code queried based on the host
2. Have the HLR return a PurgeMSRes message name of the MME (that is, the number
to the SPS. The message carries freezeP- allocated by the SPS to the MME).
TMSI, but not freezeM-TMSI. 2. The SPS converts the PurgeMSRes
message to a PUA message and sends it
to the MME. In the PUA message, the pua-
flags AVP is set to 2.

Remarks None.
T25-0105 DSR and DSA Message Conversion
Objective Verify that the SPS can perform conversion on DSR and DSA messages.
NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.
1. Have the HLR send a 3. The SPS converts the PUR message to a
DeleteSubscriberDataArg message to the SPS. PurgeMS message and sends it to the
The message carries only imsi=A, and the HLR. The UpdateGprsLocationArg carries
called GT meets the conversion condition. only the sgsn-Number IE whose value is
2. Have the MME send a DSA message to the the GT code queried based on the host
SPS. The message carries freezeP-TMSI, but name of the MME (that is, the number
not freezeM-TMSI. allocated by the SPS to the MME).
4. The SPS converts the PurgeMSRes
message to a PUA message and sends it
to the MME. In the PUA message, the pua-
flags AVP is set to 2.
Remarks None.
T25-0106 NOR Message Conversion
Objective Verify that the SPS can perform conversion on NOR messages.

NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.
1. Have the MME send an NOR message to the 1. The SPS converts the NOR message to an
SPS. The message carries the NOR-FLAGS UpdateGprsLocationArg message and
AVP, and BIT0 is set to 0. sends it to the HLR. The
2. Have the HLR return an UpdateGprsLocationArg carries the isr-
UpdateGprsLocationRes message to the SPS. Information IE, in which cancelSGSN is set
to 1.
2. The SPS does not convert the
UpdateGprsLocationRes message, but
directly releases the resources.
Remarks None.
T25-0107 CLR and CLA Message Conversion
Objective Verify that the SPS can perform conversion on CLR and CLA messages.
NODENAME="MAPNODE";

command:
following command:
AF="860755";
requirements.
1. Have the HLR send a CancelLocationArg 1. The SPS converts the CancelLocationArg
message to the SPS. The message carries the message to a CLR message and sends it
CancellationType IE whose value is to the HLR. The CLR message carries
subscriptionWithdraw, and the called GT meets Cancellation-
the conversion condition. Type=SUBSCRIPTION_WITHDRAWAL.
2. Have the MME send a CLA message to the 2. The SPS converts the CLA message to the
SPS. The message carries result- CancelLocationRes message without
code=DIAMETER_SUCCESS. carrying any MAP IE to the HLR.
Remarks None.
T25-0108 IDR and IDA Message Conversion
Objective Verify that the SPS can perform conversion on IDR and IDA messages.
NODENAME="MAPNODE";
command:
following command:
AF="860755";
requirements.

1. Have the HLR send an 1. The SPS converts the CancelLocationArg

InsertSubscriberDataArg message to the SPS. message to a CLR message and sends it
The message carries to the HLR. The CLR message carries
SubscriberData.TeleserviceList.Ext- Cancellation-
TeleserviceCode, and the called GT meets the Type=SUBSCRIPTION_WITHDRAWAL.
conversion condition. 2. The SPS converts the IDA message to the
2. Have the MME send an IDA message to the InsertSubscriberDataRes message and
SPS. The message carries result- sends it to the HLR. In the
code=DIAMETER_SUCCESS. InsertSubscriberDataRes message, the
value of TeleserviceList is the same as that
of InsertSubscriberDataArg.
Remarks None.

SPS V300R007C10 Part II Operation Guide (Special)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPS V300R007C10 Part II Operation Guide (Special)

Uploaded by

Copyright:

Available Formats

SPS V300R007C10 Operation Guide

Part II Operation Guide...............................................................................................................1

Part II Operation Guide

T13-0101 Deleting the Route-Record Field

Network Diagram See Figure 1 in Part III Appendix.

Procedure Expected Results

Internal Number T14-0101

All rights reserved Page 1 , Total 61

Network Diagram See Figure 1 in Part III Appendix.

Procedure Expected Results

Internal Number T14-0201

T14 Session Binding

T14-0101 Setting Up Session Binding

All rights reserved Page 2 , Total 61

or session from different NEs to the same peer.

Network Diagram See Figure 2 in Part III Appendix.

Procedure Expected Result

All rights reserved Page 3 , Total 61

5. Use Peer device 2 to send an AAR message to

Internal Number T15-0101

T14-02 PCRF Session Binding Removal

T14-0201 Removing Session Binding

Objective Verify that the SPS allows session binding to be removed.

Network Diagram See Figure 2 in Part III Appendix.

Procedure Expected Result

All rights reserved Page 4 , Total 61

Internal Number T15-0201

T15 Signaling Adaptation

T15-0101 Adapting Signaling Based on the Combination of an Application ID, Source

Network Diagram See Figure 2 in Part III Appendix.

Procedure Expected Result

All rights reserved Page 5 , Total 61

 Set Mediation action name to A. 2. The modification is successful.

All rights reserved Page 6 , Total 61

Internal Number T16-0101

T15-02 Signaling Adaptation Based on the Combination of an Application

T15-0201 Adapting Signaling Based on the Combination of an Application ID, Source

Network Diagram See Figure 2 in Part III Appendix.

Procedure Expected Result

1. Run ADD MEDACTION on SPS_A, with the 1. Execution of ADD MEDACTION is

 Set Layer 1 AVP code to 65535. 3. Execution of MOD DMPEER is successful.

All rights reserved Page 7 , Total 61

 Set Command code to 316.

Internal Number T16-0201

T16-0101 Supporting IPv6 on TCP Links

Objective Verify that the SPS supports IPv6 on TCP links.

Network Diagram See Figure 1 in Part III Appendix.

Prerequisites  The DA IP address has been set to an IPv6 address on SPS_A.

Procedure Expected Result

All rights reserved Page 8 , Total 61

Internal Number T17-0101

T16-02 Support for IPv6 on STCP Links

T16-0201 Support for IPv6 on STCP Links

Objective Verify that the SPS supports IPv6 on STCP links.

Network Diagram See Figure 1 in Part III Appendix.

Prerequisites  The DA IP address has been set to an IPv6 address on SPS_A.

Procedure Expected Result

Internal Number T17-0201

T17 SS7 Signaling Management

T17-0101 Inhibiting/Uninhibiting MTP Links

Network Diagram See Figure 1 in Part III Appendix.

Prerequisites  SPS_A is running properly.

All rights reserved Page 9 , Total 61

 The communication between the host and the BAM is normal.