ECMA297-1999 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) - Digital Subscriber Signalling System No Two (DSS2) .pdf

1、Standard ECMA-297December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chBroadband Integrated Services DigitalNetwork (B-ISDN) and BroadbandPrivate Integrated Services Network(B-PISN) - Digita

2、l SubscriberSignalling System No. two (DSS2),Broadband Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Prenegotiation - Part 2:Protocol Implementation ConformanceStatement (PICS) ProformaSpecificationStandard ECMA-297December 1999Standardizing Information and Communication Syst

3、emsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-297.DOC 03-01-00 12,19Broadband Integrated Services DigitalNetwork (B-ISDN) and BroadbandPrivate Integrated Services Network(B-PISN) - Digital SubscriberSignalling System No. two (DSS2),Bro

4、adband Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Prenegotiation - Part 2:Protocol Implementation ConformanceStatement (PICS) ProformaSpecificationBrief HistoryThis Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Broad

5、bandPrivate Integrated Services Networks (B-PISNs). The series uses B-ISDN concepts as developed by ITU-T and conforms tothe framework of International Standards for Open Systems Interconnection as defined by ISO/IEC.This Standard has been produced by ECMA TC32-TG15 in collaboration with ETSI Techni

6、cal Committee SignallingProtocols and Switching (SPS) under ETSI work item DEN/SPS-05131-2.The Standard is part 2 of a multi-part standard covering the Digital Subscriber Signalling System No. 2 (DSS2), BroadbandInter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) protocol specifica

7、tion for Broadband IntegratedServices Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) Prenegotiation, asdescribed below:Part 1: “Protocol specification“;Part 2: “Protocol Implementation Conformance Statement (PICS) proforma specification“;Part 3: “Test Suite Struc

8、ture and Test Purposes (TSSPart 4: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proformaspecification“.Part 3 and part 4 will only be produced by ETSI as EN 302 091-3 and EN 302 091-4 respectively.To evaluate conformance of a particular impleme

9、ntation, it is necessary to have a statement of which capabilities and optionshave been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called a ProtocolImplementation Conformance Statement (PICS).The Standard is based upon the practical experience of ECMA me

10、mber companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardizationbodies. It represents a pragmatic and widely based consensus.This ECMA Standard is technically aligned with EN 302 091-2 published b

11、y ETSI in November 1999.This Standard has been adopted by the ECMA General Assembly of December 1999.- i -Table of contents1Scope 12 Conformance 13 References 14 Definitions 14.1 Protocol Implementation Conformance Statement (PICS) 14.2 PICS proforma 15 Abbreviations 2Annex A - PICS proforma for ECM

12、A-296 3Annex B - Bibliography 9- ii -.1ScopeThis Standard is applicable to the Prenegotiation protocol at the QB, SB, TBand co-incident SB/TBreference pointswithin, between and at the access to Broadband Private Integrated Services Networks and within, between and at theaccess to public Broadband In

13、tegrated Services Digital Networks.This Standard provides the Protocol Implementation Conformance Statement (PICS) proforma for the Prenegotiationprotocol as specified in ECMA-296 in compliance with the relevant requirements and in accordance with the relevantguidance given in ISO/IEC 9646-7.2 Confo

14、rmanceIf it claims to conform to this Standard, the actual PICS proforma to be filled in by a supplier shall be technicallyequivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and orderingof the proforma items.A PICS which conforms to this Standard sh

15、all be a conforming PICS proforma completed in accordance with theguidance for completion given in clause A.1.3 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of thisStandard. References are either specific (identified by date of pub

16、lication, 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 samenum

17、ber.ECMA-296 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private IntegratedServices Network (B-PISN) - Digital Subscriber Signalling System No. two (DSS2), BroadbandInter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - Prenegotiation -Part 1: Protocol Speci

18、ficationISO/IEC 9646-1 Information technology - Open Systems Interconnection - Conformance testing methodology andframework - Part 1: General conceptsISO/IEC 9646-7 Information technology - Open Systems Interconnection - Conformance testing methodology andframework - Part 7: Implementation Conforman

19、ce Statements4 DefinitionsFor the purposes of this Standard, the following definitions apply, in addition to those given in ECMA-296.4.1 Protocol Implementation Conformance Statement (PICS)A statement made by the supplier of an Open Systems Interconnection (OSI) implementation or system, statingwhic

20、h capabilities have been implemented for a given OSI protocol (see ISO/IEC 9646-1).4.2 PICS proformaA document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier,which, when completed for an OSI implementation or system becomes the PICS (see ISO/I

21、EC 9646-1).- 2 -5 AbbreviationsFor the purposes of this Standard, the following abbreviations apply:ICS Implementation Conformance StatementIUT Implementation Under TestMC Major CapabilitiesMR Messages ReceivedMT Messages TransmittedOSI Open Systems InterconnectionPICS Protocol Implementation Confor

22、mance StatementPRN PrenegotiationRRoleSCS System Conformance StatementSUT System Under TestTM Timers- 3 -Annex A(normative)PICS proforma for ECMA-296A.1 Guidance for completing the PICS proformaA.1.1 Purposes and structureThe purpose of this PICS proforma is to provide a mechanism whereby a supplier

23、 of an implementation of therequirements defined in ECMA-296 may provide information about the implementation in a standardized manner.The PICS proforma is subdivided into subclauses for the following categories of information:- guidance for completing the PICS proforma;- identification of the imple

24、mentation;- identification of the protocol;- global statement of conformance;- Roles (Rs);- Major Capabilities (MC);- Application protocol data units;- Timers (T);- Interworking.A.1.2 Abbreviations and conventionsThe PICS proforma contained in this annex is comprised of information in tabular form i

25、n accordance with theguidelines presented in ISO/IEC 9646-7.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 suppo

26、rted by the implementation?“.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 us

27、e the capability.o.i qualified 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.c.i conditional - the requirement on the cap

28、ability (“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.- 4 -Reference column:The reference column makes reference to ECMA-296, except where ex

29、plicitly 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 o

30、r - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditionalstatus).If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to beable to answer that a capability is supported for one profile and not s

31、upported for another. In that case, the suppliershall enter the unique reference to a conditional expression, preceded by “?“ (e.g. ?3). This expression shall begiven in the space for comments provided at the bottom of the table. It uses predicates defined in the SCS, each ofwhich refers to a single

32、 profile and which takes the value TRUE if and only if that profile is to be used.EXAMPLE: ?3: IF prof1 THEN Y ELSE NNOTEAs stated in ISO/IEC 9646-7, support for a received PDU requires the ability to parse all valid parameters of thatPDU. Supporting a PDU while having no ability to parse a valid pa

33、rameter is non-conformant. Support for aparameter on a PDU means that the semantics of that parameter are supported.A.1.3 Instructions for completing the PICS proformaThe supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular,an explicit answer

34、shall be entered, in each of the support column boxes provided, using the notation described insubclause 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 subclaus

35、es of the PICS proforma.- 5 -A.2 Identification of the implementationIdentification 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 configurationoptions

36、.The product supplier information and client information should both be filled in if they are different.A person who can answer queries regarding information supplied in the ICS should be named as the contact person.A.2.1 Date of the statementA.2.2 Implementation Under Test (IUT) identificationIUT n

37、ame:IUT version:A.2.3 System Under Test (SUT) identificationSUT name:Hardware configuration:Operating system:A.2.4 Product supplierName:Address:Telephone number:Facsimile number:E-mail address:- 6 -Additional information:A.2.5 ClientName:Address:Telephone number:Facsimile number:E-mail address:Addit

38、ional information:A.2.6 PICS contact personName:Address:Telephone number:Facsimile number:Additional information:- 7 -A.3 Identification of the protocolThis PICS proforma applies to the following standard:ECMA-296 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrate

39、dServices Network (B-PISN) - Digital Subscriber Signalling System No. two (DSS2),Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) -Prenegotiation - Part 1: Protocol SpecificationA.4 Global statement of conformanceAre all mandatory capabilities implemented? (Yes/No) NOT

40、EAnswering “No“ to this question indicates non-conformance to the protocol specification. Non-supported mandatorycapabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, onpages attached to the PICS proforma.A.5 RolesTable A.1 - RolesItem Role R

41、eferences Condition Status SupportR1 Support of prenegotiation in terminalequipment(originating or terminating CC entity)5.1 o Yes No R2 Support of prenegotiation in a network node(transit CC entity)5.1 o Yes No A.6 Major CapabilitiesTable A.2 - Major CapabilitiesItem Question/feature(Does the imple

42、mentation . ?)References Condition Status SupportMC1 Support signalling procedures for invocationof prenegotiation by an originating CC entitytogether with call establishment9.2.1 R1 o.1 Yes No N/A MC2 Support signalling procedures for invocationof prenegotiation by a terminating CC entitytogether w

43、ith the first end-to-end response tocall establishment9.2.1 R1 o.1 Yes No N/A MC3 Support signalling procedures for invocationof prenegotiation by an originating CC entityafter the first end-to-end response to callestablishment9.2.1 R1 o.1 Yes No N/A MC4 Support signalling procedures for invocationo

44、f prenegotiation by a terminating CC entityafter the first end-to-end response to callestablishment9.2.1 R1 o.1 Yes No N/A MC5 Support signalling procedures for invocationof prenegotiation independently, after callestablishment9.2.1 R1 o.1 Yes No N/A MC6 Support signalling procedures forprenegotiati

45、on in a transit CC entity9.3 R2 m Yes N/A o.1 Support of at least one of these options is required.- 8 -A.7 Application protocol data unitsTable A.3 - APDUs transmittedItem Question/feature(Does the implementation support . ?)References Condition Status SupportMT1 Sending of preNegotiate invoke 9.2.

46、1 R1 OR R2 m Yes MT2 Sending of prenegotiationAlert invoke 9.2.2 R1R2 omYes No MT3 Sending of preNegotiate return result/error 9.2.2 R1 OR R2 m Yes Table A.4 - APDUs receivedItem Question/feature(Does the implementation support . ?)References Condition Status SupportMR1 Receipt of preNegotiate retur

47、n result/error 9.2.3 R1 OR R2 m Yes MR2 Receipt of a reject ADPU correlated to apreNegotiate invoke9.2.1 MT1 m Yes N/A MR3 Receipt of preNegotiate invoke 9.2.2 R1 OR R2 omYes MR4 Receipt of prenegotiationAlert invoke 9.2.3 R1 OR R2 m Yes MR5 Receipt of a reject ADPU correlated to aprenegotiationAler

48、t invoke9.2.2 MT2 m Yes N/A A.8 TimersTable A.5 - TimersItem Question/feature(Does the implementation . ?)References Condition Status SupportTM1 Support timer T1 9.2.1.1 MT1 o Yes No N/A TM2 Support timer T2 9.2.3 MR4 o Yes No N/A A.9 InterworkingTable A.6 - InterworkingItem Question/feature(Does th

49、e implementation . ?)References Condition Status SupportIW1 Support interworking procedures in case ofincoming calls from other networks notsupporting prenegotiation11.1 MC6 o Yes No N/A IW2 Support interworking procedures in case ofoutgoing calls to other networks notsupporting prenegotiation11.2 MC6 o Yes No N/A - 9 -Annex B(informative)BibliographyETS 300 406 Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications;Standardization met