ITU-T Q 1902 4 AMD 3-2006 Bearer Independent Call Control protocol (Capability Set 2) Basic call procedures Amendment 3 Support for the International Emergency Preference Scheme (S.pdf

1、 International Telecommunication Union ITU-T Q.1902.4TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 3(01/2006) SERIES Q: SWITCHING AND SIGNALLING Specifications of signalling related to Bearer Independent Call Control (BICC) Bearer Independent Call Control protocol (Capability Set 2): Bas

2、ic call procedures Amendment 3: Support for the International Emergency Preference Scheme ITU-T Recommendation Q.1902.4 (2001) Amendment 3 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING

3、Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNAL

4、LING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799

5、SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) i ITU-T Recommendation Q.1902.4 Bearer Independent Call Control p

6、rotocol (Capability Set 2): Basic call procedures Amendment 3 Support for the International Emergency Preference Scheme Summary This amendment was produced to meet the need for the implementation of the International Emergency Preference Scheme (IEPS) for disaster recovery operations as specified in

7、 ITU-T Rec. E.106. It contains the modifications to ITU-T Rec. Q.1902.4 (2001) in order to accommodate these needs. This amendment should be read in conjunction with Amendment 2 to ITU-T Rec. Q.1902.1, Amendment 3 to ITU-T Rec. Q.1902.2, and Amendment 3 to ITU-T Rec. Q.1902.3. This amendment incorpo

8、rates Amendment 1 to ITU-T Rec. Q.1902.4 and provides enhancements. Source Amendment 3 to ITU-T Recommendation Q.1902.4 (2001) was approved on 27 January 2006 by ITU-T Study Group 11 (2005-2008) under the WTSA Resolution 1 procedure. ii ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) FOREWORD The Interna

9、tional 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 responsible for studying technical, operating and tariff questions and issuing Recommendati

10、ons 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 ITU-T study groups which, in turn, produce Recommendations on these topics. The approva

11、l 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 collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration

12、“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance wi

13、th the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is requir

14、ed of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation 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 Intellectu

15、al Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of 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. Howe

16、ver, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. I

17、TU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) iii CONTENTS Page 1) Clause 4 Abbreviations 1 2) Clause 7.2.2.3 Actions required at an intermediate international SN 1 3) Clause 7.2.3.3 Actions required at an intermediate international CMN 1 4) Clause 7.2.4.3 Actions required at an outgoing international g

18、ateway SN . 2 5) Clause 7.2.5.3 Actions required at an outgoing international gateway CMN . 2 6) Clause 7.2.6.3 Actions required at an incoming international gateway SN 3 7) Clause 7.2.7.3 Actions required at an incoming international gateway CMN 3 8) Clause 7.4 Outgoing bearer set-up procedure 3 9)

19、 Clause 7.5 Incoming bearer set-up procedure . 4 10) New clause 7.4.6 Polling at an international SN for IEPS calls. 4 11) New clause 7.5.6 Polling at an international SN for IEPS calls. 4 12) New clause 8.23 IEPS call information 5 13) Annex A Timers 6 ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) 1 I

20、TU-T Recommendation Q.1902.4 Bearer Independent Call Control protocol (Capability Set 2): Basic call procedures Amendment 3 Support for the International Emergency Preference Scheme 1) Clause 4 Abbreviations Add the following new abbreviations alphabetically: CPC Calling Partys Category IEPS Interna

21、tional Emergency Preference Scheme 2) Clause 7.2.2.3 Actions required at an intermediate international SN Add the following: b) International Emergency Preference Scheme: i) If the CSF, at an intermediate international SN, receives a call with CPC set to IEPS, the call establishment proceeds with pr

22、iority. The call is established with the CPC set as IEPS call marking in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. ii) For an IEPS-call, the codec negotiation procedure

23、s are not to be invoked. If codec negotiation is already invoked on a preceding bearer path, the SN shall terminate the codec negotiation procedures and the call shall proceed. iii) If routing procedures fail to find an outgoing CIC value, the call is queued and shall take precedence over any other

24、normal call attempts. iv) Optionally, if queuing occurs, an early ACM (called party status set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the preceding CSF. However, if the incoming IAM had indicated “COT to be expec

25、ted“, the early ACM (no indication) shall not be sent until Continuity Message (COT) with Continuity Indication has been received. 3) Clause 7.2.3.3 Actions required at an intermediate international CMN Add the following: b) International Emergency Preference Scheme: i) If the CSF, at an intermediat

26、e international CMN, receives a call with CPC set to IEPS, the call establishment proceeds with priority. The call is established with the CPC set as IEPS call marking in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, Automatic Congestion Control, Hard-to-Re

27、ach procedure) are not applied to this call. ii) If routing procedures fail to find an outgoing CIC value, the call is queued and shall take precedence over any other normal call attempts. 2 ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) iii) Optionally, if queuing occurs, an early ACM (called party sta

28、tus set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the preceding CSF. However, if the incoming IAM had indicated “COT to be expected“, the early ACM (no indication) shall not be sent until Continuity Message (COT) wi

29、th Continuity Indication has been received. 4) Clause 7.2.4.3 Actions required at an outgoing international gateway SN Add the following: c) International Emergency Preference Scheme: i) If the CSF, at an outgoing international gateway SN, receives information from the national network that the call

30、 is to be treated as an IEPS call (e.g., CPC value of IEPS), call establishment proceeds with priority. The call is established with the CPC set as IEPS call marking in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, Automatic Congestion Control, Hard-to-Reac

31、h procedure) are not applied to this call. ii) For an IEPS-call, the codec negotiation procedures are not to be invoked. If codec negotiation is already invoked on a preceding bearer path, the SN shall terminate the codec negotiation procedures and the call shall proceed. iii) If routing procedures

32、fail to find an outgoing CIC value, the call is queued and shall take precedence over any other normal call attempts. iv) Optionally, if queuing occurs, an early ACM (called party status set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ m

33、ay be returned to the preceding CSF. However, if the incoming IAM had indicated “COT to be expected“, the early ACM (no indication) shall not be sent until Continuity Message (COT) with Continuity Indication has been received. 5) Clause 7.2.5.3 Actions required at an outgoing international gateway C

34、MN Add the following: b) International Emergency Preference Scheme: i) If the CSF, at an outgoing international gateway CMN, receives information from the national network that the call is to be treated as an IEPS call (e.g., CPC value of IEPS), call establishment proceeds with priority. The call is

35、 established with the CPC set as IEPS call marking in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. ii) If routing procedures fail to find an outgoing CIC value, the call i

36、s queued and shall take precedence over any other normal call attempts. iii) Optionally, if queuing occurs, an early ACM (called party status set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the preceding CSF. However,

37、 if the incoming IAM had indicated “COT to be expected“, the early ACM (no indication) shall not be sent until Continuity Message (COT) with Continuity Indication has been received. ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) 3 6) Clause 7.2.6.3 Actions required at an incoming international gateway S

38、N Add the following (after the Note): a) International Emergency Preference Scheme: i) If the CSF, at an incoming international gateway SN, receives a call with CPC set to IEPS, the call establishment proceeds with priority. The call is established with the CPC set as IEPS call marking or national s

39、pecific information for IEPS call treatment in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. ii) For an IEPS-call, the codec negotiation procedures are not to be invoked. I

40、f codec negotiation is already invoked on a preceding bearer path, the SN shall terminate the codec negotiation procedures and the call shall proceed. iii) If routing procedures fail to find an outgoing CIC value, the call is queued and shall take precedence over any other normal call attempts. iv)

41、Optionally, if queuing occurs, an early ACM (called party status set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the preceding CSF. However, if the incoming IAM had indicated “COT to be expected“, the early ACM (no in

42、dication) shall not be sent until Continuity Message (COT) with Continuity Indication has been received. 7) Clause 7.2.7.3 Actions required at an incoming international gateway CMN Add the following (after the Note): a) International Emergency Preference Scheme: i) If the CSF, at an incoming interna

43、tional gateway CMN, receives a call with CPC set to IEPS, the call establishment proceeds with priority. The call is established with the CPC set as IEPS call marking or national specific information for IEPS call treatment in the outgoing IAM. Restrictive network management controls (e.g., Automati

44、c Call Gapping, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. ii) If routing procedures fail to find a outgoing CIC value, the call is queued and shall take precedence over any other normal call attempts. iii) Optionally, if queuing occurs, an early ACM (called

45、 party status set to “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the preceding CSF. However, if the incoming IAM had indicated “COT to be expected“, the early ACM (no indication) shall not be sent until Continuity Messag

46、e (COT) with Continuity Indication has been received. 8) Clause 7.4 Outgoing bearer set-up procedure Add the following new paragraph and note at the end: The BCF shall select appropriate bearer resources for a call with CPC set to IEPS to ensure that the quality of the bearer path is guaranteed thro

47、ughout the lifetime of the call. This applies both to the set-up phase of the call as well as to the connection phase of the call in case of congested network situations. The CSF shall accordingly pass the IEPS indicator to the BCF in the BNC Information Request primitive and/or in the Bearer Set-up

48、 Request primitive. NOTE The emergency call indicator in Annex F/Q.1950 should no longer be used for IEPS. 4 ITU-T Rec. Q.1902.4 (2001)/Amd.3 (01/2006) 9) Clause 7.5 Incoming bearer set-up procedure Add the following new paragraph and note at the end: The BCF shall select appropriate bearer resource

49、s for a call with CPC set to IEPS to ensure that the quality of the bearer path is guaranteed throughout the lifetime of the call. This applies both to the set-up phase of the call as well as to the connection phase of the call in case of congested network situations. The CSF shall accordingly pass the IEPS indicator to the BCF in the BNC Information Request primitive and/or in the Bearer Set-up Request primitive. NOTE The emergency call indicator in Annex F/Q.1950 should no longer be used for IEPS. 10) New clause 7.4.6 Polling at