Multi-Access Edge Computing --> Commercial Vehicle OBE:
intersection geometry
This flow may also be implemented by
Connected Vehicle Roadside Equipment --> 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.
Multi-Access Edge Computing (Source Physical Object): 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems
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:
- MEC Intersection Management
- MEC Intersection Safety
- MEC Map Management
- 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)
Selected Solution
US: SAE Lane-Level Mapping - Secure Wireless Internet (ITS)Solution Description
|
ITS Application Entity
![]()
SAE J2735 ![]() SAE J2945/A ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
SAE J2945 ![]() SAE J2945/A ![]() |
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 | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| 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 |




