Personal Information Device --> Other PIDs:
emergency notification
This triple is bi-directional. See also
Other PIDs --> Personal Information Device: emergency notification
Definitions
emergency notification (Information Flow): 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).
Personal Information Device (Source Physical Object): 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.
Other PIDs (Destination Physical Object): '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.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: eCall - Secure Wireless Internet (EU) (6)
- US: SAE J3067 (J2735 SE) - Secure Wireless Internet (ITS) (14)
- (None-Data) - Secure Wireless Internet (EU) (43)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
|
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | High | Moderate | |
Basis | 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. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |