1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 15 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2130: Coordinated call control and bearer control signalling requirements for leaf initiated join service ITU-T Q-seri
2、es Recommendations - Supplement 15 (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 SPECIFICATIONS OF SIG
3、NALLING 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 No. 1 PUBLIC LAN
4、D 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.500-Q.599 Q.600-Q.
5、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 15 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2130: COORDINATED CALL CONTROL AND BEARER CONTROL SIGNAL
6、LING REQUIREMENTS FOR LEAF INITIATED JOIN SERVICE Summary This Supplement specifies the signalling requirements for the Leaf Initiated Join service capability. These signalling requirements cover the UNI and NNI interactions (exchange of information flows) and internal serving node procedure require
7、ments for a serving node associated with a leaf and associated with the root of the connection(s). The signalling requirements include LIJ call creation and release, attachment of new parties by the root or by themselves (“leaf initiated join“), and detachment of parties by the root or by themselves
8、. Source Supplement 15 to ITU-T Q-series Recommendations was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution 5 procedure on 3 December 1999. Q series - Supplement 15 (12/1999) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Special
9、ized 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 studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunication
10、s 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 Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T i
11、s 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 collaborative basis with IS0 and IEC. NOTE In this publication, the expression “Administration“ is used for conciseness to in
12、dicate both a telecommunication administration and a recognized 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 ITU takes no position co
13、ncerning the evidence, validity or applicability of claimed 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 ITU had not received notice of intellectual property, protected by p
14、atents, which may be required to implement this publication. However, 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 ut
15、ilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing fi-om the ITU. 11 Q series - Supplement 15 (12/1999) CONTENTS 1 2 3 4 5 6 6.1 6.2 6.3 6.4 7 8 9 9.1 9.2 9.3 Scope . References . Definitions Abbreviations Information flo
16、ws used in this Supplement Leaf initiated call registration . Root-party controlled actions Network controlled actions . 6.2.1 Handling of LIJ call join requests when an active LIJ call has been established . 6.2.2 Handling of LIJ call and bearer requests when an active LIJ call and its set of beare
17、rs have been established 6.2.3 Handling of leafjoin requests when no active LIJ call is in progress or a LIJ call is active but its set of bearers have not been established 6.2.4 Registration process for a root serving node . Registration process for a leaf serving node . Root-party notification opt
18、ions upon completion of join requests Serving node LIJ procedwes . Overview of Peer-to-Peer Functional Entity Actions . Functional Entity Actions . LIJ Call Creation . 9.1.1 9.1.2 9.1.3 Root-Party Request to Create a LIJ Call and Bearer (without attachment Root-Party Request to Create a LIJ Call and
19、 Bearer (with attachment of a Leaf-Party Request to Join LIJ Call and Bearer (no active LIJ call exists) . 9.2.1 Leaf-Party Request to Join Active Call and Bearer in Root Serving Node - Root Screening 9.2.2 Leaf-Party Request to Join Active Call and Bearer in Root Serving Node - Network Screening .
20、9.2.3 Leaf-Party Request to Join Active Call and Bearer in Leaf Serving Node - 9.2.4 Leaf-Party Request to Join Active LIJ Call and Bearer . Removal of Leaf-Party rom a LIJ Call and Bearer(s) Requested by the Root-Party . of a Leaf-Party) Leaf-Party) . Leaf-Party Request to Join Active LIJ Call and
21、Bearer Root Screening Page 1 3 3 7 9 9 14 14 15 20 21 24 . Q series . Supplement 15 (12/1999) 111 Page 9.3.1 Removal of leaf-party requested by root-party (multiple leaf-parties attached to bearer at leaf serving node) . 9.3.2 Removal of leaf-party requested by root-party (single leaf-party attached
22、 to bearer at leaf serving node) 9.3.3 Removal of leaf-party requested by root-party (last leaf-party attached to LIJ call) Leaf-Party Requests to be Released rom the LIJ Call and Bearer(s) . 9.4.1 Leaf-party release request (multiple leaf-parties attached to bearer at leaf 9.4.2 Leaf-party release
23、request (single leaf-party attached to bearer at leaf serving node) . 9.4.3 Leaf-party release request (last leaf-party attached to LIJ call) LIJ Call and Bearer Release by Root-Party . 9.5.1 Root-Party Requests to Terminate LIJ Call (with no associated Leaf-Parties) 9.5.2 Root-Party Requests to Ter
24、minate LIJ Call (with several Leaf SN associated with the LIJ Call) LIJ Call Leaf-Party detaches rom Bearer . 9.6.1 Leaf-Party Requests to Detach rom Bearer 9.6.2 Leaf-Party Requests to Detach rom Bearer 9.4 serving node) 9.5 9.6 24 26 30 34 34 37 40 44 44 46 50 50 52 iv Q series . Supplement 15 (12
25、/1999) Supplement 15 to Q-series Recommendations TECHNICAL REPORT TRQ.2130: COORDINATED CALL CONTROL AND BEARER CONTROL SIGNALLING REQUIREMENTS FOR LEAF INITIATED JOIN SERVICE (Geneva, 1999) 1 Scope This Supplement presents the procedures, information flows and Information Elements needed for suppor
26、ting calls containing root screened and network screened leaf initiated join calls with point-to- multipoint connection(s). 2 References The following Technical Reports and other references contain provisions which, through reference in this text, constitute provisions of this Supplement. At the tim
27、e of publication, the editions indicated were valid. All Supplements and 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
28、the currently valid ITU-T Recommendations and Supplements are regularly published. 11 ITU-T 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 10 (1999), Techn
29、ical Report TRQ.2002: Information Flow Elements. 3 ITU-T Q-series Recommendations - Supplement 12 (1999), Technical Report TRQ.2100: Coordinated call control and bearer control signalling requirements - Root-Party coordinated call and bearer control. 3 Definitions These signalling requirements allow
30、 a leaf-party to join a call that contains one or more point-to- multipoint connections which have been designated leaf initiated join Connections and be added to these connections. This “Special Call Association“ is called a leaf initiated join Call (LIJ Call); it is referenced by a leaf-party via
31、a Unique “LIJ Call ID“. The following three types of LIJ Calls are differentiated: 3.1 LIJ calls with root screening: The Root receives a leaf Set-up request for every leaf that wishes to join the call, then either creates the call to the Leaf or adds the leaf to the ongoing call. The root has the o
32、ption of rejecting any join attempt. When using this mode, the network never automatically joins leaves to the call. 3.2 LIJ calls network screening with root notification: The root creates the call as a leaf initiated join call, then the network automatically attempts to add all leaves to the call
33、that request to be added. After each leaf completes joining the LIJ call, the root receives a notification about the event. 3.3 LIJ calls network screening without root notification: The root creates the call as a leaf initiated join call, then the network automatically attempts to add all leaves to
34、 the call that request to be added. In this case, the root gets no indication when leaves are added by the network. Q series - Supplement 15 (12/1999) 1 4 Abbreviations The Supplement uses the following abbreviations: ATM Asynchronous Transfer Mode BC-N Bearer Control (“I) BC-T Bearer Control (UNI)
35、CC-N Call Control (“I) CC-T Call Control (UNI) LIJ Leaf Initiated Join SN Serving Node J J J J J J J J 5 Table 5- 1 contains the leaf initiated join point-to-multipoint connection(s) information flow definitions that are used across the call control (CC-T to CC-N) and bearer control (BC-T to BC-N) i
36、nterfaces specified in Supplement 7 i. These information flows are used to establish, modify, and release leaf initiated join calls and connections. Information flows used in this Supplement J (Note) J (Note) J (Note) J (Note) J (Note) J (Note) J (Note) J (Note) Table 5-1 - Information flows used fo
37、r leaf initiated join point-to-multipoint Connection(s) Call-Setup Attach-Party-to-Bearer Add-Party- therefore, the “cancel“ information flows are not used. 6 Leaf initiated call registration A root-party has the capability of creating a leaf initiated call registration with its serving node and all
38、 leaf associated serving nodes. This registration illustrates its willingness to be a root of a call allowing another party to join this call and possibly be attached to its (their) associated connection(s). The root-party can register several call instances each of which may be associated with netw
39、ork handling options for future requests rom other parties which wish to be added to the registered leaf initiated join call. The method of handling the leaf initiated join requests rom other parties are specified as part of the registration for each call instance procedure. The methods of 2 Q serie
40、s - Supplement 15 (12/1999) handling the requests can be categorized into two classifications: root-party controlled actions, and network controlled actions. These two classifications are illustrated as follows. 6.1 Root-party controlled actions If the LIJ call join or the LIJ call and bearer reques
41、t contains a valid single party address, pass the request to the root for handling. If multiple LIJ call join requests are received by the network for the same LIJ call and the call is not active, the network will queue all but the first request until the LIJ call has been established to the first r
42、equest. Queued requests then will be sent to the root-party. LIJ call and bearer requests will also be queued if the set of bearers have not been established within the network. 6.2 Network controlled actions 6.2.1 Handling of LIJ call join requests when an active LIJ call has been established If th
43、e LIJ call join request contains a valid single party address, and there is an active LIJ call, add the party to the call. 6.2.2 If the LIJ call and bearer request contains a valid single party address, and there is an active LIJ call and its set of associated bearers has been established, add the p
44、arty to the call and attach the leaf- party to the set of bearers. Handling of LIJ call and bearer requests when an active LIJ call and its set of bearers have been established 6.2.3 If the LIJ call join request or the LIJ call and bearer request contains a valid single party address, pass the reque
45、st to the root for handling. If multiple LIJ call join requests are received by the network for the same LIJ call, the network will queue all but the first request until the LIJ call has been established to the first request. Queued requests will be handled according to the options specified under h
46、andling during active call subclause above. If multiple LIJ call and bearer requests are received by the network for the same LIJ call, the network will queue all but the first request until the LIJ call associated bearers have been established to the first request. Queued requests will be handled a
47、ccording to the options specified under handling during active call and bearers subclause above. Handling of leaf join requests when no active LIJ call is in progress or a LIJ call is active but its set of bearers have not been established 6.2.4 There are notification two options that can be specifi
48、ed by the root-party as to the manner in which leaf-party join request should be handled by the root-partys associated serving node. These options are as follows: Root-party notification options upon completion of join requests o No notification is to be given to root-party when ever the network add
49、s a leaf-party to a If the request contains a valid single party address, notify the root-party that the leaf-party LIJ call. has been added to or deleted fiom the LIJ call. o NOTE - The root serving nodes information is also updated with this option. Q series - Supplement 15 (12/1999) 3 6.3 The registration process may be accomplished via several methods. These methods are described in the following list: 1) Call establishment request (begin or ready) with leaf initiated call registration: When a call establishment request is sent to the network, the root-party will provide
