1、Standard ECMA-295December 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) - Call Control in a Separated Calland Bearer Control Environment -Part 2: Protocol ImplementationConformance Statement (PICS)Proforma SpecificationStandard ECMA-295December 1999
3、Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-295.DOC 03-01-00 12,20Broadband Integrated Services DigitalNetwork (B-ISDN) and BroadbandPrivate Integrated Services Network(B-PISN) - Digita
4、l SubscriberSignalling System No. two (DSS2),Broadband Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Call Control in a Separated Calland Bearer Control Environment -Part 2: Protocol ImplementationConformance Statement (PICS)Proforma SpecificationBrief HistoryThis Standard is
5、one of a series of ECMA Standards defining services and signalling protocols applicable to BroadbandPrivate 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 define
6、d by ISO/IEC.This Standard has been produced by ECMA TC32-TG15 in collaboration with ETSI Technical Committee SignallingProtocols and Switching (SPS) under ETSI work item DEN/SPS-05132-2.The Standard is part 2 of a multi-part standard covering the Digital Subscriber Signalling System No. 2 (DSS2), B
7、roadbandInter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) protocol specification for the Broadband IntegratedServices Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) Call Control, as describedbelow:Part 1: “Protocol specification“;Part 2: “Prot
8、ocol Implementation Conformance Statement (PICS) proforma specification“;Part 3: “Test Suite Structure 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
9、ETSI as EN 302 092-3 and EN 302 092-4 respectively.To evaluate conformance of a particular implementation, 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 ProtocolImplemen
10、tation Conformance Statement (PICS).The Standard is based upon the practical experience of ECMA member 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
11、and widely based consensus.This ECMA Standard is technically aligned with EN 302 092-2 published by 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
12、 Conformance Statement (PICS) 14.2 PICS proforma 25 Abbreviations 2Annex A - PICS proforma for ECMA-294 3Annex B - Requirements 13Annex C - Bibliography 15- ii -.1ScopeThis Standard is applicable to the Call Control protocol at the QB, SB, TBand co-incident SB/TBreference pointswithin, between and a
13、t the access to Broadband Private Integrated Services Networks and within, between and at theaccess to public Broadband Integrated Services Digital Networks.This Standard provides the Protocol Implementation Conformance Statement (PICS) proforma for the Call Controlprotocol as specified in ECMA-294
14、in compliance with the relevant requirements and in accordance with the relevantguidance given in ISO/IEC 9646-7.2 ConformanceIf 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 anne
15、x A, and shall preserve the numbering/naming and orderingof the proforma items.A PICS which conforms to this Standard shall 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
16、reference in this text, constitute provisions of thisStandard. 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 applie
17、s. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.ECMA-254 Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol -Generic Functional Protocol (B-QSIG-GF)ECMA-294 Broadband Integrated Servi
18、ces 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) - Call Control in aSeparated Call and Bearer Control Environment - Part 1: Prot
19、ocol SpecificationISO/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
20、 Conformance StatementsETS 300 796-1 Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling SystemNo. two (DSS2) protocol; Generic functional protocol; Core aspects; Part 1: Protocolspecification ITU-T Rec. Q.2932.1 (1996), modified4 DefinitionsFor the purposes of this
21、 Standard, the following definitions apply, in addition to those given in ECMA-294.4.1 Protocol Implementation Conformance Statement (PICS)A statement made by the supplier of an Open Systems Interconnection (OSI) implementation or system, statingwhich capabilities have been implemented for a given O
22、SI protocol (see ISO/IEC 9646-1).- 2 -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/IEC 9646-1).5 AbbreviationsFor the purposes of
23、 this Standard, the following abbreviations apply:CC Call ControlICS Implementation Conformance StatementIUT Implementation Under TestMC Major CapabilitiesMR Messages ReceivedMT Messages TransmittedOSI Open Systems InterconnectionP ParametersPICS Protocol Implementation Conformance StatementRRoleSC
24、Subsidiary CapabilitiesSCS System Conformance StatementSUT System Under TestTM Timers- 3 -Annex A(normative)PICS proforma for ECMA-294A.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 of an implemen
25、tation of therequirements defined in ECMA-294 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 implementation;- ide
26、ntification of the protocol;- global statement of conformance;- Roles;- Major capabilities;- Subsidiary capabilities;- Application protocol data units;- APDU parameters;- Timers.A.1.2 Abbreviations and conventionsThe PICS proforma contained in this annex is comprised of information in tabular form i
27、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
28、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
29、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
30、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-294, except where ex
31、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
32、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
33、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
34、 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 p
35、arameter 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
36、 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 subclau
37、ses of the PICS proforma.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.The
38、 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 name:
39、IUT version:- 5 -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:Additional information:A.2.5 ClientName:Address:Telephone number:Facsimile number:- 6 -E-mail address:Addi
40、tional information:A.2.6 PICS contact personName:Address:Telephone number:Facsimile number:Additional information:A.3 Identification of the protocolThis PICS proforma applies to the following standard:ECMA-294 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private IntegratedSer
41、vices Network (B-PISN) - Digital Subscriber Signalling System No. two (DSS2),Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - CallControl in a Separated Call and Bearer Control Environment - Part 1: Protocol SpecificationA.4 Global statement of conformanceAre all man
42、datory capabilities implemented? (Yes/No) NOTEAnswering “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 p
43、roforma.- 7 -A.5 RolesTable A.1 - RolesItem Role References Condition Status SupportR1 Support of Call Control in an originating CCentity6.1 o.1 Yes No R2 Support of Call Control in a terminating CCentity6.1 o.1 Yes No R3 Support of Call Control in a transit CC entity 6.1 o.1 Yes No o.1 Support of a
44、t least one of these options is required.A.6 Major CapabilitiesTable A.2 - Major CapabilitiesItem Question/feature(Does the implementation . ?)References Condition Status SupportMC1 Support signalling procedures for callestablishment request when acting as apreceding CC entity9.1.1 R1 OR R3 m Yes No
45、 N/A MC2 Support signalling procedures for callestablishment request when acting as asucceeding CC entity9.1.2 R2 OR R3 m Yes No N/A MC3 Support two message sequence for callestablishment9.1, 9.3 MC1 ORMC2m Yes No N/A MC4 Support three message sequence for callestablishment9.1, 9.3 MC1MC2omYes No N/
46、A MC5 Support signalling procedures for callproceeding when acting as a preceding CCentity9.2.1 R1 OR R3 m Yes No N/A MC6 Support signalling procedures for callproceeding when acting as a succeeding CCentity9.2.2 R2R3omYes No N/A MC7 Support signalling procedures for callacceptance when acting as a
47、preceding CCentity9.3.1 R1 OR R3 m Yes No N/A MC8 Support signalling procedures for callacceptance when acting as a succeeding CCentity9.3.2 R2 OR R3 m Yes No N/A MC9 Support signalling procedures for completionof call establishment when acting as apreceding CC entity9.4.1 MC4 m Yes No N/A MC10 Supp
48、ort signalling procedures for completionof call establishment when acting as asucceeding CC entity9.4.2 MC4 m Yes No N/A - 8 -Item Question/feature(Does the implementation . ?)References Condition Status SupportMC11 Support signalling procedures for call statuschange report when acting as an initiat
49、ing CCentity9.5.1 R1 OR R2 o Yes No N/A MC12 Support signalling procedures for call statuschange report when acting as a receiving CCentity9.5.2 R1 OR R2 m Yes No N/A MC13 Support signalling procedures for call clearing 9.7 R1 OR R2OR R3m Yes No N/A MC14 Support bearer co-ordination requirementswhen acting as a CC entity that establishes abearer towards an adjacent CC entityA.1 R1 OR R2OR R3m Yes No N/A MC15 Support bearer co-ordination requirementswhen acting as a CC
