Light Vehicle OBE --> Personal Information Device:
shared vehicle access acknowledgment

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

shared vehicle access acknowledgment (Information Flow): Acknowledge request for access to a shared use vehicle, including any additional status information.

Light Vehicle OBE (Source Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.

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:

TI06: Shared Use Mobility and Dynamic Ridesharing

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

None

This Triple has the following triple relationships:

None

Communication Solutions

(None-Data) - Secure Wireless Internet (EU) (43)
(None-Data) - Secure Wireless Internet (ITS) (43)

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

Selected Solution

(None-Data) - Secure Wireless Internet (ITS)

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for I-M: Secure Wireless Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. 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 Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

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	True
Cardinality	Unicast
Initiator	Source
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	Since this is related to access to a vehicle, it should be obfuscated so that unentitled parties cannot interfere.	Since this is related to access to a vehicle, it should be delivered in timely and correct fashion, or the lack of acknowledgement may require follow-up.	Since this is related to access to a vehicle, it should be delivered in timely and correct fashion, or the lack of acknowledgement may require follow-up.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Light Vehicle OBE --> Personal Information Device:shared vehicle access acknowledgment