Transportation Information Center --> Commercial Vehicle OBE:
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.
Transportation Information Center (Source Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Commercial Vehicle OBE (Destination 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.
This Triple is an instantiation of the more general triple:
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- TIC Traffic Control Dissemination
- Vehicle Eco-Driving Assist
- Vehicle Intersection Movement
- Vehicle Map Management
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
Communication Solutions
-
US: SAE Lane-Level Mapping - Secure Wireless Internet (ITS) (4)
-
US: SAE Other J2735 - Secure Wireless Internet (ITS) (12)
-
EU: Signal Control Messages - Secure Wireless Internet (EU) (16)
-
Data for Distribution (TBD) - Apache Kafka over Wireless (44)
-
Data for Distribution (TBD) - OMG DDS over Wireless (44)
-
Data for Distribution (TBD) - Eclipse Zenoh over Wireless (44)
-
Data for Distribution (TBD) - OASIS MQTT over Wireless (47)
-
Data for Distribution (TBD) - OASIS AMQP over Wireless (61)
Selected Solution
Data for Distribution (TBD) - OASIS MQTT over WirelessSolution Description
|
ITS Application Entity
![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
OASIS MQTT DMP ![]() |
Facilities
![]()
OASIS MQTT ![]() |
Security
|
|
|
TransNet
|
|||
|
Access
![]() ![]() ![]()
|
|||
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.
This Triple is an instantiation of the more general triple:
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Local |
| Acknowledgement | False |
| Cardinality | Broadcast |
| Initiator | Destination |
| 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). |
This Triple is an instantiation of the more general triple:
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | High | Moderate | |
| Basis | Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. | Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. | Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |



