ECMA TR 101-2010 Next Generation Corporate Networks (NGCN) - Emergency Calls (2nd Edition)《下一代企业网络(NGCN) 紧急呼叫(第2版)》.pdf

《ECMA TR 101-2010 Next Generation Corporate Networks (NGCN) - Emergency Calls (2nd Edition)《下一代企业网络(NGCN) 紧急呼叫(第2版)》.pdf》由会员分享，可在线阅读，更多相关《ECMA TR 101-2010 Next Generation Corporate Networks (NGCN) - Emergency Calls (2nd Edition)《下一代企业网络(NGCN) 紧急呼叫(第2版)》.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference numberECMA TR/101:2010Ecma International 2010ECMA TR/101 2ndEdition December 2010 Next Generation Corporate Networks (NGCN) - Emergency Calls COPYRIGHT PROTECTED DOCUMENT Ecma International 2010 Ecma International 2010 i Contents Page 1 Scope 1 2 References . 2 3 Terms and definitions . 4

2、 3.1 External definitions . 4 3.2 Other definitions 4 4 Abbreviations . 5 5 Background 6 6 Technical aspects of emergency calls in enterprise networks 10 6.1 Identifying a call as an emergency call . 10 6.1.1 User actions . 10 6.1.2 Signalling impact . 11 6.1.3 Unauthenticated access . 13 6.2 Obtain

3、ing and delivering the location of the caller 14 6.2.1 Format of location information 15 6.2.2 Obtaining location information for delivery 15 6.2.3 Location conveyance in SIP . 19 6.3 Routing an emergency call to the appropriate SAP 20 6.3.1 Routing by the calling device . 21 6.3.2 Routing by enterp

4、rise SIP intermediary 22 6.4 Delivering information to the SAP to allow a return call or verification call to be made . 22 6.4.1 Delivery of caller identification 23 6.4.2 Delivery of device identification 23 6.4.3 Identifying a return call or verification call . 23 6.5 Ensuring appropriate resource

5、s are available for an emergency call, return call or verification call 24 6.6 Ensuring appropriate media quality during an emergency call . 25 6.7 Security considerations 25 6.8 Other aspects . 26 6.8.1 Hosted users 26 6.8.2 Guest users 26 7 NGN considerations 27 8 Device considerations 28 9 Altern

6、atives for roaming mobile and nomadic users 29 9.1 Establishing an emergency call when already signalling via a visited public network . 30 9.2 Establishing an emergency call via a visited public network when other traffic is signalled directly via the enterprise network 30 9.3 Establishing an emerg

7、ency call directly to a PSAP . 31 10 Enterprise responsibilities . 31 11 Summary of requirements and standardisation gaps . 31 11.1 Requirements on NGNs 31 11.2 Recommendations on enterprise networks . 32 11.3 Standardisation gaps 33 ii Ecma International 2010Introduction This Ecma Technical Report

8、is one of a series of Ecma publications that explore IP-based enterprise communication involving Corporate telecommunication Networks (CNs) (also known as enterprise networks) and in particular Next Generation Corporate Networks (NGCN). The series particularly focuses on inter-domain communication,

9、including communication between parts of the same enterprise, between enterprises and between enterprises and carriers. This particular Ecma Technical Report discusses issues related to emergency calls from an enterprise user to a safety answering point (SAP). It builds upon concepts introduced in E

10、CMA TR/95. Various regional and national bodies address emergency communications, mainly with an emphasis on public telecommunications. In particular, in the United States work is carried out by the National Emergency Number Association (NENA). In Europe, ETSI EMTEL (Special Committee on Emergency C

11、ommunications) plays a coordinating role, liaising with external bodies (e.g., in the European Commission, CEPT, CEN and CENELEC) as well as overseeing work done by other ETSI Technical Bodies (e.g., TISPAN). This Technical Report focuses on emergency calls as they impact enterprise networks, and th

12、erefore is intended to complement the work of those other bodies. Compared to the 1st Edition, this 2nd Edition makes a distinction between an answering point and an emergency control centre and clarifies a few other points, in particular to do with interaction with (public) Next Generation Networks

13、. This Technical Report is based upon the practical experience of Ecma member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI, IETF and other international and national standardization bodies. It represents a pragmatic and widely based

14、consensus. In particular, Ecma acknowledges valuable input from experts in ETSI TISPAN, ETSI EMTEL, 3GPP CT1 and IETF ECRIT. This Ecma Technical Report has been adopted by the General Assembly of December 2010. Ecma International 2010 iii “DISCLAIMER This document and possible translations of it may

15、 be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are in

16、cluded on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to Ecma International, except as needed for the purpose of developing any document or deliverable produced by Ecma International (in

17、which case the rules applied to copyrights must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by Ecma International or its successors or assigns. This document and the information contained h

18、erein is provided on an “AS IS“ basis and ECMA INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR

19、PURPOSE.“ iv Ecma International 2010 Ecma International 2010 1Next Generation Corporate Networks (NGCN) - Emergency Calls 1 Scope This Ecma Technical Report is one of a series of publications that provides an overview of IP-based enterprise communication involving Corporate telecommunication Network

20、s (CNs) (also known as enterprise networks) and in particular Next Generation Corporate Networks (NGCN). The series particularly focuses on session level communication based on the Session Initiation Protocol (SIP) 6, with an emphasis on inter-domain communication. This includes communication betwee

21、n parts of the same enterprise (on dedicated infrastructures and/or hosted), between enterprises and between enterprises and public networks. Particular consideration is given to Next Generation Networks (NGN) as public networks and as providers of hosted enterprise capabilities. Key technical issue

22、s are investigated, current standardisation work and gaps in this area are identified, and a number of requirements are stated. Among other uses, this series of publications can act as a reference for other standardisation bodies working in this field. This particular Ecma Technical Report discusses

23、 issues related to emergency calls from an enterprise user to a safety answering point (SAP), using SIP within the NGCN. A SAP can be either a public safety answering point (PSAP) or a private emergency answering point (PEAP). This Technical Report uses terminology and concepts developed in ECMA TR/

24、95 1. It identifies a number of requirements impacting NGN standardisation and concerning deployment of enterprise networks. The scope of this Technical Report is limited to calls from a user of an enterprise network to an authority, where the authority is represented by a SAP (PSAP or PEAP). This i

25、ncludes the special case where a PEAP acts as an enterprise user in making an emergency call to a PSAP. Authority to authority calls, authority to enterprise user calls and enterprise user to enterprise user calls within the context of an emergency are out of scope, with the exception of return call

26、s and verification calls as follow-up to an emergency call from the user to an authority. This Technical Report focuses on emergency calls within a SIP-based NGCN using geographic location information to indicate the whereabouts of the caller. Emergency calls can originate from devices connected to

27、the NGCN via various access technologies, e.g., SIP over fixed or wireless LAN (Local Area Network), TDM (Time Division Multiplex) networks, DECT (Digital Enhanced Cordless Telephone) networks, PMR (Private Mobile Radio) networks, PLMN (Public Land Mobile Network) etc SAPs are assumed to be reachabl

28、e either directly using SIP or via a gateway to some legacy technology (e.g., TDM). Furthermore, SAPs are assumed to be reachable either directly from the NGCN or via a public network accessed from the NGCN using SIP. In the latter case, the NGCN might identify the SAP and instruct the public networ

29、k to route to the SAP, or alternatively the NGCN might leave the public network to identify the SAP, based on the location of the caller. In all cases the NGCN is assumed to deliver the location of the caller to the SAP, gateway or public network in order to provide appropriate information to the ca

30、ll taker at the SAP. The handling of incoming emergency calls at a SAP, even when the SAP is provided within an NGCN, is outside the scope of this Technical Report. This includes the case where a PSAP is provided within an NGCN and hence the NGCN can receive emergency calls from public networks. Thi

31、s also includes the case where a PEAP is provided within an NGCN and can receive emergency calls from other enterprise networks or other parts of the same NGCN. Different territories have different regulations impacting emergency calls, together with national or regional standards in support of thes

32、e regulations. This Technical Report takes a general approach, which should be largely applicable to any territory. However, detailed differences might apply in some territories, e.g., country- or region-specific dial strings used to identify emergency calls. The scope of this Technical Report is li

33、mited to emergency communications with a real-time element, including but not limited to voice, video, real-time text and instant messaging. The focus, however, is on voice, which in the majority of situations is likely to be the most effective medium for emergency calls. However, it is 2 Ecma Inter

34、national 2010recognised that some users with special needs will require other modes of communication (e.g., real-time text, fax), as discussed in Annex B of 30, and also different modes can be used for the emergency call and the verification call. The focus is also on calls in which the caller is a

35、human user. There may also be applications where automatic sensors can make similar emergency calls (subject to regulation), but the special needs of such applications are not considered. 2 References For dated references, only the edition cited applies. For undated references, the latest edition of

36、 the referenced document (including any amendments) applies. 1 ECMA TR/95, Next Generation Corporate Networks (NGCN) - General 2 ECMA TR/100, Next Generation Corporate Networks (NGCN) - Security of Session-based Communications 3 Standard ECMA-269, Services for Computer Supported Telecommunications A

37、pplications (CSTA) Phase III 4 ANSI/TIA-1057, Link Layer Discovery Protocol - Media Endpoint Discovery 5 IEEE 802.1ab, Station and Media Access Control Connectivity Discovery 6 IETF RFC 3261, SIP: Session Initiation Protocol 7 IETF RFC 3265, Session Initiation Protocol (SIP) - Specific Event Notific

38、ation 8 IETF RFC 3825, Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information 9 IETF RFC 3859, Common Profile for Presence (CPP) 10 IETF RFC 3856, A Presence Event Package for the Session Initiation Protocol (SIP) 11 IETF RFC 3863, Presence Information Dat

39、a Format (PIDF) 12 IETF RFC 4119, A Presence-based GEOPRIV Location Object Format 13 IETF RFC 4412, Communications Resource Priority for the Session Initiation Protocol (SIP) 14 IETF RFC 4776, Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Address Configuration Information

40、15 IETF RFC 5012, Requirements for Emergency Context Resolution with Internet Technologies 16 IETF RFC 5031, A Uniform Resource Name (URN) for Emergency and Other Well-Known Services 17 IETF RFC 5139, Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) 18 IET

41、F RFC 5222, LoST: A Location-to-Service Translation Protocol 19 IETF RFC 5223, Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP) 20 IETF RFC 5491, GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Con

42、siderations, and Recommendations Ecma International 2010 321 IETF draft-ietf-ecrit-framework-12, Framework for Emergency Calling using Internet Multimedia NOTE At the time of publication of this Technical Report, the IETF had not completed the approval process for this draft and had not allocated an

43、 RFC number. If the draft (or a later version) is no longer available, readers should look for the RFC with the same title. 22 IETF draft-ietf-ecrit-phonebcp-16, Best Current Practice for Communications Services in support of Emergency Calling NOTE At the time of publication of this Technical Report

44、, the IETF had not completed the approval process for this draft and had not allocated an RFC number. If the draft (or a later version) is no longer available, readers should look for the RFC with the same title. 23 IETF RFC 5985, HTTP Enabled Location Delivery (HELD) 24 IETF RFC 5986, Discovering t

45、he Local Location Information Server (LIS) 25 IETF RFC 5627, Obtaining and Using Globally Routable User Agent URIs (GRUU) in the Session Initiation Protocol (SIP) 26 IETF draft-ietf-sipcore-location-conveyance-04, Location Conveyance for the Session Initiation Protocol NOTE At the time of publicatio

46、n of this Technical Report, the IETF had not completed the approval process for this draft and had not allocated an RFC number. If the draft (or a later version) is no longer available, readers should look for the RFC with the same title. 27 NENA 08-001, National Emergency Number Association (NENA)

47、Architecture for Enhanced 9-1-1 Services (i2) 28 3GPP TS 22.101, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service Aspects; Service Principles 29 3GPP TS 23.167, 3rd Generation Partnership Project; Technical Specification Group Services and System

48、 Aspects; IP Multimedia Subsystem (IMS) emergency sessions 30 ETSI TR 102 180, Basis of requirements for communication of individuals with authorities/organizations in case of distress (Emergency call handling) 31 ETSI TS 102 424, Telecommunications and Internet converged Services and Protocols for

49、Advanced Networking (TISPAN); Requirements of the NGN network to support Emergency Communication from Citizen to Authority 32 ETSI TS 102 650, Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Analysis of Location Information Standards produced by various SDOs 33 ETSI TS 102 660, Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Signalling Requirements and Signalling Architecture for supporting the various loc