6 Conformance to SCCP

09.163GPPGeneral Packet Radio Service (GPRS)Gs interface network service specificationServing GPRS Support Node (SGSN) - Visitors Location Register (VLR)TS

6.1 Overview

The purpose of this clause is to identify the subset of the SCCP functions which are necessary to provide addressing, error detection and segmentation facilities in the Gs interface. If this subset of SCCP functions is implemented, compatibility with a full ITU-T or ANSI SCCP shall be maintained. Only the needs of the user of SCCP (refer to GSM 09.18) are taken into account in this clause: the operations and maintenance requirements about SCCP functions are outside the scope of this technical specification.

No SCCP translation function is required in the VLR or the SGSN between the national and the local MTP. The Destination Point Code and Subsystem Number would allow direct routing by the local SCCP and MTP. Global Title addressing is supported on the Gs interface to provide flexibility in the addressing scheme implementation (note that the SGSN is assigned a global title in order to communicate with an HLR across an inter PLMN boundary).

Only connectionless class 0 SCCP services are used on the Gs interface. These simplifications are applicable to the signalling between an SGSN and a VLR in GSM PLMNs.

The minimum set of SCCP functions which apply are specified in the ITU-T Recommendations Q.711, Q.712, Q.713 and Q.714, for E1 interface and ANSI T1.112 for T1 interface with the qualifications specified in this Recommendation.

6.2 SCCP Primitives

6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation) Q.711)

– Q.711 subclause 1

– No SCCP connection-oriented services are used.

– Q.711 subclause 2

– No SCCP connection-oriented services are used. Only connectionless class 0 is used.

– Q.711 subclause 2.1

– Not applicable.

– Q.711 subclause 4.1

– Connection-oriented functions are not applicable

6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1))

T1.112.1 section 1

– No SCCP connection-oriented services are used.

T1.112.1 section 2

– No SCCP connection-oriented services are used. Only connectionless class 0.

T1.112.1 section 2.1

– Not applicable.

T1.112.1 subclause 4.1

Connection-oriented functions are not applicable

6.3 SCCP messages

6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712)

– Q.712 subclause 1.1 to 1.14

– Messages not used.

– Q.712 subclause 1.16

– The Subsystem-Out-Of-Service-Grant (SOG) message is not used.

– Q.712 subclause 1.17

– The Subsystem-Out-Of-Service-Request (SOR) message is not used.

– Q.712 subclause 2.4, 2.6, 2.7, 2.9, 2.11, 2.12, 2.13, 2.14, 2.16, 2.17

– Parameters not used.

6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2)

T1.112.2 sections 2.1 to 2.14

Messages not used.

T1.112.2 subclause 3.4

The Subsystem-Out-Of-Service-Request (SOR) message is not used.

T1.112.2 subclause 3.5

The Subsystem-Out-Of-Service-Grant (SOG) message is not used

T1.112.2 subclause 3.6

The Subsystem-Backup Routing (SBR) (Optional) message is not used.

T1.112.2 subclause 3.7

The Subsystem-Normal Routing (SNR) (Optional) message is not used.

T1.112.2 subclause 3.8

The Subsystem-Routing Status Test (SRT) (Optional) message is not used.

T1.112.2 subclauses 4. 2, 4.4, 4.6, 4.7, 4.10, 4.11, 4.12, 4.13, 4.15, 4.16, 4.17, 4.18, and 4.19

Parameters not used.

6.4 SCCP formats and codes

6.4.1 SCCP format and codes for E1 Interface ( ITU Recommendation Q.713)

– Q.713 subclause 3.4

– The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific.

– Q.713 subclause 3.4.2.2

– SSN value:

– This is a national network concern.

– Q.713 subclause 3.5

– The calling party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. .

– Q.713 subclause 3.6

– Protocol class: the classes 1, 2 and 3 are not used.

– Q.713 subclauses 3.7 3.8, 3.9, 3.10, 3.11, 3.13, 3.14, 3.15

– Parameters not used

– Q.713 subclauses 4.2 to 4.9 and 4.12 to 4.17

– Messages not used.

– Q.713 subclause 5.1.1

– SOR and SOG not needed.

6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3)

T1.112.3 subclause 3.4

– The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific.

T1.112.3 subclause 3.4.2.1

– The SSN values is a national network concern.

T1.112.3 subclause 3.5

– The calling party address shall include the appropriate sub-system number. All other aspects of SCCP addressing are network specific.

T1.112.3 subclause 3.6

– Protocol class: the classes 2 and 3 are not used.

T1.112.3 subclauses 3.7, 3.8, 3.9, 3.10, 3.11, 3.13, 3.14, 3.15

– Parameters not used

T1.112.3 subclauses 4.2 to 4.9 and 4.12 to 4.17

– Messages not used.

T1.112.3 subclause 5.1.1

SOR, SNR, SRT, SBR, and SOG not needed.

6.5 SCCP procedures

6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714)

– Q.714 subclauses 1.1.2, 1.1.3

– Protocol classes 2 and 3 not used.

– Connection-oriented services are not used.

– Q.714 subclause 1.2

– Connection-oriented services are not used.

– Q.714 subclause 1.3

– Protocol class 1 not used.

– Q.714 subclause 2.1

– The two basic categories of addresses for conectionless messages are used.

– Q.714 subclause 2.2, 2.3

– No connection-oriented message is used.

– Q.714 clause 3

– Connection-oriented procedures are not used.

– Q.714 clause 5

– Only those messages and procedures relating to non-replicated subystems or nodes are required.

6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4)

T1.112.4 subclauses 1.1.2, 1.1.3

– Protocol classes 2 and 3 not used.

– Connection-oriented services are not used.

T1.112.4 subclause 1.2

– Connection-oriented services are not used

T1.112.4 subclause 1.3

– Protocol class 1 is not used

T1.112.4 subclause 2.1

– The two basic categories of addresses for connectionless messages are used.

T1.112.4 subclause 2.2, 2.3

– No connection-oriented message is used.

T1.112.4 clause 3

– Connection-oriented procedures not used.

T1.112.4 clause 5

– Only those messages and procedures relating to non-replicated subsystems or nodes are required