TIA TSB-146-A-2007 Telecommunications IP Telephony Infrastructures IP Telephony Support for Emergency Calling Service《通信 IP电话基础设施 紧急呼叫业务用IP电话支持》.pdf

《TIA TSB-146-A-2007 Telecommunications IP Telephony Infrastructures IP Telephony Support for Emergency Calling Service《通信 IP电话基础设施 紧急呼叫业务用IP电话支持》.pdf》由会员分享，可在线阅读，更多相关《TIA TSB-146-A-2007 Telecommunications IP Telephony Infrastructures IP Telephony Support for Emergency Calling Service《通信 IP电话基础设施 紧急呼叫业务用IP电话支持》.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、 TSB-146-A March 2007R/11-2012Telecommunications IP Telephony Infrastructures IP Telephony Support for Emergency Calling Service NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, fac

2、ilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from ma

3、nufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with

4、the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated

5、with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-4726-RV1-RF1, formulated under the cogni

6、zance of the TIA TR-41 User Premises Telecommunications Requirements. TR-41.4 Subcommittee on VoIP Systems- IP Telephony Infrastructure and Endpoints). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 1320 N. Courthouse Road Arlington, VA 22201 U.S.A. PRICE: P

7、lease refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE O

8、F COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact the TIA Standards Departmen

9、t or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) there is no assurance that the Document will be approved by any Comm

10、ittee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending o

11、r issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the

12、 Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opi

13、ne or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more N

14、ormative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional el

15、ements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see E

16、ngineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending p

17、atent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIM

18、ED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSI

19、BILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COM

20、PLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, L

21、OSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS

22、HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TSB-146-A i Table of Contents 1 Introduction . 1 2 Scope . 1 3 References 3 4 Definitions, Abbreviations and Acronyms 4 4.1 Definitions 4 4.2 Abbreviations and Acronyms. 4 5 Regulatory Consideration. 6 6 Voice over IP

23、 Networks. 6 7 Requirements Summary . 6 7.1 Basic. 6 7.2 Dialing 7 7.3 Originating Call Blocking 7 7.4 Alternate Routing . 7 7.5 Attendant/Staff Notification. 7 8 Determining Caller Location 8 8.1 Network Based Solutions to IP Telephony Caller Location 8 8.1.1 SNMP based solution 8 8.1.1.1 Switch ba

24、sed solution 8 8.1.1.2 LLDP-MED Enhancement of the Switch Based SNMP Solution . 10 8.1.2 DHCP tracker based solution for delivery of ECS LCI to endpoint. 12 8.1.2.1 Interface between DHCP server and Location Mapping Function (or Wall Jack Map) 13 8.1.3 LLDP-MED based solution for delivery of ECS LCI

25、 to Endpoint. 13 8.1.4 LLDP-MED based solution using direct LIS update by endpoint 15 8.1.5 Enterprise Wide-Area Network 16 8.1.6 The Transient User 16 8.2 Set-based Solutions 16 8.2.1 Positioning Beacon . 17 8.2.2 Bluetooth 17 9 Providing Caller Location Information for Selective Routing and for De

26、livery to PSAP. 18 9.1 Call Setup Associated Signaling of Location Information. 19 9.2 Non-Call Setup Associated Signaling of Location Information 19 9.2.1 Associating Location Objects with a Location Query Key 19 9.2.1.1 Example 19 9.2.1.2 Interface between IP Device and Location Update function .

27、22 9.2.2 Sending Non-Call Associated Updates of Location Information to E911 Databases. 22 ii 10 Location Information Server (LIS) 24 10.1 LIS Functions . 24 10.2 LIS Configuration. 25 10.3 LIS Mapping Data 25 10.3.1 LAN Switch Based Method Mapping Data 25 10.3.2 DHCP Based Method Mapping Data 28 10

28、.3.3 LLDP-MED Based Method Mapping Data 28 10.3.4 Non-Call Setup Associated Location Update Method Mapping Data 28 11 Related Activities . 28 12 Related ETSI activities (ETSI SR 002 180) . 29 Annex A : Prospective 30 TSB-146-A iii List of Tables Table 1, LIS Database. 26 Table 2, ELIN to ERL Mapping

29、 . 27 Table 3, IP Address/Router resolution 27 FOREWORD This Telecommunication System Bulletin (TSB) contains information concerning IP Telephony support for Emergency Calling Service (ECS), better known as Enhanced 911 in US and Canada. It addresses calls placed from IP Telephone terminals connecte

30、d to an Enterprise IP. This document was prepared by subcommittee TR-41.4 (IP Telephony Infrastructure) of TIA. A TSB is not an industry standard, and compliance with its contents is not mandatory. This information is an extension to the current ANSI/TIA-689-A-2003, for IP Telephony support of ECS.

31、We encourage parties with additional information or contrary views to contact us so that all concerns may be addressed in an open process. The TR-41.4 IP Telephony Infrastructures Subcommittee (Chair: Avaya, Joanne McMillen, Vice Chair: Nortel, Roger Britt and Secretary: Avaya, Joachim Pomy) acknowl

32、edges the contributions provided by the following individuals in the development of this TSB. Name Representing Previous Versions TSB-146-A Nadine Abbott Telcordia null Manfred Arndt Hewlett Packard null Bob Bell Cisco Systems null null Peter Blatherwick Mitel Networks null Roger Britt Nortel Networ

33、ks null null Tony Caggiano Lucent Technologies null Dick Frank Siemens null Dick Frank Dietrich Lockard Group null Raymond Gass Alcatel Editor Richard Hatherill Mitel Networks null Marc Linsner Cisco Systems Editor null Dorothy Lockard Dietrich Lockard Group null null Joanne McMillen Avaya Inc. null

34、 null Kirit Patel Cisco Systems null null Dave Vander Maiden Siemens null null Arnaud Vergnol Alcatel Editor Mo Zonoun, Nortel Networks Editor iv TSB-146-A Suggestions for improvement of this document are welcome. They should be sent to: Telecommunications Industry Association Engineering Department

35、 Suite 300 250 Wilson Boulevard Arlington, VA 22201 v TSB-146-A 1 Introduction This TSB reviews the problems that need to be solved to support Emergency Calling Service (ECS) from IP Telephony terminals connected to an Enterprise IP network. It addresses various Enterprise Network (EN) topologies, a

36、nd describes possible solutions. The ECS in US and Canada is known as E911. An explanation of how E911 calling works may be found in 1. That TSB provides information that was used to develop 2, a standard for PBX and KTS support of enhanced 911 calling. But, that standard was written before IP Telep

37、hony was a practical consideration. This TSB provides information that should be useful in addition to referenced standards. IP Telephony, sometimes called Voice-over-Internet-Protocol (VoIP), is a new and evolving technology. When an EN provides IP Telephony service, it needs to solve the same E911

38、 support problems faced by conventional telephony. It needs the capability of determining the callers location and call back number, routing the call to the appropriate Public Safety Answering Point (PSAP), and conveying the location and call back information to that PSAP. But, IP Telephony needs ne

39、w solutions to accommodate its unique features. 2 Scope Emergency calling solutions exist to retrieve users information and geolocation for both E.164 and PLMN telephone networks: An E.164 emergency call relies on the public phone directory to retrieve information; A PLMN emergency call relies on Ce

40、ll Ids and radio triangulation process to retrieve information. This TSB covers issues associated with support of ECS from IP Telephony terminals connected to an Enterprise Network (EN). It describes new network architecture elements needed to support ECS, and the functionality of those new elements

41、, in North America. Many countries have similar ECS requirements. Portions of this document may be applicable in providing guidance in solutions for those requirements. This TSB addresses ECS calls placed from fixed, mobile, remote dial-in, or wireless access VoIP terminals, as shown in Figure 1. Th

42、is figure also illustrates similar access scenarios for ECS calls placed directly through an ISP. Solutions contained within this TSB may apply to the non-enterprise environment as well. This TSB does not address scenarios for devices connected to VoIP networks through gateways. Use cases: (A) EN ma

43、y be directly accessed by the users terminal, without crossing a tiers network. (B) EN may also be accessed through one (or several) tiers network(s): o (B.1) Case of multi-site enterprises, using leased-links to connect distant sites; o (B.2) Case of public access point based connection, using VPN

44、o (B.3) Case of private (residential) access point based solution, also using VPN. 1 (C) EN may finally be accessed by a “guest” terminal, that doesnt belong to the enterprise fleet, but that anyway tries to setup an emergency call. Cases (A) and (B.1) are covered by immediate solutions, while cases

45、 (B.2), (B.3) and (C) are mentioned for further study, some material being proposed in the document annexes. Many ECS support issues will require further investigation, and are beyond the scope of this document. These include for example: Dialing procedures Call Reliability Call set-up delay Call qu

46、euing Calling feature override (e.g. call forwarding, call waiting, call conferencing, caller ID suppression, call priority interruption 18 and do not disturb.) Access by persons with disabilities (e.g. TDD devices) Language-based call routing Use of a Private Safety Answering Point Transmission of

47、supplementary call data (e.g. biometrics) Please note that using managed, switched infrastructure described in this TSB does not necessarily provide a solution for the problem of remote access via VPN connectivity It also assumes that a sufficient number of local tandem ECS trunk connections exist t

48、o allow for routing to the appropriate PSAP. LAN IP Phone Mobile IP Phone PSTN Router ALI DatabasePSAP A Terminal Agent A Agent B Agent X E911 switch Figure 1. ECS Network Configuration 2 TSB-146-A 3 References The following standards and TSBs contain provisions, which are referenced in this documen

49、t. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of currently valid national standards published by them. 1. PBX and KTS Support of Enhanced 9-1-1 Emergency Service Calling, TIA/EIA-689-A-.2003 2. Network Interfaces for E9-1-1 and Emerging Technologies, NENA Technical Information Document, Is