Multi-Access Edge Computing --> Personal:
location correction
This flow may also be implemented by
Connected Vehicle Roadside Equipment --> Personal: location correction Definitions
location correction (Information Flow): Information provided to improve positional accuracy. These corrections allow a mobile GPS receiver, such as a GPS system in a connected vehicle, to achieve a
greater absolute positional accuracy, compensating for errors that exist in satellite positioning.
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
Personal (Destination Physical Object): The 'Personal' physical object is used to model core capabilities that are common to more than one physical object in the 'Personal' class. It provides the general executive, management, and utility functions that may be shared by different types of personal devices.
Included In
This Triple is in the following Service Packages:
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) - Guaranteed Secure Wireless Internet (EU) (43)
Selected Solution
(None-Data) - Guaranteed Secure Wireless Internet (EU)Solution Description
|
ITS Application Entity
![]() ![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
Development needed ![]() |
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.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Local |
| 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). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Not Applicable | High | High | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | An incorrect location corrections message, could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity. | If locations corrections are not delivered, catastrophic consequences could result from incorrect locations data on the device that should have received the corrections. DISC: HIGH is a tall barrier for this flow. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |


