Vehicle --> Other Vehicles:
map update sharing

Definitions

map update sharing (Information Flow): Peer to peer sharing of map updates. Map updates could include a new underlying static or real-time map or map layer(s) update. Map layers can include highways, major roads, streets, public transport routes, pedestrian routes, topography, points of interest, and regulatory information including turn restrictions and speed limits.

Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. 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, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Other Vehicles (Destination Physical Object): 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.

Included In

This Triple is in the following Service Packages:

• SU04: Map Management

This triple is associated with the following Functional Objects:

• Vehicle Map Management

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

• tov-map_updates

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - BTP/GeoNetworking/G5 (42)

Selected Solution

(None-Data) - BTP/GeoNetworking/G5

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt ETSI 302 890-1 Addressed Elsewhere	Facilities Development needed	Security Bundle: ETSI ITS-S Security Architecture
	TransNet Bundle: GeoNetworking BTP
	Access Bundle: ETSI ITS-G5

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

Security