SIST ES 202 170 V1.1.1:2005

• Abstract:

  Produce as an ES the associated conformance test specifications for the API for Open Service Access (OSA) control protocol defined in ES 201 915 Parts 1 to 12. The work content is the following: i) protocol conformance implementation statements based on the service properties defined; ii) test configurations for both the application and service capability (gateway) side; iii) test purposes in the form of sequence diagrams detailing the test scripts to be provided; iv) test suite structure (including valid and invalid behaviou).

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 202 170 V1.1.1 (2003-04) - Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification for Framework and SCFs

SIST ES 202 170 V1.1.1:2005 is the Slovenian adoption of ETSI ES 202 170 Version 1.1.1, an Implementation Conformance Statement (ICS) proforma for the Open Service Access (OSA) Application Programming Interface (API). It tells a supplier what to declare about the OSA Framework and Service Capability Feature (SCF) capabilities implemented in ES 201 915 Parts 1 to 12, so conformance can be described in a consistent way. In practice, it is used to state supported roles, interfaces, methods and optional features for the OSA API.

What does SIST ES 202 170 V1.1.1:2005 specify?

SIST ES 202 170 V1.1.1:2005 specifies the ICS proforma for the OSA API. It is the questionnaire-style document that a supplier completes to identify the implementation, declare protocol support, and state which OSA Framework and SCF capabilities are supported.

The document is organized with a general clause, definitions and abbreviations, and a conformance clause, followed by normative annexes for each OSA part covered by the proforma. The annexes provide structured tables for the supported items and use the same numbering and ordering as the standard.

Annex	What it covers
A	General ICS proforma for Framework and SCFs
B	ES 201 915-3 Framework functionalities
C	ES 201 915-4 Call Control SCF
D	ES 201 915-5 User Interaction SCF
E	ES 201 915-6 Mobility SCF
F	ES 201 915-7 Terminal Capabilities SCF
G	ES 201 915-8 Data Session Control SCF
H	ES 201 915-9 Generic Messaging SCF
I	ES 201 915-10 Connectivity Manager SCF
J	ES 201 915-11 Account Management SCF
K	ES 201 915-12 Charging SCF

This structure matters because a supplier can complete only the annexes relevant to the claimed implementation, while test and conformance teams can compare like with like across products.

What are the key requirements of SIST ES 202 170 V1.1.1:2005?

The document’s main requirement is that a claimed conforming ICS must be completed in the form and order defined by the annexes. Clause 4 says the submitted ICS proforma has to be technically equivalent to the text in the standard and keep the same numbering, naming and ordering. That matters because it makes statements comparable and usable in conformance assessment.

How the ICS proforma is completed

Annex A explains the support column notation used throughout the proforma: Y/y for supported, N/n for not supported, and N/A or - where no answer is required under the stated conditions. It also explains how item references work and how prerequisite lines control whether a table or clause needs to be completed. In practice, this means the person filling in the form must answer each item in a traceable way, and only skip items when the stated condition allows it.

What implementation identification must be given

The proforma includes identification fields for the implementation under test and the system under test, plus supplier information and, in several annexes, a PICS contact person. Clause 3 and the annex guidance make the implementation identity part of the conformance record. This matters because the statement must be tied to a specific product or system, not just to a generic design.

What the Framework annex covers

Annex B covers the Framework roles and APIs, including the Access Session API, the Framework-to-Application API, the Framework-to-Enterprise Operator API, and the Framework-to-Service API. It breaks these into interfaces and methods, with each method marked as mandatory, optional, or conditionally required. In practice, this gives a supplier a checklist for declaring exactly which framework functions are implemented, such as access, authentication, service registration, discovery, heartbeat, load management, fault management and event notification.

What Call Control, Mobility and Data Session Control cover

Annex C covers Call Control SCF functionality for Generic Call Control, MultiParty Call Control, MultiMedia Call Control and Conference Call Control, with interfaces and methods for each. Annex E covers Mobility SCF and includes user status reporting methods, with at least one method in the group required. Annex G covers Data Session Control SCF methods such as connect, release, supervision, charging-related control, deassignment, continued processing and callback handling. For users of the standard, these annexes show which call, mobility and session-control behaviors must be declared and which options are available.

What the optional and conditional support means

Many tables use mandatory, optional and conditional markings, and some tables state that at least one item in a group must be supported. Examples in the Framework annex include grouped choices for fault, load and heartbeat functions, and in the data session and connectivity annexes there are similar “at least one” requirements. This matters in practice because two compliant implementations may expose different feature sets while still using the same proforma.

What the connectivity and other service annexes cover

Annex I covers Connectivity Manager SCF and includes VPrN, VPrP and Enterprise Network Site methods. Annex H, J and K provide proformas for Generic Messaging, Account Management and Charging SCF. These annexes are useful when a product supports network provisioning, messaging, account handling or charging functions and needs to record that support in a standard format.

What terms does SIST ES 202 170 V1.1.1:2005 define?

Implementation Conformance Statement (ICS) - A statement by the supplier saying which capabilities of a claimed conforming implementation are implemented.

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

API ICS - An ICS for an implementation claimed to conform to a given API specification.

Protocol ICS (PICS) - An ICS for an implementation claimed to conform to a given protocol specification.

Implementation Under Test (IUT) - The implementation being examined for conformance.

System Under Test (SUT) - The system in which the implementation under test resides.

SCS - System Conformance Statement, listed in the abbreviations section as a related conformance statement type.

Who uses SIST ES 202 170 V1.1.1:2005?

Suppliers use this standard to complete the conformance statement for an OSA API implementation. They need it when they want to show which framework and SCF features are supported and how the product is identified.

Test labs, conformance assessors and integrators use it to compare declared support against the OSA parts referenced in the standard. Buyers, quality managers and technical reviewers can use it to check whether a product claims the right OSA capabilities before integration or procurement.

It is also relevant to telecom engineering teams working with OSA-based systems, especially where service capability features such as call control, mobility, messaging, connectivity, account management and charging are involved.

What changed in SIST ES 202 170 V1.1.1:2005 from the previous edition?

The document history shows version V1.1.1 as the published edition. The title and contents identify it as the ICS proforma specification for Framework and SCFs for the OSA API.

Which standards are used with SIST ES 202 170 V1.1.1:2005?

The standard is used together with the ES 201 915 series, Parts 1 to 12. Those parts define the OSA API overview, common data definitions, Framework, and the SCFs for Call Control, User Interaction, Mobility, Terminal Capabilities, Data Session Control, Generic Messaging, Connectivity Manager, Account Management and Charging.

It also relies on ISO/IEC 9646-1 for conformance testing concepts and ISO/IEC 9646-7 for ICS practice. ETSI ETS 300 406 is named for the testing and specification methodology used to structure the conformance material.

What does the SIST ES 202 170 V1.1.1:2005 document contain?

The document contains a general ICS proforma, guidance on how to complete it, and normatively structured annexes for the OSA Framework and each SCF part named in the contents. The annexes are laid out as tables with support columns, prerequisites, identification fields and global conformance statements.

For the parts shown in the contents, the annexes also list the interfaces and methods to be declared, with mandatory and optional statuses attached to individual items. Where a group of functions is marked as “at least one,” the completed ICS must show which member of the group is supported.

The document is designed for declaration and assessment, not for giving implementation code or performance limits. Its practical value is in making support claims about OSA API features explicit, comparable and complete across suppliers and test teams.

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) –
Izjava o skladnosti izvedbe (ICS) – Proforma specifikacija za okvirni del in funkcije
SCF
Open Service Access (OSA); Application Programming Interface (API); Implementation
Conformance Statement (ICS) proforma specification for Framework and SCFs
Ta slovenski standard je istoveten z: ES 202 170 Version 1.1.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Implementation Conformance Statement (ICS)
proforma specification for Framework and SCFs

2 ETSI ES 202 170 V1.1.1 (2003-04)

Reference
DES/SPAN-120092
Keywords
API, OSA, ICS
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 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 170 V1.1.1 (2003-04)
Contents
Intellectual Property Rights.8
Foreword.8
1 Scope.9
2 References.9
3 Definitions and abbreviations.10
3.1 Definitions.10
3.2 Abbreviations.10
4 Conformance.10
Annex A (normative): ICS proforma for Framework and SCFs - General.11
A.1 Guidance for completing the ICS proforma .11
A.1.1 Purposes and structure.11
A.1.2 Abbreviations and conventions .11
A.1.3 Instructions for completing the ICS proforma.12
A.2 Identification of the implementation .13
A.2.1 Product supplier.13
A.2.2 Client (if different from product supplier).13
A.3 Identification of the protocol.14
A.4 Global statement of conformance.14
A.5 General.14
A.5.1 Functionalities.14
Annex B (normative): ICS proforma for ES 201 915-3 framework functionalities.15
B.1 Guidance for completing the ICS proforma .15
B.1.1 Purposes and structure.15
B.1.2 Abbreviations and conventions .15
B.1.3 Instructions for completing the ICS proforma.15
B.2 Identification of the implementation .16
B.2.1 Date of the statement.16
B.2.2 Implementation under test identification.16
B.2.3 System under test identification .16
B.2.4 PICS contact person .16
B.3 Identification of the protocol.17
B.4 Global statement of conformance.17
B.5 Framework Functionalities.17
B.5.1 Roles.17
B.5.2 APIs.17
B.5.2.1 Access Session API.18
B.5.2.1.1 Service Capability Server Role .18
B.5.2.1.1.1 Interfaces.18
B.5.2.1.1.2 Methods.18
B.5.2.1.2 Framework Role.18
B.5.2.1.2.1 Interfaces.18
B.5.2.1.2.2 Methods.19
B.5.2.2 Framework-to-Application API.20
B.5.2.2.1 Interfaces.20
B.5.2.2.2 Methods.20
B.5.2.3 Framework-to-Enterprise Operator API .21
ETSI
4 ETSI ES 202 170 V1.1.1 (2003-04)
B.5.2.3.1 Interfaces.22
B.5.2.3.2 Methods.22
B.5.2.4 Framework-to-Service API.23
B.5.2.4.1 Service Capability Server Role .23
B.5.2.4.1.1 Interfaces.23
B.5.2.4.1.2 Methods.23
B.5.2.4.2 Framework Role.25
B.5.2.4.2.1 Interfaces.25
B.5.2.4.2.2 Methods.25
Annex C (normative): ICS proforma for ES 201 915-4 Call Control SCF .28
C.1 Guidance for completing the ICS proforma .28
C.1.1 Purposes and structure.28
C.1.2 Abbreviations and conventions .28
C.1.3 Instructions for completing the ICS proforma.28
C.2 Identification of the implementation .29
C.2.1 Date of the statement.29
C.2.2 Implementation under test identification.29
C.2.3 System under test identification .29
C.2.4 PICS contact person .29
C.3 Identification of the protocol.30
C.4 Global statement of conformance.30
C.5 Call Control SCF Functionalities .30
C.5.1 Major capabilities.30
C.5.2 Interfaces.31
C.5.2.1 Interfaces for Generic Call Control Service.31
C.5.2.2 Interfaces for MultiParty Call Control Service .31
C.5.2.3 Interfaces for MultiMedia Call Control Service .31
C.5.2.4 Interfaces for Conference Call Control Service .31
C.5.3 Methods.32
C.5.3.1 Methods for Generic Call Control Service .32
C.5.3.2 Methods for MultiParty Call Control Service.32
C.5.3.3 Methods for MultiMedia Call Control Service .34
C.5.3.4 Methods for Conference Call Control Service.36
Annex D (normative): ICS proforma for ES 201 915-5 User Interaction SCF.38
D.1 Guidance for completing the ICS proforma .38
D.1.1 Purposes and structure.38
D.1.2 Abbreviations and conventions .38
D.1.3 Instructions for completing the ICS proforma.38
D.2 Identification of the implementation .39
D.2.1 Date of the statement.39
D.2.2 Implementation under test identification.39
D.2.3 System under test identification .39
D.2.4 PICS contact person .39
D.3 Identification of the protocol.40
D.4 Global statement of conformance.40
D.5 User Interaction SCF Functionalities .40
D.5.1 Interfaces.40
D.5.2 Methods.41
Annex E (normative): ICS proforma for ES 201 915-6 Mobility SCF.42
E.1 Guidance for completing the ICS proforma .42
E.1.1 Purposes and structure.42
E.1.2 Abbreviations and conventions .42
ETSI
5 ETSI ES 202 170 V1.1.1 (2003-04)
E.1.3 Instructions for completing the ICS proforma.42
E.2 Identification of the implementation .42
E.2.1 Date of the statement.42
E.2.2 Implementation under test identification.43
E.2.3 System under test identification .43
E.2.4 PICS contact person .43
E.3 Identification of the protocol.44
E.4 Global statement of conformance.44
E.5 Mobility SCF Functionalities .44
E.5.1 Major capabilities.44
E.5.2 Interfaces.44
E.5.3 Methods.45
Annex F (normative): ICS proforma for ES 201 915-7 Terminal Capabilities SCF .47
F.1 Guidance for completing the ICS proforma .47
F.1.1 Purposes and structure.47
F.1.2 Abbreviations and conventions .47
F.1.3 Instructions for completing the ICS proforma.47
F.2 Identification of the implementation .48
F.2.1 Date of the statement.48
F.2.2 Implementation under test identification.48
F.2.3 System under test identification .48
F.2.4 PICS contact person .48
F.3 Identification of the protocol.49
F.4 Global statement of conformance.49
F.5 Terminal Capabilities SCF Functionalities .49
F.5.1 Interfaces.49
F.5.2 Methods.49
Annex G (normative): ICS proforma for ES 201 915-8 Data Session Control SCF.50
G.1 Guidance for completing the ICS proforma .50
G.1.1 Purposes and structure.50
G.1.2 Abbreviations and conventions .50
G.1.3 Instructions for completing the ICS proforma.50
G.2 Identification of the implementation .51
G.2.1 Date of the statement.51
G.2.2 Implementation under test identification.51
G.2.3 System under test identification .51
G.2.4 PICS contact person .51
G.3 Identification of the protocol.52
G.4 Global statement of conformance.52
G.5 Data Session Control SCF Functionalities .52
G.5.1 Interfaces.52
G.5.2 Methods.52
Annex H (normative): ICS proforma for ES 201 915-9 Generic Messaging SCF .54
H.1 Guidance for completing the ICS proforma .54
H.1.1 Purposes and structure.54
H.1.2 Abbreviations and conventions .54
H.1.3 Instructions for completing the ICS proforma.54
H.2 Identification of the implementation .55
H.2.1 Date of the statement.55
ETSI
6 ETSI ES 202 170 V1.1.1 (2003-04)
H.2.2 Implementation under test identification.55
H.2.3 System under test identification .55
H.2.4 PICS contact person .55
H.3 Identification of the protocol.56
H.4 Global statement of conformance.56
H.5 Generic Messaging SCF Functionalities .56
H.5.1 Interfaces.56
H.5.2 Methods.57
Annex I (normative): ICS proforma for ES 201 915-10 Connectivity Manager SCF .58
I.1 Guidance for completing the ICS proforma .58
I.1.1 Purposes and structure.58
I.1.2 Abbreviations and conventions .58
I.1.3 Instructions for completing the ICS proforma.58
I.2 Identification of the implementation .59
I.2.1 Date of the statement.59
I.2.2 Implementation under test identification.59
I.2.3 System under test identification .59
I.2.4 PICS contact person .59
I.3 Identification of the protocol.60
I.4 Global statement of conformance.60
I.5 Connectivity Manager SCF Functionalities .60
I.5.1 Interfaces.60
I.5.2 Methods.61
Annex J (normative): ICS proforma for ES 201 915-11 Account Management SCF.63
J.1 Guidance for completing the ICS proforma .63
J.1.1 Purposes and structure.63
J.1.2 Abbreviations and conventions .63
J.1.3 Instructions for completing the ICS proforma.63
J.2 Identification of the implementation .64
J.2.1 Date of the statement.64
J.2.2 Implementation under test identification.64
J.2.3 System under test identification .64
J.2.4 PICS contact person .64
J.3 Identification of the protocol.65
J.4 Global statement of conformance.65
J.5 Account Management SCF Functionalities.65
J.5.1 Interfaces.65
J.5.2 Methods.66
Annex K (normative): ICS proforma for ES 201 915-12 Charging SCF .67
K.1 Guidance for completing the ICS proforma .67
K.1.1 Purposes and structure.67
K.1.2 Abbreviations and conventions .67
K.1.3 Instructions for completing the ICS proforma.67
K.2 Identification of the implementation .68
K.2.1 Date of the statement.68
K.2.2 Implementation under test identification.68
K.2.3 System under test identification .68
K.2.4 PICS contact person .68
K.3 Identification of the protocol.69
ETSI
7 ETSI ES 202 170 V1.1.1 (2003-04)
K.4 Global statement of conformance.69
K.5 Charging SCF Functionalities .69
K.5.1 Major capabilities.69
K.5.2 Interfaces.69
K.5.3 Methods.70
History .71

ETSI
8 ETSI ES 202 170 V1.1.1 (2003-04)
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).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
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
9 ETSI ES 202 170 V1.1.1 (2003-04)
1 Scope
The present document provides the Implementation Conformance Statement (ICS) proforma for the Application
Programming Interface for Open Service Access (OSA) defined in ES 201 915 [1] to [12] in compliance with the
relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [14] and
ETS 300 406 [15].
The supplier of an implementation which is claimed to conform to a part of ES 201 915 [1] to [12] is required to
complete a copy of the ICS proforma provided in annex A through to annex J of the present document and is required to
provide the information necessary to identify 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.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ETSI ES 201 915-1: "Open Service Access (OSA); Application Programming Interface (API);
Part 1: Overview".
[2] ETSI ES 201 915-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 2: Common Data Definitions".
[3] ETSI ES 201 915-3: "Open Service Access (OSA); Application Programming Interface (API);
Part 3: Framework".
[4] ETSI ES 201 915-4: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control SCF".
[5] ETSI ES 201 915-5: "Open Service Access (OSA); Application Programming Interface (API);
Part 5: User Interaction SCF".
[6] ETSI ES 201 915-6: "Open Service Access (OSA); Application Programming Interface (API);
Part 6: Mobility SCF".
[7] ETSI ES 201 915-7: "Open Service Access (OSA); Application Programming Interface (API);
Part 7: Terminal Capabilities SCF".
[8] ETSI ES 201 915-8: "Open Service Access (OSA); Application Programming Interface (API);
Part 8: Data Session Control SCF".
[9] ETSI ES 201 915-9: "Open Service Access (OSA); Application Programming Interface (API);
Part 9: Generic Messaging SCF".
[10] ETSI ES 201 915-10: "Open Service Access (OSA); Application Programming Interface (API);
Part 10: Connectivity Manager SCF".
[11] ETSI ES 201 915-11: "Open Service Access (OSA); Application Programming Interface (API);
Part 11: Account Management SCF".
[12] ETSI ES 201 915-12: "Open Service Access (OSA); Application Programming Interface (API);
Part 12: Charging SCF".
ETSI
10 ETSI ES 202 170 V1.1.1 (2003-04)
[13] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[14] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[15] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 201 915 [1] to [12],
ISO/IEC 9646-1 [13] and ISO/IEC 9646-7 [14] and the following apply:
API ICS: ICS for an implementation or system claimed to conform to a given API specification
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 ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS,
etc.
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes an ICS
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:
API ICS Application Programming Interface
ICS Implementation Conformance Statement
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
SCS System Conformance Statement
SUT System Under Test
4 Conformance
If it claims to conform to the present document, the actual ICS proforma to be filled in by a supplier shall be technically
equivalent to the text of the ICS proforma given in annexes A through J, and shall preserve the numbering/naming and
ordering of the proforma items.
An ICS which conforms to the present document shall be a conforming ICS proforma completed in accordance with the
guidance for completion given in clause 1 of the annex A.
ETSI
11 ETSI ES 202 170 V1.1.1 (2003-04)
Annex A (normative):
ICS proforma for Framework and SCFs - General
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 ICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed ICS.
A.1 Guidance for completing the ICS proforma
A.1.1 Purposes and structure
The purpose of this ICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in ES 201 915 [1] to [12] may provide information about the implementation in a standardized
manner.
The PICS proforma is subdivided into clauses for the following categories of information:
• instructions for completing the PICS proforma;
• identification of the protocol;
• global statement of conformance;
• roles;
• functionalities.
A.1.2 Abbreviations and conventions
The ICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines
presented in ISO/IEC 9646-7 [14].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7 [14], are used for the status column:
NOTE: In the case where items of the group do not always belong to the same table, all o.i shall be defined in the
last clause of the ICS proforma, and the text "which is defined immediately following the table" should be
replaced by "which is defined in the last clause of this annex".
ci: Conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying an unique conditional status
expression which is defined immediately following the table.
Reference column
The reference column makes reference to parts of ES 201 915 [1] to [12], except where explicitly stated otherwise.
ETSI
12 ETSI ES 202 170 V1.1.1 (2003-04)
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 [14], 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.
References to items
For each possible item answer (answer in the support column) within the ICS 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 1: A.5/4 is the reference to the answer of item 4 in table A.5.
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in
table A.6.
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite line after a clause or table title indicates that the whole clause or the whole table is
...