Pathway Communications Unit --> Micromobility Vehicle OBE:
communications signature

This triple is bi-directional. See also Micromobility Vehicle OBE --> 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).

Micromobility Vehicle OBE (Destination Physical Object): The Micromobility Vehicle On-Board Equipment (MMV OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The MMV OBE includes general capabilities that apply to bicycles and other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles. The MMV OBE includes the common interfaces and functions that could apply to any low-powered mobility device. The radio(s) supporting V2V and V2I communications are a key component of the MMV OBE. 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, and enhanced traveler interfaces (through PIDs), complement traveler information services so that, in addition to making informed mode and route selections, the vulnerable road user travels these routes in a safer and more consistent manner.

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

  • (Data Not Needed) - Bluetooth (0)
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) - Bluetooth

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (Data Not Needed) with those for Bluetooth. The (Data Not Needed) standards include an empty set of upper-layer standards. The Bluetooth standards include lower-layer standards that support wireless communications over a personal area network of up to roughly 100 meters.

ITS Application Entity

No Standard Needed
Click gap icons for more info.
Mgmt

(None)
Facilities

No Standard Needed
Security

(None)
TransNet

No Standard Needed
Access

Bluetooth
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