|
STANDARD
PSIST I-ETS 300 315:1996
INTERIMEUROPEANI-ETS 300 315TELECOMMUNICATIONDecember 1994STANDARDSource: ETSI TC-SPSReference: DI/SPS-05016ICS:33.080Key words:ISDN, DSS1, PICS, layer 3, primary, rate, access, userIntegrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1)Protocol Implementation Conformance Statement (PICS)proforma specification for signalling network layer protocolfor circuit-mode basic call control (primary rate access, user)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [email protected].: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1994. All rights reserved.PSIST I-ETS 300 315:1996
Page 2I-ETS 300 315: December 1994Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.PSIST I-ETS 300 315:1996
Page 3I-ETS 300 315: December 1994ContentsForeword.5Introduction.51Scope.72Normative references.73Definitions.74Abbreviations.85Conformance.86PICS proforma.96.1Identification of the implementation.96.1.1Implementation Under Test (IUT) identification.96.1.2System Under Test (SUT) identification.96.1.3Product supplier.96.1.4Client.106.1.5PICS contact person.106.2PICS/System Conformance Statement (SCS).116.3Identification of the protocol.116.4Global statement of conformance.116.5Information for conformance testing.126.5.1Major capabilities.126.5.2Subsidiary capabilities.166.5.3Call states.226.5.4Supported messages.246.5.4.1Network to user (received by the user).246.5.4.2User to network (transmitted by the user).266.5.5Information elements.286.5.5.1Network to user (received by the user).286.5.5.2User to network (transmitted by the user).306.5.6Timers.326.6Additional information for interoperability.346.6.1Information element structure.34Annex A (informative):Instructions for completing the PICS proforma.47A.1PICS proforma partitioning.47A.2Identification of the implementation.47A.3Global statement of conformance.47A.4Explanation of PICS proforma subclauses.47A.4.1Major capabilities.47A.4.2Subsidiary capabilities.47A.4.3Call states.47A.4.4Supported messages, received by the IUT.48A.4.5Supported messages, transmitted by the IUT.48A.4.6Information elements, received by the IUT.48PSIST I-ETS 300 315:1996
Page 4I-ETS 300 315: December 1994A.4.7Information elements, transmitted by the IUT.48A.4.8Supported timers.48A.4.9Information elements structure.48History.49PSIST I-ETS 300 315:1996
Page 5I-ETS 300 315: December 1994ForewordThis Interim European Telecommunication Standard (I-ETS) has been produced by the SignallingProtocols and Switching (SPS) Technical Committee of the European Telecommunications StandardsInstitute (ETSI).An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution aheadof a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETSis limited to three years after which it can be converted into an ETS, have it's life extended for a furthertwo years, be replaced by a new version or be withdrawn.This I-ETS forms part of a set of I-ETSs completing the documentation of ETS 300 102-1 (ISDN signallingnetwork layer protocol) as specified in ISO/IEC 9646-1 (e.g. conformance testing) as follows:I-ETS 300 314:"Protocol Implementation Conformance Statement (PICS) proformaspecification (basic access, user)";I-ETS 300 315:"PICS proforma specification (primary rate access, user)";I-ETS 300 316:"PICS proforma specification (basic access, network)";I-ETS 300 317:"PICS proforma specification (primary rate access, network)";I-ETS 300 318:"Protocol Implementation eXtra Information for Testing (PIXIT) proformaspecification (basic access, user)";I-ETS 300 319:"PIXIT proforma specification (primary rate access, user)";I-ETS 300 322:"Abstract test suite (user)".Proposed announcement dateDate of latest announcement of this I-ETS (doa):31 March 1995IntroductionTo evaluate conformance of a particular implementation, it is necessary to have a statement of whichcapabilities and options have been implemented for a given Open Systems Interconnection (OSI)protocol. Such a statement is called a Protocol Implementation Conformance Statement (PICS).PSIST I-ETS 300 315:1996
Page 6I-ETS 300 315: December 1994Blank pagePSIST I-ETS 300 315:1996
Page 7I-ETS 300 315: December 19941ScopeThis Interim European Telecommunication Standard (I-ETS) provides the Protocol ImplementationConformance Statement (PICS) proforma for the ISDN network layer protocol (circuit-mode, primary rateaccess, user) as specified in ETS 300 102-1 [1] in compliance with the relevant requirements and inaccordance with the relevant guidance given in ISO/IEC 9646-2 [3].Both the packet interworking (clause 6 of ETS 300 102-1 [1]) and the User-to-User Signalling (UUS)procedures (clause 7 of ETS 300 102-1 [1]) are excluded from the present PICS proforma.2Normative referencesThis I-ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this I-ETS only when incorporated in it by amendment or revision. For undated references thelatest edition of the publication referred to applies.[1]ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control".[2]ISO/IEC 9646-1 (1990): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 1:General concepts" (see also CCITT Recommendation X.290 (1991)).[3]ISO/IEC 9646-2 (1990): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 2:Abstract test suite specification" (see also CCITT Recommendation X.291(1991)).3DefinitionsFor the purposes of this I-ETS, the following definitions apply:Network: the equipment existing at the network side of the user-network interface.Protocol Implementation Conformance Statement (PICS): a statement made by the supplier of anOpen Systems Interconnection (OSI) implementation or system, stating which capabilities have beenimplemented for a given OSI protocol (see ISO/IEC 9646-1 [2]).PICS proforma: a document, in the form of a questionnaire, which when completed for an OSIimplementation or system becomes the PICS (see ISO/IEC 9646-1 [2]).Static conformance review: a review of the extent to which the static conformance requirements are metby the Implementation Under Test (IUT), accomplished by comparing the PICS with the staticconformance requirements expressed in the relevant standard(s) (see ISO/IEC 9646-1 [2]).User: the equipment existing at the user side of the user-network interface.PSIST I-ETS 300 315:1996
Page 8I-ETS 300 315: December 19944AbbreviationsFor the purposes of this I-ETS, the following abbreviations apply:AbsentNot relevant to this proformaANDBoolean "and"CSprefix for index numbers for the Call States groupIERprefix for index numbers for the Received Information Elements groupIETprefix for index numbers for the Transmitted Information Elements groupISprefix for index numbers for the Information element Structure groupISDNIntegrated Services Digital NetworkIUTImplementation Under TestMMandatory requirements (these are to be observed in all cases)MCprefix for index numbers for the Major Capabilities groupMRprefix for index numbers for the Received Messages groupMTprefix for index numbers for the Transmitted Messages groupN/ANot supported, not applicable or the conditions for status are not metN/A 1Not Applicable in this direction of transmissionN/A 2Not Applicable at the implementation of this interfaceN/A 3Not Applicable to ETSI networksNOTBoolean "not"OOption (may be selected to suit the implementation, provided that anyrequirements applicable to the option are observed)O.nOptions, but support required for either at least one or only one of the options inthe group labelled with the same numeral "n"ORBoolean "or"OSIOpen Systems InterconnectionPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingSCprefix for index numbers for Subsidiary Capabilities groupSCSSystem Conformance StatementSUTSystem Under TestTMprefix for index numbers for the Timers groupUUSUser-to-User Signalling[ ] Yes [ ] NoTick "Yes" if item is supported, tick "No" if item is not supported5ConformanceThe supplier of a protocol implementation which is claimed to conform to ETS 300 102-1 [1] is required tocomplete a copy of the PICS proforma provided in this I-ETS and is required to provide the informationnecessary to identify both the supplier and the implementation.PSIST I-ETS 300 315:1996
Page 9I-ETS 300 315: December 19946PICS proformaNotwithstanding the provisions of the copyright clause related to the text of this I-ETS, ETSI grants thatusers of this I-ETS may freely reproduce the PICS proforma in this clause so that it can be used for itsintended purposes and may further publish the completed PICS.6.1Identification of the implementation6.1.1Implementation Under Test (IUT) identificationIUT name:.IUT version:.6.1.2System Under Test (SUT) identificationSUT name:.Hardware configuration:.Operating system:.6.1.3Product supplierName:.Address:.Telephone number:.PSIST I-ETS 300 315:1996
Page 10I-ETS 300 315: December 1994Facsimile number:.Additional information:.6.1.4ClientName:.Address:.Telephone number:.Facsimile number:.Additional information:.6.1.5PICS contact personName:.Telephone number:.Facsimile number:.PSIST I-ETS 300 315:1996
Page 11I-ETS 300 315: December 1994Additional information:.6.2PICS/System Conformance Statement (SCS)Provide the relationship of the PICS with the SCS for the system:.6.3Identification of the protocolThis PICS proforma applies to the following standard:ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3;Specifications for basic call control".6.4Global statement of conformanceThe implementation described in this PICS meets all the mandatory requirements of the referencedstandard.[
] Yes[
] NoNOTE:Answering "No" to this question indicates non-conformance to the protocolspecification. Non-supported mandatory capabilities are to be identified in the PICS,with an explanation of why the implementation is non-conforming.PSIST I-ETS 300 315:1996
Page 12I-ETS 300 315: December 19946.5Information for conformance testing6.5.1Major capabilitiesUnless otherwise indicated all references in the tables are to subclauses in ETS 300 102-1 [1].Table 1: Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 1support outgoing calls?O.15.1[ ]Yes [ ]NoMC 1.1support procedures of en-bloc sending?MC 1NOT MC 1O.2N/A5.1.1, 5.1.5.1[ ]Yes [ ]NoMC 1.2support procedures of overlap sending?MC 1NOT MC 1O.2N/A5.1.3, 5.1.5.2[ ]Yes [ ]NoMC 1.3send notification of interworking in the Progressindicator information element of an outgoingSETUP message if the implementation is thepoint at which a call enters an ISDNenvironment from a non-ISDN environment?MC 1NOT MC 1MN/A5.1.6[ ]Yes [ ]NoMC 1.4support transit network selection?MC 1NOT MC 1ON/A5.1.10, annex C[ ]Yes [ ]NoMC 1.5attach to the B-channel and stop appropriatetimers upon receipt of an appropriate call controland progress indicator?MC 1NOT MC 1ON/A5.1.2, 5.1.3,5.1.7, 5.4[ ]Yes [ ]NoMC 1.6interpret notification of interworking sent fromthe network on outgoing calls?MC 1NOT MC 1ON/A5.1.6[ ]Yes [ ]NoMC 1.7generate local tones and local alertingindications?MC 1NOT MC 1ON/A5.1.2, 5.1.7[ ]Yes [ ]NoMC 2support incoming calls?O.15.2[ ]Yes [ ]NoMC 2.1support procedures of en-bloc receiving?MC 2NOT MC 2MN/A5.2.1, 5.2.5.1[ ]Yes [ ]NoMC 2.2support procedures of overlap receiving?MC 2NOT MC 2ON/A5.2.1, 5.2.4[ ]Yes [ ]NoMC 2.3send notification of interworking on incomingcalls if the implementation is the point at which acall leaves an ISDN environment for a non-ISDNenvironment?MC 2NOT MC 2MN/A5.2.6[ ]Yes [ ]No(continued)PSIST I-ETS 300 315:1996
Page 13I-ETS 300 315: December 1994Table 1 (continued): Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 2.4accept the SETUP message on the point-to-point data link?MC 2NOT MC 2MN/A5.2.1, 5.2.3.1[ ]Yes [ ]NoMC 2.5accept the SETUP message on the broadcastdata link?N/A 25.2.1, 5.2.3.2MC 2.6send notification of interworking at thedestination interface to the calling user if theimplementation is the point at which a callleaves an ISDN environment for a non-ISDNenvironment?MC 2NOT MC 2MN/A5.2.6[ ]Yes [ ]NoMC 2.7support compatibility checking if a coincident Sand T reference point exists?MC 2NOT MC 2MN/A5.2.2, annex B[ ]Yes [ ]NoMC 3support user-initiated call clearing?M5.3.3[ ]Yes [ ]NoMC 4.1wait for the network to send a RELEASEmessage on the receipt of a DISCONNECTmessage with Progress indicator informationelement #8?O.35.3.4.1[ ]Yes [ ]NoMC 4.2respond with a RELEASE message on thereceipt of a DISCONNECT message withProgress indicator information element #8?O.35.3.4.1[ ]Yes [ ]NoMC 4.3support a manual configuration option betweenMC 4.1 and MC 4.2?MC 4.1 ANDMC 4.2NOT MC 4.1 ORNOT MC 4.2MN/A5.3.4.1[ ]Yes [ ]NoMC 4.4support call clearing initiated by the network withtones and announcements not provided?M5.3.4.2[ ]Yes [ ]NoMC 5support restart procedure?M5.5[ ]Yes [ ]NoMC 6support call rearrangement procedures?N/A 35.6(continued)PSIST I-ETS 300 315:1996
Page 14I-ETS 300 315: December 1994Table 1 (continued): Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 7.1support response to STATUS ENQUIRYmessage?M5.8.10[ ]Yes [ ]NoMC 7.2support sending of STATUS ENQUIRYmessage?O5.8.10[ ]Yes [ ]NoMC 8support symmetric call operation?N/A 3annex DMC 9support network specific facility selection?MC 1NOT MC 1ON/Aannex E[ ]Yes [ ]NoMC 10support Low layer compatibility informationelement negotiation?Oannex M[ ]Yes [ ]NoMC 11.1support user-to-user signalling during the set-upand clearing phases of a call (service 1)?N/A 3(note)7.1.1, 7.1.3MC 11.2support user-to-user signalling during callestablishment (service 2)?N/A 3(note)7.1.1, 7.1.4MC 11.3support user-to-user signalling in the Activestate of a call (service 3)?N/A 3(note)7.1.1, 7.1.5MC 12support procedures for establishment of bearerconnection prior to call acceptance?Oannex N[ ]Yes [ ]NoMC 13support message segmentation procedures?Oannex K[ ]Yes [ ]NoMC 14D-channel back-up procedure?N/A 3annex F(continued)PSIST I-ETS 300 315:1996
Page 15I-ETS 300 315: December 1994Table 1 (concluded): Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 15support procedures for bearer service change?N/A 3annex OO.1MC 1 and MC 2Support of at least one of these options is required.O.2MC 1.1 and MC 1.2Support of at least one of these options is required.O.3MC 4.1 and MC 4.2Support of at least one of these options is required.NOTE :These capabilities appear in the PICS proforma for UUS supplementary service. The designation of not applicable toETSI networks is therefore only in the context of basic call control.Comments:PSIST I-ETS 300 315:1996
Page 16I-ETS 300 315: December 19946.5.2Subsidiary capabilitiesTable 2: Subsidiary capabilitiesItemSubsidiary capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportCall proceduresSC 1.1send the called party address information, ifpresent, in the Called party number informationelement?M5.1.1, 5.1.3[ ]Yes [ ]NoSC 1.2send the called party address information, ifpresent, in the Keypad facility informationelement?N/A 35.1.1, 5.1.3SC 2use a 2 octets call reference value in anoutgoing SETUP message?M4.3[ ]Yes [ ]NoSC 3support the sending of CONNECTACKNOWLEDGE message during outgoing callestablishment?MC 1NOT MC 1ON/A5.1.8[ ]Yes [ ]NoSC 4monitor the status of B-channels (in use or not inuse)?MC 1NOT MC 1ON/A5.1.1[ ]Yes [ ]NoSC 5.1if a coincident S and T reference point exists,check the bearer service provided?MC 2.7NOT MC 2.7MN/A5.2.2,annex B.3.2[ ]Yes [ ]NoSC 5.2if a T reference point exists, check the bearerservice provided?MC 2.7NOT MC 2.7ON/A5.2.2,annex B.3.2[ ]Yes [ ]NoSC 6check the Low layer compatibility informationelement if available?MC 2.7NOT MC 2.7ON/A5.2.2,annex B.3.3[ ]Yes [ ]NoSC 7use the Bearer capability information element forLow layer compatibility information elementchecking if the SETUP message received doesnot include the Low layer compatibilityinformation element?MC 2.7NOT MC 2.7ON/Aannex B.3.3[ ]Yes [ ]NoSC 8check the High layer compatibility informationelement?MC 2.7NOT MC 2.7ON/A5.2.2,annex B.3.3[ ]Yes [ ]NoGeneral errorsSC 9ignore a received message with protocoldiscriminator error?M5.8.1[ ]Yes [ ]NoSC 10ignore a received message too short to containa complete information element?M5.8.2[ ]Yes [ ]No(continued)PSIST I-ETS 300 315:1996
Page 17I-ETS 300 315: December 1994Table 2 (continued): Subsidiary capabilitiesItemSubsidiary capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportCall reference errorsSC 11ignore a received message with Call referenceoctet 1 bits 5 to 8 not equal to 0?M5.8.3.1[ ]Yes [ ]NoSC 12.1ignore a received message if the Call referenceinformation element octet 1, bits 1 through 4indicate a length greater than the maximumlength supported?M5.8.3.1[ ]Yes [ ]NoSC 12.2ignore a received message related to basic callcontaining the dummy Call reference value?M5.8.3.1[ ]Yes [ ]NoSC 12.3ignore a Call reference information element of alength other than those supported? Specifically:5.8.3.1SC 12.3.1greater than 1?N/A 2SC 12.3.2less than 2?O[ ]Yes [ ]NoSC 12.3.3greater than 2?O[ ]Yes [ ]NoSC 13clear call on receiving any message other thanSETUP, RELEASE, RELEASE COMPLETE,STATUS, RESUME, with unrecognizable Callreference value?M5.8.3.2 (a)[ ]Yes [ ]NoSC 14transmit a RELEASE COMPLETE message onreceiving a RELEASE message withunrecognizable Call reference value?M5.8.3.2 (b)[ ]Yes [ ]NoSC 15take no action on receiving a RELEASECOMPLETE message with unrecognizable Callreference value?M5.8.3.2 (c)[ ]Yes [ ]NoSC 16ignore a received SETUP or RESUME messagewith unrecognizable Call reference value or witha Call reference flag incorrectly set to "1"?M5.8.3.2 (d)[
...