Conceptio › Archive › ECMA International

ECMA Internationalopen access

ECMA-295 — B-ISDN and B-PISN - Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - Call control in a separated call and bearer control environment - Part 2:

ECMA International · ECMA International

ECMA International · Standards · License: Open Access

conformance control digital ecma ecmainternational environment exchange implementation

ecma, standard, ecma international, specification, ecma-295, ecma 295, 295, b-isdn, and, b-pisn, digital, subscriber, signalling, system, no., two, dss2, broadband, inter-exchange, b-qsig, ss7, call, control, separated, bearer, environment, part, protocol, implementation, conformance, statement, pics, proforma

Standard ECMA-295 D e c e mb e r 1 9 9 9

Standardizing Information and Communication Systems

Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) - Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - Call Control in a Separated Call and Bearer Control Environment Part 2: Protocol Implementation Conformance Statement (PICS) Proforma Specification

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]

Standard ECMA-295 D e c e mb e r 1 9 9 9

Standardizing Information and Communication Systems

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW ECMA-295.DOC

03-01-00 12,20

Brief History

This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Broadband Private Integrated Services Networks (B-PISNs). The series uses B-ISDN concepts as developed by ITU-T and conforms to the 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 Technical Committee Signalling Protocols 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), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) protocol specification for the Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) Call Control, 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";

Part 4:

"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification".

Part 3 and part 4 will only be produced by 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 options have been implemented for a given Open Systems Interconnection (OSI) protocol. Such a statement is called a Protocol Implementation Conformance Statement (PICS). The Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bodies. It represents a pragmatic 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 contents 1

Scope

Conformance

References

Definitions

4.1

Protocol Implementation Conformance Statement (PICS)

4.2

PICS proforma

Abbreviations

Annex A - PICS proforma for ECMA-294

Annex B - Requirements

Annex C - Bibliography

- ii -

Scope This Standard is applicable to the Call Control protocol at the QB, SB, TB and co-incident SB/TB reference points within, between and at the access to Broadband Private Integrated Services Networks and within, between and at the access to public Broadband Integrated Services Digital Networks. This Standard provides the Protocol Implementation Conformance Statement (PICS) proforma for the Call Control protocol as specified in ECMA-294 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7.

Conformance If it claims to conform to this Standard, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and ordering of the proforma items. A PICS which conforms to this Standard shall be a conforming PICS proforma completed in accordance with the guidance for completion given in clause A.1.

References The following documents contain provisions which, through reference in this text, constitute provisions of this Standard.

•

References are either specific (identified by date of publication, edition number, version number, etc.) or non-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 same number.

ECMA-254

Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol Generic Functional Protocol (B-QSIG-GF)

ECMA-294

ISO/IEC 9646-1

Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts

ISO/IEC 9646-7

Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements

ETS 300 796-1

Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Generic functional protocol; Core aspects; Part 1: Protocol specification [ITU-T Rec. Q.2932.1 (1996), modified]

Definitions For the purposes of this 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, stating which capabilities have been implemented for a given OSI protocol (see ISO/IEC 9646-1).

- 2 -

4.2

PICS proforma A 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).

Abbreviations For the purposes of this Standard, the following abbreviations apply: CC

Call Control

ICS

Implementation Conformance Statement

IUT

Implementation Under Test

Major Capabilities

Messages Received

Messages Transmitted

OSI

Open Systems Interconnection

Parameters

PICS

Protocol Implementation Conformance Statement

Role

Subsidiary Capabilities

SCS

System Conformance Statement

SUT

System Under Test

Timers

- 3 -

Annex A (normative)

PICS proforma for ECMA-294

A.1 A.1.1

Guidance for completing the PICS proforma Purposes and structure The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements 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:

A.1.2

guidance for completing the PICS proforma;

identification of the implementation;

identification of the protocol;

global statement of conformance;

Roles;

Major capabilities;

Subsidiary capabilities;

Application protocol data units;

APDU parameters;

Timers.

Abbreviations and conventions The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported 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.

optional - the capability may be supported or not.

n/a

not applicable - in the given context, it is impossible to use the capability.

o.i

qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table.

c.i

conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table.

- 4 -

Reference column: The reference column makes reference to ECMA-294, except where explicitly 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 or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in the space for comments provided at the bottom of the table. It uses predicates defined in the 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_: ?3:

IF prof1 THEN Y ELSE N

NOTE As stated in ISO/IEC 9646-7, support for a received PDU requires the ability to parse all valid parameters 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.

A.1.3

Instructions for completing the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in subclause 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 subclauses of the PICS proforma.

A.2

Identification of the implementation Identification 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 configuration options. 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 statement

......................................................................................................................................................................................

A.2.2

Implementation Under Test (IUT) identification

IUT name: ...................................................................................................................................................................................... ...................................................................................................................................................................................... IUT version: ......................................................................................................................................................................................

- 5 -

A.2.3

System Under Test (SUT) identification

SUT name: ...................................................................................................................................................................................... ...................................................................................................................................................................................... Hardware configuration: ...................................................................................................................................................................................... ...................................................................................................................................................................................... ...................................................................................................................................................................................... Operating system: ......................................................................................................................................................................................

A.2.4

Product supplier

Name: ...................................................................................................................................................................................... Address: ...................................................................................................................................................................................... ...................................................................................................................................................................................... ...................................................................................................................................................................................... Telephone number: ...................................................................................................................................................................................... Facsimile number: ...................................................................................................................................................................................... E-mail address: ...................................................................................................................................................................................... Additional information: ...................................................................................................................................................................................... ...................................................................................................................................................................................... ......................................................................................................................................................................................

A.2.5

Client

- 6 -

E-mail address: ...................................................................................................................................................................................... Additional information: ...................................................................................................................................................................................... ...................................................................................................................................................................................... ......................................................................................................................................................................................

A.2.6

PICS contact person

Name: ...................................................................................................................................................................................... Address: ...................................................................................................................................................................................... ...................................................................................................................................................................................... Telephone number: ...................................................................................................................................................................................... Facsimile number: ...................................................................................................................................................................................... Additional information: ...................................................................................................................................................................................... ...................................................................................................................................................................................... ......................................................................................................................................................................................

A.3

Identification of the protocol This PICS proforma applies to the following standard: ECMA-294

A.4

Global statement of conformance Are all mandatory capabilities implemented? (Yes/No)

......................

NOTE Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma.

- 7 -

A.5

Roles Table A.1 - Roles

A.6

Item

Role

References

Support of Call Control in an originating CC entity

Condition

Status

Support

6.1

o.1

Yes[ ] No[ ]

Support of Call Control in a terminating CC entity

6.1

o.1

Yes[ ] No[ ]

Support of Call Control in a transit CC entity

6.1

o.1

Yes[ ] No[ ]

o.1

Support of at least one of these options is required.

Major Capabilities Table A.2 - Major Capabilities Item

Question/feature (Does the implementation ... ?)

References

Condition

Status

Support

MC1

Support signalling procedures for call establishment request when acting as a preceding CC entity

9.1.1

R1 OR R3

Yes[ ] No[ ]

Support signalling procedures for call establishment request when acting as a succeeding CC entity

9.1.2

Support two message sequence for call establishment

9.1, 9.3

MC2

MC3

N/A[ ] R2 OR R3

Yes[ ] No[ ] N/A[ ]

MC1 OR MC2

Yes[ ] No[ ] N/A[ ]

MC4

Support three message sequence for call establishment

9.1, 9.3

MC1 MC2

o m

Yes[ ] No[ ] N/A[ ]

MC5

MC6

MC7

MC8

MC9

MC10

Support signalling procedures for call proceeding when acting as a preceding CC entity

9.2.1

Support signalling procedures for call proceeding when acting as a succeeding CC entity

9.2.2

Support signalling procedures for call acceptance when acting as a preceding CC entity

9.3.1

Support signalling procedures for call acceptance when acting as a succeeding CC entity

9.3.2

Support signalling procedures for completion of call establishment when acting as a preceding CC entity

9.4.1

Support signalling procedures for completion of call establishment when acting as a succeeding CC entity

9.4.2

R1 OR R3

Yes[ ] No[ ] N/A[ ]

R2 R3

o m

Yes[ ] No[ ] N/A[ ]

R1 OR R3

Yes[ ] No[ ] N/A[ ]

R2 OR R3

Yes[ ] No[ ] N/A[ ]

MC4

Yes[ ] No[ ] N/A [ ]

MC4

Yes[ ] No[ ] N/A [ ]

- 8 -

Item

Question/feature (Does the implementation ... ?)

MC11

MC12

MC13

References

Condition

Status

Support

Support signalling procedures for call status 9.5.1 change report when acting as an initiating CC entity

R1 OR R2

Yes[ ] No[ ]

Support signalling procedures for call status change report when acting as a receiving CC entity

R1 OR R2

9.5.2

N/A[ ] m

Yes[ ] No[ ] N/A[ ]

Support signalling procedures for call clearing 9.7

R1 OR R2 OR R3

Yes[ ] No[ ] N/A[ ]

MC14

MC15

Support bearer co-ordination requirements when acting as a CC entity that establishes a bearer towards an adjacent CC entity

A.1

Support bearer co-ordination requirements when acting as a CC entity that receives a bearer establishment from an adjacent CC entity

A.2

R1 OR R2 OR R3

Yes[ ] No[ ] N/A[ ]

R1 OR R2 OR R3

Yes[ ] No[ ] N/A[ ]

MC16

Support additional bearer co-ordination A.3 requirements when acting as a transit CC entity

Yes[ ] No[ ]

MC17

Support bearer co-ordination requirements on A.4 call clearing

R1 OR R2 OR R3

N/A[ ] Yes[ ] No[ ]

Support Call Description handling at a CC signalling service user within an originating CC entity

B.1

Support Call Description handling at a CC signalling service user within a transit CC entity

B.2

MC18

MC19

MC20

MC21

MC22

MC23

MC24

N/A[ ] Yes[ ] No[ ] N/A[ ]

Yes[ ] No[ ] N/A[ ]

Support Call Description handling at a CC B.3 signalling service user within a terminating CC entity

Support interworking procedures in case of outgoing call establishment to networks not supporting separation of call and bearer control

C.1.1

Yes[ ] No[ ] N/A[ ]

Yes[ ] No[ ] N/A [ ]

Support interworking procedures in case of C.1.2 incoming bearer establishment from networks not supporting separation of call and bearer control

Support interworking procedures in case of C.1.3 addition of bearers to a call with networks not supporting separation of call and bearer control

Support interworking procedures in case of C.2.1 outgoing call establishment to networks which only support simultaneous call and bearer establishment

Yes[ ] No[ ] N/A [ ]

- 9 -

Item

Question/feature (Does the implementation ... ?)

MC25

Condition

Status

Support

Support interworking procedures in case of C.2.2 incoming call and bearer establishment from networks which only support simultaneous call and bearer establishment

Yes[ ] No[ ]

Support interworking procedures in case of addition of bearers to a call with networks which only support simultaneous call and bearer establishment

C.2.3

MC27

Support connection oriented – bearer independent (CO-BI) transport mechanism

D.1

o.2

Yes[ ] No[ ]

MC28

Support connectionless – bearer independent (CL-BI) transport mechanism

D.2

o.2

Yes[ ] No[ ]

MC29

Support a reliable transport mechanism which D is not listed in ECMA-294

o.2

Yes[ ] No[ ]

o.2

Support of at least one of these options is required.

MC26

A.7

References

N/A [ ]

Yes[ ] No[ ] N/A [ ]

Subsidiary Capabilities Table A.3 - Subsidiary Capabilities Item

Question/feature (Does the implementation ... ?)

References

Condition

Status

Support

SC1

Support signalling procedures for call establishment failure when acting as a preceding CC entity

9.6.1

R1 OR R3

Yes[ ] No[ ]

Support signalling procedures for call establishment failure when acting as a succeeding CC entity

9.6.2

Support exceptional procedures on timer expiry when acting as a preceding CC entity

9.8.1.1

SC2

SC3

N/A[ ] R2 OR R3

Yes[ ] No[ ] N/A[ ]

R1 OR R3

Yes[ ] No[ ] N/A[ ]

SC4

Support exceptional procedures on timer 9.8.1.2 expiry when acting as a succeeding CC entity

R2 OR R3

Yes[ ] No[ ] N/A[ ]

SC5

SC6

SC7

SC8

Support exceptional procedures on timer 9.8.1.3 expiry when acting as a CC entity that initiated call clearing

MC13

Support exceptional procedures on receipt of 9.8.2 APDUs with unknown Call Segment Id when acting as a succeeding CC entity

MC2

Support exceptional procedures on receipt of 9.8.3 APDUs with duplicated Call Segment Id when acting as a succeeding CC entity

MC2

Support exceptional procedures on receipt of APDUs out of sequence when acting as a preceding CC entity

MC7

9.8.4

Yes[ ] No[ ] N/A[ ]

- 10 -

Item

Question/feature (Does the implementation ... ?)

References

Condition

Status

Support

SC9

Support exceptional procedures on receipt of reject APDUs

9.8.5

MC1 OR MC2

Yes[ ] No[ ] N/A[ ]

SC10

SC11

SC12

A.8

Support procedures for the handling of unrecognized parameters within CCOperations

9.8.6

MC1 OR MC2

Yes[ ] No[ ] N/A[ ]

Support changes to the information model at a B.4 CC signalling service user within an initiating CC entity

MC11

Support changes to the information model at a B.4 CC signalling service user within a receiving CC entity

MC12

Yes[ ] No[ ] N/A[ ]

Application protocol data units Table A.4 - APDUs transmitted Item

Question/feature

References

Condition

Status

Support

MT1

Sending of callEstablish invoke

9.1.1

MC1

Yes[ ] No[ ] N/A[ ]

MT2

Sending of callProceeding invoke

9.2.2

MC6

Yes[ ] No[ ] N/A[ ]

MT3

Sending of callComplete invoke

9.4.1

MC9

Yes[ ] No[ ] N/A[ ]

MT4

Sending of callStatus invoke

9.5.1

MC11

Yes[ ] No[ ] N/A[ ]

MT5

Sending of callRelease invoke

9.7.1

MC13

Yes[ ] No[ ] N/A[ ]

MT6

Sending of callEstablish return result/error

9.3.2 / 9.6.2

MC8 / SC2

Yes[ ] No[ ] N/A[ ]

MT7

Sending of callRelease return result

9.7.2

MC13

Yes[ ] No[ ] N/A[ ]

- 11 -

Table A.5 - APDUs received Item

Question/feature

References

Condition

Status

Support

MR1

Receipt of callEstablish invoke

9.1.2

MC2

Yes[ ] No[ ] N/A[ ]

MR2

Receipt of callProceeding invoke

9.2.1

MC5

Yes[ ] No[ ] N/A[ ]

MR3

Receipt of callEstablish return result/error

9.3.1 / 9.6.1

MC7 / SC1

Yes[ ] No[ ] N/A[ ]

MR4

Receipt of callComplete invoke

9.4.2

MC10

Yes[ ] No[ ] N/A[ ]

MR5

Receipt of callStatus invoke

9.5.2

MC12

Yes[ ] No[ ] N/A[ ]

MR6

Receipt of callRelease return result

9.7.1

MC13

Yes[ ] No[ ] N/A[ ]

MR7

Receipt of callRelease invoke

9.7.2

MC13

Yes[ ] No[ ] N/A[ ]

MR8

Receipt of a reject APDU correlated to a callEstablish invoke

9.8.5.1

MC1

Yes[ ] No[ ] N/A[ ]

MR9

Receipt of a reject APDU correlated to a callProceeding invoke

9.8.5.2

MC6

Yes[ ] No[ ] N/A[ ]

MR10

Receipt of a reject APDU correlated to a callComplete invoke

9.8.5.3

MC9

Yes[ ] No[ ] N/A[ ]

MR11

Receipt of a reject APDU correlated to a callStatus invoke

9.8.5.4

MC11

Yes[ ] No[ ] N/A[ ]

MR12

Receipt of a reject APDU correlated to a callRelease invoke

9.8.5.5

MC13

Yes[ ] No[ ] N/A[ ]

MR13

Receipt of a reject APDU correlated to a callEstablish return result

9.8.5.6

MC2

Yes[ ] No[ ] N/A[ ]

MR14

Receipt of a reject APDU correlated to a callEstablish return error

9.8.5.7

MC2

Yes[ ] No[ ] N/A[ ]

MR15

Receipt of a reject APDU correlated to a callRelease return result

9.8.5.8

MC13

Yes[ ] No[ ] N/A[ ]

- 12 -

A.9

APDU Parameters Table A.6 - APDU Parameters Item

Question/feature (Does the implementation ... ?)

References

Support inclusion of bearerEstablAddress in callEstablish return result

Condition

Status

Support

8.1, 9.3.2, A.1 MT6

Yes[ ] No[ ] N/A[ ]

Support inclusion of an alternative callDescription in callEstablish return error

8.1, 9.6.2, B.3 MT6

Yes[ ] No[ ] N/A[ ]

Support inclusion of an end-to-end relevant part within callDescription

8.1, B.1

MT1

Yes[ ] No[ ] N/A[ ]

Support inclusion of a modified end-to-end relevant part within callChangedParameter

8.1, B.4

MT4

Yes[ ] No[ ] N/A[ ]

Support inclusion of a bearerIdList within callDescription

8.3, A.1

MT1

Yes[ ] No[ ] N/A[ ]

Support inclusion of service components within callDescription

8.3, B.1

MT1

Yes[ ] No[ ] N/A[ ]

A.10 Timers Table A.7 - Timers Item

Question/feature

References

Condition

Status

Value

Support

TM1

Support of timer T703 by a preceding CC entity

R1 OR R2

3s – 15s

Yes[ ] No[ ] N/A[ ]

TM2

Support of timer T708 by a preceding CC entity

R1 OR R2

30s

Yes[ ] No[ ] N/A[ ]

TM3

Support of timer T708 by a succeeding CC entity

R1 OR R2

30s

Yes[ ] No[ ] N/A[ ]

TM4

Support of timer T710 by a preceding CC entity

R1 OR R2

30s

Yes[ ] No[ ] N/A[ ]

TM5

Support of timer T701 by a succeeding CC entity

R1 OR R2

180s

Yes[ ] No[ ] N/A[ ]

- 13 -

Annex B (normative)

Requirements

This annex lists requirements to the transport mechanisms and some items of the generic functional protocol as specified in ETS 300 796-1 for the SB and coincident SB/TB reference point or in ECMA-254 for the QB reference point required for the support of ECMA-294. Table B.1 - Major Capabilities Item

Question/feature (Does the implementation ... ?)

References

MC30

Support connection oriented – bearer independent (CO-BI) transport mechanism at the SB and coincident SB/TB reference point

MC31

Condition

Status

Support

D.1

o.3

Yes[ ] No[ ]

Support connection oriented – bearer independent (CO-BI) transport mechanism at the QB reference point

D.1

o.3

Yes[ ] No[ ]

MC32

Support connectionless – bearer independent (CL-BI) transport mechanism at the SB and coincident SB/TB reference point

D.2

o.3

Yes[ ] No[ ]

MC33

Support connectionless – bearer independent (CL-BI) transport mechanism at the QB reference point

D.2

o.3

Yes[ ] No[ ]

MC34

Support a reliable transport mechanism which D is not listed in ECMA-294

o.3

Yes[ ] No[ ]

o.3

Support of at least one of these options is required.

Table B.2 - Subsidiary Capabilities Item

Question/feature (Does the implementation ... ?)

References

Condition

Status

Support

SC13

Support coding of CC operations in the Facility information element as specified in ETS 300 796-1 or ECMA-254

D.1, D.2

MC1 OR MC2 OR MC3 OR MC4

Yes[ ] No[ ]

Support coding of the instruction indicator in D.1, D.2 the Facility information element as specified in ETS 300 796-1 or ECMA-254

MC1 OR MC2 OR MC3 OR MC4

Support sending of the Facility information element in the messages for the CO-BI transport mechanism as specified in ETS 300 796-1 or ECMA-254

MC1 OR MC2

SC14

SC15

D.1

N/A[ ] Yes[ ] No[ ] N/A[ ] Yes[ ] No[ ] N/A[ ]

- 14 -

Item

Question/feature (Does the implementation ... ?)

References

Condition

Status

Support

SC16

Support coding of the instruction indicator in the messages for the CO-BI transport mechanism as specified in ETS 300 796-1 or ECMA-254

D.1

MC1 OR MC2

Yes[ ] No[ ]

SC17

SC18

SC19

N/A[ ]

Support sending of the Facility information D.2 element in the FACILITY message for the CLBI transport mechanism as specified in ETS 300 796-1or ECMA-254

MC3 OR MC4

Support coding of the instruction indicator in the FACILITY message for the CL-BI transport mechanism as specified in ETS 300 796-1or ECMA-254

MC3 OR MC4

D.2

Support inclusion of the NFE when conveying D.1, D.2 an invoke APDU of the CC operations

Yes[ ] No[ ] N/A[ ]

MC2 OR MC4

Yes[ ] No[ ] N/A[ ]

SC20

Support inclusion of the Interpretation APDU D.1, D.2 when conveying an invoke APDU of the CC operations

MC2 OR MC4

Yes[ ] No[ ] N/A[ ]

- 15 -

Annex C (informative)

Bibliography

ETS 300 406

Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology

Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email:

+41 22 849.60.01 [email protected]

Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports.

ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.

ECMA-295 — B-ISDN and B-PISN - Digital Subscriber Signalling System No. two (DSS2), Broadband Inter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - Call control in a separated call and bearer control environment - Part 2:

Related documents