1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.1902.6 (07/2001) SERIES Q: SWITCHING AND SIGNALLING Specifications of signalling related to Bearer Independent Call Control (BICC) Bearer Independent Call Control protocol (Capability Set 2): Generic signal
2、ling procedures for the support of the ISDN user part supplementary services and for bearer red i rect ion ITU-T Recommendation Q. 1902.6 (Formerly CCITT Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTER?XATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION
3、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 R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 4
4、3 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STAND- SYSTEMS Q. 1-4.3 4.4-4.59 Q.60-Q.99 Q. 10O-Q. 119 Q. 120-4.249 4.250-
5、4.309 4.310-4.399 4.400-4.499 Q. 500-Q. 599 Q.600-Q.699 4.700-4.799 Q.80O-Q.849 Q.850-Q.999 Q.lOOkQ.1099 Q. 1100-Q. 1 199 Q. 1200-Q. 1699 II SIGNALLING REOUIREMENTS AND PROTOCOLS FOR IMT-2000 O. 1700-0.1799 . . . SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL Q.190w.1999 II CONTROL
6、(BICC) Q.2000-4.2999 II ISDN For further details, please refer to the list of ITU-T Recommendations. ITU-T Recommendation 4.1902.6 Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures for the support of the ISDN user part supplementary services and for bearer re
7、direction Summary This Recommendation specifies the generic signalling procedures and support of the Signalling System No. 7 ISDN User Part (ISUP) supplementary services by the Bearer Independent Call Control (BICC) protocol. The details for the support of the ISUP supplementary services by BICC are
8、 described as delta documentation against the ITU-T Q.73-series Recommendations. In addition, BICC CS-2 procedures for bearer redirection are introduced to optimize the bearer path. Source IT-T Recommendation 4.1902.6 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resol
9、ution 1 procedure on 2 July 200 1. ITU-T RC. Q.1902.6 (07/2001) 1 FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is respo
10、nsible 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 Assembly (WTSA), which meets every four years, establishes the topics for study by the I
11、TU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborati
12、ve basis with IS0 and EC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL, PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementati
13、on of this Recommendation may involve the use of a claimed Intellectual Property Right. 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 Recommendation development process. As of
14、 the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to
15、 consult the TSB patent database. o ITU 2002 Ail 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, without permission in writing fi-om ITU. .I 11 ITU-T RC. 4.1902.6 (07/2001) CONTENT
16、S Page 1 2 3 4 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 6 Scope . References . Definitions Abbreviations Delta documentation against ITU-T 4.73-series Recommendations . Delta 4.730 - Generic procedures Delta 4.73 1 - Number Identification supplementary services . Delta 4.732 - Call Offering supplementary s
17、ervices . 5.3.1 Handling of Hop Counter with the Call Diversion supplementary services . 5.3.2 Handling of Global Call Reference with the Explicit Call Transfer supplementary services Delta 4.733 - Call Completion supplementary services 5.4.1 Delta 4.734 - Multiparty supplementary services . 5.5.1 H
18、andling of Global Call Reference with the Multiparty supplementary services Delta 4.735 - Community of Interest supplementary services 5.6.1 TC-based signalling transport with the Community of Interest supplementary services TC-based signalling transport with the Call Completion supplementary servic
19、es Delta 4.736 - Charging supplementary services 5.7.1 TC-based signalling transport with the Charging supplementary services . Delta 4.737 - Additional Information Transfer supplementary services . Bearer Redirection 6.1 Introduction . 6.2 Interaction with services invoking bearer redirection . 6.3
20、 Cut-through of new bearer connection . 6.4 Use of BAT ASE 6.5 Procedures . 6.5.1 Indication of Bearer Redirection Capability 6.5.2 Bearer redirection takes place in the same direction as the call 6.5.3 Redirection takes place in the opposite direction to the original call set.up . 6.5.4 Special Cas
21、es . 6.5.5 6.5.6 Interaction with Redirection (national use) . Interaction with Pivot Routing 1 i 2 2 5 5 5 5 6 6 6 6 6 8 8 9 9 9 12 12 14 14 ITU-T Rc . 4.1902.6 (07/2001) iii ITU-T Recommendation Q.1902.6 Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures for
22、 the support of the ISDN user part supplementary services and for bearer redirection 1 Scope This Recommendation specifies details about the procedures for the generic signalling procedures and support of the Signalling System No. 7 ISDN User Part (ISUP) supplementary services by the Bearer Independ
23、ent Call Control (BICC) protocol. For the generic signalling procedures, services and functions supported by the BICC protocol (as listed in Table 2/Q.1902.1 4) and already supported by the ISUP protocol, the BICC protocol is fully transparent, i.e. the BICC protocol is fully compatible with the ISU
24、P protocol. These generic signalling procedures, services and functions as supported by the ISUP protocol are specified in the ITU-T Q.73-series Recommendations i. The details for the support of the ISUP supplementary services by the BICC protocol are described as delta documentation against the lTU
25、-T Q.73-series Recommendations. i. All references in the ITU-T Q.73-series to the basic call procedures in ITU-T 4.761-4.764 2 and 4.767 3 shall be read as references to the equivalent procedures of the BICC protocol in ITU-T Q.1902.x-family 4. In addition, BICC CS-2 procedures for bearer redirectio
26、n are introduced to optimize the bearer path. These procedures are described in clause 6. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the edit
27、ions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently vali
28、d ITU-T Recommendations is regularly published. 11 ITU-T Q.73-series (2000), ISDN User Part supplementary services generic procedures and clauses with procedures for the individual supplementary services. 2 ITU-T 4.761 to 4.764 (2000), SpeciJications of Signalling System No. 7 ISDN User Part 3 ITU-T
29、 4.767 (1991), Application of the ISDN User Part of CCIITSignalling System No. 7 for international ISDN interconnections. 4 ITU-T Q. 1902.1 to Q. 1902.4 (200 i), Specijkations of the Bearer Independent Call Control Protocol (BICC). 5 ITU-T Q.2150.0 (2001), Generic Signalling Transport Service. 6 ITU
30、-T 4.2 150.1 (200 1), Signalling Transport Convertor on MTP3 and MTP3b. 7 ITU-T 4.765.5 (2000) and its Amendment (2001) for BICC CS-2, Application Transport Mechanism: Bearer Independent Call Control (BICC). (ISUP). EU-T Re. 4.1902.6 (07/2001) 1 3 Definitions For BICC specific terminology, the reade
31、r is referred to ITU-T Q. 1902.1 4. BC-Anchor node: see 6.2. CC-Anchor node: see 6.2. Redirecting-from node: see 6.2. Redirecting-to node: see 6.2. 4 Abbreviations This Recommendation uses the following abbreviations: 3PTY ACM APM APP ASE BAT BCF BICC BIWF CCBS CCNR CD CFB CFNR CFU CMN CON CONF CSF
32、CUG ECT GSN IAM ISDN EN ISUP ITCC PCI Three-Party Service Address Complete Message Application Transport Message Application Transport Parameter Application Service Element Bearer Association Transport Bearer Control Function Bearer Independent Call Control Bearer Interworking Function Completion of
33、 Calls to Busy Subscriber Completion of Calls on No Reply Call Deflection Call Forwarding Busy Call Forwarding No Reply Call Forwarding Unconditional Call Mediation Node Connect message Conference Calling Call Service Function Closed User Group Explicit Call Transfer Gateway Serving Node Initial Add
34、ress Message Integrated Services Digital Network Intermediate Serving Node ISDN User Part International Telecommunication Charge Card Protocol Control Indicator handled by the procedures for existing bearers with respect to the old connection. Where it is required to send an APP parameter relating t
35、o the old connection, this shall be sent as for the non-bearer redirection case. Where it is required to send an APP parameter relating to the new connection, a Bearer Redirection Indicator “New connection identiJer“ shall also be included. 6.5.2.2.2.2 Confirmation and Cut-Through of the new bearer
36、connection If the Bearer Redirection Indicators information element received with the bearer redirection request indication in 6.5.2.2.1 above did not include “late cut-through requested“, then the newly established bearer connection is cut-through immediately it is established, according to the nor
37、mal connection Set-up procedures. On completion of the outgoing Set-up procedure then except in the case of Forward Set-up with Connect Type set to “Forwards Notzfl, the BC-Anchor node shall send a BICC-Data request primitive with Action Indicator set to “Bearer Redirect“ and including Bearer Redire
38、ction Indicator “redirect bearer connected to the CC-Anchor node. In the case of Forward Set-up with Connect Type set to “Forwards Notzfl the BC-Anchor node shall behave as described in the normal Forwards Set-up procedures. E the Bearer Redirection Indicators information element received with the b
39、earer redirection Request indication in 6.5.2.2.1 above indicated “late cut-through requested, then, on receipt of a BICC-Data indication primitive (corresponding to any message) with action indicator set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect cut-through request,
40、the BC-Anchor node cuts through the new bearer connection. ITU-T RW. 4.1902.6 (07/2001) 11 6.5.2.2.3 On receipt of an APM fiom the succeeding node with the action indicator in the BICC-Data indication primitive set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect release req
41、uest“ the BC-Anchor requests the BCF to disconnect the internal through-connection of the old bearer path connection between the BC-Anchor and the Redirecting-from node. A normal cause value is passed from the CSF to the BCF. At the same time as the start of the release of the switched path, the BC-
42、Anchor sends an APM to the succeeding node with the action indicator in the BICC-Data request primitive set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect release proceed. The BC-Anchor awaits receipt of an APM from the succeeding node with the action indicator in the BICC
43、-Data indication primitive set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect release complete“. On receipt of this indication, the BC-Anchor instructs the BCF to release remaining resources associated with the old bearer connection. Release of old bearer connection 6.5.2.
44、3 An intermediate node that is not a BC-Anchor or a CC-Anchor node shall pass on unchanged all received indications related to bearer redirection. In the case that the Bearer Redirection Capability information element was sent to the succeeding node at call Set-up, then on receipt of a BICC-Data ind
45、ication fiom the preceding node with Action Indicator set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect release proceed, the node shall note that Bearer Release should be expected. Subsequent to receipt of this Bearer Release, the node shall behave according to the CMN pr
46、ocedures. NOTE - In the case that the Bearer Redirection Capability information element was not sent to the succeeding node at call Set-up, then this scenario will not occur, since the succeeding node will not invoke Bearer Redirection. Actions at an intermediate node which is not a BC-Anchor or CC-
47、Anchor node 6.5.2.4 A Redirecting-to node shall follow the normal call Set-up procedures described in ITU-T 4.1902.4 Actions at a Redirecting-to node r41. 6.5.2.5 A Redirecting-from node shall follow the normal call Set-up procedures described in IT-T 4.1902.4 4. Actions at a Redirecting-from node 6
48、.5.3 The procedures in 6.5.2 apply with the word “preceding“ replaced by “succeeding and vice versa. 6.5.4 Special Cases Redirection takes place in the opposite direction to the original call Set-up 6.5.4.1 The following procedures ensure that multiple bearer redirection requests sent along the same
49、 call leg are handled in series rather than in parallel. A CC-Anchor node may not initiate more than one bearer redirection procedure at a time for a given call. A CC-Anchor node that receives a bearer redirection request from the succeeding node while waiting for the response to a bearer redirection request sent to the preceding node shall return to the succeeding node a BICC-Data indication primitive (corresponding to an APM) with the Action Indicator set to “Bearer Redirect“ and including Bearer Redirection Indicator “redirect tempora
