Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology compliance specifications; Part 1: Revision/Update of H.225.0 Protocol Implementation Conformance Statement (PICS) proforma specification for Terminal, Gatekeeper and Gateway

DTS/TIPHON-06016-1

Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3. izdaja - Specifikacija tehnološke ustreznosti - 1. del: Popravek/obnova izjave o skladnosti izvedbe protokola (PICS) H.225.0 - Proforma specifikacija za terminal, vratarja in prehod

General Information

Status
Published
Publication Date
06-Feb-2002
Current Stage
12 - Completion
Due Date
20-Feb-2002
Completion Date
07-Feb-2002
Technical specification
TS TS 101 804-1 V1.1.1:2004
English language
70 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Specifikacija tehnološke ustreznosti - 1. del: Popravek/obnova izjave o
skladnosti izvedbe protokola (PICS) H.225.0 - Proforma specifikacija za terminal,
vratarja in prehod
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Technology compliance specifications; Part 1: Revision/Update of H.225.0
Protocol Implementation Conformance Statement (PICS) proforma specification for
Terminal, Gatekeeper and Gateway
Ta slovenski standard je istoveten z: TS 101 804-1 Version 1.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3;
Technology compliance specifications;
Part 1: Revision/update of H.225.0
Protocol Implementation Conformance
Statement (PICS) proforma specification
for Terminal, Gatekeeper and Gateway

2 ETSI TS 101 804-1 V1.1.1 (2002-02)

Reference
DTS/TIPHON-06016-1
Keywords
gatekeeper, gateway, H.323, IP, multimedia,
PICS, supplementary service, terminal, testing,
VoIP
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 enregistrée à la
Sous-Préfecture 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:
editor@etsi.fr
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
3 ETSI TS 101 804-1 V1.1.1 (2002-02)
Contents
Intellectual Property Rights.6
Foreword.6
Introduction .6
1 Scope.7
2 References.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Conformance to this PICS proforma specification.8
Annex A (normative): PICS proforma for ITU-T Recommendation H.225.0 according to
TIPHON profile .9
A.1 Guidance for completing the PICS proforma.9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions .9
A.1.3 Instructions for completing the PICS proforma.11
A.2 Identification of the implementation .11
A.2.1 Date of the statement.11
A.2.2 Implementation Under Test (IUT) identification .11
A.2.3 System Under Test (SUT) identification.11
A.2.4 Product supplier.12
A.2.5 Terminal (if different from product supplier).12
A.2.6 PICS contact person .13
A.3 PICS/System Conformance Statement (SCS) .13
A.4 Identification of the protocol.13
A.5 Global statement of conformance.14
A.6 H.323 entities.14
A.7 H.323 ITU-T protocol version.14
A.8 TIPHON roles.14
A.9 Terminal or Gateway roles.15
A.9.1 Subsidiary capabilities.15
A.9.2 RAS Messages and Parameters .16
A.9.2.1 RAS Messages.16
A.9.2.2 Parameters for Gatekeeper Request .17
A.9.2.3 Parameters for Gatekeeper Confirm .17
A.9.2.4 Parameters for Gatekeeper Reject.18
A.9.2.5 Parameters for Registration Request.19
A.9.2.6 Parameters for Registration Confirm .20
A.9.2.7 Parameters for Registration Reject .21
A.9.2.8 Parameters for Unregistration Request .21
A.9.2.9 Parameters for Unregistration Confirm.22
A.9.2.10 Parameters for Unregistration Reject.22
A.9.3 BCC Messages and Parameters .22
A.9.3.1 BCC Messages.22
A.9.3.2 Parameters for Alerting.23
A.9.3.3 Parameters for Call Proceeding .24
A.9.3.4 Parameters for Connect.25
A.9.3.5 Parameters for Information.26
ETSI
4 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.9.3.6 Parameters for Progress.27
A.9.3.7 Parameters for Release Complete .28
A.9.3.8 Parameters for Setup.29
A.9.3.9 Parameters for Setup Acknowledge.30
A.9.3.10 Parameters for Facility.31
A.9.4 RAS Timer.31
A.10 Gatekeeper network role .32
A.10.1 Subsidiary capabilities.32
A.10.2 RAS Messages and Parameters .33
A.10.2.1 RAS Messages.33
A.10.2.2 Parameters for Gatekeeper Request .34
A.10.2.3 Parameters for Gatekeeper Confirm .34
A.10.2.4 Parameters for Gatekeeper Reject.35
A.10.2.5 Parameters for Registration Request.36
A.10.2.6 Parameters for Registration Confirm .37
A.10.2.7 Parameters for Registration Reject .38
A.10.2.8 Parameters for Unregistration Request .38
A.10.2.9 Parameters for Unregistration Confirm.39
A.10.2.10 Parameters for Unregistration Reject.39
A.10.2.11 Parameters for Location Request.40
A.10.2.12 Parameters for Location Confirm .40
A.10.2.13 Parameters for Location Reject.41
A.10.3 BCC Messages and Parameters .41
A.10.3.1 BCC Messages.41
A.10.3.2 Parameters for Alerting.42
A.10.3.3 Parameters for Call Proceeding .43
A.10.3.4 Parameters for Connect.44
A.10.3.5 Parameters for Information.45
A.10.3.6 Parameters for Progress.46
A.10.3.7 Parameters for Release Complete .47
A.10.3.8 Parameters for Setup.48
A.10.3.9 Parameters for Setup Acknowledge.49
A.10.3.10 Parameters for Facility.50
A.10.4 RAS Timer.50
A.11 Gatekeeper inter-Domain role.51
A.11.1 Subsidiary capabilities.51
A.11.2 RAS Messages and Parameters .52
A.11.2.1 RAS Messages.52
A.11.2.2 Parameters for Gatekeeper Request .53
A.11.2.3 Parameters for Gatekeeper Confirm .53
A.11.2.4 Parameters for Gatekeeper Reject.54
A.11.2.5 Parameters for Registration Request.55
A.11.2.6 Parameters for Registration Confirm .56
A.11.2.7 Parameters for Registration Reject .57
A.11.2.8 Parameters for Unregistration Request .57
A.11.2.9 Parameters for Unregistration Confirm.58
A.11.2.10 Parameters for Unregistration Reject.58
A.11.2.11 Parameters for Location Request.59
A.11.2.12 Parameters for Location Confirm .59
A.11.2.13 Parameters for Location Reject.60
A.11.3 BCC Messages and Parameters .60
A.11.3.1 BCC Messages.60
A.11.3.2 Parameters for Alerting.61
A.11.3.3 Parameters for Call Proceeding .62
A.11.3.4 Parameters for Connect.63
A.11.3.5 Parameters for Information.64
A.11.3.6 Parameters for Progress.65
A.11.3.7 Parameters for Release Complete .66
A.11.3.8 Parameters for Setup.67
A.11.3.9 Parameters for Setup Acknowledge.68
ETSI
5 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.11.3.10 Parameters for Facility.69
A.11.4 RAS Timer.69
History .70

ETSI
6 ETSI TS 101 804-1 V1.1.1 (2002-02)
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 Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON).
The present document is part 1 of a multi-part deliverable covering the H225.0 protocol for Terminal, Gatekeeper and
Gateway as identified below:
Part 1: "Revision/update of H.225.0 Protocol Implementation Conformance Statement (PICS) proforma
specification for Terminal, Gatekeeper and Gateway";
Part 2: "H.225.0 conformance test specifications; Test Suite Structure and Test Purposes (TSS&TP) specification
for Terminal, Gatekeeper and Gateway";
Part 3: "H.225.0 conformance test specifications; Abstract Test Suite (ATS) and PIXIT proforma specification
for Terminal, Gatekeeper and Gateway".
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 telecommunication specification. Such a statement is called an Implementation
Conformance Statement (ICS).
ETSI
7 ETSI TS 101 804-1 V1.1.1 (2002-02)
1 Scope
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the call
signalling protocols for packet-based multimedia communication systems defined in ITU-T Recommendation H.323 [2]
in compliance with the relevant requirements specified in TS 101 883 [1] and in accordance with the relevant guidance
given in ISO/IEC 9646-7 [10].
The supplier of a protocol implementation which is claimed to conform to ITU-T Recommendation H.323 [2] profiled
by TS 101 883 [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.
2 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 TS 101 883 (V.0.3.0): "Telecommunications and Internet protocol Harmonization Over
Networks (TIPHON) Release 3; Technology Mapping; Implementation of TIPHON architecture
using H.323".
[2] ITU-T Recommendation H.323 (1999): "Framework and wire-protocol for multiplexed call
signalling transport".
[3] ITU-T Recommendation H.225.0 (1999): "Call signalling protocols and media stream
packetization for packet-based multimedia communication systems".
[4] ITU-T Recommendation H.323 (1998): "Framework and wire-protocol for multiplexed call
signalling transport".
[5] ITU-T Recommendation H.225.0 (1998): "Call signalling protocols and media stream
packetization for packet-based multimedia communication systems".
[6] ITU-T Recommendation H.323 (2000): "Framework and wire-protocol for multiplexed call
signalling transport".
[7] ITU-T Recommendation H.225.0 (2000): "Call signalling protocols and media stream
packetization for packet-based multimedia communication systems".
[8] ETSI TS 101 882: "Telecommunications and Internet protocol Harmonization Over Networks
(TIPHON) Release 3; Protocol Framework Definition and Interface Requirement Definition;
General".
[9] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
[10] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
ETSI
8 ETSI TS 101 804-1 V1.1.1 (2002-02)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions defined in TS 101 883 [1], ITU-T Recommendation
H.323 [2], ITU-T Recommendation H.225.0 [3], ISO/IEC 9646-1 [9] and ISO/IEC 9646-7 [10] and the following apply:
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes a PICS
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
NOTE: The PICS can take several forms: protocol PICS, profile PICS, profile specific PICS, information object
PICS, etc.
Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
GK GateKeeper
ICS Implementation Conformance Statement
IUT Implementation Under Test
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCS System Conformance Statement
SUT System Under Test
4 Conformance to this PICS proforma specification
If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be
technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and
ordering of the proforma items.
A PICS which conforms to the present document shall be a conforming PICS proforma completed in accordance with
the guidance for completion given in clause A.1.
ETSI
9 ETSI TS 101 804-1 V1.1.1 (2002-02)
Annex A (normative):
PICS proforma for ITU-T Recommendation H.225.0
according to TIPHON profile
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 ITU-T Recommendation H.323 profiled by TS 101 883 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;
- H.323 entities concerned;
- H.323 ITU-T protocol version;
- TIPHON roles;
- RAS Messages;
- parameters for each RAS message;
- BCC Messages;
- parameters for each BCC message;
- timers.
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.
Item column
The item column contains a qualified number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (for example parameters, timers, etc.). It
implicitly means "is < item description > supported by the implementation?".
ETSI
10 ETSI TS 101 804-1 V1.1.1 (2002-02)
Status column
The following notations, defined in ISO/IEC 9646-7, are used for the status column:
M mandatory - the capability is required to be supported;
O indicates an optional requirement in ITU-T Recommendation H.225.0. However, only sending of
the parameter/message is optional. When the parameter/message is received a TIPHON compliant
entity shall act upon the parameter/message in accordance with the procedures as described in the
main body of the present document;
"" an empty status field indicates that ITU-T Recommendation H.225.0 shall be followed in regards
to optionally;
N/A not applicable - in the given context, it is impossible to use the capability;
X prohibited (excluded) - there is a requirement not to use this capability in the given context;
Ot.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which
identifies a unique group of related optional items in the table numbered t and the logic of their
selection which is defined immediately following the table;
Ct.i 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 a unique conditional status in the
table numbered t, expression which is defined immediately following the table.
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, 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, directly or after evaluation of a conditional
status).
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
NOTE: As stated in ISO/IEC 9646-7, 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 on a PDU means that the semantics of that parameter are supported.
Values allowed
Notes describe the content of the field, when only restricted values are supported, for sent message.
References to items
For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists,
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.5/4 is the reference to the answer of item 4 in table 5 of annex A.
Prerequisite line
A prerequisite line takes the form: Prerequisite: < predicate >.
A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be
completed if the predicate is FALSE.
ETSI
11 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.1.3 Instructions for completing the PICS proforma
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 or supported column boxes provided, using the notation
described in clause A.1.2.
If necessary, the supplier may provide additional comments in space at the bottom of the tables, or separately on sheets
of paper.
More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
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 terminal 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:
...............................................................................................................................................................................................
ETSI
12 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.2.4 Product supplier
Name:
...............................................................................................................................................................................................
Address:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.2.5 Terminal (if different from product supplier)
Name:
...............................................................................................................................................................................................
Address:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
ETSI
13 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.2.6 PICS contact person
(A person to contact if there are any queries concerning the content of the PICS)
Name:
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.3 PICS/System Conformance Statement (SCS)
Provide the relationship of the PICS with the SCS for the system.
A.4 Identification of the protocol
The PICS proforma applies to the following standards:
ETSI TS 101 883: "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3;
Technology Mapping; Implementation of TIPHON architecture using H.323".
ITU-T Recommendation H.323 (1998): "Framework and wire-protocol for multiplexed call signalling transport";
ITU-T Recommendation H.323 (1999): "Framework and wire-protocol for multiplexed call signalling transport";
ITU-T Recommendation H.323 (2000): "Framework and wire-protocol for multiplexed call signalling transport";
ITU-T Recommendation H.225 (1998): " Call signalling protocols and media stream packetization for packet-based
multimedia communication systems ";
ITU-T Recommendation H.225 (1999): " Call signalling protocols and media stream packetization for packet-based
multimedia communication systems";
ITU-T Recommendation H.225 (2000): " Call signalling protocols and media stream packetization for packet-based
multimedia communication systems".
ETSI
14 ETSI TS 101 804-1 V1.1.1 (2002-02)
A.5 Global statement of conformance
Are all mandatory capabilities implemented? (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, on pages attached to the PICS proforma.
A.6 H.323 entities
Table A.1: H.323 entities
Item H.323 entitie Reference Status Support

HE 1 Terminal  O.1.1
HE 2 Gatekeeper O.1.1
HE 3 Gateway O.1.1
Comments:
O.1.1: It is mandatory to support at least one of the items
A.7 H.323 ITU-T protocol version
Table A.2: H.323 entities
Item H.323 protocol version Reference Status Support

VE 1 H.323 Version 2 O.2.1
VE 2 H.323 Version 3 O.2.1
VE 3 H.323 Version 4 O.2.1
Comments:
O.2.1: It is mandatory to support at least one of the items
A.8 TIPHON roles
Table A.3: TIPHON roles
Item TIPHON role Reference Status Support

TR 1 Terminal C.3.1
TR 1.1 Originating Terminal C:M
TR 1.2 Terminating Terminal C:M
TR 2 Gatekeeper network C.3.2
TR 3 Gatekeeper inter-Domain C.3.2
TR 3.1 Originating Gatekeeper inter-Domain C:M
TR 3.2 Terminating Gatekeeper inter-Domain C:M
TR 3 Gateway  C.3.3
TR 3.1 Originating Gateway C:M
TR 3.2 Terminating Gateway C:M
Comments:
ETSI
15 ETSI TS 101 804-1 V1.1.1 (2002-02)
C.3.1: If A.1/HE1 then M else N/A
C.3.2: If A.1/HE2 then M else N/A
C.3.3: If A.1/HE3 then M else N/A
A.9 Terminal or Gateway roles
This clause contains the PICS proforma tables related to the terminal role. It concerns exchange between a Terminal or
a gateway and its Gatekeeper at C1 and R1 TIPHON references point. The following tables need to be completed only
for Terminal or Gateway
Prerequisite: A.3/TR1 OR A.3/TR3 item -- Terminal role
A.9.1 Subsidiary capabilities
Table A.4: Subsidiary capabilities
Item Subsidiary capabilities Reference H.323 TIPHON Support
Status Status
T_SC 1 Security parameter negotiation B.1.2.1 [1] O O
T_SC 2 Registration Keep-Alive procedure 4.2 [1] O M
T_SC 3 Pre-granted admission 4.1 [1] O M
T_SC 4 Gatekeeper routed model 5.1.1.1.1 [1] O M
T_SC 5 En-Bloc Procedure 5.1.1.1.2 [1], 5.1.12.1.1 [1] O C.4.1
T_SC 6 Overlap Sending 5.1.1.1.1 [1], 5.1.12.1 [
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...