ISO IEC TR 16167-2011 Information technology - Telecommunications and information exchange between systems - Next Generation Corporate Networks (NGCN) - Emergen.pdf

1、 Reference number ISO/IEC TR 16167:2011(E) ISO/IEC 2011TECHNICAL REPORT ISO/IEC TR 16167 Second edition 2011-09-01Information technology Telecommunications and information exchange between systems Next Generation Corporate Networks (NGCN) Emergency calls Technologies de linformation Tlinformatique R

2、seaux dentreprise de prochaine gnration (NGCN) Appels durgence ISO/IEC TR 16167:2011(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, includin

3、g photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published

4、in Switzerland ii ISO/IEC 2011 All rights reservedISO/IEC TR 16167:2011(E) ISO/IEC 2011 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Normative references 2 3 Terms and definitions . 2 3.1 External definitions . 2 3.2 Other definitions 2 4 Abbreviations . 3 5 Backgrou

5、nd 5 6 Technical aspects of emergency calls in enterprise networks 8 6.1 Identifying a call as an emergency call . 8 6.1.1 User actions . 8 6.1.2 Signalling impact . 10 6.1.3 Unauthenticated access . 12 6.2 Obtaining and delivering the location of the caller 12 6.2.1 Format of location information 1

6、3 6.2.2 Obtaining location information for delivery 13 6.2.3 Location conveyance in SIP . 18 6.3 Routing an emergency call to the appropriate SAP 18 6.3.1 Routing by the calling device . 19 6.3.2 Routing by enterprise SIP intermediary 20 6.4 Delivering information to the SAP to allow a return call o

7、r verification call to be made . 21 6.4.1 Delivery of caller identification 21 6.4.2 Delivery of device identification 21 6.4.3 Identifying a return call or verification call . 22 6.5 Ensuring appropriate resources are available for an emergency call, return call or verification call 22 6.6 Ensuring

8、 appropriate media quality during an emergency call . 23 6.7 Security considerations 24 6.8 Other aspects . 25 6.8.1 Hosted users 25 6.8.2 Guest users 25 7 NGN considerations 25 8 Device considerations 27 9 Alternatives for roaming mobile and nomadic users 28 9.1 Establishing an emergency call when

9、already signalling via a visited public network . 28 9.2 Establishing an emergency call via a visited public network when other traffic is signalled directly via the enterprise network 29 9.3 Establishing an emergency call directly to a PSAP . 29 10 Enterprise responsibilities . 29 11 Summary of req

10、uirements and standardisation gaps . 30 11.1 Requirements on NGNs 30 11.2 Recommendations on enterprise networks . 30 11.3 Standardisation gaps 31 Bibliography 32 ISO/IEC TR 16167:2011(E) iv ISO/IEC 2011 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (th

11、e International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with partic

12、ular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have establ

13、ished a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technic

14、al committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, when the joint technical committee has collected data of a different kind from that which is nor

15、mally published as an International Standard (“state of the art”, for example), it may decide to publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review every five years in the same manner as an International Standard. Attention is drawn to the

16、 possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 16167 was prepared by Ecma International (as ECMA TR/101) and was adopted, under a special “fast-track proc

17、edure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. This second edition cancels and replaces the first edition (ISO/IEC TR 16167:2010), which has been technically revised. This second edition makes a distinction

18、 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. ISO/IEC TR 16167:2011(E) ISO/IEC 2011 All rights reserved vIntroduction This Technical Report is one of a series of publications

19、that provides an overview of 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 session level communication based on the Session Ini

20、tiation Protocol (SIP) 5, with an emphasis on inter-domain communication. This includes communication between 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 Generati

21、on Networks (NGN) as public networks and as providers of hosted enterprise capabilities. Key technical issues 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 refer

22、ence for other standardisation bodies working in this field. 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 Eu

23、rope, ETSI EMTEL (Special Committee on Emergency Communications) 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 emergenc

24、y calls as they impact enterprise networks, and therefore is intended to complement the work of those other bodies. 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 JTC 1, ITU-T,

25、ETSI, IETF and other international and national standardisation bodies. It represents a pragmatic and widely based consensus. In particular, Ecma acknowledges valuable input from experts in ETSI TISPAN, ETSI EMTEL, 3GPP CT1 and IETF ECRIT. TECHNICAL REPORT ISO/IEC TR 16167:2011(E) ISO/IEC 2011 All r

26、ights reserved 1Information technology Telecommunications and information exchange between systems Next Generation Corporate Networks (NGCN) Emergency calls 1 Scope This Technical Report discusses issues related to emergency calls from an enterprise user to a safety answering point (SAP) using the S

27、ession Initiation Protocol (SIP) within a Next Generation Corporate Network (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 ISO/IEC TR 12860. It identifies a number of r

28、equirements impacting Next Generation Network (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 includes

29、 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 calls and v

30、erification 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 the NGC

31、N 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 reachable eit

32、her 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 network to

33、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 call ta

34、ker 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. This als

35、o 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 these reg

36、ulations. 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 limited

37、 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 recognised that s

38、ome users with special needs will require other modes of communication (e.g., real-time text, fax), as discussed in Annex B of 29, 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 human user. There may also be

39、applications ISO/IEC TR 16167:2011(E) 2 ISO/IEC 2011 All rights reservedwhere automatic sensors can make similar emergency calls (subject to regulation), but the special needs of such applications are not considered. 2 Normative references The following referenced documents are indispensable for the

40、 application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC TR 12860, Information technology Telecommunications and information exchange between systems Next Gen

41、eration Corporate Networks (NGCN) General 3 Terms and definitions 3.1 External definitions For the purposes of this document, the following terms defined in ISO/IEC TR 12860 apply: Domain Enterprise network Next Generation Corporate Network (NGCN) Next Generation Network (NGN) Private network traffi

42、c SIP intermediary 3.2 Other definitions For the purposes of this document, the following terms and definitions apply. 3.2.1 authority organisation mandated to receive and respond to reports from individuals of emergency situations involving danger to person or property 3.2.2 emergency call call fro

43、m an enterprise user to a private authority or public authority for the purpose of reporting an emergency situation involving danger to person or property 3.2.3 emergency control centre ECC facilities used by emergency organisations to handle rescue actions in answer to emergency calls NOTE This def

44、inition is taken from 29. 3.2.4 location geographic location geographic position of an entity, in the form of either geospatial coordinates (latitude, longitude, altitude) or a civic address NOTE A civic address can extend to internal landmarks within a site, e.g., building number, floor number, roo

45、m number. ISO/IEC TR 16167:2011(E) ISO/IEC 2011 All rights reserved 33.2.5 location information location or information from which a location can be derived 3.2.6 private authority authority mandated by one or more enterprises to receive and respond to reports of emergency situations from enterprise

46、 users 3.2.7 private emergency answering point PEAP SAP established by a private authority for accepting and responding to emergency calls from users of one or more enterprise networks 3.2.8 public authority authority mandated to receive and respond to reports of emergency situations from the genera

47、l public (including enterprises) 3.2.9 public safety answering point PSAP SAP established by a public authority for accepting and responding to emergency calls from the general public (including enterprises) NOTE The term PSAP is defined by the IETF in RFC 5012 14. The definition above is used in th

48、is Technical Report to stress the difference between a PSAP and a PEAP. 3.2.10 return call call from a SAP to a caller or device that recently made an emergency call 3.2.11 safety answering point SAP answering point established by an authority for the purpose of accepting and responding to emergency

49、 calls 3.2.12 verification call call from a SAP to a person or device that can assist in verifying conditions reported during a recent emergency call NOTE Verification calls are frequently used when emergency calls have been made by sensor devices. For example, a verification call could be to another device in the vicinity, such as a camera. 4 Abbreviations A-GPS Assisted GPS AOR Address Of Record ALI Automatic Location Identification CSTA Computer Supported Telecommunications Applications DHCP Dynamic Host C