01 1705en08al 03 number portability

8/20/2019 01 1705en08al 03 Number Portability

1/40

Number Portability Extensions (SF000607) Siemens

MN1705EN08AL-031

Contents

1 Number Portability < SR8.0 3

1.1 Ported Subscribers 4

1.2 Database Query for Ported Subscribers 6

1.3 Ported Number Ranges 81.4 Query Database 10

2 Number Portability Extensions 13

2.1 EWSD Switch as Central Database 14

2.2 Support of SMS-MT 16

2.3 Support of CCBS 18

2.4 INAP Query for Circuit Switched Calls 20

2.5 GTT Handling in the MSC 22

2.6 MML Commands 28

2.7 Database Examples 322.8 Upgrade Relevance 40

Number Portability Extensions

(SF000607)


2/40

Siemens Number Portability Extensions (SF000607)

MN1705EN08AL-032


3/40


MN1705EN08AL-033

1 Number Portability < SR8.0


4/40


MN1705EN08AL-034

1.1 Ported Subscribers

“Number Portability” allows a subscriber to change the network provider or thelocation within one network without changing the number (a GSM subscriber keepsthe MSISDN, the IMSI will be changed). The arising possibilities in a GSM networkare the following:

A mobile subscriber is ported in and stays mobile.

A wire line or PABX subscriber is ported in and becomes mobile.

A wire line or PABX subscriber is ported in from another provider or moves toanother CSC and stays fixed. This is only possible if the subscriber stays in thesame LAC area.

An own subscriber (mobile, wire line or PABX) is ported out. In this chapter nofurther distinction will be made between PABX and wired subscribers. For reasons

of simplicity both are referred to as fixed subscribers.


5/40


MN1705EN08AL-035

SIEMENS SIEMENS

HLR

SIEMENS SIEMENS

MSC (CSC)

PSTN exchange

SIEMENS SIEMENS

MSC (CSC)

own PLMN

SIEMENS SIEMENS

HLR

ported in

MSUB

ported in

“wired”->MSUB

ported out

MSUB

ported in

“wired”-> “wired”

ported out

“wired”-> “wired”

ported out

“mobile”-> “wired”

Fig. 1 Ported Numbers of Different Types of Subscribers


6/40


MN1705EN08AL-036

1.2 Database Query for Ported Subscribers

In order to set up a call to a ported out subscriber, the current network of thissubscriber has to be determined. For ported in subscribers the HLR or in the case of a fixed subscriber, the MSC of the subscriber has to be identified. The appropriateidentifications can be determined in three different ways:

Query on digit processing (QoD): If a call to a ported subscriber, digit translationtriggers a database query. As a result of this query, the current network of a portedout subscriber or the HLR or MSC of a ported in subscriber may be addressed andthe subscriber reached.Main application: ported in subscribers and ported out wired subscribers

Query on HLR release (QoHR):This method is only applicable for ported out

mobile subscribers. If an MTC, interrogation of the HLR is performed as usual.Only if the HLR answers with “unknown subscriber”, a database query is carriedout to determine the current network of the subscriber.Main application: ported-out mobile subscribers.

Forwarding method: This method is only applicable for ported out fixedsubscribers: When a subscriber is called, this call is first set up to his/her former home network node (CSC). There his/her directory number is modified and digittranslation is repeated with the modified number. No database query is necessaryfor this method.


7/40


MN1705EN08AL-037

SIEMENS SIEMENS

MSC/VLR

Other network

CODE

?

list of ported

subscriber

ported in

incoming

call

Other

network

ported outquery ondigits (QOD)

SIEMENS SIEMENS

MSC/VLR

Other network

incomingcall

ported out

Other

network

SIEMENS SIEMENS

HLR

CODE?

i n t e r r o g

a t i o n

list of ported

subscriber query on

HLR release

(QOHLR)

u n k n o w

n

s u b s c r i b e

r

ported in

Fig. 2 Query on Digits and Query on HLR Release


8/40


9/40


MN1705EN08AL-039

CODE

number portability

database:

list of ported subscribers

Range of possibly ported

subscribers:

• ported in mobile subscribers

• ported in wired subscribers

• ported out wired subscribers

marked as:

• ported number range

• query on digits

Range of possibly ported

subscribers:• ported out mobile subscribers

marked as:

• query on HLR release

• ported number range

S IE ME NS S IE ME NS

HLRinterrogation

+

digit translation

unknown

subscriber

Data base

queryFurther digit processing:

• e.g. interrogation

• e.g.call to CSC MSC

• e.g. call to foreign network

Further digit processing:

• e.g. interrogation

• e.g.call to CSC MSC

• e.g. call to foreign network

Digit

translation

new digit processing

data

ported in

ported in

ported out

Other

network


MSC/

CSC

A

B

Fig. 3 Ported Number Ranges

CR CPT: CODE=,

DEST=,

TRATYP=MOBINTER,

PNR=Y, QOHR=Y,..........;

CR CPT: CODE=< identifying digits of ported in mobile subscribers>, DEST=

or

CODE=< identifying digits of ported in wired subscribers>,

DEST=

or

CODE=< identifying digits of ported out wired subscribers>,

DEST= ,

PNR=Y[, QOHR=N],..........;

B

A

Fig. 4


10/40


MN1705EN08AL-0310

1.4 Query Database

The database for number portability can be realized as a local or as a central database:

Local database implemented in the MSC

Ported in subscribers: In every MSC of the network all subscribers ported into thenetwork have to be entered.

Ported out subscribers: In every MSC of the network all subscribers ported out of the network have to be entered.

As the capacity of a local database is limited and only a certain number of subscribers can be administered, a local database is recommended if just a few

ported subscribers are existing and no IN functionality has been introduced yet. Central database implemented on IN basis

A central database is addressed via a service switching point (SSP= MSC with INfunctions) and a service control point/CAMEL service environment (SCP/CSE).The entire PLMN can be served by only one central data base or by severaldatabases (e.g. one for all ported out and one for all ported in subscribers). Acentral database is recommended if a large number of ported subscribers shall beadministered and the IN functionality is already introduced. In both databases, thedirectory numbers have to be entered with national prefix and LAC or NDC:.

In either case the local database or the access to the number portability data base inthe SCP/CSE is realized by subscriber dependent digit processing and featurecontrol (SDDPFC). In case of the code point was specified as a number portabilityrange the criterion CALLTYPE=NPP (number portability) is matched.

To program a local database all ported in and all ported out subscribers have to beprogrammed with help of the parameter CODE. The new network, the new HLR or the new MSC/CSC are identified by identification digits, that later on can beevaluated by the digit translator. With help of the parameter DICON this identificationcan be inserted in to the dialed or received digit information.

To program the access to a centralized data base, the parameter CODE contains thestarting digits of a number portability range. In the SDDPFC action the link to an INtrigger has to be specified with the parameter: IN. In this case the SCP/CSE isresponsible to check its database for ported subscribers and to provide a new routinginformation inclusive the corresponding identification digits.


11/40


MN1705EN08AL-0311

A

B

Number portability

Database:List of ported Subscribers

from digit translation

•Query on digits

•Query on HLR release

B

IN SCP/

CSE

SDDPFCLocal database:

•Criterion:

CALLTYPE=NPP

CODE= 1st ported subscriber

............ CALLTYPE=NPP

CODE= nth ported subscriber

•Action:

DICON=X+identification code

Central database:•Criterion:

CALLTYPE=NPP

•Action:

IN= -

A

Fig. 5 Local and central query database

CR DPFCACT: ACTION=LOCQUERn,

DICON=X+,

or

DICON=X+,

or

DICON=X+;

CR DPFCDAT: FEAT=NP1,

CODE=,

CALLTYPE=NPP, ACTION= LOCQUERn;

CR DPFCDAT: FEAT=NPn,

CODE=,

CALLTYPE=NPP, ACTION= LOCQUERn;

CR INTRIG: PRID=,

GENPROP=EODREQ&PROP11,...;

CR DPFCACT: ACTION=INQUER, IN=0-;

CR DPFCDAT: FEAT=NP,

CODE=,

CALLTYPE=NPP, ACTION= INQUER;

B

A

Fig. 6 MML Commands for local and central query database


12/40


MN1705EN08AL-0312


13/40


MN1705EN08AL-0313

2 Number Portabil ity Extensions


14/40


15/40


MN1705EN08AL-0315

SIEMENS SIEMENS

EWSD V12

SIEMENS SIEMENS

MSC

SIEMENS SIEMENS

MSC

SIEMENS SIEMENS

MSC

SIEMENS SIEMENS

HLR

INAP

(subset of

SINAP5M)

INAP

(subset of

SINAP5M)

INAP

(subset of

SINAP5M)

SCCP

SCCPSCCP

SCCP

Fig. 7 EWSD Switch as a Central NP Database


16/40


MN1705EN08AL-0316

2.2 Support of SMS-MT

For an SMS-MT the MAP messageSEND_ROUTING_INFO_FOR_SHORT_MESSAGE is sent by the GMSC to the HLRwith the MSISDN in the SCCP called party address.

As the MSUB with this MSISDN can be ported out or in, it is necessary to query theNP database.

Therefore these messages must be routed to the EWSD V12 switch with the NPdatabase. The V12 switch checks whether the MSISDN is entered. The MSISDN isreplaced by the local roaming number (LRN) in the SCCP called party address.

The LRN in the GT consists of

Network identification code plus MSISDN or Switch identification code (HLRID if own network) plus MSISDN

The SCCP message is routed to the correct HLR which sends theSEND_ROUTING_INFO_FOR_SM_RESULT to the GMSC.

If the MSISDN is not entered in the NP database, then the subscriber is not portedand the SCCP message is routed to the HLR according to the HLRID in the MSISDN.


17/40


MN1705EN08AL-0317

SI EMENS SIEMENS

SIEMENS SIEMENS

PBX

SMS

Center

EWSD V12

Interworking

MSC

5

3

1

2

SMS transfer

SRI for SM

SRI for SM

GT=network...

SRI for SMresult

6forward SMS

ported MSUB

SIEMENS SIEMENS

EWSD V12

SIEMENS SIEMENS

SI EMENS SIEMENS

VLR/MSC

HLR

donor

network

foreign

network

recipient

network

SRI for SM

GT=HLR ID

4

SM

Fig. 8 International SMS


18/40


MN1705EN08AL-0318

2.3 Support of CCBS

CCBS was introduced in SR5.0. But the CCBS functionality is a Siemens proprietarysolution and not the GSM standardized method.

With the introduction of NP in SR7.0, CCBS is only supported under the followingconditions:

For each call only one query to the SCP NP database is allowed. This query musttake place in the originating MSC. This means that during this one query the networkidentification code of the ported subscriber's new network AND the switchidentification code within the ported subscriber's network have to be delivered.

Only QoD (query on digits) is supported.

All other restrictions for CCBS still apply.In SR8.0 with the use of the EWSD V12 server as central NP database theserestrictions no longer apply except the general CCBS restrictions (other network andsignaling must support CCBS,....).

Now there can be more queries to the SCP NP database for each call and QoHR isalso supported.

If a network does not use an EWSD V12 server as central the NP database then theSR7.0 functionality with all restrictions is also supported in SR8.0 (This means theSR7.0 solution stays in SR8.0, too).

The Siemens solution uses the translation type IEESS for all CCBS messages. TheGT database has to be administered in such a way that all CCBS messages have tobe routed through the EWSD V12 switch (except the messages where the networkidentification code is already included in the called party of the global title).The V12 switch checks if there is a new number entered in the NP database androutes the message to the according destination.


19/40


MN1705EN08AL-0319

SIEMENS SIEMENS

SIEMENS SIEMENS

EWSD V12

InterworkingMSC

8

4

2CCBS

request

CCBS request

start

monitoring

1

ported MSUB

SIEMENS SIEMENS

EWSD V12

SI EMENS SI EMENS

SIEMENS SIEMENS

VLR/MSC

donor

network

recipient

network

5

ISUP releasebusy CCBS possible

3

CCBS request

GT=network...

TTID = IEESS

CCBS request

GT=HLR ID...TTID = IEESS

HLR

start

monitoring

result

6

7

CCBS

acknowledge

CCBS

acknowledge

9

Fig. 9 CCBS Request Routing


20/40


MN1705EN08AL-0320

2.4 INAP Query for Circuit Switched Calls

Instead of using the SCP as a number portability database or the MSC internalnumber portability database (via SDDPFC) as it was realized in SR7.0, the EWSDswitch can be used as a number portability database. The EWSD switch replaces inthis case just the SCF (service control function) of the SCP. The interface betweenthe gateway MSC and the EWSD switch is covered by a subset of the SINAP5M (so-called SINAP6NP). The following messages are realized:

Initial DP (IDP)

Only the parameters serviceKey, CalledPartyNumber and eventTypeBCSM are used.(serviceKey and CalledPartyNumber must be available to ensure that an LNPdatabase query is possible)

Collect Information (CI) and RequestReportBCSMEvent (RRB):To initiate the collection of further digits if the available digits are not enough for theNP query.

EventReportBCSMEvent (ERB):To receive the former required digits from the SCP.

Continue (CUE)

This message is sent if the number is not ported (that means the number is not foundin the NP database)

Connect (CON)

To route the call with the LRN if the number is ported. (LRN contained in destinationrouting address)

ReleaseCall (RC)

The call should be released because there is no database entry found and QoHR isused.


21/40


MN1705EN08AL-0321

SIEMENS SIEMENS

gateway

MSC

1

2

MOC

SRI

6

ported MSUB

VLR/MSC

donor

network

recipient

network

ISUP IAM

(PrefixxxxMSISDN)

SRI result

unknown

subscriber

SIEMENS SIEMENS

EWSD V12

SIEMENS SIEMENS

HLR

SIEMENS SIEMENS

HLR

SIEMENS SIEMENS

gateway

MSC

3

IDP (MSISDN)

4 CONNECT (PrefixxxxMSISDN)

5

8SRI

SRI result

9

2 3and only for query on HLR release

INAP


query inrecipient

network

7

via

MSC/VLR

Fig. 10 INAP Query via V12 EWSD


22/40


MN1705EN08AL-0322

2.5 GTT Handling in the MSC

2.5.1 SMS Handling in the MSC

The short message transfer is received from the short message service center withthe standardized translation type UNKNOWN. In the inter-working MSC themessages to ported MSUBs and non-ported subscribers must be separated bydifferent global title code points, i.e. code points must be created with the portednumber ranges, which route the SEND_ROUTING_INFO_FOR_SM to the EWSDV12 SCF and code points with the non-ported number ranges which route theSEND_ROUTING_INFO_FOR_SM directly to the HLR.

2.5.2 MTC in the MSC with or without INAP Query

The send routing information of a normal mobile terminating call should not be routedto the EWSD V12 SCCP relay node automatically, but should be handled as inreleases


23/40


MN1705EN08AL-0323

SIEMENS SIEMENSSIEMENS SIEMENSPBX

SMS

Center EWSD V12

Interworking

MSC

1 2SMS Transfer

TTID=UNKNOWN

GT Translation

GTDIG= ported number range

TTID=UNKNOWN

=>SPC EWSD V12

GT Translation


TTID=UNKNOWN

=>SPC EWSD V12

SRI for SM

TTID=UNKNOWN

Fig. 11 SMS Handling

SIEMENS SIEMENS

SIEMENS SIEMENS HLR

Gateway

MSC

1

B-MSISDNSRI

TTID=UNKNOWN

project data:

new TTID for SRI

or

PREFIX for SRI

project data:

new TTID for SRI

or

PREFIX for SRI

digit translator

CODE=

query on HLR release

CODE=

query on digits

CODE=

unknown subscriber 5a

2a

2b

4a

2c

SDDPFC

IN Trigger

= SPC of SCP or EWSD SCF

or

SDDPFC internal NP database

6a

SIEMENS SIEMENS

EWSD V12

or

SCP

SDDPFC

IN trigger

=> SPC of SCP or EWSD SCF

or

SDDPFC internal NP database

6a

7a

3b

4b

INITIAL_DP

GT translation


TTID=new TTID

to be sent TTID=UNKNOWN

or

GTDIG=ported number range

TTID=UNKNOWN

=>SPC HLR

3a 3c

4c

Fig. 12 MTC Handling


24/40


MN1705EN08AL-0324

2.5.3 CCBS Handl ing in the MSC

For the call completion of a busy subscriber no special handling must be foreseen,because a special standardized translation type exists for CCBS. This means that inthe global title translation messages with the global title TTID=IEESS and the globaltitle digits of the ported number range have to be routed to the EWSD V11 SCF andmessages with global title digits outside of the ported number range are routed to theHLR directly.


25/40


MN1705EN08AL-0325

SIEMENS SIEMENSSIEMENS SIEMENS

EWSD V12Interworking

MSC

1 2CCBS Request

GT Translation


TTID=IEESS

=>SCP EWSD V12

GT Translation


TTID=IEESS

=>SCP EWSD V12

CCBS Request

TTID=IEESS

Fig. 13 CCBS Handling


26/40


MN1705EN08AL-0326

2.5.4 EWSD Version 12 SCCP Query

The EWSD V12 switch is used as a central NP database which has INAP and SCCPconnections to the MSCs.

Therefore every subscriber ported in or out has to be entered in the NP databasewith the LRN (local routing number).

If an NP query (Query via SCCP) must be performed for a called party addressduring global title translation, then the parameter PPN of the command CR GTCPTmust be set to yes (default is no).

The SCCP called party address must be in national format (only national format issupported). With this number a corresponding entry in the NP database is searchedfor.

There are two possible results:

The number is not found in the NP database. In this case the destination given bythe GT code point is used to route the SCCP message.

The number is found in the NP database, this means the number is ported. In thiscase the LNP database provides a new number. This new number is used with theTTID, NP and NA of the original global title to form a new GT. This new global titleis translated and the SCCP message is routed to the resulting destination.

TIPThe DICON in the original GT code point (with the parameter PPN=Y) is performed

only after the NP database query and no new number is returned!

If a new number is delivered by the NP database, then this DICON is not performed. A new GT translation will be started immediately.


27/40


MN1705EN08AL-0327

SIEMENS SIEMENS

EWSD V12

SIEMENS SIEMENS

MSC

SIEMENS SIEMENS

HLR of ported-

in MSUB

SRI:

GT=MSISDN

SCCP

GT digittreeGT digittree

number portability

database

MSISDN e.g. HLRID

number portability

database

MSISDN e.g. HLRID

GT CPT:GTDIG=ported

number range

„portability processing necessary“

GT DEST: GTDIG=MSISDN

SPC= e.g. SPC of HLR

GT CPT:GTDIG=e.g.HLRID

GT DEST:

GTDIG= e.g.HLRIDSPC= e.g. SPC of new HLR

GT CPT:GTDIG=ported

number range

„portability processing necessary“

GT DEST: GTDIG=MSISDN

SPC= e.g. SPC of HLR

GT CPT:GTDIG=e.g.HLRID

GT DEST:

GTDIG= e.g.HLRID

SPC= e.g. SPC of new HLR

not

ported

ported

SIEMENS SIEMENS

HLR of not

ported MSUB

Fig. 14 Query in the EWSD V12


28/40


MN1705EN08AL-0328

2.6 MML Commands

MSC MML

MPRDDAT

In the mobile project data the TTID or a global title prefix can be stored. Bothparameters are valid for the global title translation if a send routing information issupposed to be sent out. These data have to be set back in the global titletranslation, because they are not allowed to be sent out e.g. in a foreign network.With the aid of the MML command Display MPRDDAT these data can be displayed.

MSERVOPT

The feature number portability for CCBS has to be activated if it was sold for a certainproject. The activation can just be changed during installation. If the feature flag is notactive, the system behavior is the same as in releases before SR8.0 (see Support of CCBS)

If the feature flag is active then there is no restriction.

IN Trigger

If the INAP interface is used to retrieve number portability information from the EWSD

V12 an IN trigger profile must be set up. The IN trigger profile is created with theknown MML command CR INTRIG. The parameter ACNSEL must be set to 9 inorder to activate special protocol checks for the number portability query function.The parameter GENPROP has to be set to DPINH and PROP11. The service keycan be set to any value.


29/40


MN1705EN08AL-0329

Project data for Send Routing Information

DISP MPRDDAT; NPTTID {TTnn|UNKNOWN|....} NPPFX

Feature Activation

MOD MSERVOPT: FEAT=NPCCBS,STAT=ACT;

IN Trigger profile

CR INTRIG: PRID=, SSID=IN4, ACNSEL=9,SKEY=, GENPROP=DPINH&PROP11,RTGP=SPC, DPC=,NETIND=....,....;

Fig. 15 MML Commands in the MSC


30/40


31/40


MN1705EN08AL-0331

Ported number administration

ENTR LNPDAT: PORTDN= ,ROUTN=,STATUS={ACT|INACT};

Global title Translation with query

CR GTCPT: TRID=...., GTDIG= , PPN=Y,...;

Fig. 16 MML Commands in the EWSD V12


32/40


MN1705EN08AL-0332

2.7 Database Examples

SRI for SMS routing

On the opposite page an example of SMS routing via EWSD V12 switch is shown.The short message is received from the short message service center with the TTID= UNKNOWN. In the global title translation, the global title digits of possible portedsubscribers must be evaluated and the messages must be routed via the EWSD V12relay node. The format of the global title digits is changed to national format, i.e. thecountry code is cut with DICON and the nature of address is set to NATNO.


33/40


MN1705EN08AL-0333

/***********************************************************

/* MSC with international connection to a other PLMN or PSTN

/***********************************************************

/***********************************************************/* TRANSLATION TYPE

/***********************************************************

/* no new translation type (that means UNKNOWN is used)

/*

/***********************************************************

/* CREATION OF THE TRANSLATION GROUP NPDB01,

/* CONTAINING THE SPC OF THE EWSD V12 SWITCH

/***********************************************************

/*


34/40


35/40


MN1705EN08AL-0335

/***********************************************************

/* V12 switch with international connection to

/* a other PLMN or PSTN

/***********************************************************/*

//***********************************************************

//* CREATE GT-DIGIT-TREE

//***********************************************************

/*


36/40


MN1705EN08AL-0336

Normal SRI routing

As mentioned above, global title translation for the normal SEND_ROUTING_INFO

message (interrogation) is different from the global title translation in SR.7.0 or theglobal title translation without the feature "number portability extension". As theSEND_ROUTING_INFO of call related signaling should never have been routed viathe EWSD V12 node, the SEND_ROUTING_INFO and theSEND_ROUTING_INFO_FOR_SM have to be distinguished. Therefore theSEND_ROUTING_INFO gets a new project specific translation type (e.g. TT15). Onthe opposite page an example of the global title translation is shown. The reductionshown from international format to national format is not mandatory because it couldalso be done by the MINMAX parameter in the corresponding destination area for interrogation.

The most important thing for the database setup is that the global title digit tree iscreated with the project-dependent TTID. Depending on the project, further routingwith or without global title, the TTID, should be set back in CR GTCPT to thestandardized value UNKNOWN.


37/40


38/40


MN1705EN08AL-0338

CCBS request for own possible ported out MSUBs

The CCBS handling is almost the same as in SR7.0 because of CCBS uses its own

translation type IESS. The only necessary change if the global title digits are in theported number range, then the messages are routed to the EWSD V12 instead of tothe HLR.


39/40


MN1705EN08AL-0339

/***********************************************************

/* MSCs (this must be enter in every MSC)

/***********************************************************

/*/***********************************************************

/* CREATION OF THE TRANSLATION GROUP NPDB01,

/* CONTAINING THE SPC OF THE EWSD V12 SWITCH

/***********************************************************

/*


40/40


2.8 Upgrade Relevance

If a feature introduction is planned, then the TTID or the prefix for the normalSEND_ROUTING_INFO has to be changed in the project data and thecorresponding modification of the global title database for the new TTID or the prefixhas to be done during the APS change.

01 1705en08al 03 number portability

Documents