tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

RFC 7852

Proposed STD
Pages: 113
Top     in Index     Prev     Next
in Group Index     Prev in Group     No Next: Highest Number in Group     Group: ECRIT

Additional Data Related to an Emergency Call

Part 1 of 5, p. 1 to 22
None       Next Section

Updates:    6443    6881


Top       ToC       Page 1 
Internet Engineering Task Force (IETF)                        R. Gellens
Request for Comments: 7852
Updates: 6443, 6881                                             B. Rosen
Category: Standards Track                                        NeuStar
ISSN: 2070-1721                                            H. Tschofenig

                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                         J. Winterbottom
                                             Winterb Consulting Services
                                                               July 2016


              Additional Data Related to an Emergency Call

Abstract

   When an emergency call is sent to a Public Safety Answering Point
   (PSAP), the originating device, the access network provider to which
   the device is connected, and all service providers in the path of the
   call have information about the call, the caller, or the location,
   which is helpful for the PSAP to have in handling the emergency.
   This document describes data structures and mechanisms to convey such
   data to the PSAP.  The intent is that every emergency call carry as
   much of the information described here as possible using the
   mechanisms described here.

   The mechanisms permit the data to be conveyed by reference (as an
   external resource) or by value (within the body of a SIP message or a
   location object).  This follows the tradition of prior emergency
   services standardization work where data can be conveyed by value
   within the call signaling (i.e., in the body of the SIP message) or
   by reference.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7852.

[Page 2] 
Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Data Structures . . . . . . . . . . . . . . . . . . . . . . .   7
    4.1.  Data Provider Information. . . . . . . . . . . . . . . . .   9
     4.1.1.  Data Provider String  . . . . . . . . . . . . . . . . .   9
     4.1.2.  Data Provider ID .  . . . . . . . . . . . . . . . . . .   9
     4.1.3.  Data Provider ID Series . . . . . . . . . . . . . . . .  10
     4.1.4.  Type of Data Provider . . . . . . . . . . . . . . . . .  11
     4.1.5.  Data Provider Contact URI . . . . . . . . . . . . . . .  12
     4.1.6.  Data Provider Language(s) Supported . . . . . . . . . .  13
     4.1.7.  xCard of Data Provider  . . . . . . . . . . . . . . . .  14
     4.1.8.  Subcontractor Principal . . . . . . . . . . . . . . . .  14
     4.1.9.  Subcontractor Priority  . . . . . . . . . . . . . . . .  15
     4.1.10. ProviderInfo Example  . . . . . . . . . . . . . . . . .  15
    4.2.  Service Information  . . . . . . . . . . . . . . . . . . .  18
     4.2.1.  Service Environment . . . . . . . . . . . . . . . . . .  18
     4.2.2.  Service Type  . . . . . . . . . . . . . . . . . . . . .  19
     4.2.3.  Service Mobility Environment .  . . . . . . . . . . . .  21
     4.2.4.  EmergencyCallData.ServiceInfo Example . . . . . . . . .  22
    4.3.  Device Information . . . . . . . . . . . . . . . . . . . .  22
     4.3.1.  Device Classification . . . . . . . . . . . . . . . . .  22
     4.3.2.  Device Manufacturer . . . . . . . . . . . . . . . . . .  23
     4.3.3.  Device Model Number . . . . . . . . . . . . . . . . . .  24
     4.3.4.  Unique Device Identifier  . . . . . . . . . . . . . . .  24
     4.3.5.  Device/Service-Specific Additional Data Structure . . .  25
     4.3.6.  Device/Service-Specific Additional Data Structure Type   26
     4.3.7.  EmergencyCallData.DeviceInfo Example  . . . . . . . . .  27
    4.4.  Owner/Subscriber Information . . . . . . . . . . . . . . .  27
     4.4.1.  Subscriber Data Privacy Indicator . . . . . . . . . . .  27
     4.4.2.  xCard for Subscriber's Data . . . . . . . . . . . . . .  28

Top      ToC       Page 3 
     4.4.3.  EmergencyCallData.SubscriberInfo Example  . . . . . . .  29
    4.5.  Comment  . . . . . . . . . . . . . . . . . . . . . . . . .  31
     4.5.1.  Comment . . . . . . . . . . . . . . . . . . . . . . . .  31
     4.5.2.  EmergencyCallData.Comment Example . . . . . . . . . . .  32
   5.  Issues with Getting New Types of Data into Use  . . . . . . .  32
    5.1.  Choosing between Defining a New Type of Block or a New
          Type of Device/Service-Specific Additional Data  . . . . .  33
   6.  Data Transport Mechanisms . . . . . . . . . . . . . . . . . .  33
    6.1.  Transmitting Blocks Using Call-Info  . . . . . . . . . . .  36
    6.2.  Transmitting Blocks by Reference Using the <provided-by>
          Element  . . . . . . . . . . . . . . . . . . . . . . . . .  37
    6.3.  Transmitting Blocks by Value Using the <provided-by>
          Element  . . . . . . . . . . . . . . . . . . . . . . . . .  38
    6.4.  The Content-Disposition Parameter  . . . . . . . . . . . .  39
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  41
   8.  XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . .  53
    8.1.  EmergencyCallData.ProviderInfo XML Schema  . . . . . . . .  54
    8.2.  EmergencyCallData.ServiceInfo XML Schema . . . . . . . . .  56
    8.3.  EmergencyCallData.DeviceInfo XML Schema  . . . . . . . . .  57
    8.4.  EmergencyCallData.SubscriberInfo XML Schema  . . . . . . .  59
    8.5.  EmergencyCallData.Comment XML Schema . . . . . . . . . . .  60
    8.6.  provided-by XML Schema . . . . . . . . . . . . . . . . . .  61
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  62
   10. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  64
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  67
    11.1.  Emergency Call Additional Data Registry . . . . . . . . .  67
     11.1.1.  Provider ID Series Registry  . . . . . . . . . . . . .  67
     11.1.2.  Service Environment Registry . . . . . . . . . . . . .  68
     11.1.3.  Service Type Registry  . . . . . . . . . . . . . . . .  68
     11.1.4.  Service Mobility Registry  . . . . . . . . . . . . . .  68
     11.1.5.  Type of Provider Registry  . . . . . . . . . . . . . .  69
     11.1.6.  Device Classification Registry . . . . . . . . . . . .  69
     11.1.7.  Device ID Type Registry  . . . . . . . . . . . . . . .  69
     11.1.8.  Device/Service Data Type Registry  . . . . . . . . . .  70
     11.1.9.  Emergency Call Data Types Registry . . . . . . . . . .  70
    11.2.  'EmergencyCallData' Purpose Parameter Value . . . . . . .  72
    11.3.  URN Sub-Namespace Registration for <provided-by>
           Registry Entry  . . . . . . . . . . . . . . . . . . . . .  72
    11.4.  MIME Registrations  . . . . . . . . . . . . . . . . . . .  72
     11.4.1.  MIME Content-Type Registration for
              'application/EmergencyCallData.ProviderInfo+xml' . . .  72
     11.4.2.  MIME Content-Type Registration for
              'application/EmergencyCallData.ServiceInfo+xml'  . . .  73
     11.4.3.  MIME Content-Type Registration for
              'application/EmergencyCallData.DeviceInfo+xml' . . . .  74
     11.4.4.  MIME Content-Type Registration for
              'application/EmergencyCallData.SubscriberInfo+xml' . .  75

Top      ToC       Page 4 
     11.4.5.  MIME Content-Type Registration for
              'application/EmergencyCallData.Comment+xml'  . . . . .  76
    11.5.  URN Sub-Namespace Registration  . . . . . . . . . . . . .  78
     11.5.1.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData . . . . . . .  78
     11.5.2.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo . 78
     11.5.3.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo  . 79
     11.5.4.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo . . 80
     11.5.5.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 81
     11.5.6.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:Comment . . .  81
    11.6.  Schema Registrations  . . . . . . . . . . . . . . . . . .  82
    11.7.  vCard Parameter Value Registration  . . . . . . . . . . .  83
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  84
    12.1.  Normative References  . . . . . . . . . . . . . . . . . .  84
    12.2.  Informative References  . . . . . . . . . . . . . . . . .  85
   Appendix A.  XML Schema for vCard/xCard . . . . . . . . . . . . .  89
   Appendix B.  XML Validation . . . . . . . . . . . . . . . . . . . 111
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 112
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 113

1.  Introduction

   When an IP-based emergency call is initiated, a rich set of data from
   multiple data sources is conveyed to the Public Safety Answering
   Point (PSAP).  This data includes information about the calling party
   identity, the multimedia capabilities of the device, the request for
   emergency services, location information, and metadata about the
   sources of the data.  In addition, the device, the access network
   provider, and any service provider in the call path has even more
   information that is useful for a PSAP when handling an emergency.

   This document extends the basic set of data communicated with an
   emergency call based on the Session Initiation Protocol (SIP), as
   described in RFC 6443 [RFC6443] and RFC 6881 [RFC6881], in order to
   carry additional data that is useful to an entity or call taker
   handling the call.  This data is "additional" to the basic
   information found in the emergency call signaling used.  The intent
   is that every emergency call carry as much of the information
   described here as possible using the mechanisms described here.

Top      ToC       Page 5 
   This document defines three categories of this additional data that
   can be transmitted with an emergency call:

   Data Associated with a Location:  Primary location data is conveyed
      in the Presence Information Data Format Location Object (PIDF-LO)
      data structure as defined in RFC 4119 [RFC4119] and extended by
      RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location
      information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for
      geodetic location information), and RFC 7035 [RFC7035] (for
      relative location).  This primary location data identifies the
      location or estimated location of the caller.  However, there
      might exist additional, secondary data that is specific to the
      location, such as floor plans, tenant and building owner contact
      data, heating, ventilation, and air conditioning (HVAC) status,
      etc.  Such secondary location data is not included in the location
      data structure but can be transmitted using the mechanisms defined
      in this document.  Although this document does not define any
      structures for such data, future documents can do so following the
      procedures defined here.

   Data Associated with a Call:  While some information is carried in
      the call setup procedure itself (as part of the SIP headers as
      well as in the body of the SIP message), there is additional data
      known by the device making the call, the access network to which
      the device is connected, and service providers along the path of
      the call.  This information includes service provider contact
      information, subscriber identity and contact information, the type
      of service the service provider and the access network provide,
      what type of device is being used, etc.  Some data is broadly
      applicable, while other data is dependent on the type of device or
      service.  For example, a medical monitoring device might have
      sensor data.  The data structures defined in this document (Data
      Provider Information, Device Information, and Owner/Subscriber
      Information) all fall into the category of "Data Associated with a
      Call".  Note that the owner/subscriber information includes the
      subscriber's vCard, which might contain personal information such
      as birthday, anniversary, etc., but the data block itself is still
      considered to be about the call, not the caller.

   Data Associated with a Caller:  This is personal data about a caller,
      such as medical information and emergency contact data.  Although
      this document does not define any structures within this category,
      future documents can do so following the procedures defined here.

   While this document defines data structures only within the category
   of Data Associated with a Call, by establishing the overall framework
   of Additional Data, along with general mechanisms for transport of
   such data, extension points, and procedures for future extensions, it

Top      ToC       Page 6 
   minimizes the work needed to carry data in the other categories.
   Other specifications can make use of the facilities provided here.

   For interoperability, there needs to be a common way for the
   information conveyed to a PSAP to be encoded and identified.
   Identification allows emergency services authorities to know during
   call processing which types of data are present and to determine if
   they wish to access it.  A common encoding allows the data to be
   successfully accessed.

   This document defines an extensible set of data structures, and
   mechanisms to transmit this data either by value or by reference,
   either in the SIP call signaling or in the PIDF-LO.  The data
   structures are usable by other communication systems and transports
   as well.  The data structures are defined in Section 4, and the
   transport mechanisms (using SIP and HTTPS) are defined in Section 6.

   Each data structure described in this document is encoded as a
   "block" of information.  Each block is an XML structure with an
   associated Multipurpose Internet Mail Extensions (MIME) media type
   for identification within transport such as SIP and HTTPS.  The set
   of blocks is extensible.  Registries are defined to identify the
   block types that can be used and to allow blocks to be included in
   emergency call signaling.

   Much of the information supplied by service providers and devices is
   private and confidential.  Service providers and devices generally go
   to lengths to protect this information; disclosing it in the context
   of an emergency call is a trade-off to protect the greater interest
   of the customer in an emergency.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   This document also uses terminology from [RFC5012].  We use the term
   "service provider" to refer to an Application Service Provider (ASP).
   A Voice Service Provider (VSP) is a special type of ASP.  With the
   term "Access Network Provider", we refer to the Internet Access
   Provider (IAP) and the Internet Service Provider (ISP) without
   further distinguishing these two entities, since the difference
   between the two is not relevant for this document.  Note that the
   roles of an ASP and access network provider might be provided by a
   single company.  An Emergency Services Provider is an entity directly
   involved in providing emergency services.  This includes PSAPs,

Top      ToC       Page 7 
   dispatch, police, fire, emergency medical, other responders, and
   other similar agencies.

   Within each data block definition (see Section 4), the values for the
   'Use:' label are specified as one of the following:

   'Required':  means it MUST be present in the data structure.

   'Conditional':  means it MUST be present if the specified
      condition(s) is met.  It MAY be present if the condition(s) is not
      met.

   'Optional':  means it MAY be present.

   vCard [RFC6350] is a data format for representing and exchanging a
   variety of information about individuals and other entities.  For
   applications that use XML, the format defined in vCard is not
   immediately applicable.  For this reason, an XML-based encoding of
   the information elements defined in the vCard specification has been
   defined, and the name of that specification is xCard [RFC6351].
   Since the term vCard is more familiar to most readers, we use the
   terms xCard and vCard interchangeably.

3.  Document Scope

   The scope of this document is explicitly limited to emergency calls.
   The data structures defined here are not appropriate to be conveyed
   in non-emergency calls because they carry sensitive and private data.
   However, in certain private-use situations between a specialized
   service provider (such as a vehicle telematics service provider) and
   dedicated equipment (such as in a vehicle) where the endpoints have a
   preexisting relationship and privacy issues are addressed within the
   relationship, the mechanisms and data structures defined here can be
   used with communications within the limited context of the
   preexisting relationship.

4.  Data Structures

   This section defines the following five data structures, each as a
   data block.  For each block, we define the MIME media type and the
   XML encoding.  The five data structures are:

   'Data Provider':  This block supplies name and contact information
      for the entity that created the data.  Section 4.1 provides the
      details.

   'Service Information':  This block supplies information about the
      service.  The description can be found in Section 4.2.

Top      ToC       Page 8 
   'Device Information':  This block supplies information about the
      device placing the call.  Device information can be found in
      Section 4.3.

   'Owner/Subscriber':  This block supplies information about the owner
      of the device or about the subscriber.  Details can be found in
      Section 4.4.

   'Comment':  This block provides a way to supply free form human-
      readable text to the PSAP or emergency responders.  This simple
      structure is defined in Section 4.5.

   Each block contains a mandatory <DataProviderReference> element.  The
   purpose of the <DataProviderReference> element is to associate all
   blocks added by the same data provider as a unit.  The
   <DataProviderReference> element associates the data provider block to
   each of the other blocks added as a unit.  Consequently, when a data
   provider adds additional data to an emergency call (such as device
   information), it MUST add information about itself (via the data
   provider block), and the blocks added contain the same value in the
   <DataProviderReference> element.  All blocks added by a single entity
   at the same time MUST have the same <DataProviderReference> value.
   (In certain situations, the same provider might process a call more
   than once, likely in different roles, and in such cases, each time it
   processes the call, it adds a new set of blocks with a new
   <DataProviderReference> value.)  The value of the
   <DataProviderReference> element has the same syntax and properties
   (specifically, world-uniqueness) as the value of the 'Message-ID'
   message body header field specified in RFC 5322 [RFC5322] except that
   the <DataProviderReference> element is not enclosed in brackets (the
   '<' and '>' symbols are omitted).  In other words, the value of a
   <DataProviderReference> element is syntactically a msg-id as
   specified in RFC 5322 [RFC5322].

   Each block is added to the "Additional Data Blocks" registry created
   in Section 11.1.9 and categorized as providing data about the caller.
   New blocks added to the registry in the future MUST also be
   categorized per the description of the three categories in Section 1.
   See Sections 5 and 5.1 for additional considerations when adding new
   blocks or types of data.

   Note that the xCard format is reused in some of the data structures
   to provide contact information.  In an xCard, there is no way to
   specify a 'main' telephone number (that is, a primary or main contact
   number, typically of an enterprise, as opposed to a direct-dial
   number of an individual).  These numbers are useful to emergency
   responders who are called to a large enterprise.  This document adds
   a new parameter value called 'main-number' to the 'TYPE' parameter of

Top      ToC       Page 9 
   the 'tel' property.  It can be used in any xCard in an emergency call
   additional data block.

4.1.  Data Provider Information

   This block is intended to be supplied by any service provider in the
   path of the call, or the access network provider, and the device.  It
   includes identification and contact information.  This block MUST be
   supplied by any entity that provides any other block; it SHOULD be
   supplied by every service provider in the call path and by the access
   network provider if those entities do not add any other blocks.
   Devices SHOULD use this block to provide identifying information.
   The MIME media type is 'application/
   EmergencyCallData.ProviderInfo+xml'.  An access network provider
   SHOULD provide this block either by value or by reference in the
   <provided-by> element of a PIDF-LO.

4.1.1.  Data Provider String

   Data Element:  Data Provider String

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.

   XML Element:  <DataProviderString>

   Description:  This is a plaintext string suitable for displaying the
      name of the service provider that supplied the data structure.  If
      the device creates the structure, it SHOULD use the value of the
      contact header field in the SIP INVITE.

   Reason for Need:  Inform the call taker of the identity of the entity
      providing the data.

   How Used by Call Taker:  Allows the call taker to interpret the data
      in this structure.  The source of the information often influences
      how the information is used, believed, or verified.

4.1.2.  Data Provider ID

   Data Element:  Data Provider ID

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.  This data MUST be provided by all
      entities other than the originating device in order to uniquely
      identify the service provider or access provider.

   XML Element:  <ProviderID>

Top      ToC       Page 10 
   Description:  A jurisdiction-specific code for, or the fully
      qualified domain name of, the access network provider or service
      provider shown in the <DataProvidedBy> element that created the
      structure.  NOTE: The value SHOULD be assigned by an organization
      appropriate for the jurisdiction.  In the United States, if the
      provider is registered with NENA, the provider's NENA Company ID
      MUST appear here.  Additional information can be found at the
      National Emergency Number Association (NENA) Company Identifier
      Program <http://www.nena.org/?page=cid2014> or the NENA Company ID
      <http://www.nena.org/?page=CompanyID>.  The NENA Company ID MUST
      be in the form of a URI in the following format:
      urn:nena:companyid:<NENA Company ID>.  If the organization does
      not have an identifier registered with a jurisdiction-specific
      emergency services registrar (such as NENA), then the value MAY be
      the fully qualified domain name of the service provider or access
      provider.  The device MAY use its IP address or fully qualified
      domain name (and set the 'Data Provider ID Series' element to
      'domain').

   Reason for Need:  Inform the call taker of the identity of the entity
      providing the data.

   How Used by Call Taker:  Where jurisdictions have lists of providers,
      the Data Provider ID provides useful information about the data
      source.  The Data Provider ID uniquely identifies the source of
      the data, which might be needed especially during unusual
      circumstances and for routine logging.

4.1.3.  Data Provider ID Series

   Data Element:  Data Provider ID Series

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.

   XML Element:  <ProviderIDSeries>

   Description:  Identifies the issuer of the <ProviderID>.  The
      "Provider ID Series" registry created in Section 11.1.1 initially
      contains the entries shown in Figure 1.

   Reason for Need:  Identifies how to interpret the Data Provider ID.
      The combination of ProviderIDSeries and ProviderID MUST be
      globally unique.

   How Used by Call Taker:  Determines which provider ID registry to
      consult for more information.

Top      ToC       Page 11 
      +-----------+--------------------------+----------------------+
      | Name      | Source                   | URL                  |
      +-----------+--------------------------+----------------------+
      | NENA      | National Emergency       | http://www.nena.org  |
      |           | Number Association       |                      |
      |           |                          |                      |
      | EENA      | European Emergency       | http://www.eena.org  |
      |           | Number Association       |                      |
      |           |                          |                      |
      | domain    | (The ID is a fully       | (not applicable)     |
      |           | qualified domain name)   |                      |
      +-----------+--------------------------+----------------------+

                   Figure 1: Provider ID Series Registry

4.1.4.  Type of Data Provider

   Data Element:  Type of Data Provider

   Use:  Required

   XML Element:  <TypeOfProvider>

   Description:  Identifies the type of data provider supplying the
      data.  The registry containing all valid values is created in
      Section 11.1.5, and the initial set of values is shown in
      Figure 2.

   Reason for Need:  Identifies the category of data provider.

   How Used by Call Taker:  This information can be helpful when
      deciding whom to contact when further information is needed.

Top      ToC       Page 12 
   +------------------------------+------------------------------------+
   | Token                        | Description                        |
   +------------------------------+------------------------------------+
   |Client                        | Originating client/device          |
   |                              |                                    |
   |Access Network Provider       | Access network service provider    |
   |                              |                                    |
   |Telecom Provider              | Telecom service provider (including|
   |                              |    native and over-the-top VoIP    |
   |                              |    services)                       |
   |                              |                                    |
   |Telematics Provider           | A sensor-based service provider,   |
   |                              |    especially vehicle based        |
   |                              |                                    |
   |Language Translation Provider | A spoken language translation      |
   |                              |    service                         |
   |                              |                                    |
   |Emergency Service Provider    | An emergency service provider      |
   |                              |    conveying information to another|
   |                              |    emergency service provider      |
   |                              |                                    |
   |Emergency Modality Translation| An emergency-call-specific         |
   |                              |    modality translation service,   |
   |                              |    e.g., for sign language         |
   |                              |                                    |
   |Relay Provider                | An interpretation service, e.g.,   |
   |                              |    video relay for sign language   |
   |                              |    interpretation                  |
   |                              |                                    |
   |Other                         | Any other type of service provider |
   +------------------------------+------------------------------------+

                 Figure 2: Type of Data Provider Registry

4.1.5.  Data Provider Contact URI

   Data Element:  Data Provider Contact URI

   Use:  Required

   XML Element:  <ContactURI>

   Description:  When provided by a service provider or an access
      network provider, this information is expected to be a URI to a
      24/7 support organization tasked to provide PSAP support for this
      emergency call.  When provided by a device, this MUST be the
      contact information of the user or owner of the device.  (Ideally,
      this is the contact information of the device user, but when the

Top      ToC       Page 13 
      owner and user are separate (e.g., the device owner is an
      organization), this MAY be the contact information of the owner.)
      The Data Provider Contact URI SHOULD be a tel URI [RFC3966] in
      E.164 format and fully specified with a country code.  If a tel
      URI is not available, a generic SIP URI is acceptable.  Note that
      this contact information is not used by PSAPs for callbacks (a
      call from a PSAP directly related to a recently terminated
      emergency call, placed by the PSAP using a SIP Priority header
      field set to 'psap-callback', as described in [RFC7090]).

   Reason for Need:  Additional data providers might need to be
      contacted in error cases or other unusual circumstances.

   How Used by Call Taker:  To contact the supplier of the additional
      data for assistance in handling the call.

4.1.6.  Data Provider Language(s) Supported

   Data Element:  Data Provider Language(s) supported

   Use:  Required

   XML Element:  <Language>

   Description:  This field encodes the language used by the entity at
      the Data Provider Contact URI.  The content of this field consists
      of a single token from the Language Subtag Registry, which can be
      found at [LanguageSubtagRegistry], and is defined in [RFC5646].
      Multiple instances of this element MAY occur, but the order is
      significant and the preferred language SHOULD appear first.  The
      content MUST reflect the languages supported at the contact URI.

      (Note that this field informs the PSAP of the language(s) used by
      the data provider.  If the PSAP needs to contact the data
      provider, it can be helpful to know in advance the language(s)
      used by the data provider.  If the PSAP uses a communication
      protocol to reach the data provider, that protocol might have
      language facilities of its own (such as the 'language' media
      feature tag, defined in RFC 3840 [RFC3840], and the more extensive
      language negotiation mechanism proposed in [HUMAN-LANG]), and if
      so, those are independent of this field.)

   Reason for Need:  This information indicates if the emergency service
      authority can directly communicate with the service provider or if
      an interpreter will be needed.

Top      ToC       Page 14 
   How Used by Call Taker:  If the call taker cannot speak any language
      supported by the service provider, a translation service will need
      to be added to the conversation.  Alternatively, other persons at
      the PSAP, besides the call taker, might be consulted for help
      (depending on the urgency and the type of interaction).

4.1.7.  xCard of Data Provider

   Data Element:  xCard of Data Provider

   Use:  Optional

   XML Element:  <DataProviderContact>

   Description:  Per [RFC6351], the xCard structure is represented
      within a <vcard> element.  Although multiple <vcard> elements can
      be contained in a structure, only one <vcard> element SHOULD be
      provided.  If more than one appears, the first SHOULD be used.
      There are many fields in the xCard, and the creator of the data
      structure is encouraged to provide all available information.  N,
      ORG, ADR, TEL, and EMAIL are suggested at a minimum.  N SHOULD
      contain the name of the support group or device owner as
      appropriate.  If more than one TEL property is provided, a
      parameter from the "vCard Property Values" registry SHOULD be
      specified for each TEL.  For encoding of the vCard, this
      specification uses the XML-based encoding specified in [RFC6351],
      which is referred to in this document as 'xCard'.

   Reason for Need:  Information needed to determine additional contact
      information.

   How Used by Call Taker:  Assists the call taker by providing
      additional contact information aside from what is included in the
      SIP INVITE or the PIDF-LO.

4.1.8.  Subcontractor Principal

   When the entity providing the data is a subcontractor, the Data
   Provider Type is set to that of the primary service provider, and
   this entry is supplied to provide information regarding the
   subcontracting entity.

   Data Element:  Subcontractor Principal

   Use:  Conditional.  This data is required if the entity providing the
      data is a subcontractor.

   XML Element:  <SubcontractorPrincipal>

Top      ToC       Page 15 
   Description:  Some providers outsource their obligations to handle
      aspects of emergency services to specialized providers.  If the
      data provider is a subcontractor to another provider, this element
      contains the DataProviderString of the service provider to
      indicate which provider the subcontractor is working for.

   Reason for Need:  Identify the entity the subcontractor works for.

   How Used by Call Taker:  Allows the call taker to understand what the
      relationship is between data providers and the service providers
      in the path of the call.

4.1.9.  Subcontractor Priority

   Data Element:  Subcontractor Priority

   Use:  Conditional.  This data is required if the entity providing the
      data is a subcontractor.

   XML Element:  <SubcontractorPriority>

   Description:  If the subcontractor is supposed to be contacted first,
      then this element MUST have the value 'sub'.  If the provider the
      subcontractor is working for is supposed to be contacted first,
      then this element MUST have the value 'main'.

   Reason for Need:  Inform the call taker whom to contact first, if
      support is needed.

   How Used by Call Taker:  To decide which entity to contact first if
      assistance is needed.

4.1.10.  ProviderInfo Example

   <?xml version="1.0" encoding="UTF-8"?>
   <ad:EmergencyCallData.ProviderInfo
       xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
       <ad:DataProviderReference>string0987654321@example.org
       </ad:DataProviderReference>
       <ad:DataProviderString>Example VoIP Provider
       </ad:DataProviderString>
       <ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>
       <ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
       <ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider>
       <ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI>
       <ad:Language>en</ad:Language>
       <ad:DataProviderContact
           xmlns="urn:ietf:params:xml:ns:vcard-4.0">

Top      ToC       Page 16 
                   <vcard>
                       <fn><text>Hannes Tschofenig</text></fn>
                       <n>
                           <surname>Hannes</surname>
                           <given>Tschofenig</given>
                           <additional/>
                           <prefix/>
                           <suffix>Dipl. Ing.</suffix>
                       </n>
                       <bday><date>--0203</date></bday>
                       <anniversary>
                           <date-time>20090808T1430-0500</date-time>
                       </anniversary>
                       <gender><sex>M</sex></gender>
                       <lang>
                           <parameters><pref><integer>1</integer></pref>
                           </parameters>
                           <language-tag>de</language-tag>
                       </lang>
                       <lang>
                           <parameters><pref><integer>2</integer></pref>
                           </parameters>
                           <language-tag>en</language-tag>
                       </lang>
                       <org>
                           <parameters><type><text>work</text></type>
                           </parameters>
                           <text>Example VoIP Provider</text>
                       </org>
                       <adr>
                           <parameters>
                               <type><text>work</text></type>
                               <label><text>Hannes Tschofenig
                                   Linnoitustie 6
                                   Espoo , Finland
                                   02600</text></label>
                           </parameters>
                           <pobox/>
                           <ext/>
                           <street>Linnoitustie 6</street>
                           <locality>Espoo</locality>
                           <region>Uusimaa</region>
                           <code>02600</code>
                           <country>Finland</country>
                       </adr>
                       <tel>
                           <parameters>
                               <type>

Top      ToC       Page 17 
                                   <text>work</text>
                                   <text>voice</text>
                               </type>
                           </parameters>
                           <uri>tel:+358 50 4871445</uri>
                       </tel>
                       <tel>
                           <parameters>
                               <type>
                                   <text>work</text>
                                   <text>main-number</text>
                                   <text>voice</text>
                               </type>
                           </parameters>
                           <uri>tel:+358 50 5050505</uri>
                       </tel>
                       <email>
                           <parameters><type><text>work</text></type>
                           </parameters>
                           <text>hannes.tschofenig@nsn.com</text>
                       </email>
                       <geo>
                           <parameters><type><text>work</text></type>
                           </parameters>
                           <uri>geo:60.210796,24.812924</uri>
                       </geo>
                       <key>
                           <parameters><type><text>home</text></type>
                           </parameters>
                           <uri>
                             http://www.example.com/key.asc
                           </uri>
                       </key>
                       <tz><text>Finland/Helsinki</text></tz>
                       <url>
                           <parameters><type><text>home</text></type>
                           </parameters>
                           <uri>http://www.tschofenig.priv.at</uri>
                       </url>
                   </vcard>
       </ad:DataProviderContact>
   </ad:EmergencyCallData.ProviderInfo>

             Figure 3: EmergencyCallData.ProviderInfo Example

Top      ToC       Page 18 
4.2.  Service Information

   This block describes the service that the service provider provides
   to the caller.  It SHOULD be included by all service providers in the
   path of the call.  The MIME media type is 'application/
   EmergencyCallData.ServiceInfo+xml'.

4.2.1.  Service Environment

   Data Element:  Service Environment

   Use:  Conditional.  Required unless the 'ServiceType' value is
      'wireless'.

   XML Element:  <ServiceEnvironment>

   Description:  This element indicates whether a call is from a
      business or residence.  Currently, the only valid entries are
      'Business', 'Residence', and 'Unknown', as shown in Figure 4.  New
      values can be defined via the registry created in Section 11.1.2.

   Reason for Need:  To provide context and a hint when determining
      equipment and manpower requirements.

   How Used by Call Taker:  Information can be used to provide context
      and a hint to assist in determining equipment and manpower
      requirements for emergency responders.  This is non-authoritative;
      there are situations where the service provider does not know the
      type of service (e.g., anonymous prepaid service).  The type of
      service does not necessarily reflect the nature of the premises
      (e.g., a business line installed in a residence or cellular
      service).  The registry does not contain all possible values for
      all situations.  Hence, this is at best advisory information, but
      since it mimics a similar capability in some current emergency
      calling systems (e.g., a field in the Automatic Location
      Information (ALI) used with legacy North American wireline
      systems), it is known to be valuable to PSAPs.  The service
      provider uses its best information (such as a rate plan,
      facilities used to deliver service, or a service description) to
      determine the information and is not responsible for determining
      the actual characteristics of the location from which the call
      originated.  Because the usefulness is unknown (and less clear)
      for cellular, this element is OPTIONAL for commercial mobile radio
      services (e.g., cellular) and REQUIRED otherwise.

Top      ToC       Page 19 
                  +-----------+--------------------------+
                  | Token     | Description              |
                  +-----------+--------------------------+
                  | Business  | Business service         |
                  |           |                          |
                  | Residence | Residential service      |
                  |           |                          |
                  | Unknown   | Type of service unknown  |
                  |           |    (e.g., anonymous pre- |
                  |           |    paid service)         |
                  +-----------+--------------------------+

                  Figure 4: Service Environment Registry

4.2.2.  Service Type

   Data Element:  Service Delivered by Provider to End User

   Use:  Required

   XML Element:  <ServiceType>

   Description:  This defines the type of service over which the call is
      placed (similar to the Class of Service delivered with legacy
      emergency calls in some regions).  The implied mobility of this
      service cannot be relied upon.  A registry is created in
      Section 11.1.3.  The initial set of values is shown in Figure 5.
      More than one value MAY be returned.  For example, a VoIP inmate
      telephone service is a reasonable combination.

   Reason for Need:  Knowing the type of service can assist the PSAP in
      the handling of the call.

   How Used by Call Taker:  Call takers often use this information to
      determine what kinds of questions to ask callers and how much to
      rely on supportive information.  As the information is not always
      available, and the registry is not all encompassing, this is at
      best advisory information, but since it mimics a similar
      capability in some legacy emergency calling systems, it is known
      to be valuable.

      +--------------+------------------------------------------+
      | Name         | Description                              |
      +--------------+------------------------------------------+
      | wireless     | Wireless Telephone Service: Includes     |
      |              |   CDMA, GSM, Wi-Fi, WiMAX, and LTE       |
      |              |   (but not satellite)                    |
      |              |                                          |

Top      ToC       Page 20 
      | coin         | Fixed public pay/coin telephones: Any    |
      |              |   device operated by coin or credit card |
      |              |                                          |
      | one-way      | One-way outbound service                 |
      |              |                                          |
      | temp         | Soft dial tone/quick service/warm        |
      |              |   disconnect/suspended                   |
      |              |                                          |
      | MLTS-hosted  | Hosted multi-line telephone system       |
      |              |   such as Centrex                        |
      |              |                                          |
      | MLTS-local   | Local multi-line telephone system,       |
      |              |   including all PBXs, key systems, and   |
      |              |   Shared Tenant Services                 |
      |              |                                          |
      | sensor-      | These are devices that generate DATA     |
      |   unattended |   ONLY.  This is a one-way information   |
      |              |   transmit without interactive media.    |
      |              |                                          |
      | sensor-      | Devices that are supported by a          |
      |   attended   |   monitoring service provider or that    |
      |              |   are capable of supporting interactive  |
      |              |   media                                  |
      |              |                                          |
      | POTS         | Wireline: Plain Old Telephone Service    |
      |              |                                          |
      | OTT          | An over-the-top service that provides    |
      |              |   communication over arbitrary Internet  |
      |              |   access (fixed, nomadic, mobile)        |
      |              |                                          |
      | digital      | Wireline non-OTT digital phone service   |
      |              |                                          |
      | OPX          | Off-premise extension                    |
      |              |                                          |
      | relay        | A service where a human third-party      |
      |              |   agent provides additional assistance.  |
      |              |   This includes sign language relay/     |
      |              |   interpretation, telematics services    |
      |              |   that provide a human on the call,      |
      |              |   and similar services.                  |
      +--------------+------------------------------------------+

       Figure 5: Service Delivered by Provider to End User Registry

   The initial set of values has been collected from sources of
   currently used systems, including [NENA-02-010], [nc911], [NANP], and
   [LERG].

Top      ToC       Page 21 
4.2.3.  Service Mobility Environment

   Data Element:  Service Mobility Environment

   Use:  Required

   XML Element:  <ServiceMobility>

   Description:  This provides the service provider's view of the
      mobility of the caller's device.  As the service provider might
      not know the characteristics of the actual device or access
      network used, the value should be treated as advisory and not be
      relied upon.  A registry is created in Section 11.1.4 with the
      initial valid entries shown in Figure 6.

   Reason for Need:  Knowing the service provider's belief of mobility
      can assist the PSAP with the handling of the call.

   How Used by Call Taker:  To determine whether to assume the location
      of the caller might change.

                  +-----------+----------------------------+
                  | Token     | Description                |
                  +-----------+----------------------------+
                  | Mobile    | The device is able to move |
                  |           |   at any time              |
                  |           |                            |
                  | Fixed     | The device is not expected |
                  |           |   to move unless the       |
                  |           |   service is relocated     |
                  |           |                            |
                  | Nomadic   | The device is not expected |
                  |           |   to change its point of   |
                  |           |   attachment while on a    |
                  |           |   call                     |
                  |           |                            |
                  | Unknown   | No information is known    |
                  |           |   about the service        |
                  |           |   mobility environment for |
                  |           |   the device               |
                  +-----------+----------------------------+

                    Figure 6: Service Mobility Registry

Top      ToC       Page 22 
4.2.4.  EmergencyCallData.ServiceInfo Example

   <?xml version="1.0" encoding="UTF-8"?>
   <svc:EmergencyCallData.ServiceInfo
       xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo">
       <svc:DataProviderReference>2468.IBOC.MLTS.1359@example.org
       </svc:DataProviderReference>
       <svc:ServiceEnvironment>Business</svc:ServiceEnvironment>
       <svc:ServiceType>MLTS-hosted</svc:ServiceType>
       <svc:ServiceMobility>Fixed</svc:ServiceMobility>
   </svc:EmergencyCallData.ServiceInfo>

              Figure 7: EmergencyCallData.ServiceInfo Example



(page 22 continued on part 2)

Next Section