ETSI EN 300 009-1 V1.4.3 (2001-02)

Integrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-oriented) to support international interconnection; Part 1: Protocol specification [ITU-T Recommendations Q.711 to Q.716 (1996), modified]

REN/SPAN-01063-1

Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Krmilni del signalizacijske zveze (SCCP) (nepovezavni in povezavni /razred 2/) za podporo mednarodnega medomrežnega povezovanja - 1. del: Specifikacija protokola [priporočila ITU-T Q.711 do Q.716 (1996), spremenjena]

General Information

• Status: Published
• Publication Date: 07-Feb-2001
• Technical Committee: SPAN 1 - Network Signalling
• Current Stage: 12 - Completion
• Due Date: 23-Feb-2001
• Completion Date: 08-Feb-2001
• Ref Project: SIST EN 300 009-1:2004 - Integrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-oriented) to support international interconnection; Part 1: Protocol specification [ITU-T Recommendations Q.711 to Q.716 (1996), modified]

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.WRNRODIntegrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-oriented) to support international interconnection; Part 1: Protocol specification [ITU-T Recommendations Q.711 to Q.716 (1996), modified]33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:3SIST EN 300 009-1:200en01-MXOLM-2003SIST EN 300 009-1:200SLOVENSKI
STANDARD



SIST EN 300 009-1:2004



Draft ETSI EN 300 009-1 V1.4.2 (1999-11)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Signalling System No.7;Signalling Connection Control Part (SCCP)(connectionless and connection-oriented)to support international interconnection;Part 1: Protocol specification[ITU-T Recommendations Q.711 to Q.716 (1996), modified]SIST EN 300 009-1:2004



ETSIDraft ETSI EN 300 009-1 V1.4.2 (1999-11)2ReferenceREN/SPAN-01063-1 (03090jdc.PDF)KeywordsCL, CO, ISDN, SCCP, SS7ETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail] copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: [e-mail] noticeThis ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific networkdrive within ETSI Secretariat.Copyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 300 009-1:2004



ETSI3Draft ETSI EN 300 009-1 V1.4.2 (1999-11)ForewordThis European Standard (Telecommunications series) has been produced by the ETSI Technical Committee Servicesand Protocols for Advanced Networks (SPAN), and is now submitted for the Public Enquiry phase of the ETSIstandards Two-step Approval Procedure.The present document is part 1 of a multi-part EN covering the Integrated Services Digital Network (ISDN); SignallingSystem No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-oriented) to supportinternational interconnection, as identified below:Part 1:" Protocol specification [ITU-T Recommendations Q.711 to Q.716 (1996), modified]";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification".The present document implies the existence of a number of functional subsets of the SCCP protocol without, however,explicitly identifying them. Depending on their functional requirements, conforming implementations would probablyonly implement a subset of the overall functions, e.g. a switch might only implement class 2 embedded, or a GSMbasestation might not handle Global Titles. The possibility of having such implementations is reflected by theoptionality of the corresponding capabilities in the PICS proforma specification ETS 300 009-2 [4].The present document also incorporates agreements made at ITU-T since the last formal issue of theQ.71x recommendations.Proposed national transposition datesDate of latest announcement of this EN (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this EN (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaEndorsement noticeThe elements of ITU-T Recommendation Q.711 to Q.716 apply, with the following modifications:SIST EN 300 009-1:2004



ETSIDraft ETSI EN 300 009-1 V1.4.2 (1999-11)4Global modifications to ITU-T Recommendations Q.711 toQ.716Insert the following three clauses (scope, normative references and abbreviations):1ScopeThe present document defines the Signalling Connection Control Part (SCCP) signalling protocol of Signalling SystemNo.7 for use in and between international relay points and gateways and, optionally, in public networks.The present document covers the use of connectionless functions (class 0 and class 1) and connection-oriented functions(class 2, excluding embedded connection set-up).NOTE:The SCCP gateway functions are relay functions that bridge two Message Transfer Part (MTP) networks.The present document is applicable to the international network and does not intend to restrict national networks.However, to facilitate SCCP interworking, its adoption within national networks is recommended.Concerning the interconnection of SCCPs, the present document is based on the assumption that the Message TransferPart (MTP) specified in ETS 300 008-1 [1] and EN 301 004-1 [2] support the SCCP.LUDT(S) messages and associated procedures need not be provided. If they are provided they shall be providedaccording to the ITU-T recommendations endorsed by the present document, unless modified herein.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.•References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.•For a specific reference, subsequent revisions do not apply.•For a non-specific reference, the latest version applies.•A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]ETS 300 008-1 (1997): "Signalling System No.7; Message Transfer Part (MTP) to supportinternational interconnection".[2]EN 301 004-1: "Signalling System No.7; B-ISDN Message Transfer Part (MTP-3b) to supportinternational interconnection".[3]EG 201 693: "Integrated Services Digital Network (ISDN); Signalling System No.7; Master list ofcodepoints" (DEG/SPAN-01065).[4]ETS 300 009-2: "Integrated Services Digital Network (ISDN); Signalling System No.7; SignallingConnection Control Part (SCCP) (connectionless and connection-oriented class 2) to supportinternational interconnection; Part 2: Protocol Implementation Conformance Statement (PICS)proforma specification".SIST EN 300 009-1:2004



ETSI5Draft ETSI EN 300 009-1 V1.4.2 (1999-11)3AbbreviationsFor the purposes of the present document, the following abbreviations apply:CCConnection Confirm messageCRConnection Request messageCREFConnection Refused messageDPCDestination Point CodeERRprotocol data unit Error messageGTGlobal TitleISDNIntegrated Services Digital NetworkISUPISDN User PartITInactivity Test messageLUDTLong Unitdata messageLUDTSLong Unitdata Service messageMTPMessage Transfer PartOPCOriginating Point CodeRIRouting IndicatorRLCRelease Complete messageRLSDReleased messageSCCPSignalling Connection Control PartSLSSignalling Link SelectionSPCSignalling Point CodeSSSubsystemSSNSubsystem NumberUDTUnitdata messageUDTSUnitdata Service messageXUDTExtended Unitdata messageXUDTSExtended Unitdata Service messageSIST EN 300 009-1:2004



ETSIDraft ETSI EN 300 009-1 V1.4.2 (1999-11)6Modifications to ITU-T Recommendation Q.711Page 7, subclause 6Class 3 is not in the scope of this EN.Page 8, subclause 6.1Permanent signalling connections are not in the scope of this EN.Page 8, subclause 6.1.1.1.2Sequence control and flow control are not in the scope of this EN.Page 10, subclause 6.1.1.2.1N-EXPEDITED DATA and N-RESET are not in the scope of this EN.Page 11, figure 8/Q.711REQUEST type 1, REQUEST type 2, REPLY, N-EXPEDITED DATA and N-RESET are not in the scope of this EN.Add the following note to figure 8/Q.711:NOTE:
ISUP requests connection setup with the REQUEST Type 1 or REQUEST Type 2 interface elements.Page 11, subclause 6.1.1.2.2Negotiation of expedited data is not in the scope of this EN.Page 13, subclause 6.1.1.2.3N-EXPEDITED DATA and N-RESET are not in the scope of this EN.Page 17, subclause 6.1.1.3.2Delete subclause 6.1.1.3.2. User part type A interface is not in the scope of this EN.Connection establishment interfaceelements are used by ISUP for the embedded setup of connections. The "quality of service parameter set" shall indicateClass 2.NOTE:
In the international network, the REQUEST Type 1 interface element would normally not be used. Thisinterface element only applies at the originating node in the national network. However, it should bepossible that ISUP performs an association ("chaining") of connection sections itself on the user level (seefigure 12 of ITU-T Recommendation Q.730 as modified by ETS 300 356-2). This may be necessary ifdifferent versions of SCCP are used in the national and international networks, or if User-to-user data istransported in the national network in another way.Page 17, subclause 6.1.2Delete subclause 6.1.2. Permanent signalling connections are not in the scope of this EN.SIST EN 300 009-1:2004



ETSI7Draft ETSI EN 300 009-1 V1.4.2 (1999-11)Page 18, subclause 6.2.1If the in-sequence delivery is not required (Protocol Class 0), the SCCP shall insert Signalling Link Selection (SLS)codes with respect to the appropriate load sharing within the signalling network. If the in-sequence delivery is required(Protocol Class 1), the SCCP, at the originating node, while adhering to the sequence control instruction from the user,shall allocate SLS codes between sequence streams with respect to appropriate load sharing within the signallingnetwork.As in relay nodes, user sequence control is not available. There shall be a fixed mapping between incoming andoutgoing SLS code values for Class 1. This mapping may be different for different signalling relations.Page 22, subclause 6.3.2.1N-COORD is only needed in nodes that contain local replicated subsystems.Page 24, subclause 6.3.2.3.1N-COORD is only needed in nodes that contain local replicated subsystems.Page 31, subclause 8.1Class 3 functions are not in the scope of this EN.Page 31, subclause 8.1.1.2Flow control is not in the scope of this EN.Expedited data support is not in the scope of this EN.Missequence detection is not in the scope of this EN.Reset is not in the scope of this EN.Page 31, subclause 8.1.2Delete subclause 8.1.2. Functions for permanent signalling connections are not in the scope of this EN.Page 32, subclause 8.3Co-ordinated state change is only needed in nodes that contain local replicated subsystems.Page 32, subclause 8.4The routing and translation function of SCCP does not apply for the embedded method.NOTE:
ISUP executes its own routing function. It provides the minimally necessary information for SCCP in theMTP-routing label and the Originating Point Code (OPC) field of the embedded request (seesubclause 3.15 of ITU-T Recommendation Q.763 as modified by ETS 300 356-1).SIST EN 300 009-1:2004



ETSIDraft ETSI EN 300 009-1 V1.4.2 (1999-11)8Modifications to ITU-T Recommendation Q.712Page 1, subclause 1.4Delete subclause 1.4. Data acknowledgement is not in the scope of this EN.Page 1, subclause 1.6Delete subclause 1.6. Data form 2 is not in the scope of this EN.Page 1, subclause 1.7Delete subclause 1.7. Expedited data is not in the scope of this EN.Page 2, subclause 1.8Delete subclause 1.8. Expedited data acknowledgement is not in the scope of this EN.Page 2, subclause 1.13Delete subclause 1.13. Reset confirm is not in the scope of this EN.Page 2, subclause 1.14Delete subclause 1.14. Reset request is not in the scope of this EN.Page 2, subclause 1.16Subsystem-out-of-service-grant is only needed in nodes that contain local replicated subsystems.Page 2, subclause 1.17Subsystem-out-of-service-request is only needed in nodes that contain local replicated subsystems.Page 4, subclause 2.4Delete subclause 2.4. Credit is not in the scope of this EN.Page 5, subclause 2.11Delete subclause 2.11. Receive sequence number is not in the scope of this EN.Page 5, subclause 2.14Delete subclause 2.14. Reset cause is not in the scope of this EN.Page 5, subclause 2.17Delete subclause 2.17. Sequencing/segmenting is not in the scope of this EN.SIST EN 300 009-1:2004



ETSI9Draft ETSI EN 300 009-1 V1.4.2 (1999-11)Modifications to ITU-T Recommendation Q.713Page 8, subclause 3.4.1Insert after the third paragraph, beginning with "A "1" in bit 2 .":On transmission of the called or calling party address, the Subsystem Number (SSN) indicator field shall always beincluded and set to 0 if unknown.Page 9, subclause 3.4.2.2, list of subsystem numbersThe SSN values recorded in the master list of codepoints [3] apply.Replace codepoint 0000 1100 ,reserved for international use, by INAP (Intelligent Network Application Protocol).NOTE:Although, there are currently no SCCP users in the international network and Aaddressing codes notstandardized within ITU-T may be exchanged subject to agreement of all concerned operators. It isrecommended to allocate SSNs in ETSI and/or ITU for all those SCCP subsystems whose messages maycross network boundaries, so that international agreement is required secured for the SSNs used. Addresscodes for the support of services not standardised in ITU-T but agreed within ETSI are recorded in [3].Page 10, subclause 3.4.2.3.1Global title indicator = 0001 is not in the scope of this EN.The NAI values recorded in the master list of codepoints [3] apply.Page 11, subclause 3.4.2.3.2Global title indicator = 0010 is not in the scope of this EN.Page 12, subclause 3.4.2.3.3Global title indicator = 0011 is not in the scope of this EN.The NP values recorded in the master list of codepoints [3] apply.Page 13, subclause 3.4.2.3.4The TT values recorded in the master list of codepoints [3] apply.Page 13, subclause 3.5Insert after the last paragraph:If segmenting/reassembly of connectionless messages or the return option are used, an unambiguous (note) identificationof the originating SCCP user (possibly complemented by additional MTP information) shall be supplied in the callingparty address.NOTE:"unambiguous" is used here as defined in ITU-T Recommendation X.650: "A name is unambiguouswithin a given scope when it identifies one and only one object within that scope. Unambiguity does notpreclude the existence of synonyms".SIST EN 300 009-1:2004



ETSIDraft ETSI EN 300 009-1 V1.4.2 (1999-11)10Page 14, subclause 3.8Delete subclause 3.8. Receive sequence number is not in the scope of this EN.Page 15, subclause 3.9Delete subclause 3.9. Sequencing/segmenting is not in the scope of this EN.Page 15, subclause 3.10Delete subclause 3.10. Credit is not in the scope of this EN.Page 16, subclause 3.13Delete subclause 3.13. Reset cause is not in the scope of this EN.Page 22, subclause 4.8Delete subclause 4.8. Data form 2 is not in the scope of this EN.Page 22, subclause 4.9Delete subclause 4.9. Data acknowledgement is not in the scope of this EN.Page 23, subclause 4.12Delete subclause 4.12. Expedited data is not in the scope of this EN.Page 24, subclause 4.13Delete subclause 4.13. Expedited data acknowledgement is not in the scope of this EN.Page 25, subclause 4.14Delete subclause 4.14. Reset request is not in the scope of this EN.Page 25, subclause 4.15Delete subclause 4.15. Reset confirm is not in the scope of this EN.Page 31, annex AAnnex A has the status of a normative annex.SIST EN 300 009-1:2004



ETSI11Draft ETSI EN 300 009-1 V1.4.2 (1999-11)Page 36, annex B.2replace items 1 and 2 with:"1) If SCCP routing is to be performed using the GT and the next SCCP relay node is outside the national networkboundary, only the GT with global title indicator (GTI) indicating "4" shall be sent in the SCCP called party address(CdPA). In addition, a SSN address element shall always be present in the SCCP called party address, and shall take oneof the following values:•if known and internationally standardized, the SSN of the called SCCP user entity, or•if known and not internationally standardized, the SSN (from the national range) for the called SCCP user entity inthe destination network, or•zero, and coded as “0" (where the identity of the called SCCP user entity is not known).A PC may be present in the SCCP called party address, but is not evaluated.If the SSN supplied in the called party address cannot be used by the destination network, the content of the GT at thefinal translation point needs to be sufficient for the translation to derive an SSN for message distribution from theSCCP at the message’s destination SP. The values of address elements of the CdPA (including the translation type [TT]and any SSN that is not internationally standard) need to be established between the operators of the end SCCP userentities.If SCCP routing is based on the SSN and the destination SCCP user is outside the national boundary, an internationallystandard Q.713 SSN shall be used and the GT may be optionally include
...