SIST EN 301 140-2 V1.4.1:2003

• Abstract:

  The scope is to produce a PICS proforma specification for the physical entity SCP for ETSI Core INAP CS-2 covering the following interfaces: SCF-SSF, SCF-SRF, SCF-CUSF. It should be an extension to the EN 301 140-2

• Status: Published
• Publication Date: 31-Oct-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-2003
• Due Date: 01-Nov-2003
• Completion Date: 01-Nov-2003
• Ref Project: ETSI EN 301 140-2 V1.4.1 (2002-07) - Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST EN 301 140-2 V1.4.1:2003 is the Slovenian standard identical to ETSI EN 301 140-2 Version 1.4.1. It is a Protocol Implementation Conformance Statement (PICS) proforma for Intelligent Network Application Protocol (INAP) Capability Set 2 (CS2), so a supplier can state which CS2 functions, options, timers and value ranges an implementation supports. In practice, it is used to describe and check conformance for implementations of the Core INAP CS2 interfaces.

What does SIST EN 301 140-2 V1.4.1:2003 specify?

SIST EN 301 140-2 V1.4.1:2003 specifies the PICS proforma used to record conformance information for INAP CS2 implementations. The document is organized as a short main body with the scope, references, definitions and conformance rules, plus a normative annex that contains the completion guidance and the detailed SSP and SCP proformas.

Annex / clause	What it covers
Clause 1	Scope of the PICS proforma for INAP CS2
Clause 2	References used by the standard
Clause 3	Definitions, symbols and abbreviations
Clause 4	Conformance rule for the completed ICS/PICS
Annex A (normative)	PICS proforma, guidance for completion, SSP and SCP tables, timers, range constants
Annex B (informative)	Bibliography

Annex A contains the practical working material: identity fields, conformance statements, support tables, and the detailed items to be completed by the supplier. The SCP section in Annex A.6.2 is the part most directly aligned with the stated SCP scope and its SCF-SSF, SCF-SRF and SCF-CUSF interfaces.

What are the key requirements of SIST EN 301 140-2 V1.4.1:2003?

The key requirements are mostly about how the PICS is completed and how support is declared for each role, interface and operation. Annex A turns a protocol implementation into a structured declaration that can be reviewed, compared and used for test selection.

Completion and traceability

Clause 4 requires any claimed conformance statement to be technically equivalent to the Annex A proforma, with the same numbering, naming and ordering. In practice, this keeps different suppliers’ statements comparable and prevents important items from being moved or renamed.

Annex A.1 defines how to read and complete the tables. The status column uses the standard conformance notations, and the support column is completed by the supplier using the allowed answers and conditional expressions. This matters because the completed PICS must show not only what is supported, but also what is not applicable, excluded, or dependent on other options.

Annex A.2 to A.5 collect the identifying information: date, Implementation Under Test (IUT), System Under Test (SUT), hardware configuration, operating system, supplier, client, contact person, protocol identification, and the global statement of conformance. In practice, this ties the conformance claim to a specific implementation and gives testers a contact point for clarification.

Role-specific support in SSP and SCP

Annex A.6 splits the proforma into SSP and SCP sections. Each section lists the physical entities, the external interfaces, and the supported application contexts for that role. For the SCP view, the key interfaces are SCF-SSF, SCF-SRF and SCF-CUSF, each marked with its own support status.

The application-context tables are important because they show which INAP CS2 communication profiles apply to each side of the exchange. This lets an engineer or tester see whether the implementation is expected to speak as SCF-to-SSF, SCF-to-SRF, or SCF-to-CUSF, instead of assuming one generic INAP capability.

Operation coverage and protocol content

Annex A.6.1.4 and A.6.2.4 list the supported operations for the two role views. The document covers operations for charging, call control, announcements, user interaction, service filtering, UTSI, association management and call-segment handling. For each operation, the tables show whether the operation is mandatory, optional or conditional for that role.

The operation tables also list the associated arguments, results and errors. That is the part a buyer, engineer or test lab uses to check whether an implementation can parse and generate the required protocol data, not just whether it claims the operation name.

A few examples show the practical breadth of the proforma:

• call setup and routing: InitialDP, Connect, ConnectToResource, InitiateCallAttempt
• charging: ApplyCharging, ApplyChargingReport, FurnishChargingInformation, SendChargingInformation
• user interaction: PlayAnnouncement, PromptAndCollectUserInformation, PromptAndReceiveMessage, ScriptRun
• event reporting and control: RequestReportBCSMEvent, EventReportBCSM, RequestNotificationChargingEvent
• call-segment and leg handling: CreateCallSegmentAssociation, MoveLeg, SplitLeg, MergeCallSegments

Timers and range limits

Annex A.6.1.6 and A.6.2.6 list timers for operations and states. Some timers have standard value ranges, while others are marked so that the implementor must state the supported value. This is important in practice because timeout handling affects interoperability and test execution.

Annex A.6.1.7 and A.6.2.7 list supported range constants such as lengths and counts for identifiers, numbers, messages, counters and related protocol data. These declarations tell a tester what encoded lengths and list sizes the implementation claims to handle.

What terms does SIST EN 301 140-2 V1.4.1:2003 define?

PICS (Protocol Implementation Conformance Statement) is the supplier’s statement of which capabilities and options an implementation supports.

ICS (Implementation Conformance Statement) is the completed conformance statement, filled in according to the proforma guidance.

IUT (Implementation Under Test) is the protocol implementation being checked against the proforma.

SUT (System Under Test) is the system that contains the IUT during conformance evaluation.

SCS (System Conformance Statement) is the document that summarizes which OSI standards are implemented and what conformance is claimed.

Static conformance review is the comparison of the PICS against the static conformance requirements in the standard.

INAP (Intelligent Network Application Protocol) is the protocol family covered by the standard, and CS2 (Capability Set 2) is the specific capability set addressed here.

Who uses SIST EN 301 140-2 V1.4.1:2003?

Suppliers of INAP CS2 implementations use the standard to complete the PICS for their product and to declare the supported functions, timers and data limits. That is the starting point for claiming conformance to EN 301 140-1.

Test laboratories and conformance engineers use the completed PICS to select test cases and check which operations, arguments and errors must be covered. The note in the foreword makes clear that a PICS is needed to evaluate conformance of a particular implementation.

Quality managers, integrators and buyers use the statement to compare implementations on the same basis. The PICS tells them which interfaces and application contexts are supported, so they can match a product to the intended network role.

What changed in SIST EN 301 140-2 V1.4.1:2003 from the previous edition?

The foreword states that the earlier public-enquiry version contained the SSP PICS proforma only, while this version also contains the CUSF PICS proforma. The document history also shows the earlier V1.3.3 publication and the later V1.4.1 publication.

Which standards are used with SIST EN 301 140-2 V1.4.1:2003?

Standard / part	Contribution
ETSI EN 301 140-1	The protocol specification referenced by the PICS proforma
ISO/IEC 9646-1	General concepts for OSI conformance testing; also the basis for static conformance review
ISO/IEC 9646-7	Rules for Implementation Conformance Statements, including table notation and completion guidance
Part 3 of EN 301 140	Test Suite Structure and Test Purposes (TSS&TP) for SSF
Part 4 of EN 301 140	Abstract Test Suite (ATS) specification and PIXIT proforma for SSF
Part 5 of EN 301 140	Distributed Functional Plane (DFP), modified from ITU-T Recommendation Q.1224 (1997)

Annex B also cites ETSI ETS 300 406 as background for protocol and profile conformance testing methodology.

What does the SIST EN 301 140-2 V1.4.1:2003 document contain?

Annex A.1 explains the completion rules, including the meaning of the status entries, the support column, conditional answers, and prerequisite lines. Annex A.2 to A.5 provide the identification and conformance declaration forms, so the completed PICS can be tied to a named implementation and contact person.

Annex A.6 contains the detailed conformance tables for SSP and SCP. These tables cover physical entities, external interfaces, application contexts, operations, arguments, results, errors, timers and range constants.

The operation tables are the core of the document. They include the protocol data for call control, charging, announcements, event reporting, user interaction, association management and call-segment handling, all arranged so that a supplier can mark exactly what is supported.

For testing and certification work, the document also gives the timer references and the supported size or count limits for protocol fields. That makes the PICS useful not just as a declaration, but also as a basis for conformance review and test planning.

SLOVENSKI STANDARD
01-november-2003
Inteligentno omrežje (IN) - Aplikacijski (uporabovni) protokol inteligentnega
omrežja (INAP) – Drugi nabor zmožnosti inteligentnega omrežja (CS2) – 2. del:
Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacije
Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2
(CS2); Part 2: Protocol Implementation Conformance Statement (PICS) proforma
specification
Ta slovenski standard je istoveten z: EN 301 140-2 Version 1.4.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Intelligent Network (IN);
Intelligent Network Application Protocol (INAP);
Capability Set 2 (CS2);
Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification

2 ETSI EN 301 140-2 V1.4.1 (2002-07)

Reference
REN/SPAN-120068
Keywords
CS2, ICS, IN, INAP, PICS
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.
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 EN 301 140-2 V1.4.1 (2002-07)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
3 Definitions, symbols and abbreviations .7
3.1 Definitions.7
3.2 Symbols.8
3.3 Abbreviations.8
4 Conformance.8
Annex A (normative): PICS proforma for EN 301 140-1 .9
A.1 Guidance for completing the ICS proforma .9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions .9
A.1.3 Instructions for completing the ICS proforma.11
A.1.4 Guidelines for reading the PICS.12
A.2 Identification of the implementation .12
A.2.1 Date of the statement.12
A.2.2 Implementation Under Test (IUT) identification .12
A.2.3 System Under Test (SUT) identification.12
A.2.4 Product supplier.13
A.2.5 Client.13
A.2.6 PICS contact person .14
A.3 PICS/SCS relationship.14
A.4 Identification of the protocol.15
A.5 Global statement of conformance.15
A.6 PICS proforma tables .15
A.6.1 SSP.15
A.6.1.1 Physical entities.15
A.6.1.2 External interfaces.15
A.6.1.3 Application contexts supported.16
A.6.1.4 Operations supported.17
A.6.1.5 Supported arguments, results and errors.18
A.6.1.5.1 ActivateServiceFiltering.18
A.6.1.5.2 ActivityTest.19
A.6.1.5.3 ApplyCharging.19
A.6.1.5.4 ApplyChargingReport.19
A.6.1.5.5 AssistRequestInstructions.20
A.6.1.5.6 CallGap.21
A.6.1.5.7 CallInformationReport.22
A.6.1.5.8 CallInformationRequest.22
A.6.1.5.9 Cancel.23
A.6.1.5.10 CollectInformation.23
A.6.1.5.11 Connect.24
A.6.2.5.12 ConnectAssociation.25
A.6.1.5.13 ConnectToResource.26
A.6.1.5.14 Continue.26
A.6.2.5.15 ContinueAssociation.27
A.6.1.5.16 ContinueWithArguments.28
A.6.1.5.17 CreateCallSegmentAssociation.29
ETSI
4 ETSI EN 301 140-2 V1.4.1 (2002-07)
A.6.1.5.18 DisconnectForwardConnection.29
A.6.1.5.19 DisconnectForwardConnectionWithArguments.29
A.6.1.5.20 DisconnectLeg.30
A.6.1.5.21 EntityReleased.30
A.6.1.5.22 EstablishTemporaryConnection.31
A.6.1.5.23 EventNotificationCharging.32
A.6.1.5.24 EventReportBCSM.33
A.6.1.5.25 EventReportBCUSM.34
A.6.1.5.26 FurnishChargingInformation.34
A.6.1.5.27 InitialAssociationDP.35
A.6.1.5.28 InitialDP.36
A.6.1.5.29 InitiateAssociation.37
A.6.1.5.30 InitiateCallAttempt.38
A.6.1.5.31 ManageTriggerData.39
A.6.1.5.32 MergeCallSegments.39
A.6.1.5.33 MoveCallSegments.40
A.6.1.5.34 MoveLeg.40
A.6.1.5.35 PlayAnnouncement.41
A.6.1.5.36 PromptAndCollectUserInformation.43
A.6.1.5.37 PromptAndReceiveMessage.44
A.6.1.5.38 ReleaseAssociation.45
A.6.1.5.39 ReleaseCall.45
A.6.1.5.40 ReportUTSI.46
A.6.1.5.41 RequestNotificationChargingEvent.46
A.6.1.5.42 RequestReportBCSMEvent.47
A.6.1.5.43 RequestReportBCUSMEvent.47
A.6.1.5.44 RequestReportUTSI.48
A.6.1.5.45 ResetTimer.48
A.6.1.5.46 SendChargingInformation.49
A.6.1.5.47 SendSTUI.49
A.6.1.5.48 ServiceFilteringResponse.50
A.6.1.5.49 SpecializedResourceReport.50
A.6.1.5.50 SplitLeg.50
A.6.1.6 Timers.52
A.6.1.7 Range Constants supported.53
A.6.2 SCP.55
A.6.2.1 Physical entities.55
A.6.2.2 External interfaces.55
A.6.2.3 Application contexts supported.55
A.6.2.4 Operations supported.56
A.6.2.5 Supported arguments, results and errors.57
A.6.2.5.1 ActivateServiceFiltering.57
A.6.2.5.2 ActivityTest.58
A.6.2.5.3 ApplyCharging.58
A.6.2.5.4 ApplyChargingReport.58
A.6.2.5.5 AssistRequestInstructions.59
A.6.2.5.6 CallGap.60
A.6.2.5.7 CallInformationReport.61
A.6.2.5.8 CallInformationRequest.61
A.6.2.5.9 Cancel.62
A.6.2.5.10 CollectInformation.62
A.6.2.5.11 Connect.63
A.6.2.5.12 ConnectAssociation.64
A.6.2.5.13 ConnectToResource.65
A.6.2.5.14 Continue.65
A.6.2.5.15 ContinueAssociation.66
A.6.2.5.16 ContinueWithArguments.67
A.6.2.5.17 CreateCallSegmentAssociation.68
A.6.2.5.18 DisconnectForwardConnection.68
A.6.2.5.19 DisconnectForwardConnectionWithArgument.68
A.6.2.5.20 DisconnectLeg.69
A.6.2.5.21 EntityReleased.69
ETSI
5 ETSI EN 301 140-2 V1.4.1 (2002-07)
A.6.2.5.22 EstablishTemporaryConnection.70
A.6.2.5.23 EventNotificationCharging.71
A.6.2.5.24 EventReportBCSM.72
A.6.2.5.25 EventReportBCUSM.73
A.6.2.5.26 FurnishChargingInformation.73
A.6.2.5.27 InitialAssociationDP.74
A.6.2.5.28 InitialDP.75
A.6.2.5.29 InitiateAssociation.76
A.6.2.5.30 InitiateCallAttempt.77
A.6.2.5.31 ManageTriggerData.78
A.6.2.5.32 MergeCallSegments.78
A.6.2.5.33 MoveCallSegments.79
A.6.2.5.34 MoveLeg.79
A.6.2.5.35 PlayAnnouncement.80
A.6.2.5.36 PromptAndCollectUserInformation.82
A.6.2.5.37 PromptAndReceiveMessage.84
A.6.2.5.38 ReleaseAssociation.85
A.6.2.5.39 ReleaseCall.85
A.6.2.5.40 ReportUTSI.86
A.6.2.5.41 RequestNotificationChargingEvent.86
A.6.2.5.42 RequestReportBCSMEvent.87
A.6.2.5.43 RequestReportBCUSMEvent.87
A.6.2.5.44 RequestReportUTSI.88
A.6.2.5.45 ResetTimer.88
A.6.2.5.46 ScriptClose.89
A.6.2.5.47 ScriptEvent.89
A.6.2.5.48 ScriptInformation.90
A.6.2.5.49 ScriptRun.90
A.6.2.5.50 SendChargingInformation.91
A.6.2.5.51 SendSTUI.91
A.6.2.5.52 ServiceFilteringResponse.92
A.6.2.5.53 SpecializedResourceReport.92
A.6.2.5.54 SplitLeg.92
A.6.2.6 Timers.94
A.6.2.7 Range Constants supported.96
Annex B (informative): Bibliography .98
History .99

ETSI
6 ETSI EN 301 140-2 V1.4.1 (2002-07)
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 European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
NOTE: The present document was originally released on Public Enquiry with the PICS proforma for the SSP
only. The present version also contains the CUSF PICS proforma.
The present document is part 2 of a multi-part deliverable covering the Intelligent Network Application Protocol
(INAP) Capability Set 2 (CS2) as identified below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF)";
Part 4: "Abstract Test Suite (ATS) specification and Partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma for Service Switching Function (SSF)";
Part 5: "Distributed Functional Plane (DFP) [ITU-T Recommendation Q.1224 (1997), modified]".
To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and
options have been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called a
Protocol Implementation Conformance Statement (PICS).

National transposition dates
Date of adoption of this EN: 19 July 2002
Date of latest announcement of this EN (doa): 31 October 2002
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 April 2003
Date of withdrawal of any conflicting National Standard (dow): 30 April 2003

ETSI
7 ETSI EN 301 140-2 V1.4.1 (2002-07)
1 Scope
The present document is applicable to Intelligent Network Application Protocol (INAP) Capability Set 2 (CS2).
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the Core
INAP CS2 for:
• the physical element SSP on the interfaces SSF/SRF-SCF and CUSF-SCF in compliance with the relevant
requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3];
• the physical element SCP on the interfaces SSF-SCF, SRF-SCF and CUSF-SCF in compliance with the relevant
requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3].
The supplier of a protocol implementation which is claimed to conform to EN 301 140-1 [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 EN 301 140-1: "Intelligent Network (IN); Intelligent Network Application Protocol (INAP);
Capability Set 2 (CS2); Part 1: Protocol specification".
[2] ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 1: General concepts".
[3] ISO/IEC 9646-7: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 7: Implementation Conformance Statements".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 301 140-1 [1], ISO/IEC 9646-1 [2],
ISO/IEC 9646-7 [3] and the following apply:
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes an ICS
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.
Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
ETSI
8 ETSI EN 301 140-2 V1.4.1 (2002-07)
static conformance review: review of the extent to which the static conformance requirements are met by the IUT,
accomplished by comparing the PICS with the static conformance requirements expressed in the relevant standard(s)
NOTE: See ISO/IEC 9646-1 [2].
3.2 Symbols
For the purposes of the present document, the following symbols apply:
AND Boolean "and"
NOT Boolean "not"
OR Boolean "or"
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASE Application Service Element
CS2 Capability Set 2
ICS Implementation Conformance Statement
IN Intelligent Network
INAP Intelligent Network Application Protocol
IUT Implementation Under Test
OSI Open Systems Interconnection
PICS Protocol Implementation Conformance Statement
SCP Service Control Point
SCS System Conformance Statement
SSP Service Switching Point
SUT System Under Test
4 Conformance
If it claims to conform to the present document, the actual Implementation Conformance Statement (ICS) proforma to
be filled in by a supplier shall be technically equivalent to the text of the ICS proforma given in annex A, 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 A.1.
ETSI
9 ETSI EN 301 140-2 V1.4.1 (2002-07)
Annex A (normative):
PICS proforma for EN 301 140-1
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 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 EN 301 140-1 may provide information about the implementation in a standardized manner.
The ICS proforma is subdivided into clauses for the following categories of information:
- guidance for completing the ICS proforma;
- identification of the implementation;
- identification of the protocol;
- global statement of conformance;
- physical entity;
- external interfaces;
- application contexts;
- operations;
- arguments, results and errors;
- timers;
- range constants;
- explicit statements about the implemented capabilities.
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.
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?".
ETSI
10 ETSI EN 301 140-2 V1.4.1 (2002-07)
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 optional - the capability may be supported or not.
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.
o.i qualified optional - for selectable options from a set. "i" is an integer which identifies an unique
group of related optional items and the logic of their selection which is defined immediately
following the table.
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.
c:o optional if the hierarchically preceding option is implemented.
c:o.i qualified optional if the hierarchically preceding option is implemented.- for selectable options
from a set. "i" is an integer which identifies an unique group of related optional items and the logic
of their selection which is defined immediately following the table.
c:m mandatory if the hierarchically preceding option is implemented.
i irrelevant (out-of-scope) - capability outside the scope of the reference specification. No answer is
requested from the supplier.
NOTE 1: This use of "i" status is not to be confused with the suffix "i" to the "o" and "c" statuses above.
Reference column
The reference column makes reference to EN 301 140-1, 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, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
If this ICS 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 "?" (e.g. ?3). This expression shall be given in the space
for comments provided at the bottom of the table. It uses predicates defined in the System Conformance Statement
(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
NOTE 2: 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.
ETSI
11 ETSI EN 301 140-2 V1.4.1 (2002-07)
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: .
example: 5 . 20
- list of values: , , .,
example: 2, 4, 6, 8, 9
example: '1101'B, '1011'B, '1111'B
example: '0A'H, '34'H, '2F'H
- list of named values: (), (), ., ()
example: reject(1), accept(2)
- length: 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 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 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.
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 not required to be
completed if the predicate is FALSE.
A.1.3 Instructions for completing the ICS proforma
The supplier of the implementation shall complete the ICS 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.
More detailed instructions are given at the beginning of the different clauses of the ICS proforma.
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.
ETSI
12 ETSI EN 301 140-2 V1.4.1 (2002-07)
A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
The System Conformance Statement (SCS) as defined in ISO/IEC 9646-1 is a document supplied by the client or
product supplier that summarizes which OSI standards are implemented and to which conformance is claimed. The
PICS/SCS clause should describe the relationship of the PICS to the SCS.
If the answer to the statement in clause A.5 is "Yes", all subsequent clauses should be completed to facilitate selection
of test cases for optional functions.
If the answer to the statement in clause A.5 is "No", all subsequent clauses should be completed, and all non-supported
mandatory capabilities should be identified and explained. Explanations may be entered in the comments field at the
bottom of each table or on attached sheets of paper.
A.1.4 Guidelines for reading the PICS
Optional items in EN 301 140-1 are dealt with as follows:
- mandatory protocol items need to be supported by both operation invokers and responders;
- optional protocol items are optional for operation invokers, but mandatory for operation responders;
- network specific options are optional for both operation invokers and responders.
A.2 Identification of the implementation
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:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
ETSI
13 ETSI EN 301 140-2 V1.4.1 (2002-07)
Hardware configuration:
...............................................................................................................................................................................................
...............................................................................................................................................................................................
...............................................................................................................................................................................................
Operating system:
.......................................................................................................
...