1、 International Telecommunication Union ITU-T Q.764TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 4(01/2006) SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 ISDN user partSignalling System No. 7 ISDN User Part signalling procedures Amendment 4: Support for the
2、International Emergency Preference Scheme ITU-T Recommendation Q.764 (1999) Amendment 4 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICE
3、S 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 SIGNALLING SYSTEM No. 7 Q.700Q.799 General Q.700 Message
4、transfer part (MTP) Q.701Q.710 Signalling connection control part (SCCP) Q.711Q.719 Telephone user part (TUP) Q.720Q.729 ISDN supplementary services Q.730Q.739 Data user part Q.740Q.749 Signalling System No. 7 management Q.750Q.759 ISDN user part Q.760Q.769 Transaction capabilities application part
5、Q.770Q.779 Test specification Q.780Q.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
6、.1700Q.1799 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.764 (1999)/Amd.4 (01/2006) i ITU-T Recommendation Q.764 Signalling System No. 7 ISD
7、N User Part signalling procedures Amendment 4 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 ITU-T Rec. E.10
8、6. It contains the modifications to ITU-T Rec. Q.764 (1999) in order to accommodate these needs. This amendment should be read in conjunction with Amendment 3 to ITU-T Rec. Q.761, Amendment 3 to ITU-T Rec. Q.762, and Amendment 4 to ITU-T Rec. Q.763. This amendment incorporates Amendment 2 to ITU-T R
9、ec. Q.764 and provides enhancements. Source Amendment 4 to ITU-T Recommendation Q.764 (1999) 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.764 (1999)/Amd.4 (01/2006) FOREWORD The International Telecommunication Union (ITU)
10、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 Recommendations on them with a view to standardiz
11、ing 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 approval of ITU-T Recommendations is covered
12、 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“ is used for conciseness to indicate
13、 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 with the Recommendation is achieved whe
14、n 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 required of any party. INTELLECTUAL PROPERT
15、Y 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 Intellectual Property Rights, whether asserted
16、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. However, implementors are cautioned that
17、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. ITU-T Rec. Q.764 (1999)/Amd.4 (01/2006
18、) iii CONTENTS Page 1) Clause 1.2 References 1 2) Clause 1.4 Abbreviations. 1 3) Clause 2.1.1.3 Actions required at an outgoing international exchange . 1 4) Clause 2.1.1.4 Actions required at an intermediate international exchange 1 5) Clause 2.1.1.5 Actions required at an incoming international ex
19、change. 2 6) Clause 2.1.2.3 Actions required at an outgoing international exchange . 2 7) Clause 2.1.2.4 Actions required at an intermediate international exchange 3 8) Clause 2.1.2.5 Actions required at an incoming international exchange. 3 9) New clause 2.28 3 ITU-T Rec. Q.764 (1999)/Amd.4 (01/200
20、6) 1 ITU-T Recommendation Q.764 Signalling System No. 7 ISDN User Part signalling procedures Amendment 4 Support for the International Emergency Preference Scheme 1) Clause 1.2 References Insert the following new reference: 28 ITU-T Recommendation E.106 (2003), International Emergency Preference Sch
21、eme (IEPS) for disaster relief operations. 2) Clause 1.4 Abbreviations Add the following new abbreviations alphabetically: CPC Calling Partys Category IEPS International Emergency Preference Scheme 3) Clause 2.1.1.3 Actions required at an outgoing international exchange Add the following: e) Interna
22、tional Emergency Preference Scheme If an outgoing international exchange 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 established with the CPC set as IEPS call marking i
23、n the outgoing IAM. Restrictive network management controls (e.g., Automatic Call Gapping, ISUP Signalling Congestion Control, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. If routing procedures fail to find an outgoing circuit, the call is queued and shall tak
24、e precedence over any other normal call attempts. 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 originating exchange. However, if the incoming IAM
25、 had requested continuity check (either on this circuit or a previous circuit), the early ACM (no indication) shall not be sent until a successful continuity indication has been received. 4) Clause 2.1.1.4 Actions required at an intermediate international exchange Add the following: e) International
26、 Emergency Preference Scheme If an intermediate international exchange 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
27、 Gapping, ISUP Signalling Congestion Control, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. 2 ITU-T Rec. Q.764 (1999)/Amd.4 (01/2006) If routing procedures fail to find an outgoing circuit, the call is queued and shall take precedence over any other normal call
28、 attempts. 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 originating exchange. However, if the incoming IAM had requested continuity check (either
29、 on this circuit or a previous circuit), the early ACM (no indication) shall not be sent until a successful continuity indication has been received. 5) Clause 2.1.1.5 Actions required at an incoming international exchange Add the following: e) International Emergency Preference Scheme If an incoming
30、 international exchange 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., Auto
31、matic Call Gapping, ISUP Signalling Congestion Control, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. If routing procedures fail to find an outgoing circuit, the call is queued and shall take precedence over any other normal call attempts. Optionally, if queuin
32、g 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 originating exchange. However, if the incoming IAM had requested continuity check (either on this circuit or a previous c
33、ircuit), the early ACM (no indication) shall not be sent until a successful continuity indication has been received. 6) Clause 2.1.2.3 Actions required at an outgoing international exchange Add the following: e) International Emergency Preference Scheme If an outgoing international exchange receives
34、 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 established with the CPC set as IEPS call marking in the outgoing IAM. Restrictive network management controls (e.g., Automatic Call
35、 Gapping, ISUP Signalling Congestion Control, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. If routing procedures fail to find an outgoing circuit, the call is queued and shall take precedence over any other normal call attempts. Optionally, if queuing occurs,
36、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 originating exchange. However, if the incoming IAM had requested continuity check (either on this circuit or a previous circuit), t
37、he early ACM (no indication) shall not be sent until a successful continuity indication has been received. ITU-T Rec. Q.764 (1999)/Amd.4 (01/2006) 3 7) Clause 2.1.2.4 Actions required at an intermediate international exchange Add the following: e) International Emergency Preference Scheme If an inte
38、rmediate international exchange 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, ISUP Signalling Congestion Co
39、ntrol, Automatic Congestion Control, Hard-to-Reach procedure) are not applied to this call. If routing procedures fail to find an outgoing circuit, the call is queued and shall take precedence over any other normal call attempts. Optionally, if queuing occurs, an early ACM (called party status set t
40、o “no indication“) with the inclusion of the generic notification parameter set to “call completion delay“ may be returned to the originating exchange. However, if the incoming IAM had requested continuity check (either on this circuit or a previous circuit), the early ACM (no indication) shall not
41、be sent until a successful continuity indication has been received. 8) Clause 2.1.2.5 Actions required at an incoming international exchange Add the following: e) International Emergency Preference Scheme If an incoming international exchange receives a call with CPC set to IEPS, the call establishm
42、ent 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., Automatic Call Gapping, ISUP Signalling Congestion Control, Automatic Congestion Cont
43、rol, Hard-to-Reach procedure) are not applied to this call. If routing procedures fail to find an outgoing circuit, the call is queued and shall take precedence over any other normal call attempts. Optionally, if queuing occurs, an early ACM (called party status set to “no indication“) with the incl
44、usion of the generic notification parameter set to “call completion delay“ may be returned to the originating exchange. However, if the incoming IAM had requested continuity check (either on this circuit or a previous circuit), the early ACM (no indication) shall not be sent until a successful conti
45、nuity indication has been received. 9) New clause 2.28 Add the following new clause: 2.28 IEPS call information 2.28.1 Actions required at an outgoing international gateway exchange Where the exchange logic determines that an IEPS call (as set out in 2.1.1.3 e and 2.1.2.3 e) requires IEPS informatio
46、n to be transported in the forward direction and based on bilateral agreement between administrations, the exchange shall include the IEPS call information parameter in the outgoing IAM. This parameter will contain the identity of the entity (the country or international network) originating the IEP
47、S call, and the national priority level of the call. The priority level in the IEPS call information parameter will be the national priority level of the call in the entity originating the call. The priority level in the IEPS call information parameter is signalled in inverse order of the numerical
48、value, i.e., the lower the numerical value is, the higher the priority. For example, numerical value 0 indicates the highest priority possible. 4 ITU-T Rec. Q.764 (1999)/Amd.4 (01/2006) 2.28.2 Actions required at an intermediate international exchange If an intermediate international exchange receiv
49、es a call with CPC set to IEPS, the call establishment proceeds with priority. The call is established with the CPC set as IEPS in the outgoing IAM. The IEPS call information parameter shall be passed on transparently. The exchange shall not provide IEPS priority treatment if the CPC value is not IEPS, even if the optional IEPS call information parameter is present. 2.28.3 Actions required at an incoming international gateway exchange If an incoming international gateway exchange receives a call with CPC set to IEPS, the
