SIST ETS 300 239 E1:2005
(Main)Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Generic functional protocol for the support of supplementary services
Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Generic functional protocol for the support of supplementary services
Stage 3 of generic functional sup service at Q ref pt. See ENV41005 for definition of stage 3. See ENV41004 for definition of Q reference point. To contain PICS proforma.
Zasebno telekomunikacijsko omrežje (PTN) – Medcentralni signalizacijski protokol - Generični funkcijski protokol za podporo dopolnilnim storitvam
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 239 E1:2005
01-maj-2005
=DVHEQRWHOHNRPXQLNDFLMVNRRPUHåMH 371 ±0HGFHQWUDOQLVLJQDOL]DFLMVNLSURWRNRO
*HQHULþQLIXQNFLMVNLSURWRNRO]DSRGSRURGRSROQLOQLPVWRULWYDP
Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Generic
functional protocol for the support of supplementary services
Ta slovenski standard je istoveten z: ETS 300 239 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 239 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 239 E1:2005
---------------------- Page: 2 ----------------------
SIST ETS 300 239 E1:2005
EUROPEAN ETS 300 239
TELECOMMUNICATION June 1993
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-0045
ICS: 33.080
PTN, QSIG-GF, ECMA-165
Key words:
Private Telecommunication Network (PTN);
Inter-exchange signalling protocol
Generic functional protocol for the support of
supplementary services
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
No part may be reproduced except as authorized by written permission. The copyright and the
Copyright Notification:
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1993. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
SIST ETS 300 239 E1:2005
Page 2
ETS 300 239:1993
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.
---------------------- Page: 4 ----------------------
SIST ETS 300 239 E1:2005
Page 3
ETS 300 239:1993
Foreword 9
1Scope 11
2 Conformance 11
3 References 11
4 Definitions 12
4.1 External definitions 12
4.2 Additional Network Feature (ANF) 12
4.3 Adjacent PTNX 12
4.4 Application Protocol Data Unit (APDU) 12
4.5 Call, Basic call 12
4.6 Call independent signalling connection 12
4.7 Call independent 12
4.8 Call related 12
4.9 Connection oriented 12
4.10 Connectionless 12
4.11 Co-ordination Function 13
4.12 Destination PTNX 13
4.13 DSE APDU 13
4.14 Dialogue Service Element (DSE) 13
4.15 End PTNX 13
4.16 Gateway PTNX 13
4.17 Generic Functional Transport Control (GFT-Control) entity 13
4.18 Incoming side 13
4.19 Interpretation APDU 13
4.20 Invocation 13
4.21 Link significance 13
4.22 Mistyped 13
4.23 Network significance 13
4.24 Next PTNX 14
4.25 Notification 14
4.26 Originating PTNX 14
4.27 Outgoing side 14
4.28 Preceding PTNX 14
4.29 Protocol Control 14
4.30 ROSE APDU 14
4.31 Side 14
4.32 Source PTNX 14
4.33 Subsequent PTNX 14
4.34 Supplementary service 14
4.35 Supplementary Services Control (SS-Control) entity 14
4.36 Terminating PTNX 15
4.37 Transit PTNX 15
4.38 Unrecognised 15
5 List of acronyms 15
6 General principles 15
6.1 Application Association 16
6.2 Protocol Model 16
---------------------- Page: 5 ----------------------
SIST ETS 300 239 E1:2005
Page 4
ETS 300 239:1993
6.3 Application of the protocol model to communication between SS-Control entities in
non-Adjacent PTNXs 18
6.4 Services provided by ROSE 19
6.5 Services provided by DSE 19
6.6 Services provided by GFT-Control 20
6.6.1 Connection oriented services 20
6.6.2 Connectionless transport services 20
6.6.3 Notification services 20
6.7 Services provided by Protocol Control to GFT-Control 20
6.7.1 Connection oriented transport services 20
6.7.2 Connectionless transport service 21
6.7.3 Notification services 21
6.8 Services required of the Data Link Layer 21
7 Protocol Control and GFT-Control Requirements 21
7.1 Call related Procedures for the transport of APDUs 21
7.1.1 Protocol Control requirements 21
7.1.1.1 Sending the Facility information element 21
7.1.1.2 Receiving the Facility information element 22
7.1.2 GFT Control Requirements 22
7.1.2.1 Actions at a Source PTNX 22
7.1.2.2 Actions at a Receiving PTNX 23
7.1.2.2.1 End PTNX actions 24
7.1.2.2.2 Transit PTNX actions 24
7.1.2.3 Actions at a Destination PTNX 25
7.1.2.4 Dynamic description (SDL) of Generic Functional Transport
Control 25
7.2 Connectionless APDU Transport Mechanism 30
7.2.1 Protocol Control requirements 30
7.2.1.1 Requirements for sending a Connectionless message 30
7.2.1.2 Requirements for receiving a Connectionless message 30
7.2.2 GFT-Control requirements 30
7.2.2.1 Actions at a Source PTNX 30
7.2.2.2 Actions at a Receiving PTNX 31
7.2.2.3 Actions at a Destination PTNX 31
7.3 Connection oriented APDU transport mechanism 31
7.3.1 Protocol Control requirements 31
7.3.1.1 Actions in the Null state 31
7.3.1.2 Actions in the Call initiated state 32
7.3.1.3 Actions in the Incoming call proceeding state 32
7.3.1.4 Actions in the Outgoing call proceeding state 32
7.3.1.5 Actions in the Connect request state 33
7.3.1.6 Actions in the Active state 33
7.3.1.7 Connection release 33
7.3.1.8 Actions in the Release request state 33
7.3.1.9 Transport of APDUs associated with a Call independent
signalling connection 33
7.3.1.10 Protocol error handling 34
7.3.1.11 Protocol timer values 34
7.3.1.12 Procedures for layer management 34
7.3.2 Dynamic Description (SDL) of Connection oriented Protocol Control procedures 36
7.3.3 GFT Control requirements 47
7.3.3.1 Actions at an Originating PTNX 47
7.3.3.1.1 Actions in the Originating_connection_idle state 47
---------------------- Page: 6 ----------------------
SIST ETS 300 239 E1:2005
Page 5
ETS 300 239:1993
7.3.3.1.2 Actions in the Originating_connection_request
state 47
7.3.3.1.3 Actions in the Originating_connection_active state 47
7.3.3.2 Actions at a Transit PTNX 48
7.3.3.2.1 Actions in the Transit_Connection_idle state: 48
7.3.3.2.2 Actions in the Transit_Connection_request state 49
7.3.3.2.3 Actions in the Transit_Connection_active state 49
7.3.3.3 Actions at a Terminating PTNX 49
7.3.3.3.1 Actions in the Incoming_Connection_idle state: 49
7.3.3.3.2 Actions in the Incoming_Connection_active state 49
7.3.3.4 Actions at a Source PTNX 50
7.3.3.5 Actions at a Destination PTNX 50
7.4 Call related procedures for the transport of Notifications 50
7.4.1 Categories of notifications 50
7.4.2 Protocol Control requirements 50
7.4.2.1 Sending notification information 50
7.4.2.2 Receiving notification information 51
7.4.3 GFT-Control requirements 51
7.4.3.1 Actions at a PTNX which generates notifications 51
7.4.3.2 Actions at a Transit PTNX 51
7.4.3.3 Actions at a Receiving End PTNX 51
8 Application layer requirements 51
8.1 Co-ordination Function requirements 51
8.1.1 Inclusion of an Interpretation APDU at a Source PTNX 52
8.1.2 Handling of APDUs at a Destination PTNX 52
8.2 ROSE requirements 52
8.3 DSE requirements 52
8.3.1 Actions at the PTNX which initiates the dialogue (PTNX A) 53
8.3.1.1 Idle state procedures 53
8.3.1.2 Initiate sending state procedures 53
8.3.2 Actions at the PTNX which terminates the dialogue (PTNX B) 54
8.3.2.1 Idle state procedures 54
8.3.2.2 Initiate receiving state procedures 54
8.3.3 Dialogue Continuation in the Active State 54
8.3.4 Dialogue Protocol Timers 55
8.3.5 Error procedures relating to dialogue control 55
8.3.6 Example of a dialogue 55
8.3.7 Dynamic Description (SDL) of Dialogue Identification Protocol Procedures 56
8.4 SS-Control requirements 61
9 Manufacturer Specific Information 61
9.1 Manufacturer specific operations 61
9.2 Manufacturer specific additions to standardised operations 62
9.3 Manufacturer specific notifications 63
10 Message functional definitions and contents 63
10.1 ALERTING 63
10.2 CONNECT 64
10.3 SETUP 64
10.4 DISCONNECT 65
10.5 RELEASE 65
10.6 RELEASE COMPLETE 65
10.7 FACILITY 65
---------------------- Page: 7 ----------------------
SIST ETS 300 239 E1:2005
Page 6
ETS 300 239:1993
10.8 NOTIFY 66
10.9 PROGRESS 67
11 General Message Format and Information Element Coding 67
11.1 Message Type 67
11.2 Call reference 67
11.3 Other Information Elements 67
11.3.1 Bearer capability 68
11.3.2 Channel identification 68
11.3.3 Facility 69
11.3.3.1 Network Facility Extension Coding 70
11.3.3.2 Interpretation APDU 71
11.3.3.3 DSE APDU 72
11.3.3.4 ROSE APDUs 73
11.3.4 Notification Indicator 76
Annex A (informative): 78
Application of the Functional Protocol 78
A.1 Examples of the use of the functional protocol over the PTN 78
A.2 Call related Supplementary services 78
A.2.1 Call Establishment 78
A.2.1.1 End to end Service request 78
A.2.1.2 Link Service Request 79
A.2.2 Call Clearing 82
A.2.2.1 End to End Request 82
A.2.2.2 Link Service Request 82
A.2.3 Call Active 82
A.2.3.1 End to End Request 82
A.2.3.2 Link Service Request 83
A.3 Call independent Supplementary services 83
A.3.1 Connectionless Transport 83
A.3.2 Connection oriented Transport 84
Annex B (informative): 85
Remote Operations Protocol 85
Annex C (informative): 87
Formal Rose Definitions 87
Annex D (informative): 89
Examples of the Use of Manufacturer Specific Information 89
D.1 Manufacturer Specific Object Identifiers in Operation Values 89
D.2 Manufacturer specific extensions to standardised operations 90
Annex E (informative): 93
Problem Code Definitions 93
Annex F (informative): 95
Bibliography 95
Annex G (informative): 96
ASN.1 Definition of PartyNumber 96
---------------------- Page: 8 ----------------------
SIST ETS 300 239 E1:2005
Page 7
ETS 300 239:1993
Annex H (informative): 99
Object Identifiers Used in this ETS 99
Annex J (normative): 100
Protocol Implementation Conformance Statement (PICS) Proforma 100
J.1 Introduction 100
J.2 Instructions for completing the PICS proforma 100
J.2.1 General structure of the PICS proforma 100
J.2.2 Additional information 101
J.2.3 Exception information 101
J.3 PIC Proforma for ETS 300 239 102
J.3.1 Implementation Identification 102
J.3.2 Protocol Summary 102
J.3.3 Call Related Protocol Control and GFT-Control Requirements 103
J.3.4 Connectionless APDU transport mechanism 103
J.3.5 Connection oriented APDU transport mechanism 104
J.3.6 Co-ordination Function requirements 104
J.3.7 ROSE requirements 104
J.3.8 DSE requirements 104
J.3.9 Manufacturer specific information 105
J.3.10 Encoding 105
J.3.11 Implemented information elements in messages 106
J.3.11.1 ALERTING message 106
J.3.11.2 CONNECT message 106
J.3.11.3 SETUP message 106
J.3.11.4 DISCONNECT message 106
J.3.11.5 RELEASE message 107
J.3.11.6 RELEASE COMPLETE message 107
J.3.11.7 FACILITY message 107
J.3.11.8 NOTIFY message 108
J.3.11.9 PROGRESS message 108
History 109
---------------------- Page: 9 ----------------------
SIST ETS 300 239 E1:2005
Page 8
ETS 300 239:1993
Blank Page
---------------------- Page: 10 ----------------------
SIST ETS 300 239 E1:2005
Page 9
ETS 300 239:1993
Foreword
This European Telecommunication Standard (ETS) has been produced by the European Computer Manufacturers
Association (ECMA) on behalf of its members and those of the European Telecommunications Standards Institute
(ETSI).
This ETS defines the signalling protocol for use at the Q reference point between two PTNXs for the transport of
protocol information as part of supplementary services and/or Additional Network Features (ANFs) within a Private
Telecommunication Network.
The generic functional procedures provide a flexible and open ended approach to the provision of Supplementary
service and ANF protocols. These procedures provide:
- generic protocols which may be utilised in the provision of Supplementary services and ANFs, both related to
existing calls and separate from existing calls where appropriate to the capability required;
- a dialogue identification protocol to enable Supplementary service or ANF information flows to be tied together to
form a dialogue;
- Supplementary service and ANF transparency across a PTN, whereby transit PTNXs need have no knowledge of the
capability provided to the PTN user or PTN itself unless involved in the provision of that capability; and
- the capability for standardised and manufacturer specific capabilities to coexist in both single and multi-vendor
PTNs.
The protocol defined in this ETS is based upon that described in ETS 300 196.
This ETS was produced by ECMA using the ECMA guidelines for the production of standards and the ECMA
stylesheet. In order to avoid undue delays in the approvals procedure, it has been agreed that this ETS will not be
converted to the ETSI stylesheet.
---------------------- Page: 11 ----------------------
SIST ETS 300 239 E1:2005
Page 10
ETS 300 239:1993
Blank Page
---------------------- Page: 12 ----------------------
SIST ETS 300 239 E1:2005
Page 11
ETS 300 239:1993
1Scope
This ETS specifies the generic functional protocol for the control of Supplementary services and Additional
Network Features (ANFs) at the Q reference point. The Q reference point exists between Private
Telecommunication Network Exchanges (PTNX) connected together within a Private Telecommunication
Network (PTN) and is defined in ENV 41004. Detailed procedures applicable to individual Supplementary
services and ANFs are beyond the scope of this ETS.
ETS 300 172 defines the Layer 3 protocol for circuit-switched call control at the Q reference point. This ETS
defines additional protocol procedures, to be used in conjunction with those defined in ETS 300 172 for the
control of Supplementary services and ANFs. The protocol defined in this ETS can also be used for the
transport of Manufacturer Specific Information (MSI) between PTNXs.
NOTE 1
Typical examples of the application of these generic functional procedures to some Supplementary services are
provided in Annex A, for explanatory and illustrative purposes only.
NOTE 2
Specific Supplementary services and Additional Network Features may require additional information transfer
mechanisms which are service or feature specific and are beyond the scope of this ETS.
2 Conformance
In order to conform to this ETS, a PTNX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in Annex J.
3 References
ETS 300 171 (1992) Private Telecommunication Networks (PTN) - Specification, Functional Model and
Information Flows - Control Aspects of Circuit Mode Basic Services
ETS 300 172 (1992) Private Telecommunication Networks (PTN) - Inter-exchange signalling protocol -
Circuit mode basic services
ETS 300 196 Integrated Services Digital Network (ISDN) - Generic functional protocol for the
support of supplementary services - Digital Subscriber Signalling System No. One
(DSS1) protocol
ENV 41004 (1989) Reference Configurations for Calls Through Exchanges of Private Telecommunication
Networks
ENV 41007 (1989) Definitions of Terms in Private Telecommunication Networks
CCITT Rec. I.112 (1988) Vocabulary of Terms for ISDNs
CCITT Rec. I.210 (1988) Principles of Telecommunication Services Supported by an ISDN and the Means to
Describe Them
CCITT Rec. X.208 (1988) Specification of Abstract Syntax Notation One (ASN.1)
CCITT Rec. X.209 (1988) Encoding Rules for Abstract Syntax Notation One (ASN.1)
CCITT Rec. X.219 (1988) Remote Operations Model, Notation and Service
CCITT Rec. X.229 (1988) Remote Operations Protocol Specification
---------------------- Page: 13 ----------------------
SIST ETS 300 239 E1:2005
Page 12
ETS 300 239:1993
4 Definitions
For the purposes of this ETS, the following definitions apply:
4.1 External definitions
This ETS uses the following terms defined in other documents:
Connection (ENV 41007)
Link (ENV 41007)
Private (ENV 41007)
Private Telecommunication Network Exchange (PTNX) (ENV 41007)
Service (CCITT Rec. I.112)
Signalling (CCITT Rec. I.112)
Terminal, Terminal Equipment (ENV 41007)
User (ETS 300 171)
4.2 Additional Network Feature (ANF)
A capability provided by a PTN, not generally directly to a User, over and above that of the Basic call.
4.3 Adjacent PTNX
A PTNX as considered from another PTNX to which it is directly connected via one or more inter-PTNX
links.
4.4 Application Protocol Data Unit (APDU)
A sequence of data elements exchanged between peer application layer entities, e.g. DSE APDUs and ROSE
APDUs.
4.5 Call, Basic call
An instance of the use of a basic service.
4.6 Call independent signalling connection
A signalling connection established between SS-Control entities located in different PTNXs that does not
have an associated user-information connection.
4.7 Call independent
A property of information which is conveyed across the Q reference point in a message which does not use a
call reference which has an associated user-information connection (that is, using a Connectionless or
Connection oriented transport mechanism as defined in 7.2 or 7.3).
4.8 Call related
A property of information which is conveyed across the Q reference point in a message which uses a call
reference which has an associated user-information connection.
4.9 Connection oriented
Communication between peer protocol entities by means of a connection or association established by an
underlying layer.
4.10 Connectionless
Communication between peer protocol entities by means of an unacknowledged, unidirectional transport
mechanism provided by an underlying layer.
---------------------- Page: 14 ----------------------
SIST ETS 300 239 E1:2005
Page 13
ETS 300 239:1993
4.11 Co-ordination Function
An entity which provides co-ordination between various SS-Control entities, ROSE, DSE, GFT-Control and
Call Control for different Supplementary services (see clause 6).
4.12 Destination PTNX
In the context of a single one-way exchange of information between two SS-Control entities, the PTNX
where the receiving SS-Control entity is located.
4.13 DSE APDU
An APDU defined by the Dialogue Service Element.
4.14 Dialogue Service Element (DSE)
A service element which provides services to SS-Control via the Co-ordination Function that associate ROSE
APDUs which are not implicitly associated by an underlying network layer connection.
4.15 End PTNX
In the context of a particular call, an Originating or Terminating PTNX. It can also be a Gateway PTNX,
dependent on the capabilities of the signalling system being interworked (i.e. unless it transports APDUs
unchanged to or from the other signalling system).
4.16 Gateway PTNX
Sub-clause 5.1.5 of ETS 300 172 shall apply. Dependent on the capabilities of the signalling system being
interworked by the Gateway PTNX, it can act as a Transit or an End PTNX in the context of the
Supplementary services APDUs. That is, it can either transport the APDUs unchanged to or from the other
signalling system, perhaps embedded in some other protocol unit, or process the APDUs and perform an
interworking function of the information flows and encoding of the Supplementary service concerned.
4.17 Generic Functional Transport Control (GFT-Control) entity
The entity that exists within a PTNX and provides a range of services (defined in clause 6) to SS-Control,
ROSE and DSE via the Co-ordination Function.
4.18 Incoming side
In the context of a Call independent signalling connection, the Side which receives the request for
connection establishment from the Preceding PTNX.
4.19 Interpretation APDU
An APDU defined by the Co-ordination Function.
4.20 Invocation
A request by a SS-Control entity to perform an operation in a remote SS-Control entity.
4.21 Link significance
A property of a Facility information element which does not contain a Network Facility Extension octet
group. It indicates that the element has only significance on a single inter-PTNX link - i.e. only between two
Adjacent PTNXs.
4.22 Mistyped
A property of an APDU whose structure does not conform to the structure defined in clause 11 of this ETS
or the structure defined for a particular Supplementary service.
4.23 Network significance
A property of a Facility information element which includes a Network Facility Extension octet group. It
indicates that the element has significance between two PTNXs which are not necessarily Adjacent.
---------------------- Page: 15 ----------------------
SIST ETS 300 239 E1:2005
Page 14
ETS 300 239:1993
4.24 Next PTNX
An Adjacent PTNX to which an APDU is to be sent in the context of an existing signalling connection
(related to a call or independent of a call).
4.25 Notification
A piece of protocol information which has the following properties:
- it is intended to be delivered only to terminals and is therefore passed on transparently by PTNXs;
- it does not cause a change of state on either side of the Q reference point;
- it represents a one-way flow of information that requires no response; and
- it provides additional information that can be discarded without the need for significant error recovery if
it is unrecognised by the terminal.
4.26 Originating PTNX
Sub-clause 5.1.4 of ETS 300 172 shall apply. In addition, the term is also applied to a PTNX which
originates a Call independent signalling connection.
4.27 Outgoing side
In the context of a Call independent signalling connection, the Side which sends the request for connection
establishment to the Next PTNX.
4.28 Preceding PTNX
Sub-clause 5.1.6 of ETS 300 172 shall apply. In addition, the term is also applied in a similar way to a PTNX
participating in a Call independent signalling connection.
4.29 Protocol Control
An entity which exists within a PTNX and provides a range of services (defined in clause 6) to the Generic
Functional Transport Control entity.
4.30 ROSE APDU
An APDU defined by the Remote Operations Service Element (ROSE) - see 11.3.
4.31 Side
The Protocol Control entity within a PTNX at one end of an inter-PTNX link.
4.32 Source PTNX
In the context of a single one-way exchange of information between two SS-Control entities, the PTNX
where the sending SS-Control entity is located.
4.33 Subsequent PTNX
Sub-clause 5.1.6 of ETS 300 172 shall apply. In addition, the term is also applied in a similar way to a PTNX
participating in a Call independent signalling connection.
4.34 Supplementary service
Section 2.4 of CCITT Recommendation I.210 shall apply.
For the purpose of this ETS, ANFs shall be regarded as Supplementary services.
4.35 Supplementary Services Control (SS-Control) entity
An entity that exists within a PTNX and provides the procedures associated with the support of a particular
Supplementary service.
---------------------- Page: 16 ----------------------
SIST ETS 300 239 E1:2005
Page 15
ETS 300 239:1993
4.36 Terminating PTNX
Sub-clause 5.1.4 of ETS 300 172 shall apply. In addition, the term is also applied to a PTNX which
terminates a Call independent signalling connection.
4.37 Transit PTNX
Sub-clause 5.1.4 of ETS 300 172 shall apply. In addition, the term is also applied to a PTNX which
participates in the provision of a Call independent signalling connection, but does not originate or terminate
that connection.
4.38 Unrecognised
A property of a message, information element, APDU or operation value whose type identifier is not one
supported by the Destination PTNX.
5 List of acronyms
ACSE Association Control Service Element
AE Application Entity
ANF Additional Network Feature
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation One
BER Basic Encoding Rules
DSE Dialogue Service Element
DSS1 Digital Subscriber Signalling no. 1
FIE Facility Information Element
GFT Generic Functional Transport
ICD International Code Designator
MSI Manufacturer Specific Information
NFE Network Facility Extension
PC Protocol Control
PICS Protocol Implementation Conformance Statement
PTN Private Telecommunication Network
PTNX Private Telecommunication Network Exchange
RO Remote Operations
ROSE Remote Operations Service Element
RTSE Reliable Transport Service Element
SS Supplementary Service
6 General principles
The generic functional protocol defined in this ETS provides the means to exchange signalling information for
the control of Supplementary services over a PTN. It does not by itself control any Supplementary service but
rather provides generic services to specific SS-Control entities. Procedures for individual Supplementary
services based on these generic procedures are defined in other ETSs or may be manufacturer-specific.
The generic functional protocol operates at the Q reference point between two PTNXs in conjunction with a
Layer 3 protocol for Basic call control (ETS 300 172). Together these use the services of the Data Link Layer.
The generic functional protocol provides mechanisms for the support of Supplementary services which relate to
existing basic calls or are entirely independent of any existing basic calls. In performing a Supplementary
service, whether Call independent or Call related, use may be made of both the Call related (7.1) and Call
independent (7.2 and 7.3) information transfer procedures.
---------------------- Page: 17 ----------------------
SIST ETS 300 239 E1:2005
Page 16
ETS 300 239:1993
If a particular Supplementary service comprises Call related and Call independent information transfer
procedures or relates to several basic calls at the same time it is - for the purpose of this ETS - deemed to
consist of separate instances of Call related (one for each call) and Call independent services respectively. The
combined use of two or more instances of Call related and/or Call independent procedures in support of a
particular Supplementary service is outside the scope of this ETS.
ETSs specifying the protocol for individual supplementary services will identify the particular mechanisms
used (Call related, Call independent correction oriented or Call independent connectionless).
6.1 Application Association
The use of explicit Application Association control by means of the Association Control Service Element
(ACSE, CCITT Rec. X.217/227) is beyond the scope of this ETS. However, Supplementary service
operations require an association between the respective peer SS-Control entities. This ETS provides two
means by which this association can be implicitly achieved:
(a) by the network layer connection in the case of Call related connections and for call-independent
signalling connections; or
(b) by the application layer dialogue service, in which case the association is independent of the
underlying network layer connections and can use a combination of different mechanisms, including
Call independent Connectionless information transfer.
6.2 Protocol Model
Figure 1 shows the conceptual model for the generic functional protocol and its relation to the Basic call
model defined in ETS 300 172.
---------------------- Page: 18 ----------------------
SIST ETS 300 239 E1:2005
Page 17
ETS 300 239:1993
NOTE
The capabilities defined in this ETS are indicated by shading, i.e. GFT-Control, DSE, ROSE and extensions to
Protocol Control. Part of the functions of the Co-ordination Function are also defined in this ETS, but the
remainder of this element governs Supplementary service specific interactions which are beyond the scope of
this ETS.
Figure 1 - Conceptual Model for the Generic Functional Protocol
At the top layer (the application layer) the actual Supplementary service protocol operates between peer
Supplementary Services Control (SS-Control) entities which are service-specific. The operation of specific
SS-Control entities is beyond the scope of this ETS.
SS-Control entities can use the services of the Remote Operations Service Element (ROSE) and the Dialogue
Service Element (DSE) at the application layer via the Co-ordination Function. These entities use the
services of Generic Functional Transport Control (GFT-Control) at the network layer via the Co-ordination
Function. GFT-Control uses the services of Protocol Control at the network layer.
The Remote Operations Service Element (ROSE) is defined in CCITT Rec. X.219.
---------------------- Page: 19 ----------------------
SIST ETS 300 239 E1:2005
Page 18
ETS 300 239:1993
NOTE 3
In the application of ROSE for the support of Supplementary services at the Q reference point, the
underlying services used by ROSE are those provided by GFT-Control and not those provided by the
Association Control Service Element (ACSE) and the Reliable Transport Service Element (RTSE).
The Dialogue Service Element (DSE) provides a means of associating ROSE APDUs which are not
implicitly associated by an underlying network layer connection.
The Co-ordination Function provides co-ordination between GFT-Control, the various SS-Control entities,
ROSE, DSE and Call Control for different Supplementary services. The relationships it co-ordinates are
beyond the scope of this ETS. It also provides functions to support the handling of unrecognised APDUs.
ETSs specifying the protocol for individual supplementary services will specify how SS-Control entities and
the Co-ordination Function make use of ROSE or DSE.
GFT-Control provides two distinct types of service via the Co-ordination Function:
- transport services for the carriage of Notifications, ROSE APDUs and DSE APDUs between SS-Control
entities in different PTNXs, including transparent relaying through Transit PTNXs. These services can be
related to a Call or independent of a Call; and,
- establishment and release of Call independent signalling connections.
Protocol Control is an extension of the existing ETS 300 172 Protocol Control entity. It provides services to
GFT-Control for:
- the transport of APDUs between Adjacent PTNXs; and
- the establishment and release of signalling connections (Call independent Connection oriented service)
between Adjacent PTNXs.
This entity builds on the ETS 300 172 (Basic call) Protocol Control in the following way:
- the Call
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.