VoIP Emergency Calling E-Book

Karl Heinz Wolf

• Herausgeber: John Wiley & Sons
• Kategorie: Wissenschaft und neue Technologien
• Sprache: Englisch

Seitenzahl: 342

Veröffentlichungsjahr: 2010

Beschreibung

This book provides a comprehensive view of the emerging standards for VoIP emergency calling from an International perspective

In this book, the authors provide a treatment of the VoIP emergency calling process that is both comprehensive, looking at all aspects of emergency calling, and practical, providing technical details on how such functions can be implemented. In addition, the authors describe the standardization efforts of the Internet Engineering Task Force who are currently working to improve the situation for VoIP emergency calls. The book provides an overview of emergency calling with a particular focus on the ECRIT emergency calling architecture, and discusses considerations related to implementation, deployment, and regulation of next-generation emergency calling. It also takes a look at practical aspects of emergency calling, with a set of exercises to help the reader get familiar with the technologies involved.

Key Features:

• Comprehensive view of emerging standards for VoIP emergency calling from an international perspective
• Practical guides for implementing the core of the emergency calling architecture
• Architectural, practical, and regulatory perspectives
• Written by experts working on the development of emergency calling architectures and its implementation
• Includes an accompanying website with open-source software packages (http://www.voip-sos.net/)

This book will be an invaluable resource for product managers and developers, equipment vendors, network operators, emergency service providers, and telecommunications regulators. Industry professionals interested in standards compliance will also find this book of interest.

Leseprobe

Table of Contents

Title Page

Copyright

Foreword

Useful Links

List of Abbreviations

Chapter 1: Introduction

1.1 Calling over the Internet

1.2 VoIP Emergency Calling Problem Statement

1.3 Emergency Communication

1.4 Overview of this Book

Chapter 2: Emergency Calling

2.1 Overview

2.2 Infrastructure Requirements

2.3 The Role of Location Information

Chapter 3: The ECRIT Emergency Calling Architecture

3.1 Overview

3.2 Location Information

3.3 Service URNs

3.4 Determining the Appropriate PSAP—the LoST Protocol

3.5 The Emergency Call Itself

3.6 Home Dial String Configuration via LoST

3.7 Deployment Models

3.8 Considerations for Proxies

3.9 Standardization

3.10 Summary

Chapter 4: Including Location Information

4.1 Location Configuration

4.2 Positioning Using GPS

4.3 Network-Based Positioning

4.4 Location Hiding

4.5 Default Location

Chapter 5: Implementation and Regulatory Considerations

5.1 Distribution of Implementation Tasks

5.2 Austria

5.3 The United States

5.4 The European Union

5.5 Japan

5.6 Summary

Chapter 6: VoIP Emergency Calling in Practice

6.1 Software

6.2 Practice Exercises

Chapter 7: Security

7.1 ECRIT Security

7.2 Location Security

7.3 PSAP and VoIP Network Security

Chapter 8: Ongoing Emergency Calling Work

8.1 Prototyping, Implementation, and Interoperability

8.2 Ongoing Standardization Issues

8.3 Ongoing Implementation Issues

Chapter 9: Summary and the Outlook for the Future

Index

This edition first published 2011

© 2011 John Wiley & Sons Ltd.

Registered office

John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom

For details of our global editorial offices, for customer services and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com.

The right of the author to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988.

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher.

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.

Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. The publisher is not associated with any product or vendor mentioned in this book. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold on the understanding that the publisher is not engaged in rendering professional services. If professional advice or other expert assistance is required, the services of a competent professional should be sought.

Library of Congress Cataloging-in-Publication Data

Barnes, Richard, 1982-

VoIP emergency calling : foundations and practice / Richard Barnes, Karl Heinz Wolf.

p. cm.

Includes bibliographical references and index.

ISBN 978-0-470-66594-7 (cloth)

1. Internet telephony. 2. Telephone–Emergency reporting systems. I. Wolf, Karl Heinz, 1982- II. Title.

TK5105.8865.B36 2011

384.6' 4—dc22

2010033579

A catalogue record for this book is available from the British Library.

Print ISBN: 978-0-470-66594-7 (H/B)

ePDF ISBN: 978-0-470-97696-8

oBook ISBN: 978-0-470-97697-5

ePub ISBN: 978-0-470-97694-4

Foreword

In an emergency, it has become natural to reach for the nearest telephone in order to obtain assistance from Law Enforcement, the Fire Department, or the emergency services (EMS). From any common fixed or mobile telephone, you dial an emergency number, and the telecommunications provider routes the emergency call in such a way that it will be delivered to the control center for the proper emergency service. The caller's number is sent along with the call and the calling location is made available.

With Internet telephony (Voice over IP, or VoIP), the situation is a little more complicated. It is often possible for a caller to dial into the VoIP system and make or receive calls no matter where he is, as long as he has a suitable Internet connection. Making the clear correspondence between a calling number and a geographical location is more difficult (or may not happen at all). For VoIP service operators, the extreme case means failure to deliver an emergency call, since the caller's whereabouts are unknown.

In the United States, for example, it is required that the caller's “registered location” be part of the emergency calling process. This means that the caller has to pre-identify the location of their VoIP interface connection. However, if the caller is nomadic, moving periodically to another service location, and they do not update the emergency service record to reflect their new location, their subsequent emergency call may well be routed to the wrong place. The challenge for the future, then, is how to accomplish automatic location update, based on where the caller really is when they make that critical emergency contact. Looking forward to the day when VoIP emergency calls are supported with the technology to supply current location involves development and convergence of technical and operational standards.

In my role as Technical Issues Director for the National Emergency Number Association (NENA), I welcome the authors' initiative in presenting this publication to give interested readers comprehensive theoretical and practical guidance on emergency calling over the Internet.

Roger Hixson

Technical Issues Director—NENA

Useful Links

Throughout this book there are many references to documents of the Internet Engineering Task Force (IETF). In the jargon of the IETF, RFCs are permanent, archival documents that reflect the consensus of the IETF, while Internet-drafts are working documents (which often eventually become RFCs); all RFCs start as Internet-drafts. All of these documents can be quickly accessed by name using the IETF document retrieval service. The document named “document-name” can be accessed at the URI http://tools.ietf.org/html/[document-name]. For example:

– draft-ietf-ecrit-framework can be found at http://tools.ietf.org/html/draft-ietf-ecrit-framework– RFC 5582 can be found at http://tools.ietf.org/html/rfc5582

In cases where the document name is unclear, you can also search for author names or titles on the general IETF document site at http://tools.ietf.org/html/.

Currently, ECRIT and GEOPRIV are still refining these standards and developing new documents to address a few remaining use cases. There are thus more documents being developed than are referenced specifically in this book, so you can also refer to the working group status pages:

– GEOPRIV: http://tools.ietf.org/wg/geopriv/– ECRIT: http://tools.ietf.org/wg/ecrit/– SIPCORE: http://tools.ietf.org/wg/sipcore/

These pages will give you the latest information on the state of play regarding the Internet standards being developed by these groups.

List of Abbreviations

Topics covered in this book involve several different technical areas, standards organizations, and regions of the world. This broad array of topics brings with it a wide array of jargon and acronyms. This list is provided as a reference point for the abbreviations in the main text.

3GPPThird-Generation Partnership ProjectADSLAsymmetric Digital Subscriber LineAJAXAsynchronous Javascript And XMLAK-TKArbeitskreis für technische Koordination (Technical Coordination working group, Austria)ALIAutomatic Location IdentificationANIAutomatic Number IdentificationANSIAmerican National Standards InstituteATOCAAuthority-to-Citizen Alerting (IETF working group)BAKOMBundesamt für Kommunikation (Federal Office of Communications, Switzerland)BCPBest Current Practices (IETF document type)BERECBody of European Regulators for Electronic CommunicationsCDPCisco Discovery ProtocolCGALIESCo-ordination Group on Access to Location Information by Emergency ServicesCIDContent-IDCPECustomer Premise EquipmentCSCFCall Session Control FunctionDHCPDynamic Host Configuration ProtocolDHCPv6Dynamic Host Configuration Protocol for IPv6DNSDomain Name SystemDNSSECDomain Name System Security ExtensionsDOPDilution of PrecisionDSLDigital Subscriber LineECRITEmergency Context Resolution with Internet Technologies (IETF working group)EENAEuropean Emergency Number AssociationEGEAExpert Group on Emergency AccessELINEmergency Location Identification NumberEMTELEmergency Telecommunications (ETSI working group)EPSGEuropean Petroleum Survey GroupESGWEmergency Services GatewayESInetEmergency Services IP network (NENA)ESWEmergency Services WorkshopETSIEuropean Telecommunications Standards InstituteEUEuropean UnionFCCFederal Communications Commission (US)FGForest GuideFMKForum Mobilkommunikation (Mobile Communications Forum, Austria)FTTHFiber to the HomeGEOPRIVGeolocation and Privacy (IETF working group)GMLGeography Markup LanguageGMTGreenwich Mean TimeGPSGlobal Positioning SystemHELDHTTP Enabled Location DeliveryHTTPHypertext Transfer ProtocolHTTPSHTTP SecureIANAInternet Assigned Numbers AuthorityICEIndustry Collaboration Event (NENA)IEEEInstitute for Electrical and Electronics EngineersIETFInternet Engineering Task ForceIMSIP Multimedia SubsystemIMSIInternational Mobile Subscriber IdentityIPInternet ProtocolIPv4Internet Protocol version 4IPv6Internet Protocol version 6ISCInternet Systems ConsortiumISOInternational Organization for StandardizationISPInternet Service ProviderITU-TInternational Telecommunication Union—Telecommunication Standardization SectorKEM-VKommunikationsparameter-, Entgelt- und Mehrwertdiensteverordnung (Communications Parameters, Fees and Value-Added Services Ordinance, Austria)LCPLocation Configuration ProtocolLISLocation Information ServerLLDPLink-Layer Discovery ProtocolLLDP-MEDLink-Layer Discovery Protocol—Media Endpoint DiscoveryLoSTLocation-to-Service Translation ProtocolLRFLocation Retrieval FunctionMICMinistry for Internal Affairs and Communications (Japan)MIMEMultipurpose Internet Mail ExtensionsMLTSMulti-Line Telephone SystemMSAGMaster Street Address GuideNAPTRNaming Authority PointerNATNetwork Address TranslationNENANational Emergency Number Association (US)NG112Next Generation 112NG9-1-1Next Generation 9-1-1NICCNetwork Interoperability Consultative Committee (UK)OASISOrganization for the Advancement of Structured Information StandardsOMAOpen Mobile AlliancePBXPrivate Branch ExchangePEACEIP-Based Emergency Application and Services for Next-Generation NetworksPIDF-LOPresence Information Data Format—Location ObjectPSAPPublic Safety Answering PointPSTNPublic Switched Telephone NetworkRFCRequest For Comments (IETF document type)RFIDRadio-Frequency IdentificationRTPReal-Time ProtocolRTRRundfunk und Telekom Regulierungs-GmbH (Regulatory Authority for Broadcasting and Telecommunications, Austria)SBCSession Border ControllerSDPSession Description ProtocolSIMSubscriber Identity ModuleSIPSession Initiation ProtocolSIPCORESession Initiation Protocol Core (IETF working group)SIPSSession Initiation Protocol SecureSMSShort Message ServiceSNMPSimple Network Management ProtocolSQLStructured Query LanguageSRSSpatial Reference SystemTBDTo Be DeterminedTCPTransmission Control ProtocolTIATelecommunications Industry AssociationTKGTelekommunikationgesetz (Telecommunications Act, Austria)TLSTransport Layer SecurityUDPUser Datagram ProtocolURIUniform Resource IdentifierURLUniform Resource LocatorURNUniform Resource NameUTCCoordinated Universal TimeUTF-8Unicode Transformation Format (8-bit)VDSLVery-high-bitrate Digital Subscriber LineVPCVoIP Positioning CenterVPNVirtual Private NetworkVoIPVoice over IPVSPVoIP Service ProviderW3CWorld Wide Web ConsortiumWGS84World Geodetic System, 1984WLANWireless Local Area NetworkXCAPXML Configuration Access ProtocolXMLExtensible Markup LanguageXMPPExtensible Messaging and Presence ProtocolXPCOMCross Platform Component Object Model

1

Introduction

Emergency calling is a critical function of current telephone networks. Emergency calls are placed in order to prevent danger to life and limb, as well as to property and the environment. In an emergency, it's essential that appropriate responders arrive quickly, so an emergency call must be routed directly to the responsible emergency call center. The police in Vienna, Austria alone receive 3,000 to 4,000 calls each day—from fixed-line telephones, mobile phones, and Internet phones.

This “VoIP Emergency Calling” book is focused on emergency calls that are placed using Voice over IP (VoIP) (and thus carried over the Internet), since these calls often receive inadequate service. We will describe the standardization activities of the Internet Engineering Task Force (IETF) devoted to bettering this situation for VoIP emergency calls, and then delve into them in a more practical terms. This book is intended for several audiences interested in emergency services: operators of emergency call centers, VoIP services, and IP networks; vendors of VoIP telephones and software; representatives of regulatory bodies. Those who are focused more on operational considerations will be able to explore several scenarios with the help of the Practice chapter.