ETSI EN 300 009-2: Final Draft V1.4.1

Final draft
ETSI EN 300 009-2 V1.4.1 (2001-12)

European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);

Signalling System No.7;
Signalling Connection Control Part (SCCP)
(connectionless and connection-oriented class 2)
to support international interconnection;
Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification
Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)
Reference
REN/SPAN-130063-2
Keywords
CL, CO, ISDN, SS7, SCCP, PICS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N 348 623 562 00017 - NAF 742 C
Association but non lucratif enregistre la
Sous-Prfecture de Grasse (06) N 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[email protected]
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 2001.
All rights reserved.
ETSI
Contents
Intellectual Property Rights ................................................................................................................................4
Foreword.............................................................................................................................................................4
Introduction ........................................................................................................................................................4
1
Scope ........................................................................................................................................................5
References ................................................................................................................................................5
Definitions and abbreviations...................................................................................................................6
3.1
3.2
Definitions..........................................................................................................................................................6
Abbreviations .....................................................................................................................................................6
Conformance ............................................................................................................................................7
Annex A (normative):
A.1
Guidance for completing the PICS proforma...........................................................................................8
A.1.1
A.1.2
A.1.3
A.2
PICS proforma for EN 300 009-1...................................................................8
Purposes and structure........................................................................................................................................8

Abbreviations and conventions ..........................................................................................................................8
Instructions for completing the PICS .................................................................................................................9
Identification of the implementation ......................................................................................................10
A.2.1
A.2.2
A.2.3
A.2.4
A.2.5
A.2.6
Date of the statement ........................................................................................................................................10

Implementation Under Test (IUT) identification .............................................................................................10
System Under Test (SUT) identification ..........................................................................................................10
Product supplier................................................................................................................................................10
Client ................................................................................................................................................................11
PICS contact person .........................................................................................................................................11
A.3
Identification of the protocol..................................................................................................................12
A.4
Global statement of conformance...........................................................................................................12
A.5
Capabilities.............................................................................................................................................12
A.5.1
A.5.1.1
A.5.1.2
A.5.1.3
A.5.2
A.5.3
A.5.4
A.5.5
A.5.6
A.5.7
A.5.8
General requirements .......................................................................................................................................12

Implemented class ......................................................................................................................................12
SCCP routeing capabilities .........................................................................................................................13
Called/Calling party address parameter ......................................................................................................14
Major capabilities - SCCP management...........................................................................................................14
Major capabilities - connectionless SCCP........................................................................................................15
Major capabilities - connection-oriented SCCP ...............................................................................................16
Timers used in SCCP .......................................................................................................................................18
Messages ..........................................................................................................................................................18
Message parameters .........................................................................................................................................19
Multi-layer dependencies .................................................................................................................................22
Annex B (informative):
Bibliography...................................................................................................23
History ..............................................................................................................................................................24
ETSI
Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN), and is now submitted for the ETSI standards One-step Approval Procedure.
The present document is part 2 of a multi-part deliverable covering the Integrated Services Digital Network (ISDN);
Signalling System No.7; Signalling Connection Control Part (SCCP) (connectionless and connection-oriented) to
support international 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".
Proposed national transposition dates

Date of latest announcement of this EN (doa):
3 months after ETSI publication
Date of latest publication of new National Standard

or endorsement of this EN (dop/e):
6 months after doa
Date of withdrawal of any conflicting National Standard (dow):
6 months after doa
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and
options have been implemented for a given OSI protocol. Such a statement is called a Protocol Implementation
Conformance Statement (PICS).
ETSI
Scope
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Signalling
Connection Control Part (SCCP) signalling protocol of Signalling System No.7 for use between and, optionally, in
public networks as specified in EN 300 009-1 [1] in compliance with the relevant requirements and in accordance with
the relevant guidance given in ISO/IEC 9646-7 [4].
The supplier of a protocol implementation that is claimed to conform to EN 300 009-1 [1] is required to complete a
copy of the PICS proforma provided in annex A of the present document and is required to provide the information
necessary to identify both the supplier and the implementation.
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies.
[1]
ETSI EN 300 009-1 (V1.4.3): "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]".
[2]
ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing

methodology and framework - Part 1: General concepts".
[3]
ITU-T Recommendation Q.701: "Functional description of the message transfer part (MTP) of
Signalling System No. 7".
[4]
ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing

methodology and framework - Part 7: Implementation Conformance Statements".
[5]
ITU-T Recommendation Q.1400: "Architecture framework for the development of signalling and
OA&M protocols using OSI concepts".
[6]
ITU-T Recommendation Q.711: "Functional description of the signalling connection control part".
[7]
ITU-T Recommendation Q.712: "Definition and function of signalling connection control part
messages".
[8]
ITU-T Recommendation Q.713: "Signalling connection control part formats and codes".
[9]
ITU-T Recommendation Q.714: "Signalling connection control part procedures".
[10]
ITU-T Recommendation Q.704: "Signalling network functions and messages".
[11]
ITU-T Recommendation Q.716: "Signalling System No. 7 - Signalling connection control part
(SCCP) performance".
ETSI
Definitions and abbreviations
3.1
Definitions
For the purposes of the present document, the terms and definitions given in EN 300 009-1 [1], ISO/IEC 9646-1 [2] and
ISO/IEC 9646-7 [4] apply:
Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system
claimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take
several forms: protocol ICS (PICS), profile ICS, profile specific ICS, and information object ICS.
Protocol Implementation Conformance Statement (PICS): ICS for an implementation or system claimed to conform
to a given protocol specification
PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes a PICS
3.2
Abbreviations
For the purposes of the present document, the following abbreviations apply:
AK
c
CC
CR
CREF
DPC
DT1
DT2
EA
ED
ERR
GT
i
ICS
ISDN
IT
IUT
LUDT
LUDTS
m
MTP
n/a
o
OSI
PDU
PICS
RLC
RLSD
RSC
RSR
SCCP
SCS
SOG
SOR
SPC
SSA
SSC
SSN
data AcKnowledgement message

conditional
Connection Confirm message
Connection Request message
Connection REFused message
Destination Point Code
Data Form 1 message
Data Form 2 message
Expedited data Acknowledgement message
Expedited Data message
protocol data unit ERRor message
Global Title
irrelevant
Implementation Conformance Statement
Integrated Services Digital Network
Inactivity Test message
Implementation Under Test
Long Unit DaTa message
Long Unit DaTa message Service
mandatory
Message Transfer Part
not/applicable
optional
Open System Interconnection
Protocol Data Unit
Protocol Implementation Conformance Statement
ReLease Complete message
ReLeaSeD message
ReSet Confirm message
ReSet Request message
Signalling Connection Control Part
System Conformance Statement
Subsystem Out of service Grant message
Subsystem Out of service Request message
Signalling Point Code
SubSystem Allowed message
SubSystem Congested
SubSystem Number
ETSI
SSP
SST
SUT
UDT
UDTS
x
XUDT
XUDTS
SubSystem Prohibited message

Subsystem Status Test message
System Under Test
UnitDaTa message
UnitDaTa Service message
eXcluded
eXtended UnitDaTa message
eXtended UnitDaTa Service message
Conformance
A PICS proforma that conforms to this PICS proforma specification shall be technically equivalent to annex A, and
shall preserve the numbering and ordering of the items in annex A.
A PICS that conforms to this PICS proforma specification shall:
a) describe an implementation which conforms to EN 300 009-1 [1];
b) be a conforming PICS proforma, which has been completed in accordance with the instructions for
completion given in clause A.1;
c) include the information necessary to uniquely identify both the supplier and the implementation.
ETSI
Annex A (normative):
PICS proforma for EN 300 009-1
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PICS.
A.1
Guidance for completing the PICS proforma
A.1.1
Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in EN 300 009-1 [1] may provide information about the implementation in a standardized manner.
The PICS proforma is subdivided into clauses for the following categories of information:
guidance for completing the PICS proforma;
identification of the implementation;
identification of the protocol;
global statement of conformance;
explicit statements about the implemented capabilities.
A.1.2
Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the
guidelines presented in ISO/IEC 9646-7 [4].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is <item description> supported by the implementation?"
Status column
The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:
m
mandatory - the capability is required to be supported.
optional - the capability may be supported or not.
n/a
not applicable - in the given context, it is impossible to use the capability.
prohibited (excluded) - there is a requirement not to use this capability in the given context.
o.i
qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which
identifies an unique group of related optional items and the logic of their selection which is
defined immediately following the table.
ETSI
ci
conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying an unique conditional status
expression which is defined immediately following the table.
c:
Conditional upon the immediately previous item at the next higher level.
irrelevant - this capability is outside the scope of the given base standard and hence irrelevant and
not subject to conformance testing. No answer is requested from the supplier.
Reference column
The reference column gives reference to ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as
modified by EN 300 009-1 [1], except where explicitly stated otherwise.
NOTE 1: However, a reference merely indicates the place where the core of a description of an item can be found.
Any additional information contained in EN 300 009-1 [1] needs to be taken into account when making a
statement about the conformance of that particular item.
Support column
The support column shall be filled in by the supplier of the implementation. The following common notations, defined
in ISO/IEC 9646-7 [4], are used for the support column:
Y or y
supported by the implementation.
N or n
not supported by the implementation.
N/A, n/a or -
no answer required (allowed only if the status is n/a or i, directly or after evaluation of a
conditional status c).
NOTE 2: For automatic test selection, a N/A after evaluation of a conditional status has to be interpreted as not
supported (N or n).
NOTE 3: As stated in ISO/IEC 9646-7 [4], support for a received PDU requires the ability to parse all valid
parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is
non-conformant. Support for a parameter of a PDU implies that the semantics of that parameter are
supported.
If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able
to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall
enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in the
space for comments provided at the bottom of the table. It uses predicates defined in the System Conformance
Statement (SCS), each of which refers to a single profile and which takes the value TRUE if and only if that profile is to
be used.
EXAMPLE:
?3: IF prof1 THEN Y ELSE N
References to items
For each possible item answer (answer in the support column) within the PICS proforma exists a unique reference,
used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/",
followed by the item number in the table.
EXAMPLE:
A.1.3
A.5/4 is the reference to the answer of item 4 in table A.5 of annex A.
Instructions for completing the PICS
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an
explicit answer shall be entered in each of the support boxes provided, using the notation described in clause A.1.2.
If necessary, the supplier may provide additional comments in the space at the bottom of the tables or separately.
More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
ETSI
10
A.2
Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test
(SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration
options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
A.2.1
Date of the statement
.........................................................................................................................................................................................
A.2.2
Implementation Under Test (IUT) identification
IUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
IUT version:
.........................................................................................................................................................................................
A.2.3
System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Operating system:
.........................................................................................................................................................................................
A.2.4
Product supplier
Name:
.........................................................................................................................................................................................
Address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
ETSI
11
Telephone number:
.........................................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
Additional information:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.2.5
Client
Name:
.........................................................................................................................................................................................
Address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.2.6
PICS contact person
Name:
.........................................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................................
ETSI
12
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.3
Identification of the protocol
This PICS proforma applies to the following standard:

EN 300 009-1 (V1.4.3): "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]".
A.4
Global statement of conformance
Does the implementation described in this PICS meet all the mandatory requirements of the referenced standard?
[ ] Yes [ ] No
NOTE:
Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported
mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is
non-conforming. Explanations may be entered at the bottom of each table or be attached to the PICS
proforma.
The supplier of the implementation will have fully complied with the requirements for a statement of conformance by
completing the tabulations contained in the following clause.
A.5
Capabilities
This clause contains the core of the PICS proforma for the SCCP protocol specified in Q.711 [6], Q.712 [7], Q.713 [8]
and Q.714 [9] as modified by EN 300 009-1 [1]. The proforma are presented in the form of tables.
NOTE:
A.5.1
The compatibility capabilities with CCITT Blue Book (1988) and CCITT Red Book (1984)
Recommendations are for further study (ffs).
General requirements
A.5.1.1 Implemented class

The supplier of the implementation shall state whether or not the following service classes are supported.
ETSI
13
Table A.1: Service Class

Item
Service Class
Reference
Status
Support
1/1 Class 0
Q.714, clause 1.1.2.1 m (see note)
1/2 Class 1
Q.714, clause 1.1.2.2 o
1/3 Class 2
Q.714, clause 1.1.2.3 o
1/4 Class 3
Q.714, clause 1.1.2.4 i
NOTE:
A.4/7, remote SCCP unavailability management is mandatory, consequently
class 0 is mandatory.
Comments:
A.5.1.2 SCCP routeing capabilities

The supplier of the implementation shall state whether or not the following routing functionalities are supported.
Table A.2: Routeing functionalities
Item
Routeing functionality
2/1 End node
2/1.1 Outgoing routing to remote subsystem after Global Title translation
in own node (input: GT+[SSN])
2/1.2 Outgoing routing to relay node after Global Title translation in own
node (input: GT+[SSN])
2/1.3 Outgoing routing to relay node identified by user (input:
DPC+GT+[SSN])
2/1.4 Incoming routing with translation to local subsystem (received:
GT+[SSN] )
2/1.5 Internal routing to local subsystem (input: own SPC +SSN+[GT])
2/1.6 Internal routing with Global Title translation to local subsystem
(input: GT+[SSN] )
2/2 Relay node
2/2.1 Incoming routing with translation to remote subsystem (received:
GT+[SSN] )
2/2.2 Incoming routing with translation to relay node
(received: GT+[SSN])
2/2.3 Hop counter protection
2/2.4 Coupling of connection sections
2/3 Translation with selection of backup if the GT translation leads to
an unavailable SCCP subsystem in the primary node
2/4 Translation with selection of backup if the GT translation leads to
an unavailable point code or SCCP in the primary node
2/5 Capabilities to generate a new GT
2/6 Capabilities to generate a new SSN
2/7 Outgoing routing to remote subsystem (input: DPC+SSN+[GT])
2/8 Incoming routing to local subsystem (received: [DPC]+SSN+[GT])
2/9 Compatibility Test
Reference
Q.714, clause 2.3
Q.714, clause 2.3
Status
o.21
c:o.22
Q.714, clause 2.3
c:o.22
Q.714, clause 2.3
c:o.22
Q.714, clause 2.3
c:o.22
Q.714, clause 2.3

Q.714, clause 2.3
c:o
c:o
Q.714, clause 2.3

Q.714, clause 2.3
o.21
c:o.23
Q.714, clause 2.3
c:o.23
Q.714, clause 2.3

Q.714, clause 2.3
Q.714, clause 2.3
c:m
c:c.24
o
Q.714, clause 2.3
o
o
m
m
c25
(see note)
2/10 Traffic limitation mechanism (importance parameter)
Q.714, clause 2.6.2 o
NOTE:
When inter-working with networks only supporting SCCP versions prior to the 1993 edition is required, the
compatibility test capability is mandatory.
o.21: support of at least one of these options is mandatory

c.24: IF A.1/3 THEN o ELSE n/a
-- Class 2 implemented
c.25: IF A.2/2 THEN o ELSE n/a
-- Relay node role
Comments:
ETSI
Q.714, clause 2.3

Q.714, clause 2.3
Q.714, clause 2.3
Q.714, clause 2.3
Q.714, clause 2.5
Support
14
A.5.1.3 Called/Calling party address parameter

As these parameters include a lot of options, it is necessary that the supplier of the IUT enter which options are set in
his Called/Calling party address parameter.
Table A.3: Called/Calling party address options
Item
Option
Reference
Status
Support
Required
3/1
3/2
3/3
3/4
3/5
3/6
3/7
Translation Type
Numbering Plan
Nature of the address
Global title indicators
Point code indicator
SSN indicator
Routeing Indicator
Q.713, clause 3.4

Q.713, clause 3.4
Q.713, clause 3.4
Q.713, clause 3.4
Q.713, clause 3.4
Q.713, clause 3.4
Q.713, clause 3.4
Values
Supported
c.31 (see note 1)

c.31 (see note 1)
c.31 (see note 1)
m
m (see note 1)
m (see note 2)
m (see note 1)
0
1..7
4
0,4
0/1
1
Route-on-SSN,
Route-on-GT
NOTE 1: Which values have to be supported depends on the applications served by the SCCP implementation. For
international applications, annex E of ITU-T Recommendation Q.714 [9] as modified by EN 300 009-1 [1]
applies.
NOTE 2: According to EN 300 009-1 [1], the SSN shall always be included in an address on sending a message.
c.31: IF A.2/1.2 OR A.2/1.3 OR A.2/1.4 OR A.2/2 THEN m ELSE o
-- Routeing capabilities with global title

translation.
Comments:
A.5.2
Major capabilities - SCCP management
The supplier of the implementation shall state whether or not the (signalling) SCCP management procedures specified
in ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as modified by EN 300 009-1 [1] are
supported, in table A.4.
Table A.4: SCCP management procedures
Item
4/1
4/2
4/3
4/4
4/5
4/6
4/7
Procedure
Signalling point status management
Subsystem status management
Local MTP availability
Co-ordinated state change between replicas
Local broadcast of remote subsystem, SCCP or SPC status
changes
Remote broadcast in case of subsystem or SCCP status changes
at local or adjacent SPCs.
Remote SCCP unavailable
Reference
Q.714, clause 5.2
Q.714, clause 5.3
Q.714, clause 5.2.5
Q.714, clause 5.3.5
Q.714, clause 5.3.6
Status
Support
m
m (see note)
m
c41
m
Q.714, clause 5.3.7 o
Q.714, clauses 5.2 m (see note)

and 5.3
4/8 Signalling Point restart
Q.714, clause 5.4
m
NOTE:
Mandatory because the 'user part availability control' capability at the underlying layer is mandatory.
c41: IF A.2/1 THEN o ELSE n/a

Comments:
-- end node role
ETSI
15
A.5.3
Major capabilities - connectionless SCCP
The supplier of the implementation shall state whether or not the (signalling) connectionless procedures and options for
the SCCP specified in ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as modified by
EN 300 009-1 [1] are supported, in table A.5.
Table A.5: Procedures and options for data transfer in connectionless mode
Item
Procedure or option
5/1 Data transfer - non sequenced (Class 0), no return option, using
UDT or non-segmented XUDT
5/2 Data transfer, sequenced (Class 1), no return option, using UDT or
non-segmented XUDT
5/3 Segmentation/reassembly
Reference
Status
Support
Q.714,
m (see note 1)
clause 4.1
Q.714,
c51
clause 4.1
(see note 1)
Q.714,
c52
clause 4.1.1
5/4 Message return option
Q.714,
c53 (see note 2)
clause 4.2
5/5 Message return procedure
Q.714,
m (see note 3)
clause 4.2
5/6 Syntax error
Q.714,
m (see note 4)
clause 4.3
5/7 Sending of XUDT for non-segmented messages
Q.714,
c54 (see note 5)
clause 4.1
5/8 Reception of XUDT for non-segmented messages
Q.714,
m (see note 5)
clause 4.1
5/9 Sending of XUDT for non-segmented messages manageable
Q.714,
c55
clause 4.1
5/10 Use of LUDT messages
Q.714,
o (see note 6)
clause 4.1
5/11 Message change
Q.714,
c56
clause 4.1.2
(see note 7)
NOTE 1: The 'return option' is not offered to the SCCP-user. SCCP does not set the 'return message on error' special
option for the connectionless protocol class in the UDT or non-segmented XUDT.
NOTE 2: SCCP offers the 'return option' as a capability to its users in addition to capabilities 5/1 and 5/2.
NOTE 3: This capability comprises the 'message return' procedure which evaluates the 'message return on error'
special option subfield of the protocol class parameter contained in the received UDT or XUDT message.
NOTE 4: Mandatory in end node (complete check) and in relay node (as far as needed to reliable route the message).
NOTE 5: To allow the transition from the use of UDT to XUDT also for messages that do not need segmenting,
reception of XUDT messages should be prepared (see EN 300 009-1 [1], clause ZA.2). The sending of
XUDT messages has to be manageable.
NOTE 6: The possibility to use LUDT messages depends on the availability of the capabilities of the MTP-3b.
NOTE 7: When inter-working with networks only supporting SCCP versions prior to the 1993 edition is required, the
message change capability is mandatory.
c51: IF A.1/2 THEN m ELSE x

c52 IF A.1/2 THEN o ELSE x
c53 IF A.2/1 THEN o ELSE n/a
c54 IF A.2/2 THEN m ELSE o
c55: IF A.5/7 AND A.2/1 THEN m ELSE n/a
Comments:
-- End node role
-- Relay node role
-- Sending of XUDT implemented and end node role
-- Relay node role
ETSI
16
A.5.4
Major capabilities - connection-oriented SCCP
The supplier of the implementation shall state whether or not the (signalling) connection-oriented procedures and
options for the SCCP as specified in ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as
modified by EN 300 009-1 [1] are supported, in tables A.6 to A.12.
Table A.6: Procedures and options for connection establishment
Item
6/1
6/2
6/3
6/4
6/5
6/6
6/7
6/8
6/9
6/10
6/11
NOTE:
Procedure or option
Explicit setup, Class 2 in end node
Embedded setup, Class 2 in end node
Explicit setup, Class 2 in relay node with coupling
Embedded setup, Class 2 in relay node with coupling
Explicit setup, refusal procedure
Embedded setup, refusal procedure
Responding address in CREF on user refusal
Responding address in CREF on SCCP refusal
Responding address in CC
Class 3 window negotiation
Class 3 protocol class negotiation
Reference
Q.714, clause 3.1
Q.714, clause 3.1
Q.714, clause 3.1.5
Q.714, clause 3.1.5
Q.714, clause 3.2
Q.714, clause 3.2
Q.711, clause 2.1.1.2.2
Q.711, clause 2.1.1.2.2
Q.711, clause 2.1.1.2.2
Q.714, clause 3.1.3
Q.714, clause 3.1.3.1
and 3.1.5.1
Status
c61
c62
c63
c64 (see note)
c65
c66
c61
c67
c61
i
c68
Support
SCCP-user available in the relay node.
c61:
c62:
c63:
IF A.1/3 AND A.2/1 THEN m ELSE n/a

IF A.1/3 AND A.2/1 THEN o ELSE n/a
IF A.1/3 AND A.2/2 AND A.2/2.4 THEN m ELSE n/a
c64:
IF A.1/3 AND A.2/2 AND A.2/2.4 THEN o ELSE n/a
c65: IF A.6/1 OR A.6/3 THEN m ELSE n/a

c67 IF A.1/3 THEN o ELSE n/a
c68 IF A.6/1 OR A.6/2 OR A.6/3 OR A.6/4 THEN m ELSE n/a
Comments:
-- SUT = end node for connection-oriented

-- SUT = end node for connection-oriented
-- SUT = relay node for connection-oriented
-- with coupling of connection sections
-- SUT = relay node for connection-oriented
-- with coupling of connection sections
-- explicit setup in end node or relay node
-- embedded setup supported
-- class 2 supported
-- connection setup supported
Table A.7: Procedures for connection release

Item
Procedure
7/1 Release procedure in end nodes
7/2 Release procedure in relay nodes with coupling
c71: IF A.1/3 AND A.2/1 THEN m ELSE x

c72: IF A.1/3 AND A.2/2.4 THEN m ELSE x
Comments:
Reference
Q.714, clause 3.3.3/5
Q.714, clause 3.3.4
Status
c71
c72
Support
Status
c81
i
Support
-- Class 2 in end nodes

-- Class 2 in relay node with coupling
Table A.8: Procedure for inactivity control

Item
Procedure
8/1 Inactivity control for Class 2
8/2 Inactivity control for Class 3
c81: IF A.1/3 THEN m ELSE n/a

Comments:
Reference
Q.714, clause 3.4
Q.714, clause 3.4
-- Class 2 provided
ETSI
17
Table A.9: Procedures and options for data transfer in connection oriented mode
Item
Procedure or option
Reference
Status Support
9/1 Data transfer Class 2 in end node
Q.714, clause 3.5.1
c91
9/2 Data transfer in relay node with coupling
Q.714, clause 3.5.1
c92
9/3 Data transfer Class 3 with flow control
Q.714, clause 3.5.2
i
9/4 Data transfer, segmenting/reassembly
Q.714, clause 3.5.3
c91
9/5 Expedited data transfer
Q.714, clause 3.6
i
9/6 Data acknowledgement
Q.714, clause 3.6.3
i
9/7 Data transfer in CR message
Q.711, clause 2.1.1.2.2 c93
9/8 Data transfer in CC message
Q.711, clause 2.1.1.2.2 c93
9/9 Data transfer in CREF message
Q.711, clause 2.1.1.2.2 c93
9/10 Data transfer in RLSD message
Q.711, clause 2.1.1.2.4 c93
NOTE 1: In a relay point, the segmenting/reassembly functions are not invoked. The M bit is just passed
transparently according to the compatibility rules of ITU-T Recommendation Q.1400 [5], sect.12.
NOTE 2: The transfer of data in CR/CC/CREF/RLSD messages is a user option.
c91: IF A.1/3 AND A.2/1 THEN m ELSE n/a

c92: IF A.1/3 AND A.2/2.4 THEN m ELSE n/a
Comments:
-- Class 2 in end nodes

-- Class 2 in relay node with coupling
-- Class 2
Table A.10: Procedure for reset

Item
10/1 Reset
Procedure
Reference
Q.714, clause 3.7
Status
Support
Status
c111
Support
Reference
Status
Q.714, clause 3.10, c121
annex B
Support
Comments:
Table A.11: Procedure for restart
Item
11/1 Restart

Comments:
Procedure
Reference
Q.714, clause 3.8
-- Class 2
Table A.12: Procedure for abnormalities

Item
12/1 Abnormalities

Comments:
Procedure
-- Class 2
ETSI
18
A.5.5
Timers used in SCCP
The supplier of the implementation shall state whether or not the following timers, used by the SCCP protocol, as
specified in ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as modified by EN 300 009-1 [1]
are supported and their value or range(s), in table A.13.
Table A.13: Timers - SCCP
Item
Timer
Reference
Values
Allowed
Supported
13/1 T(conn est)
Q.714, clause C.4 c131
y
1 mn to 2 min
13/2 T(ias)
y
1 mn to 10 min (see note)
13/3 T(iar)
y
13/4 T(rel)
y
10 s to 20 s
13/5 T(guard)
y
13/6 T(reset)
Q.714, clause C.4 i
n/a
10 s to 20 s
13/7 T(reassembly) Q.714, clause C.4 c132
y
10 s to 20 s
13/8 T(coord)
n/a
1 mn to 2 min
13/9 T(interval)
y
up to 1 min
13/10 T(repeat rel)
y
up to 20 s
13/11 T(ignore SST) Q.714, clause C.4 c134
n/a
selected by management
13/12 T(stat info)
y
starting from 5 to 10 s to
max. 10 mn to 20 min
NOTE:
Provisional values. These values cover both the provisional ranges specified in
ITU-T Recommendation Q.714 [9] as modified by EN 300 009-1 [1], and the finally agreed ranges to be
published in the next edition of ITU-T Recommendations.

Comments:
A.5.6
Status Support
-- Class 2
-- connectionless segmenting/reassembly
-- SCCP subsystem management
-- co-ordinated state change procedure
Messages
The supplier of the implementation shall state whether or not the messages specified in ITU-T Recommendations
Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as modified by EN 300 009-1 [1] are supported, in table A.14. Support of
a message implies full support of all message parameters, unless specifically covered by A.5.7.
The supplier shall indicate for each message the status of support for sending and receiving.
ETSI
19
Table A.14: Messages

Item
14/1
14/2
14/3
14/4
14/5
14/6
14/7
14/8
14/9
14/10
14/11
14/12
14/13
14/14
14/15
14/16
14/17
14/18
14/19
14/20
14/21
14/22
14/23
14/24
14/25
14/26
c141:
c142:
c143:
c144:
c145:
c146:
c147:
Message
CC
CR
CREF
AK
DT1
DT2
ED
EA
IT
ERR
RLSD
RLC
RSC
RSR
SSA
SOG
SOR
SSP
SST
UDT
UDTS
XUDT
XUDTS
SSC
LUDT
LUDTS
Reference
Q.712, clause 1.1
Q.712, clause 1.2
Q.712, clause 1.3
Q.712, clause 1.4
Q.712, clause 1.5
Q.712, clause 1.6
Q.712, clause 1.7
Q.712, clause 1.8
Q.712, clause 1.9
Q.712, clause 1.10
Q.712, clause 1.11
Q.712, clause 1.12
Q.712, clause 1.13
Q.712, clause 1.14
Q.712, clause 1.15
Q.712, clause 1.16
Q.712, clause 1.17
Q.712, clause 1.18
Q.712, clause 1.19
Q.712, clause 1.20
Q.712, clause 1.21
Q.712, clause 1.22
Q.712, clause 1.23
Q.712, clause 1.24
Q.712, clause 1.25
Q.712, clause 1.26
Sending
Status Support
c141
c141
c141
i
c142
i
i
i
c143
c143
c141
c141
i
i
m
c144
c144
c145
m
m
m
c147
m
c145
o
o
Receiving
Status Support
c141
c141
c141
i
c142
i
i
i
c143
c143
c141
c141
i
i
m
c144
c144
m
m
m
c146
m
c148
m
o
o
IF A.1/3 AND (A.2/1 OR A.2/2.4) THEN m ELSE x

IF A.9/1 OR A.9/2 THEN m ELSE n/a
IF A.1/3 THEN m ELSE n/a
IF A.4/4 THEN m ELSE n/a
IF A.2/1 THEN m ELSE o
IF A.5/4 THEN m ELSE x
IF A.5/7 OR A.5/3 THEN m ELSE n/a
-- Class 2 and (end node or relay point with coupling)

-- data transfer provided
-- class 2
-- co-ordinated status change implemented
-- end node
-- message return option supported
-- sending of XUDT for non-segmented messages or
-- segmenting/reassembly supported
c148: IF A.5/4 AND (A.5/7 OR A.5/3) THEN m ELSE n/a -- XUDT messages sent with return option
Comments:
A.5.7
Message parameters
Unless specifically covered by a table listing message parameters and giving details regarding their status all parameters
of a message are required to be fully supported. All parameters in the fixed and variable mandatory part are required to
be present. In case parameter field values are irrelevant for certain protocol classes, this is appropriately indicated in the
following tables and does not imply the parameter may be absent.
The supplier of the implementation shall state whether or not each message parameter of the messages specified in
ITU-T Recommendations Q.711 [6], Q.712 [7], Q.713 [8] and Q.714 [9] as modified by EN 300 009-1 [1] are
supported, in tables A.15 to A.22.
The supplier shall indicate the status of support for sending and receiving for each parameter in each message.
NOTE:
The status of the message parameters is subject to the implementation of the corresponding message (see
table A.14). When an unknown, unsupported or unrecognized optional parameter or value is received, the
compatibility rules specified in clause 1.1.4 of ITU-T Recommendation Q.714 [9] as modified by
EN 300 009-1 [1] apply.
ETSI
20
Table A.15: Connection Request (CR)

Item
Parameter
Reference
Sending
Status
Support
Receiving
Status
Support
15/1 Message Type Code

Q.713, clause 2.1
m
m
15/2 Source Local Reference Number Q.712, clause 2.9
m
m
15/3 Called Party Address
Q.712, clause 2.3
m
m
15/4 Calling Party Address
Q.712, clause 2.3
o
o
15/5 Protocol class
Q.712, clause 2.10 m
m
15/6 Credit
Q.712, clause 2.4
i
i (see note 2)
15/7 User Data
Q.712, clause 2.5
c151 (see note 1)
c151
15/8 Hop Counter
Q.712, clause 2.19 c152
c152
15/9 End of Optional Parameters
Q.712, clause 2.8
c153
c154
NOTE 1: Dependent on user data being provided by the application in the originated node.
NOTE 2: The base specifications only specify that an unrecognized parameter in a received message has to be ignored.
They do not specify any treatment for not supported parameters in a received message.

c152: IF A.2/2.3 THEN m ELSE n/a
c153: IF A.15/4 OR A.15/7 OR A.15/8 THEN m ELSE n/a
c154: IF A.15/4 OR A.15/6 OR A.15/7 OR A.15/8 THEN m ELSE n/a
-- user data in CR is supported

-- hop counter protection provided
-- mandatory when optional parameters are
-- present
-- mandatory when optional parameters are
-- present
Comments:
Table A.16: Connection Confirm (CC)
Item
16/1
16/2
16/3
16/4
16/5
16/6
16/7
16/8
Parameter
Message Type Code
Destination Local Reference Number
Source Local Reference Number
Called Party Address
Protocol class
Credit
User Data
End of Optional Parameters

Comments:
Reference
Q.713, clause 2.1
Q.712, clause 2.9
Q.712, clause 2.9
Q.712, clause 2.3
Q.712, clause 2.10
Q.712, clause 2.4
Q.712, clause 2.5
Q.712, clause 2.8
Sending
Status Support
m
m
m
c161
m
i
c162
c163
Receiving
Status Support
m
m
m
c161
m
i
c162
c163
-- responding address in CC message

-- user data in CC is supported
-- mandatory when optional parameters are present
Table A.17: Connection Refused (CREF)

Item
17/1
17/2
17/3
17/4
17/5
17/6
Parameter
Message Type Code
Called Party Address
User Data
Refusal Cause
End Of Optional Parameters

Comments:
Reference
Q.713, clause 2.1
Q.712, clause 2.9
Q.712, clause 2.3
Q.712, clause 2.5
Q.712, clause 2.12
Q.712, clause 8
Sending
Status Support
m
m
c171
c172
m
c173
Receiving
Status Support
m
m
c171
c172
m
c173
-- responding address in CREF message

-- user data in CREF is supported
ETSI
21
Table A.18: Released (RLSD)

Item
18/1
18/2
18/3
18/4
18/5
18/6
Parameter
Reference
Message Type Code

Source Local Reference Number
Release Cause
User Data
End of Optional Parameters

Comments:
Q.713, clause 2.1

Q.712, clause 2.9
Q.712, clause 2.9
Q.712, clause 2.13
Q.712, clause 2.5
Q.712, clause 2.8
Sending
Status Support
m
m
m
m
c181
c182
Receiving
Status Support
m
m
m
m
c181
c182
-- data transport in RLSD is supported

Table A.19: Protocol Data Unit Error (ERR)

Item
Parameter
Reference

19/2 Destination Local Reference Number
19/3 Error Cause
Q.713, clause 2.1

Q.712, clause 2.9
Q.712, clause 2.7
Sending
Receiving
Status Support Status Support
m
m
m
m
m
m
Comments:
Table A.20: Inactivity Test (IT)
Item
Parameter
Reference
Sending
Status
Support

Q.713, clause 2.1
m
20/2 Destination Local Reference Number Q.712, clause 2.9
m
20/3 Source Local Reference Number
Q.712, clause 2.9
m
20/4 Protocol class
Q.712, clause 2.10
m
20/5 Sequencing/Segmenting
Q.712, clause 2.17
i (see note)
20/6 Credit
Q.712, clause 2.4
i (see note)
NOTE:
These parameter field values are relevant for protocol class 3 only.
Receiving
Status
Support
m
m
m
m
i (see note)
i (see note)
Comments:
Table A.21: Extended UnitData (XUDT)
Item
Parameter
Sending
Status Support
Q.713, clause 2.1
m
21/2 Protocol class
21/3 Hop counter
Q.712, clause 2.3
m
Q.712, clause 2.3
m
21/6 UserData
Q.712, clause 2.5
m
21/7 Segmentation (see note)
Q.712, clause 2.20 c211
21/8 End Of Optional Parameters
Q.712, clause 2.8
c212
NOTE:
Should not be present in case of a single-segment XUDT message.

Comments:
Reference
ETSI
Receiving
Status Support
m
m
m
m
m
m
c211
c212
22
Table A.22: Extended UnitData Service (XUDTS)

Item
Parameter
Sending
Status Support
Q.713, clause 2.1
m
22/2 Return Cause
22/3 Hop counter
Q.712, clause 2.3
m
Q.712, clause 2.3
m
22/6 UserData
Q.712, clause 2.5
m
22/7 Segmentation (see note)
Q.712, clause 2.20 c221
22/8 End Of Optional Parameters
Q.712, clause 2.8
c222
NOTE:
Should not be present in case of a single-segment XUDTS message.

Comments:
A.5.8
Reference
Receiving
Status Support
m
m
m
m
m
m
c221
c222
Multi-layer dependencies
The supplier of the implementation shall provide information relevant to the support for other layer standards in
table A.23. Where appropriate, the supplier shall provide an external reference to the completed PICS for that layer
standard. The purpose of this clause is to identify the implementation support for specific requirements on the
underlying layers, not made mandatory by the underlying layer protocol specifications.
Table A.23: Underlying layers protocols
Item
Procedure
23/1 MTP
Reference
Q.701 [3] to Q.704 [10]
PICS references
Comments:
ETSI
23
Annex B (informative):
Bibliography
ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and
framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
ITU-T Recommendation Q.715: "Signalling connection control part user guide".
ETSI
24
History
Document history
Edition 1
September 1996
Publication as ETS 300 009-2
V1.3.2
March 2000
Publication
V1.4.1
December 2001
One-step Approval Procedure
ETSI
OAP 20020412: 2001-12-12 to 2002-04-12

ETSI EN 300 009-2: Final Draft V1.4.1

Uploaded by

Copyright:

Available Formats

ETSI EN 300 009-2: Final Draft V1.4.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ETSI EN 300 009-2: Final Draft V1.4.1

Uploaded by

Copyright:

Available Formats

Final draft

ETSI EN 300 009-2 V1.4.1 (2001-12)

Integrated Services Digital Network (ISDN);

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Definitions and abbreviations...................................................................................................................6

Guidance for completing the PICS proforma...........................................................................................8

PICS proforma for EN 300 009-1...................................................................8

Purposes and structure........................................................................................................................................8

Identification of the implementation ......................................................................................................10

Date of the statement ........................................................................................................................................10

Identification of the protocol..................................................................................................................12

Global statement of conformance...........................................................................................................12

General requirements .......................................................................................................................................12

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Intellectual Property Rights

" Protocol specification [ITU-T Recommendations Q.711 to Q.716 (1996), modified]";

"Protocol Implementation Conformance Statement (PICS) proforma specification";

Proposed national transposition dates

3 months after ETSI publication

Date of latest publication of new National Standard

6 months after doa

Date of withdrawal of any conflicting National Standard (dow):

6 months after doa

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing

ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing

ITU-T Recommendation Q.714: "Signalling connection control part procedures".

ITU-T Recommendation Q.704: "Signalling network functions and messages".

Definitions and abbreviations

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

data AcKnowledgement message

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

SubSystem Prohibited message

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Guidance for completing the PICS proforma

Purposes and structure

Abbreviations and conventions

mandatory - the capability is required to be supported.

optional - the capability may be supported or not.

not applicable - in the given context, it is impossible to use the capability.

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

supported by the implementation.

not supported by the implementation.

?3: IF prof1 THEN Y ELSE N

A.5/4 is the reference to the answer of item 4 in table A.5 of annex A.

Instructions for completing the PICS

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Identification of the implementation

Date of the statement

Implementation Under Test (IUT) identification

System Under Test (SUT) identification

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

PICS contact person

Final draft ETSI EN 300 009-2 V1.4.1 (2001-12)

Identification of the protocol

This PICS proforma applies to the following standard:

Global statement of conformance

A.5.1.1 Implemented class