INAP NP Service and 800

Service of the UGC3200

www.huawei.com

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Foreword
 This document describes how to implement the NP service
and the 800 service on the UGC3200 based on the application
scenarios, implementation principle, and service configuration
of the INAP NP service.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Training Objectives
 Upon completion of this course, you will be able to:

 Understand the basic concepts of the INAP NP service of the UGC3200.

 Understand the implementation principle of the INAP NP service of the UGC3200.

 Understand the key configuration of the INAP NP service of the UGC3200.

 Understand the basic concepts of the 800 service of the UGC3200.

 Understand the implementation principle of the 800 service of the UGC3200.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Contents
1. Basic Concepts of the INAP NP Service

2. Application Scenarios of the INAP NP Service

3. Implementation Principle of the INAP NP Service

4. Service Configuration of the INAP NP Service

5. Service Configuration Examples of the INAP NP Service

6. Basic Concepts of the 800 Service

7. Implementation Principle of the 800 Service

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Basic Concepts of the INAP NP Service
Definition:
NP: The number portability (NP) service allows a subscriber to retain the existing directory number after subscribing
to another network within a country or region. All services of the subscriber are provided by the new subscription
network and not affected by the original subscription network.
Related concepts:
 NP: Number Portability
The NP service allows a subscriber to retain the existing directory number after subscribing to another network
within a country or region. All services of the subscriber are provided by the new subscription network and not
affected by the original subscription network.
 CIC: Carrier Identification Code
It is a parameter used for carrier preselection. The UGC3200 selects a carrier for call routing based on this
parameter.
 NRN: Network Routing Number
The NRN returned from the NP database (NPDB) to the UGC3200.
 PDIC: Point of Inter-Connection
The PDIC is used for call connection when two network entities (NEs) are not directly connected.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Application Scenarios of the INAP NP Service
The service is applicable to the public switched telephone network (PSTN) and IP Multimedia
Subsystem (IMS) networks where the UGC3200 functions as a media gateway control function
(MGCF). With the NP service, subscribers can retain the existing directory number after
subscribing to a new network. During service implementation, the UGC3200 queries the NPDB by
using the Intelligent Network Application Part (INAP) protocol. The application scenarios are as
follows:

1.In a call originated from the IMS, the MGCF queries the NPDB and processes the call based on
the query results.

2.In a call originated from the PSTN, if the called number contains the CIC, the MGCF strips the
CIC from the called number and routes the call to the actual home network of the called party.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Implementation Principle of the INAP NP Service
After receiving a call routed from the IMS to the PSTN, the MGCF queries the MNP Service Prefix table based on
the CIC (if contained) and the called number to determine whether to trigger the NP service. If the NP service
needs to be triggered, the MGCF queries the NPDB by using the INAP protocol.
If the NRN contained in the CONNECT message returned by the NPDB is different from the called number
contained in the IDP message used to query the NPDB, the MGCF determines that the called number has been
ported. The MGCF then directly routes the call out based on the CIC (if contained) and the NRN. The format of the
called number for routing is "CIC (if contained) + NRN + D (special separator) + called number."
When the NRN contained in the CONNECT message returned by the NPDB is the same as the called number
contained in the IDP message used to query the NDPB, the NPDB returns a CONTINUE message to the MGCF,
or the MGCF fails to query or does not query the NPDB, the MGCF determines that the called number has not
been ported. The MGCF then queries the local database for a PDIC number based on the CIC (if contained), the
called number (in national number format), and the calling number (in national number format).

1.If the PDIC number is obtained, the MGCF routes the call based on the PDIC number. The format of the called
number for routing is "PDIC + CIC (if contained) + called number."

2.If the PDIC number is not obtained, the MGCF routes the call based on the CIC (if contained) and the called
number. The format of the called number for routing is "CIC (if contained) + called number."

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Implementation Principle of the INAP NP Service

The service procedure is as follows:

1. After receiving an incoming call without the CIC from the IMS, the MGCF queries the NPDB
based on the called number and the called number has been ported.

The service procedure is as follows:

P1: After receiving an INIVITE request from the IMS, the MGCF queries the MNP Service Prefix table to
determine whether to query the NPDB. If such a query is required, the MGCF sends an IDP
message to the NPDB. The calling number and called number in the IDP message are normalized.
P2: The MGCF receives a CONNECT message from the NPDB and determines whether the called
number has been ported. If the NRN contained in the CONNECT message is different from the
called number contained in the IDP message, the MGCF determines that the called number has
been ported and sends an IAM message to the terminating network based on the NRN. The format
of the called number contained in the IAM message is "NRN + D (a special separator) + called
number (in national number format)."

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Implementation Principle of the INAP NP Service
2. After receiving an incoming call without the CIC from the IMS, the MGCF determines
that the called number has not been ported.

The service procedure is as follows:

P1: After receiving an INIVITE request from the IMS, the MGCF queries the MNP Service Prefix table based on the
called number to determine whether to query the NPDB. If such a query is required, the MGCF sends an IDP
message to the NPDB. The calling number and called number in the IDP message are normalized.

The MGCF continues the processing based on the results obtained from the NPDB.
 L1: After receiving the RELEASECALL message from the NPDB, the MGCF releases the call.
 L2: After receiving the CONTINUE message from the NPDB, the MGCF determines that the called number
has not been ported and continues to connect the call.
 L3: After receiving the CONNECT message from the NPDB, the MGCF detects that the NRN contained in the
CONNECT message is the same as the called number contained in the IDP message and determines that the
called number has not been ported. Then the MGCF continues to route the call.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Implementation Principle of the INAP NP Service
3. After receiving an incoming call from the PSTN, the MGCF directly routes the call to the IMS.

The service procedure is as follows:

P1: After receiving an IAM message from the PSTN, the MGCF queries the CIC Information table based on the
called number and determines whether the called number contains the CIC. If the called number contains
the CIC, the MGCF strips the CIC from the called number and considers the called number without the CIC
as the new called number. Then, the MGCF sends an INVITE request to the IMS based on the CIC and
the called number. The INVITE request contains the called number in international number format and the
CIC (if contained).

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Implementation Principle of the INAP NP Service
4. After receiving an incoming call with the CIC from the IMS, the MGCF directly routes the call to the
IMS.

The service procedure is as follows:

P1: After receiving an INVITE request containing the CIC from the IMS, the MGCF queries the MNP Service Prefix Table based on the CIC and called
number to determine whether to query the NPDB. If such a query is required, the MGCF sends an IDP message to the NPDB.

P2: The MGCF receives a CONNECT message from the NPDB and determines whether the called number has been ported.
 If the NRN contained in the CONNECT message is different from the called number contained in the IDP message, the MGCF determines that
the called number has been ported and routes the call based on the CIC and NRN. The called number in the IMA message is in "CIC + NRN +
D (a special parameter) + called number" format.
 If the NRN contained in the CONNECT message is the same as the called number contained in the IDP message, the MGCF determines that
the called number has not been ported. The MGCF then queries the local database for the PDIC number based on the CIC and the called
number (in national number format).

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Service Configuration of the INAP NP Service
List of commands
1. The ADD MNP command is used to configure the NP service. To configure the INAP NP service, MNP
processing type is set to FIXED IN based NP query and service key is selected. Otherwise, the service
key is invisible.

2. The ADD IDPNPRO command is used to configure whether to change the number contained in the IDP
message.

3. The ADD TDPAC command is used to configure the TDP access code.
4. The ADD TDPCFG command is used to configure the TDO configuration information.
5. The ADD SCPINFO command is used to configure the SCP address information.
6. The ADD SCPCFG command is used to add the SCP configuration information.
7. The ADD SCPPARA command is used to add the SCP parameter information.
8. The ADD SSPINFO command is used to configure the SSP physical address.
9. The ADD SSNSRV command is used to add a service type of the SSN.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Service Configuration of the INAP NP Service
Task examples:
/*Configure the INAP NP service.*/
ADD MNP: CSN="MVNO", CALLFROM=ISUP, CLDPFX=K'B0584, MINDNLEN=5, MAXDNLEN=32, MNPPFT=UNKNOWN, MNPPRT=FIXINBASED,
SRVKEY=1;
/*Configure the called number analysis.*/
ADD CNACLD: P=10, PFX=K'B0584, CSA=LCT, RSNAME="msx_hw_isup", MINL=4, MAXL=32;
/*Configure whether to change the number and whether to change the number contained in the IDP message.*/
ADD DNC: DCN="RMV_B058", DCT=TYPE6, DCL=4;
ADD IDPNPRO: CNTYP=NGN, SRVKEY=1, INTRGTP=ALL, NUMT=CLD, NUMPFX=K'B0584, NUMADDRTYP=ALL, MAXLEN=32,
NCNAME="RMV_B058";
/*Add SSP configuration. The IDP message contains only the caller, caller and service key.*/
ADD SSPCFG: SSPINDEX="SSPCFG", ITAEGET=IDP, IMASK=CEDNUM-1&CINGNUM-1;
/*Add the TDP access code.*/
ADD TDPAC: ACNAME="FSCP", ACODE=K'40141225;
/*Add the TDP configuration.*/
ADD TDPCFG: NETTYPE=NGN, DPNO=DP3, CODE="FSCP", SKEY=0, CSRCWLCDF=NO, CSRCNAME="MVNO";
/*Add the SCP address information.*/
ADD SCPINFO: SCP="FSCP", INVER=INAP_RU, SSNF=YES, RT=DPC, DPC="111999", SSN=ss251, SCFID="333";
/*Add an SCP configuration table.*/
ADD SCPCFG: SKEY=0, NETTYPE=NGN, ISSPCFG="SSPCFG", SNAME=PPS, SCPADDRNAME0="FSCP";
/*Add the SSP physical address.*/
ADD SSPINFO: SCP="FSCP", DPCF=YES, SSNF=YES, RT=DPC, OPC="1199", SSN=ss250;
/*Add the service type of the SCCP SSN.*/
ADD SSNSRV: SSN=SSN251, SVT=INAP;

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Basic Concepts of the 800 Service
Definition:

An IMS subscriber dials the 800 number. Then the CSCF routes the
call to the MGCF based on the IM-SSF mode and the MGCF
triggers the 800 service based on the service key configured by the
CSCF by using the INAP protocol. The MGCF makes calls to the
CSCF in the outgoing INVITE message by replacing Request URI
with the query number according to the query results.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Implementation Principle of the 800 Service
The service flow is as follows:
IMS IM-SSF SG7000 CSCF

INVITE

Intial_dp

CONNECT

INVITE

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Implementation Principle of the 800 Service
The implementation principle of the 800 service is described as follows:
1. The IM-SSF determines whether to trigger the IN service on whether to trigger the IN based on the parameter information about the Route header
field of the incoming INVITE message.
The format of the Route header is as follows:
Route: <sip:im-ssf@huawei.com:5060;lr;orig;scpaddr=G-xxxxxx;servicekey=xx;ssf=xxxxxxx>;sip:10.8.2.53:10228;lr;ORGDLGID=6d-1.
The first route of the Route header field includes domain name, port number, and caller process (orig) of the IM-SSF, IN type, SCP address (scpaddr),
service key (servicekey) information, and the IMSI.
2. The IM-SSF triggers the IN service to the SG7000, and carries related information about the caller and the callee, IN service key and SCP address.
3. The SG7000 determines the service as an INAP800 service based on the IN service key, and returns a CONNECT message to the IM-SSF. The
message contains the redirecting number.
4. The IM-SSF routes the call to the CSCF by replacing the redirecting number in the CONNECT message with the Request URI number.

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Thank you
www.huawei.com

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.