Map Update System --> Vehicle:
intersection geometry

Definitions

intersection geometry (Information Flow): The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.

Map Update System (Source Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.

Vehicle (Destination 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.

Included In

This Triple is in the following Service Packages:

• SU04: Map Management

This triple is associated with the following Functional Objects:

• Map Management
• Vehicle Eco-Driving Assist
• Vehicle Intersection Warning
• Vehicle Map Management

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

• intersection_details_for_vehicle
• intersection_lanes_for_vehicle

This Triple has the following triple relationships:

Communication Solutions

• US: SAE Other J2735 - Secure Wireless Internet (ITS) (9)
• EU: Signal Control Messages - Secure Wireless Internet (EU) (13)
• Data for Distribution (TBD) - Apache Kafka over Wireless (36)
• Data for Distribution (TBD) - OMG DDS over Wireless (36)
• Data for Distribution (TBD) - OASIS MQTT over Wireless (42)
• Data for Distribution (TBD) - OASIS AMQP over Wireless (45)

Selected Solution

Data for Distribution (TBD) - Apache Kafka over Wireless

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Apache Zookeeper	Facilities Apache Kafka Apache Zookeeper	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	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

Security