1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 13 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.21 I O: Coordinated call control and bearer control signalling requirements - Leaf-party coordinated call and bearer c
2、ontrol ITU-T Q-series Recommendations - Supplement 13 (Formerly CCITT Recommendations) STD.ITU-T RECMN SERIES Q SUPP 13-ENGL 1999 4862591 0686002 9b9 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORK
3、ING 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 SYSTEMS SPECIFICATION
4、S 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.3 Q. 4-Q. 59 Q.60-Q.
5、 99 Q 100-Q.119 Q.120-Q.249 Q.250-Q.309 Q. 3 1 O-Q. 399 Q.400-Q.499 Q. 500-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 I - - - For further details, please refir to the list ofTU-T Recommendarrons - STD-ITU-T RECMN SERIES 13 SU
6、PP 13-ENGL 1977 4862571 ObBb003 T5 SUPPLEMENT 13 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2110: COORDINATED CALL CONTROL AND COORDINATED CALL AND BEARER CONTROL BEARER CONTROL SIGNALLING REQUIREMENTS - LEAF-PARTY Summary This Supplement specifies the signalling requirements for coordin
7、ated call control and bearer control capability of the leaf-party of a call. The coordinated call control and bearer control functional entity actions by a leaf-party of a call are defined in terms of information flows. This Supplement is intended to specify the essential UNI and NNI interactions re
8、quired to develop leaf-party coordinated call control and bearer control functional entity actions. Source Supplement 13 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. STDaITU-T RECMN SERI
9、ES SUPP L3-ENGL 1999 m 4862591 Ob86004 731 m FOREWORD 1T (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studyin
10、g 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 (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Group
11、s 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. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a
12、 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 agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or
13、 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 Property Rights, whether asserted by ITU members or others outside of the publication development pro
14、cess. 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, implementors are cautioned that this may not represent the latest information and are therefore strongly
15、 urged to consult the TSB patent database. O ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized iii any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. STD-ITU-T RECMN SERIES d SUPP
16、 13-ENGL 1999 D 48b259L Ob86005 CONTENTS 1 2 3 4 5 6 7 7.1 7.2 7.3 8 8.1 8.2 9 10 Scope Normative References Definitions Abbreviations . Information flows used in this Supplement Overview of Call Control Level Peer-to-Peer Functional Entity Actions Coordinated call and network connection establishme
17、nt . Two-party call establishment with one or more network connections . Three- or more-party call establishment with one or more network connections 7.2.1 Call and network connection establishment - Root node branch . Leaf- party . 7.2.2 Call and network connection establishment - Two network conne
18、ctions - Leaf-party Multicast address establishment with one or more network connections 7.3.1 address is used by requesting party - Mandatory Multicast Set-up 7.3.2 address is used by requesting party - Optional multicast Set-up . Call and connection establishment single network connection - Multic
19、ast Call and connection establishment single network connection - Multicast Addition of one or more new 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 par
20、ty requested by a party which is the leaf of the network connection - Without network look-ahead . 8.1.2 Add two new parties requested by a party which is the leaf of the network connection - Without network look-ahead . Addition of one or more new parties with attachment to one or more new network
21、connections . 8.2.1 Add one new party requested by a party which will be a leaf of the new network connection . 8.2.2 Add two new parties requested by a party which will be a leaf of the new connection . Release one or more parties and their associated network connection branches from the call Call
22、Release with one or more parties and their associated network connections . b78 Page i 2 2 2 3 3 5 5 5 5 16 39 40 50 60 61 61 68 80 80 92 109 109 STD-ITU-T RECMN SERIES 4 SUPP 13-ENGL 1999 D 4b2591 Ob8bb 504 Supplement 13 to Q-series Recommendations TECHNICAL REPORT TRQ.2110: COORDINATED CALL CONTRO
23、L AND COORDINATED CALL AND BEARER CONTROL (Geneva, 1999) BEARER CONTROL SIGNALLING REQUIREMENTS - LEAF-PARTY 1 Scope This Supplement presents the procedures, information flows and information elements needed for supporting leaf-party control of coordinated calls and bearers involving type 1, 2, 3 an
24、d type 5 network connections. Table 1 - 1 illustrates the scope of the capabilities contained within this Supplement. Table 1-1 - Leaf-party Call Control Capabilities Coordinated call and network connection establishment Two-party call establishment with one or more network connections Three- or mor
25、e-party call establishment with one or more network connections Multicast address establishment with one or more network connections Addition of one or more new parties to an existing call with attachment to existing or new network connections Addition of one or more new parties with attachment to o
26、ne 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 branches from the call Release a party and its associated network connection branches from a two-party call R
27、elease 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 Release of a single-party call and its associated connections requested by the call owner Release of a two-party
28、call and its associated connections, requested by the call owner Release of a multiparty call and its associated connections, requested by the call owner Release of a two-party call and its associated connections, requested by a non-call owner party Release of a multiparty call and its associated co
29、nnections, requested by a non-call owner party Network connection type ;Ype 1,2,3, and 5 type 2,3, and 5 type 2,3, and 5 Lype 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 type 1,2,3, and 5 type 1,2,3, and 5 STD-ITU-T RECMN SERIE
30、S d SUpp L3-ENGL 1777 4862571 0686007 440 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
31、 other references 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 is regularly p
32、ublished. i ITU-T Q-series Recommendations - Supplement 7 (1 999), Technical Report TRQ. 2001: General aspects for the development of unified signalling requirements. 2 ITU-T Q-series Recommendations - Supplement 1 O (1 999), Technical Report TRQ. 2002: Information Flow Elements. 3 Definitions This
33、Supplement defines the 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
34、.10 3.1 1 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 backward: The direction from the
35、 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 Call Owner. There is only on
36、e 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 requesting party: The party request
37、ing 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 Applicable PEP Party End Point
38、 - STD-ITU-T RECMN SERIES Q SUPP 13-ENGL 1999 4862591 0686008 387 5 Table 5-1 contains the leaf-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 1 J. These information flows are u
39、sed to establish, modify and release root-party calls and 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
40、leaf-party control Information Flow begin ready Add-Bearer-to-Call J J commit cancel indication J I Add-Party-&-Bearer-to-Call IJIJIJI I Add-Party-to-Bearer Call-&-Bearer-Set-up Call-Set-up Remote-Call-&-Bearer- Set-up J J J J J J J J J J J J J I Remote-Add-Party-to-Bearer IJIJIJI I Interrogation-Te
41、rminating-End-Point Notie-Call-&-Bearer-Change Release-Bearer Release-Cal I Release-Call-&-Bearer I Remote-Add-Party-&-Bearer-to-Call I J I J I J I I J J J J J J J J J J I Detach-Party-from-Bearer I IJIJI I Release-Party-from-Call Remote-Release-Party-from Call J J J J 6 Stage 2 flows for each signa
42、lling capability is illustrated via a high levei overview. The overview model does not illustrate all 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
43、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 of a coordinated call and network connections. Overview of Call Control Level Peer-to-Peer Functional Entity Actions - STDUITU
44、-T RECMN SERIES Q SUPP L3-ENGL 1999 = - Requesting - Party W Node Node Node Addressed -El T1 1 1 1 O1 8003 Figure 6-1 - Two-party coordinated call and network connection establishment Note that for the purpose of this overview, the information flows and actions illustrate the establishment of a two-
45、party call with two network connections. The actions illustrated in Figure 6-1 are described as follows: Signalling Service Request issued by service requester: Receiving entity validates request, modifies internal state information, and then issues action 2. Relayed Signalling Service Request issue
46、d by requesters serving node: Receiving entity validates request, modifies intemal state information, and then issues its response as action 3. Signalling Service Response issued by addressed partys serving node: Receiving entity validates request, modifies internal state information, and then issue
47、s the request on the relay node as action 4. Signalling Service Request issued by requesters serving node: Receiving entity records request, modifies internal state information and then relays request as action 5. Relayed Signalling Service Request issued by relay node: Receiving entity records requ
48、est, modifies internal state information and then issues the request on the addressed partys interface as action 6. Signalling Service Request issued by addressed partys serving node: Receiving entity validates request, modifies internal state information and then issues its response as action 7. Si
49、gnalling 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 9. Signalling Service Confirmation issued by addressed partys serving node: Receiving entity records response, modifies internal state information and notifies user of the outcome of the responded service. Signalling Service Response issued by addressed partys serving node: Receiving entity records response, modifies internal state information and
