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

《ECMA296-1999 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) - Digital Subscriber Signalling System No Two (DSS2) .pdf》由会员分享，可在线阅读，更多相关《ECMA296-1999 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) - Digital Subscriber Signalling System No Two (DSS2) .pdf（34页珍藏版）》请在麦多课文档分享上搜索。

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

2、l SubscriberSignalling System No. two (DSS2),Broadband Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Prenegotiation - Part 1:Protocol SpecificationStandard ECMA-296December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01

3、- URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-296.DOC 03-01-00 12,19Broadband Integrated Services DigitalNetwork (B-ISDN) and BroadbandPrivate Integrated Services Network(B-PISN) - Digital SubscriberSignalling System No. two (DSS2),Broadband Inter-Exchange Signalling(B-QSIG), and Signa

4、lling System No. 7(SS7) - Prenegotiation - Part 1:Protocol SpecificationBrief HistoryThis Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to BroadbandPrivate Integrated Services Networks (B-PISNs). The series uses B-ISDN concepts as developed by IT

5、U-T and conforms tothe framework of International Standards for Open Systems Interconnection as defined by ISO/IEC.This Standard has been produced by ECMA TC32-TG15 in collaboration with ETSI Technical Committee SignallingProtocols and Switching (SPS) under ETSI work item DEN/SPS-05131-1.The Standar

6、d is part 1 of a multi-part standard covering the Digital Subscriber Signalling System No. 2 (DSS2), BroadbandInter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) protocol specification for Broadband IntegratedServices Digital Network (B-ISDN) and Broadband Private Integrated Servic

7、es Network (B-PISN) Prenegotiation, asdescribed below:Part 1: “Protocol specification“;Part 2: “Protocol Implementation Conformance Statement (PICS) proforma specification“;Part 3: “Test Suite Structure and Test Purposes (TSSPart 4: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtr

8、a Information for Testing (PIXIT) proformaspecification“.Part 3 and part 4 will only be produced by ETSI as EN 302 091-3 and EN 302 091-4 respectively.The Standard is based upon the practical experience of ECMA member companies and the results of their active andcontinuous participation in the work

9、of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardizationbodies. It represents a pragmatic and widely based consensus.This ECMA Standard is technically aligned with EN 302 091-1 published by ETSI in November 1999.This Standard has been adopted by the ECMA General Assembly of

10、December 1999.- i -Table of contents1Scope 12 References 13 Definitions 23.1 External definitions 23.2 Additional definitions 23.2.1 Prenegotiation 24 Abbreviations 25 Description 25.1 Overview 25.2 Protocol model for PRN 36 Operational requirements 47 Primitive definitions and state definitions 47.

11、1 Service primitives 47.2 PRN states 47.2.1 PRN Idle 47.2.2 PRN Initiated 47.2.3 PRN Delivered 47.2.4 PRN Present 47.2.5 PRN Received 48 Coding requirements 48.1 Abstract definition of the PRN operations 49 PRN procedures 69.1 General 69.2 Procedures at an originating or terminating CC entity 69.2.1

12、 Invoking the PRN operation by the initiating CC entity 69.2.2 Responding to the PRN invocation 89.2.3 Completion of PRN 99.2.4 Error handling 109.2.5 Crossing of bearer establishment messages with prenegotiation-related APDUs 109.3 Procedures at a transit CC entity 1010 Interactions 1011 Interworki

13、ng with networks not supporting PRN 1011.1 Calls from other networks to a network supporting PRN 1011.2 Calls to other networks not supporting PRN 10- ii -12 SDL Diagrams 10Annex A - Information flow diagrams 17Annex B - Object identifiers defined in this Standard 19Annex C - Bibliography 211ScopeTh

14、is Standard specifies the signalling protocol for the purpose of prenegotiation at the QB, SB,TBand co-incidentSB/TBreference points within, between and at the access to Broadband Private Integrated Services Networks andwithin, between and at the access to public European Broadband Integrated Servic

15、es Digital Networks. The protocoloperates between two adjacent call control entities. The protocol is applicable in a separated call and bearer(connection) control environment for the support of calls having none, one or multiple bearers. The protocol isapplicable to a two-party call or a multi-part

16、y call. However, prenegotiation is performed between two parties. In caseof multi-party connections (point-to-multipoint connections), prenegotiation may be performed between the root andthe first party.The QBreference point is defined in ISO/IEC 11579-1. The SBand TBreference points are defined inI

17、TU-T Rec. I.327.This Standard is based on the transport capabilities as defined in ETS 300 796-1 and ECMA-254, and is closelyrelated to the call control protocol specification as defined in ECMA-294.The purpose of prenegotiation as specified in this Standard is to allow a user to check compatibility

18、 and availability atthe remote user with regard to one or more connections the user intends to establish during the lifetime of the call,without reserving connection-oriented resources in the network. Reservation of connection-oriented resources at theremote user is outside the scope of this Standar

19、d.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of thisStandard. References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific. For a specific reference, subsequent revisio

20、ns 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 samenumber.ECMA-254 Broadband Private Integrated Services Network (B-PISN) - Inter-Exchange Signalling Protocol -Ge

21、neric Functional Protocol (B-QSIG-GF)ECMA-294 Broadband Integrated Services Digital Network (B-ISDN) and Broadband Private IntegratedServices Network (B-PISN) - Digital Subscriber Signalling System No. two (DSS2), BroadbandInter-Exchange Signalling (B-QSIG), and Signalling System No. 7 (SS7) - Call

22、Control in aSeparated Call and Bearer Control Environment - Part 1: Protocol SpecificationISO/IEC 11579-1 Information technology - Telecommunications and information exchange between systems -Private integrated services network - Part 1: Reference configuration for PISN Exchanges(PINX)ISO/IEC 13247

23、Information technology - Telecommunications and information exchange between systems -Broadband Private Integrated Services Network - Inter-exchange signalling protocol - Basiccall/connection controlEN 300 443-1 Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling Sy

24、stemNo. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basiccall/bearer control; Part 1: Protocol specification ITU-T Rec. Q.2931 (1995), modifiedETS 300 796-1 Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling SystemNo. two (DSS2) pro

25、tocol; Generic functional protocol; Core aspects; Part 1: Protocolspecification ITU-T Rec. Q.2932.1 (1996), modifiedEN 302 093-1 Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling SystemNo. two (DSS2) protocol; Point-to-point multiconnection bearer control specific

26、ation in aseparated call and bearer environment; Part 1: Protocol specification- 2 -ITU-T Rec. I.327 B-ISDN functional architectureITU-T Rec. X.680 Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notationITU-T Rec. X.690 Information technology - ASN.1 encoding r

27、ules: Specification of Basic Encoding Rules (BER),Canonical Encoding Rues (CER) and Distinguished Encoding Rules (DER)ITU-T Rec. X.880 Information technology - Remote operations: concepts, model and notationCCITT Rec. Z.100 CCITT specification and description language (SDL)3 Definitions3.1 External

28、definitionsThe definitions used in ECMA-254, ECMA-294, ISO/IEC 13247, EN 300 443-1 and ETS 300 796-1 apply.3.2 Additional definitionsFor the purposes of this Standard the following additional definitions apply.3.2.1 PrenegotiationThe user action of checking compatibility and availability at the remo

29、te user with regard to one or more bearerconnections the user intends to establish during the lifetime of the call, without already reserving bearerconnection-oriented resources in the network.4 AbbreviationsFor the purposes of this Standard, the abbreviations used in ECMA-254, ECMA-294, ISO/IEC 132

30、47, EN 300 443-1,ETS 300 796-1, and EN 302 093-1 apply. In addition, the following abbreviations are used:CC Call Controlmp modification possible (9.2.1.3, figure 2)PRN PrenegotiationT/F True/False (9.2.1.3, figure 2)UM User Mandatory (9.2.1.3, figure 2)UO User Optional (9.2.1.3, figure 2)5 Descript

31、ion5.1 OverviewThis Standard specifies the procedures, messages, information elements and components needed for the support ofPrenegotiation (PRN).PRN is an optional procedure which may be invoked by either the calling or called user at either the SBor the co-incident SB/TBreference point. In both c

32、ases, it can only be invoked in conjunction with or after call establishment.PRN does not establish connections.PRN is performed between two users. In case of point-to-multipoint connections, it may be performed between theroot and the first party.The PRN protocol operates between two adjacent call

33、control entities (points of call and bearer co-ordination).It is not required that the network interprets and processes the contents of the PRN operation, except that incomingcall segment identifier and bearer identifiers have to be mapped to the corresponding values on the outgoing side.The network

34、 may either relay the related information, or call control entities in the network(s) may also be involvedin looking at various parameters of network relevance and may take action/possibly intervene in the PRNprocedure. Possible actions/interventions of network nodes based on the interpretation of t

35、he contents of the PRNoperation are outside the scope of this Standard.In general, all connection related parameters for any number of connections can be prenegotiated.- 3 -The purpose of PRN is to check compatibility and availability between the users without already reservingconnection-related res

36、ources in the network. The response of a user to a PRN request may be:- positive, if a user is fully compatible with the parameters proposed by the remote party - in this case, theconnections may be established with the parameters as proposed by the remote party;- positive, if a user is not fully co

37、mpatible with the parameters proposed by the remote party, but supports acompatible alternative/subset - in this case, the connections may be established with those parameters whichwere proposed as an alternative;- negative, if a user is not compatible with the parameters proposed by the remote part

38、y;- negative, if a user is compatible with the parameters proposed by the remote party, but the negotiatedresources are currently unavailable.NOTEIf PRN is performed in combination with Call Establishment i.e. if no connections are existing/pending, the callmight be released if the result of the PRN

39、 is negative.The PRN procedures allow a user to return either only one or several alternative acceptable parameter sets perconnection.5.2 Protocol model for PRNFor PRN, the basic protocol model outlined in figure 1-1 of ETS 300 796-1 applies. Figure 1 shows how PRN fitsinto this basic model. It shou

40、ld be noted that figure 1 only shows those ASEs which are directly related to PRN.PrenegotiationCall ControlROSEGFT-ControlTransport mech.CoordinationfunctionTelecommunication serviceapplicationSAALe.g. CO-BI(separated)Figure 1 - PRN within the B-QSIG/DSS2 protocol model- 4 -6 Operational requiremen

41、tsPRN may be used within an environment of multiconnection calls. In such an environment, no specific operationalrequirements exist, and PRN may be invoked according to the procedures of subclause 9.2.1.PRN is based on the transport capabilities as defined in ETS 300 796-1 and ECMA-254, and on the c

42、all establishmentprocedures as defined in ECMA-294.7 Primitive definitions and state definitions7.1 Service primitivesThe following services for PRN are defined:Prenegotiate confirmedPrenegotiation-Alert unconfirmedError indication7.2 PRN statesFor the purpose of PRN the following additional states

43、exist in a Call Control entity (CC entity).7.2.1 PRN IdleNo PRN procedure invoked.7.2.2 PRN InitiatedThis state exists at a preceding CC entity when a request for PRN has been sent to the succeeding CC entity butno response has been received.7.2.3 PRN DeliveredThis state exists at a preceding CC ent

44、ity when it has received an indication that PRN alerting has been initiated.7.2.4 PRN PresentThis state exists at a succeeding CC entity that has not yet responded to a received request for PRN.7.2.5 PRN ReceivedThis state exists at a succeeding CC entity when PRN alerting has been initiated but the

45、 PRN request has not yetbeen answered.8 Coding requirements8.1 Abstract definition of the PRN operationsTable 1 shows the definition of the operations, errors and types required for PRN using ASN.1 as defined inITU-T Rec. X.680 and using the OPERATION and ERROR object classes as defined in ITU-T Rec

46、. X.880.APDUs based on these operations shall be of types invoke, returnResult, returnError and reject as defined intable B.1 of ETS 300 796-1. The Basic Encoding Rules (BER) as defined in ITU-T Rec. X.690 shall be applied tothe encoding of APDUs based on these operations and errors.Table 1 - PRN op

47、erations and errorsPrenegotiation-Operations-and-Errorsitu-t recommendation q 2984 prenegotiation-operations-and-errors (1)DEFINITIONS AUTOMATIC TAGS :=BEGINEXPORTS preNegotiate, PrenegotiationProposal, prenegotiationAlert;IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objectsjoint-iso-

48、itu-t remote-operations(4) informationObjects(5) version1(0)CallSegmentId FROM CC-Operationsitu-t recommendation q 2981 cc-operations (1)BearerId FROM Call-Object-Class-Definitionsitu-t recommendation q 2981 call-object-class-definitions (5);PrenegotiationOperations OPERATION := preNegotiate | prene

49、gotiationAlert - 5 -preNegotiationOperationsDefinitions OBJECT IDENTIFIER := itu-t recommendation q 2984 prenegotiation-operations-definitions (2)preNegotiate OPERATION :=ARGUMENT SEQUENCE prenegotiationProposal PrenegotiationProposal,callAssociation CHOICE callSegmentId CallSegmentId,callId CallIdValue RESULT SEQUENCE prenegotiationProposal PrenegotiationProposal,callAssociation CHOICE callSegmentId CallSegmentId,callId CallIdValue RETURN RESULT TRUEERRORS prenegotiateErrorSimple | prenegotiateErrorItemised SYNCHRONOUS FALSEALWAYS RESPONDS TRUEC