Personal Information Device --> Other PIDs:
VRU hazard event
This triple is bi-directional. See also
Other PIDs --> Personal Information Device: VRU hazard event
Definitions
VRU hazard event (Information Flow): Notification of a potential hazard or event that is detected or reported by the traveler or vulnerable road user (VRU) using a PID or riding a micromobility vehicle (MMV). Potential hazards may be determined by sudden movements by travelers, such as movements around a location which may indicate foreign objects (people, animals, debris, other obstacles) in the travel lanes. Hazards may also be manually entered by the traveler into a personal information device (e.g., crowdsourcing) to be shared with other travelers.
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
- US: SAE VRU Messages - Local Unicast Wireless (1609.2) (4)
- (None-Data) - Local Unicast Wireless (EU) (38)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 SAE J2945 SAE J2945/9 |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
SAE J2735 SAE J2945 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
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 | False |
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 | Low | High | Moderate | |
Basis | Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation. | MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians. | MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |