ETSI ETS 300 009 ed.2 (1995-01)

SLOVENSKI STANDARD
PSIST ETS 300 009:1996
01-november-1996
Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Krmilni del
signalizacijske zveze (SCCP) (nepovezavni in povezavni) za podporo
mednarodnega vzajemnega povezovanja
Integrated Services Digital Network (ISDN); Signalling System No.7; Signalling
Connection Control Part (SCCP) [connectionless and connection-oriented] to support
international interconnection
Ta slovenski standard je istoveten z: ETS 300 009 E2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
PSIST ETS 300 009:1996 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

PSIST ETS 300 009:1996
PSIST ETS 300 009:1996
EUROPEAN ETS 300 009
TELECOMMUNICATION January 1995
STANDARD Second Edition
Source: ETSI TC-SPS Reference: RE/SPS-02003
ICS: 33.080
ISDN, SS7, SCCP
Key words:
Integrated Services Digital Network (ISDN);
Signalling System No.7;
Signalling Connection Control Part (SCCP)
[connectionless and connection-oriented]
to support international interconnection
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No 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 1995. All rights reserved.
New presentation - see History box

PSIST ETS 300 009:1996
Page 2
ETS 300 009: January 1995
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

PSIST ETS 300 009:1996
Page 3
ETS 300 009: January 1995
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Abbreviations.7
4 Requirements.8
5 Modifications to ITU-T Recommendations Q.711 to Q.714 .8
5.1 Modifications to ITU-T Recommendation Q.711 "Functional description of the
signalling connection control part" .8
5.2 Modifications to ITU-T Recommendation Q.712 "Definition and function of SCCP
messages" .11
5.3 Modifications to ITU-T Recommendation Q.713 "SCCP formats and codes" .13
5.4 Modifications to ITU-T Recommendation Q.714 "Signalling connection control part
procedures".15
6 Modifications not included in the ITU-T Recommendations.20
6.1 Compatibility issues .20
6.1.1 Interface to MTP according to ETS 300 008 .20
6.1.2 Segmenting/reassembly of connectionless messages .21
6.1.3 Embedded method.21
6.2 Additional information for the SCCP embedded method.21
6.2.1 Service request for UUS3.21
6.2.2 Treatment in transit exchanges.21
6.2.3 Failure situations .22
6.2.3.1 SCCP not existing in another network.22
6.2.3.2 Embedded method not supported by SCCP .22
6.2.3.3 ISUP fails to invoke a REQUEST TYPE 2 primitive in a
transit exchange .22
6.2.3.4 Node restarting during setup .22
6.3 Specification and Description Language (SDL) diagrams for connectionless
segmenting/reassembly.23
Annex A (informative): Bibliography.36
History.37

PSIST ETS 300 009:1996
Page 4
ETS 300 009: January 1995
Blank page
PSIST ETS 300 009:1996
Page 5
ETS 300 009: January 1995
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the Signalling
Protocols and Switching (SPS) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
This ETS further develops the Signalling System No.7 protocols for the Integrated Services Digital
Network (ISDN), Public Switched Telephone Network (PSTN) and Public Land Mobile Networks (PLMNs).
It is based on ITU-T Recommendations Q.711 to Q.714 and Q.716 (1993).
This ETS is based on the assumption concerning the interconnection of national Signalling Connection
Control Parts (SCCPs) that the Message Transfer Part (MTP) specified in ETS 300 008 (1991) supports
the SCCP for international interconnection.
This second edition of ETS 300 009 introduces:
- the use of connectionless functions in international relay points and gateways;
- the use of the connection-oriented (Class 2, with embedded connection setup only) service, which
is required to support the ISDN User-To-User Signalling Service 3 (UUS3) (see ETS 300 356-2);
- the procedures for connectionless segmentation and reassembly, needed to support the Intelligent
Network Application Protocol (INAP) and the Mobile Application Part (MAP), Version 2;
- the rules for the application of Signalling Connection Control Part (SCCP) addressing in the
international network.
In (a) later edition(s), the following features are foreseen to be added:
- the possibility of having subsystems within the international network, for example the Operations,
Maintenance and Administration Part (OMAP);
- the SCCP restart procedure;
- Open System Interconnection (OSI) adaptations to allow the use of Signalling System No.7 as
transport network for Telecommunications Management Network (TMN) information.
Proposed transposition dates
Date of latest announcement of this ETS (doa): 30 April 1995
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 October 1995
Date of withdrawal of any conflicting National Standard (dow): 31 October 1995

PSIST ETS 300 009:1996
Page 6
ETS 300 009: January 1995
Blank page
PSIST ETS 300 009:1996
Page 7
ETS 300 009: January 1995
1 Scope
This European Telecommunication Standard (ETS) defines the use of connectionless functions in
1)
international relay points and gateways , the use of the connection-oriented (Class 2, with embedded
connection setup only) service, the procedures for connectionless segmentation and reassembly, and the
rules for the application of Signalling Connection Control Part (SCCP) addressing in the international
network.
This ETS is applicable to the international network and does not intend to restrict national networks.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited as the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ITU-T Recommendation Q.711 (1993): "Specifications of Signalling System
No.7; Functional description of the signalling connection control part".
[2] ITU-T Recommendation Q.712 (1993): "Specifications of Signalling System
No.7; Definition and function of SCCP messages".
[3] ITU-T Recommendation Q.713 (1993): "Specifications of Signalling System
No.7; SCCP formats and codes".
[4] ITU-T Recommendation Q.714 (1993): "Specifications of Signalling System
No.7; Signalling connection control part procedures".
[5] ITU-T Recommendation Q.716 (1993): "Specifications of Signalling System
No.7; Signalling Connection Control Part (SCCP) performances".
[6] ETS 300 008 (1991): "Integrated Services Digital Network (ISDN); CCITT
Signalling System No.7; Message Transfer Part (MTP) to support international
interconnection".
3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
CC Connection Confirm message
CCBS Completion of Calls to Busy Subscriber
CR Connection Request message
DA Data Acknowledgement message
DPC Destination Point Code
DT2 Data Form 2 message
EA Expedited Data Acknowledgement message
ED Expedited Data message
INAP Intelligent Network Application Protocol
ISDN Integrated Services Digital Network
ISS ISDN Supplementary Services
ISUP ISDN User Part
IT Inactivity Test message
LBCS Local Broadcast Control
MAP Mobile Application Part
MTP Message Transfer Part
OMAP Operations, Maintenance and Administration Part
OPC Originating Point Code
1)
The SCCP gateway functions are relay functions that bridge two Message Transfer Part (MTP) networks.

PSIST ETS 300 009:1996
Page 8
ETS 300 009: January 1995
OSI Open System Interconnection
PLMN Public Land Mobile Network
PSTN Public Switched Telephone Network
RI Routeing Indicator
RSC Reset Confirm message
RSR Reset Request message
SCCP Signalling Connection Control Part
SCLC SCCP ConnectionLess Control
SCOC SCCP Connection-Oriented Control
SDL Specification and Description Language
SLS Signalling Link Selection
SOG Subsystem-Out-of-service-Grant message
SOR Subsystem-Out-of-service-Request message
SPAC Signalling Point Allowed Control
SPC Signalling Point Code
SPCC Signalling Point Congested Control
SPPC Signalling Point Prohibited Control
SSA SubSystem-Allowed message
SSN SubSystem Number message
SSP SubSystem-Prohibited message
SST SubSystem-status-Test message
TCAP Transaction Capabilities Application Part
TMN Telecommunications Management Network
UDT UnitDaTa message
UDTS UnitDaTa Service message
UUS User-to-User Signalling
UUS3 UUS Service 3
XUDT eXtended UnitDaTa message
XUDTS eXtended UnitDaTa Service message
4 Requirements
This ETS is based on ITU-T Recommendations Q.711 to Q.714 ([1] to [4]) and Q.716 [5]. The
requirements of these recommendations shall apply with the modifications identified in clause 5 and the
specific requirements given in clause 6 of this ETS.
NOTE: Some of the clauses in this ETS on SCCP management procedures are indicated as
"not required". In these cases, ITU-T White Book (1993) procedures may be applied if
desirable. This should not cause incompatibilities with this ETS.
5 Modifications to ITU-T Recommendations Q.711 to Q.714
The following exceptions to ITU-T Recommendations Q.711 to Q.714 ([1] to [4]) shall apply.
5.1 Modifications to ITU-T Recommendation Q.711 "Functional description of the signalling
connection control part"
§ 2 Services provided by the SCCP
Class 3 is not required.
§ 2.1 Connection-oriented services
Permanent signalling connections are not required.
§ 2.1.1.1.2 Data transfer phase
Sequence control and Flow control are not required.

PSIST ETS 300 009:1996
Page 9
ETS 300 009: January 1995
§ 2.1.1.2.1 Overview
N-CONNECT REQUEST is not required. N-EXPEDITED DATA, N-DATA ACKNOWLEDGE, and
N-RESET are not required.
§ 2.1.1.2.2 Connection establishment phase
The N-CONNECT REQUEST primitive shall not be used. Instead, the ISDN User Part (ISUP) requests
connection setup with the REQUEST TYPE 1 or REQUEST TYPE 2 interface elements.
Negotiation of expedited data is not required.
§ 2.1.1.2.3 Data transfer phase
N-EXPEDITED DATA, N-DATA ACKNOWLEDGE, and N-RESET are not required.
§ 2.1.1.3.2 Connection establishment interface elements
These interface elements are used by ISUP for the embedded setup of connections. The "receipt
confirmation selection" shall be set to false. The "quality of service parameter set" shall indicate protocol
class 2.
NOTE: In the international network, the REQUEST TYPE 1 interface element would normally
not be used. This interface element only applies at the originating node in the national
network. However, it should be possible that ISUP performs an association of
connection sections itself on user level (see ITU-T Recommendation Q.730,
figure 12/Q.730). This may be necessary if different versions of SCCP are used in the
national and international networks, or if User-to-User data are transported in the
national network in another way.
§ 2.1.2 Permanent signalling connections
Not required.
§ 2.2.1 Description
If 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 signalling network.
As in relay nodes, user sequence control is not available, there shall be a fixed mapping between
incoming and outgoing SLS code values for class 1. This mapping may be different for different signalling
relations.
§ 2.3.2.1 Overview
N-STATE and N-COORD are not required.
NOTE: N-STATE and N-COORD are not required as long as there are no (duplicated)
subsystems (other than ISUP) in the international network.
§ 2.3.2.2 Parameters
"Affected subsystem", "Subsystem multiplicity indicator", "User status" and "Remote SCCP status" are not
required.
PSIST ETS 300 009:1996
Page 10
ETS 300 009: January 1995
§ 2.3.2.3.1 COORD
N-COORD is not required.
NOTE: N-COORD is not required as long as there are no (duplicated) subsystems (other than
ISUP) in the international network.
§ 2.3.2.3.2 STATE
Subsystem management is not required.
NOTE: Subsystem management is not required as long as there are no (duplicated)
subsystems (other than ISUP) in the international network.
§ 3.2 Primitives and parameters
The "cause" parameter in the MTP-STATUS primitive may take the values:
- "Signalling point congested";
- "User part unavailable".
For the cause "Signalling point congested", no congestion priorities are used.
NOTE: The values:
- "User part unavailability: unknown";
- "User part unavailability: unequipped remote user";
- "User part unavailability: inaccessible remote user",
occur in ITU-T Recommendation Q.701, § 8. The first one corresponds to "User part
unavailable" in ETS 300 008 [6], the latter two are not part of ETS 300 008 [6].
§ 3.2.4 STATUS
The "cause" parameter in the MTP-STATUS primitive may take the values:
- "Signalling point congested";
- "User part unavailable".
For the cause "Signalling point congested", no congestion priorities are used.
NOTE: The values:
- "User part unavailability: unknown";
- "User part unavailability: unequipped remote user";
- "User part unavailability: inaccessible remote user",
occur in ITU-T Recommendation Q.701, § 8. The first one corresponds to "User part
unavailable" in ETS 300 008 [6], the latter two are not part of ETS 300 008 [6].
§ 4.1 Connection-oriented functions
Class 3 functions are not required.
§ 4.1.1.2 Data transfer function
Flow control is not required.
Expedited data support is not required.
Missequence detection is not required.
Reset is not required.
Receipt confirmation is not required.

PSIST ETS 300 009:1996
Page 11
ETS 300 009: January 1995
§ 4.1.2 Functions for permanent signalling connections
Not required.
§ 4.3 Management functions
Co-ordinated state change is not required.
NOTE: Co-ordinated state change is not required as long as there are no (duplicated)
subsystems (other than ISUP) in the international network.
§ 4.4 Routeing and translation functions
The routeing and translation function of SCCP does not apply for the embedded method.
NOTE: ISUP executes its own routeing function. It provides the minimally necessary
information for SCCP in the MTP-routeing label and the Originating Point Code (OPC)
field of the embedded request (see ITU-T Recommendation Q.763, § 3.15).
5.2 Modifications to ITU-T Recommendation Q.712 "Definition and function of SCCP
messages"
§ 1.2 Connection Request (CR)
Not required (only embedded connection requests are issued).
§ 1.4 Data Acknowledgement (DA)
Not required.
§ 1.6 Data Form 2 (DT2)
Not required.
§ 1.7 Expedited Data (ED)
Not required.
§ 1.8 Expedited Data Acknowledgement (EA)
Not required.
§ 1.13 Reset Confirm (RSC)
Not required.
§ 1.14 Reset Request (RSR)
Not required.
§ 1.15 SubSystem-Allowed (SSA)
Not required.
§ 1.16 Subsystem-Out-of-service-Grant (SOG)
Not required.
§ 1.17 Subsystem-Out-of-service-Request (SOR)
Not required.
PSIST ETS 300 009:1996
Page 12
ETS 300 009: January 1995
§ 1.18 SubSystem-Prohibited (SSP)
Not required.
§ 1.19 SubSystem-Status-Test (SST)
Not required.
§ 2.4 credit
Not required.
§ 2.6 diagnostic
Not required.
§ 2.11 receive sequence number
Not required.
§ 2.14 reset cause
Not required.
§ 2.17 sequencing/segmenting
Not required.
§ 2.18 subsystem multiplicity indicator
For further study.
§ 3 Inclusion of fields in messages
Table 1/Q.712: Inclusion of fields in messages and
Table 2/Q.712: SCCP management messages
Management messages are not required.

PSIST ETS 300 009:1996
Page 13
ETS 300 009: January 1995
5.3 Modifications to ITU-T Recommendation Q.713 "SCCP formats and codes"
§ 3.4.1 Address indicator
On transmission of the called party address, the SubSystem Number (SSN) indicator field shall always be
included and set to 0 if unknown.
Bit 8 (reserved for national use) shall always be coded 0 and is not evaluated.
§ 3.4.2.2 Subsystem number
Except for ISUP, there are currently no SCCP-users in the international network. Nevertheless, SSNs
have to be allocated for all those SCCP subsystems whose messages may cross network borders, so that
international agreement is needed for the SSNs used. If not yet specified by ITU-T, such SSNs will be
taken up in this ETS. In addition to the SSNs allocated already in ITU-T Recommendation Q.713 [3], one
additional SSN is necessary for ISDN Supplementary Services (ISS) to identify the services (completion of
calls to busy subscribers, reverse charging, etc.) that are based on the Transaction Capabilities
Application Part (TCAP). The value 0000 1011 is allocated for ISS.
Bits 8 7 6 5 4 3 2 1
.
.
0 0 0 0 1 0 1 1 ISDN Supplementary Services (ISS)
0 0 0 0 1 1 0 0 }
to } spare
1 1 1 1 1 1 1 0 }
1 1 1 1 1 1 1 1 reserved for expansion
§ 3.4.2.3.1 Global title indicator = 0001
Not required for transmission.
§ 3.4.2.3.2 Global title indicator = 0010
Not required for transmission.
For use by the Completion of Calls to Busy Subscriber (CCBS) supplementary service, one value is
allocated for the translation type.
Bits 8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 not used
.
.
0 0 0 1 0 0 0 1 ISDN end-to-end supplementary services (e.g. CCBS)
.
.
1 1 1 1 1 1 1 1 reserved for expansion
NOTE: The CCBS supplementary service uses Global title indicator = 0100 (see
ETS 300 356-18). However, the translation type is defined in § 3.4.2.3.2 of ITU-T
Recommendation Q.713 [3] and referred to in the subsequent paragraphs covering
Global title indicator values 0011 and 0100.
§ 3.4.2.3.3 Global title indicator = 0011
Not required for transmission.

PSIST ETS 300 009:1996
Page 14
ETS 300 009: January 1995
§ 3.5 Calling party address
For the international network, if segmenting/reassembly of connectionless messages or the return option
is used, it is necessary to supply in the calling party address a unique identification of the originator.
Inclusion of a global title, uniquely identifying the caller would be sufficient for this purpose. The "address
indicator" field shall then never be coded as the "all zeroes" value.
§ 3.8 Receive sequence number
Not required.
§ 3.9 Sequencing/segmenting
Not required.
§ 3.10 Credit
Not required.
§ 3.13 Reset cause
Not required.
§ 4.2 Connection request
Not required (only embedded connection requests are issued).
§ 4.8 Data form 2
Not required.
§ 4.9 Data acknowledgement
Not required.
§ 4.12 Expedited data
Not required.
§ 4.13 Expedited data acknowledgement
Not required.
§ 4.14 Reset request
Not required.
§ 4.15 Reset confirm
Not required.
§ 5 SCCP management messages and codes
Subsystem management messages are not required.
NOTE: Subsystem management messages are not required as long as no subsystems (other
than ISUP) are introduced in the international network.

PSIST ETS 300 009:1996
Page 15
ETS 300 009: January 1995
5.4 Modifications to ITU-T Recommendation Q.714 "Signalling connection control part
procedures"
§ 1.1.2 Protocol classes
Class 3 procedures are not required.
§ 1.1.2.2 Protocol class 1
The in-sequence delivery not only relies on the properties of the MTP-network, but also SCCP shall
guarantee the sequential processing of SCCP-messages. This excludes e.g. arbitrary parallel processing
of global title translations in relay nodes.
§ 1.1.2.3 Protocol class 2
Only the embedded method of connection setup is required.
§ 1.1.2.4 Protocol class 3
Not required.
§ 1.1.3 Signalling connections
NOTE: The ITU-T White Book (1993) leaves the possibility of having relay points without
coupling for connection-oriented services for further study. This because it is not clear
how a connection can be completed (with a Connection Confirm (CC) message) to the
originator without changing or including the calling address parameter of the
Connection Request (CR) message in relay nodes.
For the embedded method, there is in fact the possibility of having no association in an
ISUP relay point (ISUP would in this case simply pass the embedded request further
on, without issuing a REQUEST TYPE 2). This is in this case no problem, since the
OPC of the originating node or of the last relay node with coupling is included in the
embedded connect request of the IAM message. It is therefore always possible to
route back the CC message to the correct originator.
§ 1.2.1 Connection establishment
The CR message is not used. The connection request is carried embedded in an ISUP message instead.
NOTE: See also the note relating to § 1.1.3.
The ISUP has the control whether the association of connection sections shall be performed or not. If the
SCCP receives a REQUEST TYPE 2 from ISUP with the "reply bit" set, an association of connection
sections shall be performed.
§ 1.2.2 Data transfer
Flow control is not required.
Expedited data support is not required.
Missequence detection is not required.
Reset is not required.
Receipt confirmation is not required.

PSIST ETS 300 009:1996
Page 16
ETS 300 009: January 1995
§ 2.2.2 Messages from connection-oriented or connectionless control to SCCP routeing
control
In order to route an SCCP message from one country to another, a global title shall always be available.
Therefore, the possibility of routeing on Destination Point Code (DPC) and SSN shall not apply for the
transit traffic in the international network.
NOTE 1: Routeing on DPC and SSN does not apply as long as no subsystems (other than
ISUP) are introduced in the international network.
For routeing from one network to another, passing through the international network, the Routeing
Indicator (RI) shall always be set to route on global title.
NOTE 2: The routeing of the embedded connect requests for ISUP, is not done by SCCP, but by
ISUP itself. The other connection-oriented messages are routed on DPC only.
§ 3 Connection-oriented procedures
Class 3 procedures are not required.
§ 3.1.1 General
N-CONNECT REQUEST is not required.
§ 3.1.3.1 Protocol class negotiation
If a connection request for protocol class 3 is received, it
...