1、STD-ITU-T RECMN SERIES Q SUPP 10-ENGL 1997 48b2591 Ob83852 T7T INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series Q Supplement 1 O (I 2/1999) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2002: Information Flow Elements ITU-T Q-series Recomme
2、ndations - Supplement I O (Formerly CCITT Recommendations) _ STDOITU-T RECMN SERIES Q SUPP LO-ENGL 1999 48b259L Ob83853 90b = ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORM
3、ATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 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 BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q. I -Q.3 Q.4-Q.59 Q. 1 OO-Q. I 1 9 Q.120- Q.249 Q.
5、250- Q.309 Q.310-Q.339 Q .60-Q. 99 Q.400-Q .499 Q. 500-(2.599 Q.60- Q.699 Q .70O-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 refer to ITU-T Lis of Recommendations. STD-ITU-T RECMN SERIES Q SUPP LO-ENGL L999 48b259L Ob83854
6、 842 SUPPLEMENT 10 TO ITU-T Q-SERIES RECOMMENDATIONS TECHNICAL REPORT TRQ.2002: INFORMATION FLOW ELEMENTS Summary This Supplement specifies the information flow elements that will be used in the development of the TRQ.2xxx series of signalling requirements. The content of the information flow elemen
7、ts are based on the general aspects as defined in the Supplement 7 - Technical Report TRQ.2001: General aspects for the development of unified signalling requirements. Source Supplement 10 to ITU-T Q-series Recommendations was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the W
8、TSC Resolution No. 5 procedure on 3 December 1999. STDOITU-T RECMN SERIES Q SUPP LO-ENGL b999 W 48b2591 Ob83855 789 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-
9、T) is a permanent organ of the ITU. The IT-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 Standardization Conference (WTSC), which meets ever
10、y 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 No. 1. In some areas of information technology
11、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 recognized operating agency. INTELLECTUAL PROP
12、ERTY 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 claimed Intellectual Property Rights, whether a
13、sserted 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 publication. However, implementors are cautioned th
14、at 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, including,photocopying and microfilm,
15、 without permission in writing fi-om the ITU. 1 2 3 4 5 5.1 5.2 6 Scope Normative References Definitions Abbreviations . Information flow principles Information flows and FE actions for release one service Information flow conventions for capability set three services 5.2.1 Convention of reference d
16、irection . 5.2.2 Convention for ATM switch through 5.2.3 Information flow terminology . Description of information flow elements 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 6.1.9 6.1.10 6.1.11 6.1.12 6.1.13 6.1.14 6.1.15 6.1.16 6.1.17 6.1.18 6.1.19 6.1.20 6.1.21 6.1.22 6.1.23 6.1.24 6.1.25 6.1.2
17、6 Call- 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 published. i ITU-T Q-series Recommen
18、dations - Supplement 9 (1999), Technical Report TRQ.2000: Roadmap for the TRQ.2m-seres Technical Reports. 2 ITU-T Q-series Recommendations - Supplement 7 (1999), Technical Report TRQ.2001: General aspects for the development of unijed signalling requirements. 3 Definitions This Supplement defines th
19、e following terms: 3.1 3.2 requested signalling capability. 3.3 capability. 3.4 Table 1-4/TRQ.2001 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.10 3.11 signal
20、ling capability. 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 addressed party to the party requesting a signalling network connection: An ATM network
21、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 one Call Owner per forward: The direction from the requesting party to the addressed party.
22、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 requesting a signalling capability. requesting serving node: Network equipment associated with th
23、e party requesting a 3.12 which contains call control and bearer control functional entities. serving node: Network equipment, such as a local exchange or private branch exchange, DCA LC - 4 Abbreviations This Supplement uses the following abbreviations: NA Not Applicable PEP Party End Point DC EC -
24、_- EC DCA LC LC LC LC 5 Information flow principles 5.1 The information flows and functional entity actions are covered in Recommendation Q.71. Information flows and FE actions for release one service 5.2 The drawing conventions associated with user plane and control plane reference direction, ATM s
25、witch through, symbology used to describe functional entity actions during connection establishment are contained in the following figures. Information flow conventions for capability set three services 5.2.1 Convention of reference direction See Figure 5-1. m a Requesting User TE Requesting Serving
26、 Node - I I Addressed Serving Node Addressed User TE I I - - I I Forward - I - TI 1108920-00 . - Backward Figure 5-1 - Reference Direction Convention Requesting Serving Node is associated with the user terminal requesting a signalling capability. Addressed Serving Node is associated with the user te
27、rminal addressed by the requested signalling capability. Incoming side of a Node is the side closest to the user terminal requesting a signalling capability. Outgoing side of a node is the side closest to the user terminal addressed by the requested signalling capability. Forward direction is fi-om
28、the requesting user terminal to the addressed user terminal. Backward direction is from the addressed user terminal to the user terminal requesting a signalling capability. STDmITU-T RECMN SERIES Q SUPP LO-ENGL 1799 48bi59L Ob838b0 04b The reference to the incoming side and outgoing side is independ
29、ent of the direction of transport of user data. When a call establishment signalling action has been requested, then the requesting user TE becomes the originating user TE and the requesting serving node becomes the originating serving node. In the same instance, the addressed user TE becomes the te
30、rminating user and the addressed serving node becomes the terminating serving node. However, when other signalling capabilities are invoked, the above convention is more useful since these actions could be invoked by a party that did not originate the call. 5.2.2 Figure 5-2 illustrates the switch co
31、nvention to be used in the handling of ATM connections within a network node. Convention for ATM switch through - User Plane I incoming I Outgoing I T11108930-( Control Plane -9- Figure 5-2 - Convention for ATM switch through The “BC“ is responsible for bandwidth reservation, bandwidth allocation, c
32、onnection switch through, connection release, and bandwidth release in the forward and backward direction. 5.2.3 Information flow terminology The terminology for information flows to be used in the stage 2 representation of the signalling capability sets are covered in this subclause. The signalling
33、 information flows are based on the two “generic“ information flow sequences illustrated below. It is useful to conceive for the exchange of information between peer functional entities in terms of both one-phase and two-phase interactions. The one-phase mechanism is analogous to the two message req
34、uestlresponse approach, while the two-phase is analogous to the CCR begin/ready/commit. Both of these mechanisms can be combined into a single one using CCR terminology as shown below. All peer-to-peer exchanges are defined in terms of a superiorhbordinate relationship according to the following def
35、initions: 5.2.3.1 superior: The entity that ultimately decides on the commitment. 5.2.3.2 subordinate: The peer of the supenor. The type A request (one phase mechanism) consists of the following exchange. The requesting functional entity, acting as a subordinate, signals its peer with X.ready - wher
36、e X represents the action to be performed. If the requested operation is successful, the superior functional entity shall complete the requested action and noti the subordinate functional entity that the action STD-ITU-T RECMN SERIES Q SUPP 10-ENGL 1999 48b2591 Ob83863 TB2 has been completed with X.
37、commit. If the action cannot be completed, the superior functional entity will notify the subordinate functional entity that the action was not completed with X.cance1. This is shown in the information flow in Figure 5-3 below: Subordinate Subordinate X.ready X.commit i Superior Superior Completed A
38、ction Non-completed Action T1110894-O Figure 5-3 - Information flows for single-phase request mechanism The type B request (two-phase mechanism) consists of the following exchange. The requesting functional entity, acting as a superior, signals its peer with X.begin. If the request will be able to b
39、e completed, the subordinate functional entity shall noti6 the superior functional entity of this condition with X.ready and wait for further instructions from the superior functional entity before the requested action is completed. The superior may respond with either a flow that indicates that the
40、 action shall be completed (X.commit) or with a flow that indicates that the receiver shall disregard the requested action (X.cance1). If the requested operation is not successful, the subordinate functional entity shall notify the superior functional entity with X.cance1. These flows are illustrate
41、d below in Figure 5-4. Superior Subordinate Completed Action Superior Superior Subordinate Non-completed Action Subordinate Disregard Action T11108960-00 Figure 5-4 - Information flows for two-phase request mechanism Figures 5-5 and 5-6 illustrate where the one-phase and two-phase mechanism are used
42、. - - STD-ITU-T RECMN SERIES Q SUPP LO-ENGL 1999 W 4862591 Ob838b2 717 UNI X.ready I Sub SUP X.commitB(.cancel I NNI X.readv Sub SUP X.commitB(.cancel UNI X.begin SUP Sub X.ready/X.cancel I X.commitB(.cancel I T1110896(MO Figure 5-5 - UNUNNI flows with one-phase request on NNI UNI L X.ready X.begin
43、X.begin I X.readyB(.cancel 1 X.ready/X.cancel - X.commitB(.cancel L X.commitB(.cancel w b T1 ll970-00 Figure 5-6 - UNUNNI flows with two-phase request on NNI In Figure 5-5, the one-phase mechanism is used at the calling (or requesting) users side, and both the one-phase and the two-phase mechanisms
44、are used at the called (or confirming) users side. Either mechanism can be employed at the “I, depending on which side should have the ultimate authority to commit. The authority is generally transferred to the called user side when there is a single mandatory party. -F -1 + -1- - -1- -+ ,II r- I w
45、1 1 1 - 1 1 Case 1 - Single Terminating Party - Type B flows at terminating side w Broadcast Service Offenne _* d I= d d 1 w 1 1 w w 1 Case 2 - Single Terminating Party - Type A flows at terminating side w 1 d d TE 1 w d Case 3 -Multiple Terminating Parties - Type B flows at terminating side cc/Bcl
46、T11108980-00 Figure 5-7 - Flows illustrating conversion of X.ready to X.begin An unconfirmed information flow has also to be considered e.g. in order to support the notification capability items. The set of mechanisms may be executed e.g. in order to cover user-to-user negotiation of U-plane attribu
47、tes. It should be noted that for human non-interactive based services, the generic information flow sequence is terminated by either a single X.cance1, or one X.commit information flow. - STD-ITU-T RECMN SERIES Q SUPP LO-ENGL 1999 - Li862591 06838b4 791 6 Table 6-1 contain the information flows sequ
48、ences to be used in the specification of the stage 2 flows. The table associates each information flow “Action“ with the signalling capabilities and the signalling plane which carries these infomation flow sequences. Description of information flow elements Remote-Add-Party-to-Bearer Remote-Attach-P
49、arty-to-Bearer Remote-Add-Party-; LC BC L Serving Node r14 ml I I l I I Relay Node Serving Node TE TI110899000 Figure 6-6 - Information relationships in broadband functional Signalling model Table 6-2 illustrates parameters to be used for either or both link and edgehd-to-end signalling control. All the parameters discussed in this subclause may not have one-to-one mapping to stage 3 protocol information elements. Direct Call association Addressed party Information PEP “x“ ID Both LC/EC - M - -M- BothLCEC
