Number Portability Extensions (SF000607)

Siemens

Number Portability Extensions

(SF000607)

Contents
1
1.1
1.2
1.3
1.4
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8

Number Portability < SR8.0

Ported Subscribers
Database Query for Ported Subscribers
Ported Number Ranges
Query Database
Number Portability Extensions
EWSD Switch as Central Database
Support of SMS-MT
Support of CCBS
INAP Query for Circuit Switched Calls
GTT Handling in the MSC
MML Commands
Database Examples
Upgrade Relevance

MN1705EN08AL-03

3
4
6
8
10
13
14
16
18
20
22
28
32
40

Siemens

Number Portability Extensions (SF000607)

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

Number Portability < SR8.0

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

1.1

Ported Subscribers

Number Portability allows a subscriber to change the network provider or the

location within one network without changing the number (a GSM subscriber keeps
the MSISDN, the IMSI will be changed). The arising possibilities in a GSM network
are 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 to

another CSC and stays fixed. This is only possible if the subscriber stays in the
same LAC area.

An own subscriber (mobile, wire line or PABX) is ported out. In this chapter no
further distinction will be made between PABX and wired subscribers. For reasons
of simplicity both are referred to as fixed subscribers.

MN1705EN08AL-03

Number Portability Extensions (SF000607)

SIEMENS

Siemens

SIEMENS

MSC (CSC)
PSTN exchange

SIEMENS

SIEMENS

HLR

ported out
MSUB

ported in
wired->MSUB

ported in
MSUB

ported in
wired-> wired
SIEMENS

SIEMENS

MSC (CSC)

ported out
mobile-> wired

SIEMENS

SIEMENS

HLR

own PLMN
ported out
wired-> wired
Fig. 1 Ported Numbers of Different Types of Subscribers

MN1705EN08AL-03

Siemens

1.2

Number Portability Extensions (SF000607)

Database Query for Ported Subscribers

In order to set up a call to a ported out subscriber, the current network of this
subscriber 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 appropriate
identifications can be determined in three different ways:

Query on digit processing (QoD): If a call to a ported subscriber, digit translation

triggers a database query. As a result of this query, the current network of a ported
out subscriber or the HLR or MSC of a ported in subscriber may be addressed and
the 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 carried
out to determine the current network of the subscriber.
Main application: ported-out mobile subscribers.

Forwarding method: This method is only applicable for ported out fixed
subscribers: 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 digit
translation is repeated with the modified number. No database query is necessary
for this method.

MN1705EN08AL-03

Number Portability Extensions (SF000607)

incoming
call

SIEMENS

Siemens

ported in

SIEMENS

MSC/VLR

CODE
?
Other network

list of ported
subscriber

query on
digits (QOD)

ported in
Other
network

ported out

incoming
call
SIEMENS

SIEMENS

MSC/VLR

CODE
?

on
gati
o
r
r
inte
n
now
unk criber
s
sub

SIEMENS

SIEMENS

HLR

Other
network

Other network

ported out
query on
HLR release
(QOHLR)

list of ported
subscriber

Fig. 2 Query on Digits and Query on HLR Release

MN1705EN08AL-03

Siemens

1.3

Number Portability Extensions (SF000607)

Ported Number Ranges

Ported number ranges (PNR) are ranges within the numbering plan including
directory numbers of subscribers ported into or out of the network. In addition to
directory numbers of ported subscribers, a ported number range can also contain
directory numbers of non-ported subscribers. A code point within a ported number
range has to be entered with the parameter PNR=Y.
This initiates a database query which is performed
l

whenever this code point is reached, parameter QOHR=N (query on HLR release
= NO default) and PNR=Y.

after unsuccessful interrogation (HLR returns unknown subscriber). The code

point leading to interrogation has to be entered with QOHR=Y and PNR=Y.

Therefore the parameter PNR=Y defines that the directory number is contained
within a ported number range while the parameter QOHR specifies which method
should be used: query on digit processing (QoD) or query on HLR release (QoHR).
Ported number ranges must not contain numbers leading to IN services.

MN1705EN08AL-03

Number Portability Extensions (SF000607)

CODE

Siemens

digit translation
A Range of possibly ported
subscribers:
ported out mobile subscribers
marked as:
query on HLR release
ported number range
B 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
Data base
query

interrogation

SIEMENS

SIEMENS

HLR

unknown
subscriber

ported in

SIEMENS

SIEMENS

MSC/
CSC

Digit
translation

ported in

Further digit
digitprocessing:
processing:
new digit processing Further
e.g.
interrogation
e.g. interrogation
data
e.g.call
e.g.calltotoCSC
CSCMSC
MSC
e.g.
e.g.call
calltotoforeign
foreignnetwork
network

number portability
database:
list of ported subscribers

Other
network

ported out

Fig. 3 Ported Number Ranges

A CR CPT: CODE=<identifying digits of ported out mobile subscribers>,

DEST=<min-max destination>,
TRATYP=MOBINTER,
PNR=Y, QOHR=Y,..........;
B CR CPT: CODE=< identifying digits of ported in mobile subscribers>,
DEST= <original foreign network>
or
CODE=< identifying digits of ported in wired subscribers>,
DEST= <original foreign network>
or
CODE=< identifying digits of ported out wired subscribers>,
DEST= <original CSC MSC>,
PNR=Y[, QOHR=N],..........;
Fig. 4

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

1.4

Query Database

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

Local database implemented in the MSC

Ported in subscribers: In every MSC of the network all subscribers ported into the
network 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 IN
functions) and a service control point/CAMEL service environment (SCP/CSE).
The entire PLMN can be served by only one central data base or by several
databases (e.g. one for all ported out and one for all ported in subscribers). A
central database is recommended if a large number of ported subscribers shall be
administered and the IN functionality is already introduced. In both databases, the
directory numbers have to be entered with national prefix and LAC or NDC:
<natpref><LAC or NDC><subscriber number>.

In either case the local database or the access to the number portability data base in
the SCP/CSE is realized by subscriber dependent digit processing and feature
control (SDDPFC). In case of the code point was specified as a number portability
range the criterion CALLTYPE=NPP (number portability) is matched.
To program a local database all ported in and all ported out subscribers have to be
programmed 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 be
evaluated by the digit translator. With help of the parameter DICON this identification
can be inserted in to the dialed or received digit information.
To program the access to a centralized data base, the parameter CODE contains the
starting digits of a number portability range. In the SDDPFC action the link to an IN
trigger has to be specified with the parameter: IN. In this case the SCP/CSE is
responsible to check its database for ported subscribers and to provide a new routing
information inclusive the corresponding identification digits.

10

MN1705EN08AL-03

Number Portability Extensions (SF000607)

from digit translation

Query on digits
Query on HLR release

Siemens

Number portability
Database:
List of ported Subscribers

SDDPFC
A

Local database:
Criterion:
CALLTYPE=NPP
CODE= 1st ported subscriber
............
CALLTYPE=NPP
CODE= nth ported subscriber
Action:
DICON=X+identification code

IN SCP/
CSE

Central database:
Criterion:
CALLTYPE=NPP
Action:
IN= <length>-<trigger name>

Fig. 5 Local and central query database

CR DPFCACT: ACTION=LOCQUERn,
DICON=X+<HLR id of ported in MSUB>,
or
DICON=X+<CSC id of ported in wired subscriber>,
or
DICON=X+<net id of ported out subscriber>;
CR DPFCDAT: FEAT=NP1,
CODE=<identifying digits of ported subscriber 1>,
CALLTYPE=NPP, ACTION= LOCQUERn;
CR DPFCDAT: FEAT=NPn,
CODE=<identifying digits of ported subscriber n>,
CALLTYPE=NPP, ACTION= LOCQUERn;

CR INTRIG:

PRID=<IN trigger name>,

GENPROP=EODREQ&PROP11,...;
CR DPFCACT: ACTION=INQUER, IN=0-<IN trigger name>;
CR DPFCDAT: FEAT=NP,
CODE=<identifying digits of ported subscribers>,
CALLTYPE=NPP, ACTION= INQUER;

Fig. 6 MML Commands for local and central query database

MN1705EN08AL-03

11

Siemens

12

Number Portability Extensions (SF000607)

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

Number Portability Extensions

MN1705EN08AL-03

13

Siemens

2.1

Number Portability Extensions (SF000607)

EWSD Switch as Central Database

The number portability solution <SR8.0 just covers circuit switched connections.
Therefore some services like SMS or CCBS are not supported with number
portability.
If number portability (NP) becomes a mandatory feature in Europe and a lot of Asian
and other countries, required by the EU and national regulation institutions, these
restrictions are not acceptable.
With number portability extensions NP for non circuit switched connections is
supported, and SMS and CCBS are also supported for ported subscribers.
With EWSD switching system version 12 it is possible, to use the switch as central
number portability server. The server can be queried via INAP (reduced SINAP5
parameter set) and via SCCP (SCCP STP functionality).
To reduce the effort, we use this V12 switch as external central number portability
server, which can be queried via INAP by every MSC. The corresponding SCCP
message has to be routed to this switch.
Number portability for SCCP messages are only supported directly in the V12 switch.
That means that the affected SCCP messages must be routed through the V12
switch with global title translation in the switch.
In the V12 switch the NP database is queried and if there is a corresponding entry in
the database, the called party address of the global title is replaced. With the new GT
the SCCP message is routed to the new destination (e.g. HLR or other network). The
V12 switch is called signaling relay function (SRF).
The database in the V12 switch for NP of SCCP message and NP via INAP is the
same.

14

MN1705EN08AL-03

Number Portability Extensions (SF000607)

SIEMENS

Siemens

SIEMENS

EWSD V12
SCCP
SIEMENS

SIEMENS

HLR
INAP
(subset of
SINAP5M)

SCCP
SIEMENS

SCCP

SIEMENS

SCCP

MSC
INAP
(subset of
SINAP5M)

INAP
(subset of
SINAP5M)
SIEMENS

SIEMENS

SIEMENS

MSC

SIEMENS

MSC

Fig. 7 EWSD Switch as a Central NP Database

MN1705EN08AL-03

15

Number Portability Extensions (SF000607)

Siemens

2.2

Support of SMS-MT

For an SMS-MT the MAP message

SEND_ROUTING_INFO_FOR_SHORT_MESSAGE is sent by the GMSC to the HLR
with 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 the
NP database.
Therefore these messages must be routed to the EWSD V12 switch with the NP
database. The V12 switch checks whether the MSISDN is entered. The MSISDN is
replaced by the local roaming number (LRN) in the SCCP called party address.
The LRN in the GT consists of
l

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 the
SEND_ROUTING_INFO_FOR_SM_RESULT to the GMSC.
If the MSISDN is not entered in the NP database, then the subscriber is not ported
and the SCCP message is routed to the HLR according to the HLRID in the MSISDN.

16

MN1705EN08AL-03

Number Portability Extensions (SF000607)

foreign
network

Siemens

donor
network
SIEMENS

recipient
network

SIEMENS

EWSD V12

SIEMENS

SIEMENS

EWSD V12
SRI for SM
GT=network...

SRI for SM

SIEMENS

HLR
SRI for SM
GT=HLR ID

SRI for SM
result

2
SIEMENS

SIEMENS

SIEMENS

SIEMENS

SIEMENS

VLR/MSC

Interworking
MSC

6
forward SMS

SM

1
SMS transfer
PBX

SMS
Center
ported MSUB

Fig. 8 International SMS

MN1705EN08AL-03

17

Number Portability Extensions (SF000607)

Siemens

2.3

Support of CCBS

CCBS was introduced in SR5.0. But the CCBS functionality is a Siemens proprietary
solution and not the GSM standardized method.
With the introduction of NP in SR7.0, CCBS is only supported under the following
conditions:
For each call only one query to the SCP NP database is allowed. This query must
take place in the originating MSC. This means that during this one query the network
identification code of the ported subscriber's new network AND the switch
identification 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 these
restrictions no longer apply except the general CCBS restrictions (other network and
signaling must support CCBS,....).
Now there can be more queries to the SCP NP database for each call and QoHR is
also supported.
If a network does not use an EWSD V12 server as central the NP database then the
SR7.0 functionality with all restrictions is also supported in SR8.0 (This means the
SR7.0 solution stays in SR8.0, too).
The Siemens solution uses the translation type IEESS for all CCBS messages. The
GT database has to be administered in such a way that all CCBS messages have to
be routed through the EWSD V12 switch (except the messages where the network
identification 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 and
routes the message to the according destination.

18

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

donor
network
SIEMENS

recipient
network

SIEMENS

SIEMENS

EWSD V12

SIEMENS

EWSD V12

CCBS request
GT=network...
TTID = IEESS

SIEMENS

SIEMENS

HLR

CCBS request
GT=HLR ID...
TTID = IEESS

CCBS request

CCBS
acknowledge

8
SIEMENS

SIEMENS

SIEMENS

VLR/MSC

SIEMENS

Interworking
MSC

CCBS 2
request

start
monitoring
result

start
6
monitoring

ISUP release
busy CCBS possible

9 CCBS
acknowledge

ported MSUB

Fig. 9 CCBS Request Routing

MN1705EN08AL-03

19

Number Portability Extensions (SF000607)

Siemens

2.4

INAP Query for Circuit Switched Calls

Instead of using the SCP as a number portability database or the MSC internal
number portability database (via SDDPFC) as it was realized in SR7.0, the EWSD
switch can be used as a number portability database. The EWSD switch replaces in
this case just the SCF (service control function) of the SCP. The interface between
the gateway MSC and the EWSD switch is covered by a subset of the SINAP5M (socalled 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 LNP
database query is possible)
Collect Information (CI) and RequestReportBCSMEvent (RRB):
To initiate the collection of further digits if the available digits are not enough for the
NP 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 found
in the NP database)
Connect (CON)
To route the call with the LRN if the number is ported. (LRN contained in destination
routing address)
ReleaseCall (RC)
The call should be released because there is no database entry found and QoHR is
used.

20

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

donor
network
SIEMENS

recipient
network

SIEMENS
SIEMENS

SIEMENS

SIEMENS

EWSD V12

SIEMENS

HLR

HLR

3 SRI result
unknown
subscriber

SRI

SRI

INAP

9
SRI result

4
IDP
(MSISDN)

CONNECT
(PrefixxxxMSISDN)

5
SIEMENS

SIEMENS

SIEMENS

SIEMENS

SIEMENS

SIEMENS

gateway
MSC

ISUP IAM
(PrefixxxxMSISDN)

MOC 1

VLR/MSC
gateway
MSC

via
MSC/VLR

query in
recipient
network

ported MSUB
2

and

only for query on HLR release

Fig. 10 INAP Query via V12 EWSD

MN1705EN08AL-03

21

Siemens

2.5
2.5.1

Number Portability Extensions (SF000607)

GTT Handling in the MSC

SMS Handling in the MSC

The short message transfer is received from the short message service center with
the standardized translation type UNKNOWN. In the inter-working MSC the
messages to ported MSUBs and non-ported subscribers must be separated by
different global title code points, i.e. code points must be created with the ported
number ranges, which route the SEND_ROUTING_INFO_FOR_SM to the EWSD
V12 SCF and code points with the non-ported number ranges which route the
SEND_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 routed
to the EWSD V12 SCCP relay node automatically, but should be handled as in
releases <SR8, i.e. if a query on digits or query on HLR release is required, the query
should take place either in the internal database (realized by subscriber-dependent
digit processing and feature control) or an INAP dialog to the SCP or the SCFunction
in the EWSD V12.
Therefore the circuit-oriented traffic (MTC) has to be distinguished from the pure
SCCP traffic (SMS/CCBS). With the aid of a project-dependent database setup
(MPRDDAT) the TTID or the global title digits (prefix in front of the received digits) for
the message SRI can be changed. So in the global title translation the operator has
to ensure that the TTID or the global title digits for the interrogation are changed
according to the mobile project data.
The way to recognize the number portability database query for mobile terminating
calls is the same as in versions <SR8.0.

22

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

1
SMS Transfer
TTID=UNKNOWN

PBX

SMS
Center

SIEMENS

SRI for SM
TTID=UNKNOWN

SIEMENS

SIEMENS

SIEMENS

EWSD V12

Interworking
MSC

GT Translation
GT Translation
GTDIG=
GTDIG=ported
portednumber
numberrange
range
TTID=UNKNOWN
TTID=UNKNOWN
=>SPC
=>SPCEWSD
EWSDV12
V12

Fig. 11 SMS Handling

1
B-MSISDN

project
projectdata:
data:
new TTID for SRI
new TTID for SRI
or
or
PREFIX
PREFIXfor
forSRI
SRI
SIEMENS

SIEMENS

4a 4c
SRI
TTID=UNKNOWN

SIEMENS

Gateway
MSC

SIEMENS

HLR

5a
unknown subscriber

2a

digit translator
CODE=<ported number range>
query on HLR release

3a 3c
2b CODE=<ported number range>
query on digits

2c

CODE=<other digits>

6a
6a 3b

SDDPFC
SDDPFC
IN
IN trigger
Trigger
=>
SPCofofSCP
SCPororEWSD
EWSDSCF
SCF
= SPC
or
or
SDDPFC
SDDPFC internal
internal NP
NP database
database

GT translation
GTDIG= ported number range
TTID=new TTID
to be sent TTID=UNKNOWN
or
GTDIG=<prefix>ported number range
TTID=UNKNOWN
=>SPC HLR
SIEMENS

SIEMENS

7a
4b
INITIAL_DP

EWSD V12
or
SCP

Fig. 12 MTC Handling

MN1705EN08AL-03

23

Siemens

2.5.3

Number Portability Extensions (SF000607)

CCBS Handling 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 in
the global title translation messages with the global title TTID=IEESS and the global
title digits of the ported number range have to be routed to the EWSD V11 SCF and
messages with global title digits outside of the ported number range are routed to the
HLR directly.

24

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

1
CCBS Request
SIEMENS

SIEMENS

Interworking
MSC

CCBS Request
TTID=IEESS

SIEMENS

SIEMENS

EWSD V12

GT Translation
GT Translation
GTDIG=
GTDIG=ported
portednumber
numberrange
range
TTID=IEESS
TTID=IEESS
=>SCP
=>SCPEWSD
EWSDV12
V12

Fig. 13 CCBS Handling

MN1705EN08AL-03

25

Number Portability Extensions (SF000607)

Siemens

2.5.4

EWSD Version 12 SCCP Query

The EWSD V12 switch is used as a central NP database which has INAP and SCCP
connections to the MSCs.
Therefore every subscriber ported in or out has to be entered in the NP database
with the LRN (local routing number).
If an NP query (Query via SCCP) must be performed for a called party address
during global title translation, then the parameter PPN of the command CR GTCPT
must be set to yes (default is no).
The SCCP called party address must be in national format (only national format is
supported). With this number a corresponding entry in the NP database is searched
for.
There are two possible results:
l

The number is not found in the NP database. In this case the destination given by
the 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 this
case the LNP database provides a new number. This new number is used with the
TTID, NP and NA of the original global title to form a new GT. This new global title
is translated and the SCCP message is routed to the resulting destination.

TIP
The 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.

26

MN1705EN08AL-03

Number Portability Extensions (SF000607)

SIEMENS

Siemens

SIEMENS

MSC

SCCP
SRI:
GT=MSISDN
SIEMENS

SIEMENS

ported

EWSD V12
GT
GTdigittree
digittree
SIEMENS

SIEMENS

HLR of not
ported MSUB

GT
GTCPT:GTDIG=ported
CPT:GTDIG=ported
number
numberrange
range

portability processing necessary

portability processing necessary

SIEMENS

SIEMENS

HLR of portedin MSUB

GT
GTDEST:
DEST:GTDIG=MSISDN
GTDIG=MSISDN
SPC=
SPC=e.g.
e.g.SPC
SPCofofHLR
HLR
GT
GTCPT:GTDIG=e.g.HLRID
CPT:GTDIG=e.g.HLRID

number
numberportability
portability
database
database
MSISDN
MSISDN e.g.
e.g.HLRID
HLRID
not
ported

GT
GTDEST:
DEST:
GTDIG=
GTDIG=e.g.HLRID
e.g.HLRID
SPC=
SPC=e.g.
e.g.SPC
SPCofofnew
newHLR
HLR

Fig. 14 Query in the EWSD V12

MN1705EN08AL-03

27

Number Portability Extensions (SF000607)

Siemens

2.6

MML Commands

MSC MML
MPRDDAT
In the mobile project data the TTID or a global title prefix can be stored. Both
parameters are valid for the global title translation if a send routing information is
supposed to be sent out. These data have to be set back in the global title
translation, 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 certain
project. The activation can just be changed during installation. If the feature flag is not
active, 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 the
known MML command CR INTRIG. The parameter ACNSEL must be set to 9 in
order to activate special protocol checks for the number portability query function.
The parameter GENPROP has to be set to DPINH and PROP11. The service key
can be set to any value.

28

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

Project data for Send Routing Information

DISP MPRDDAT;

NPTTID
NPPFX

{TTnn|UNKNOWN|....}
<1...5 hexadecimal digits>

Feature Activation
MOD MSERVOPT: FEAT=NPCCBS,STAT=ACT;
IN Trigger profile
CR INTRIG:

PRID=<name>, SSID=IN4, ACNSEL=9,

SKEY=<any>, GENPROP=DPINH&PROP11,
RTGP=SPC, DPC=<ewsd v12 spc>,
NETIND=....,....;

Fig. 15 MML Commands in the MSC

MN1705EN08AL-03

29

Siemens

Number Portability Extensions (SF000607)

MML commands in the EWSD V12 switch

Ported number administration
In the EWSD switch the ported numbers must be administered. This means an
allocation between the old number (PORTDN) and the new number (ROUTN), both
in national format has to be set up. The parameter STATUS has to be set up to
activate this allocation. Up to 1 million numbers can be administered.
Global title translation
As the EWSD switch works as an SCCP relay node the incoming messages have to
be forwarded to the right destination. However, as the subscriber addressed by the
party address called in the SCCP message can be a ported one, the received global
title digits are used for a number portability database query. This query is indicated
by the parameter PPN (portability processing needed) in the MML command CR
GTCPT. In this case the global title translation is interrupted and a number portability
query is performed. If the called party address is found in the number portability
database the digits are replaced by the new number administered. If the called party
number is not found the original global title translation is continued.

30

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

Ported number administration

ENTR LNPDAT:

PORTDN= <ported number national format>,

ROUTN=<routing number national format>,
STATUS={ACT|INACT};

Global title Translation with query

CR GTCPT:

TRID=...., GTDIG= <GT digits>, PPN=Y,...;

Fig. 16 MML Commands in the EWSD V12

MN1705EN08AL-03

31

Number Portability Extensions (SF000607)

Siemens

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 ported
subscribers must be evaluated and the messages must be routed via the EWSD V12
relay node. The format of the global title digits is changed to national format, i.e. the
country code is cut with DICON and the nature of address is set to NATNO.

32

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

/***********************************************************
/* 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
/***********************************************************
/*
<ENTR SCTRLG: TRLG=NPDB01, NETIND=NAT0, PRM1=0-9-1;
/*
//***********************************************************
//* CREATE GT-DIGIT-TREE
//***********************************************************
/*
<CR GTDIGTR: TRID=INTER#ISDN, TTID=UNKNOWN, NP=ISDNTNP, NA=INTNO;
/*
/***********************************************************
/* ROUTING OF INTERNATIONAL INCOMING MESSAGES TO V12 SWITCH
/***********************************************************
/*
<CR GTCPT:TRID=INTER#ISDN, GTDIG = 49-172-20,
#
DICON=.., NA=NATNO;
<CR GTDEST:TRID=INTER#ISDN,GTDIG = 49-172-20,ROUTE=TRLG,
#
TRLG= NPDB01, RTGP=PGTT;
/*

Fig. 17 Evaluation of the MSISDN for the SEND_ROUTING_INFO_FOR_SM to the EWSD V12

MN1705EN08AL-03

33

Siemens

Number Portability Extensions (SF000607)

NP query in the EWSD V12

On the opposite page the number portability query in an EWSD V12 relay node is
shown. International global titles incoming e.g. from the inter working MSC are
reduced to national format by global title re-translation.
The global title code point contains the parameter <possible ported number>. The
EWSD V12 internal database is consulted, to check if the global title digits are ported
or not.
In case they are not ported the global title translation is continued with the global title
destination.
In case they are ported a new global title translation is necessary with the new global
title digits (not shown in the example).

34

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

/***********************************************************
/* V12 switch with international connection to
/* a other PLMN or PSTN
/***********************************************************
/*
//***********************************************************
//* CREATE GT-DIGIT-TREE
//***********************************************************
/*
<CR GTDIGTR: TRID=INTER#ISDN, TTID=UNKNOWN, NP=ISDNTNP, NA=INTNO;
<CR GTDIGTR: TRID=D2#ISDN#NA, TTID=UNKNOWN, NP=ISDNTNP, NA=NATNO;
/*
/***********************************************************
/* ROUTING OF INTERNATIONAL INCOMING MESSAGES
/* CONVERT TO NATIONAL FORMAT AND RETRANSLATION
/***********************************************************
/*
<CR GTCPT:TRID=INTER#ISDN, GTDIG = 49-172-20
#
DICON=.., NA=NATNO;
<CR GTDEST:TRID=INTER#ISDN,GTDIG = 49-172-20,ROUTE=RETRANS,
#
LTRID=D2#ISDN#NA, RDIG=3;
/*
/*
/*
/***********************************************************
/* ROUTING OF MESSAGES TO ACCORDING HLR (HLRID=20)
/***********************************************************
/*
<CR GTCPT:TRID= D2#ISDN#NA, GTDIG = 172-20, PPN=Y, TTID=UNKNOWN;
<CR GTDEST:TRID= D2#ISDN#NA,GTDIG = 172-20,ROUTE=INTERNAL,
#
DPC=2-0-0-0, RTGP=CANGT, NI=NAT0;

Fig. 18 Global Title Translation in the EWSD V12

MN1705EN08AL-03

35

Siemens

Number Portability Extensions (SF000607)

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 the
global title translation without the feature "number portability extension". As the
SEND_ROUTING_INFO of call related signaling should never have been routed via
the EWSD V12 node, the SEND_ROUTING_INFO and the
SEND_ROUTING_INFO_FOR_SM have to be distinguished. Therefore the
SEND_ROUTING_INFO gets a new project specific translation type (e.g. TT15). On
the opposite page an example of the global title translation is shown. The reduction
shown from international format to national format is not mandatory because it could
also 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 is
created with the project-dependent TTID. Depending on the project, further routing
with or without global title, the TTID, should be set back in CR GTCPT to the
standardized value UNKNOWN.

36

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

/***********************************************************
/* Gateway MSC with evaluation of not ported MSISDN for the
/* SEND ROUTING INFO to the HLR
/***********************************************************
/*
/***********************************************************
/* TRANSLATION TYPE
/***********************************************************
/* a new translation type (set up in the project data)
/* e.g. TTN=TTnn is used
/*
<CR SCTTCD: TTID=TTnn, TTN=xx, NETIND=NAT0;
//***********************************************************
//* CREATE GT-DIGIT-TREE
//***********************************************************
/*
<CR GTDIGTR: TRID=INTNAT, TTID=TTnn, NP=ISDNTNP, NA=NATNO;
<CR GTDIGTR: TRID=INTINT, TTID=TTnn, NP=ISDNTNP, NA=INTNO;
/*
/***********************************************************
/* ROUTING OF INTERNATIONAL INCOMING MESSAGES
/* CONVERT TO NATIONAL FORMAT AND RETRANSLATION
/***********************************************************
/*
<CR GTCPT:TRID=INTINT, GTDIG = 49-172-30
#
DICON=.., NA=NATNO,TTID=UNKNOWN;
<CR GTDEST:TRID=INTINT,GTDIG = 49-172-30,ROUTE=RETRANS,
#
LTRID=INTNAT, RDIG=3;
/*
/*
/*
/***********************************************************
/* ROUTING OF MESSAGES TO ACCORDING HLR (HLRID=30)
/***********************************************************
/*
<CR GTCPT:TRID= INTNAT, GTDIG = 172-30, TTID=UNKNOWN;
<CR GTDEST:TRID= INTNAT,GTDIG = 172-30,ROUTE=INTERNAL,
#
DPC=3-0-0-0, RTGP=CANGT,NI=NAT0;
Fig. 19 Evaluation of the MSISDN for the SEND_ROUTING_INFO to the HLR

MN1705EN08AL-03

37

Siemens

Number Portability Extensions (SF000607)

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 the
ported number range, then the messages are routed to the EWSD V12 instead of to
the HLR.

38

MN1705EN08AL-03

Number Portability Extensions (SF000607)

Siemens

/***********************************************************
/* MSCs (this must be enter in every MSC)
/***********************************************************
/*
/***********************************************************
/* CREATION OF THE TRANSLATION GROUP NPDB01,
/* CONTAINING THE SPC OF THE EWSD V12 SWITCH
/***********************************************************
/*
<ENTR SCTRLG: TRLG=NPDB01, NETIND=NAT0, PRM1=0-9-1;
/*
//***********************************************************
//* CREATE GT-DIGIT-TREE
//***********************************************************
/*
/***********************************************************
/* GT-DATABASE FOR CCBS
/***********************************************************
/*
/* TRANSLATION TYPE
<ENTR SCTTCD: TTID=IEESS, TTN=17, NETIND=NAT0;
/*
/*
//***********************************************************
//* CREATE GT-DIGIT-TREE -- FOR INTERNATIONAL AND
//* NATIONAL NUMBER FORMAT!!
//***********************************************************
/*
<CR GTDIGTR: TRID=CCBSINT, TTID=IEESS, NP=ISDNTNP, NA=INTNO;
<CR GTDIGTR: TRID=CCBSNAT, TTID=IEESS, NP=ISDNTNP, NA=NATNO;
/*
/***********************************************************
/* ROUTING OF CCBS-MESSAGES FOR OWN SUBSCRIBER
/* TO V12 SWITCH (NOT DIRECTLY TO THE HLR BECAUSE
/* CAN BE PORTED OUT)
/* INTERNATIONAL NUMBER IS CONVERTED IN NATIONAL FORMAT
/***********************************************************
/*
<CR GTCPT:TRID=CCBSINT, NA=NATNO, DICON=..
#
GTDIG = 49-172-20;
<CR GTDEST:TRID=CCBSINT,GTDIG = 49-172-20,ROUTE=TRLG,
#
SSID=ISS, TRLG=NPDB01, RTGP=PGTT;
/*
<CR GTCPT:TRID=CCBSNAT,
#
GTDIG = 172-20;
<CR GTDEST:TRID=CCBSNAT,GTDIG = 172-20,ROUTE=TRLG,
#
SSID=ISS, TRLG=NPDB01, RTGP=PGTT;
Fig. 20 Evaluation of MSISDN of Own Possible Ported out MSUBs for CCBS

MN1705EN08AL-03

39

Number Portability Extensions (SF000607)

Siemens

2.8

Upgrade Relevance

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

40

MN1705EN08AL-03