1、 TIA TELECOMMUNICATIONS SYSTEMS BULLETIN Telecommunications IP Telephony Infrastructures IP Telephony Support for Emergency Calling Service TSB-146 MARCH 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecom
2、munications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufact
3、urers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmem
4、ber of TIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA members, whether the standard is to be used either domestically or internationally. Sta
5、ndards, Publications and Bulletins are adopted by TIA in accordance with 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, Publication, or
6、 Bulletin. Further details of the development process are available in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm Technical Bulletins are distinguished from TIA Standards or Documents, in that they contain a compilation of engineering data or
7、information useful to the technical community, and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineering practice, or that may be acceptabl
8、e to, or have been accepted by, appropriate bodies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this Bulletin are encouraged to do so. It is the intention of the formulating committee to review this do
9、cument every five years, but it maybe revised and updated at any time as may be occasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons. (From Project No. 3-4726, formulated under the cognizance of the TIA TR-41.4 Subcommittee on IP Telepho
10、ny Gateways and Infrastructure.) . Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2003 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIO
11、NS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under license with EI
12、ANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF DISCLAIMER AND LIMITATION OF LIABILITY The document to which this Notice is affixed (the “Document”) has been prepared by one or more Engineering Committees or Formulating Groups of the Telecommunications I
13、ndustry Association (“TIA”). TIA is not the author of the Document contents, but publishes and claims copyright to the Document pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees and Formulating Groups are expected to conduct their affairs in accor
14、dance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are available at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm. TIAs function is to administer the process, but not the content, of document preparation in accordance with the Manual and, w
15、hen appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). TIA does not evaluate, test, verify or investigate the information, accuracy, soundness, or credibility of the contents of the Document. In publishing the Document, TIA disclaims any undertaking to pe
16、rform any duty owed to or for anyone. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of p
17、atents 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 Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity
18、of any claims of IPR. 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 DISCLA
19、IMED, 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 NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPO
20、NSIBILITIES 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
21、COMPLY 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
22、, LOSS 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 CONTEN
23、TS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-PLEASE! DONT VIOLATETHELAW!This document is
24、 copyrighted by the TIA and may not be reproduced without prior permission of the Telecommunications Industry Association. For information consult our website at http:/www.tiaonline.org/about/faqDetail.cfm?id=18 Organizations may obtain permission to reproduce a limited number of copies through ente
25、ring into a license agreement. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 U.S.A. or call U.S.A. and Canada 1-800-854-7179, International (303) 397-7956 Copyright Telecommunications Industry Association Provided by IHS under license with EIAN
26、ot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 1 TABLE OF CONTENTS 1. INTRODUCTION . 4 2. SCOPE 5 3. REFERENCES 7 4. DEFINITIONS, ABBREVIATIONS AND ACRONYMS . 9 4.1. ABBREVIATIONS AND ACRONYMS. 9 5. REGULATORY CONSIDERATION . 11 6. VOICE OVER IP NETWORKS 12
27、 7. REQUIREMENTS SUMMARY 13 7.1 BASIC 13 7.2 DIALING 13 7.3 ORIGINATING CALL BLOCKING. 14 7.4 ALTERNATE ROUTING. 14 7.5 ATTENDANT/STAFF NOTIFICATION 14 8. SOLUTIONS 15 8.1. DETERMINING CALLER LOCATION . 15 8.1.1. Network Based Solutions to IP Telephony Caller Location. 15 8.1.1.1 Enterprise Applicat
28、ion (with Call Agent) 15 8.1.1.1. 1 SNMP Basic Components. 16 8.1.1.1.1.1 Managed Device 16 8.1.1.1.1.2. Agent 16 8.1.1.1.1.3. Network Management System (NMS) 16 8.1.1.1.2. Call Agent 17 8.1.1.1.3 Location Information Server (LIS) 17 8.1.1.1.3.1 Location Information (LIS) Configuration 18 8.1.1.1.4.
29、 Operation 19 8.1.1.1.5. Enterprise Wide-Area Network 25 8.1.1.1.6. The Transient User 25 8.1.1.2 Centrex Application (Hybrid Approach) 25 8.1.2. Set-based Solutions . 27 8.1.2.1. Architecture. 28 8.1.2.2. Positioning Beacon 28 8.1.2.2.1. Beacon Signaling 28 8.1.2.2.1.1. Bluetooth 28 8.1.2.2.1.2. GP
30、S 28 8.2. LOCATION INFORMATION FORMAT . 29 9. RELATED ACTIVITIES . 30 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 2 LIST OF FIGURES Figure 1, ECS Network configurati
31、on . 6 Figure 2, Relationship Between NMS and Managed Devices. 17 Figure 3, Automatic Upload of Location Information. 19 Figure 4, LIS Logical Processing. 22 Figure 5, LIS Communications 23 Figure 6, 911 Call Progression. 24 Figure 7, Hybrid Approach IP Device and LIS Communications 27 Figure 8, Mes
32、sage Flow Among Various Components of the Set Based Solution 29 LIST OF TABLES Table 1, Network-Based and Set-Based Comparison 15 Table 2, LIS Database 19 Table 3, ELIN to ERL Mapping 20 Table 4, IP Address/Router resolution. 21 Copyright Telecommunications Industry Association Provided by IHS under
33、 license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 3 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.
34、 It addresses calls placed from IP Telephone terminals connected 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
35、 current TIA/EIA 689 1997, for IP Telephony support of ECS. 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 Engineering Technical Subcommittee acknowledges the contribution made by the following in
36、dividuals in the development of this document. Name Representing Bob Bell Cisco Systems Chair Roger Britt Nortel Networks Tony Caggiano Lucent Technologies Dick Frank Dietrich Lockard Group Dorothy Lockard Dietrich Lockard Group Richard Hatherill Mitel Networks Marc Linsner Cisco Systems Dorothy Loc
37、kard Dietrich Lockard Group Joanne McMillen Avaya Inc. Kirit Patel Cisco Systems Mo Zonoun, Nortel Editor Suggestions for improvement of this document are welcome. They should be sent to: Telecommunications Industry Association Engineering Department Suite 300 250 Wilson Boulevard Arlington, VA 2220
38、1 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 4 Introduction This TSB reviews the problems that must be solved to support Emergency Calling Service (ECS) from IP Tel
39、ephony terminals connected to an Enterprise IP network. It addresses various Enterprise Network (EN) topologies, and describes possible solutions. The ECS in US and Canada is known as E911. An explanation of how E911 calling works may be found in TSB103-1993 Reference 1. That TSB provides informatio
40、n that was used to develop TIA/EIA-689-1997 Reference 2, a standard for PBX and KTS support of enhanced 911 calling. But, that standard was written before IP Telephony was a practical consideration. This TSB provides information that should be useful in addition to referenced standards. IP Telephony
41、, sometimes called Voice-over-Internet-Protocol (VoIP), is a new and evolving technology. When an EN provides IP Telephony service, it must solve the same E911 support problems faced by conventional telephony. It must have the capability of determining the callers location and call back number, rout
42、ing the call to the appropriate Public Safety Answering Point (PSAP), and conveying the location and call back information to that PSAP. But, IP Telephony must use new solutions to accommodate its unique features. Copyright Telecommunications Industry Association Provided by IHS under license with E
43、IANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 5 Scope 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 th
44、e functionality of those new elements. Many countries have similar ECS requirements. Portions of this document may be applicable in providing solutions for those requirements. This TSB addresses ECS calls placed from fixed, mobile, remote dial-in, or wireless access VoIP terminals, as shown in Figur
45、e 1. This 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. Many ECS supp
46、ort 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 queuing Calling feature override (e.g. call forwarding, call waiting, call conferencing, caller ID suppression, and do not d
47、isturb.) Access by persons with disabilities (e.g. TDD devices) Language-based call routing Use of a Private Safety Answering Point Transmission of supplementary call data (e.g. biometrics) Please note that using managed, switched infrastructure described in this TSB does not necessarily provide a s
48、olution for the problem of remote access via VPN connectivity. It should be further noted that the determination of the appropriate PSAP to delivery of the ECS call is not detailed in this TSB. It also assumes that a sufficient number of local tandem ECS trunk connections exist to allow for a direct
49、 connection to the appropriate PSAP. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TSB-146 Enterprise IPNetworkremote uservpnremote uservpnMobile UserWireless UserRouterGatewayPSTNE911 TandemSwitchfixed localterminalCAMA/DSS1PSAP ATerminalTelephoneALIData
