Standard ECMA-254 2 n d E d i t i o n - D e c e mb e r 1 9 9 9
Standardizing Information and Communication Systems
Broadband Private Integrated Services Network (B-PISN) Inter-Exchange Signalling Protocol Generic Functional Protocol
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]
..
Standard ECMA-254 2 n d E d i t i o n - D e c e mb e r 1 9 9 9
Standardizing Information and Communication Systems
Broadband Private Integrated Services Network (B-PISN) Inter-Exchange Signalling Protocol Generic Functional Protocol (B-QSIG-GF)
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW ECMA-254.DOC
13-06-01 08,57
..
Brief History
This Standard is one of a series of ECMA standards defining services and signalling protocols applicable to Broadband Private Integrated Services Networks. The series uses the B-ISDN concepts as developed by ITU-T (formerly CCITT) and is also within the framework of standards for open systems interconnection as defined by ISO. This Standard is based upon ATM Forum’s specification AF-CS-0102.000 with modification indicated in the text of this Standard. This Standard specifies the signalling protocol for use at the Q reference point in support of the Generic Functional Protocol. 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 standardisation bodies. It represents a pragmatic and widely based consensus. This ECMA Standard is contributed to ISO/IEC JTC1 under the terms of the fast-track procedure for adoption as an ISO/IEC International Standard.
Adopted as 2nd Edition of Standard ECMA-254 by the General Assembly of December 1999.
..
List of corrected errata for ECMA-254 5 June 2001
Summary Following is a summary of the errors detected and corrected in Standard ECMA-254, Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol - Generic Functional Protocol.
Clause 1 Scope, paragraph 1 and clause 5 Abbreviations The abbreviation “PINX” is wrong in both clause 1 and clause 5 – it should be changed to “Private Integrated services Network eXchange” Clause 1 Scope, paragraph 1 Corrected: This Standard specifies the functional protocol for the support of supplementary services and additional basic call capabilities at the Q-reference point. The Q-reference point exists between Private Integrated services Network eXchanges (PINX) connected together within a Private Integrated Services Network (PISN) and is defined in ISO/IEC 11579-1. The generic functional protocol is part of the B-QSIG signalling system. Original: This Standard specifies the functional protocol for the support of supplementary services and additional basic call capabilities at the Q-reference point. The Q-reference point exists between Private Integrated Services Exchanges (PINX) connected together within a Private Integrated Services Network (PISN) and is defined in ISO/IEC 11579-1. The generic functional protocol is part of the B-QSIG signalling system.
Clause 5 Abbreviations, paragraph 9 Corrected: PINX
Private Integrated services Network eXchange
Original: PINX
Private Integrated Network Exchange
Clause 3 References (normative) ‘References contained in section 26.3 ....’, should refer to section 26.2. Corrected: References contained in section 26.2 of AF-CS-0102.000 shall apply with the following additions: Original: References contained in section 26.3 of AF-CS-0102.000 shall apply with the following additions:
Clause 4 Definitions ‘Definitions contained in section 26.2 ....’, should refer to section 26.3. Corrected: Definitions contained in section 26.3 of AF-CS-0102.000 shall apply with the following additions:
Original: Definitions contained in section 26.2 of AF-CS-0102.000 shall apply with the following additions:
Clause 6.3 Protocol architecture ‘Protocol Architecture described in section 26.6.3 ....’, should refer to section 26.5.3. Corrected: Protocol Architecture described in section 26.5.3 of AF-CS-0102.000 shall apply with the following modifications: Original: Protocol Architecture described in section 26.6.3 of AF-CS-0102.000 shall apply with the following modifications:
Clause 10.2.3.1 Actions at a source node The title should be ‘Actions at a source PINX’. Also the word ‘node’ in the first paragraph of this section should be changed to ‘PINX’. Corrected: 10.2.3.1 Actions at a source PINX Actions at a source PINX described in section 26.9.2.3.1 of AF-CS-0102.000 shall apply with the following modifications: Proposal:
Original:
10.2.3.1 Actions at a source node Actions at a source node described in section 26.9.2.3.1 of AF-CS-0102.000 shall apply with the following modifications:
Clause 10.2.3.2 Actions at a receiving node The title should be ‘Actions at a receiving PINX’. Also the word ‘node’ in the first paragraph of this section should be changed to ‘PINX’. Corrected: 10.2.3.2 Actions at a receiving PINX Actions at a receiving PINX described in section 26.9.2.3.2 of AF-CS-0102.000 shall apply with the following modifications: Original: 10.2.3.2 Actions at a receiving node Actions at a receiving node described in section 26.9.2.3.2 of AF-CS-0102.000 shall apply with the following modifications:
Clause 10.2.3.3 Actions at a destination node The title should be ‘Actions at a destination PINX’. Also the word ‘node’ in the first paragraph of this section should be changed to ‘PINX’. Corrected: 10.2.3.3 Actions at a destination PINX Actions at a destination PINX described in section 26.9.2.3.3 of AF-CS-0102.000 shall apply.
Original: 10.2.3.3 Actions at a destination node Actions at a destination node described in section 26.9.2.3.3 of AF-CS-0102.000 shall apply.
.
- i -
Table of contents 1
Scope
1
2
Conformance
1
3
References (normative)
1
4
Definitions
1
4.1
Gateway PINX
1
4.2
Inter-PINX link (IPL)
1
4.3
Preceding side
1
4.4
Private Integrated services Network eXchange (PINX)
2
4.5
Succeeding side
2
5
Abbreviations
2
6
Description
2
6.1
Overview
2
6.2
Addressing mechanisms
2
6.2.1
Explicit addressing
2
6.2.2
Functional addressing
2
6.3
Protocol architecture
3
6.4
Services provided by individual protocol entities
3
6.4.1
Services provided by ROSE
3
6.4.2
Services provided by GFT-control
3
6.4.3
Services provided by bearer-related transport
3
6.4.4
Services provided by connectionless bearer-independent transport
3
6.4.5
Services provided by connection-oriented bearer-independent transport
3
7 8
Operational requirements
3
Primitive definitions and state definitions
3
8.1
Primitive definitions
3
8.2
State definitions
3
8.2.1
APDU transport mechanisms
3
8.2.2
GFT-Control
3
Coding requirements
4
Message functional definitions and content
4
9 9.1 9.1.1
Additional messages for bearer-related transactions
4
9.1.2
Messages for connectionless bearer-independent transport
4
9.1.3
Messages for connection-oriented bearer-independent transport
4
9.2
General message format and information element coding
5
9.2.1
Message type
5
9.2.2
Other information elements
5
- ii -
9.2.3 10
Encoding of information described using ASN.1 Signalling procedures
10.1
5 5
APDU transport mechanisms
5
10.1.1
Bearer-related transport
6
10.1.2
Bearer-independent transport mechanisms
6
10.1.3
Connection-oriented bearer-independent transport mechanism
6
10.1.4
Connectionless bearer-independent transport mechanism
7
10.2
GFT-Control procedures for APDUs
7
10.2.1
GFT-control procedures for transport of APDUs
7
10.2.2
GFT-Control procedures for CO-BI connection control
8
10.2.3
GFT-Control procedures for CL-BI mode
8
10.3
Remote operations procedures
9
10.3.1
Introduction
9
10.3.2
Procedures for operations
9
10.4
Notification transport mechanisms
9
10.4.1
Sending notification information
9
10.4.2
Receiving notification information
9
GFT-Control procedures for notifications
9
10.5 10.5.1
Actions at a PINX which generates notifications
9
10.5.2
Actions at a receiving PINX
9
Interworking with (narrowband) QSIG
10
11 11.1
Full termination of generic functional protocol
10
11.2
Generic interworking function
10
11.2.1
Architecture
10
11.2.2
Bearer-related transport mechanism
10
11.2.3
Connection-oriented bearer independent transport mechanism
10
11.2.4
Connectionless bearer independent transport mechanism
10
12
Parameter values
12.1 13
Connection-oriented bearer-independent transport
10 10
Dynamic description (SDLs)
10
13.1
Block overview diagram
10
13.2
Component transport mechanisms
10
13.2.1
Bearer-related transport mechanism
10
13.2.2
Connection-oriented bearer-independent transport mechanism
10
13.2.3
Connectionless bearer-independent transport mechanism
10
13.3 14
GFT-Control Manufacturer Specific Information (MSI)
11 17
14.1
Manufacturer specific operations and errors
17
14.2
Manufacturer specific additions to standardised operations and error
17
14.3
Manufacturer specific notifications
17
- iii -
Annex A - Protocol Implementation Conformance Statement (PICS) proforma
19
Annex B - Formal definition of data types using ITU-T Rec. X.208
21
Annex C - Formal definition of data types using ITU-T Rec. X.680
23
Annex D - Information flows
25
Annex E - Instruction indicators
27
Annex F - Formal definitions of remote operations notation using ITU-T Rec. X.208
29
Annex G - Formal definitions of remote operations notation using ITU-T Rec. X.680
31
Annex H - Examples of the use of Manufacturer Specific Information
33
Annex I - Remote operations protocol
35
Annex J - Problem code definitions
37
- iv -
.
1
Scope This Standard specifies the functional protocol for the support of supplementary services and additional basic call capabilities at the Q-reference point. The Q-reference point exists between Private Integrated services Network eXchanges (PINX) connected together within a Private Integrated Services Network (PISN) and is defined in ISO/IEC 11579-1. The generic functional protocol is part of the B-QSIG signalling system. The procedures specified in this Standard can be used in association with a bearer connection (bearer-related) or outside the context of any bearer connection (bearer-independent).The application of this Standard to individual additional basic call capabilities and supplementary services is outside the scope of this Standard and should be defined in those standards or proprietary specifications that specify the individual capabilities. All conformance to this Standard is based on the external behaviour at the interface at the Q-reference point, i.e. on the generation of the correct message structure and in the proper sequence as specified in this Standard. The generic functional protocol is based on ATM Forum specification AF-CS-0102.000, which itself is based on the DSS2 generic functional protocol specified in ITU-T Rec. Q.2932.1 but extended to allow non-local information exchange as well as local information exchange. This Standard is applicable to PINXs supporting additional basic call capabilities and/or supplementary services requiring the functional protocol for signalling at the Q-reference point.
2
Conformance In order to conform to this Standard, a PINX shall satisfy the requirements identified in the Protocol Implementation Conformance Statement (PICS) proforma in section 30 of AF-CS-0102.000.
3
References (normative) AF-CS-0102.000
PNNI Addendum on PNNI/B-QSIG Interworking and Generic Functional Protocol for the Support of Supplementary Services
References contained in section 26.2 of AF-CS-0102.000 shall apply with the following additions:
4
ECMA-265
Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol Signalling ATM Adaptation Layer (International Standard ISO/IEC 13246)
ECMA-266
Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol Basic Call/Connection Control (International Standard ISO/IEC 13247)
ISO/IEC 11579-1
Information technology - Telecommunications and information exchange between systems Private Integrated Services Network - Part 1: Reference configuration for PISN exchanges (PINX) (1994)
Definitions Definitions contained in section 26.3 of AF-CS-0102.000 shall apply with the following additions:
4.1
Gateway PINX The definition in ECMA-266 shall apply. Dependent on the capabilities of the signalling system being interworked by the gateway PINX, it can act as a Transit or an End PINX in the context of the supplementary services APDUs. That is, it can either transport the APDUs unchanged to or from the other signalling system, perhaps embedded in some other protocol unit, or process the APDUs and perform an interworking function of the information flows and encoding of the Supplementary service concerned.
4.2
Inter-PINX link (IPL) The definition in ECMA-266 shall apply.
4.3
Preceding side In the context of a call/connection or a CO-BI connection using an IPL, the side that initiates call/connection or CO-BI connection establishment over that IPL (see figure 1 in ECMA-266).
- 2 -
4.4
Private Integrated services Network eXchange (PINX) As specified in ISO/IEC 11579-1.
4.5
Succeeding side In the context of a call/connection or a CO-BI connection using an IPL, the opposite side from the side that initiates call/connection or CO-BI connection establishment over that IPL (see figure 1 in ECMA-266). NOTE The term ‘node’ in AF-CS-0102.000 is equal to the term ‘PINX’. The term ‘PNNI’ in AF-CS-0102.000 is equal to the term ‘B-QSIG’.
5
Abbreviations Abbreviations contained in section 26.4 of AF-CS-0102.000 shall apply with the following additions:
6
APDU
Application Protocol Data Unit
CL-BI
Connectionless Bearer Independent
CO-BI
Connection Oriented Bearer Independent
IPL
Inter-PINX Link
IPVCI
Inter-PINX Virtual Channel Identifier
IPVPI
Inter-PINX Virtual Path Identifier
PISN
Private Integrated Services Network
PINX
Private Integrated services Network eXchange
ROSE
Remote Operation Service Element
VCI
Virtual Channel Identifier
VPI
Virtual Path Identifier
Description
6.1
Overview The generic functional protocol provides a means of exchanging ROSE APDUs on behalf of Application Service Control entities located in different PINXs. These Application Service Control entities may be for the support of supplementary services or additional basic call capabilities. This exchange may take place either in association with a bearer established using the procedures of ECMA-266 or independently of any bearer. Bearer independent transport can either be connection-oriented or connectionless. In the case of connection-oriented bearerindependent transport, establishment and release of the connection is specified in this Standard. For bearer-related transport and connection-oriented bearer-independent transport, the exchange of ROSE APDUs can be between any of two PINXs involved in the connection, as determined by addressing information transported with the APDUs (e.g., between the two End PINXs). For connectionless bearer independent transport, the exchange of ROSE APDUs is between the source PINX and the destination PINX for the transporting message.
6.2
Addressing mechanisms Addressing mechanisms described in section 26.5.2 of AF-CS-0102.000 shall apply.
6.2.1
Explicit addressing Explicit addressing described in section 26.5.2.1 of AF-CS-0102.000 shall apply.
6.2.2
Functional addressing Functional addressing described in section 26.5.2.2 of AF-CS-0102.000 shall apply.
- 3 -
6.3
Protocol architecture Protocol Architecture described in section 26.5.3 of AF-CS-0102.000 shall apply with following modification: − Replace all references to PNNI, ITU-T Rec. Q.2931 and Q.2971 with references to ECMA-266.
6.4
Services provided by individual protocol entities
6.4.1
Services provided by ROSE Services provided by ROSE described in section 26.5.4.1 of AF-CS-0102.000 shall apply.
6.4.2
Services provided by GFT-control Services provided by GFT-control described in section 26.5.4.2 of AF-CS-0102.000 shall apply.
6.4.3
Services provided by bearer-related transport Services provided by bearer-related transport described in section 26.5.4.3 of AF-CS-0102.000 shall apply with following modification: − Replace all references to PNNI, ITU-T Rec. Q.2931 and Q.2971 with references to ECMA-266.
6.4.4
Services provided by connectionless bearer-independent transport Services provided by connectionless bearer-independent transport described in section 26.5.4.4 of AF-CS-0102.000 shall apply.
6.4.5
Services provided by connection-oriented bearer-independent transport Services provided by connection-oriented bearer-independent transport described in section 26.5.4.5 of AF-CS-0102.000 shall apply.
7
Operational requirements Operational requirements described in section 26.6 of AF-CS-0102.000 shall apply.
8
Primitive definitions and state definitions
8.1
Primitive definitions Primitive definitions described in section 26.7.1 of AF-CS-0102.000 shall apply with following modification: − Replace all references to PNNI, ITU-T Rec. Q.2931 and Q.2971 with references to ECMA-266.
8.2
State definitions
8.2.1 8.2.1.1
APDU transport mechanisms Bearer-related transport mechanism There are no additional call/connection states over and above those defined in ECMA-266 clause 6.4.
8.2.1.2
Connectionless bearer-independent transport mechanism Connectionless bearer-independent transport states described in section 26.7.2.1.2 of AF-CS-0102.000 shall apply.
8.2.1.3
Connection-oriented bearer-independent transport mechanism Connection-oriented bearer-independent transport states described in section 26.7.2.1.3 of AF-CS-0102.000 shall apply.
8.2.2
GFT-Control The GFT-control state described in section 26.7.2.2 of AF-CS-0102.000 shall apply.
- 4 -
9
Coding requirements
9.1
Message functional definitions and content This subclause shall be read in conjunction with clause 7 of ECMA-266. All messages are additional to those defined in that clause and the following tables should be interpreted according to the introductory material of clause 7 of ECMA-266. To determine if an information element specified in this Standard is allowed to be included in the following messages, see subclause 9.2. Information elements not defined in subclause 9.2 are only allowed to be included in the following messages when explicitly indicated in the message structure.
9.1.1
Additional messages for bearer-related transactions Additional messages for bearer-related transactions described in section 26.8.1.1 of AF-CS-0102.000 shall apply.
9.1.1.1
FACILITY FACILITY message described in section 26.8.1.1.1 of AF-CS-0102.000 shall apply.
9.1.2 9.1.2.1
Messages for connectionless bearer-independent transport FACILITY FACILITY message described in section 26.8.1.2.1 of AF-CS-0102.000 shall apply with the following modification: − Broadband repeat indicator is not applicable. − Designated transit list is not applicable. − Connection scope selection is not applicable.
9.1.3 9.1.3.1
Messages for connection-oriented bearer-independent transport CALL PROCEEDING CALL PROCEEDING message described in section 26.8.1.3.1 of AF-CS-0102.000 shall apply.
9.1.3.2
CO-BI SETUP CO-BI SETUP message described in section 26.8.1.3.2 of AF-CS-0102.000 shall apply with the following modification: − Broadband repeat indicator is not applicable. − Designated transit list is not applicable. − Connection scope selection is not applicable.
9.1.3.3
CONNECT CONNECT message described in section 26.8.1.3.3 of AF-CS-0102.000 shall apply.
9.1.3.4
FACILITY FACILITY message described in section 26.8.1.3.4 of AF-CS-0102.000 shall apply.
9.1.3.5
NOTIFY NOTIFY message described in section 26.8.1.3.5 of AF-CS-0102.000 shall apply.
9.1.3.6
RELEASE RELEASE message described in section 26.8.1.3.6 of AF-CS-0102.000 shall apply with the following modification: − Crankback is not applicable.
9.1.3.7
RELEASE COMPLETE RELEASE COMPLETE message described in section 26.8.1.3.7 of AF-CS-0102.000 shall apply with the following modification: − Crankback is not applicable.
- 5 -
9.1.3.8
STATUS STATUS message described in section 26.8.1.3.8 of AF-CS-0102.000 shall apply.
9.1.3.9
STATUS ENQUIRY STATUS ENQUIRY message described in section 26.8.1.3.9 of AF-CS-0102.000 shall apply.
9.2
General message format and information element coding Section 26.8.2 of AF-CS-0102.000 shall apply.
9.2.1
Message type Message type described in section 26.8.2.1 of AF-CS-0102.000 shall apply.
9.2.2
Other information elements Other information elements described in section 26.8.2.2 of AF-CS-0102.000 shall apply.
9.2.2.1
Call state The call state information element is defined as in subclause 8.5.15 of ECMA-266. However the state value assignments defined in table 9 / Q.2932.1 exist for the connection-oriented bearer-independent transport mechanism.
9.2.2.2
Facility Facility information element described in section 26.8.2.2.2 of AF-CS-0102.000 shall apply.
9.2.2.2.1
Network Facility Extension (NFE) Network Facility Extension (NFE) described in section 26.8.2.2.2.1 of AF-CS-0102.000 shall apply.
9.2.2.2.2
Interpretation APDU Interpretation APDU described in section 26.8.2.2.2.2 of AF-CS-0102.000 shall apply.
9.2.2.2.3
ROSE APDU ROSE APDU described in section 26.8.2.2.2.3 of AF-CS-0102.000 shall apply.
9.2.2.3
Notification indicator Notification indicator information element described in section 26.8.2.2.3 of AF-CS-0102.000 shall apply.
9.2.2.4
Treatment of existing ECMA-266 information elements as parameters Supplementary service or additional basic call capability protocol specifications are expected to require new parameters to be defined and to require existing ECMA-266 information elements. New parameters shall be defined using ITU-T Rec. X.209 coding, or ITU-T Rec. X.690 as appropriate, if they do not appear elsewhere in ECMA-266 messages. Supplementary service or additional basic call capability protocol specifications may elect to encapsulate one or more existing ECMA-266 information elements within an ITU-T Rec. X.209 data element, or ITU-T Rec. X.690 data element, as appropriate, thereby retaining the ISO/IEC 13247 coding for these information elements. When this option is chosen, all the ECMA-266 information elements should be grouped together as the content following the BqsigInformationElement tag. This data element may appear by itself or as a member of a sequence or set. Encapsulation of the Facility information element within Facility information elements shall not be used. Type BqsigInformationElement is defined in B.2 of annex B using ASN.1 as specified in ITU-T recommendation X.208 and in C.2 of annex C using ASN.1 as specified in ITU-T recommendation X.680.
9.2.3
Encoding of information described using ASN.1 Encoding of information described using ASN.1 described in section 26.8.2.3 of AF-CS-0102.000 shall apply.
10 10.1
Signalling procedures APDU transport mechanisms APDU transport mechanisms described in section 26.9.1 of AF-CS-0102.000 shall apply.
- 6 -
10.1.1
Bearer-related transport Bearer-related transport described in section 26.9.1.1 of AF-CS-0102.000 shall apply.
10.1.1.1
Normal operation Normal operation described in section 26.9.1.1.1 of AF-CS-0102.000 shall apply.
10.1.1.2
Exceptional procedures If a receiving entity recognises a supplementary service or additional basic call capability request in a received SETUP message but is not able to process the request, then the following options shall apply: − the receiving entity may clear the call/connection request and reject the supplementary service or additional basic call capability invocation by means of an appropriate call-clearing message which contains the Cause information element and a return error APDU with the appropriate parameters in the Facility information element; − the receiving entity may continue to process the call/connection request according to the call/connection control procedures of ECMA-266, and reject the supplementary service or additional basic call capability invocation by including a return error APDU with the appropriate parameters in the Facility information element in a FACILITY message or in an appropriate call/connection control message or party control message; The option to be used depends on the individual supplementary service or additional basic call capability procedures, which are the subject of other standards. In addition, when the receiving entity identifies an error in the received APDU, the receiving entity may continue to process the call/connection request according to the call/connection control procedures of ECMA-266, and ignore the supplementary service or additional basic call capability invocation, in which case a reject component shall be generated. No response message shall be sent after the call reference value has been released. The procedures of subclause 10.1.1 are an extension to the procedures of ECMA-266. As such the general error handling procedures as defined in subclause 9.6 of ECMA-266 apply. However, the handling of errors in octets 5 onwards of the Facility information element is specified in subclause 10.2.1. The handling of errors in APDUs is specified in subclause 10.3. If the connection is being cleared, the treatment of outstanding supplementary service or additional basic call capability requests is subject to the standards for the individual supplementary services or additional basic call capabilities.
10.1.2
Bearer-independent transport mechanisms Bearer-independent transport mechanisms described in section 26.9.1.2 of AF-CS-0102.000 shall apply with following modification: − B-QSIG utilises the signalling AAL connection defined in ECMA-265 instead of ITU-T Rec. Q.2130.
10.1.3
Connection-oriented bearer-independent transport mechanism Connection-oriented bearer-independent transport mechanism described in section 26.9.1.3 of AF-CS-0102.000 shall apply.
10.1.3.1
Actions in the Null state Actions in the null state described in section 26.9.1.3.1 of AF-CS-0102.000 shall apply with following modification: − Replace all references to ITU-T Rec. Q.2931 with references to ECMA-266. − − B-QSIG utilises the signalling AAL connection defined in ECMA-265 instead of ITU-T Rec. Q.2130. − When entering the call present state, a CALL PROCEEDING message shall be sent. − Designated transit list is not applicable.
- 7 -
− The preceding side shall include the Called party number and the Calling party number information elements identifying the destination and the source respectively of the bearer independent signalling connection. 10.1.3.2
Actions in the Call Present state Actions in the Call Present state described in section 26.9.1.3.2 of AF-CS-0102.000 shall apply.
10.1.3.3
Actions in the Call Initiated state Actions in the Call Initiated state described in section 26.9.1.3.3 of AF-CS-0102.000 shall apply.
10.1.3.4
Actions in the Incoming Call Proceeding state Actions in the Incoming Call Proceeding state described in section 26.9.1.3.4 of AF-CS-0102.000 shall apply.
10.1.3.5
Actions in the Outgoing Call Proceeding state Actions in the Outgoing Call Proceeding state described in section 26.9.1.3.5 of AF-CS-0102.000 shall apply.
10.1.3.6
Actions in the Active state Actions in the Active state described in section 26.9.1.3.6 of AF-CS-0102.000 shall apply.
10.1.3.7
Connection release Actions in the Connection Release state described in section 26.9.1.3.7 of AF-CS-0102.000 shall apply.
10.1.3.8
Actions in the Release Request state Actions in the Release Request state described in section 26.9.1.3.8 of AF-CS-0102.000 shall apply.
10.1.3.9
Transport of APDUs associated with a connection-oriented bearer-independent signalling connection Transport of APDUs associated with a connection-oriented bearer-independent signalling connection described in section 26.9.1.3.9 of AF-CS-0102.000 shall apply.
10.1.3.10 Protocol error handling Protocol error handling described in section 26.9.1.3.10 of AF-CS-0102.000 shall apply with following modification: − Replace “- Actions regarding the handling of VCIs and VPCIs are not applicable;” with “- Actions regarding the handling of IPVCIs and IPVPIs are not applicable”. − Replace all references to ITU-T Rec. Q.2931 with references to ECMA-266. 10.1.4
Connectionless bearer-independent transport mechanism Connectionless bearer-independent transport mechanism described in section 26.9.1.4 of AF-CS-0102.000 shall apply.
10.1.4.1
Normal operation Normal operation described in section 26.9.1.4.1 of AF-CS-0102.000 shall apply with the following modification: − Designated Transit List is not applicable.
10.1.4.2
Exceptional procedure Exceptional procedure described in section 26.9.1.4.2 of AF-CS-0102.000 shall apply.
10.2
GFT-Control procedures for APDUs
10.2.1 10.2.1.1
GFT-control procedures for transport of APDUs Actions at a source PINX Actions at a source PINX described in section 26.9.2.1.1 of AF-CS-0102.000 shall apply
10.2.1.2
Actions at a receiving PINX Actions at a receiving PINX described in section 26.9.2.1.2 of AF-CS-0102.000 shall apply.
- 8 -
10.2.1.2.1
End PINX actions End PINX actions described in section 26.9.2.1.2.1 of AF-CS-0102.000 shall apply.
10.2.1.2.2
Transit PINX actions Transit PINX actions described in section 26.9.2.1.2.2 of AF-CS-0102.000 shall apply.
10.2.1.3
Actions at a destination PINX Actions at a destination PINX described in section 26.9.2.1.3 of AF-CS-0102.000 shall apply.
10.2.2
GFT-Control procedures for CO-BI connection control
10.2.2.1
Actions at an Originating PINX
10.2.2.1.1
Actions in the Originating_connection_idle state Actions in the Originating_connection_idle state described in section 26.9.2.2.1.1 of AF-CS-0102.000 shall apply with the following modification: − Designated transit list information is not applicable.
10.2.2.1.2
Actions in the Originating_connection_request state Actions in the Originating_connection_request state described in section 26.9.2.2.1.2 of AF-CS-0102.000 shall apply.
10.2.2.1.3
Actions in the Originating_connection_active state Actions in the Originating_connection_active state described in section 26.9.2.2.1.3 of AF-CS-0102.000 shall apply.
10.2.2.2
Actions at a Transit PINX Actions at a Transit PINX described in section 26.9.2.2.2 of AF-CS-0102.000 shall apply with the following modification: − Designated transit list information is not applicable. − Crankback is not applicable.
10.2.2.2.1
Actions in the Transit_connection_idle state Actions in the Transit_connection_idle state described in section 26.9.2.2.2.1 of AF-CS-0102.000 shall apply with the following modification: − Designated transit list information is not applicable. − Crankback is not applicable.
10.2.2.2.2
Actions in the Transit_connection_request state Actions in the Transit_connection_request state described in section 26.9.2.2.2.2 of AF-CS-0102.000 shall apply with the following modification: − Crankback is not applicable.
10.2.2.2.3
Actions in the Transit_connection_active state Actions in the Transit_connection_active state described in section 26.9.2.2.2.3 of AF-CS-0102.000 shall apply.
10.2.2.3
Actions at a Terminating PINX
10.2.2.3.1
Actions in the Incoming_connection_idle state Actions in the Incoming_connection_idle state described in section 26.9.2.2.3.1 of AF-CS-0102.000 shall apply.
10.2.2.3.2
Actions in the Incoming_connection_active state Actions in the Incoming_connection_active state described in section 26.9.2.2.3.2 of AF-CS-0102.000 shall apply.
10.2.3
GFT-Control procedures for CL-BI mode GFT-Control procedures for CL-BI mode described in section 26.9.2.3 of AF-CS-0102.000 shall apply.
- 9 -
10.2.3.1
Actions at a source PINX Actions at a source PINX described in section 26.9.2.3.1 of AF-CS-0102.000 shall apply with the following modification: − Designated transit list is not applicable.
10.2.3.2
Actions at a receiving PINX Actions at a receiving PINX described in section 26.9.2.3.2 of AF-CS-0102.000 shall apply with the following modification: − Designated transit list is not applicable.
10.2.3.3
Actions at a destination PINX Actions at a destination PINX described in section 26.9.2.3.3 of AF-CS-0102.000 shall apply.
10.3
Remote operations procedures
10.3.1
Introduction Introduction described in section 26.9.3.1 of AF-CS-0102.000 shall apply.
10.3.2
Procedures for operations Procedures for operations described in section 26.9.3.2 of AF-CS-0102.000 shall apply.
10.3.2.1
Invocation Invocation described in section 26.9.3.2.1 of AF-CS-0102.000 shall apply.
10.3.2.2
Return result Return result described in section 26.9.3.2.2 of AF-CS-0102.000 shall apply.
10.3.2.3
Return error Return error described in section 26.9.3.2.3 of AF-CS-0102.000 shall apply.
10.3.2.4
Reject Reject described in section 26.9.3.2.4 of AF-CS-0102.000 shall apply.
10.3.2.5
Formal definition of data types Formal definition of data types described in section 26.9.3.2.5 of AF-CS-0102.000 shall apply.
10.4
Notification transport mechanisms Notification transport mechanisms described in section 26.9.4 of AF-CS-0102.000 shall apply.
10.4.1
Sending notification information Sending notification information described in section 26.9.4.1 of AF-CS-0102.000 shall apply.
10.4.2
Receiving notification information Receiving notification information described in section 26.9.4.2 of AF-CS-0102.000 shall apply.
10.5
GFT-Control procedures for notifications
10.5.1
Actions at a PINX which generates notifications Actions at a PINX that generates notifications described in section 26.9.5.1 of AF-CS-0102.000 shall apply.
10.5.2
Actions at a receiving PINX Actions at a receiving PINX described in section 26.9.5.2 of AF-CS-0102.000 shall apply.
10.5.2.1
Actions at a Transit PINX Actions at a Transit PINX described in section 26.9.5.2.1 of AF-CS-0102.000 shall apply.
10.5.2.2
Actions at a Receiving End PINX Actions at a Receiving End PINX described in section 26.9.5.2.2 of AF-CS-0102.000 shall apply.
- 10 -
11
Interworking with (narrowband) QSIG Interworking with (narrowband) QSIG described in section 26.10 of AF-CS-0102.000 shall apply.
11.1
Full termination of generic functional protocol Full termination of generic functional protocol described in section 26.10.1 of AF-CS-0102.000 shall apply.
11.2
Generic interworking function
11.2.1
Architecture Architecture described in section 26.10.2.1 of AF-CS-0102.000 shall apply.
11.2.2
Bearer-related transport mechanism Bearer-related transport mechanism described in section 26.10.2.2 of AF-CS-0102.000 shall apply.
11.2.3
Connection-oriented bearer independent transport mechanism Connection-oriented bearer independent transport mechanism described in section 26.10.2.3 of AF-CS-0102.000 shall apply with the following modification: −
11.2.4
Other information elements are mapped as defined in ECMA-266 annex B.
Connectionless bearer independent transport mechanism Connectionless bearer independent transport mechanism described in section 26.10.2.4 of AF-CS-0102.000 shall apply.
12
Parameter values
12.1
Connection-oriented bearer-independent transport Connection-oriented bearer-independent transport described in section 26.11.1 of AF-CS-0102.000 shall apply.
13
Dynamic description (SDLs) Dynamic Description (SDL) described in ITU-T Rec. Q.2932.1 clause 13 shall apply.
13.1
Block overview diagram Block overview diagram described in ITU-T Rec. Q.2932.1 clause 13.1 shall apply with the following modification: − The processes Q.2931_U and Q.2931_N shall be replaced by a single process " ECMA-266 protocol control". This shall comprise the Protocol Control process specified in ECMA-266 enhanced as specified in 13.2.1.
13.2 13.2.1
Component transport mechanisms Bearer-related transport mechanism For bearer-related transport, the Protocol Control SDL of ECMA-266 shall be enhanced as specified in figure 1-10 of Q.2932.1 with the following modification: − All states are ECMA-266 protocol control states.
13.2.2
Connection-oriented bearer-independent transport mechanism Connection-oriented bearer-independent transport mechanism described in ITU-T Rec. Q.2932.1 clause 13.2.2 shall apply with the following modification: − In state 0 (Null), on receipt of a CO-BI SETUP message, a CALL PROCEEDING output symbol (to the right) shall be shown before the CO-BI-Setup.ind. output symbol. − In state 6 (Call Present), the branch beginning with the input symbol CO-BI Proceed.req shall not apply.
13.2.3
Connectionless bearer-independent transport mechanism Connectionless bearer-independent transport mechanism described in ITU-T Rec. Q.2932.1 clause 13.2.3 shall apply.
- 11 -
13.3
GFT-Control The SDL diagram for APDU aspects of GFT-Control is shown in following flows.
Legend
Signal from ROSE to GFT-control (note)
Signal from a Protocol entity to GFT-control
Signal from GFT-control to a Protocol entity
Signal from GFT-control to ROSE (note)
Ci
A
B
Task symbol
Calling macro
Decision symbol
Start of macro
Connector number i
Exit from macro
Connector(s)
Implementation symbol
State symbol
Save
FIE = Facility Information Element Note: These signals are sent via the coordination function
- 12 -
SDL for GFT-control for the transport of APDUs
Pending
GF-Data Request
NO
NO
YES
is APDU response to previous FIE ?
YES
handle Interpretation APDU Normal
C1
APDUDiscard
do not include NFE in n-Data request to protocol entity
C3
C2
(see next page)
Link significance, or request for CLBI transport
set NFE destination to previously received source CLBI-transport requested ?
YES
NO
is this PINX a Transit PINX ?
NO CLBI-Data request
YES
C3 set NFE source entity ‘AnyTypeOfPINX’ and include PINX address
set NFE source entity ‘EndPINX’ and don’t include PINX address
YES
bearer related transport requested ?
NO (note 1)
BR-Data request
(note 2)
COBI-Data request
Pending
Note 1: Such information can be synchronized with bearer-realated messages within the co-ordination process. Such synchronization is implementation dependent, and therefore not shown in this SDL. Note 2: If appropriate, data can also be sent in the COBI-setup request, COBI-setup response and COBI-release reqeuest primitives. It is an implementation dependent matter and is outside the scope of this standard as to when the COBI process is established.
- 13 -
SDL for GFT-control for the transport of APDUs
(see previous page)
NO
C1
is a specific destination required ?
YES
specific PINX required ?
END PINX
EXPLICITLY ADDRESSED PINX set NFE destination entity = anuTypeOfPINX with PINX address
set NFE destination entity = anyTypeOfPINX with no PINX address
(see previous page)
C2
set NFE destination entity = anyTypeOfPINX with no PINX address
- 14 -
SDL for GFT-control for the transport of APDUs
Pending
note 1, 4
note 1, 3 BR-Data ind.
note 1 CLBI-Data ind.
COBI-Data ind.
PASS ON
determine destination
PROCESS
DISCARD
YES BR-Data ?
NO note 2 BR-Data request
note 2 COBI-Data request
discard entire received FIE
GF-Data ind.
Pending
Note 1: This primitive indicates that the Protocol entity has received a Facility information element from an Adjacent PINX. Note 2: This primitive to the Protocol entity causes a Facility information element to be sent to the Next PINX in the direction of the Destination PINX. Note 3: Such information can be synchronized with bearer-realated messages within the coordination process. The mechanism for separating this information is performed by the coordination process. Note 4: Such information can also appear in the COBI-setup indication, COBI-setup confirm and COBI-release indication primitives. As the time of establishment/release of the COBI transfer mechanism is outside the scope of this standard, this SDL does not provide this in detail.
- 15 -
SDL for GFT-control for the transport of APDUs
determine destination
NO
is NFE included in FIE ?
YES C
YES
more than one FIE ?
discard all NFEs except first
NO
D
NO
is NFE structure correct ?
YES TRANSIT
ANY PINX
END PINX or value 2 - 11 (note 1)
NFE destination =?
END
entity of receiving PINX ?
OTHER
OTHER
NFE destination =?
EndPINX or value 2 - 11 (note 2)
D
D destination address included ?
YES
does PINX wish to intercept ?
NO
B
is destination address included?
YES
NO
NO does destination address match ?
YES does PINX understand and wish to be destination ?
YES
NO does destination address match ?
ANY PINX
B
YES
YES C
NO
save Interpretation APDU, if present Pass on
Process
Note 1: Values 2 to 11 are reserved for future use (see subclause 10.2.1.2.2) Note 2: Values 2 to 11 are reserved for future use (see subclause 10.2.1.2.1)
Discard
NO
- 16 -
SDL for GFT-control for the transport of APDUs
Handle Interpretation APDU
NO
does generic functional data contain any RejectAPDU with problem code Invoke Problem ?
YES
NORMAL
NO is there a saved Interpretation APDU ?
YES NORMAL YES
instruction to Discard ?
NO
discard these Reject APDUs
NO
instruction to clear call/ connection ?
YES
YES
any more APDUs to be sent?
initiate clearing of call/connection
NO
NORMAL
APDU-DISCARD
NORMAL
- 17 -
14
Manufacturer Specific Information (MSI) B-QSIG permits the inclusion in messages of non-standardised information which is specific to a particular design of PINX or a particular network etc. This information is known as Manufacturer Specific Information (MSI). Manufacturer specific information may exist in the PISN as a result of the following: − manufacturer specific Supplementary services; − manufacturer specific extensions to Standard Supplementary services; or − manufacturer specific notifications In all these cases, any information which is manufacturer specific shall be encoded in such a way that it can be uniquely identified. Apart from the use of information elements belonging to codesets 6 or 7, as described in ECMA-266 for conveyance of MSI to an Adjacent PINX, any manufacturer specific information generated by a PINX conforming to this International Standard shall be encoded in conformance with the contents of this clause.
14.1
Manufacturer specific operations and errors Manufacturer specific operations and errors described in section 26.12.1 of AF-CS-0102.000 shall apply.
14.2
Manufacturer specific additions to standardised operations and error Manufacturer specific additions to standardised operations and error described in section 26.12.2 of AF-CS-0102.000 shall apply.
14.3
Manufacturer specific notifications Manufacturer specific notifications described in section 26.12.3 of AF-CS-0102.000 shall apply.
- 18 -
- 19 -
Annex A (normative)
Protocol Implementation Conformance Statement (PICS) proforma
Protocol Implementation Conformance Statement (PICS) proforma described in section 30 of AF-CS-0102.000 shall apply.
- 20 -
- 21 -
Annex B (normative)
Formal definition of data types using ITU-T Rec. X.208
This annex provides the ASN.1 modules defined for the purpose of this Standard.
B.1
ROSE APDU types ROSE APDU types described in section 27.1 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Remote-Operations-Apdus { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) remote-operations-apdus(1) }
B.2
Definition of embedded B-QSIG information elements Table B-2 contains the ASN.1 definition of a general applicable type used to include B-QSIG information elements in ASN.1 definitions. The B-QSIG information elements to be used shall be indicated as comment at the point where the type BqsigInformationElement is used. Table B-2 - Definition of embedded B-QSIG information elements
Bqsig-generic-parameter-definition {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) bqsig-generic-parameters(2) } DEFINITIONS EXPLICIT TAGS ::= BEGIN EXPORTS BqsigInformationElement; BqsigInformationElement ::= [APPLICATION 0] END
-- of Bqsig-generic-parameter-definition
B.3
Network facility extension
IMPLICIT
OCTET STRING
Network facility extension described in section 27.3 of AF-CS-0102.000 shall apply with the following modification: The module name shall be Network-Facility-Extension {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) network-facility-extension( 3) }
- 22 -
B.4
NOTIFICATION macro and notification for conveying embedded B-QSIG information elements NOTIFICATION macro and notification for conveying embedded B-QSIG information elements described in section 27.4 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Notification-macro {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) notification-macro (4) }
B.5
Addressing information definition Addressing information definition described in section 27.5 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Addressing-Data-Elements {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) addressing-data-elements (15) }
B.6
Interpretation APDU Interpretation APDU described in section 27.6 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Interpretation-Apdu { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) interpretation-apdu (6) }
B.7
Notification Data Structure Notification Data Structure described in section 27.7 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Notification-Data-Structure iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) notification-data-structure (7) }
B.8
EXTENSION macro and Extension data type EXTENSION macro and Extension data type described in section 27.8 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Manufacturer-specific-service-extension-definition { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) msi-definition (8) }
- 23 -
Annex C (normative)
Formal definition of data types using ITU-T Rec. X.680
This annex provides the ASN.1 modules defined for the purpose of this Standard.
C.1
APDU types APDU types described in section 28.1 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Revised-Remote-Operations-Apdus { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) revised-remote-operations-apdus(11) }
C.2
Definition of embedded B-QSIG information elements Table C-2 contains the ASN.1 definition of a general applicable type used to include B-QSIG information elements in ASN.1 definitions. The B-QSIG information elements to be used shall be indicated as comment at the point where the type BqsigInformationElement is used.
Table C-2 - Definition of embedded B-QSIG information elements Bqsig-generic-parameter-definition {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) bqsig-generic-parameters(12) } DEFINITIONS EXPLICIT TAGS ::= BEGIN EXPORTS BqsigInformationElement; BqsigInformationElement ::= [APPLICATION 0] IMPLICIT OCTET STRING END -- of Bqsig-generic-parameter-definition
C.3
Network facility extension Network facility extension described in section 28.3 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Network-Facility-Extension {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) network-facility-extension(13) }
- 24 -
C.4
NOTIFICATION object class and notification for conveying embedded B-QSIG information elements NOTIFICATION object class and notification for conveying embedded B-QSIG information elements described in section 28.4 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Notification-object-class {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) notification-object-class (14) }
C.5
Addressing information definition Addressing information definition described in section 28.5 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Addressing-Data-Elements {iso(1) identified-organisation(3) icd-ecma(0012) standard (0) bqsig-generic-procedures (254) addressing-data-elements (15) }
C.6
Interpretation APDU Interpretation APDU described in section 28.6 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Interpretation-Apdu { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) interpretation-apdu (16) }
C.7
Notification Data Structure Notification Data Structure described in section 28.7 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Notification-Data-Structure { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) notification-data-structure (17) }
C.8
EXTENSION macro and Extension data type EXTENSION macro and Extension data type described in section 28.8 of AF-CS-0102.000 shall apply with the following modification: The module name shall be
Manufacturer-specific-service-extension-definition { iso(1) identified-organisation(3) icd-ecma(0012) standard(0) bqsig-generic-procedures (254) msi-definition (18) }
- 25 -
Annex D (informative)
Information flows
Information flows described in section 31 of AF-CS-0102.000 shall apply.
- 26 -
- 27 -
Annex E (informative)
Instruction indicators
Instruction indicators described in section 32 of AF-CS-0102.000 shall apply.
- 28 -
- 29 -
Annex F (informative)
Formal definitions of remote operations notation using ITU-T Rec. X.208
Formal definitions of remote operations notation described in section 33 of AF-CS-0102.000 shall apply.
- 30 -
- 31 -
Annex G (informative)
Formal definitions of remote operations notation using ITU-T Rec. X.680
Formal definitions of remote operations notation using ITU-T Rec. X.680 described in section 34 of AF-CS-0102.000 shall apply.
- 32 -
- 33 -
Annex H (informative)
Examples of the use of Manufacturer Specific Information
Examples of the use of Manufacturer Specific Information described in section 35 of AF-CS-0102.000 shall apply.
- 34 -
- 35 -
Annex I (informative)
Remote operations protocol
Remote operations protocol described in section 36 of AF-CS-0102.000 shall apply.
- 36 -
- 37 -
Annex J (informative)
Problem code definitions
Problem code definitions described in section 37 of AF-CS-0102.000 shall apply.
.
.
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.