10.12.2012 Views

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2) Inter-PLMN addressing<br />

Page 39<br />

<strong>GSM</strong> <strong>09.02</strong> version <strong>5.3.0</strong>: August 1996<br />

a) Called Party Address<br />

- SSN indicator = 1 (MAP SSN always included);<br />

- Global title indicator = 0100 (Global title includes translation type, numbering plan,<br />

encoding scheme and nature of address indicator);<br />

- the translation type field will be coded "00000000" (Not used);<br />

- Routing indicator = 0 (Routing on global title);<br />

b) Calling Party Address<br />

- SSN indicator = 1 (MAP SSNs always included);<br />

- Point code indicator = 0;<br />

- Global title indicator = 0100 (Global title includes translation type, numbering plan,<br />

encoding scheme and nature of address indicator);<br />

- the translation type field will be coded "00000000" (Not used);<br />

- Routing indicator = 0 (Routing on Global Title).<br />

When an SCCP UNITDATA message is sent, the Called Party Address is derived from the Called Address<br />

of the N-UNITDATA-REQUEST primitive issued by the local TC. The Calling Party Address received in the<br />

dialogue initiating SCCP UNITDATA message is forwarded to the local TC of the dialogue responding<br />

entity as Calling Address within the N-UNITDATA-INDICATION primitive in order to be stored as Called<br />

Address for the current transaction.<br />

In the case of intra-PLMN addressing, it may be necessary to complement the Calling Party Address<br />

received in the dialogue initiating SCCP UNITDATA message by the associated Originating Point Code<br />

taken from the MTP-TRANSFER-INDICATION primitive as indicated above. In this case, the Signalling<br />

Point Code included in the Calling Address forwarded to the local TC on receipt of the dialogue initiating<br />

message is used as Destination Point Code for MTP routeing of all messages sent by the dialogue<br />

responding entity within one dialogue.<br />

For supporting the <strong>GSM</strong> protocol for inter-PLMN addressing, SCCP shall not modify the SCCP address<br />

information received in an SCCP UNITDATA message before forwarding it to the local TC. In particular,<br />

the Calling Party Address received within the dialogue initiating message shall not be complemented by a<br />

Signalling Point Code before forwarding it to TC as Calling Address in the N-UNITDATA-INDICATION<br />

primitive. Any modification of the SCCP address information received in an SCCP UNITDATA message in<br />

the case of inter-PLMN addressing constitutes a PLMN specific option.<br />

For supporting the <strong>GSM</strong> protocol, the options provided by ITU-T (03/93) SCCP for processing of the<br />

Called Address received from the local TC in the N-UNITDATA-REQUEST primitive shall be restricted as<br />

follows: If the Called Address received from TC in the N-UNITDATA-REQUEST primitive contains a Global<br />

Title, a Destination Point Code shall be established by means of Global Title translation. In the case of<br />

inter-PLMN signalling, the Global Title translation shall result in "routing on Global Title". PLMN specific<br />

requirements may cause application of a different option provided by ITU-T (03/93) SCCP.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!