ITU-T SERIES Q SUPP 12-1999 Technical Report TRQ 2100 Coordinated Call Control and Bearer Control Signalling Requirements - Root-Party Coordinated Call and Bearer Control (Study Gr.pdf

《ITU-T SERIES Q SUPP 12-1999 Technical Report TRQ 2100 Coordinated Call Control and Bearer Control Signalling Requirements - Root-Party Coordinated Call and Bearer Control (Study Gr.pdf》由会员分享，可在线阅读，更多相关《ITU-T SERIES Q SUPP 12-1999 Technical Report TRQ 2100 Coordinated Call Control and Bearer Control Signalling Requirements - Root-Party Coordinated Call and Bearer Control (Study Gr.pdf（176页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 12 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2100: Coordinated call control and bearer control signalling requirements - Root-party coordinated call and bearer con

2、trol ITU-T Q-series Recommendations - Supplement 12 (Formerly CCITT Recommendations) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPEC

3、IFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM

4、 No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 BROADBAND ISDN Q.1-Q.3 Q.4-Q. 59 Q.60-Q.99 Q.100-Q.119 Q. 120-Q.249 Q.250-Q.309 Q.310-Q.399 Q.400-Q.499 Q.5

5、00-Q.599 Q.600-Q.699 Q.700-Q.849 Q.850-Q.999 Q. 1000-Q. 1 O99 Q.1100-Q.1199 Q. 1200-Q. 1699 Q. 1700-Q. 1799 Q.2000-Q.2999 For further details, please rer to the list of ITD-T Recommendations. SUPPLEMENT 12 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2100: COORDINATED CALL CONTROL AND COOR

6、DINATED CALL AND BEARER CONTROL BEARER CONTROL SIGNALLING REQUIREMENTS - ROOT-PARTY Summary This Supplement specifies the signalling requirements for the root-party coordinated call control and bearer control capability. These coordinated call control and bearer control functional entity actions are

7、 defined in terms of information flows. This Supplement is intended to speciQ the essential UNI and NNI interactions required to develop root-party coordinated call control and bearer control functional entity actions. Source Supplement 12 to ITU-T Q-series Recommendations was prepared by ITU-T Stud

8、y Group 1 1 (1997-2000) and was approved under the WTSC Resolution No. 5 procedure on 3 December 1999. Q series - Supplement 12 (12/1999) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Stan

9、dardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference

10、 (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas o

11、f information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this publication, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating

12、agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual P

13、roperty Rights, whether asserted by ITU members or others outside of the publication development process. As of the date of approval of this publication, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this publication. However, impl

14、ementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including ph

15、otocopying and microfilm, without permission in writing fi-om the ITU. 11 Q series - Supplement 12 (12/1999) CONTENTS 1 2 3 4 5 6 7 7.1 7.2 7.3 7.4 8 8.1 8.2 Scope . Normative references Definitions Abbreviations Information flows used in this Supplement Overview of Call Control Level Peer-to-Peer F

16、unctional Entity Actions Coordinated call and network connection establishment Two-party call establishment with one or more network connections . 7.1.1 Call and network connection establishment - Single network connection - Without look-ahead Call and network connection establishment - Single netwo

17、rk connection - With look-ahead . Call and network connection establishment - Two network connections . Without look-ahead . 7.1.2 7.1.3 Three- or more-party call establishment with one or more network connections . 7.2.1 Call and network connection establishment - Originating node branch - Root-par

18、ty 7.2.2 Call and network connection establishment - Relay node branch - Root- party . 7.2.3 Call and network connection establishment - Two network connections - Without look-ahead . Multicast address establishment with one or more network connections . 7.3.1 Call and connection establishment singl

19、e network connection - Multicast address is used by requesting party - Mandatory Multicast Set-up . Call and connection establishment single network connection - Multicast address is used by requesting party - Optional multicast Set-up . 7.3.2 Any-cast address procedures . Addition of one or more ne

20、w parties to an existing call with attachment to existing or new network connections . Addition of one or more new parties with attachment to one or more existing connections . 8.1.1 Add one new party requested by a party which is the root of the network connection - Without network 1ook.ahead 8.1.2

21、 Add two new parties requested by a party which is the root of the network connection - Without network 1ook.ahead Addition of one or more new parties with attachment to one or more new network connections . Page 1 2 2 2 3 3 5 5 5 10 16 25 25 35 42 62 62 71 80 88 88 88 95 105 . Q series . Supplement

22、 12 (12/1999) 111 Page 9 9.1 9.2 9.3 10 10.1 10.2 10.3 10.4 10.5 8.2.1 8.2.2 Add one new party requested by a party which will be the root of the new network connection - Without network look-ahead . Add two new parties requested by a party which will be the root of the new network connection - With

23、out network look-ahead Release one or more parties and their associated network connection branches from the call General rules for release of a party . Release a party and its associated network connection branches from a two-party call . 9.2.1 Release of a party by the call owner - Clear call opti

24、on - Connection release from requesting party . 9.2.2 Release of a party by the call owner - Clear all option - Connection release from addressed party 9.2.3 Release of a party by the call owner - Retain call option Release one or more parties and their associated network connection branches from a

25、three- or more-party call 9.3.1 Release of a party requested by the call owner - Root-party is the call 9.3.2 Release of a party requested by the party owner - Root-party is the call owner . owner . Call release with one or more parties and their associated network connections . General rules for re

26、leasing a call . Release of a single-party call and its associated connections. requested by the call Release of a two-party call and its associated connections. requested by the call 10.3.1 Release of the call by the call owner - Connection release from requesting party 10.3.2 Release of the call b

27、y the call owner - Connection release from both Release of a multiparty call and its associated connections. requested by the call Release of a call requested by a non-call owner . 10.5.1 Release of a two-party call requested by a non-call owner 10.5.2 Release of a multiparty call requested by a non

28、-call owner owner owner parties . owner 106 112 124 124 125 125 128 132 136 136 140 146 146 147 148 148 151 154 161 161 164 iv Q series . Supplement 12 (12/1999) Supplement 12 to Q-series Recommendations Release of a two-party call and its associated connections requested by a non-call TECHNICAL REP

29、ORT TRQ.2100: COORDINATED CALL CONTROL AND COORDINATED CALL AND BEARER CONTROL BEARER CONTROL SIGNALLING REQUIREMENTS - ROOT-PARTY I Type 1,2,3 and 5 1 Scope This Supplement presents the procedures, information flows and information elements needed for supporting root-party control of coordinated ca

30、lls and bearers involving type 1, 2, 3 and type 5 network connections. Table 1 - 1 illustrates the scope of the capabilities contained within this Supplement. Table 1-1 - Root-party call control capabilities Coordinated call and network connection establishment Two-party call establishment with one

31、or more network connections Three- or more-party call establishment with one or more network connections Multicast address establishment with one or more network connections Any cast address establishment with one or more network connections Addition of one or more new parties to an existing call wi

32、th attachment to existing or new network connections Addition of one or more new parties with attachment to one or more existing connections Addition of one or more new parties with attachment to one or more new network connections Release one or more parties and their associated network connection

33、branches from the call Release a party and its associated network connection branches from a two-party call. Release one or more parties and their associated network connection branches from a three- or more party-call. Call release with one or more parties and their associated network connection Re

34、lease of a single-party call and its associated connections, requested by the call owner Release of a two-party call and its associated connections, requested by the call owner Release of a multiparty call and its associated connections, requested by the call owner Network connection type Type 1,2,3

35、 and 5 Type 2,3, and 5 Type 2,3 and 5 Type 1 Type 2,3 and 5 Type 2,3 and 5 Type 1,2,3 and 5 Type 1,2,3 and 5 Type 1,2,3 and 5 Type 1,2,3 and 5 Type 1,2,3 and 5 owner party Release of a multiparty call and its associated connections, requested by a non- call owner party Type 1,2,3 and 5 Q series - Su

36、pplement 12 (12/1999) 1 2 Normative references The following Technical Reports and other references contain provisions which, through reference in this text, constitute provisions of this Supplement. At the time of publication, the editions indicated were valid. All supplements and other references

37、are subject to revision; all users of this Supplement are therefore encouraged to investigate the possibility of applying the most recent edition of the supplements and other references listed below. A list of the currently valid ITU-T Recommendations and supplements are regularly published. i ITU-T

38、 Q-series Recommendations, Supplement 7 (1999), Technical Report TRQ.2001: General aspects for the development of uniped signalling requirements. 2 ITU-T Q-series Recommendations, Supplement 1 O (1 999), Technical Report TRQ.2002: Information flow elements. 3 Definitions This Supplement defines the

39、following terms: 3.1 3.2 requested signalling capability. 3.3 capability. 3.4 Supplement 7 i. 3.5 between one call party end point and its Serving Node. 3.6 call. 3.7 3.8 several party owners within a call. 3.9 control functional entity but no call control functional entity. 3.10 3.11 signalling cap

40、ability. 3.12 which contains call control and bearer control functional entities. addressed party: The party addressed by the requested signalling capability. addressed serving node: Network equipment associated with the party addressed by the backward: The direction fiom the addressed party to the

41、party requesting a signalling network connection: An ATM network connection of topology type 1 to 5 as defined in call: An end-to-end communications service between two or more call party end points, or call owner: One who initiates a call is the Call Owner. There is only one Call Owner per forward:

42、 The direction fiom the requesting party to the addressed party. party owner: One who adds a party to a call is the owner of that party. There may be relay node: Network equipment, such as a transit bearer exchange, which contains a bearer requesting party: The party requesting a signalling capabili

43、ty. requesting serving node: Network equipment associated with the party requesting a serving node: Network equipment, such as a local exchange or private branch exchange, 4 Abbreviations This Supplement uses the following abbreviations: NA Not Applicable PEP Party End Point 2 Q series - Supplement

44、12 (12/1999) 5 Table 5-1 contains the root-party control information flows that are used across the call control and bearer control interfaces illustrated in the Unified Functional Model contained in Supplement 7 i. These information flows are used to establish, modify and release root-party calls a

45、nd network connections. In addition to those information flows defined in Table 5-1, the full set of information flow definitions can be found in Supplement 1 O 2. Information flows used in this Supplement Table 5-1 - Information flows used for root-party control Information Flow I begin I ready I c

46、ommit I cancel I indication I Add-Bearer-to-Call IJIJIJI I I Add-Party-&-Bearer-to-Call IJIJIJI I Add-Party-to-Bearer IJIJIJI I Remote-Release-Party-fkom Call I IJIJI I I 6 Stage 2 flows for each signalling capability is illustrated via a high level overview. The overview model does not illustrate a

47、ll possible configurations which could exist within an actual instant of the service, however, the examples have been chosen in order to illustrate the general principles. The overview will employ the network configuration shown in Figure 6- 1. The actions illustrated in this figure can be used to d

48、escribe signalling control actions associated with establishment or release of a coordinated Call and network connections. Note that for the purpose of this overview, the information flows and actions illustrate the establishment of a two-party call with two network connections. Overview of Call Con

49、trol Level Peer-to-Peer Functional Entity Actions Q series - Supplement 12 (12/1999) 3 Requesting - - Addressed TI 11 09690-00 Figure 6-1 - Two party coordinated call and network connection establishment The actions illustrated in Figwe 6-1 are described as follows: 4 Signalling Service Request issued by service requester: Receiving entity validates request, modifies internal state information, and then issues action 2. Relayed Signalling Service Request issued by requesters serving node: Receiving entity validates request, modifies internal state information, and then issues its