ETSI EN 301 140-2 V1.3.2 (1999-03)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentno omrežje (IN) - Drugi nabor zmožnosti inteligentnega omrežja (CS2) - 2. del: Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacijeIntelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 140-2 Version 1.3.3SIST EN 301 140-2:2001en01-februar-2001SIST EN 301 140-2:2001SLOVENSKI
STANDARD



SIST EN 301 140-2:2001



ETSI EN 301 140-2 V1.3.3 (1999-08)European Standard (Telecommunications series)Intelligent Network (IN);Intelligent Network Application Protocol (INAP);Capability Set 2 (CS2);Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specificationSIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)2ReferenceDEN/SPS-03038-2 (ak0i0j20.PDF)KeywordsCS2, IN, INAP, PICS, ICSETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright NotificationNo 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 1999.All rights reserved.SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions, symbols and abbreviations.63.1Definitions.63.2Symbols.73.3Abbreviations.74Conformance.7Annex A (normative):PICS proforma for EN 301 140-1.8A.1Guidance for completing the ICS proforma.8A.1.1Purposes and structure.8A.1.2Abbreviations and conventions.8A.1.3Instructions for completing the ICS proforma.10A.1.4Guidelines for reading the PICS.11A.2Identification of the implementation.11A.2.1Date of the statement.11A.2.2Implementation Under Test (IUT) identification.11A.2.3System Under Test (SUT) identification.11A.2.4Product supplier.12A.2.5Client.12A.2.6PICS contact person.13A.3PICS/SCS relationship.13A.4Identification of the protocol.14A.5Global statement of conformance.14A.6PICS proforma tables.14A.6.1SSF.14A.6.1.1Physical entities.14A.6.1.2External interfaces.14A.6.1.3Application contexts supported.15A.6.1.4Operations supported.16A.6.1.5Supported Arguments, Results and Errors.17A.6.1.5.1ActivateServiceFiltering.17A.6.1.5.2ActivityTest.18A.6.1.5.3ApplyCharging.18A.6.1.5.4ApplyChargingReport.18A.6.1.5.5AssistRequestInstructions.19A.6.1.5.6CallGap.20A.6.1.5.7CallInformationReport.21A.6.1.5.8CallInformationRequest.21A.6.1.5.9Cancel.22A.6.1.5.10CollectInformation.22A.6.1.5.11Connect.23A.6.1.5.12ConnectToResource.24A.6.1.5.13Continue.25A.6.1.5.14ContinueWithArguments.25A.6.1.5.15CreateCallSegmentAssociation.26A.6.1.5.16DisconnectForwardConnection.26SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)4A.6.1.5.17DisconnectForwardConnectionWithArguments.27A.6.1.5.18DisconnectLeg.27A.6.1.5.19EntityReleased.28A.6.1.5.20EstablishTemporaryConnection.28A.6.1.5.21EventNotificationCharging.29A.6.1.5.22EventReportBCSM.30A.6.1.5.23FurnishChargingInformation.31A.6.1.5.24InitialDP.32A.6.1.5.25InitiateCallAttempt.33A.6.1.5.26ManageTriggerData.34A.6.1.5.27MergeCallSegments.35A.6.1.5.28MoveCallSegments.35A.6.1.5.29MoveLeg.36A.6.1.5.30PlayAnnouncement.37A.6.1.5.31PromptAndCollectUserInformation.38A.6.1.5.32PromptAndReceiveMessage.39A.6.1.5.33ReleaseCall.40A.6.1.5.34ReportUTSI.40A.6.1.5.35RequestNotificationChargingEvent.41A.6.1.5.36RequestReportBCSMEvent.42A.6.1.5.37RequestReportUTSI.42A.6.1.5.38ResetTimer.43A.6.1.5.39SendChargingInformation.43A.6.1.5.40SendSTUI.44A.6.1.5.41ServiceFilteringResponse.45A.6.1.5.42SpecializedResourceReport.45A.6.1.5.43SplitLeg.45A.6.1.6Timers.46A.6.1.7Range Constants supported.47A.6.2CUSF.48A.6.2.1Physical entities.48A.6.2.2External interfaces.49A.6.2.3Application contexts supported.49A.6.2.4Operations supported.49A.6.2.5Supported Arguments, Results and Errors.49A.6.2.5.1ActivityTest.49A.6.2.5.2ConnectAssociation.49A.6.2.5.3ContinueAssociation.50A.6.2.5.4EventReportBCUSM.51A.6.2.5.5InitialAssociationDP.51A.6.2.5.6InitiateAssociation.52A.6.2.5.7ReleaseAssociation.52A.6.2.5.8ReportUTSI.52A.6.2.5.9RequestReportBCUSMEvent.53A.6.2.5.10RequestReportUTSI.53A.6.2.5.11ResetTimer.54A.6.2.5.12SendSTUI.54A.6.2.6Timers.55A.6.2.7Range Constants supported.56Bibliography.57History.58SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).NOTE:The present document was originally released on Public Enquiry with the PICS proforma for the SSPonly. The present version also contains the CUSF PICS proforma.The present document is part 2 of a multi-part standard covering the Intelligent Network Application Protocol (INAP)Capability Set 2 (CS2) as described 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 forTesting (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 andoptions have been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called aProtocol Implementation Conformance Statement (PICS).National transposition datesDate of adoption of this EN:30 July 1999Date of latest announcement of this EN (doa):31 October 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 April 2000Date of withdrawal of any conflicting National Standard (dow):30 April 2000SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)61ScopeThis second part of EN 301 140 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 CoreINAP CS2 for the physical element SSP on the interface SSF/SRF-SCF and the CUSF on the interface SCF-CUSF incompliance 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 acopy of the PICS proforma provided in annex A of the present document and is required to provide the informationnecessary to identify both the supplier and the implementation.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, the latest version applies.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]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 testingmethodology and framework - Part 1: General concepts".[3]ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 7: Implementation Conformance Statements".3Definitions, symbols and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply, in addition to those given inEN 301 140-1 [1], ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [3]:Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or systemclaimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take severalforms: 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 systembecomes an ICSProtocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specificationstatic 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)(see ISO/IEC 9646-1 [2])SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)73.2SymbolsFor the purposes of the present document, the following symbols apply:ANDBoolean "and"NOTBoolean "not"ORBoolean "or"3.3AbbreviationsFor the purposes of the present document, the following abbreviations apply:ASEApplication Service ElementICSImplementation Conformance StatementIUTImplementation Under TestMCMajor CapabilitiesMRMessages ReceivedMTMessages TransmittedOSIOpen Systems InterconnectionPParametersPICSProtocol Implementation Conformance StatementRRoleSCSubsidiary CapabilitiesSCSSystem Conformance StatementSUTSystem Under TestTMTimers4ConformanceIf it claims to conform to the present document, the actual Implementation Conformance Statement (ICS) proforma to befilled in by a supplier shall be technically equivalent to the text of the ICS proforma given in annex A, and shall preservethe 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 theguidance for completion given in clause A.1.SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)8Annex A (normative):PICS proforma for EN 301 140-1Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that usersof the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intendedpurposes and may further publish the completed PICS.A.1Guidance for completing the ICS proformaA.1.1Purposes and structureThe purpose of this ICS proforma is to provide a mechanism whereby a supplier of an implementation of therequirements defined in EN 301 140-1 [1] may provide information about the implementation in a standardized manner.The ICS proforma is subdivided into subclauses 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.2Abbreviations and conventionsThe ICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelinespresented in ISO/IEC 9646-7 [3].Item columnThe item column contains a number which identifies the item in the table.Item description columnThe item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitlymeans "is supported by the implementation?".SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)9Status columnThe following notations, defined in ISO/IEC 9646-7 [3], are used for the status column:mmandatory - the capability is required to be supported.ooptional - the capability may be supported or not.n/anot applicable - in the given context, it is impossible to use the capability.xprohibited (excluded) - there is a requirement not to use this capability in the given context.o.iqualified optional - for mutually exclusive or selectable options from a set. "i" is an integer whichidentifies an unique group of related optional items and the logic of their selection which is definedimmediately following the table.ciconditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support ofother optional or conditional items. "i" is an integer identifying an unique conditional statusexpression which is defined immediately following the table.c:ooptional if the hierarchically preceding option is implemented.c:o.iqualified optional if the hierarchically preceding option is implemented.- for mutually exclusive orselectable options from a set. "i" is an integer which identifies an unique group of related optionalitems and the logic of their selection which is defined immediately following the table.c:mmandatory if the hierarchically preceding option is implemented.iirrelevant (out-of-scope) - capability outside the scope of the reference specification. No answer isrequested 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 columnThe reference column makes reference to EN 301 140-1 [1], except where explicitly stated otherwise.Support columnThe support column shall be filled in by the supplier of the implementation. The following common notations, defined inISO/IEC 9646-7 [3], are used for the support column:Y or ysupported by the implementation.N or nnot 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 conditionalstatus).If this ICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able toanswer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enterthe unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in the spacefor 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 NNOTE 2:As stated in ISO/IEC 9646-7 [3], support for a received PDU requires the ability to parse all validparameters 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.SIST EN 301 140-2:2001



ETSIETSI EN 301 140-2 V1.3.3 (1999-08)10Values allowed columnThe values allowed column contains the type, the list, the range, or the length of values allowed. The following notationsare used:-range of values: . example: 5 . 20-list of values:, , ., example: 2, 4, 6, 8, 9example:'1101'B, '1011'B, '1111'Bexample:'0A'H, '34'H, '2F'H-list of named values:(), (), ., ()example:reject(1), accept(2)-length:size ( . )example:size (1 . 8)Values supported columnThe values supported column shall be filled in by the supplier of the implementation. In this column, the values or theranges of values supported by the implementation shall be indicated.References to itemsFor 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 arediscriminated 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 6of annex A.Prerequisite lineA 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 becompleted if the predicate is FALSE.A.1.3Instructions for completing the ICS proformaThe suppl
...