1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000628.2000(R2015) Emergency Calling Service 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 ATIS committees
2、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 design and innovat
3、ion 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 Generation Partnershi
4、p 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 NATIONAL STANDA
5、RD 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, substantial agreement
6、 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. The use of Ameri
7、can 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 National Standar
8、ds 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 Standards Institute. R
9、equests 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 require that actio
10、n 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 theirexistence does not in any respect preclude any
11、one, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any Ameri
12、can NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titl
13、epage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards
14、 mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAlliance for Telecommunications Industry Solutions1200 G. St., NW, Washington, D.C. 20005Copyright 2000 by Alliance for Telecommunications Industry So
15、lutionsAll rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the copyright holder.Printed in the United States of AmericaiContentsPage1 Scope, Purpose, and Application . 12 Normative References
16、 13 Definitions. 24 Description of Emergency Calling Service . 55 Functional Capabilities and Information Flows . 126 Switching and Signaling Specification for ECS at the User-Network Interface. 147 Switching and Signaling Specification for ECS at Interexchange Interfaces 288 Specification for Proto
17、col Interworking . 35iiForeword (This foreword is not part of American National Standard T1.628-2000.)This standard specifies the protocol and procedures applicable for the support ofEmergency Calling Service in an Integrated Services Digital Network (ISDN). This standard was developed by Working Gr
18、oup T1S1.3 and T1S1.7 of AccreditedStandards Committee T1 - Telecommunications. Suggestions for improvement of this standard will be welcome. They should be sentto the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 GStreet NW, Suite 500, Washington, DC, 20005.This standard
19、was processed and approved for submittal to ANSI by AccreditedStandards Committee T1 - Telecommunications. Committee approval of the standarddoes not imply that all committee members voted for its approval. At the time it ap-proved this standard, Accredited Standards Committee T1 had the following m
20、em-bers:G. H. Peterson, T1 ChairmanE. Raymond Hapeman, Vice-ChairJ. A. Crandall, T1 DirectorSusan M. Carioti, T1 DisciplinesSteven D. Barclay, T1 SecretarySelvam Rengasami, Technical EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAT the maximum number of occurrences is network
21、 dependent. 6 Included when the PSAP is invoking E9-1-1 call linking capability. T1.628-2000 16 6.1.1.2 FACILITY See T1.610. 6.1.2 Codesets The Facility information element is defined in T1.610 to be in codeset 0. In addition, the Generic Information infor-mation element and the Emergency call contr
22、ol information element are in codeset “5”. 6.1.3 Information elements The following information elements are applicable to the operation of ECS: Generic information, Emergency call control, and Facility. 6.1.3.1 Generic information The purpose of the Generic information (GI) information element is t
23、o allow the transmittal of generic information across an ISDN interface. The GI information element is coded as shown in Figure 7. 8 7 6 5 4 3 2 1 Octet Generic information information element identifier 0 0 0 1 0 0 1 0 1 Length of Generic information contents 2 1 0 0 Type of information ext. spare
24、3 Information 4 etc. Figure 7 - Generic information information element Type of information (octet 3) Bits 5 4 3 2 1 0 0 0 0 1 Calling Geodetic Location information (Note) 0 1 1 0 1 Location identification number All other values are reserved NOTE - The Type of Information coding value of Calling Ge
25、odetic Location information is currently only applicable in the network to user direction. Information (octets 4 etc.) By default, this field is coded with IA5 characters. T1.628-2000 17 The detailed encoding of the Information field is dependent on the value in the Type of information field, as fol
26、lows: Calling Geodetic Location information When the “Type of Information” field is coded to “Calling Geodetic Location information”, the “Informa-tion” field (i.e., octet 4 etc.) shall be coded identically to the coding of Octet 1 - n of the SS7 Calling Geodetic Location information parameter. Refe
27、r to 7.1.2.3 for detailed coding of these octets. Location Identification Number When the “Type of information” field is coded to “Location Identification Number”, the “Information” field shall contain one or more digits of this identifier. The actual number sent by the ISDN user to the network shal
28、l consist of a 10 digit number conformant to the North American Numbering Plan. Typi-cally, this Location Identification Number value is one of the NANP numbers assigned to the ISDN in-terface. Octet 4 etc., shall be coded as ASCII characters as shown below. 8 7 6 5 4 3 2 1 0 Number digits (ASCII ch
29、aracters) 4 etc. 6.1.3.2 Emergency call control The purpose of the Emergency call control information element is to convey emergency call control information across an ISDN interface. The Emergency call control information element is coded as shown in Figure 8. 8 7 6 5 4 3 2 1 Octet Emergency call c
30、ontrol information element identifier 1 0 0 0 1 0 0 0 1 Length of Emergency call control information contents 2 1 ext. Coding Stan-dard Control 3 Figure 8 - Emergency call control information element T1.628-2000 18 Coding standard (octet 3) Bits 7 6 1 0 National Standard 1 1 Standard defined for the
31、 network present at the network side of the interface (see Note) All other values are reserved NOTE - This coding standard should be used only when the desired Emergency call control information element cannot be represented with national standardized coding. Control (octet 3) (see Note) Bits 5 4 3
32、2 1 0 0 0 0 0 Normal/Steady display 0 0 0 0 1 Flashing display All other values are reserved NOTE - These are the American national codepoints that apply only when the coding standard field specifies national standard “1 0”. 6.1.3.3 Facility The Facility information element is defined in T1.610. The
33、 protocol profile shall be coded to “Networking Exten-sions”. The Network Protocol profile shall be omitted. The Interpretation component may be excluded. 6.1.3.3.1 ASN.1 DEFINITIONS:= BEGIN EXPORTS e911CallTransferLink IMPORTS OPERATION, ERROR FROM Remote-Operation-Notation joint-iso-ccitt remote-o
34、perations(4) notation(0) notAvailable, notSubscribed, invalidCallState FROM General-Error-List ccitt recommendation q 950 general-error-list(1) linkIDNotAssignedByNetwork FROM ccitt recommendation q 952 explicit-call-transfer (7) operations-and-errors (1) e911CallTransferLink:= OPERATION ARGUMENT IM
35、PLICIT SEQUENCE linkID, dChannelIdentifier OPTIONAL - e911CallTransferLink is a Class 2 operation that provides a link between a call origination, - and another call that is to be transferred. Successful invocation of this operation results in - the use of stored calling station number information i
36、n setting up the new call. - linkID contains two octets coded with the call reference value and flag of the other call T1.628-2000 19 - to be transferred. - dChannelIdentifier contains a 1-to-4 octet value identifying the D-channel of the interface - serving the other call to be transferred, obtaine
37、d from a previous dCIRequest. (Please refer - to the requirements for ECT in T1.643). - This argument is only included when the two calls are served by different ISDN interfaces. RESULT - The return of a Return Result component is an acknowledgment of a - successful outcome of the e911 call transfer
38、 link operation. ERRORS notSubscribed, notAvailable, invalidCallState, linkIdNotAssignedByNetwork, dCINotAssignedByNetwork DClRequest : = OPERATION RESULT dChannelIdentifier ERRORS notAvailable LinkIdNotAssignedByNetwork := ERROR DCINotAssignedByNetwork := ERROR linkID := INTEGER (-32,768 32,767) dC
39、hannelIdentifier := OCTET STRING (SIZE (1 4) e911CallTransferLink E911CallTransferLink := 1 2 840 10005 0 12 - this operation value is an object identifier in number form which represents: ISO (1), - ansi (2), t1s1(840), ISDN-supplementary-services (10005), operations (0), - e911CallTransferLink (12
40、) dCIRequest DCIRequest := 1 2 840 10005 0 9 linkIdNotAssignedByNetwork LinkIdNotAssignedByNetwork := 61 dCINotAssignedByNetwork DCINotAssignedByNetwork := 1 2 840 10005 1 1 END 6.1.4 Codepoints The codepoints defined in T1.607, T1.610, and in this standard, shall be used by ECS, as appropriate. 6.2
41、 Procedures This clause details the procedures that shall be supported between the two sides of an ISDN interface in order to support Emergency Calling Service signaling. The procedures describe the generation and transmission of location information and other typifying information between a TE or N
42、T2 and the network, and between the network and a PSAP. 6.2.1 States and timers 6.2.1.1 States ECS uses all of the same call states as defined in T1.607 for basic call control. There are no additional states be-yond those defined in T1.607 for ECS. 6.2.1.2 Timers ECS uses all of the same timers as d
43、efined in T1.607 for basic call control. There are no new timers associated with ECS. 6.2.2 Invocation ECS is invoked when the called party number digits received by the network from the originating user are 911. The inclusion of location information in an originating SETUP message does not constitu
44、te the invocation of ECS. T1.628-2000 20 Conversely, the exclusion of location information in an originating SETUP message does not preclude the invoca-tion of ECS. 6.2.3 Notification Notification of an ECS call including the delivery of caller location information is provided to the terminating PSA
45、P as described in 6.2.4.2. 6.2.4 Normal Operation 6.2.4.1 Origination A user (TE or NT2), when originating an Emergency Service call, may optionally send information about the loca-tion of the caller to the network during call establishment. Caller location information in the form of a LIN, if pro-v
46、ided, shall be sent in a Generic information (GI) information element in a SETUP message, with the “Type of in-formation” field of the GI information element coded to “01101” Location Identification Number. The originating exchange may allow a service provider to provision whether a user-provided ca
47、lling party number or the charge number associated with an originating ISDN interface shall be used as the calling party number for the ESC. If this capability is supported in an originating exchange and the user-provided calling party number is to be used, then the network shall follow the procedur
48、es of T1.625 for determining the calling party number for the call with the following clarification. The network shall perform screening on the user-provided calling party number; A number that fails screening shall not be sent towards the emergency service exchange. If the user provided calling par
49、ty number fails screening, then the main (i.e., network provided) number shall be sent as the calling party number toward the emergency service exchange. If the charge number is to be used, then the network shall utilize the charge number as the calling party number for the call. In either case, only a single calling party number shall be sent towards the emergency service exchange. If a SETUP message is received at an exchange where the called number digits are 911 and the exchange sup-ports access to an SRF, the EC
