Personal Information Device --> Other PIDs:
emergency notification relay

This triple is bi-directional. See also Other PIDs --> Personal Information Device: emergency notification relay

Definitions

emergency notification relay (Information Flow): 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.

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:

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

Data for Distribution (TBD) - Apache Kafka over Wireless

Solution Description

This solution is used within the U.S.. It combines standards associated with Data for Distribution (TBD) with those for Apache Kafka over Wireless. The Data for Distribution (TBD) standards include a placeholder for upper-layer standards necessary to define the data (elements and structures) necessary to complete a solution for the information flow based on data distribution technologies. The data standard will need to include a specific customization for the desired data distribution technology used (e.g., Kafka, DDS, etc.).. The Apache Kafka over Wireless standards include lower-layer open source code that supports data distribution of specific types of data over wireless links.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

Apache Zookeeper
Facilities
Mind the gapMind the gap

Apache Kafka
Apache Zookeeper
Security

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
Access
Mind the gapMind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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