7 Addressing of SCCP layer messages on the SSAP interface

09.133GPPSignalling interworking between ISDN supplementary services Application Service Element (ASE) and Mobile Application Part (MAP) protocolsTS

The SCCP layer addressing for messages on the SSAP interface is described.

7.1 Use of SCCP

Clarifications and restrictions on the use and coding of the main SCCP parameters impacted by CCBS on the SSAP interface are indicated. See ETS 300 356-18 and the associated references for the full specification on the use of SCCP on the SSAP interface. The SCCP routeing on the SSAP interface shall be based on the Global Title (GT) translation mechanism as for routeing on the international interface. GT addressing shall be used for inter and intra PLMN signalling. This allows any impact of other network features e.g. Mobile Number Portability to be minimised.

7.2 Addressing of messages at the originating PLMN

7.2.1 TC-BEGIN message from the originating network HLR

The relevant SCCP parameters in the first message from the HLR A transporting TC-BEGIN are shown in table 7.1. All other SCCP parameters shall be as indicated in ETS 300 356-18.

Table 7.1: SCCP parameters used by HLR A for TC-BEGIN

SCCP PARAMETERS for the message
transporting TC-BEGIN

PARAMETER VALUE

CdPA-Called Party Address

E.164 number of the Called Party. This may be in either international or national E.164 format, see subclause 7.4.1. It is derived from the translatedB-Number parameter which is available from the CCBS application in HLRA, see RegisterCCEntry in GSM 09.02.

CgPA-Calling Party Address

E.164 number of HLR A. This may be in either international or national E.164 format, see subclause 7.4.1.

SSN- Subsystem Number

0000 1011
(See ETS 300 356-18)

TT- Translation Type

0001 0001
(See ETS 300 356-18)

Other SCCP Parameters

See ETS 300 356-18

7.2.2 TC-CONTINUE, TC-END messages from the originating network HLR

The relevant SCCP parameters in the subsequent messages from the HLR A transporting TC-CONTINUE and TC-END are shown in table 7.2. All other SCCP parameters shall be as indicated in ETS 300 356-18.

Table 7.2: SCCP parameters used by HLR A for TC-CONTINUE, TC-END

SCCP PARAMETERS for the message
transporting TC-CONTINUE, TC-END

PARAMETER VALUE

CdPA-Called Party Address

The Called Party Address is the E.164 address of the calling entity in the destination network that was received in the first response message from the destination network (note 1).

CgPA-Calling Party Address

E.164 number of HLR A. This may be in either international or national E.164 format as used in the message transporting TC-BEGIN, see subclause 7.4.1.

SSN- Subsystem Number

0000 1011
(See ETS 300 356-18)

TT- Translation Type

0001 0001
(See ETS 300 356-18)

Other SCCP Parameters

See ETS 300 356-18

NOTE 1 If the destination network is a GSM PLMN, this is E.164 number of HLR B.

7.3 Addressing of messages at the destination PLMN

7.3.1 TC-CONTINUE, TC-END messages from the destination network HLR

The relevant SCCP parameters in the first and subsequent messages from the HLR B transporting TC-CONTINUE and TC-END are shown in table 7.3. All other SCCP parameters shall be as indicated in ETS 300 356-18.

Table 7.3: SCCP parameters for TC-CONTINUE, TC-END used by HLR B

SCCP PARAMETERS for the message
transporting TC-CONTINUE, TC-END

PARAMETER VALUE

CdPA-Called Party Address

The Called Party Address is the E.164 address of the calling entity in the originating network that was received in the first message transporting TC-BEGIN from the originating network (note 1).

CgPA-Calling Party Address

E.164 number of HLR B. This may be in either international or national E.164 format, see subclause 7.4.2 (note 2)

SSN- Subsystem Number

0000 1011
(See ETS 300 356-18)

TT- Translation Type

0001 0001
(See ETS 300 356-18)

Other SCCP Parameters

See ETS 300 356-18

NOTE 1 If the originating network is a GSM PLMN, this is E.164 number of HLR A.

NOTE 2 The E.164 number of HLRB is used as this allows any impact of other network features to be minimised.

7.4 Number formats of the SCCP address parameters

The Called and Calling Party Address information in SCCP should be in international E.164 format. Optionally national format E.164 addresses may be used in SCCP for routeing of national traffic. For this, the HLR has to modify the addresses which are in international E.164 format to a national E.164 format. If a national format E.164 option is used, all involved network nodes in a given country (i.e. the originating network, any transit networks and the destination network) need support that option. As negotiation is not possible, the option selected by the originating network shall determine the addressing used for all messages which are a part of a single dialogue.

7.4.1 Originating PLMN

The Called and Calling Party Address information in SCCP should be in international E.164 format.

The originating network HLR A may use the SCCP Called Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A.

The originating network HLR A may use the SCCP Calling Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A.

The originating network HLR A shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format.

7.4.2 Destination PLMN

The Called and Calling Party Address information in SCCP should be in international E.164 format.

The destination network HLR B may use the SCCP Called Party Address in national E.164 format if the originating network is in the same country as HLR B.

The destination network HLR B may use the SCCP Calling Party Address in national E.164 format if the originating network is in the same country as HLR B.

The destination network HLR B shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format.

Annex A (informative):
Status of Technical Specification GSM 09.13

Status
of
Technical Specification GSM 09.13

Date

Version

Remarks

May 1998

version 0.0.0

First draft

June 1998

version 0.1.0

Revision 1. Various editorial changes made. Open issues marked as {FFS} Version 0.1.0 – in Tdoc 98P151, from SMG 3 Plenary, Chester, UK.

June 1998

version 0.1.1

GSM 09.13 to SMG#26 for first information and to SPS1

July 1998

version 0.2.0

GSM 09.13 to SMG3 WPB, Stuttgart 10 – 14 August 1998.

August 1998

version 0.3.0

GSM 09.13 to SMG3, SMG3 WPC., September 1998.

September 1998

version 0.4.0

GSM 09.13 to SMG3, September 1998.

October 1998

version 2.0.0

To SMG#27 for approval

October 1998

version 6.0.0

Specification approved by SMG#26 for Release 97

August 1999

version 7.0.0

Specification version upgrade to Release 1998 version 7.0.0

Text and figures: word 6.0
Stylesheet: etsiw_70.dot
Rapporteur: Sunil Chotai (Cellnet)