GTT PDF

Global Title Translation Siemens
Global Title Translation
Contents
1 Routing without global title translation 3
2 Routing with global title translation 7
2.1 Why global title translation? 8
2.2 Examples of global title translation 10
3 Global title translation 23
3.1 SCCP calling and called party addresses 24
3.2 Where is global title translation done? 28
3.3 Message flows 30
3.4 Administration of global title translation 34
4 Application examples 51
4.1 Network-internal location update 52
4.2 Mobile terminating call 56
4.3 International location update 60
MN2513EU11MN_0001
1
© 2006 Siemens AG
Siemens Global Title Translation
2 MN2513EU11MN_0001
© 2006 Siemens AG
1 Routing without global title translation
MN2513EU11MN_0001
3
© 2006 Siemens AG
Link-by-link signaling is always used for traffic channel-oriented connections. In other

words, the problem of addressing destination points in an unknown network does not
occur with this kind of signaling.
However, the problem of network gateways also exists in this case because the
addressing in CCS7 is only possible within one network (NAT0/ NAT1/ INAT0). This
does not present too many difficulties though, as the messages are evaluated and
regenerated at user level (e.g., ISUP) in each switching center the traffic channels
pass through. For this reason, at network gateways from e.g. the network NAT0 to
the network NAT1, the incoming message from NAT0 is received and evaluated in
the standard routing database,
CR CPT
CR DEST
CR ROUTE
CR TGRP
CR TRUNK
regenerated and sent to the signaling point defined using ENTRC7TGREL: DPC= ,
TGNO=.,NETIND=NAT1. In other words, signaling points that cover network
gateways must have an OPC for different signaling networks.
4 MN2513EU11MN_0001
© 2006 Siemens AG
Dialing Info
Dialing Info
SIEMENS SIEMENS
ENTR
ENTR
C7TGREL:
C7TGREL:
DPC=
Origin DPC=
NETIND=
Dialing Info Net NETIND=
Dialing Info
Dialing Info
ENTR
SIEMENS SIEMENS
ENTR
C7TGREL:
C7TGREL:
DPC=
DPC=
NETIND=
NETIND=
Dialing Info
Dialing Info
SIEMENS SIEMENS
ENTR
ENTR
C7TGREL:
C7TGREL:
Destination DPC=
DPC=
Net NETIND=
NETIND=
SIEMENS SIEMENS
Signaling
Circuit
Fig. 1 Routing without global title translation
MN2513EU11MN_0001
5
© 2006 Siemens AG
6 MN2513EU11MN_0001
© 2006 Siemens AG
2 Routing with global title translation
MN2513EU11MN_0001
7
© 2006 Siemens AG
2.1 Why global title translation?

The CCS7 signaling method identifies the destination and the origin of a signaling
message by using signaling point codes (SPCs). Since a signaling point code has got
14 bits only, it is too small to address all signaling points worldwide unambiguously.
For this reason, signaling point codes are always combined with a network indicator
NI – which means that a code is only ever valid in one particular signaling network.
To facilitate unambiguous global addressing, a unique international address or
sender information is necessary. This global address is known as the global title and
is sent in the SCCP called- and calling party address of CCS7 messages.
Since SPCs are only valid within individual networks, so-called global title
translation must be performed at each relevant network gateway. The SCCP
performs the global title translation, whereby an internationally unique address
(global title) is translated into an SPC and network indicator in order to be transferred
to the network border, or to a destination if it is located in the same network.
Global title translation is always used if no SPC for the destination is available at all.
For example, the HLR has to be identified on the basis of the IMSI or the VLR/MSC
on the basis of the VLRISD.
8 MN2513EU11MN_0001
© 2006 Siemens AG
No
SPC
NAT0 100 NAT0 200
Global
GlobalTitle
Title
300
NAT0 NAT0
DPC
DPC&&
NETIND
NETIND NAT0 300
NAT1 100 SPC=200
Global
GlobalTitle
Title NETIND=NAT0
NAT1 300
NAT1
?
DPC
DPC&&
NETIND
NETIND SPC=200
NETIND=NAT0
Global NAT1 300

GlobalTitle
Title
NAT0 400
DPC
DPC&&
NETIND
NETIND 200
NAT0
NAT0 200
NAT0 100
NAT0
Fig. 2 Why global title translation?
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
9
© 2006 Siemens AG
2.2 Examples of global title translation

Location update
The visitor location register (VLR) requests the HLR for the subscriber data. The
home location register (HLR) is determined by the IMSI (global title). The MCC and
the MNC indicate if the HLR is from the home or from a foreign PLMN. The first digits
of the MSIN identify the HLR within the PLMN. If the mobile subscriber has changed
the VLR area, the HLR cancels the location in the old VLR. The old VLR is
determined by the VLRISD (global title), stored in the subscriber's mobility data.
Mobile terminating call

The gateway MSC (GMSC) requests routing information from the HLR
(interrogation). The HLR is determined by the dialed MSISDN (global title). The CC
and NDC indicate if the HLR is from the own or from a foreign PLMN. The first digits
of the SN identify the HLR within the PLMN. The HLR then requests the VLR for an
MSRN. The VLR is determined by the VLRISD (global title).
Triple request
The VLR requests new authentication triples from the HLR. The HLR is determined
by the IMSI (global title).
Inter MSC handover

The old MSC requests a handover to a new MSC. The new MSC is determined by
the MSCID (global title).
10 MN2513EU11MN_0001
© 2006 Siemens AG
SIEMENS SIEMENS SIEMENS SIEMENS
Location
VLR/ Update
HLR
MSC
IMSI DPC
NETIND
Location Update
SRI
VLR/
HLR
MSC
MSISDN DPC
VLRISD
NETIND
Mobile Terminating Call DPC PRN
NETIND
SIEMENS SIEMENS
VLR/
MSC
Triple
VLR/ Request
HLR
MSC
IMSI DPC
NETIND
Triple Request
SIEMENS SIEMENS
Old MSC
MSCID
SIEMENS SIEMENS
Handover
Request
Handover new DPC

MSC NETIND
Fig. 3 Examples of global title administration
MN2513EU11MN_0001
11
© 2006 Siemens AG
2.2.1 Location update with national / international roaming
National roaming
For location updates with national roaming, the IMSI is supplied by the mobile station,
or, if the location changes, from a known VLR in the new location. The location
update must then be sent to the HLR of the subscriber. The IMSI is transferred to the
SCCP for this purpose. The SCCP contains the global title database. Using this
database, the SCCP translates the IMSI, including the HLRID, to a destination point
code and the associated network indicator. Global title translation is not required for
the reply from the HLR because the DPC can be used for addressing.
12 MN2513EU11MN_0001
© 2006 Siemens AG
Global Title
Global Title
Translation
Translation
MCC/MNC/HLRID
MCC/MNC/HLRID
SPC&NETIND
SPC&NETIND
of HLR
of HLR
B
S
INAP EIR MSC VLR HLR
O S
T A TCAP
H P
E
R
SCCP
MTP
VLR/MSC
DPC
NETIND
SIEMENS SIEMENS
MCC/MNC/HLRID HLR
Fig. 4 National location update
MN2513EU11MN_0001
13
© 2006 Siemens AG
International roaming
For location updates with international roaming, the IMSI is supplied by the mobile
station or, if the location changes, from a known VLR in the new location. The
location update must then be sent to the HLR in the remote network of the booking
subscriber. The IMSI is transferred to the SCCP for this purpose. The SCCP contains
the global title database. Using this database, the SCCP translates the IMSI up to the
MNC into the destination point code of the gateway to the next network. The IMSI is
also transferred as the international address/global title in the SCCP called party
address. The IMSI must therefore be changed to an international standard that can
be recognized by the PSTN (hybrid IMSI). Global title translation takes place again in
that gateway in order to obtain the CCS7 address in the next signaling network.
Global title translation is performed for each change in network until the destination
network is reached. Generally, translation takes place a last time in the gateway of
the destination network, where the DPC and network indicator of the HLR are
determined.
14 MN2513EU11MN_0001
© 2006 Siemens AG
MCC/MNC
MCC/MNC
MCC/MNC/MSIN
NAT0 100 NAT0 DPC=200

DPC=200
NI=NAT0
MSC/VLR Origin NI=NAT0
Global Title Net

„ hybrid IMSI“
„ hybrid IMSI“
NAT0 200
NAT1 100 DPC=300
DPC=300
NI=NAT1
NI=NAT1
Global Title NAT1
NAT1 300 „ hybrid IMSI“

„ hybrid IMSI“
INAT0 100
Global Title DPC=300

DPC=300
NI=INAT0
NI=INAT0
INAT0
INAT0 300
„ hybrid IMSI“
Global Title NAT1 DPC=300

DPC=300
NI=NAT1
NI=NAT1
NAT1 300
„ hybrid IMSI“
No Global Title
DPC=200
DPC=200
NI=NAT0
NAT0 NI=NAT0
Destination
NAT0 200 Net
HLR
Fig. 5 Location update with international roaming
MN2513EU11MN_0001
15
© 2006 Siemens AG
2.2.2 National mobile terminating call

The digit translator receives a dialed MSISDN of the own PLMN with the result
"interrogation" (TRATYP=MOBINTER). This result leads to a destination with
MINMAX on one hand, and to global title translation on the other. Similar to the IMSI
in location updates, the MSISDN is translated by global title translation into the CCS7
signaling address of the HLR of the called party. The MAP message “Send Routing
Information” is then sent to the HLR.
The mobility data of the called party are read in the HLR in response to the message.
Using the VLRISD stored in the HLR, the global title translation function is activated
to translate the VLRISD into the CCS7 signaling address of the VLR/MSC of the
called party. The request to provide a mobile station roaming number is sent to this
address.
16 MN2513EU11MN_0001
© 2006 Siemens AG
B INAP EIR MSC VLR HLR

S
S Global Title
O
A Global Title
T
H P
TCAP Translation:
Translation:
E
R
CC/NDC/HLRID
SCCP
CC/NDC/HLRID
SPC&NETIND
SPC&NETIND
MTP ofofHLR
HLR
Global
GlobalTitle
Title
Translation:
Translation:
VLR/MSC VLRISD
VLRISD
[CC]/[NDC]/SN SPC&NETIND
SPC&NETIND
ofofMSC/VLR
MSC/VLR
B INAP EIR MSC VLR HLR
S
S
O
T
A
TCAP
H P
E
R
SCCP
MTP
SIEMENS SIEMENS
HLR visited
HLR VLR/MSC
of B sub
Fig. 6 National mobile terminating call
MN2513EU11MN_0001
17
© 2006 Siemens AG
2.2.3 International mobile terminating call

If a foreign MSISDN is received by an MSC, usually no international interrogation is
started.
The dialed MSISDN is analyzed in the visited MSC and the call is switched as a
normal traffic channel connection (e.g., ISUP) to the destination network (usually via
PSTN).
The call received in the destination network is analyzed in the gateway MSC and
interrogation is started. From this point on, the mobile terminating call is handled in
the same way as a national mobile terminating call, described before.
18 MN2513EU11MN_0001
© 2006 Siemens AG
MSISDN
SIEMENS SIEMENS
Origin
VLR/ ISUP Net
MSC SIEMENS SIEMENS
Gate-
way
ISUP
SIEMENS SIEMENS
PSTN
Switch ISUP
SIEMENS SIEMENS
PSTN
PSTN Switch
Global Title
Net Global Title
Translation:
Translation:
MSISDN
ISUP MSISDN
SPC&NETIND
SIEMENS SIEMENS
SPC&NETIND
of HLR
Gate- of HLR
way
MAP
SIEMENS SIEMENS
HLR Destination
Net
Fig. 7 International mobile terminating call
MN2513EU11MN_0001
19
© 2006 Siemens AG
2.2.4 Mobile terminating call to an own mobile subscriber

roaming in a foreign PLMN
In case of mobile terminating calls to a network’s own mobile subscriber, currently
located in a foreign network, the MSISDN of the called party is received by the calling
party’s MSC. Since the mobile user belongs to the same network, interrogation is
started in the network’s own HLR. The VLRISD of the foreign VLR is stored in the
HLR as part of the mobility data of the called party.
Using global title translation, the VLRISD is translated into the address of the
network’s own gateway switches and the MAP message “Provide Roaming Number”
is sent there.
Since this involves a change in networks, global title translation is again necessary.
The VLRISD is translated to the signaling address of the next network node (e.g., to
NAT1) and the message is transferred.
Global title translation is performed for each change in network until the gateway in
the destination network is reached. Generally, translation takes place a last time here
because the VLR can be identified from this point by means of the CCS7 signaling
address.
20 MN2513EU11MN_0001
© 2006 Siemens AG
MSISDN
MSISDN
MSISDN
NAT0 100 DPC=300

DPC=300
MSC NAT0 300 NI=NAT0
NI=NAT0
NAT0 Origin HLR

VLRISD
Net VLRISD
NAT0 200 Global Title
NAT1 100 DPC=200
DPC=200
NI=NAT0
NI=NAT0
Global Title NAT1
VLRISD
VLRISD
NAT1 300
INAT0 100
DPC=300
DPC=300
Global Title NI=NAT1
NI=NAT1
INAT0
INAT0 300 VLRISD
VLRISD
NAT1 100
DPC=300
DPC=300
Global Title NAT1 NI=INAT0
NI=INAT0
NAT1 300 VLRISD

VLRISD
NAT0 100
No Global Title DPC=300
DPC=300
NI=NAT1
NI=NAT1
NAT0
Destination
NAT0 200 Net
VLRISD
VLRISD
VLR
DPC=200
DPC=200
NI=NAT0
NI=NAT0
Fig. 8 Mobile terminating call to an own mobile subscriber roaming in a foreign net
MN2513EU11MN_0001
21
© 2006 Siemens AG
22 MN2513EU11MN_0001
© 2006 Siemens AG
3 Global title translation
MN2513EU11MN_0001
23
© 2006 Siemens AG
3.1 SCCP calling and called party addresses

The variable mandatory part and optional part fields in the SCCP message contain
the called party and calling party addresses. The addresses are used for global
addressing of signaling point codes and additionally contain the subsystem number.
This number is used for addressing the subsystem in the destination point by the
SCCP.
The global title is not required in the simplest case (internal network routing) because
the routing label of the CCS7 message can be used for addressing. In other words,
the subsystem number is adequate as addressing information in this case.
The information units of this type of address have the following meaning:
• Length indicator (mandatory)
The length indicator indicates the amount of the following octets
• Address indicator (mandatory):

1. SPC indicator (bit 0)
A "1" indicates that the address contains an SPC
A "0" indicates that the address does not contain an SPC
(set to 0 according to GSM recommendation)
2. Subsystem indicator (bit 1)
A "1" indicates that the address contains a subsystem number SSN
(set to 1 according to GSM recommendation)
3. Global title indicator (bits 2...5)
The global title indicator indicates the content of the address field
0000 no global title included
0100 global title includes translation type, numbering plan, encoding scheme
and nature of address (Global Title Format 4)
4. Routing indicator (bit 6)
Bit 6 of the address indicator octet informs the next SCCP signaling node how
SCCP routing has to be performed:
a) A "0" in bit 6 indicates that routing should be based on the global title in the
address.
b) A "1" in bit 6 indicates that routing should be based on the DPC in the MTP
routing label and the subsystem number SSN in the called party address. (If
the point code indicator is set to "1", the SCCP receiver could take the SPC of
the SCCP address instead of the MTP-DPC.)
5. Bit 7 of the address indicator octet is designated for national use.
24 MN2513EU11MN_0001
© 2006 Siemens AG
• Subsystem Number
Carries the number of the calling/called Subsystem, e.g. HLR, VLR, BSSAP.
Called and Calling Party Address structure if routing

is done on OPC/DPC of the MTP L3 Routing Label.
Shortest possible length of Address fields!
Lenght Indicator (2)

(0) (0) (0) (0) (0) (0) (1) (0)
Routing SSN SPC

not
Indicator Global Title Indicator (0) Indicator Indicator
used
(1) (0) (0) (0) (0) (1) (0)
SSN (e.g. VLR=7)

(0) (0) (0) (0) (0) (1) (1) (1)
Length Indicator is 2 because two Global Title Indicator is 0 because no

more bytes follow. GT is included. Recommended!
SPC Indicator is 0 because no SPC Routing Indicator 1 means “Route on

is included. Recommended! OPC/DPC of MTP L3 Routing Label”.
SSN Indicator is 1 because SSN is Subsystem Number.

always included in Siemens solution. E.g. HLR=6, VLR=7, MSC=8, EIR=9
Fig. 9 Example of called and calling party addresses for net internal use: no GT contained
MN2513EU11MN_0001
25
© 2006 Siemens AG
• Signaling point code SPC (optional, but not necessary for GSM).
The SPC identifies the absolute end SPC and, if point code indicator = 1, consists
of 14 bits of 2 octets.
• Subsystem number (optional, but necessary for GSM)

The subsystem number (SSN) identifies an SCCP user function and if subsystem
indicator = "1", consists of one octet coded as follows (examples):
1. 11111110= 254 BSSAP (SSID = BSSAP)
2. 00000111= 7 VLR (SSID = MAPVLR)
3. 00000110 = 6 HLR (SSID = MAPHLR)
4. 00001000= 8 MSC (SSID = MAPMSC)
5. 00001001= 9 EIR (SSID = MAPEIR)
• Translation type
The translation type is a one-octet field that is used to direct the message to the
appropriate global title translation function. Thus, it may be possible for the
address information to be translated into different values for and different
combinations of DPCs, SSNs and GTs.
1. 00000000= 0 TTID=UNKNOWN (mandatory for international
applications)
2. 00000001= 1 TTID=IMSI (not used: in case of international location
update TTID=IMSI has to be converted to UNKNOWN)
3. 00000010= 2 TTID=IMEI According to GSM recommendation, the
translation type should be UNKNOWN
• Numbering plan
1. 0000= 0 NP= unknown: not used in international traffic
2. 0010= 1 NP= ISDNTNP (ISDN telephony numbering plan,

E.163/E.164). Example: to address a VLR of a foreign
PLMN
3. 0110= 6 NP= LMNP (land mobile numbering plan, E.212): not
used in intern. traffic
4. 0111= 7 NP= ISDNMNP (ISDN mobile numbering plan, E.214).
Example: to send a location update message to an HLR
of a foreign PLMN
26 MN2513EU11MN_0001
© 2006 Siemens AG
• Encoding scheme (that information cannot be administered)

1. 0001 = 1 odd number of digits
2. 0010 = 2 even number of digits
• Nature of address
1. 0000001= 1 NA = SUBNO (subscriber number)
2. 0000010= 2 reserved for national use
3. 0000011= 3 NA = NATNO (national number)
4. 0000100= 4 NA = INTNO (international number)
Called and Calling Party Address structure if routing

is done on Global Title Translation.
Length depends on number of Global Title digits!
Length Indicator depends on number

Lenght Indicator (e.g. 11) of Global Title Digits.
(0) (0) (0) (0) (1) (0) (1) (1)
SPC Indicator is 0 because no SPC
Routing SSN SPC
not is included. Recommended!
Indicator Global Title Indicator (Type 4) Indicator Indicator
used
(0) (0) (1) (0) (0) (1) (0) SSN Indicator is 1 because SSN is
always included in Siemens solution.
(SPC bits 0-7)
Global Title Indicator is 4 because
GT of Type 4 is included.
not not Routing Indicator 0 means “Route on
(SPC bits 8-14)
used used Global Title”.
Position and structure of SPC if it is

SSN (e.g. HLR=6) included. NOT RECOMMENDED!
(0) (0) (0) (0) (0) (1) (1) (0)
Subsystem Number.
E.g. HLR=6, VLR=7, MSC=8, EIR=9
TTID (e.g. UNKNOWN)
(0) (0) (0) (0) (0) (0) (0) (0) Translator Type Identification.
0=UNKNOWN, 1=IMSI, 17=IEESS.
NP (e.g. ISDNTNP) Encoding Scheme (e.g. odd) Encoding Scheme. 1=odd number of
(0) (0) (0) (1) (0) (0) (0) (1) GT digits, 2=even number of digits.
not Numbering Plan. 1=ISDNTNP,

NA (e.g. INTNO)
used 6=LMNP, 7=ISDNMNP.
(0) (0) (0) (0) (1) (0) (0)
Nature of Address. 3=National
GT digit 2 (e.g. 9) GT digit 1 (e.g. 4) number, 4=International Number
(1) (0) (0) (1) (0) (1) (0) (0)
GT digits. Last digit is a filler (H’F) if
Encoding Scheme is odd.
GT digit 4 (e.g. 7) GT digit 3 (e.g. 1)
(0) (1) (1) (1) (0) (0) (0) (1)
...
GT digit n+1 (e.g. Filler) GT digit n (e.g. 6)

(1) (1) (1) (1) (0) (1) (1) (0)
Fig. 10 Example of called/calling party addresses for international use: GT contained
MN2513EU11MN_0001
27
© 2006 Siemens AG
3.2 Where is global title translation done?

One (or more) of the main processors for applications (MP:AP) has to be determined
to be responsible for GTT. The functions of this "MP:GTT" is not exclusively available
to the shelf in which it is located but to the whole node.
The parameters Load type and Load model determine the software functions of the
MP, since the HW is the same for all MP:AP. For "MP:GTT" the Load models
SLTSGTR (recommended use) or SLTSGTR1/2 may be used in combination with the
Load type TSLT0001.
Load Type Load Model Meaning

TSLT0001 SLTSGTR MP for SCCP global title translation only
(recommended)
TSLT0001 SLTSGTR1/2 MP for SCCP global title translation and MTP L2/L3
functions
28 MN2513EU11MN_0001
© 2006 Siemens AG
Create MP for Global Title Translation
CRMP: MP = ,
Load type = TSLT0001,
Load model= <SLTSGTR / SLTMTPSGTR1/2>,
Rack= ,
Shelf= ,
Pitch= ,
Board type= ,
Statistics= FALSE,
[Alarm profile MP= ,]
[Alarm profile MP Mpu= ];
Fig. 11 Creating a main processor for global title translation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
29
© 2006 Siemens AG
3.3 Message flows

3.3.1 Signaling end point
Messages from a LTG, for which global title translation has to be done are forwarded
to the MP responsible for GTT automatically. After GTT, the MSU with the new
DPC/NETIND in it's routing label leaves towards the MP:SLT that will do message
routing by evaluating the DPC and allocating a linkset and a link via which the
message leaves the NE.
Signaling messages, coming in from another NE, will be received by an MP:SLT and
also routed to the MP responsible for GTT. After GTT the message will be passed on
to the subsystem responsible for evaluating the message content. This may be
located in the CP or in a GP of the LTGs. (Example: The switch receiving such a
message is a Gateway AND the final receiver).
The SSNC-internal path of the MSU is the same, no matter via which kind of link it
was received (64kbit/s link or high speed link).
30 MN2513EU11MN_0001
© 2006 Siemens AG
SS7-Links 64kbit/s, LTG

trunks
LTG
SSNC
LTG
LIC ASN DLU
SS7-Links 64kbit/s LTG
or
HS-Links 2Mbit/s LIC
SN
SN
MP/SLT
MB D
MP/GTT
SC
MP/STAT
MP/SM
MP/OAM
CP113C
CP113C
Fig. 12 Signaling end point, incoming MSU

trunks
LTG
SSNC
LTG
LIC ASN DLU
or
SN
SN
MP/SLT
MB D
MP/GTT
SC
MP/STAT
MP/SM
MP/OAM
CP113C
CP113C
Fig. 13 Signaling end point, outgoing MSU
MN2513EU11MN_0001
31
© 2006 Siemens AG
3.3.2 Signaling relay point

Pure signaling transfer points (STP) do not care about the message content. They
forward an MSU because of the DPC in it's routing label and don't do global title
translation.
Signaling relay points (SRP) also don't care about the message content, but they
do a global title translation and forward the message, depending on the result of that
GTT (typical application: international gateway exchange for signaling traffic).
Incoming MSUs will be received by an MP:SLT, forwarded to the MP responsible for
GTT and, depending on the result of the GTT, forwarded to another MP:SLT that
provides the connection to the link, leading to the DPC found in GTT.
The SSNC-internal path of the MSU is the same, no matter via which kind of link it
was received (64kbit/s link or high speed link).
32 MN2513EU11MN_0001
© 2006 Siemens AG

trunks
LTG
SSNC
LTG
LIC ASN DLU
or
SN
SN
MP/SLT
MP/GTT
MB D
MP/SLT
SC
MP/STAT
MP/SM
MP/OAM
CP113C
CP113C
Fig. 14 Signaling relay point with GTT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
33
© 2006 Siemens AG
3.4 Administration of global title translation

The global title translation database should be created in the following sequence:
1. CR SPLNKLOC / SPLNKREM:
General data about the own SCCP or the SCCP in the destination signaling
points (see chapter about SCCP administration).
2. CR SPSSN:
Links a subsystem ID to a subsystem number for a local SCCP linkage (see
chapter about SCCP administration).
3. CR SPAPLOC / SPAPREM:
Creation of subsystems control data in the own or the destination signaling point
(see chapter about SCCP administration).
4. CR SPCLGPA:
Creation of Calling Party addresses for local subsystems which use message
transfer via Global Title Routing
5. CR SPTT:
Linking an SCCP-specific translation type id to a translation type number that will
be used in the SCCP messages.
6. CR SPENS/SPRNS:
List of possible routes, used to reach a local or remote SCCP linkage with or
without further GTT.
7. CR SPGTTRL:
Combinations of format parameters that describe the global title digits.
8. CR SPGTCRUL:
List of instructions to modify the global title that leaves the NE as new SCCP
called party address (if required).
9. CR SPGTRUL:
Definition of how to find the result of global title translation.
34 MN2513EU11MN_0001
© 2006 Siemens AG
Incoming MSU
SCCP OPC DPC NI

cdPA
Global Title
Translator
Global Title Global Title Rule

Conversion Rule
End Point Entity

Set Relay Node Set Retranslation
without SSN
Remote SCCP
Linkage
SCCP
Linkage
SCCP OPC DPC NI

cdPA
Outgoing MSU
Fig. 15 Global title translation
MN2513EU11MN_0001
35
© 2006 Siemens AG
3.4.1 Administration of the calling party address

For each local SCCP subsystem which may use message routing via GT, a calling
party address (cgPA) has to be defined, containing the global title of the NE (E.164)
and the subsystem number. It has the same data fields as the SCCP called party
address.
This cgPA is included in outgoing SCCP messages to other signaling networks and
contains enough information to identify the originating signaling point and/or the
SCCP service access point unambiguously.
A cgPA may contain a global title, e.g. for international signaling. A global title is
usually not required in an SCCP calling party address for network internal signaling,
since in that case all necessary information for routing an acknowledgement can be
obtained from the routing label. The 'CLGPA type indicator' defines the routing
preference, i.e. whether a GT shall be contained in the cgPA field of an outgoing
MSU or not.
36 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP calling party address
CRSPCLGPA: SPCLGPA name = ,

[SPCLGPA id = ,]
SPAPLOC name / ID = ,
SPLNKLOC name / ID = ,
GT Address Info = <GT digits>,
TTID = Unknown,
NP = ISDN Telephone Numbering Plan,
NA = International Nr. ,
CLGPA Type Indicator = Programmed ,
[Include SPC = False,]
[Include GT = False];
Fig. 16 SCCP calling party address
SIEMENS SIEMENS
HLR
:
=1 SN
RI nly S
o n
A = atio
cgP e _Loc
dat
Up
SIEMENS SIEMENS
Location VLR
Update
foreign
PLMN
cgP R
A = I = 0:
Ful SIEMENS SIEMENS
Titl l Glob
Upd e al SIEMENS SIEMENS
HLR
ate
_Lo
cat
ion IGE
CRSPCLGPA:
CLGPA Type Ind=
Programmed, ...
Fig. 17 Effect of parameter 'CLGPA Type Indicator'
MN2513EU11MN_0001
37
© 2006 Siemens AG
3.4.2 SCCP end node entity sets

The SCCP End Node Entity Sets describe a local or remote SCCP linkage as result
of global title translation in case the final signaling end point (i.e. where the message
content is evaluated) can be determined in the own node.
In these cases, no further GTT is necessary (RI=1) and the global title will be
removed from the called party address automatically.
A primary and, optionally, a second destination are provided that may be operated in
a loadsharing mode, described by the 'Sharing Mode' (only one of them may be a
local SCCP). Both destinations must exist and must have been created in the same
signaling network.
The 'Sharing Mode' parameter has the following meanings:
Sharing Mode Primary 1 Primary 2

Dupli Load Shared 50% 50%
Dupli Dominant 100% standby
Solitary 100% not entered
TIP
Sharing mode = 'Dupli Replacement' can also be found in the selection lists of the
switch commander but is not supported by the SCCP.
38 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP End Node Entity Set without Subsystem Number
CRSPENS: SPENS Name = ,

Primary 1 Name = <SCCP Linkage Name>,
[Primary 2 Name = <SCCP Linkage Name>,]
Sharing Mode = <Dupli Dominant /
Dupli Load Shared /
Solitary>;
Fig. 18 End node set without SSN
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
39
© 2006 Siemens AG
3.4.3 SCCP relay node entity sets

The SCCP Relay Node Entity Sets describe a remote SCCP linkage as result of
global title translation in case the final signaling end point can not be determined in
the own node.
In this case, a further GTT is necessary in these SCCPs (RI=0).
Two primary and two backup SCCP Linkages may be defined. At least 'Primary 1
ID/Name' must be entered. The loadsharing mode between the entered SCCPs is
assigned implicitly without extra parameter.
The optional 'SSID' parameter allows to set the subsystem number in the outgoing
MSU after global title translation if routing is done on global title to a relay node. This
parameter should not be used!
Implicit loadsharing mode:
SCCP linkage Primary 1 Backup 1 Primary 2 Backup 2

combinations: load load load load
Primary 1 100%
Primary 1/Primary 2 50% 50%
Primary 1/Backup 1 100% standby for
Primary 1
Primary 1/Backup 1/ 50% standby for 50% standby for
Primary 1 Primary 2
Primary 2/Backup 2
40 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP Relay Node Entity Set
CRSPRNS: SPRNS Name = ,

Primary 1 Name = <SCCP Linkage Name>,
[Primary 2 Name = <SCCP Linkage Name>,]
[Backup 1 Name = <SCCP Linkage Name>,]
[Backup 2 Name = <SCCP Linkage Name>,]
[SSID = ];
Fig. 19 Relay node entity set
Primary1:active
OPC
Backup1:standby
Primary1:active
OPC
50 : 50
Primary2:active
Primary1:active
Backup1:standby 50 : 50
OPC
Primary2:active
Backup2:standby
Fig. 20 Loadsharing models for relay node entity sets
MN2513EU11MN_0001
41
© 2006 Siemens AG
3.4.4 Global title translator

The global title translator specifies the entry requirement for global title translation by
providing the format parameters for each possible global title as a combination of
Translation Type ID (TTID), Numbering Plan (NP) and Nature of Address (NA). In
other words: it tells the SCCP how to interpret the global title digits. This combination
must be unique.
The 'Global Title Translation Type attribute' represents the translation type, which is a
pure SCCP concept. It is part of the global title that indicates the specific use of the
global title address information. In other words, it is the key information that
differentiates between the use of identical NP/NA/GT- digit combinations. This global
title translation has to be converted into a Translation Type Number (TTN) by means
of the task CRSPTT.
42 MN2513EU11MN_0001
© 2006 Siemens AG
SCCP Global Title Translator
CRSPGTTRL: SPGTTRL Name = ,

[SPGTTRL Id = ,]
TTID = ,
NP = ,
NA = ;
Fig. 21 SCCP global title translator
GT Supplements
GT Number Type
TTID NP NA
IMSI IMSI LMNP INTNO
Hybrid-IMSI UNKNOWN ISDNMNP INTNO

International Telephone Number UNKNOWN ISDNTNP INTNO
National Telephone Number UNKNOWN ISDNTNP NATNO
CCBS International Number IEESS ISDNTNP INTNO

CCBS National Number IEESS ISDNTNP NATNO
Fig. 22 Examples of format parameters
MN2513EU11MN_0001
43
© 2006 Siemens AG
3.4.5 Global title conversion rule

The conversion rule for the global title digits contains an ordered list of instructions
specifying to insert, delete, replace, or take-over digits or supplements in the old
called party address to produce a new one. This new called party address will not be
processed again in the own node but will be part of the outgoing MSU.
Conversion operations to be defined in a global title conversion rule are:
Operation Meaning
+ Digits after the '+' sign are inserted at the respective position
R Digits after the 'R' sign replace the original digits at the respective
position
X The original digit remains at the respective position (one 'X' per digit)
. The original digit is deleted (one '.' per digit)
S Stop converting immediately
T Copy the remaining characters, and then stop
Example: (see next page)

An IMSI of a roaming subscriber is being received in a VLR during location update
and used as global title in the called party address of the 'Update_Location' message
to the subscriber's HLR. Since that global title is not in accordance with the
international standard for routing based on global title, it has to be converted into a
'hybrid IMSI'. Whether this conversion is done in the VLR immediately or in a
gateway, just before the message leaves the own PLMN, is up to the operator.
IMSI 'hybrid IMSI'

MCC - MNC – MSIN CC - NDC – MSIN
e.g.: 262 - 02 - 1234567890 e.g.: 49 - 172 - 1234567890
TTID=IMSI TTID=UNKNOWN
NP=LMNP NP=ISDNMNP
NA=INTNO NA=INTNO
44 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP Global Title Conversion Rule
CRSPGTCRUL: SPGTCRUL Name = ,

Addr. Info Conv. Rule = ,
New TTID = ,
New NP = ,
New NA = ;
Fig. 23 SCCP global title conversion rule
Incoming MSU
SCCP OPC DPC NI

cdPA
IMSI = 262 - 02 - 1234567890
CR SPGTCRUL:
SPGTCRUL Name= .............................................................
Addr. Info Conv. Rule= .......................................................
New TTID= .................................................................................
New NP= .....................................................................................
New NA= .....................................................................................
hybrid-IMSI = 49 - 172 - 1234567890
SCCP OPC DPC NI

cdPA
Outgoing MSU
Fig. 24 GT conversion rule for location updates
MN2513EU11MN_0001
45
© 2006 Siemens AG
3.4.6 Cancel a Global Title in the cdPA

A special version of a conversion rule is usually used to cancel a GT address in the
CALLED Party Address. This can be done e.g. in the last Gateway, because the final
destination is known there so no further GTT is necessary, or in the very first switch,
when no routing on GT is used for an outgoing message. The benefit will be that the
outgoing message is shortened and is therefore transmitted more efficiently.
The creation of this rule is very simple. The name is free, but CANGT is a very
common name. For the Addr. Info Conv. Rule parameter just enter the character
"S", which means "Stop conversion and delete all remaining digits and supplements".
All other parameters of the task are not used in this case.
TIP
As this can be done for the CALLED PARTY only, the CALLING PARTY address will
remain unchanged in the outgoing message which is routed on GT! But the CALLING
PARTY address will also be deleted, if routing on OPC/DPC (SPENS) is already
used in the first switch and the parameter CLGPA Type Indicator = Programmed of
the task CRSPCLGPA (see 3.4.1) is used.
The following rules should be noticed:

1. Message CREATED in a switch and sent with routing on OPC/DPC (SPENS):
a) Conversion Rule to delete CALLED Party address necessary (CANGT)
b) CALLING Party address automatically deleted ("Programmed")
2. Message CREATED in a switch and sent with routing on GTT (SPRNS):
a) No Conversion Rule to delete CALLED Party address allowed
b) CALLING Party address automatically included ("Programmed")
3. Message TRANSFERRED in a switch with routing on OPC/DPC (SPENS):
Switch is just STP so doesn't touch the SCCP addresses anyway
4. Message TRANSFERRED in a switch with routing on GTT (Gateway/SRP):
a) Conversion Rule to delete CALLED Party address only allowed if switch is the
VERY LAST Gateway/SRP to the final receiver, so change to routing on
OPC/DPC (SPENS)
b) CALLING Party address is still included, because the message was not
created there (so "Programmed" is not relevant) and the incoming message to
be transferred already contained a CALLING Party address
46 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP Global Title Conversion Rule to cancel GT in cdPA
CRSPGTCRUL: SPGTCRUL Name = CANGT,

Addr. Info Conv. Rule = S,
Fig. 25 Special Conversion Rule to cancel a GT in the cdPA
SIEMENS SIEMENS
Destination
Routing on OPC/DPC:
SIEMENS SIEMENS
Origin cdPA = cancelled

cgPA = not included
SIEMENS SIEMENS
STP
CRSPCLGPA:
CLGPA Type Ind=
Programmed,...; Does not touch
CRSPGTRUL: the SCCP
GTCRUL Name=CANGT,
addresses
SPENS Name=<whatever>,...;
Fig. 26 Example for CANGT with routing on OPC/DPC
SIEMENS SIEMENS
SIEMENS SIEMENS
Destination
Gateway
foreign
C:
DP
PLMN
Tit T:
own
T
le
ca lude PC/
lob on G
Ro ll G
PLMN
ell d!
Fu
PA inc O
ut lob
!
ed
al
ing a
Cd PA g on
Fu uting
on l Tit
nc
ll G
Cg utin
Ro
G T le
Ro
T:
SIEMENS SIEMENS
SIEMENS SIEMENS
Origin
Last
Gateway
CANGT to
delete cdPA
Fig. 27 Example for CANGT with routing on GTT
MN2513EU11MN_0001
47
© 2006 Siemens AG
3.4.7 Global title rule

The GT-Rule contains matching attributes ('Global Title Address Info' and 'Global
Title Translator') used to select the right GT-Rule as well as attributes that allow
translation of a global title.
The SPENS Name points to a SCCP Entity Set with a LOCAL or REMOTE Sccp
linkage. In this case, no further GTT will be performed (RI=1) because the final
destination signaling point can be determined in the own node. The global title will
NOT automatically be canceled from the SCCP called party address, so use the
CANGT conversion rule described before to keep the outgoing message as
short as possible!
The SPRNS Name points to a relay node entity set, where another GTT has to be
performed (RI=0) because the final destination signaling point can't be determined in
the own node. In this case, the global title can not be canceled from the SCCP called
party address.
Global title retranslation can be invoked by means of SPGTT Rule Reference Name
and Resume At Digit parameters which allow the selection of another GT Rule.
Include SPC indicates whether or not the SPC as the result of GTT shall additionally
be included in the SCCP called party address field of the outgoing message. NOT
RECOMMENDED!
SPGTCRUL is used to modify the address and address indicator fields in the called
party address of outgoing messages (e.g. IMSI->hybrid IMSI or CANGT).
Traffic Type provides data for traffic measurements by allowing to analyze the cdPA
without the need to analyze all possible combinations of global title digits. Possible
values are: 'Local', 'Nat. Own', 'Nat. Foreign' or International'.
48 MN2513EU11MN_0001
© 2006 Siemens AG
Create SCCP Global Title Rule
CRSPGTRUL: SPGTRUL Name = ,

SPGTTRL Name = ,
[SPGTCRUL Name = <Conversion Rule Name>,]
GT Address Info = <Global Title Digits> ,
[SPENS Name =<Entity Set without SSN>,]
[SPRNS Name = <Relay Node Set>,]
[SPGTT Rule Reference Name = ,]
[Resume At Digit = ,]
[Include SPC = ,]
[Traffic Type = ,]
Fig. 28 SCCP global title rule
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
49
© 2006 Siemens AG
50 MN2513EU11MN_0001
© 2006 Siemens AG
4 Application examples
MN2513EU11MN_0001
51
© 2006 Siemens AG
4.1 Network-internal location update

VLR and HLR within the same node
An own mobile subscriber requests a location update in a VLR that is located in the
same D900 as his HLR (i.e. they share the same message transfer part and the
same SCCP).
Location
update SIEMENS SIEMENS
MSC/VLR/HLR
IMSI=
262 02 42 12345678
SP 100
HLRISD=49 172 4200096

VLRISD=49 172 4200097
Fig. 29 Node internal location update
52 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
SCCP cdPA OPC NI+DPC
Relay Point
End Point with SSN
Global Title: End Point without SSN
GTDIG= CRSPENS:
SSID=
SPENS Name= Remote SCCP Linkage
cgPA: Local SCCP Linkage
Prim1 Name=
Prim2 Name= CRSPLNKLOC:
GT Translator Sharing Mode=
GT Translator SPLNKLOC Name=
Net Name=
CRSPGTTRL: ...
SPGTTRL Name=
TTID=
NP= Local Access Point
NA= Remote Access Point
CRSPAPREM:
SPAPREM Name=
GT Rule SPLNKREM Name=
GT Rule SSID= outgoing MSU
CRSPGTRUL: SCCP cdPA OPC NI+DPC
SPGTRUL Name=
SPGTTRL Name= GTDIG=
GT Adr Info= OPC=
SPENS Name= Global Title Conversion Rule DPC=
SPENSSSN Name= Global Title Conversion Rule SSID=
SPRNS Name= Global Title Conversion Rule NI=
SPGTCRUL Name= RI=
SPGTT Rule Ref Name= CRSPGTCRUL:
Resume at Digit= cgPA:
SPGTCRUL Name=
Include SPC= Addr Info Cov Rule=
Traffic Type= New TTID=
New NP=
New NA=
Fig. 30 GTT database
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
53
© 2006 Siemens AG
HLR and VLR in different nodes

An own mobile subscriber registers with a VLR inside his home network and, as a
result, causes an 'Update_Location' message, sent from VLR to his HLR.
IMSI=262 02 4112345678
SIEMENS SIEMENS
MSC/VLR VLRISDN=
49 172 4200097
SP 100
SIEMENS SIEMENS
HLR
Location
update
SP 200
HLRISDN=49 172 4100096
Fig. 31 Location update in HPLMN
54 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
Relay Point
Global Title: End Point with SSN
GTDIG= End Point without SSN
SSID= CRSPENS:
SPENS Name=
Prim1 Name= Remote SCCP Linkage
Prim2 Name= CRSPLNKREM:
GT Translator SPLNKREM Name=
Net Name=
CRSPGTTRL: DPC=
SPGTTRL Name= Ass. Con. Section=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name= SCCP cdPA OPC NI+DPC
SPGTTRL Name=
GT Adr Info=
GTDIG=
SPENS Name= Global Title Conversion Rule OPC=
SPENSSSN Name= Global Title Conversion Rule DPC=
SPRNS Name= Global Title Conversion Rule
NI=
SPGTCRUL Name=
CRSPGTCRUL: RI=
SPGTT Rule Ref Name=
Resume at Digit= SPGTCRUL Name= cgPA:
New NP=
New NA=
Fig. 32 GTT database
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
55
© 2006 Siemens AG
4.2 Mobile terminating call

Interrogating the HLR
A mobile subscriber dials the MSISDN of the subscriber from the previous section.
The MSC of the A-subscriber send the MAP message 'Send_Routing_Info' to the B
subscriber's HLR.
VLRISDN=491724200097
SIEMENS SIEMENS
MSC/VLR
SIEMENS SIEMENS
MSC/VLR
MSISDN=
01724112345
SP 300
SP 100
SIEMENS SIEMENS Send

Provide HLR Routing
Roaming
Info
Number
SP 200
HLRISDN=491724100096
Fig. 33 Mobile terminating call
56 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
Relay Point
SSID= CRSPENS:
SPENS Name=
Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
GTDIG=
NI=
SPGTCRUL Name=
CRSPGTCRUL: RI=
New NP=
New NA=
Fig. 34 GTT database in A-MSC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
57
© 2006 Siemens AG
Requesting an MSRN
Due to the VLRISDN, found in the mobility data of the B-subscriber, the HLR
requests an MSRN by sending 'Provide_Roaming_Number' to the visited MSC/VLR
of the B-subscriber.
VLRISDN=491724200097
SIEMENS SIEMENS
MSC/VLR
SIEMENS SIEMENS
MSC/VLR
MSISDN
SP 300
SP 100
Send
Provide SIEMENS SIEMENS
Routing
Roaming HLR Info
Number
SP 200
HLRISDN=491724100096
Fig. 35 Mobile terminating call
58 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
Relay Point
SSID= CRSPENS:
SPENS Name=
Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
GTDIG=
NI=
SPGTCRUL Name=
CRSPGTCRUL: RI=
New NP=
New NA=
Fig. 36 GTT database in B-HLR
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
59
© 2006 Siemens AG
4.3 International location update

Location update in the VLR
A roaming subscriber registers with the VLR of a foreign PLMN. The VLR sends an
'Update_Location' message via two possible gateways towards the subscriber's HLR.
The gateways are operating in loadsharing mode and are connected to the VLR on
network NAT0.
VLRISD=491724200097
IMSI= SIEMENS SI EMENS
232011234567890 MSC/VLR own

PLMN
SP 100 Location
update SIEMENS SI EMENS
Gateway
SIEMENS SIEMENS
Gateway
SP 300
SIEMENS SIEMENS
SP 200 SIEMEN S SIEMENS

PSTN
PSTN
SP 500
SP 400
SIEMENS SIEMENS
SIEMENS SIEMENS
Gateway
foreign Gateway
PLMN SIEMENS SIEMENS
MCC=232 HLR
MNC=01 SP 300
SP 200
HLRISDN=
SP 100 436641200096
Fig. 37 International location update in VLR
60 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
End Point with SSN
End Point without SSN
Global Title: Relay Point
GTDIG= CRSPRNS:
SSID=
SPRNS Name= Local SCCP Linkage
cgPA: Prim1 Name= Remote SCCP Linkage
GT Translator Back1 Name=
GT Translator Back2 Name= SPLNKREM Name=
SSID= Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
SPENS Name= GTDIG=
Global Title Conversion Rule OPC=
SPENSSSN Name= Global Title Conversion Rule
SPRNS Name= Global Title Conversion Rule DPC=
SPGTCRUL Name= SSID=
SPGTT Rule Ref Name= CRSPGTCRUL: NI=
Resume at Digit= SPGTCRUL Name= RI=
Include SPC= Addr Info Cov Rule= cgPA:
New NP=
New NA=
Fig. 38 GTT database in VLR
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
61
© 2006 Siemens AG
Location update in the own gateway

One of the own gateway switches receives the 'Update_Location' message and
forwards it to one of two possible PSTN gateways which have a connection to the
destination PLMN. The signaling connection to the PSTN is on network level NAT1
and the PSTN gateways are addressed with loadsharing.
VLRISD=491724200097
SI EMENS SI EM ENS
Own
MSC/VLR PLMN
IMSI=
232011234567890
SP 100 Location
update SI EM EN S SI EM EN S
Gateway
SIEM EN S SI EM EN S
Gateway
SP 300
SI EM ENS SI EM ENS
SP 200 SI EM EN S SIEM EN S
PSTN
PSTN
SP 500
SP 400
SIEM ENS SIEM ENS
foreign SI EM EN S SI EM ENS
Gateway
PLMN Gateway
MCC=232 SI EM EN S SI EM EN S
MNC=01 HLR HLRISD=

SP 300 436641200096
SP 200
SP 100
Fig. 39 Location update in the own gateway
62 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
End Point with SSN
GTDIG= CRSPRNS:
SSID=
SSID= Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
SPENS Name= GTDIG=
Global Title Conversion Rule
SPENSSSN Name= OPC=
New NP=
New NA=
Fig. 40 GTT database in the own gateway switches
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
63
© 2006 Siemens AG
Location update in the gateway of the destination network

The 'Update_Location' message is received in the gateway of the B-subscribers
PLMN and forwarded to his HLR.
VLRISD= 491724200097
SIEMENS SIEMENS
IMSI= MSC/VLR
Now regarded as a foreign
232011234567890 network
SP 100 Location
Update SI EMENS SIEMENS
Gateway
SI EMENS SI EMENS
Gateway
SP 300
SIEMENS SIEMENS
SP 200 SI EMENS SI EMENS

PSTN
PSTN
SP 500
Now regarded
SP 400
as the own SI EMENS SIEMENS
network SI EMENS SI EMENS

Gateway
MCC=232 Gateway
MNC=01 SIEMENS SI EMENS
HLR HLRISDN=
SP 300 436641200096
SP 200
SP 100
Fig. 41 Location update in the gateway of the destination PLMN
64 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
Relay Point
SSID= CRSPENS:
SPENS Name=
Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
GTDIG=
NI=
SPGTCRUL Name=
CRSPGTCRUL: RI=
New NP=
New NA=
Fig. 42 GTT database in the gateway of the destination PLMN
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
65
© 2006 Siemens AG
Insert subscriber data in HLR

The HLR has received the 'Update_Location' message and returns the subscriber
data to the visited VLR. The own gateways are operated in loadsharing.
VLRISD= 491724200097
SIEMENS SIEMENS
MSC/VLR Now regarded as

IMSI= a foreign network
232011234567890
SP 100
SIEM ENS SIEM EN S
Gateway
SIEM ENS SIEM EN S
Gateway
SP 300
SIEM ENS SIEM ENS
SP 200 SIEM ENS SIEM ENS

PSTN
PSTN
SP 500
Now regarded HLRISD=
SP 400
as the own SIEM EN S SIEMENS
436641200096
network SIEM ENS SIEM EN S
Gateway
MCC=232 Gateway
MNC=01 SIEM EN S SIEM ENS
HLR
SP 300
SP 200
Subscriber
Data SP 100
Fig. 43 Transmission of subscriber data in the HLR
66 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU
End Point with SSN
GTDIG= CRSPRNS:
SSID=
SSID= Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
GT Rule SSID=
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
SPENS Name= GTDIG=
SPENSSSN Name= OPC=
New NP=
New NA=
Fig. 44 GTT database in HLR
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
67
© 2006 Siemens AG
Insert subscriber data in the gateway

The subscriber data from the HLR are received by the gateways in the HLR's PLMN
which distribute them to the PSTN gateways, addressed in load sharing. Signaling
connection to the PSTN is realized on network NAT1.
VLRISD= 491724200097
SIEMENS SI EMENS
MSC/VLR Now regarded as a foreign

IMSI= network
232011234567890
SP 100
SI EMENS SIEMENS
Gateway
SI EMENS SIEMENS
Gateway
SP 300
SIEMENS SI EMENS
SP 200 SIEMENS SIEMENS

PSTN
PSTN
SP 500
SP 400
SI EMENS SI EMENS
Now regarded SI EMENS SIEMENS

Gateway
HLRISD=
as the own Gateway 436641200096
network SIEMENS SIEMENS
MCC=232 HLR
MNC=01 SP 300
SP 200
Subscriber
Data SP 100
Fig. 45 Transmission of subscriber data in the gateway
68 MN2513EU11MN_0001
© 2006 Siemens AG
incoming MSU

End Point with SSN
Relay Point
CRSPRNS:
Prim2 Name=
CRSPLNKREM:
Back1 Name=
GT Translator
Back2 Name= SPLNKREM Name=
GT Translator
SSID= Net Name=
CRSPGTTRL: DPC=
TTID=
CRSPAPREM:
SPAPREM Name=
SPLNKREM Name=
GT Rule
SSID=
GT Rule
outgoing MSU
CRSPGTRUL:
SPGTRUL Name=
SPGTTRL Name=
GT Adr Info=
SPENS Name= GTDIG=
SPENSSSN Name= Global Title Conversion Rule OPC=
SPGTCRUL Name= Global Title Conversion Rule
SSID=
Resume at Digit= RI=
Include SPC= SPGTCRUL Name=
Traffic Type= Addr Info Cov Rule= cgPA:
New TTID=
New NP=
New NA=
Fig. 46 GTT database in the gateway
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN2513EU11MN_0001
69
© 2006 Siemens AG
70 MN2513EU11MN_0001
© 2006 Siemens AG

GTT PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

GTT PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Global Title Translation Siemens

Global Title Translation

1 Routing without global title translation

Link-by-link signaling is always used for traffic channel-oriented connections. In other

Fig. 1 Routing without global title translation

2 Routing with global title translation

2.1 Why global title translation?

Global NAT1 300

Fig. 2 Why global title translation?

2.2 Examples of global title translation

Mobile terminating call

Inter MSC handover

SIEMENS SIEMENS SIEMENS SIEMENS

SIEMENS SIEMENS SIEMENS SIEMENS

SIEMENS SIEMENS SIEMENS SIEMENS

Handover new DPC

Fig. 3 Examples of global title administration

2.2.1 Location update with national / international roaming

Fig. 4 National location update

NAT0 100 NAT0 DPC=200

Global Title Net

NAT1 300 „ hybrid IMSI“

Global Title DPC=300

Global Title NAT1 DPC=300

Fig. 5 Location update with international roaming

2.2.2 National mobile terminating call

B INAP EIR MSC VLR HLR

Fig. 6 National mobile terminating call

2.2.3 International mobile terminating call

Fig. 7 International mobile terminating call

2.2.4 Mobile terminating call to an own mobile subscriber

NAT0 100 DPC=300

NAT0 Origin HLR

NAT1 300 VLRISD

3 Global title translation

3.1 SCCP calling and called party addresses

• Address indicator (mandatory):

Called and Calling Party Address structure if routing

Lenght Indicator (2)

Routing SSN SPC

SSN (e.g. VLR=7)

Length Indicator is 2 because two Global Title Indicator is 0 because no

SPC Indicator is 0 because no SPC Routing Indicator 1 means “Route on

SSN Indicator is 1 because SSN is Subsystem Number.

• Subsystem number (optional, but necessary for GSM)

2. 0010= 1 NP= ISDNTNP (ISDN telephony numbering plan,

• Encoding scheme (that information cannot be administered)

Called and Calling Party Address structure if routing

Length Indicator depends on number

Position and structure of SPC if it is

not Numbering Plan. 1=ISDNTNP,

GT digit n+1 (e.g. Filler) GT digit n (e.g. 6)

Fig. 10 Example of called/calling party addresses for international use: GT contained

3.2 Where is global title translation done?

Load Type Load Model Meaning

Create MP for Global Title Translation

Fig. 11 Creating a main processor for global title translation

3.3 Message flows

SS7-Links 64kbit/s, LTG

Fig. 12 Signaling end point, incoming MSU

SS7-Links 64kbit/s, LTG

Fig. 13 Signaling end point, outgoing MSU

3.3.2 Signaling relay point