< < PS03 : PS04 : PS05 > >

PS04: Mayday Notification

This service package provides the capability for a vehicle to automatically transmit an emergency message when the vehicle has been involved in a crash or other distress situation. An automatic crash notification feature transmits key data on the crash recorded by sensors mounted in the vehicle (e.g. deployment of airbags) without the need for involvement of the driver. The emergency message is sent to emergency response services, which determines and carries out the appropriate response. This service package allows passing vehicles to receive and forward mayday requests in areas where no communications infrastructure exists. Emergency notifications from personal devices are also supported.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Vehicle Maintainer Basic Vehicle Maintains
Basic Vehicle Manager Basic Vehicle Manages
Basic Vehicle Manager Driver System Usage Agreement
Basic Vehicle Owner Basic Vehicle Maintainer System Maintenance Agreement
Basic Vehicle Owner Basic Vehicle Manager Operations Agreement
Basic Vehicle Owner Driver Application Usage Agreement
Basic Vehicle Owner Driver Vehicle Operating Agreement
Basic Vehicle Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Basic Vehicle Owner Vehicle Owner Expectation of Data Provision
Basic Vehicle Owner Vehicle User Service Usage Agreement
Basic Vehicle Supplier Basic Vehicle Owner Warranty
Driver Basic Vehicle Operates
Driver Vehicle Operates
Emergency Management Center Maintainer Emergency Management Center Maintains
Emergency Management Center Manager Emergency Management Center Manages
Emergency Management Center Manager Emergency System Operator System Usage Agreement
Emergency Management Center Owner Driver Application Usage Agreement
Emergency Management Center Owner Emergency Management Center Maintainer System Maintenance Agreement
Emergency Management Center Owner Emergency Management Center Manager Operations Agreement
Emergency Management Center Owner Other Emergency Management Centers Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Other Emergency Management Centers Owner Information Exchange Agreement
Emergency Management Center Owner Other Emergency Management Centers User Service Usage Agreement
Emergency Management Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Personal Information Device Owner Information Provision Agreement
Emergency Management Center Owner Personal Information Device User Service Usage Agreement
Emergency Management Center Owner Traveler Application Usage Agreement
Emergency Management Center Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Vehicle Owner Information Provision Agreement
Emergency Management Center Owner Vehicle User Service Usage Agreement
Emergency Management Center Supplier Emergency Management Center Owner Warranty
Emergency System Operator Emergency Management Center Operates
Enforcement Center Maintainer Enforcement Center Maintains
Enforcement Center Manager Enforcement Center Manages
Enforcement Center Owner Enforcement Center Maintainer System Maintenance Agreement
Enforcement Center Owner Enforcement Center Manager Operations Agreement
Enforcement Center Supplier Enforcement Center Owner Warranty
Other Emergency Management Centers Maintainer Other Emergency Management Centers Maintains
Other Emergency Management Centers Manager Other Emergency Management Centers Manages
Other Emergency Management Centers Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Other Emergency Management Centers Owner Emergency Management Center Owner Information Exchange Agreement
Other Emergency Management Centers Owner Emergency Management Center User Service Usage Agreement
Other Emergency Management Centers Owner Emergency System Operator Application Usage Agreement
Other Emergency Management Centers Owner Other Emergency Management Centers Maintainer System Maintenance Agreement
Other Emergency Management Centers Owner Other Emergency Management Centers Manager Operations Agreement
Other Emergency Management Centers Supplier Other Emergency Management Centers Owner Warranty
Other PIDs Maintainer Other PIDs Maintains
Other PIDs Manager Other PIDs Manages
Other PIDs Owner Other PIDs Maintainer System Maintenance Agreement
Other PIDs Owner Other PIDs Manager Operations Agreement
Other PIDs Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Other PIDs Owner Personal Information Device Owner Information Provision and Action Agreement
Other PIDs Owner Personal Information Device User Service Usage Agreement
Other PIDs Owner Traveler Application Usage Agreement
Other PIDs Supplier Other PIDs Owner Warranty
Other Vehicles Maintainer Other Vehicles Maintains
Other Vehicles Manager Other Vehicles Manages
Other Vehicles Owner Driver Application Usage Agreement
Other Vehicles Owner Driver Vehicle Operating Agreement
Other Vehicles Owner Other Vehicles Maintainer System Maintenance Agreement
Other Vehicles Owner Other Vehicles Manager Operations Agreement
Other Vehicles Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Other Vehicles Owner Vehicle Owner Expectation of Data Provision
Other Vehicles Owner Vehicle User Service Usage Agreement
Other Vehicles Supplier Other Vehicles Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Manager Traveler System Usage Agreement
Personal Information Device Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Emergency Management Center Owner Information Provision and Action Agreement
Personal Information Device Owner Emergency Management Center User Service Usage Agreement
Personal Information Device Owner Emergency System Operator Application Usage Agreement
Personal Information Device Owner Other PIDs Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Other PIDs Owner Information Provision and Action Agreement
Personal Information Device Owner Other PIDs User Service Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Traveler Personal Information Device Operates
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Basic Vehicle Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Basic Vehicle Owner Expectation of Data Provision
Vehicle Owner Basic Vehicle User Service Usage Agreement
Vehicle Owner Driver Application Usage Agreement
Vehicle Owner Driver Vehicle Operating Agreement
Vehicle Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Emergency Management Center Owner Expectation of Data Provision
Vehicle Owner Emergency Management Center User Service Usage Agreement
Vehicle Owner Emergency System Operator Application Usage Agreement
Vehicle Owner Emergency System Operator Vehicle Operating Agreement
Vehicle Owner Enforcement Center Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Enforcement Center Owner Expectation of Data Provision
Vehicle Owner Enforcement Center User Service Usage Agreement
Vehicle Owner Other Vehicles Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Other Vehicles Owner Expectation of Data Provision
Vehicle Owner Other Vehicles User Service Usage Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Basic Vehicle Vehicle 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Emergency Management Center Center The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers.

It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system.

It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted.

It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
Emergency System Operator Center 'Emergency System Operator' represents the public safety personnel that monitor emergency requests, (including those from the E911 Operator) and set up pre-defined responses to be executed by an emergency management system. The operator may also override predefined responses where it is observed that they are not achieving the desired result. This also includes dispatchers who manage an emergency fleet (police, fire, ambulance, HAZMAT, etc.) or higher order emergency managers who provide response coordination during emergencies.
Enforcement Center Center The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Other Emergency Management Centers Center 'Other Emergency Management Centers' provides a source and destination for information flows between various communications centers operated by public safety agencies, emergency management agencies, other allied agencies, and private companies that participate in coordinated management of transportation-related incidents, including disasters. The interface represented by this object enables emergency management activities to be coordinated across jurisdictional boundaries and between functional areas, supporting requirements for general networks connecting many allied agencies. It also supports interface to other allied agencies like utility companies that also participate in the coordinated response to selected highway-related incidents.
Other PIDs Personal 'Other PIDs' represents other personal information devices (PIDs) that are communicating with the device. This includes all connected personal information devices that support wireless short-range communications, including those used by pedestrians, cyclists, and other vulnerable road users (VRUs). This object provides a source and destination for information transfers between connected personal devices. The host device, represented by the Personal Information Device physical object, sends information to, and receives information from the Other PIDs to model all connected personal-to-personal (P2P) communications in ARC-IT.
Other Vehicles Vehicle 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Traveler Personal The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
Emergency Call-Taking 'Emergency Call-Taking' supports the emergency call-taker, collecting available information about the caller and the reported emergency, and forwarding this information to other objects that formulate and manage the emergency response. It receives 9-1-1, 7-digit local access, and motorist call-box calls and interfaces to other agencies to assist in the verification and assessment of the emergency and to forward the emergency information to the appropriate response agency. Emergency Management Center
Emergency Notification Support 'Emergency Notification Support' receives emergency notification messages from vehicles or personal handheld devices, determines an appropriate response, and either uses internal resources or contacts a local agency to provide that response. The nature of the emergency is determined based on the information in the received message as well as other inputs. This object effectively serves as an interface between automated collision notification systems and the local public safety answering point for messages that require a public safety response. This capability depends on an up-to-date registry of public safety answering points/response agencies by coverage area, the type of emergency, and hours of service. Emergency Management Center
Personal Emergency Notification 'Personal Emergency Notification' provides the capability for travelers to report an emergency or activate a panic button to summon assistance. The personal mayday capability is provided by a portable device such as a smart phone. Personal Information Device
Vehicle Emergency Notification 'Vehicle Emergency Notification' provides the capability for drivers or collision detection sensors to report an emergency and summon assistance. It gathers data from on-board collision detection sensors, provides a mechanism for the driver to summon assistance, and includes a communications capability to report the collision including indicators of collision severity, the number of passengers involved, and information about the vehicle that may affect the response. Vehicle

Includes Information Flows:

Information Flow Description
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver input information Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
driver update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
emergency acknowledge Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
emergency data request A request for additional information or a control command issued by the emergency response agency in response to an emergency request for assistance from a traveler.
emergency notification An emergency request for assistance that is automatically initiated by a vehicle or manually initiated by a vehicle occupant or a traveler (vulnerable road user) with a personal information device. The request includes call-back number, date, time, location, pre-event vehicle heading, vehicle make, model, model year, and fuel type, and crash severity indicators. Crash severity indicators include: airbags deployed, number of impacts, crash delta velocity, principle direction of force, and rollover indication. In addition, seatbelt restraint use, number of occupants, occupant location, and intrusion may be included. For commercial vehicles, this flow may also include freight equipment type (box, flatbed, trailer, container, etc.), type of cargo (refrigerated, non-perishable, liquid, etc.), hazardous material data, quantity of cargo, and cargo permits as applicable (hazmat, special routing permissions).
emergency notification relay The relay of a previously received emergency notification. This relay enables a connected vehicle or an equipped personal information device (PID) that is passing within radio range of a vehicle or PID in need of assistance to store the notification and then forward it to a public safety agency when communications is available. Multiple relays may be necessary in remote areas with infrequent traffic and spotty communications coverage. The relay includes all of the information included in the original emergency notification (see 'emergency notification') and relay-specific data that can be used to manage the relay. Relay-specific data may include the date and time of original emergency notification receipt and the number of times the message has been relayed.
emergency operations input Emergency operator input supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
emergency operations status Presentation of information to the operator including emergency operations data, supporting a range of emergency operating positions including call taker, dispatch, emergency operations, security monitoring, and various other operations and communications center operator positions.
host vehicle status Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment.
incident report Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response.
request for service Driver inputs that summon an emergency response, request a financial transaction, or initiate other services.
traveler input User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.
vehicle incident record Data that has been recorded during an incident.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve security

Associated Objective Categories

Objective Category
Emergency/Incident Management: Incident Duration

Associated Objectives and Performance Measures

Objective Performance Measure
Reduce mean incident clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and the time the last responder has left the scene.) Mean incident clearance time per incident.
Reduce mean incident notification time (defined as the time between the first agency's awareness of an incident and the time to notify needed response agencies) by X percent over Y years (i.e., through "Motorist Assist" roving patrol programs, reduction of inaccurate verifications, etc.). Average incident notification time of necessary response agencies.
Reduce mean roadway clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and restoration of lanes to full operational status.) Mean roadway clearance time per incident.
Reduce mean time for needed responders to arrive on-scene after notification by X percent over Y years. Mean time for needed responders to arrive on-scene after notification.
Reduce mean time of incident duration (from awareness of incident to resumed traffic flow) on transit services and arterial and expressway facilities by X percent in Y years. Mean time of incident duration.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status. Emergency Notification Support 01 The center shall determine that a crash or emergency situation has taken place, based on on-board sensor data collected from the vehicle.
02 The center shall monitor subscribed vehicle data, including changes in velocity, attitude/orientation, position, and air bag status to determine when an emergency situation (crash) has happened.
10 The center shall request additional emergency details from or issue commands to the vehicle's security systems or vehicle driver if needed.
11 The center shall maintain a log of all mayday signals received from vehicles.
13 The center shall determine that a collision has occurred based on changes in vehicle sensor data.
14 The center shall determine the location of the sender when it receives a collision notification broadcast.
15 The center shall determine the nature of the emergency from the contents of the received collision notification message.
Vehicle Emergency Notification 09 The vehicle shall provide further details about the emergency to the center upon request from that function.
10 The vehicle shall forward a request for assistance to a center containing the driver's current location, its identity and basic vehicle data relevant to its current condition, as well as any other data, such as personal medical history, vehicle orientation, etc., that may be developed in-vehicle by other systems.
02 Drivers need to be able to automatically or manually send a mayday alert or emergency requests and provide data about the crash and the vehicle's occupants in order to facilitate the quickest and most appropriate response. Emergency Notification Support 04 The center shall collect mayday messages from drivers via onboard devices.
06 The center shall communicate with the mayday emergency message sender (driver) to determine the nature and severity of their situation.
09 The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock doors.
Vehicle Emergency Notification 11 The vehicle shall provide the capability to automatically identify that a collision has occurred using equipment such as collision detection sensors with an interface to mayday type equipment that would automatically detect vehicle problems and send appropriate distress signals to a center.
03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services. Emergency Notification Support 03 The center shall collect mayday messages from travelers via personal handheld devices.
Personal Emergency Notification 01 The personal traveler interface shall provide the capability for a traveler to report an emergency and summon assistance.
02 The personal traveler interface shall provide the capability to accept input from a traveler via a panic button or some other functionally similar form of input device provided as part of the traveler's personal portable device.
03 When initiated by a traveler, the personal traveler interface shall forward a request for assistance to the center containing the traveler's current location and identity.
05 When initiated by a traveler, the personal traveler interface shall forward a request for assistance to another personal traveler interface containing the traveler's current location and identity.
04 Drivers need to be able to rebroadcast crash alerts to remote connected vehicles as well as roadside "hotspots" in order to forward mayday requests even in areas where no vehicle to infrastructure communications exists. Vehicle Emergency Notification 05 The vehicle shall notify emergency responders of the characteristics and damage identified to the vehicle involved in a collision.
10 The vehicle shall forward a request for assistance to a center containing the driver's current location, its identity and basic vehicle data relevant to its current condition, as well as any other data, such as personal medical history, vehicle orientation, etc., that may be developed in-vehicle by other systems.
05 Emergency Management needs to be able to route crash alerts to the appropriate emergency communications center for action. Emergency Call-Taking 05 The emergency call-taking center shall receive emergency notification information from other public safety agencies and present the possible incident information to the emergency system operator.
Emergency Notification Support 07 After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday message.
08 The center shall determine whether the mayday message indicates an emergency that requires the attention of public safety agencies, and forward mayday emergency data to the appropriate agency as necessary.
16 AACN-Relay shall maintain a registry of emergency communications center (ECCs) based on factors such as coverage area (county, state, continent), types of emergencies serviced (e.g. all, hazmat, rail crossing, Brand X autos), and hours of service (days, 24 hr., etc.).
06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities. Emergency Call-Taking 03 The emergency call-taking center shall receive emergency call information from vehicles and present the possible incident information to the emergency system operator.
07 The emergency call-taking center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls and internal analysis of security sensor and surveillance data, and assign each a level of confidence.
Emergency Notification Support 05 The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by the vehicle's safety systems, or by a traveler via a personal handheld device.
12 The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the portable handheld device as directed by the personnel.
Personal Emergency Notification 04 The personal traveler interface shall acknowledge the request for emergency assistance.
07 Travelers need to be able to share information about conditions, incidents, and hazards in their vicinity in order to inform appropriate authorities and other travelers. Personal Emergency Notification 06 The personal traveler interface shall be able to forward conditions, incidents and hazards in their vicinity to other personal traveler interface devices.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
R.E.S.C.U.M.E. (Response, Emergency Staging and Communications, Uniform Management, and Evacuation) ConOps Final 11/19/2012
R.E.S.C.U.M.E. Report on Functional and Performance Requirements, and High-Level Data and Communication Needs Final 2/7/2013
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods 8/15/2014


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Basic Vehicle  
Emergency Management Center High High Moderate Class 4
Enforcement Center Moderate Moderate Low Class 2
Other Emergency Management Centers High High Moderate Class 4
Other PIDs Moderate High Moderate Class 3
Other Vehicles Moderate High Moderate Class 3
Personal Information Device Moderate High Moderate Class 3
Vehicle Moderate High Moderate Class 3



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Basic Vehicle Vehicle driver input information Moderate High High
Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise. Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation.
Basic Vehicle Vehicle host vehicle status Low Moderate High
Unlikely that this includes any information that could be used against the originator. This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety.
Driver Vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Driver Vehicle request for service Moderate High High
This request implies a declaration of intent, which if observed could provide leverage over the driver. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Emergency Management Center Emergency System Operator emergency operations status Moderate High High
Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Emergency Management Center Other Emergency Management Centers incident report High Moderate Moderate
This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Emergency Management Center Personal Information Device emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Emergency Management Center Vehicle emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Emergency Management Center Vehicle emergency data request Moderate Moderate Moderate
This request is a response to an emergency outreach from the Vehicle OBE. If a hostile third party observed this information they might use it in the commission of a crime. An incorrect message may mislead the originator of the emergency request and/or invalidate the request, which which could affect the emergency response scenario. Given that this is part of the mayday chain of events, it should have some priority over other flows. Probably not HIGH, as even without this a physical response will be issued.
Emergency System Operator Emergency Management Center emergency operations input Moderate High High
Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Other Emergency Management Centers Emergency Management Center incident report High Moderate Moderate
This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Other PIDs Personal Information Device emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Other PIDs Personal Information Device emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other PIDs Personal Information Device emergency notification relay Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other Vehicles Vehicle emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Other Vehicles Vehicle emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Other Vehicles Vehicle emergency notification relay Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device Emergency Management Center emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device Other PIDs emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Personal Information Device Other PIDs emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device Other PIDs emergency notification relay Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Personal Information Device Traveler traveler interface updates Not Applicable Moderate Moderate
Personalized data that includes directions and guidance for an individual, but eventually evident anyway. Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Traveler Personal Information Device traveler input Not Applicable Moderate Low
This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Vehicle Basic Vehicle driver update information Low Moderate Moderate
This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Vehicle Emergency Management Center emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle Emergency Management Center emergency notification relay Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle Enforcement Center vehicle incident record Moderate Moderate Low
Any information relevant to legal authorities should be considered need-to-know only. Any information relevant to legal authorities should be provided intact, or the originator may be negatively impacted. There should be other ways for this data to be exchanged.
Vehicle Other Vehicles emergency acknowledge Low Moderate Low
As the request for emergency assistance is by definition going to be a broadcast, the response can be reasonably assumed as not containing any personal information. An incorrect message may mislead the originator of the emergency request, which could affect his behavior If this flow is not delivered the worst case is probably that the originator of the emergency request keeps asking for emergency assistance. There may be some channel loading issues, but unlikely to require anything beyond LOW.
Vehicle Other Vehicles emergency notification Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.
Vehicle Other Vehicles emergency notification relay Moderate High Moderate
Emergency notification flows intended for centers can include PII, so they should be obfuscated. Emergency notification has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for emergency notifications, so MODERATE.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.





System Requirements

System Requirement Need
001 The system shall receive emergency call information from vehicles and present the possible incident information to the emergency system operator. 06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities.
002 The system shall receive emergency notification information from other public safety agencies and present the possible incident information to the emergency system operator. 05 Emergency Management needs to be able to route crash alerts to the appropriate emergency communications center for action.
003 The system shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls and internal analysis of security sensor and surveillance data, and assign each a level of confidence. 06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities.
004 The system shall determine that a crash or emergency situation has taken place, based on on-board sensor data collected from the vehicle. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
005 The system shall monitor subscribed vehicle data, including changes in velocity, attitude/orientation, position, and air bag status to determine when an emergency situation (crash) has happened. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
006 The system shall collect mayday messages from travelers via personal handheld devices. 03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services.
007 The system shall collect mayday messages from drivers via onboard devices. 02 Drivers need to be able to automatically or manually send a mayday alert or emergency requests and provide data about the crash and the vehicle's occupants in order to facilitate the quickest and most appropriate response.
008 The system shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by the vehicle's safety systems, or by a traveler via a personal handheld device. 06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities.
009 The system shall communicate with the mayday emergency message sender (driver) to determine the nature and severity of their situation. 02 Drivers need to be able to automatically or manually send a mayday alert or emergency requests and provide data about the crash and the vehicle's occupants in order to facilitate the quickest and most appropriate response.
010 The system shall determine the appropriate response to the mayday message. 05 Emergency Management needs to be able to route crash alerts to the appropriate emergency communications center for action.
011 The system shall determine whether the mayday message indicates an emergency that requires the attention of public safety agencies, and forward mayday emergency data to the appropriate agency as necessary. 05 Emergency Management needs to be able to route crash alerts to the appropriate emergency communications center for action.
012 The system shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock doors. 02 Drivers need to be able to automatically or manually send a mayday alert or emergency requests and provide data about the crash and the vehicle's occupants in order to facilitate the quickest and most appropriate response.
013 The system shall request additional emergency details from or issue commands to the vehicle's security systems or vehicle driver if needed. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
014 The system shall maintain a log of all mayday signals received from vehicles. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
015 The system shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the portable handheld device as directed by the personnel. 06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities.
016 The system shall determine that a collision has occurred based on changes in vehicle sensor data. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
017 The system shall determine the location of the sender when it receives a collision notification broadcast. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
018 The system shall determine the nature of the emergency from the contents of the received collision notification message. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
019 The system shall maintain a registry of emergency communications center (ECCs) based on factors such as coverage area (county, state, continent), types of emergencies serviced (e.g. all, hazmat, rail crossing, Brand X autos), and hours of service (days, 24 hr., etc.). 05 Emergency Management needs to be able to route crash alerts to the appropriate emergency communications center for action.
020 The system shall provide the capability for a traveler to report an emergency and summon assistance. 03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services.
021 The system shall provide the capability to accept input from a traveler via a panic button or some other functionally similar form of input device provided as part of the traveler's personal portable device. 03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services.
022 The system shall forward a request for assistance to the center containing the traveler's current location and identity. 03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services.
023 The system shall acknowledge the request for emergency assistance. 06 Emergency management needs to verify the crash alert message and/or provide additional notification to the appropriate authorities.
024 The system shall notify emergency responders of the characteristics and damage identified to the vehicle involved in a collision. 04 Drivers need to be able to rebroadcast crash alerts to remote connected vehicles as well as roadside "hotspots" in order to forward mayday requests even in areas where no vehicle to infrastructure communications exists.
025 The system shall forward a request for assistance to another personal traveler interface containing the traveler's current location and identity. 03 Travelers need to be able to send a mayday alert to Emergency Management or other traveler devices in order to get help from emergency services.
026 The system shall be able to forward conditions, incidents and hazards in their vicinity to other personal traveler interface devices. 07 Travelers need to be able to share information about conditions, incidents, and hazards in their vicinity in order to inform appropriate authorities and other travelers.
027 The system shall provide further details about the emergency to the center upon request from that function. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
028 The system shall forward a request for assistance to a center containing the driver's current location, its identity and basic vehicle data relevant to its current condition, as well as any other data, such as personal medical history, vehicle orientation, etc., that may be developed in-vehicle by other systems. 01 Emergency Management needs to be able to determine that a crash or emergency situation has taken place, based on on-board sensor data that detect changes in velocity, vehicle orientation, and airbag status.
04 Drivers need to be able to rebroadcast crash alerts to remote connected vehicles as well as roadside "hotspots" in order to forward mayday requests even in areas where no vehicle to infrastructure communications exists.
029 The system shall provide the capability to automatically identify that a collision has occurred using equipment such as collision detection sensors with an interface to mayday type equipment that would automatically detect vehicle problems and send appropriate distress signals to a center. 02 Drivers need to be able to automatically or manually send a mayday alert or emergency requests and provide data about the crash and the vehicle's occupants in order to facilitate the quickest and most appropriate response.