ETSI I-ETS 300 316 ed.1 (1994-12)
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1); Protocol Implementation Conformance Statement (PICS) proforma specification for signalling network layer protocol for circuit-mode basic call control (basic access, network)
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1); Protocol Implementation Conformance Statement (PICS) proforma specification for signalling network layer protocol for circuit-mode basic call control (basic access, network)
DI/SPS-05012
Digitalno omrežje z integriranimi storitvami (ISDN) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - Izjava o skladnosti izvedbe protokola (PICS) - Proformna specifikacija protokola signalizacijske omrežne plasti za krmiljenje vodovnega osnovnega klica (osnovni dostop, omrežje)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1); Protocol Implementation Conformance Statement (PICS) proforma specification for signalling network layer protocol for circuit-mode basic call control (basic access, network)33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:I-ETS 300 316 Edition 1PSIST I-ETS 300 316:1996en01-oktober-1996PSIST I-ETS 300 316:1996SLOVENSKI
STANDARD
PSIST I-ETS 300 316:1996
INTERIMEUROPEANI-ETS 300 316TELECOMMUNICATIONDecember 1994STANDARDSource: ETSI TC-SPSReference: DI/SPS-05012ICS:33.080Key words:ISDN, DSS1, PICS, layer 3, basic, access, networkIntegrated 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 (basic access, network)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: secretariat@etsi.frTel.: +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 316:1996
Page 2I-ETS 300 316: 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 316:1996
Page 3I-ETS 300 316: 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.156.5.3Call states.216.5.4Supported messages.236.5.4.1User to network (received by the network).236.5.4.2Network to user (transmitted by the network).256.5.5Information elements.276.5.5.1User to network (received by the network).276.5.5.2Network to user (transmitted by the network).296.5.6Timers.316.6Additional information for interoperability.336.6.1Information element structure.33Annex A (informative):Instructions for completing the PICS proforma.40A.1PICS proforma partitioning.40A.2Identification of the implementation.40A.3Global statement of conformance.40A.4Explanation of PICS proforma subclauses.40A.4.1Major capabilities.40A.4.2Subsidiary capabilities.40A.4.3Call states.40A.4.4Supported messages, received by the IUT.41A.4.5Supported messages, transmitted by the IUT.41A.4.6Information elements, received by the IUT.41A.4.7Information elements, transmitted by the IUT.41A.4.8Supported timers.41A.4.9Information elements structure.41PSIST I-ETS 300 316:1996
Page 4I-ETS 300 316: December 1994History.42PSIST I-ETS 300 316:1996
Page 5I-ETS 300 316: 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 316:1996
Page 6I-ETS 300 316: December 1994Blank pagePSIST I-ETS 300 316:1996
Page 7I-ETS 300 316: December 19941ScopeThis Interim European Telecommunication Standard (I-ETS) provides the Protocol ImplementationConformance Statement (PICS) proforma for the ISDN network layer protocol (circuit-mode, basic access,network) 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 316:1996
Page 8I-ETS 300 316: 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 316:1996
Page 9I-ETS 300 316: 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 316:1996
Page 10I-ETS 300 316: 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 316:1996
Page 11I-ETS 300 316: 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 316:1996
Page 12I-ETS 300 316: 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 call establishment at the originatinginterface (outgoing calls from the user's point ofview)?M5.1[ ]Yes [ ]NoMC 1.1support procedures of en-bloc receiving(sending from the user's point of view)?M5.1.1, 5.1.5.1,5.1.8[ ]Yes [ ]NoMC 1.2support procedures of overlap receiving(sending from the user's point of view)?M5.1.3, 5.1.5.2,5.1.8[ ]Yes [ ]NoMC 1.3interpret notification of interworking receivedfrom the calling user?M5.1.6[ ]Yes [ ]NoMC 1.4support transit network selection?O5.1.10, annex C[ ]Yes [ ]NoMC 1.5provide in-band information and in-bandtones/announcements?O5.1.2, 5.1.3,5.1.7, 5.3.4.1,5.4[ ]Yes [ ]NoMC 1.6send notification of interworking from the calleduser or network to the calling user?M5.1.6[ ]Yes [ ]NoMC 2support call establishment at the destinationinterface (incoming calls from the user's point ofview)?M5.2[ ]Yes [ ]NoMC 2.1support procedures of en-bloc sending(receiving from the user's point of view)?O.15.2.1, 5.2.5.1[ ]Yes [ ]NoMC 2.2support procedures of overlap sending(receiving from the user's point of view)?O.15.2.1, 5.2.4[ ]Yes [ ]NoMC 2.3send notification of interworking received fromthe calling user or network?M5.2.6[ ]Yes [ ]NoMC 2.4support delivery of the SETUP message to thecalled user on the point-to-point data link?O.25.2.1, 5.2.3.1[ ]Yes [ ]NoMC 2.5support delivery of the SETUP message to thecalled user on the broadcast data link?O.25.2.1, 5.2.3.2[ ]Yes [ ]No(continued)PSIST I-ETS 300 316:1996
Page 13I-ETS 300 316: December 1994Table 1 (continued): Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 2.6send notification of interworking at thedestination interface to the calling user?M5.2.6[ ]Yes [ ]NoMC 3accept user-initiated call clearing?M5.3.3[ ]Yes [ ]NoMC 4.1support call clearing initiated by the network withtones/announcements provided?MC 1.5NOT MC 1.5MN/A5.3.4.1[ ]Yes [ ]NoMC 4.2support call clearing initiated by the network withtones/announcements not provided?M5.3.4.2[ ]Yes [ ]NoMC 5support the restart procedure?see note15.5[ ]Yes [ ]No[ ]Yes [ ]NoMC 6support call rearrangement procedures?O5.6[ ]Yes [ ]NoMC 7.1support response to Status enquiry message?M5.8.10[ ]Yes [ ]NoMC 7.2support sending of Status enquiry message?O5.8.10[ ]Yes [ ]NoMC 8support symmetric call operation?N/A 3annex DMC 9support network specific facility selection?Oannex E[ ]Yes [ ]NoMC 10support Low layer compatibility informationelement negotiation?N/A 2annex M(continued)PSIST I-ETS 300 316:1996
Page 14I-ETS 300 316: December 1994Table 1 (concluded): Major capabilitiesItemMajor capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMC 11.1support user-to-user signalling during the set-upand clearing phases of a call (service 1)?N/A 3(note 2)7.1.1, 7.1.3MC 11.2support user-to-user signalling during callestablishment (service 2)?N/A 3(note 2)7.1.1, 7.1.4MC 11.3support user-to-user signalling in the Activestate of a call (service 3)?N/A 3(note 2)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 2annex FMC 15support procedures for bearer service change?N/A 3annex OO.1MC 2.1 and MC 2.2Support of at least one of these options is required.O.2MC 2.4 and MC 2.5Support of at least one of these options is required.NOTE 1: If point-to-point configuration then Status = Mandatory, otherwise Status = OptionalNOTE 2: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 316:1996
Page 15I-ETS 300 316: December 19946.5.2Subsidiary capabilitiesTable 2: Subsidiary capabilitiesItemSubsidiary capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportCall proceduresSC 1include the Sending complete informationelement in the SETUP message to the calleduser?O5.2.1, 5.2.4[ ]Yes [ ]NoSC 2support the indication "no B-channel available"in the SETUP message to the called user?O5.2.3.1[ ]Yes [ ]NoSC 3use a 1 octet call reference value in an outgoingSETUP message?M4.3[ ]Yes [ ]NoSC 4.1accept only one SETUP ACKNOWLEDGEmessage from the called user on point-to-pointdata link?MC 2.2NOT MC 2.2MN/A5.2.4[ ]Yes [ ]NoSC 4.2accept up to 8 SETUP ACKNOWLEDGEmessages from the called user on broadcastdata link?MC 2.2 ANDMC 2.5NOT MC 2.2 ORNOT MC 2.5ON/A5.2.4[ ]Yes [ ]NoSC 5clear subsequent responding users after the firstSETUP ACKNOWLEDGE message onbroadcast data link?MC 2.5NOT MC 2.5ON/A5.2.4[ ]Yes [ ]NoSC 6clear non-selected users on broadcast data link?MC 2.5NOT MC 2.5MN/A5.2.9[ ]Yes [ ]NoSC 7support priority to incoming call (form the user'spoint of view) on call collision?M5.7[ ]Yes [ ]NoSC 8check calling side compatibility?M5.1.5, annex B.2[ ]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 [ ]NoCall reference errorsSC 11ignore a received message with Call referenceoctet 1 bits 5 to 8 not equal to 0?M5.8.3.1[ ]Yes [ ]No(continued)PSIST I-ETS 300 316:1996
Page 16I-ETS 300 316: December 1994Table 2 (continued): Subsidiary capabilitiesItemSubsidiary capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportSC 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?O[ ]Yes [ ]NoSC 12.3.2less than 2?N/A 2SC 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)[ ]Yes [ ]NoSC 17ignore a SETUP message containing a Callreference value relating to an existing call?M5.8.3.2 (e)[ ]Yes [ ]NoSC 18transmit a STATUS message on receiving anymessage other than RESTART, RESTARTACKNOWLEDGE, STATUS, with global Callreference value?M5.8.3.2 (f)[ ]Yes [ ]No(continued)PSIST I-ETS 300 316:1996
Page 17I-ETS 300 316: December 1994Table 2 (continued): Subsidiary capabilitiesItemSubsidiary capabilityDoes the implementation.Conditions forstatusStatusReferenceSupportMessage type, message sequence errorsSC 19transmit a STATUS message on receipt of anunexpected message other than RELEASE,RELEASE COMPLETE or of an unrecognizablemessage in any other state than the Null state?O.15.8.4[ ]Yes [ ]NoSC 20initiate status enquiry procedures on receipt ofan unexpected message other than RELEASE,RELEASE COMPLETE or of an unrecognizablemessage in any other state than the Null state?O.15.8.4, 5.8.10[ ]Yes [ ]NoSC 21clear call on receipt of an unexpectedRELEASE, RELEASE COMPLETE message?M5.8.4[ ]Yes [ ]NoGeneral information element errorsSC 22support general information element errorprocedures in codesets o
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.