ITU-T SERIES Q SUPP 17-1999 Technical Report TRQ 2200 Call Control Signalling Requirements - Party Call Control Series Q Switching and Signalling (Study Group 11 56 pp)《技术报告TRQ 220.pdf

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

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 17 (1 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2200: Call control signalling requirements - Party call control ITU-T Q-series Recommendations - Supplement 17 (Former

2、ly 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 SPECIFICAT

3、IONS 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 SATELLI

4、TE 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 O

5、99 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 17 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2200: CALL CONTROL SIGNALLING REQUIREMENTS - PARTY CALL CONTROL Summary This Supplement specifies

6、the signalling requirements for the basic call control capability. The call control functional entity actions are defined in terms of information flows. This Supplement is intended to speciQ the essential UNI and NNI interactions required to develop call control functional entity actions. Source Sup

7、plement 17 to ITU-T Q-series Recommendations, was prepared by ITU-T Study Group 1 1 (1997-2000) and was approved under the WTSC Resolution 5 procedure on 3 December 1999. Q series - Supplement 17 (12/1999) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agenc

8、y 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 telecommunications on a wor

9、ldwide 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 is covered

10、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 indicate bot

11、h 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 concerning t

12、he 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 patents, wh

13、ich 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 utilized in

14、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 17 (12/1999) 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 10.3 Scope . References . Definitions Abbreviations Informa

15、tion flows used in this Supplement Overview of call control level peer-to-peer functional entity actions . Call establishment . Two-party call establishment Establishment of a call with three or more parties Addition of one or more parties to a call Addition of one party to a call Addition of two or

16、 more parties to a call Release of a party fiom an existing call General rules for release of a party . Release of a party fiom an existing two-party call 9.2.1 Release of a party by the call owner - Clear call option 9.2.2 Release of a party by the call owner - Retain call option Release of a party

17、 fiom an existing multiparty call 9.3.1 9.3.2 Release of a party fiom an existing multiparty call requested by the call Release of a party fiom an existing multiparty call requested by the party owner . owner . Release of a call General rules for releasing a call . Release of a call requested by the

18、 call owner . 10.2.1 Release of a single-party call requested by the call owner 10.2.2 Release of a multiparty call requested by the call owner . Release of a call requested by a non-call owner . 10.3.1 Release of a two-party call requested by a non-call owner 10.3.2 Release of a multiparty call req

19、uested by a non-call owner Page 1 2 2 2 2 3 12 12 16 23 23 23 23 26 29 29 32 35 35 36 36 37 42 42 45 . Q series . Supplement 17 (12/1999) 111 Supplement 17 to Q-series Recommendations TECHNICAL REPORT TRQ.2200: CALL CONTROL SIGNALLING (Geneva, 1999) REQUIREMENTS - PARTY CALL CONTROL 1 Scope This Sup

20、plement presents the procedures, information flows and information elements needed for establishment, modification and release of calls without network connection. Network connections may be establishedreleased during a call. However, these network connection additionrelease procedures are covered i

21、n another Technical Report. It should be noted that the procedure of establishingmodifymgreleasing call without any network connections is an advanced service capability that is typically not associated with a “POTS“ voice call. This capability is needed to support non-human intervention type servic

22、es where an end point located user agent will be in charge with the invocation, modification, and release decisions. When an actual bearer service is added to the call via a network connection will the user agent actually notify the end user. Table 1 - 1 illustrates the scope of the call control cap

23、abilities contained within this Technical Report. Table 1-1 - Party call control capability Call establishment without any network connections Establish a call with two parties Establish a call with three or more parties Addition of one or more parties without network connections to an existing call

24、 Add one new party to an existing call requested by any party already associated with that call Add two or more new parties to an existing call requested by any party already associated with that call Release of a party without network connections from an existing call Release of a party from an exi

25、sting two-party call Release of a party from an existing three- or more-party call Release of a call without Network Connections Release of a single-party call requested by the call owner Release of a two-party call requested by the call owner Release of a multiparty call requested by the call owner

26、 Release of a two-party call requested by a non-call owner party Release of a multiparty call requested by a non-call owner party Network connection type NA NA NA NA NA NA NA NA NA NA NA Q series - Supplement 17 (12/1999) 1 2 References The following Technical Reports and other references contain pr

27、ovisions 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; all users of this Supplement are therefore encouraged to investigate the possibility

28、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. 11 ITU-T Q-series Recommendations - Supplement 7 (1999), Technical Report TRQ.2001, General aspects for the developme

29、nt of uniped signalling requirements. 2 ITU-T Q-series Recommendations - Supplement 10 (1999), Technical Report TRQ.2002, Information Flow Elements. 3 Definitions This Supplement defines the following terms: 3.1 3.2 requested signalling capability. 3.3 Supplement 7 i. 3.4 between one call party end

30、point and its serving node. 3.5 3.6 3.7 several party owners within a call. 3.8 control functional entity but no call control functional entity. 3.9 3.10 signalling capability. 3.11 call control and bearer control functional entities. addressed party: The party addressed by the requested signalling

31、capability. addressed serving node: Network equipment associated with the party addressed by the 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- party call end points, or call owner: One who initiate

32、s a call is the call owner. There is only one call owner per call. party: The designation given to an end point associated with a call. 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 contain

33、s a bearer requesting 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 (LEX) or PBX, which contains 4 Abbreviations This Supplement uses the following abbre

34、viations: NA Not Applicable PEP Party End Point 5 Table 5-1 contains the information flows that are used across the call control interfaces illustrated in the Unified Functional Model contained in Supplement 7 i. These information flows are used to establish, modify and release calls and their assoc

35、iated parties. Information flows used in this Supplement 2 Q series - Supplement 17 (12/1999) Table 5-1 - Information flows used for party control capability Add-Party-to-Call Release-Party- fi-om-Call Notify-Call-Change Remote-Release-Party-fi-om Call Release-Call Information Flow I Begin I Ready I

36、 Commit I Cancel I Indication J J J Note J J Note J J J J J Note Call-Setup I J I J I J INoteI I NOTE - Only successful flows are shown. In addition to those information flows defined in Table 5-1, the full set of information flow definitions for B-ISDN can be found in Supplement 10 2. 6 Stage 2 flo

37、ws 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 examples have been chosen in order to illustrate the general principles. The overvie

38、w 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 of a call. Overview of call control level peer-to-peer functional entity actions Figure 6-1 - Two party cal

39、l establishment For the purpose of this overview, the information flows and actions illustrate the establishment of a two-party call, when the requesting party is or will be associated with the specified call. The actions illustrated in Figure 6-1 are described as follows: 1) Signalling service requ

40、est issued by service requester: Receiving entity validates request, modifies internal state information, and then issues action 2. Q series - Supplement 17 (12/1999) 3 2) Relayed signalling service request issued by requesters serving node: Receiving entity validates request, modifies internal stat

41、e information, and then issues the request on the addressed partys interface as action 3. Signalling service request issued by addressed partys serving node: Receiving entity validates request, modifies internal state information, and then issues its response as action 4. Signalling service response

42、 issued by addressed party: Receiving entity records response, modifies internal state information and then relays response as action 5. Relayed signalling service response issued by addressed partys serving node: Receiving entity records response, modifies internal state information and then relays

43、 response to the service requester as action 6. Signalling service response issued by requesters serving node: Requester 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

44、-to-end pictorial representation of the signalling capability in one figure. 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

45、replacing the serving nodes and relay nodes with local serving networks and transit networks. The remaining clauses of this Supplement describe the basic call control signalling capabilities using this model. 3) 4) 5) 6) 7 Call establishment The establishment of a call has two variations, establishi

46、ng a call between two parties and establishing a call with more than two parties. These examples illustrate the necessary information to be carried in order that at the end of the example, each serving node associated with the call, contains a dull description of the call. In many service scenarios,

47、 the full description of the call is not necessary, however, it was felt the illustrations of a more complete signalling procedure would allow simplified variations to be constructed. 7.1 Two-party call establishment Party A requests a two-party call with party B. If party B, or party Bs agent, dete

48、rmines that the call establishment request can be accepted, the agent will indicate acceptance of the call establishment request. This is illustrated in Figure 7- 1. T11109I- Figure 7-1 - Call transition diagram 4 Q series - Supplement 17 (12/1999) The signalling capability of establishing this call

49、 between the two parties is illustrated in Figure 7-2. Figure 7-2 - Call establishment of a two-party call The actions illustrated in Figure 7-2 are as follows: Requesting partys terminal equipment issues the following information flow towards its serving node and awaits the acknowledgement of the request. 1 Call-Setup.ready Party A to Serving Node A Resource information Call information Bearer information Session ID Call Control Segment ID, Addressed party Information Requesting party information PEP 73 ID, Network address, PEP “A” ID, Network Address Initiat