Pathway Communications Unit --> Personal Information Device:
communications signature

This triple is bi-directional. See also Personal Information Device --> Pathway Communications Unit: communications signature

Definitions

communications signature (Information Flow): Communications from vehicle or personal devices that can be monitored by ITS field equipment to uniquely identify the device. This flow represents communications from devices (via Bluetooth or Wi-Fi) that may be monitored by ITS field equipment or any other passive or active communications from the device that can be used to identify the device. This flow specifically covers passive monitoring of device communications.

Pathway Communications Unit (Source Physical Object): The 'Pathway Communications Unit' provides wireless communications between the pathway infrastructure (either indoor or outdoor) and nearby mobile devices; Communications with adjacent field equipment (including other PCUs) and back-office centers that monitor and control the PCU are also supported. The PCU provides basic radio communications supporting the lower layers of the OSI stack (TransNet and SubNet layers of the ARC-IT communications model). Importantly, it can also serve as a reference for mobile devices to determine their position more accurately (e.g., through triangulation or other means).

Personal Information Device (Destination 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.

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 Not Needed) - Local Unicast Wireless (1609.2)

Solution Description

This solution is used within the U.S.. It combines standards associated with (Data Not Needed) with those for V-X: Local Unicast Wireless (1609.2). The (Data Not Needed) standards include an empty set of upper-layer standards. The V-X: Local Unicast Wireless (1609.2) standards include lower-layer standards that support local-area unicast wireless solutions applicable to North America, such as WAVE DSRC, LTE-V2X, LTE, Wi-Fi, etc.

ITS Application Entity

No Standard Needed
Click gap icons for more info.

Mgmt

Addressed Elsewhere
Facilities

No Standard Needed
Security
Mind the gap
TransNet

IEEE 1609.3
Access
Mind the gapMind 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 Adjacent
Acknowledgement False
Cardinality Broadcast
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 Not Applicable Moderate Low
Basis Byproduct flow, does contain PII (Bluetooth MAC addresses for example) but already existant and not required. While the flow here is a byproduct of existing transmissions, if the data contained within is not reliable then the application using this data will generate erroneous results. Integrity is set MODERATE to emphasize to the application developer that they should verify the flows' integrity, or develop methods to minimize integrity's importance, in which case this could be LOW. This is a by-product flow; taking advantage of existing wireless emissions to measure travel times for example. If this flow is not present then the application might not function, however, the application is not deploying this flow, it already exists.


Security Characteristics Value
Authenticable True
Encrypt False