ITU-T SERIES Q SUPP 19-1999 Technical Report TRQ 2300 Bearer Control Signalling Requirements - Root-Party Bearer Control Series Q Switching and Signaling (Study Group 11)《技术报告TRQ 2.pdf

1、 STD-ITU-T RECMN SERIES Q SUPP 19-ENGL 1999 W 4Bb2591 ObBb137 270 INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement I9 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2300: Bearer control Sig na1 I i ng req ui rements -

2、 Root-party bearer control ITU-T Q-series Recommendations - Supplement I9 (Formerly CCITT Recommendations) STD-ITU-T RECMN SERIES Q SUPP 19-ENGL 1999 9 48b259L 068bLL LO7 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AN

3、D SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS 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

4、SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM 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.

5、3 Q.4-Q.59 Q.60-Q. 99 Q.100-Q.119 Q .I 204.249 Q.250-Q.309 Q.310-Q.399 Q.400-Q.499 Q.500-Q. 599 Q.6004.699 Q.700-Q. 849 Q.850-Q. 999 Q. 1000-Q. I O99 Q.1100-Q.1199 Q.1200-Q.1699 Q.1700-Q.1799 Q.2000-Q.2999 For firther details, please refer to the list of ITU-T Recommendations. STD-ITU-T RECMN SERIES

6、 Q SUPP 17-ENGL 1777 - 4b2571 Obb119 043 m SUPPLEMENT 19 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2300: BEARER CONTROL SIGNALLING REQUIREMENTS - ROOT-PARTY BEARER CONTROL Summary This Supplement specifies the signalling requirements for bearer control capability by the root-party in a

7、call. The bearer control functional entity actions by a root-party in a call are defined in terms of information flows. This Supplement is intended to specie the essential UNI and NNI interactions required to develop root-party initiated bearer control functional entity actions. Source Supplement 19

8、 to ITU-T Q-series Recommendations was prepared by ITU-T Study Group 11 (1 997-2000) and was approved under the WTSC Resolution 5 procedure on 3 December 1999. FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Te

9、lecommunication Standardization 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 Standa

10、rdization Conference (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 1.

11、 In some areas of information technology which fali 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 recog

12、nized operating 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 IT takes no position concerning the evidence, validity or applicability of claimed

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

14、ever, implementors 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, in

15、cluding photocopying and microfilm, without permission in writing from the ITU. STDWITU-T RECMN SERIES 13 SUPP LEI-ENGL LEI99 = 48b259L ObBbL2L CONTENTS 1 2 3 4 5 6 7 7.1 7.2 8 8.1 8.2 9 9.1 9.2 9.3 10 10.1 10.2 Scope Normative References Definitions Abbreviations . Information flows used in this Su

16、pplement Overview of Bearer Control Level Peer-to-Peer Functional Entity Actions Addition of one or more new network connections to an existing call Addition of one new network connection to an existing call . Addition of two new network connections to an existing call . Attachment of one or more ex

17、isting parties to one or more existing network connections . Attach one existing party to one or more existing connections 8.1.1 Attach one existing party to one existing connection . 8.1.2 Attach one existing party to two existing connections Attach two existing parties to one or existing connectio

18、ns 8.2.1 Attach two existing parties to one existing connection . Detachment of one or more parties from one or more connections . General Rules for the detachment of a party Detach a party from its associated network connection branch in a two-party call 9.2.1 Detachment of a party by the call owne

19、r - Clear call option . Party detachment from requesting party . 9.2.2 Detachment of a party by the call owner - Clear all option . Connection release from addressed party . 9.2.3 Detachment of a party by the call owner . Retain call option Detach one party from its associated network connection bra

20、nch in a four-party call 9.3.1 Detachment of a party requested by the call owner - Root-party is call 9.3.2 Detachment of a party requested by the party owner - Root-party is call single Connection Call . owner . owner . Removal of one or more connections from a call . General rules for the removal

21、of a connection from a call . Removal of one or more network connections from a two-party call - 7TL Page 1 1 2 2 2 3 4 4 8 17 17 17 24 36 36 46 46 47 48 51 54 58 58 62 68 68 69 STD.ITU-T RECMN SERIES Q SUPP 17-ENGL Lqqq - 48b2591i Ob8bL22 638 Page 10.2.1 Connection Release request in a two-party co

22、nnection - Requested by the call owner 69 10.2.2 Connection Release request in a two-party connection - Requested by connection owner 72 . 10.3 Removal of one or more network connections from a three- or more-party call 75 10.3. i 1 0.3.2 Removal of one network connection requested by connection own

23、er Removal of one network connection requested by call owner 75 80 10.3.3 Removal of one network connection requested by a party which does not own either the call or the connection 85 STD.ITU-T RECMN SERIES Q SUPP 19-ENGL 1999 48b259L Ob8bL23 574 Addition of one or more new network connections to a

24、n existing call requested by the party that will be the root of the new network connection(s) Addition of one new network connection to an existing call Addition of one or more new network connections to an existing call Attachment of one or more existing parties to one or more existing network conn

25、ections requested by the party associated with the root of the existing network connection Attach one or more existing parties to one or more existing connections Attach one or more existing parties to one or more new connections Detachment of one or more parties from one or more connections by eith

26、er the call owner, network connection owner or the party owner Detach a party from its associated network connection branches in a two-party call. Detach one or more parties from their associated network connection branches in a three- or more-party call. Supplement 19 to Q-series Recommendations Ne

27、twork connection We Type I, 2,3 and 5 Type 1,2,3 and 5 Type 1,2,3 and 5 Type I, 2,3 and 5 Type 1 , 2,3 and 5 Type 1 , 2,3 and 5 TECHNICAL REPORT TRQ.2300: BEARER CONTROL SIGNALLING (Geneva, 1999) REQUIREMENTS - ROOT-PARTY BEARER CONTROL Removal of one or more connections from a call requested by the

28、 network requested by either the connection owner or call owner Removal of one or more network connections from a two-party call. Removal of one or more network connections from a three- or more-party call. 1 Scope This Supplement presents the procedures, information flows and information elements n

29、eeded for supporting control by the root-party of bearers involving type 1, 2, 3 and 5 network connections. Table 1 - 1 illustrates the scope of the capabilities contained within this Supplement. Tpe 1,2,3 and 5 Tpe 1,2,3 and 5 Table 1-1 - Root-party Bearer Control Capabilities 2 Normative Reference

30、s 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 are subject to revision; ail users of this Su

31、pplement 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 is regularly published. i ITU-T Q-series Recommendations - Supplement 7 (1999

32、), Technical Report TRQ. 2001: General aspects for the development of unijied signalling requirements. STDmITU-T RECMN SERIES Q SUPP 19-ENGL 1999 - 48b2591 0b86324 400 = 2 ITU-T Q-Series Recommendations - Supplement 1 O (1 999), Technical Repor! TRQ. 2002; Information Flow Elements. 3 Definitions Th

33、is Supplement defines the following terms: 3.1 3.2 requested signalling capability. 3.3 capability. 3.4 Q-series Recommendations 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

34、control functional entity. 3.10 3.11 signalling capability. 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 backw

35、ard: The direction from the addressed party to the 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 C

36、all Owner. There is only one Call Owner per forward: The direction from 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 requesti

37、ng party: The party requesting a signalling capability. 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 App

38、licable PEP Party End Point 5 Table 5-1 contains the root-party control information flows that are used across the bearer control interfaces illustrated in the Unified Functional Model contained in Q-series Recommendations Supplement 7 i. These information flows are used to establish, modi and relea

39、se root-party requested network connections. Information flows used in this Supplement Information Flow I begin I ready I commit 1 cancel I indication I - D L In addition to those information flows defined in Table 5-1, the full set of information flow definitions can be found in Q-series Recommenda

40、tion Supplement 10 2. - C - J u T1 11 1035ooo Serving Relay Serving 6 Stage 2 flows for each signalling capability is illustrated via a high level overview. The overview model does not illustrate all possible configurations which could exist within an actual instant of the service, however, the exam

41、ples 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 describe signalling control actions associated with establishment or release network connections. Note th

42、at 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 Bearer Control Level Peer-to-Peer Functional Entity Actions NETWORK Requesting I Requesting Relay Addressed Serving Node Node Serving Node

43、 Addressed ( Node- Nod Node- ) Figure 6-1 - Two-party coordinated call and network connection establishment The actions illustrated in Figure 6-1 are described as follows: 1) Signalling Service Request issued by service requester: Receiving entity validates request, modifies internal state informati

44、on, and then issues action 2. STD-ITU-T RECMN SERIES Q SUPP 19-ENGL 1979 - 48b2591 Ob8bL2b 283 2) 3) Signalling Service Request issued by requesters serving node: Receiving entity records request, modifies internal state information and then relays request as action 3. Relayed Signalling Service Req

45、uest issued by relay node: Receiving entity records request, modifies internal state information and then issues the request on the addressed partys interface as action 4. Signalling Service Request issued by addressed partys serving node: Receiving entity validates request, modifies internal state

46、information, and then issues its response as action 5. Signalling Service Response issued by addressed party: Receiving entity records response, modifies internal state information, and then issues its confirmation as action 8 and its response as action 6. Signalling Service Confirmation issued by a

47、ddressed partys serving node: Receiving entity records response, modifies internal state information, and notifies the user of the outcome of the responded service. Signalling Service Response issued by addressed partys serving node: Receiving entity records response, modifies internal state informa

48、tion and then relays response as action 8. Signalling Service Response issued by relay node: Receiving entity records response, modifies intemal state information and relays response to the service requester as action 9. Signalling Service Response issued by requesters serving node: Receiving entity

49、 records response, modifies internal state information, and notifies the user of the outcome of the requested service. The purpose of this overview model is that it provides an end-to-end pictorial representation of the signalling capability in one figure. Again, note that the model does not present all possible network topologies, however, it illustrates the general configurations that would be encountered in intra-network operation. The extension to multiple networks can be extrapolated by replacing the serving nodes and relay nodes with local servi