1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000628.a.2001(R2015) ECS Connection and Ring Back Addendum As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through AT
2、IS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from desi
3、gn and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generat
4、ion Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit . AMERICAN N
5、ATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substan
6、tial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. Th
7、e use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American Na
8、tional Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standard
9、s Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute requ
10、ire that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer Supplement to T1.628-2000) American N
11、ational Standard for Telecommunications ECS - Connection and Ring Back Addendum Secretariat Alliance for Telecommunications Industry Solutions Approved August 21, 2001 American National Standards Institute, Inc. Abstract This addendum to T1.628-2000 specifies the use of the Connection Hold network c
12、apability by the Emergency Calling Service (ECS) to support ECS call hold and ring back. This addendum also specifies the TCAP messages exchanged between a switching node routing ECS calls and a Selective Routing Database (SRDB) that contains information determining the PSAP that should receive the
13、emergency calls originating from a given caller or calling location. ii Foreword The information contained in this Foreword is not part of this American National Standard (ANS) and has not been processed in accordance with ANSIs requirements for an ANS. As such, this Foreword may contain material th
14、at has not been subjected to public review or a consensus process. In addition, it does not contain requirements necessary for conformance to the standard. Accredited Standards Committee T1, Telecommunications serves the public through improved understanding between carriers, customers, and manufact
15、urers. Technical Subcommittee T1S1 of Committee T1 develops telecommunications standards and technical reports related to services, architectures, and signaling, in addition to related subjects under consideration in other North American and international standards bodies. ANSI guidelines specify tw
16、o categories of requirements: mandatory and recommendation. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently
17、 identifiable as having distinct compatibility or performance advantages. Suggestions for improvement of this standard are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 G Street NW, Suite 500, Washington, DC 20005. This standard was proc
18、essed and approved for submittal to ANSI by Accredited Standards Committee on Telecommunications, T1. Committee approval of the standard does not necessarily imply that all members voted for its approval. Working Group T1S1.7 on Services, Architecture, and Control of Technical Subcommittee T1S1 on S
19、ervices, Architectures, and Signaling, was responsible for the development of this standard. iii Table of Contents 1 SCOPE, PURPOSE, AND APPLICATION. 1 2 NORMATIVE REFERENCES . 1 3 CHANGES TO T1.628-2000 1, SCOPE, PURPOSE, AND APPLICATION. 2 4 CHANGES TO T1.628-2000 2, NORMATIVE REFERENCES . 2 5 CHA
20、NGES TO T1.628-2000 4, DESCRIPTION OF EMERGENCY CALLING SERVICE 2 6 CHANGES TO T1.628-2000 5, FUNCTIONAL CAPABILITIES AND INFORMATION FLOWS 2 7 CHANGES TO T1.628-2000, 6 SWITCHING AND SIGNALLING SPECIFICATION FOR ECS AT THE USERNETWORK INTERFACE 3 8 CHANGES TO T1.628-2000 7, SWITCHING AND SIGNALING
21、SPECIFICATION FOR ECS AT INTEREXCHANGE INTERFACES . 7 Table of Tables Table 1/T1.628A ECS analyzedInformation message .10 Table 2/T1.628A ECS analyzeRoute .13 Table 3/T1.628A ECS terminationAttempt message15 Table 4/T1.628 ECS collectedInformation message 18 Table 5/T1.628A ECS forwardCall message21
22、 .AMERICAN NATIONAL STANDARD ATIS-1000628.a.2001American National Standard for Telecommunications ECS - Connection and Ring Back Addendum 1 1 Scope, Purpose, and Application This addendum to T1.628-2000 specifies the use of the Connection Hold network capability by the Emergency Calling Service (ECS
23、) to support ECS call hold and ring back. This addendum also specifies the TCAP messages exchanged between a switching node routing ECS calls and a Selective Routing Database (SRDB) that contains information determining the PSAP that should receive the emergency calls originating from a given caller
24、 or calling location. The Connection Hold Network Capability disables a calling users capability to initiate release of a call. Connection hold also provides a mechanism to indicate that the calling user has requested disconnect (or reconnect) without initiating release procedures. The procedures de
25、scribed in this addendum supplement the procedures in T1.6282000, American National Standard for TelecommunicationsEmergency Calling Service. In particular the procedures described here take precedence over normal call release procedures when ECS Call Hold is invoked. The use of connection hold is r
26、estricted when the caller has an ISDN usernetwork interface. Due to existing provisions of the DSS1 protocol it is not possible to prevent an ISDN caller from disconnecting an active call. When call hold is applied to ECS calls originating from an ISDN usernetwork interface and the caller disconnect
27、s, the network will attempt to reconnect to the users terminal in cases when the network has information that permits it to identify the end users terminal. A PSAP using an ISDN access can invoke the network to apply ring back to the callers terminal using the protocol defined in this addendum. Foll
28、owing the references clause, the remainder of this addendum specifies changes to the existing text of T1.628-2000 using strikeout to indicate deletions and underlining to indicate insertions. 2 Normative References The following listed standards contain provisions which, through reference in this te
29、xt, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this American National Standard are encouraged to investigate the possibility of applying the most re
30、cent editions of the standards indicated below. T1.628-2000, Emergency Calling Service.1T1.666-1999, Signalling System Number 7 (SS7)Operator Services Network Capabilities.11This document is available from the Alliance for Telecommunications Industry Solutions, 1200 G Street N.W., Suite 500, Washing
31、ton, DC 20005. 2 T1.667-1999, Intelligent Network.13 Changes to T1.628-2000 1, Scope, purpose, and application NOTE - In this and in succeeding clauses, a section mark () indicates a reference to a clause of T1.628-2000. 1.1, paragraph 3: Capabilities needed for supporting ECS Call Hold and Ringback
32、 are described in Clauses 47 and 5. However, there is no DSS1 or SS7 support for these capabilities at this time. 4 Changes to T1.628-2000 2, Normative References 2. Append: T1.666-1999, Signalling System Number 7 (SS7)Operator Services Network Capabilities.1T1.667-1999, Intelligent Network.15 Chang
33、es to T1.628-2000 4, Description of Emergency Calling Service 4.1.4 and 4.1.5. Delete the second paragraph in each. 4.5. Retitle to “Interactions with supplementary services and network capabilities.” Add a new 4.5.6, “Connection Hold Network Capability“: As a network option, ECS may attempt invocat
34、ion of the connection hold network capability in conjunction with an emergency service call. Connection hold, if successfully invoked, disables the callers ability to initiate release of the emergency service call. When ECS employs the connection hold network capability, ECS is the network service r
35、eferred to in T1.666.4-1999. 6 Changes to T1.628-2000 5, Functional Capabilities and Information Flows 5.1.5. Append a sentence: When ECS uses the optional connection hold network capability, FE5 controls the operation of connection hold functional entity CH3 described in T1.666.4-1999. 3 5.1.11 and
36、 5.1.12. Delete the second paragraph in each of these clauses, replacing each with: FE11 and FE12 collectively provide the capabilities of functional entities CH1and CH2 in the function entity model of T1.666.4-1999. Note that the distribution of capabilities between FE11 and FE12 differs from the d
37、istribution between CH1 and CH2. 5.2, third paragraph. Append to the existing text: An attempt to invoke FE11 when the caller is an ISDN user does not succeed. In this case, if acknowledgement of connection hold invocation is requested, a negative acknowledgement will be given. 7 Changes to T1.628-2
38、000, 6 Switching and signalling specification for ECS at the usernetwork interface 6.2.1.1. Replace the second sentence with: In addition, the following additional service-specific states are defined for use with the ECS Call Hold capability: 6.2.1.1.Insert a bulleted list and three new paragraphs f
39、ollowing this new sentence: Idle. ECS Call HoldConnected. ECS Call HoldHeld. The Idle state exists before ECS Call Hold capability is invoked. “ECS Call Hold-Connected” represents the state where the ECS Call Hold procedures have been invoked by the switch serving the calling user and the calling us
40、er is connected to the ECS call. “ECS Call Hold-Held” represents the state where the ECS Call Hold procedures have been invoked by the switch serving the calling user and the calling user has disconnected from the ECS call. 6.1.3.3.1. (ASN.1) Add a definition of the Ringback Request operation follow
41、ing the existing definition of the DCI Request operation and the ringbackRequest operation value following the definition of the dCIRequest operation value. RingbackRequest : = OPERATION ringbackRequest RingbackRequest := 1 2 840 10005 0 13 6.2. Add new clauses 6.2.7 and 6.2.8 to describe the proced
42、ure for Call Hold and Ringback respectively: 4 6.2.7 ECS Call Hold 6.2.7.1 BRI/TE Operation If the ECS Call Hold feature is supported and invoked for a BRI/TE, then the procedures of this section apply. While in the “ECS Call Hold-Connected” service state and under normal conditions, the network sha
43、ll not initiate call clearing over the ISDN access unless call clearing was initiated from the direction of the PSAP. If the user initiates call clearing while the network is in the “ECS Call Hold-Connected” service state, then the network shall allow the call clearing procedures to complete on the
44、ISDN access interface. In addition, the network shall: Retain the telephone number used as the calling party number for the calling user; Hold the ECS call/connection towards the PSAP; Reserve a B-channel for the held ECS call; Wait for the user to re-connect to the ECS held call; and Move to the “E
45、CS Call Hold-Held” service state. While in the “ECS Call Hold-Held” service state, if the network receives a SETUP message whose bearer capability is either speech or 3.1 kHz audio and the network determines that the calling party number for that call is the same as the retained calling party number
46、 for the held ECS call, then the network shall take the following actions. Assign a B-channel to the terminal (and un-reserve a B-channel); Connect the B-channel to the held ECS call; Move to the “ECS Call Hold-Connected” service state; and Complete the call origination procedures on the ISDN access
47、 by sending a CALL PROCEEDING message followed by a CONNECT message. While in the “ECS Call Hold Held” service state, if the network receives SETUP message for which a different DN is used for call origination, the network should follow the procedures of T1.607-2000 for call origination, with the ex
48、ception that since a B-channel is reserved for the held ECS call, the network shall ensure that a B-channel continues to be reserved for that held call. If the ECS call is cleared from the direction of the PSAP, the network shall release any B-channel that it might have been reserving for the ECS ca
49、ll. 6.2.7.2 BRI/NT2 and PRI/NT2 Operation Support of ECS Call Hold capability by the NT2 on an ISDN BRI or PRI is optional. If the NT2 does not support ECS Call Hold and the caller hangs up, the user follows the normal call clearing procedures of T1.607-2000. If the NT2 does support ECS call hold, then it enters the ECS Call HoldConnected service state on recognizing a call as an ECS call. If the caller disconnects (hangs up) while in the ECS Call Hold5 Connected service state, the NT2 enters the ECS Call Hold
