SIST ETS 300 192:2005/A1 E1:2005

Private Telecommunication Network (PTN); Signalling protocol at the S-reference point; Circuit mode basic services

Contains PICS proforma for basic call at the S reference point. See ISO 9646 for definition of PICS

Zasebno omrežje z integriranimi storitvami (PISN) - Signalizacijski protokol na referenčni točki S - Vodovne osnovne storitve

General Information

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Mandate: T-75D.5
• Ref Project: ETSI ETS 300 192/A1 ed.1 (1996-01) - Private Telecommunication Network (PTN); Signalling protocol at the S-reference point; Circuit mode basic services

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 192:2005/A1 E1:2005
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,616LJQDOL]DFLMVNLSURWRNROQD
UHIHUHQþQLWRþNL69RGRYQHRVQRYQHVWRULWYH
Private Telecommunication Network (PTN); Signalling protocol at the S-reference point;
Circuit mode basic services
Ta slovenski standard je istoveten z: ETS 300 192/A1 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 192:2005/A1 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 192:2005/A1 E1:2005

---------------------- Page: 2 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
ETS 300 192
AMENDMENT A1
January 1996
Source: ETSI TC-ECMA Reference: RE/ECMA-00025
ICS: 35.120
PTN, SSIG-BC
Key words:
This amendment A1 modifies
the European Telecommunication Standard ETS 300 192 (1992)
Private Telecommunication Network (PTN);
Signalling protocol at the S-reference point;
Circuit mode basic services
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 - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
*
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 1996. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 2
ETS 300 192: December 1992/A1: January 1996
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 192:2005/A1 E1:2005
Page 3
ETS 300 192: December 1992/A1: January 1996
Foreword
This amendment to ETS 300 192 (1992) 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 amendment contains changes to ETS 300 192 (1992) as detailed below:
- the replacement of the Conformance clause (clause 2);
- the addition of the PICS proforma as a new annex G (normative).
Transposition dates
Date of adoption of this amendment: 31 January 1996
Date of latest announcement of this amendment (doa): 30 April 1996
Date of latest publication or endorsement of this amendment (dop/e): 31 October 1996
Date of withdrawal of any conflicting National Standard (dow): 31 October 1996
This European Telecommunication Standard (ETS) was produced by ECMA using the ECMA guidelines for the production of
standards and using the ECMA stylesheet. In order to avoid undue delays in the approval process for this ETS, it has been
agreed that this ETS will not be converted to the ETSI stylesheet.
Amendments
Page 9, clause 2
Delete subclause 2 and replace it with the following:
2 Conformance
In order to conform to this Standard, a PTNX shall satisfy the PTN requirements and a TE shall satisfy the TE
requirements identified in the Protocol Implementation Conformance Statement (PICS) proforma in annex G.
Page 38, new annex G
Insert the following annex G:

---------------------- Page: 5 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 4
ETS 300 192: December 1992/A1: January 1996
Annex G
(normative)
Protocol Implementation Conformance Statement (PICS) proforma
G.1 Introduction
The supplier of a protocol implementation which is claimed to conform to this Standard shall complete one of
the following Protocol Implementation Conformance Statement (PICS) proformas. The PICS proforma in G.3
is for a PTNX. The PICS proforma in G.4 is for a TE.
A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of
which capabilities and options of the protocol have been implemented. The PICS can have a number of uses,
including use:
− by the protocol implementor, as a check list to reduce the risk of failure to conform to the standard
through oversight;
− by the supplier and acquirer (or potential acquirer) of the implementation, as a detailed indication of the
capabilities of the implementation, stated relative to the common basis for understanding provided by the
standard PICS proforma;
− by the user (or potential user) of the implementation, as a basis for initially checking the possibility of
interworking with another implementation (note that, while interworking cannot be guaranteed, failure to
interwork can often be predicted from incompatible PICS);
− by a protocol tester, as the basis for selecting appropriate tests against which to assess the claim for
conformance of the implementation.
G.2 Instructions for completing the PICS proforma
G.2.1 General structure of the PICS proforma
The PICS proforma is a fixed format questionnaire divided into subclauses each containing a group of
individual items. Each item is identified by an item number, the name of the item (question to be
answered), and the reference(s) to the clause(s) specifying the item in the main body of the Standard.
The "Status" column indicates whether an item is applicable and if so whether support is mandatory or
optional. The following terms are used:
m mandatory (the capability is required for conformance to the protocol);
o optional (the capability is not required for conformance to the protocol, but if the
capability is implemented it is required to conform to the protocol specifications);
o. optional, but support of at least one of the group of options labelled by the same
numeral is required;
x prohibited;
c. conditional requirement, depending on support for the item or items listed in condition
;
:m simple-conditional requirement, the capability being mandatory if item number
is supported, otherwise not applicable;
:o simple-conditional requirement, the capability being optional if item number is
supported, otherwise not applicable.

---------------------- Page: 6 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 5
ETS 300 192: December 1992/A1: January 1996
Answers to the questionnaire items are to be provided in the "Support" column, by simply marking an
answer to indicate a restricted choice (Yes or No), or in the "Not Applicable" column (N/A).
G.2.2 Additional Information
Items of Additional information allow a supplier to provide further information intended to assist the
interpretation of the PICS. It is not intended or expected that a large quantity will be supplied, and a PICS
can be considered complete without any such information. Examples might be an outline of the ways in
which a (single) implementation can be set up to operate in a variety of environments and configurations.
References to items of Additional Information may be entered next to any answer in the questionnaire, and
may be included in items of Exception Information.
G.2.3 Exception Information
It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status
(after any conditions have been applied) in a way that conflicts with the indicated requirements. No pre-
printed answer will be found in the Support column for this. Instead, the supplier is required to write into
the support column an x. reference to an item of Exception Information, and to provide the appropriate
rationale in the Exception item itself.
An implementation for which an Exception item is required in this way does not conform to this Standard.
A possible reason for the situation described above is that a defect in the Standard has been reported, a
correction for which is expected to change the requirement not met by the implementation.

---------------------- Page: 7 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 6
ETS 300 192: December 1992/A1: January 1996
G.3 PICS proforma for ETS 300 192 PTNX implementation
G.3.1 Implementation Identification
Table G.1
Supplier
Contact point for queries about the
PICS
Implementation Name(s) and Version(s)
Other information necessary for full
identification, e.g. name(s) and
version(s) for machines and/or
operating systems; system name(s)
Only the first three items are required for all implementations; other information may be completed as
appropriate in meeting the requirement for full identification.
The terms Name and Version should be interpreted appropriately to correspond with a suppliers
terminology (e.g., Type, Series, Model).
G.3.2 Protocol summary
Table G.2
Protocol version Second Edition
Addenda Implemented
Amendments Implemented
Have any exception items been required? No [ ]  Yes [ ]
(The answer Yes means that the implementation
does not conform to this Standard)
Date of Statement

---------------------- Page: 8 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 7
ETS 300 192: December 1992/A1: January 1996
G.3.3 Major Capabilities
Table G.3
Item Questions/feature Reference Status N/A Support
Z1 Support of the 64 kbps unrestricted bearer 12.5.5 o.1 Yes [ ]  No [ ]
Z2 Support of the 64 kbps bearer with speech 12.5.5 o.1 Yes [ ]  No [ ]
transfer capability
Z3 Support of the 64 kbps bearer with 3,1 kHz 12.5.5 o.1 Yes [ ]  No [ ]
audio transfer capability
Z4 Support of point to point configuration for basic o.2 Yes [ ]  No [ ]
access
Z5 Support of multipoint configuration for basic o.2 Yes [ ]  No [ ]
access
Z6 Support of primary rate access o.2 Yes [ ]  No [ ]
G.3.4 General Procedures
G.3.4.1 Use of the Services of Layer 2
Table G.4
Item Questions/feature Reference Status N/A Support
A1 Establishment of a data link connection 7.1.1 m Yes [ ]
A2 Transfer of data 7.1.2 m Yes [ ]
G.3.4.2 Message Segmentation Procedures
Table G.5
Item Questions/feature Reference Status N/A Support
A3 Maximum message size generated 7.2 m Size [ ]
A4 Maximum message size received 7.2 m Size [ ]
A5 Length of data link information field generated 7.2 o Yes [ ]  No [ ]
< Max. message size generated
A6 Length of data link information field received 7.2 o Yes [ ]  No [ ]
< Max. message size received
A7 Procedures for message segmentation 7.2 c.1 m: Yes [ ]
x: No [ ]
A8 Procedures for message reassembly 7.2 A6:m [ ] m: Yes [ ]
c.1 If A5, then mandatory
 else, prohibited

---------------------- Page: 9 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 8
ETS 300 192: December 1992/A1: January 1996
G.3.4.3 Handling of Protocol Error Conditions
Table G.6
Item Questions/feature Reference Status N/A Support
A9 Treatment of protocol discriminator error 7.3 m Yes [ ]
A10 Treatment of too short message 7.3 m Yes [ ]
A11 Treatment of call reference errors 7.3 m Yes [ ]
A12 Treatment of message type or message sequence 7.3 m Yes [ ]
errors
A13 Treatment of general information element errors 7.3 m Yes [ ]
A14 Treatment of mandatory information element 7.3 m Yes [ ]
errors
A15 Treatment of non mandatory information 7.3 m Yes [ ]
element errors
A16 Treatment of data link reset 7.3 m Yes [ ]
A17 Treatment of data link failure 7.3 m Yes [ ]
G.3.4.4 Handling of a Multipoint Configuration
Table G.7
Item Questions/feature Reference Status N/A Support
A18 Limit of positive responses to a SETUP message 7.4 Z5:o [ ] o: Yes [ ] No [ ]
in a multipoint configuration Limit [ ]
A19 Number of maintained state machines that track 8.2.5 Z5:m [ ] m: Yes [ ]
the overall progression of an incoming call on a Number [ ]
broadcast data link
A20 Procedure for positive responses exceeding the 7.4 A18:m [ ] m: Yes [ ]
limit of PTN capabilities
G.3.4.5 Status and Status Enquiry
Table G.8
Item Questions/feature Reference Status N/A Support
A21 Receipt of a STATUS ENQUIRY message 7.5 m Yes [ ]
A22 Sending of a STATUS ENQUIRY message 7.5 o Yes [ ]  No [ ]
A23 Receipt of a solicited STATUS message 7.5 A22:m [ ] m: Yes [ ]
A24 Receipt of an unsolicited STATUS message 7.5 m Yes [ ]

---------------------- Page: 10 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 9
ETS 300 192: December 1992/A1: January 1996
G.3.5 Messages and Information Elements for General Procedures
Table G.9
Item Questions/feature Reference Status N/A Support
B1 Receipt of the messages in accordance with the 11 m Yes [ ]
procedures supported and receipt of all the
permitted information elements in those
messages
B2 Sending of messages, including for each 11 m Yes [ ]
message those information elements marked as
mandatory for that message, in accordance with
procedures supported
B3 Sending of the Channel identification 11 m Yes [ ]
information element in a SETUP
ACKNOWLEDGE, CALL PROCEEDING,
ALERTING or CONNECT message when that
message is a first response to a SETUP message
B4 Sending of a Progress indicator information 11.2.1 o Yes [ ]  No [ ]
element in an ALERTING message in
connection with the provision of in-band
information/patterns
B5 Sending of a Party category information element 11.2.1 o Yes [ ]  No [ ]
in an ALERTING message
B6 Sending of a Progress indicator information 11.2.2 o Yes [ ]  No [ ]
element in a CALL PROCEEDING message in
connection with the provision of in-band
information/patterns
B7 Sending of a Progress indicator information 11.2.3 o Yes [ ]  No [ ]
element in a CONNECT message in connection
with the provision of in-band
information/patterns
B8 Sending of a Low layer compatibility 11.2.3 o Yes [ ]  No [ ]
information element in a CONNECT message
B9 Sending of a Party category information element 11.2.3 o Yes [ ]  No [ ]
in a CONNECT message
B10 Sending of Date/Time information element in a 11.2.3 o Yes [ ]  No [ ]
CONNECT message
11.2.5 o Yes [ ]  No [ ]
B11 Sending of a Progress indicator information
element in a DISCONNECT message in
connection with the provision of in-band
information/patterns
(continued)

---------------------- Page: 11 ----------------------

SIST ETS 300 192:2005/A1 E1:2005
Page 10
ETS 300 192: December 1992/A1: January 1996
Table G.9 (concluded)
B12 Sending of a Cause information element in a 11.2.7 o Yes [ ]  No [ ]
PROGRESS message
B13 Sending of a Cause information element in a 11.2.8 o Yes [ ]  No [ ]
RELEASE message when it is not the first
clearing message
B14 Sending of a Cause information element in a 11.2.9 o Yes [ ]  No [ ]
RELEASE COMPLETE message when it is not
the first clearing message
B15 Sending of a Sending complete information 11.2.13 o Yes [ ]  No [ ]
element in a SETUP message when en bloc
sending
B16 Sending of a Progress indicator information 11.2.13 o Yes [ ]  No [ ]
element in a SETUP message
B17 Sending of a Calling party number information 11.2.13 o Yes [ ]  No [ ]
element in a SETUP message
B18 Sending of a Calling party subaddress 11.2.13 o Yes [ ]  No [ ]
information element in a SETUP message
B19 Sending of a Called party subaddress 11.2.13 o Yes [ ]  No [ ]
information element in a SETUP message
B20 Sending of a Low layer compatibility 11.2.13 o Yes [ ]  No [ ]
...