ITU-T SERIES Q SUPP 18-1999 Technical Report TRQ 2230 Call Control Signalling Requirements for Join Call Service Series Q Switching and Signalling (Study Group 11 44 pp)《技术报告TRQ 22.pdf

《ITU-T SERIES Q SUPP 18-1999 Technical Report TRQ 2230 Call Control Signalling Requirements for Join Call Service Series Q Switching and Signalling (Study Group 11 44 pp)《技术报告TRQ 22.pdf》由会员分享，可在线阅读，更多相关《ITU-T SERIES Q SUPP 18-1999 Technical Report TRQ 2230 Call Control Signalling Requirements for Join Call Service Series Q Switching and Signalling (Study Group 11 44 pp)《技术报告TRQ 22.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 18 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2230: Call control signalling requirements for Join Call service ITU-T Q-series Recommendations - Supplement 18 (Forme

2、rly 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 SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICA

3、TIONS 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 LAND MOBILE NETWORK INTERWORKING WITH SATELL

4、ITE 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.699 Q.700-Q.849 Q.850-Q.999 Q. 1000-Q. 1

5、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 18 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2230: CALL CONTROL SIGNALLING REQUIREMENTS FOR JOIN CALL SERVICE Summary This Supplement specifie

6、s the signalling requirements for the Join Call (call only) service capability. These signalling requirements cover the UNI and NNI interactions (exchange of information flows) and internal serving node procedure requirements for a serving node associated with a joining party and associated with the

7、 call registering party. The signalling requirements include registered call creation (without network connections), attachment of new parties by themselves (“join call“), and detachment of parties by the call registering party or by themselves. Source Supplement 18 to ITU-T Q-series Recommendations

8、 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 18 (12/1999) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU

9、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 telecommunications on a worldwide basis. The World Telecommunication Stan

10、dardization 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

11、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 indicate both a telecommunication administration and a rec

12、ognized 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 concerning the evidence, validity or applicability of clai

13、med 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 patents, which may be required to implement this publicat

14、ion. 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 utilized in any form or by any means, electronic or mechan

15、ical, including photocopying and microfilm, without permission in writing fi-om the ITU. 11 Q Series - Supplement 18 (12/1999) CONTENTS 1 2 3 4 5 6 6.1 6.2 6.3 6.4 7 8 9 9.1 9.2 Scope . References . Definitions Abbreviations Information flows used in this Supplement Registered call registration . Ca

16、ll registering party controlled actions . Network controlled actions . 6.2.1 Handling of call join requests when an active registered call has been established . 6.2.2 Handling of call join requests when no active registered call exists . 6.2.3 Call initiating party notification options upon complet

17、ion of join requests Registration process for an initiators serving node Registration process for a joining partys serving node Serving node Call Join procedures . Overview of Peer-to-Peer Functional Entity Actions . Functional Entity Actions . Registered Call Creation . 9.1.1 Call Initiating Party

18、Request to Create a Registered Call (without attachment of a another Party) . 9.1.2 Call Initiating Party Request to Create a Registered Call (with attachment of another Party) 9.1.3 Joining Party Request to Join a Registered Call - No Active Call Joining Party Request to Join Active Registered Call

19、 9.2.1 Joining Party Request to Join Active Call in Initiators Serving Node - Initiator Screening . 9.2.2 Joining Party Request to Join Active Call in Initiators Serving Node - 9.2.3 Party Request to Join Active Call in a Joining Partys Serving Node - Initiator Screening . 9.2.4 Party Request to Joi

20、n Active Call in a Joining Partys Serving Node - Removal of Party from a Registered Call requested by the Call Initiating Party 9.3.1 Removal of party requested by call initiating party - (multiple parties attached to registered call at joining partys serving node) 9.3.2 Removal of a party requested

21、 by call initiating party (single party attached to registered call at joining partys serving node) . Network Screening Network Screening Q Series . Supplement 18 (12/1999) Page 1 1 1 2 2 2 2 2 6 7 7 10 10 10 13 13 16 16 18 . 111 Page 9.3.3 Removal of a party requested by call initiating party (last

22、 party attached to Party Requests to be Released fiom the Registered Call 24 9.4.1 Party release request (multiple parties attached to registered call at joining partys serving node) 24 9.4.2 Party release request (single party attached to registered call at joining partys serving node) . 27 9.4.3 2

23、9 registered call) . 21 9.4 Party release request (last party attached to registered call) . 9.5 Registered Call Release by Call Initiating Party . 32 associated parties) 32 other serving nodes associated with the registered call). . 9.5.1 9.5.2 Call Initiating Party Requests to Terminate Registered

24、 Call (with no Call Initiating Party Requests to Terminate Registered Call (with several 34 iv Q Series - Supplement 18 (12/1999) Supplement 18 to Q-series Recommendations TECHNICAL REPORT TRQ.2230: CALL CONTROL SIGNALLING REQUIREMENTS FOR JOIN CALL SERVICE (Geneva, 1999) 1 Scope This Supplement pre

25、sents the procedures, information flows and Information Elements needed for supporting calls containing call registering party screened and network screened registered call joins. 2 References The following Technical Reports and other references contain provisions which, through reference in this te

26、xt, constitute provisions of this Supplement. At the time 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 s

27、upplements and other references listed below. A list of the currently valid ITU-T Recommendations and supplements is 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

28、 Q-series Recommendations - Supplement 10 (1999), Technical Report TRQ.2002: Information flow elements. 3 ITU-T Q-series Recommendations - Supplement 17 (1999), Technical Report TRQ.2200: Call control signalling requirements for party call control. 3 Definitions This Supplement defines the following

29、 terms: 3.1 join call: Supplement 18 to Q-series Recommendations allows a party to join a call. This “Special Call Association“ is called Join Call; it is referenced by a joining party via a unique “Registered Call ID“. The following three types of Registered Calls are differentiated. 3.2 registered

30、 calls with initiator screening: The call registering party (initiator) receives a joining setup request for every party that wishes to join the call, then either creates the call or adds the party to the ongoing call. The initiator has the option of rejecting any join attempt. When using this mode,

31、 the network never automatically joins parties to the call. 3.3 registered calls network screening with initiator notification: The call registering party (initiator) creates the call as a registered join call, then the network automatically attempts to add all parties to the call that request to be

32、 added. After each party completes joining the registered call, the initiator receives a notification about the event. 3.4 registered calls network screening without initiator notification: The call registering party (initiator) creates the call as a registered join call, then the network automatica

33、lly attempts to add all parties to the call that request to be added. In this case, the initiator gets no indication when parties are added by the network. Q Series - Supplement 18 (12/1999) 1 4 Abbreviations This Supplement uses the following abbreviations: ATM Asynchronous Transfer Mode CC-N Call

34、Control (“I) CC-T Call Control (UNI) SN Serving Node Notify-Party-Change 5 Table 5-1 contains the registered join information flow definitions that are used across the call control (CC-T to CC-N) interfaces specified in Supplement 10 2. These information flows are used to establish, modify, and rele

35、ase registered join calls. Information flows used in this Supplement J Table 5-1 - Information Flows used to join Registered Call(s) Information Flow I Begin I Ready I Commit I Cancel I Indication I Call-Setup I J I J I J I (Note) I I Join-Call I J I J I J I (Note) I I Release-Party- fi-om-Call I I

36、J I J I (Note) I I Release-Call I I J I J I (Note) I I 6 Registered call registration Any party has the capability of creating a call registration with its serving node that other parties may join. This registration illustrates its willingness to maintain a call allowing another party to join this c

37、all. This party can register several call instances each of which may be associated with network handling options for future requests rom other parties which wish to be added to the registered call. The method of handling the join requests rom other parties are specified as part of the registration

38、for each call instance procedure. The methods of handling the requests can be categorized into two classifications; call registering party (initiator) controlled actions, and network controlled actions. These two classifications are illustrated as follows. 6.1 If the call join request contains a val

39、id single party address, pass the request to the call initiator for handling. If multiple call join requests are received by the network for the same registered call and the call is not active, the network will queue all but the first request until the registered call has been established to the fir

40、st request. Queued requests then will be sent to the initiating party. Call registering party controlled actions 6.2 Network controlled actions 6.2.1 Handling of call join requests when an active registered call has been established If the call join request contains a valid single party address, and

41、 there is an active registered call, add the party to the call. 2 Q Series - Supplement 18 (12/1999) 6.2.2 If the call join request contains a valid single party address, pass the request to the call initiator for handling. If multiple call join requests are received by the network for the same regi

42、stered call, the network will queue all but the first request until the registered call has been established to the first request. Queued requests will be handled according to the options specified under handling during active call subclause above. Handling of call join requests when no active regis

43、tered call exists 6.2.3 There are two notification options that can be specified by the call initiating party as to the manner in which party join request should be handled by the call initiating partys associated serving node. These options are as follows: Call initiating party notification options

44、 upon completion of join requests o No notification is to be given to call initiating party when the network adds a joining party to If the request contains a valid single party address, notify the call initiating party that the a registered call. joining party has been added to or deleted rom the r

45、egistered call. o NOTE - The initiators serving nodes information is also updated with this option. 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 call registration: When a c

46、all establishment request is sent to the network, the call initiating party will provide the registered call ID and Service Characteristics to the network for the registration. The local call control segment ID will be associated with the registered call ID in order to provide trace-ability. Add par

47、ty request (begin or ready) with call join registration: When an add party request is sent to the network, the call initiating party will provide the registered call ID and service characteristics to the network for the registration. The local call control segment ID will be associated with the regi

48、stered call ID in order to provide trace-ability. Registration process for an initiators serving node 2) 6.4 The registration process methods for a joining partys serving node are as follows: 1) Call establishment acceptance (commit) with call join registration: When a call establishment acceptance

49、is received by the network rom a joining party Basic Call state Model (BCSM), the registered call ID and service characteristics received rom the initiating partys serving node via the call establishment request will be used for the joining partys serving node registration process. The local call control segment ID between the network and the joining party will be associated with the registered call ID in order to provide trace- ability. Add party acceptance (commit) with call join registration: When an add party acceptance is received by the network rom a join