idnits 2.17.00 (12 Aug 2021) /tmp/idnits64400/draft-ietf-ecrit-car-crash-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 04, 2014) is 2877 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC4119' is defined on line 880, but no explicit reference was found in the text == Unused Reference: 'RFC6442' is defined on line 900, but no explicit reference was found in the text == Unused Reference: 'RFC4481' is defined on line 929, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) == Outdated reference: draft-ietf-ecrit-trustworthy-location has been published as RFC 7378 Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Qualcomm Technologies, Inc 4 Intended status: Informational B. Rosen 5 Expires: January 5, 2015 NeuStar, Inc. 6 H. Tschofenig 7 (no affiliation) 8 July 04, 2014 10 Internet Protocol-based In-Vehicle Emergency Calls 11 draft-ietf-ecrit-car-crash-00.txt 13 Abstract 15 This document describes how to use IP-based emergency services 16 mechanisms to support the next generation of emergency calls placed 17 by vehicles (automatically in the event of a crash or serious 18 incident, or manually invoked by a vehicle occupant) and conveying 19 vehicle, sensor, and location data related to the crash or incident. 20 Such calls are often referred to as "Automatic Crash Notification" 21 (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the 22 case of manual trigger. The "Advanced" qualifier refers to the 23 ability to carry a richer set of data. 25 This document also registers a MIME Content Type and an Emergency 26 Call Additional Data Block for the vehicle, sensor, and location data 27 (often referred to as "crash data" even though there is not 28 necessarily a crash). 30 Profiling and simplifications are possible due to the nature of the 31 functionality that is provided in vehicles with the usage of Global 32 Satellite Navigation System (GNSS). 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on January 5, 2015. 50 Copyright Notice 52 Copyright (c) 2014 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3. Overview of Current Deployment Models . . . . . . . . . . . . 7 70 4. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 71 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 72 6. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 73 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 11 74 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 14 75 9. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 14 76 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 77 11. Security Considerations . . . . . . . . . . . . . . . . . . . 17 78 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 79 12.1. Service URN Registration . . . . . . . . . . . . . . . . 17 80 12.2. MIME Content-type Registration for 81 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 17 82 12.3. Registration of the 'VEDS' entry in the Emergency Call 83 Additional Data registry . . . . . . . . . . . . . . . . 19 84 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 85 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 86 15. Changes from Previous Versions . . . . . . . . . . . . . . . 19 87 15.1. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 19 88 15.2. Changes from draft-gellens-01 to -02 . . . . . . . . . . 19 89 15.3. Changes from draft-gellens-00 to -01 . . . . . . . . . . 19 90 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 91 16.1. Normative References . . . . . . . . . . . . . . . . . . 20 92 16.2. Informative references . . . . . . . . . . . . . . . . . 21 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 95 1. Terminology 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119]. 101 This document re-uses terminology defined in Section 3 of [RFC5012]. 103 Additionally, we use the following abbreviations: 105 3GPP: 3rd Generation Partnership Project 107 AACN: Advanced Automatic Crash Notification 109 ACN: Automatic Crash Notification 111 APCO: Association of Public-Safety Communications Officials 113 EENA: European Emergency Number Association 115 ESInet: Emergency Services IP network 117 GNSS: Global Satellite Navigation System (which includes the various 118 such systems including the Global Positioning System or GPS) 120 IVS: In-Vehicle System 122 MNO: Mobile Network Operator 124 NENA: National Emergency Number Association 126 TSP: Telematics Service Provider 128 VEDS: Vehicle Emergency Data Set 130 2. Introduction 132 Emergency calls made by in-vehicle systems (e.g., in the event of a 133 crash) assist in significantly reducing road deaths and injuries by 134 allowing emergency services to respond quickly and often with better 135 location. 137 Drivers often have a poor location awareness, especially outside of 138 major cities, at night and when away from home (especially abroad). 139 In the most crucial cases, the victim(s) may not be able to call 140 because they have been injured or trapped. 142 For more than a decade, some vehicles have been equipped with 143 telematics systems that, among other features, place an emergency 144 call automatically in the event of a crash or manually in response to 145 an emergency call button. Such systems generally have on-board 146 location determination systems that make use of satellite-based 147 positioning technology, inertial sensors, gyroscopes, etc., to 148 provide a fairly accurate position for the vehicle. Such built-in 149 systems can take advantage of the benefits of being integrated into a 150 vehicle, such as more reliable power, ability to have larger or 151 specialized antenna, ability to be engineered to avoid or minimise 152 degradation by vehicle glass coatings, interference from other 153 vehicle systems, etc. Thus, the PSAP can be provided with a good 154 estimate of where the vehicle is during an emergency. Vehicle 155 manufacturers are increasingly adopting such systems, both for the 156 safety benefits and for the additional features and services they 157 enable (e.g., remote engine diagnostics, remote door unlock, stolen 158 vehicle tracking and disabling, etc.). 160 The general term for such systems is Automatic Crash Notification 161 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 162 used in this document as a general term. ACN systems transmit some 163 amount of data specific to the incident, referred to generally as 164 "crash data" (the term is commonly used even though there might not 165 have been a crash). While different systems transmit different 166 amounts of crash data, standardized formats, structures, and 167 mechanisms are needed to provide interoperability among systems and 168 PSAPs. 170 Currently deployed in-vehicle telematics systems are circuit-switched 171 and lack a standards-based ability to convey crash data directly to 172 the PSAP (generally relying on either a human call taker or an 173 automated system to provide the PSAP call taker with some crash data 174 orally, or possibly a proprietary mechanism). The PSAP call taker 175 needs to first realize that the call is related to a vehicle 176 incident, and in most cases must then listen to the data and 177 transcribe it. 179 The transition to next-generation calling in general, and emergency 180 calling in particular, provides an opportunity to vastly improve the 181 scope, breadth, reliability and usefulness of crash data during an 182 emergency by allowing it to be presented alongside the call, and to 183 be automatically processed by the PSAP and made available to the call 184 taker in an integrated, automated way. In addition, vehicle 185 manufacturers are provided an opportunity to take advantage of the 186 same standardized mechanisms for data transmission for internal use 187 if they wish (such as telemetry between the vehicle and a service 188 center for both emergency and non-emergency uses, including location- 189 based services, multi-media entertainment systems, and road-side 190 assistance applications). 192 Next-generation ACN provides an opportunity for such calls to be 193 recognized and processed as such during call set-up, and routed to a 194 specialized PSAP where the vehicle data is available to assist the 195 call taker in assessing and responding to the situation. 197 An ACN call may be either occupant-initiated or automatically 198 triggered. (The "A" in "ACN" does stand for "Automatic," but the 199 term is often used to refer to the class of calls that are placed by 200 an in-vehicle system (IVS) and that carry incident-related data as 201 well as voice.) Automatically triggered calls indicate a car crash 202 or some other serious incident (e.g., a fire) and carry a greater 203 presumption of risk of injury. Manually triggered calls are often 204 reports of serious hazards (such as drunk drivers) and may require 205 different responses depending on the situation. Manually triggered 206 calls are also more likely to be false (e.g., accidental) calls and 207 may thus be subject to different handling by the PSAP. 209 This document describes how the IETF mechanisms for IP-based 210 emergency calls, including [RFC6443] and [additional-data-draft], are 211 used to provide the realization of next-generation ACN. 213 The Association of Public-Safety Communications Officials (APCO) and 214 the National Emergency Number Association (NENA) have jointly 215 developed a standardized set of incident-related vehicle data for ACN 216 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 217 is often referred to as crash data although it is applicable in 218 incidents other than crashes. 220 VEDS provides a standard data set for the transmission, exchange, and 221 interpretation of vehicle-related data. A standard data format 222 allows the data to be generated by an IVS, and interpreted by PSAPs, 223 emergency responders, and medical facilities (including those capable 224 of providing trauma level patient care). It includes incident- 225 related information such as airbag deployment, location of the 226 vehicle, if the vehicle was involved in a rollover, various sensor 227 data that can indicate the potential severity of the crash and the 228 likelihood of severe injuries to the vehicle occupants, etc. This 229 data better informs the PSAP and emergency responders as to the type 230 of response that may be needed. This information was recently 231 included in the federal guidelines for field triage of injured 232 patients. These guidelines are designed to help responders at the 233 accident scene identify the potential existence of severe internal 234 injuries and to make critical decisions about how and where a patient 235 needs to be transported. 237 This document registers the 'application/EmergencyCallData.VEDS+xml' 238 MIME content-type, and registers the 'VEDS' entry in the Emergency 239 Call Additional Data registry. 241 VEDS is an XML structure (see [VEDS]). The 'application/ 242 EmergencyCallData.VEDS+xml' MIME content-type is used to identify it. 243 The 'VEDS' entry in the Emergency Call Additional Data registry is 244 used to construct a 'purpose' parameter value for conveying VEDS data 245 in a Call-Info header (as described in [additional-data-draft]). 247 VEDS is a versatile structure that can accomodate varied needs. 248 However, if additional sets of data are determined to be needed, the 249 steps to enable each data block are very briefly summarized below: 251 o A standardized format and encoding (such as XML) is defined and 252 published by a Standards Development Organization (SDO). 253 o A MIME Content-Type is registered for it (typically under the 254 'Application' media type and with a sub-type starting with 255 'EmergencyCallData.'). 256 o An entry for the block is added to the Emergency Call Additional 257 Data Blocks sub-registry (established by [additional-data-draft]); 258 the registry entry is the root of the MIME sub-type (not including 259 the 'EmergencyCallData' prefix and any suffix such as '+xml'). 261 A next-generation In-Vehicle System (IVS) transmits crash data by 262 encoding it in a standardized and registered format (such as VEDS) 263 and attaching it to an INVITE as a MIME body part. The body part is 264 identified by its MIME content-type (such as 'application/ 265 EmergencyCallData.VEDS+xml') in the Content-Type header field of the 266 body part. The body part is assigned a unique identifier which is 267 listed in a Content-ID header field in the body part. The INVITE is 268 marked as containing the crash data by adding (or appending to) a 269 Call-Info header field at the top level of the INVITE. The Call-Info 270 header field contains a CID URL referencing the body part's unique 271 identifier, and a 'purpose' parameter identifying the data as the 272 crash data per the registry entry; the 'purpose' parameter's value is 273 'EmergencyCallData.' and the root of the MIME type (not including the 274 'EmergencyCallData' prefix and any suffix such as '+xml' (e.g., 275 'purpose=EmergencyCallData.VEDS'). 277 The mechanisms described here can be used place emergency calls that 278 are identifiable as ACN calls and that carry one or more standardized 279 crash data objects in an interoperable way. 281 Note that while ACN systems in the U.S. and other regions are not 282 currently mandated, Europe has a mandated and standardized system for 283 emergency calls by in-vehicle systems. This pan-European system is 284 known as "eCall" and is not further discussed in this document but is 285 the subject of a separate document, [eCall-draft] 287 3. Overview of Current Deployment Models 289 Current (circuit-switched or legacy) systems for placing emergency 290 calls by in-vehicle systems, including automatic crash notification 291 systems, generally have a limited ability to convey at least location 292 and in some cases telematics data to the PSAP. Most such systems use 293 one of three architectural models, which are described here as: 294 "Telematics Service Provider" (TSP), "direct", and "paired handset". 295 These three models are illustrated below. 297 In the TSP model, both emergency and non-emergency calls are placed 298 to a Telematics Service Provider (TSP); a proprietary technique is 299 used for data transfer (such as proprietary in-band modems) to the 300 TSP. 302 In an emergency, the TSP call taker bridges in the PSAP and 303 communicates location, crash data (such as impact severity and trauma 304 prediction), and other data (such as the vehicle description) to the 305 PSAP call taker verbally. Typically, a three-way voice call is 306 established between the vehicle, the TSP, and the PSAP, allowing 307 communication between the PSAP call taker, the TSP call taker, and 308 the vehicle occupants (who might be unconscious). 310 ///----\\\ proprietary +------+ 911 trunk +------+ 311 ||| IVS |||-------------->+ TSP +------------------>+ PSAP | 312 \\\----/// crash data +------+ +------+ 314 Figure 1: Legacy TSP Model. 316 In the paired model, the IVS uses a Bluetooth link with a previously- 317 paired handset to establish an emergency call with the PSAP (by 318 dialing a standard emergency number such as 9-1-1), and then 319 communicates location data to the PSAP via text-to-speech; crash data 320 is not conveyed. Some such systems use an automated voice prompt 321 menu (e.g., "this is an automatic emergency call from a vehicle; 322 press 1 to open a voice path to the vehicle; press 2 to hear the 323 location read out") to allow the call taker to request location data 324 via text-to-speech. 326 +---+ 327 ///----\\\ | H | 911/etc voice call via handset +------+ 328 ||| IVS |||-->| S +----------------------------------->+ PSAP | 329 \\\----/// +---+ location via text-to-speech +------+ 331 Figure 2: Legacy Paired Model 333 In the direct model, the IVS directly places an emergency call with 334 the PSAP by dialing a standard emergency number such as 9-1-1. Such 335 systems might communicate location data to the PSAP via text-to- 336 speech; crash data might not be conveyed. 338 ///----\\\ 911/etc voice call via IVS +------+ 339 ||| IVS |||---------------------------------------->+ PSAP | 340 \\\----/// location via text-to-speech +------+ 342 Figure 3: Legacy Direct Model 344 4. Document Scope 345 This document is focused on the interface to the PSAP, that is, how 346 an ACN emergency call is setup and incident-related data (including 347 vehicle, sensor, and location data) is transmitted to the PSAP using 348 IETF specifications. (The goal is to re-use specifications rather 349 than to invent new.) For the direct model, this is the end-to-end 350 description (between the vehicle and the PSAP). For the TSP model, 351 this describes the right-hand side (between the TSP and the PSAP), 352 leaving the left-hand side (between the vehicle and the TSP) up to 353 the entities involved (i.e., IVS and TSP vendors) who are then free 354 to use the same mechanism as for the right-hand side (or not). 356 This document does not address pan-European eCall (a mandated and 357 standardized system for emergency calls by in-vehicle systems within 358 Europe and other regions), which is the subject of a separate 359 document, [eCall-draft] 361 5. Migration to Next-Generation 363 Migration of emergency calls placed by in-vehicle systems to next- 364 generation (all-IP) technology provides a standardized mechanism to 365 identify such calls and to present crash data with the call. This 366 allows ACN calls and crash data to be automatically processed by the 367 PSAP and made available to the call taker in an integrated, automated 368 way. 370 Vehicle manufacturers using the TSP model may choose to take 371 advantage of the same mechanism to carry telematics data between the 372 vehicle and the TSP for both emergency and non-emergency calls. 374 A next-generation IVS establishes an emergency call using the 3GPP 375 IMS solution with a Request-URI indicating an ACN type of emergency 376 call with vehicle data attached; the MNO only needs to recognize the 377 call as an emergency call and route it to an ESInet; the ESInet 378 recognizes the call as an ACN with vehicle data and routes the call 379 to an NG-ACN capable PSAP; the PSAP interpets the vehicle data sent 380 with the call and makes it available to the call taker. 382 Because of the need to identify and specially process Next-Generation 383 ACN calls (as discussed above), this document registers new service 384 URN children within the "sos" subservice. These URNs provide the 385 mechanism by which an NG-ACN call is identified, and differentiate 386 between manually and automatically triggered NG-ACN calls (which may 387 be subject to different treatment, depending on policy). The two 388 service URNs are: 'urn:service:sos.vehicle.automatic' and 389 'urn:service:sos.vehicle.manual'. 391 Migration of the three architectural models to next-generation (all- 392 IP) is described below. 394 In the TSP model, the IVS transmits crash and location data to the 395 TSP using either a protocol that is based on a proprietary design or 396 one that re-uses IETF specifications. In an emergency, the TSP call 397 taker bridges in the PSAP and the TSP transmits crash and other data 398 to the PSAP using IETF specifications. There is a three-way call 399 between the vehicle, the TSP, and the PSAP, allowing communication 400 between the PSAP call taker, the TSP call taker, and the vehicle 401 occupants (who might be unconscious). 403 proprietary 404 ///----\\\ or standard +------+ standard +------+ 405 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 406 \\\----/// crash + other data +------+ crash + other data +------+ 408 Figure 4: Next-Generation TSP Model 410 The vehicle manufacturer and the TSP may choose to use the same IETF 411 specifications to transmit crash and location data from the vehicle 412 to the TSP as is described here to transmit such data from the TSP to 413 the PSAP. 415 In the paired model, the IVS uses a Bluetooth link to a previously- 416 paired handset to establish an emergency call with the PSAP; it is 417 not clear what facilities are or will be available for transmitting 418 crash data through the Bluetooth link. 420 +---+ 421 ///----\\\ (unclear) | H | (unclear) +------+ 422 ||| IVS |||------------------>| S +------------------->+ PSAP | 423 \\\----/// (unclear) +---+ (unclear) +------+ 425 Figure 5: Next-Generation Paired Model 427 In the direct model, the IVS communicates crash data to the PSAP 428 directly using IETF specifications. 430 ///----\\\ NG1-1-2/NG9-1-1 call +------+ 431 ||| IVS |||----------------------------------------->+ PSAP | 432 \\\----/// crash data +------+ 434 Figure 6: Next-Generation Model 436 6. Profile 438 In the context of emergncy calls placed by an in-vehicle system it is 439 assumed that the car is equipped with a built-in GNSS receiver. For 440 this reason only geodetic location information will be sent within an 441 emergency call. The following location shapes MUST be implemented: 443 2d and 3d Point (see Section 5.2.1 of [RFC5491]), Circle (see 444 Section 5.2.3 of [RFC5491]), and Ellipsoid (see Section 5.2.7 of 445 [RFC5491]). The coordinate reference systems (CRS) specified in 446 [RFC5491] are also mandatory for this document. The 447 element, as defined in [RFC5962] which indicates the direction of 448 travel of the vehicle, is important for dispatch and hence it MUST be 449 included in the PIDF-LO . The element specified in 450 [RFC5962] MUST be implemented and MAY be included. 452 Calls by in-vehicle systems are placed via cellular networks, which 453 may ignore location sent by an originating device in an emergency 454 call INVITE, instead attaching their own location (often determined 455 in cooperation with the originating device). The IVS MAY attach 456 location data to the call INVITE. Standardized crash data structures 457 often include location as determined by the IVS. A benefit of this 458 is that it allows the PSAP to see both the location as determined by 459 the cellular network (often in cooperation with the originating 460 device) and the location as determined by the IVS. 462 This specification also inherits the ability to utilize test call 463 functionality from Section 15 of [RFC6881]. 465 7. Call Setup 467 It is important that ACN calls be easily identifiable as such at all 468 stages of call handling, and that automatic versis manual triggering 469 be known. ACN calls differ from general emergency calls in several 470 aspects, including the presence of standardized crash data, the fact 471 that the call is known to be placed by an in-vehicle system (which 472 has implications for PSAP operational processes), and, especially for 473 automatic calls, information that may indicate a likelihood of severe 474 injury and hence need for trauma services. Knowledge that a call is 475 an ACN and further that it was automatically or manually invoked 476 carries a range of implications about the call, the circumstances, 477 and the vehicle occupants. Calls by in-vehicle systems may be 478 considered a specific sub-class of general emergency calls and need 479 to be handled by a PSAP with the technical and operational 480 capabilities to serve such calls. (This is especially so in 481 environments such as the U.S. where there are many PSAPs and where 482 individual PSAPs have a range of capabilities.) Technical 483 capabilities include the ability to recognize and process 484 standardized crash data. Operational capabilities include training 485 and processes for assessing severe injury likelihood and responding 486 appropriately (e.g., dispatching trauma-capable medical responders, 487 transporting victims to a trauma center, alerting the receiving 488 facility, etc.). 490 Because ACN calls differ in significant ways from general emergency 491 calls, and because such calls need to be handled by specialized PSAPs 492 (equipped technically to interpet and make use of crash data, and 493 operationally to handle emergency calls placed by in-vehicle 494 systems), this document proposes an SOS sub-service for ACN/car 495 crash, specifically, "SOS.vehicle". Using a sub-service makes it 496 readily obvious that the call is an ACN; a further child elements is 497 proposed to distinguish calls automatically placed due to a crash or 498 other serious incident (such as a fire) from those manually invoked 499 by a vehicle occupant (specifically, "SOS.vehicle.automatic" and 500 "SOS.vehicle.manual"). The distinction between automatic and manual 501 invocation is also significant; automatically triggered calls 502 indicate a car crash or some other serious incident (e.g., a fire) 503 and carry a greater presumption of risk of injury and hence need for 504 specific responders (such as trauma or fire). Manually triggered 505 calls are often reports of serious hazards (such as drunk drivers) 506 and may require different responses depending on the situation. 507 Manually triggered calls are also more likely to be false (e.g., 508 accidental) calls and may thus be subject to different handling by 509 the PSAP. 511 A next-generation In-Vehicle System (IVS) transmits crash data by 512 encoding it in a standardized and registered format and attaching it 513 to an INVITE as an additional data block as specified in Section 4.1 514 of [additional-data-draft]. As described in that document, the block 515 is identified by its MIME content-type, and pointed to by a CID URL 516 in a Call-Info header with a 'purpose' parameter value corresponding 517 to the block. 519 Specifically, the steps required during standardization are: 521 o A set of crash data is standardized by an SDO or appropriate 522 organization 524 o A MIME Content-Type for the crash data set is registered with IANA 526 * If the data is specifically for use in emergency calling, the 527 MIME type is normally under the 'application' type with a 528 subtype starting with 'EmergencyCallData.' 530 * If the data format is XML, then by convention the name has a 531 suffix of '+xml' 533 o The item is registered in the Emergency Call Additional Data 534 registry, as defined in Section 9.1.7 of [additional-data-draft] 536 * For emergency-call-specific formats, the registered name is the 537 root of the MIME Content-Type (not including the 538 'EmergencyCallData' prefix and any suffix such as '+xml') as 539 described in Section 4.1 of [additional-data-draft] 541 When placing an emergency call: 543 o The crash data set is created and encoded per its specification 545 o The crash data set is attached to the emergency call INVITE as 546 specified in Section 4.1 of [additional-data-draft], that is, as a 547 MIME body part identified by its MIME Content-Type in the body 548 part's Content-Type header field 550 o The body part is assigned a unique identifier label in a Content- 551 ID header field of the body part 553 o A Call-Info header field at the top level of the INVITE references 554 the crash data and identifies it by its MIME root (as registered 555 in the Emergency Call Additional Data registry) 557 * The crash data is referenced in the Call-Info header field by a 558 CID URL that contains the unique Content ID assigned to the 559 crash data body part 561 * The crash data is identified in the Call-Info header field by a 562 'purpose' parameter whose value is 'EmergencyCallData.' 563 concatenated with the specific crash data entry in the 564 Emergency Call Additional Data registry 566 * The Call-Info header field MAY be either solely to reference 567 the crash data (and hence have only the one URL) or may also 568 contain other URLs referencing other data 570 o Additional crash data sets MAY be included by following the same 571 steps 573 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 574 the Association of Public-Safety Communications Officials (APCO) and 575 the National Emergency Number Association (NENA) [VEDS]. The 576 'application/EmergencyCallData.VEDS+xml' MIME content-type is used to 577 identify it. The 'VEDS' entry in the Emergency Call Additional Data 578 registry is used to construct a 'purpose' parameter value for 579 conveying VEDS data in a Call-Info header. 581 The VEDS data is attached as a body part with MIME content type 582 'application/EmergencyCallData.VEDS+xml' which is pointed at by a 583 Call-Info URL of type CID with a 'purpose' parameter of 584 'EmergencyCallData.VEDS'. 586 Entities along the path between the vehicle and the PSAP are able to 587 identify the call as an ACN call and handle it appropriately. The 588 PSAP is able to identify the crash data as well as any other 589 additional data attached to the INVITE by examining the Call-Info 590 header fields for 'purpose' parameters whose values start with 591 'EmergencyCallData.' The PSAP is able to access and the data it is 592 capable of handling and is interested in by checking the 'purpose' 593 parameter values. 595 8. Call Routing 597 An Emergency Services IP Network (ESInet) is a network operated by 598 emergency services authorities. It handles emergency call routing 599 and processing before delivery to a PSAP. In the NG9-1-1 600 architecture adopted by NENA as well as the NG1-1-2 architecture 601 adopted by EENA, each PSAP is connected to one or more ESInets. Each 602 originating network is also connected to one or more ESInets. The 603 ESInets maintain policy-based routing rules which control the routing 604 and processing of emergency calls. The centralization of such rules 605 within ESInets provides for a cleaner separation between the 606 responsibilities of the originating network and that of the emergency 607 services network, and provides greater flexibility and control over 608 processing of emergency calls by the emergency services authorities. 609 This makes it easier to react quickly to unusual situations that 610 require changes in how emergency calls are routed or handled (e.g., a 611 natural disaster closes a PSAP), as well as ease in making long-term 612 changes that affect such routing (e.g., cooperative agreements to 613 specially handle calls requiring translation or relay services). 615 In an environment that uses ESInets, the originating network need 616 only detect that the service URN of an emergency call is or starts 617 with "sos", passing all types of emergency calls to an ESInet. The 618 ESInet is then responsible for routing such calls to an appropriate 619 PSAP. In an environment without an ESInet, the emergency services 620 authorities and the originating carriers would need to determine how 621 such calls are routed. 623 9. Test Calls 625 This specification also inherits the ability to utilize test call 626 functionality from Section 15 of [RFC6881]. 628 A service URN starting with "test." indicates a request for an 629 automated test. For example, 630 "urn:service:test.sos.vehicle.automatic" indicates such a test 631 feature. This functionality is defined in [RFC6881]. 633 10. Example 635 Figure 7 shows an emergency call placed by a vehicle whereby location 636 information and VEDS crash data are both attached to the SIP INVITE 637 message. The INVITE has a request URI containing the 638 'urn:service:sos.vehicle.automatic' service URN and is thus 639 recognized as an ACN type of emergency call, and is also recognized 640 as a type of emergency call because the request URI starts with 641 'urn:service:sos'. The mobile network operator (MNO) routes the call 642 to an Emergency services IP Network (ESInet), as for any emergency 643 call. The ESInet processes the call as an ACN and routes the call to 644 an appropriate ACN-capable PSAP (using location information and the 645 fact that that it is an ACN). (In deployments where there is no 646 ESInet, the MNO itself needs to route directly to an appropriate ACN- 647 capable PSAP.) The call is processed by the Emergency Services 648 Routing Proxy (ESRP), as the entry point to the ESInet. The ESRP 649 routes the call to an appropriate ACN-capable PSAP, where the call is 650 received by a call taker. 652 +-----------------------------------------+ 653 | | 654 +------------+ | +-------+ | 655 | | | | PSAP2 | | 656 | | | +-------+ | 657 | Originating| | | 658 | Mobile | | +------+ +-------+ | 659 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |---> Call-Taker | 660 | | | +------+ +-------+ | 661 | | | | 662 +------------+ | +-------+ | 663 | | PSAP3 | | 664 | +-------+ | 665 | | 666 | | 667 | | 668 | ESInet | 669 +-----------------------------------------+ 671 Figure 7: Example of Vehicle-Placed Emergency Call Message Flow 673 The example, shown in Figure 8, illustrates a SIP emergency call 674 eCall INVITE that is being conveyed with location information (a 675 PIDF-LO) and crash data (as VEDS data). 677 INVITE urn:service:sos.vehicle.automatic SIP/2.0 678 To: urn:service:sos.ecall.automatic 679 From: ;tag=9fxced76sl 680 Call-ID: 3848276298220188511@atlanta.example.com 681 Geolocation: 682 Geolocation-Routing: no 683 Call-Info: cid:1234567890@atlanta.example.com; 684 purpose=EmergencyCallData.VEDS 685 Accept: application/sdp, application/pidf+xml 686 CSeq: 31862 INVITE 687 Content-Type: multipart/mixed; boundary=boundary1 688 Content-Length: ... 690 --boundary1 692 Content-Type: application/sdp 694 ...Session Description Protocol (SDP) goes here 696 --boundary1 698 Content-Type: application/pidf+xml 699 Content-ID: 700 701 709 710 711 712 713 -34.407 150.883 714 715 716 278 717 718 719 720 721 gps 722 723 2012-04-5T10:18:29Z 724 1M8GDM9A_KP042788 725 726 728 --boundary1 730 Content-Type: application/EmergencyCallData.VEDS+xml 731 Content-ID: 1234567890@atlanta.example.com 733 ...eCall VEDS data object goes here 735 --boundary1-- 737 Figure 8: SIP INVITE indicating an In-Vehicular Emergency Call 739 11. Security Considerations 741 This document does not raise security considerations beyond those 742 described in [RFC5069]. As with emergency service systems with end 743 host provided location information there is the possibility that that 744 location is incorrect, either intentially (in case of an a denial of 745 service attack against the emergency services infrastructure) or due 746 to a malfunctioning devices. The reader is referred to 747 [I-D.ietf-ecrit-trustworthy-location] for a discussion of some of 748 these vulnerabilities. 750 12. IANA Considerations 752 12.1. Service URN Registration 754 IANA is requested to register the URN 'urn:service:sos.vehicle' under 755 the sub-services 'sos' registry defined in Section 4.2 of [RFC5031]. 757 This service identifier reaches a public safety answering point 758 (PSAP), which in turn dispatches aid appropriate to the emergency 759 related to accidents of vehicles. The following two sub-services are 760 registered as well: 762 urn:service:sos.vehicle.manual 764 This service URN indicates that an emergency call carrying vehicle 765 sensor ("crash") data has been placed by an in-vehicle system 766 (IVS) based on the manual interaction of the driver or a 767 passenger. 769 urn:service:sos.vehicle.automatic 771 This service URN indicates that an emergency call carrying vehicle 772 sensor ("crash") data has been placed by an in-vehicle system 773 (IVS) triggered automatically, for example, due to a crash. 775 12.2. MIME Content-type Registration for 'application/ 776 EmergencyCall.VEDS+xml' 778 This specification requests the registration of a new MIME type 779 according to the procedures of RFC 4288 [RFC4288] and guidelines in 780 RFC 3023 [RFC3023]. 782 MIME media type name: application 784 MIME subtype name: EmergencyCallData.VEDS+xml 786 Mandatory parameters: none 788 Optional parameters: charset 790 Indicates the character encoding of enclosed XML. 792 Encoding considerations: Uses XML, which can employ 8-bit 793 characters, depending on the character encoding used. See 794 Section 3.2 of RFC 3023 [RFC3023]. 796 Security considerations: This content type is designed to carry 797 vehicle crash data during an emergency call. This data may 798 contains personal information including vehicle VIN, location, 799 direction, etc. appropriate precautions need to be taken to limit 800 unauthorized access, inappropriate disclosure to third parties, 801 and eavesdropping of this information. Please refer to Section 7 802 and Section 8 of [additional-data-draft] for more information. 804 Interoperability considerations: None 806 Published specification: [VEDS] 808 Applications which use this media type: Emergency Services 810 Additional information: None 812 Magic Number: None 814 File Extension: .xml 816 Macintosh file type code: 'TEXT' 818 Person and email address for further information: Hannes 819 Tschofenig, Hannes.Tschofenig@gmx.net 821 Intended usage: LIMITED USE 823 Author: This specification is a work item of the IETF ECRIT 824 working group, with mailing list address . 826 Change controller: The IESG 828 12.3. Registration of the 'VEDS' entry in the Emergency Call Additional 829 Data registry 831 This specification requests IANA to add the 'VEDS' entry to the 832 Emergency Call Additional Data registry, with a reference to this 833 document. The Emergency Call Additional Data registry has been 834 established by [additional-data-draft]. 836 13. Contributors 838 We would like to thank Ulrich Dietz for his help with earlier 839 versions of the original version of this document. 841 14. Acknowledgements 843 We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, 844 and Gunnar Hellstrom for their feedback. 846 15. Changes from Previous Versions 848 15.1. Changes from draft-gellens-02 to draft-ietf-00 850 o Renamed from draft-gellens- to draft-ietf- 852 o Added text to Introduction to clarify that during a CS ACN, the 853 PSAP call taker usually needs to listen to the data and transcribe 854 it 856 15.2. Changes from draft-gellens-01 to -02 858 o Fixed case of 'EmergencyCallData', in accordance with changes to 859 [additional-data-draft] 861 15.3. Changes from draft-gellens-00 to -01 863 o Now using 'EmergencyCallData' for purpose parameter values and 864 MIME subtypes, in accordance with changes to 865 [additional-data-draft] 867 o Added reference to RFC 6443 869 o Fixed bug that caused Figure captions to not appear 871 16. References 872 16.1. Normative References 874 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 875 Requirement Levels", BCP 14, RFC 2119, March 1997. 877 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 878 Types", RFC 3023, January 2001. 880 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 881 Format", RFC 4119, December 2005. 883 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 884 Registration Procedures", RFC 4288, December 2005. 886 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 887 Emergency and Other Well-Known Services", RFC 5031, 888 January 2008. 890 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 891 Presence Information Data Format Location Object (PIDF-LO) 892 Usage Clarification, Considerations, and Recommendations", 893 RFC 5491, March 2009. 895 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 896 Thomson, "Dynamic Extensions to the Presence Information 897 Data Format Location Object (PIDF-LO)", RFC 5962, 898 September 2010. 900 [RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance 901 for the Session Initiation Protocol", RFC 6442, December 902 2011. 904 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 905 "Framework for Emergency Calling Using Internet 906 Multimedia", RFC 6443, December 2011. 908 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 909 Communications Services in Support of Emergency Calling", 910 BCP 181, RFC 6881, March 2013. 912 [VEDS] , "Vehicular Emergency Data Set (VEDS) version 3", July 913 2012, . 916 [additional-data-draft] 917 Rosen, B., Tschofenig, H., Marshall, R., Gellens, R., and 918 J. Winterbottom, "Additional Data related to an Emergency 919 Call", draft-ietf-ecrit-additional-data-11 (work in 920 progress), July 2013. 922 16.2. Informative references 924 [I-D.ietf-ecrit-trustworthy-location] 925 Tschofenig, H., Schulzrinne, H., and B. Aboba, 926 "Trustworthy Location", draft-ietf-ecrit-trustworthy- 927 location-07 (work in progress), July 2013. 929 [RFC4481] Schulzrinne, H., "Timed Presence Extensions to the 930 Presence Information Data Format (PIDF) to Indicate Status 931 Information for Past and Future Time Intervals", RFC 4481, 932 July 2006. 934 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 935 Emergency Context Resolution with Internet Technologies", 936 RFC 5012, January 2008. 938 [RFC5069] Taylor, T., Tschofenig, H., Schulzrinne, H., and M. 939 Shanmugam, "Security Threats and Requirements for 940 Emergency Call Marking and Mapping", RFC 5069, January 941 2008. 943 [eCall-draft] 944 Gellens, RG., "Next-Generation Pan-European eCall", 2013. 946 Authors' Addresses 948 Randall Gellens 949 Qualcomm Technologies, Inc 950 5775 Morehouse Drive 951 San Diego 92651 952 US 954 Email: rg+ietf@qti.qualcomm.com 956 Brian Rosen 957 NeuStar, Inc. 958 470 Conrad Dr 959 Mars, PA 16046 960 US 962 Email: br@brianrosen.net 963 Hannes Tschofenig 964 (no affiliation) 966 Email: Hannes.Tschofenig@gmx.net 967 URI: http://www.tschofenig.priv.at