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

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

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

2、l SubscriberSignalling System No. two (DSS2),Broadband Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Call Control in a Separated Calland Bearer Control Environment -Part 1: Protocol SpecificationStandard ECMA-294December 1999Standardizing Information and Communication Systems

3、Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-294.DOC 06-01-00 09,01Broadband Integrated Services DigitalNetwork (B-ISDN) and BroadbandPrivate Integrated Services Network(B-PISN) - Digital SubscriberSignalling System No. two (DSS2),Broadb

4、and Inter-Exchange Signalling(B-QSIG), and Signalling System No. 7(SS7) - Call Control in a Separated Calland Bearer Control Environment -Part 1: Protocol SpecificationBrief HistoryThis Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to BroadbandPr

5、ivate Integrated Services Networks (B-PISNs). The series uses B-ISDN concepts as developed by ITU-T and conforms tothe framework of International Standards for Open Systems Interconnection as defined by ISO/IEC.This Standard has been produced by ECMA TC32-TG15 in collaboration with ETSI Technical Co

6、mmittee SignallingProtocols and Switching (SPS) under ETSI work item DEN/SPS-05132-1.The Standard 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 f

7、or the Broadband IntegratedServices Digital Network (B-ISDN) and Broadband Private Integrated Services Network (B-PISN) Call Control, as describedbelow:Part 1: “Protocol specification“;Part 2: “Protocol Implementation Conformance Statement (PICS) proforma specification“;Part 3: “Test Suite Structure

8、 and Test Purposes (TSSPart 4: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proformaspecification“.Part 3 and part 4 will only be produced by ETSI as EN 302 092-3 and EN 302 092-4 respectively.The Standard is based upon the practical experience

9、 of ECMA member companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardizationbodies. It represents a pragmatic and widely based consensus.This ECMA Standard is technically aligned with EN 302 092-1

10、published by ETSI in November 1999.This Standard has been adopted by the ECMA General Assembly of December 1999.- i -Table of contents1Scope 12 References 13 Definitions 13.1 Adjacent call control entities (adjacent CC entities) 13.2 Bearer 23.3 Bearer control 23.4 Bearer control entity (BC entity)

11、23.5 Call 23.6 Call control 23.7 Call control entity (CC entity) 23.8 Call control signalling service provider 23.9 Call control signalling service user 23.10 Call segment 23.11 Called party 23.12 Calling party 23.13 Information model 23.14 Originating CC entity 23.15 Party 23.16 Preceding CC entity

12、 23.17 Succeeding CC entity 23.18 Terminating CC entity 33.19 Transit CC entity 34 Abbreviations 35Basic model 35.1 Separation of Call Control (CC) and Bearer control (BC) 35.2 Point-to-point and multi-party CC 35.3 CC architecture 45.4 Relationship to BC architecture 45.5 Screening function 56 Oper

13、ational requirements 66.1 Provision and withdrawal 66.2 Transport mechanism 67 Primitive definitions and state definitions 67.1 Service primitives 67.1.1 Service primitive architecture 67.1.2 ESTABLISH-CALL 77.1.3 COMPLETE-CALL 87.1.4 STATUS-CALL 8- ii -7.1.5 RELEASE-CALL 97.1.6 PROCEED-CALL 97.1.7

14、ERROR 107.2 Parameters 107.2.1 Call segment ID 107.2.2 Call description 107.2.3 Call changed parameter 107.2.4 Await complete indicator 107.2.5 Bearer establishment address 107.2.6 Release cause 107.2.7 Result 117.2.8 Diagnostics 117.3 CC states 117.3.1 Call Idle 117.3.2 Call Initiated 117.3.3 Outgo

15、ing Call Proceeding 117.3.4 Call Ready 117.3.5 Call Present 117.3.6 Incoming Call Proceeding 117.3.7 Await Call Completion 117.3.8 Call Active 117.3.9 Call Release Request 117.3.10 Call Release Indication 118 Coding requirements 118.1 Abstract definition of the CC operations 118.2 Definition of CC O

16、bject Super Class 158.3 Definitions of CC Object Classes in the Information Model 159 Procedures 179.1 Call establishment request 179.1.1 Preceding CC entity 179.1.2 Succeeding CC entity 179.2 Call Proceeding 189.2.1 Preceding CC entity 189.2.2 Succeeding CC entity 189.3 Call accepted 189.3.1 Preced

17、ing CC entity 189.3.2 Succeeding CC entity 189.4 Completion of call establishment 199.4.1 Preceding CC entity 199.4.2 Succeeding CC entity 199.5 Call status change report 199.5.1 General 199.5.2 Initiating CC entity 19- iii -9.5.3 Receiving CC entity 199.6 Call establishment failure 209.6.1 Precedin

18、g CC entity 209.6.2 Succeeding CC entity 209.7 Call clearing 219.7.1 Procedures at the CC entity that initiates call clearing 219.7.2 Procedures at the CC entity that responds to clearing 219.7.3 Call clearing collision 219.8 Exceptional Procedures 219.8.1 Timer Expiry 219.8.2 Receipt of APDUs with

19、unknown Call Segment Id 229.8.3 Receipt of APDUs with duplicated Call Segment Id 229.8.4 Receipt of APDUs out of sequence 229.8.5 Receipt of Reject APDUs 229.8.6 Handling of unrecognized parameters within CC-Operations 2310 Parameter values (Timers) 2411 Transport mechanism 2412 SDL Diagrams 2412.1

20、Outgoing CC-ASE 2712.2 Incoming CC-ASE 33Annex A - Bearer co-ordination requirements for CC signalling service users 43Annex B - Call Description handling requirements for CC signalling service users 47Annex C - Interworking 51Annex D - Transport mechanisms 53Annex E - Information flow diagrams 55An

21、nex F - Imported ASN.1 Definitions 59Annex G - Object identifiers defined in this Standard 61Annex H - Bibliography 63- iv -.1ScopeThis Standard specifies a signalling protocol for the purpose of call control at the QB, SB, TB, and co-incident SB/TBreference points within, between, and at the access

22、 to Broadband Private Integrated Services Networks and within,between, and at the access to European Broadband Integrated Services Digital Networks. The protocol operatesbetween two adjacent call control entities. The protocol is applicable to a terminal or network node in a separated calland bearer

23、 (connection) control environment for the support of calls having none, a single bearer or multiple bearers.The protocol is applicable to a two-party call. The protocol also provides forward compatibility to the extent that animplementation can also operate within a multi-party call with other imple

24、mentations that use additional capabilities,provided the implementation is deployed where it does not need to be aware of more than two parties.This Standard is related to other Standards in this series which will describe the architecture of a separated call andbearer control environment and scenar

25、ios in which such an architecture can be applied.The protocol specified in this Standard is independent of the supporting transport service.The protocol specified in this Standard is independent of the protocol used for bearer establishment.2 ReferencesThe following documents contain provisions whic

26、h, 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 revisions do not apply. For a non-specific reference, the latest ver

27、sion 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 -Generic Functional Protocol (B-QSIG-GF)ETS 300 796-1 Broadband

28、Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling SystemNo. two (DSS2) protocol; Generic functional protocol; Core aspects; Part 1: Protocolspecification ITU-T Rec. Q.2932.1 (1996), modifiedITU-T Rec. X.680 Information technology - Abstract Syntax Notation One (ASN.1): Spec

29、ification of basic notationITU-T Rec. X.681 Information Technology - Abstract Syntax Notation One (ASN.1): Information objectspecificationITU-T Rec. X.682 Information technology - Abstract Syntax Notation One (ASN.1): Constraint specificationITU-T Rec. X.683 Information technology - Abstract Syntax

30、Notation One (ASN.1): Parameterization of ASN.1specificationsITU-T Rec. X.690 Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER),Canonical Encoding Rues (CER) and Distinguished Encoding Rules (DER)ITU-T Rec. X.880 Information technology - Remote operations: co

31、ncepts, model and notationCCITT Rec. Z.100 CCITT specification and description language (SDL)3 DefinitionsFor the purposes of this Standard the following definitions apply.3.1 Adjacent call control entities (adjacent CC entities)Within the context of a single call, two CC entities that signal direct

32、ly to each other with no intervening CC entity.- 2 -3.2 BearerA connection for the transport of user plane information between users involved in a call.3.3 Bearer controlFunctionality and signalling in and between networks and terminals to effect the control of a bearer, that bearerbeing part of a c

33、all.3.4 Bearer control entity (BC entity)An entity that is located in a terminal or a network and that participates in bearer control.3.5 CallAn association between two or more users using a telecommunication service to communicate through one or morenetworks.3.6 Call controlFunctionality and signal

34、ling in and between networks and terminals to effect the control of a call, excluding thecontrol of individual bearers.3.7 Call control entity (CC entity)An entity that is located in a terminal or a network and that participates in call control.3.8 Call control signalling service providerAn entity w

35、hich provides the signalling services of call control.3.9 Call control signalling service userAn entity within the CC entity to which the signalling services of call control are provided.NOTEThe call control signalling service user performs the Call Description handling, provides the interactions wi

36、thbearer control, and in a network node, co-ordinates the incoming and outgoing side of the CC entity (figure 6).3.10 Call segmentA part of a call located between two adjacent call control entities.3.11 Called partyAny party in a call other than the calling party.3.12 Calling partyThe party which in

37、itiates the call establishment.3.13 Information modelA representation of the service and abstract communications configuration using an object oriented technique.3.14 Originating CC entityThe CC entity that initiates call establishment and is located in a terminal or equipment that functions like at

38、erminal (e.g. a server in the network).3.15 PartyAn addressable signalling endpoint.3.16 Preceding CC entityThe CC entity that initiates call establishment across a given call segment.3.17 Succeeding CC entityThe CC entity at the opposite end of a call segment from the preceding CC entity.- 3 -3.18

39、Terminating CC entityThe CC entity to which call establishment is directed and that is located in a terminal or equipment that functionslike a terminal.3.19 Transit CC entityA CC entity through which a call passes, excluding the originating and terminating CC entity.4 AbbreviationsFor the purposes o

40、f this Standard, the following abbreviations apply:APDU Application Protocol Data UnitASN.1 Abstract Syntax Notation OneBC Bearer ControlB-PISN Broadband Private Integrated Services NetworkCC Call ControlMMandtoryO Optional5 Basic model5.1 Separation of Call Control (CC) and Bearer control (BC)The p

41、rotocol specified in this Standard is applicable to an environment in which the control of a call is separatefrom the control of the bearer or bearers that exist within the context of that call.In order for two users to communicate using a telecommunication service, an association, or call, is estab

42、lishedbetween the two users. Within the context of the call, one or more bearers can be established for transporting userplane information between the users. However, bearers are not normally established until the call has been acceptedby the called terminal, and therefore resources required by bear

43、ers are not occupied unnecessarily if the call cannotbe established, e.g., if the called terminal is unable to accept the call because resources are not available. During thelife-time of the call, bearers can be added or cleared down as required. The call is terminated by one of the twousers when th

44、ere is no further need for communication. Termination of the call implies that all bearers (if any) arecleared down.Although for some telecommunication services a single bearer is sufficient, other telecommunication servicesbenefit from the use of multiple bearers, each tailored to suit the characte

45、ristics of the user plane information to betransported. This is particularly true for multi-media applications involving audio, video and data. The call providesa context in which the various bearers can exist and a means of binding the bearers together.5.2 Point-to-point and multi-party CCIn a poin

46、t-to-point configuration the protocol specified in this Standard operates between any two adjacent CCentities between the calling party and the called party.In a multi-party configuration the protocol specified in this Standard operates between any two adjacent CC entitieson the point-to-point leg b

47、etween a co-ordination point in the network and a called party. In this case a networknode in the calling partys network takes responsibility for co-ordinating the responses from multiple point-to-pointsignalling associations to the called parties into one signalling association to the calling party

48、. Enhancements to bemade to the CC protocol in order to make it suitable also for this signalling association to the calling party in caseof a multi-party call are outside the scope of this Standard.Figure 1 shows an example configuration for a multi-party call with two called parties involved.- 4 -

49、Calling partyCalled partyCalled partyCalled partysnetworkCalled partysnetworkCalling partysnetworkCoordinationpointCallFigure 1 - Multi-party call with two called parties5.3 CC architectureCC provides the means of establishing, maintaining and clearing down a call, including the operation of anysupplementary services that relate to the call rather than to individual bearers. Control of a call is effected by meansof a number of call control entities (CC entities) located in the users terminals and in various network nodes.Whereas BC involves a bearer control entity (BC entity)