Commercial Vehicle OBE --> Fleet and Freight Management Center:
commercial vehicle identities

Definitions

commercial vehicle identities (Information Flow): Identification information for the Commercial Vehicle (e.g., license plate number or USDOT number), Freight Equipment (e.g., container, chassis, or trailer identification), Carrier, and Driver.

Commercial Vehicle OBE (Source Physical Object): The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles.

Fleet and Freight Management Center (Destination Physical Object): The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.

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

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

Selected Solution

US: SAE J3067 (J2735 SE) - Secure Wireless Internet (ITS)

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for I-M: Secure Wireless Internet (ITS). The US: SAE J3067 (J2735 SE) standards include a proposed solution for the upper-layers to implement V2X information flows that do not yet have fully standardized messages, functionality or performance characteristics. The I-M: Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.

ITS Application Entity
Mind the gapMind the gapMind the gap

SAE J3067
Click gap icons for more info.
Mgmt
Facilities

SAE J2945
Security
Mind the gapMind the gap
TransNet
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 Destination
Authenticable True
Encrypt True


Interoperability Description
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Moderate Moderate Moderate
Basis Includes vehicle and or driver PII, which should be disclosed only to the intended recipient or the driver/vehicle may be inappropriately tracked or monitored. Data should be timely and correct to support application needs, but not catastrophic if it is temporarily wrong or unavailable. Data should be timely and correct to support application needs, but not catastrophic if it is temporarily wrong or unavailable.


Security Characteristics Value
Authenticable True
Encrypt True