SIST-TS TS 101 890-1 V1.1.1:2004

• Abstract:

  Design of H.245 PICS for protocol implementation in Terminal, Gatekeeper and Gateway.

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI TS 101 890-1 V1.1.1 (2002-01) - Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Compliance Specifications; TIPHON profile for ITU-T H.245; Part 1: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST-TS TS 101 890-1 V1.1.1:2004 is the Slovenian version of ETSI TS 101 890-1, a technical specification for TIPHON Release 3. It defines a Protocol Implementation Conformance Statement (PICS) proforma for the TIPHON profile for ITU-T H.245, so a supplier can state which H.245 capabilities and options are implemented in a terminal, gatekeeper, or gateway context.

What does SIST-TS TS 101 890-1 V1.1.1:2004 specify?

SIST-TS TS 101 890-1 V1.1.1:2004 specifies the PICS proforma for the control protocol for multimedia communication defined by ITU-T Recommendation H.245. The document tells suppliers how to declare implementation support in a standard format, so conformance claims can be checked in a consistent way.

The scope links the PICS to TIPHON Release 3 and to the technology mapping in TS 101 883. It also points to ISO/IEC 9646-7 for the conformance-statement format, which matters because the document is a questionnaire to be completed, not the protocol specification itself.

The document is organized into four clauses and one normative annex:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions and abbreviations
• Clause 4 - Conformance to this PICS proforma specification
• Annex A - Normative PICS proforma for the TIPHON Release 3 profile for ITU-T Recommendation H.245

Annex A is the working part of the document. It contains completion guidance, identification fields, a global conformance statement, and the capability tables that a supplier fills in.

What are the key requirements of SIST-TS TS 101 890-1 V1.1.1:2004?

SIST-TS TS 101 890-1 V1.1.1:2004 requires a supplier claiming conformance to complete the Annex A PICS proforma and identify both the supplier and the implementation. In practice, this gives buyers and test labs a traceable statement for a specific product version and system setup.

Clause 4 is strict about the form of the PICS. If the document claims conformance, the completed proforma must be technically equivalent to Annex A and must keep the same numbering, naming, and order of items.

Annex A.1 and A.2 define the information that has to be recorded:

• date of the statement
• Implementation Under Test (IUT) identification
• System Under Test (SUT) identification
• product supplier
• client, if different from the supplier
• PICS contact person

This matters because conformance statements are only useful when they can be tied to a named implementation and a person who can answer follow-up questions.

Annex A.1.2 defines the status and support notation used throughout the tables. The document distinguishes mandatory, optional, not applicable, prohibited, qualified optional, conditional, and irrelevant items. That helps a reader see at a glance what must be supported, what may be supported, and what is excluded in the given context.

Annex A.5 asks a global conformance question: are all mandatory capabilities implemented? A negative answer means the implementation is non-conforming, so any missing mandatory item has to be identified and explained. For a supplier, this is the main checkpoint before the PICS can be used in a conformance claim.

Annex A.6 breaks the profile into capability areas:

• TIPHON roles and H.245 roles
• H.245 entities
• H.245 message sets
• H.245 procedures
• timers and counters
• primitives, states, and variables for each procedure
• message content for key H.245 messages

The practical point is that conformance is not just about listing supported features. The proforma also checks how an implementation behaves in protocol procedures, which messages it sends and receives, and which state machines and timers it supports.

The profile separates originating endpoint and terminating endpoint behavior in Annex A.6.9 and A.6.10. That matters for products that can operate on either side of a call, because the PICS asks about sending and receiving support for both roles.

What terms does SIST-TS TS 101 890-1 V1.1.1:2004 define?

Implementation Conformance Statement (ICS) - A supplier statement that says which capabilities have been implemented in a claimed-conforming implementation or system.

ICS proforma - A questionnaire-style document that becomes an ICS when it is completed for a particular implementation or system.

Protocol Implementation Conformance Statement (PICS) - An ICS for a protocol specification, used here for the H.245 profile in TIPHON Release 3.

Implementation Under Test (IUT) - The implementation being described or evaluated in the PICS.

System Under Test (SUT) - The system that contains the IUT and provides the operating context recorded in the PICS.

System Conformance Statement (SCS) - The system-level conformance statement that the PICS is linked to in Annex A.3.

Who uses SIST-TS TS 101 890-1 V1.1.1:2004?

SIST-TS TS 101 890-1 V1.1.1:2004 is used by suppliers of H.245 implementations who need to publish a standardized conformance statement. It is also used by test laboratories, assessors, and quality teams that need to compare a product against the TIPHON profile.

In practice, it supports work on terminal, gatekeeper, and gateway implementations in multimedia and VoIP environments. Buyers and integrators can use the completed PICS to check which protocol roles, message sets, and procedures a product supports before deployment.

What changed in SIST-TS TS 101 890-1 V1.1.1:2004 from the previous edition?

SIST-TS TS 101 890-1 V1.1.1:2004 is stated to be identical to ETSI TS 101 890-1 Version 1.1.1. The document history records publication as January 2002.

Which standards are used with SIST-TS TS 101 890-1 V1.1.1:2004?

• ETSI TS 101 883 - Defines the TIPHON architecture using H.323 and provides the profile context that this PICS applies to.
• ITU-T Recommendation H.323 - Gives the packet-based multimedia communications system framework used by the TIPHON architecture.
• ITU-T Recommendation H.245 - Defines the multimedia control protocol being profiled and conformance-checked here.
• ISO/IEC 9646-1 - Provides the general conformance testing concepts and framework.
• ISO/IEC 9646-7 - Provides the rules and guidance for Implementation Conformance Statements and the notation used in the PICS.
• TIPHON Part 2 and Part 3 - The foreword identifies related deliverables for Test Suite Structure and Test Purposes, and for Abstract Test Suite plus partial PIXIT proforma.

What does the SIST-TS TS 101 890-1 V1.1.1:2004 document contain?

Annex A is a table-driven proforma with item numbers, status fields, support fields, value fields, references, and prerequisite lines. It gives the structure for completing the PICS and for showing which items are mandatory, optional, prohibited, or conditional.

The annex includes identification sections, role selection, entity tables, message-set tables, procedure tables, timer and counter tables, and state-machine tables. It also includes detailed message-content tables for items such as Terminal Capability Set, Open Logical Channel, Close Logical Channel, and Request Mode.

The document is therefore useful for conformance declarations and for later testing of H.245 behavior, especially where a product must show how it handles control, capability exchange, channel setup, and related signaling.

SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Specifikacija tehnološke ustreznosti - Profil TIPHON za ITU-T H.245 - 1. del:
Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacija
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Technology Compliance Specifications; TIPHON profile for ITU-T H.245; Part
1: Protocol Implementation Conformance Statement (PICS) proforma specification
Ta slovenski standard je istoveten z: TS 101 890-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;
TIPHON profile for ITU-T H.245;
Part 1: Protocol Implementation Conformance
Statement (PICS) proforma specification

2 ETSI TS 101 890-1 V1.1.1 (2002-01)

Reference
DTS/TIPHON-06018-1
Keywords
ICS, IP, PICS, supplementary service, testing,
VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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:
[e-mail]
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 2002.
All rights reserved.
ETSI
3 ETSI TS 101 890-1 V1.1.1 (2002-01)
Contents
Intellectual Property Rights.6
Foreword.6
Introduction .6
1 Scope.7
2 References.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.8
4 Conformance to this PICS proforma specification.8
Annex A (normative): PICS proforma for TIPHON Release 3 profile for ITU-T
Recommendation H.245 .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 Client (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.13
A.6 Capabilities.14
A.6.1 Role.14
A.6.2 Major capabilities.14
A.6.3 H.245 Entities.15
A.6.4 H.245 Message sets .15
A.6.5 H.245 Procedures.16
A.6.6 Timers for H.245 procedures.16
A.6.7 Counters for H.245 procedures.17
A.6.8 Primitives and states for H.245 procedures .17
A.6.8.1 MSDSE procedures.17
A.6.8.2 CESE procedures.18
A.6.8.3 LCSE procedures.19
A.6.8.4 B-LCSE procedures.20
A.6.8.5 CLCSE procedures.21
A.6.8.6 MTSE procedures.22
A.6.8.7 RMESE procedures.24
A.6.8.8 MRSE procedures.25
A.6.8.9 RTDSE procedures.26
A.6.8.10 MLSE procedures.26
A.6.9 Originating endpoint.28
A.6.9.1 Sending.28
A.6.9.1.1 Master slave Determination message set (MD).28
A.6.9.1.2 Terminal capability message set (CE).28
A.6.9.1.3 Logical Channel signalling message set (LC).28
ETSI
4 ETSI TS 101 890-1 V1.1.1 (2002-01)
A.6.9.1.4 Multiplex Table signalling message set (MT).29
A.6.9.1.5 Request multiplex Table signalling message set (RM) .29
A.6.9.1.6 Request Mode message set (MR).29
A.6.9.1.7 Round Trip delay message set (RT).29
A.6.9.1.8 Maintenance Loop message set (ML) .30
A.6.9.1.9 Communication Mode message set (CM) .30
A.6.9.1.10 Conference Request and response message set (CR) .31
A.6.9.1.11 Multilink Message set (MM).32
A.6.9.1.12 Logical channel Bit rate change message set (LB) .32
A.6.9.1.13 Commands message set (CD) .32
A.6.9.1.14 Indications Message set (IM) .33
A.6.9.2 Receiving.33
A.6.9.2.1 Master slave Determination message set (MD).33
A.6.9.2.2 Terminal capability message set (CE).33
A.6.9.2.3 Logical Channel signalling message set (LC).34
A.6.9.2.4 Multiplex Table signalling message set (MT).34
A.6.9.2.5 Request Multiplex table signalling message set (RM) .34
A.6.9.2.6 Request Mode message set (MR).35
A.6.9.2.7 Round Trip delay message set (RT).35
A.6.9.2.8 Maintenance Loop message set (ML) .35
A.6.9.2.9 Communication Mode message set (CM) .35
A.6.9.2.10 Conference Request and response message set (CR) .36
A.6.9.2.11 Multilink Message set (MM).37
A.6.9.2.12 Logical channel Bit rate change message set (LB) .37
A.6.9.2.13 Commands message set (CD) .37
A.6.9.2.14 Indications Message set (IM) .38
A.6.9.3 Message content.38
A.6.9.3.1 Terminal Capability Set .38
A.6.9.3.2 Terminal Capability Set Acknowledge .38
A.6.9.3.3 Terminal Capability Set Reject .39
A.6.9.3.4 Open Logical Channel.39
A.6.9.3.5 Open Logical Channel Acknowledge.39
A.6.9.3.6 Open Logical Channel Reject .39
A.6.9.3.7 Open Logical Channel Confirm .40
A.6.9.3.8 Close Logical Channel .40
A.6.9.3.9 Close Logical Channel Acknowledge .40
A.6.9.3.10 Request mode.40
A.6.9.3.11 Request Mode Acknowledge.41
A.6.9.3.12 Request Mode Reject .41
A.6.10 Terminating endpoint.41
A.6.10.1 Sending.41
A.6.10.1.1 Master slave Determination message set (MD).41
A.6.10.1.2 Terminal capability message set (CE).42
A.6.10.1.3 Logical Channel signalling message set (LC).42
A.6.10.1.4 Multiplex Table signalling message set (MT).42
A.6.10.1.5 Request Multiplex table signalling message set (RM) .43
A.6.10.1.6 Request Mode message set (MR).43
A.6.10.1.7 Round Trip delay message set (RT).43
A.6.10.1.8 Maintenance Loop message set (ML) .44
A.6.10.1.9 Communication Mode message set (CM) .44
A.6.10.1.10 Conference Request and response message set (CR) .45
A.6.10.1.11 Multilink Message set (MM).46
A.6.10.1.12 Logical channel Bit rate change message set (LB) .46
A.6.10.1.13 Commands message set (CD) .46
A.6.10.1.14 Indications Message set (IM) .47
A.6.10.2 Receiving.47
A.6.10.2.1 Master slave Determination message set (MD).47
A.6.10.2.2 Terminal capability message set (CE).47
A.6.10.2.3 Logical Channel signalling message set (LC).48
A.6.10.2.4 Multiplex Table signalling message set (MT).48
A.6.10.2.5 Request Multiplex table signalling message set (RM) .48
A.6.10.2.6 Request Mode message set (MR).49
ETSI
5 ETSI TS 101 890-1 V1.1.1 (2002-01)
A.6.10.2.7 Round Trip delay message set (RT).49
A.6.10.2.8 Maintenance Loop message set (ML) .49
A.6.10.2.9 Communication Mode message set (CM) .49
A.6.10.2.10 Conference Request and response message set (CR) .50
A.6.10.2.11 Multilink Message set (MM).51
A.6.10.2.12 Logical channel Bit rate change message set (LB) .51
A.6.10.2.13 Commands message set (CD) .51
A.6.10.2.14 Indications Message set (IM) .52
A.6.10.3 Message content.52
A.6.10.3.1 Terminal Capability Set .52
A.6.10.3.2 Terminal Capability Set Acknowledge .52
A.6.10.3.3 Terminal Capability Set Reject .53
A.6.10.3.4 Open Logical Channel.53
A.6.10.3.5 Open Logical Channel Acknowledge.53
A.6.10.3.6 Open Logical Channel Reject .53
A.6.10.3.7 Open Logical Channel Confirm .54
A.6.10.3.8 Close Logical Channel .54
A.6.10.3.9 Close Logical Channel Acknowledge .54
A.6.10.3.10 Request mode.54
A.6.10.3.11 Request Mode Acknowledge.55
A.6.10.3.12 Request Mode Reject .55
History .56

ETSI
6 ETSI TS 101 890-1 V1.1.1 (2002-01)
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 multi-part deliverable covering Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3; Technology Compliance Specifications; TIPHON profile for
ITU-T Recommendation H.245, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification".
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 890-1 V1.1.1 (2002-01)
1 Scope
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the control
protocol for multimedia communication as specified in ITU-T Recommendation H.245 [3] 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 [5].
The supplier of a protocol implementation which is claimed to conform to ITU-T Recommendation H.245 [3] as
specified in 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: "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 (Version 3, 1999): "Packet-based multimedia communications
systems".
[3] ITU-T Recommendation H.245 (Version 7, 2000): "Control protocol for multimedia
communication".
[4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[5] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
• Terms defined in ITU-T Recommendation H.323 [2];
• Terms defined in ITU-T Recommendation H.245 [3];
• Terms defined in ISO/IEC 9646-1 [4] and in ISO/IEC 9646-7 [5].
In particular, the following terms defined in ISO/IEC 9646-1 [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
NOTE: The PICS can take several forms: protocol PICS, profile PICS, profile specific PICS, information object
PICS, etc.
ETSI
8 ETSI TS 101 890-1 V1.1.1 (2002-01)
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes PICS
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:
B-LCSE Bi-directional Logical Channel Signalling Entity
CESE Capability Exchange Signalling Entity
CLCSE Close Logical Channel Signalling Entity
GK GateKeeper
ICS Implementation Conformance Statement
IUT Implementation Under Test
LCSE Logical Channel Signalling Entity
MLSE Maintenance Loop Signalling Entity
MRSE Mode Request Signalling Entity
MSDSE Master Slave Determination Signalling Entity
MTSE Multiplex Table Signalling Entity
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
RMESE Request Multiplex Entry Signalling Entity
RTDSE Round Trip Delay Signalling Entity
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.
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 890-1 V1.1.1 (2002-01)
Annex A (normative):
PICS proforma for TIPHON Release 3 profile for ITU-T
Recommendation H.245
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.245 as specified in 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;
- Role and 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 ITU-T Recommendation H.245.
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 (for example parameters, timers, etc.). It
implicitly means "is < item description > supported by the implementation?"
Status column
The following notations, defined in ISO/IEC 9646-7, are used for the status column:
M or m mandatory - the capability is required to be supported;
O or o optional - the capability may be supported or not;
N/A or n/a not applicable - in the given context, it is impossible to use the capability;
X or x prohibited (excluded) - there is a requirement not to use this capability in the given context;
O.i or o.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 and the logic of their selection which is defined
immediately following the table;
Ci.j or ci.j 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 the table and "j" is an integer
sequentially allocated inside the table. Ci.j forms a unique conditional status expression which is
defined immediately following the table;
ETSI
10 ETSI TS 101 890-1 V1.1.1 (2002-01)
I or i irrelevant (out-of-scope) - the requirement on the capability is outside the scope of the reference
specification. No answer is requested from the supplier.
Reference column
The reference column makes reference to ITU-T Recommendation H.245 except where explicitly stated otherwise.
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 or n/a no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
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 "?" (For example ?3). This expression shall be given
in the space for comments provided at the bottom of the table. It uses predicates defined in the 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 1: ?3: IF prof1 THEN Y ELSE N.
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 column
The values allowed column contains the type, the list, the range, or the length of values allowed. The following
notations are used:
Range of values: < min value > . < max value >: Example: 5 . 20.
List of values: < value1 >, < value2 >, ., < valueN >: Example: 2, 4, 6, 8, 9;
Example: '1101'B, '1011'B, '1111'B;
Example: '0A'H, '34'H, '2F'H.
List of named values: < name1 >(< val1 >), < name2 >(< val2 >), ., Example: reject(1), accept(2).
< nameN >(< valN >:
Length: size (< min size > . < max size >): Example: size (1 . 8).

Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the values or the
ranges of values supported by the implementation shall be indicated.
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. If there is more than one support column in a table, the columns are
discriminated by letters (a, b, etc.), respectively.
EXAMPLE 2: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.
EXAMPLE 3: A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in
table 6 of annex A.
ETSI
11 ETSI TS 101 890-1 V1.1.1 (2002-01)
Prerequisite line
A prerequisite line takes the form: Prerequisite: < predicate >.
A prerequisite line after a clause or before a table header indicates that the whole clause or the whole table is not
required to be completed if the predicate is FALSE.
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 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:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
ETSI
12 ETSI TS 101 890-1 V1.1.1 (2002-01)
Operating system:
...............................................................................................................................................................................................
A.2.4 Product supplier
Name:
...............................................................................................................................................................................................
Address:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
A.2.5 Client (if different from product supplier)
Name:
...............................................................................................................................................................................................
Address:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Telephone number:
...............................................................................................................................................................................................
Facsimile number:
...............................................................................................................................................................................................
E-mail address:
...............................................................................................................................................................................................
ETSI
13 ETSI TS 101 890-1 V1.1.1 (2002-01)
Additional information:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
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:
...............................................................................................................................................................................................
.................................................................................................................................
...