1、Standard ECMA-2542nd Edition - December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chBroadband Private Integrated ServicesNetwork (B-PISN) -Inter-Exchange Signalling Protocol -Generic Functi
2、onal ProtocolStandard ECMA-2542nd Edition - December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-254.DOC 13-06-01 08,57Broadband Private Integrated ServicesNetwork (B-PISN) -Inter-E
3、xchange Signalling Protocol -Generic Functional Protocol(B-QSIG-GF)Brief HistoryThis Standard is one of a series of ECMA standards defining services and signalling protocols applicable to Broadband PrivateIntegrated Services Networks. The series uses the B-ISDN concepts as developed by ITU-T (former
4、ly CCITT) and is alsowithin the framework of standards for open systems interconnection as defined by ISO.This Standard is based upon ATM Forums specification AF-CS-0102.000 with modification indicated in the text of thisStandard.This Standard specifies the signalling protocol for use at the Q refer
5、ence 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 andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardisationbodies. It re
6、presents 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/IECInternational Standard.Adopted as 2nd Edition of Standard ECMA-254 by the General Assembly of December 1999.List of corrected errata
7、 for ECMA-2545 June 2001SummaryFollowing is a summary of the errors detected and corrected in Standard ECMA-254, Broadband Private IntegratedServices Network (B-PISN) - Inter-Exchange Signalling Protocol - Generic Functional Protocol.Clause 1 Scope, paragraph 1 and clause 5 AbbreviationsThe abbrevia
8、tion “PINX” is wrong in both clause 1 and clause 5 it should be changed to “Private Integrated servicesNetwork eXchange”Clause 1 Scope, paragraph 1Corrected:This Standard specifies the functional protocol for the support of supplementary services and additional basic callcapabilities at the Q-refere
9、nce point. The Q-reference point exists between Private Integrated services NetworkeXchanges (PINX) connected together within a Private Integrated Services Network (PISN) and is defined inISO/IEC 11579-1. The generic functional protocol is part of the B-QSIG signalling system.Original:This Standard
10、specifies the functional protocol for the support of supplementary services and additional basic callcapabilities 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 d
11、efined in ISO/IEC 11579-1.The generic functional protocol is part of the B-QSIG signalling system.Clause 5 Abbreviations, paragraph 9Corrected:PINX Private Integrated services Network eXchangeOriginal:PINX Private Integrated Network ExchangeClause 3 References (normative)References contained in sect
12、ion 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 DefinitionsDefinitions contained in sect
13、ion 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 architectureProtocol Archit
14、ecture 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 m
15、odifications:Clause 10.2.3.1 Actions at a source nodeThe title should be Actions at a source PINX. Also the word node in the first paragraph of this section should bechanged to PINX.Corrected:10.2.3.1 Actions at a source PINXActions at a source PINX described in section 26.9.2.3.1 of AF-CS-0102.000
16、shall apply with the followingmodifications:Proposal: Original:10.2.3.1 Actions at a source nodeActions at a source node described in section 26.9.2.3.1 of AF-CS-0102.000 shall apply with the followingmodifications:Clause 10.2.3.2 Actions at a receiving nodeThe title should be Actions at a receiving
17、 PINX. Also the word node in the first paragraph of this section should bechanged to PINX.Corrected:10.2.3.2 Actions at a receiving PINXActions at a receiving PINX described in section 26.9.2.3.2 of AF-CS-0102.000 shall apply with the followingmodifications:Original:10.2.3.2 Actions at a receiving n
18、odeActions at a receiving node described in section 26.9.2.3.2 of AF-CS-0102.000 shall apply with the followingmodifications:Clause 10.2.3.3 Actions at a destination nodeThe title should be Actions at a destination PINX. Also the word node in the first paragraph of this section shouldbe changed to P
19、INX.Corrected:10.2.3.3 Actions at a destination PINXActions 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 nodeActions at a destination node described in section 26.9.2.3.3 of AF-CS-0102.000 shall apply.- i -Table of con
20、tents1Scope 12 Conformance 13 References (normative) 14 Definitions 14.1 Gateway PINX 14.2 Inter-PINX link (IPL) 14.3 Preceding side 14.4 Private Integrated services Network eXchange (PINX) 24.5 Succeeding side 25 Abbreviations 26 Description 26.1 Overview 26.2 Addressing mechanisms 26.2.1 Explicit
21、addressing 26.2.2 Functional addressing 26.3 Protocol architecture 36.4 Services provided by individual protocol entities 36.4.1 Services provided by ROSE 36.4.2 Services provided by GFT-control 36.4.3 Services provided by bearer-related transport 36.4.4 Services provided by connectionless bearer-in
22、dependent transport 36.4.5 Services provided by connection-oriented bearer-independent transport 37 Operational requirements 38 Primitive definitions and state definitions 38.1 Primitive definitions 38.2 State definitions 38.2.1 APDU transport mechanisms 38.2.2 GFT-Control 39 Coding requirements 49.
23、1 Message functional definitions and content 49.1.1 Additional messages for bearer-related transactions 49.1.2 Messages for connectionless bearer-independent transport 49.1.3 Messages for connection-oriented bearer-independent transport 49.2 General message format and information element coding 59.2
24、.1 Message type 59.2.2 Other information elements 5- ii -9.2.3 Encoding of information described using ASN.1 510 Signalling procedures 510.1 APDU transport mechanisms 510.1.1 Bearer-related transport 610.1.2 Bearer-independent transport mechanisms 610.1.3 Connection-oriented bearer-independent trans
25、port mechanism 610.1.4 Connectionless bearer-independent transport mechanism 710.2 GFT-Control procedures for APDUs 710.2.1 GFT-control procedures for transport of APDUs 710.2.2 GFT-Control procedures for CO-BI connection control 810.2.3 GFT-Control procedures for CL-BI mode 810.3 Remote operations
26、procedures 910.3.1 Introduction 910.3.2 Procedures for operations 910.4 Notification transport mechanisms 910.4.1 Sending notification information 910.4.2 Receiving notification information 910.5 GFT-Control procedures for notifications 910.5.1 Actions at a PINX which generates notifications 910.5.2
27、 Actions at a receiving PINX 911 Interworking with (narrowband) QSIG 1011.1 Full termination of generic functional protocol 1011.2 Generic interworking function 1011.2.1 Architecture 1011.2.2 Bearer-related transport mechanism 1011.2.3 Connection-oriented bearer independent transport mechanism 1011.
28、2.4 Connectionless bearer independent transport mechanism 1012 Parameter values 1012.1 Connection-oriented bearer-independent transport 1013 Dynamic description (SDLs) 1013.1 Block overview diagram 1013.2 Component transport mechanisms 1013.2.1 Bearer-related transport mechanism 1013.2.2 Connection-
29、oriented bearer-independent transport mechanism 1013.2.3 Connectionless bearer-independent transport mechanism 1013.3 GFT-Control 1114 Manufacturer Specific Information (MSI) 1714.1 Manufacturer specific operations and errors 1714.2 Manufacturer specific additions to standardised operations and erro
30、r 1714.3 Manufacturer specific notifications 17- iii -Annex A - Protocol Implementation Conformance Statement (PICS) proforma 19Annex B - Formal definition of data types using ITU-T Rec. X.208 21Annex C - Formal definition of data types using ITU-T Rec. X.680 23Annex D - Information flows 25Annex E
31、- Instruction indicators 27Annex F - Formal definitions of remote operations notation using ITU-T Rec. X.208 29Annex G - Formal definitions of remote operations notation using ITU-T Rec. X.680 31Annex H - Examples of the use of Manufacturer Specific Information 33Annex I - Remote operations protocol
32、 35Annex J - Problem code definitions 37- iv -.1ScopeThis Standard specifies the functional protocol for the support of supplementary services and additional basic callcapabilities at the Q-reference point. The Q-reference point exists between Private Integrated services NetworkeXchanges (PINX) conn
33、ected together within a Private Integrated Services Network (PISN) and is defined inISO/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) oroutside the co
34、ntext of any bearer connection (bearer-independent).The application of this Standard to individualadditional basic call capabilities and supplementary services is outside the scope of this Standard and should bedefined in those standards or proprietary specifications that specify the individual capa
35、bilities.All conformance to this Standard is based on the external behaviour at the interface at the Q-reference point, i.e. onthe 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
36、AF-CS-0102.000, which itself is based on theDSS2 generic functional protocol specified in ITU-T Rec. Q.2932.1 but extended to allow non-local informationexchange as well as local information exchange.This Standard is applicable to PINXs supporting additional basic call capabilities and/or supplement
37、ary servicesrequiring the functional protocol for signalling at the Q-reference point.2 ConformanceIn order to conform to this Standard, a PINX shall satisfy the requirements identified in the Protocol ImplementationConformance Statement (PICS) proforma in section 30 of AF-CS-0102.000.3 References (
38、normative)AF-CS-0102.000 PNNI Addendum on PNNI/B-QSIG Interworking and Generic Functional Protocol for theSupport of Supplementary ServicesReferences contained in section 26.2 of AF-CS-0102.000 shall apply with the following additions:ECMA-265 Broadband Private Integrated Services Network (B-PISN) -
39、 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 Informa
40、tion technology - Telecommunications and information exchange between systems -Private Integrated Services Network - Part 1: Reference configuration for PISN exchanges(PINX) (1994)4 DefinitionsDefinitions contained in section 26.3 of AF-CS-0102.000 shall apply with the following additions:4.1 Gatewa
41、y PINXThe definition in ECMA-266 shall apply. Dependent on the capabilities of the signalling system being interworkedby 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 oth
42、er signalling system, perhaps embedded insome other protocol unit, or process the APDUs and perform an interworking function of the information flows andencoding of the Supplementary service concerned.4.2 Inter-PINX link (IPL)The definition in ECMA-266 shall apply.4.3 Preceding sideIn the context of
43、 a call/connection or a CO-BI connection using an IPL, the side that initiates call/connection orCO-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 sideIn the context of a
44、call/connection or a CO-BI connection using an IPL, the opposite side from the side that initiatescall/connection or CO-BI connection establishment over that IPL (see figure 1 in ECMA-266).NOTEThe 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 t
45、erm B-QSIG.5 AbbreviationsAbbreviations contained in section 26.4 of AF-CS-0102.000 shall apply with the following additions:APDU Application Protocol Data UnitCL-BI Connectionless Bearer IndependentCO-BI Connection Oriented Bearer IndependentIPL Inter-PINX LinkIPVCI Inter-PINX Virtual Channel Ident
46、ifierIPVPI Inter-PINX Virtual Path IdentifierPISN Private Integrated Services NetworkPINX Private Integrated services Network eXchangeROSE Remote Operation Service ElementVCI Virtual Channel IdentifierVPI Virtual Path Identifier6 Description6.1 OverviewThe generic functional protocol provides a mean
47、s of exchanging ROSE APDUs on behalf of Application ServiceControl entities located in different PINXs. These Application Service Control entities may be for the support ofsupplementary services or additional basic call capabilities. This exchange may take place either in association witha bearer es
48、tablished using the procedures of ECMA-266 or independently of any bearer. Bearer independenttransport can either be connection-oriented or connectionless. In the case of connection-oriented bearer-independent transport, establishment and release of the connection is specified in this Standard.For b
49、earer-related transport and connection-oriented bearer-independent transport, the exchange of ROSE APDUscan be between any of two PINXs involved in the connection, as determined by addressing information transportedwith the APDUs (e.g., between the two End PINXs). For connectionless bearer independent transport, theexchange of ROSE APDUs is between the source PINX and the destination PINX for the transporting message.6.2 Addressing mechanismsAddressing mechanisms described in section 26.5.2 of AF-CS-0102.000 shall apply.6.2.1 Explicit addressingExplici
