Service Monitor System --> Multi-Access Edge Computing:
time local form
This flow may also be implemented by
Service Monitor System --> Connected Vehicle Roadside Equipment: time local form Definitions
time local form (Information Flow): Time local form includes UTC time synchronized with the external source in a format usable by connected vehicle center functions.
Service Monitor System (Source Physical Object): The 'Service Monitor System' represents one or more center-based systems that provide monitoring, management and control services necessary to other applications and/or devices operating within the Connected Vehicle Environment. These support services enable other applications to provide transportation services.
Multi-Access Edge Computing (Destination 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
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:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
Communication Solutions
-
NTP - UDP/IP (11)
Selected Solution
NTP - UDP/IPSolution Description
|
ITS Application Entity
No Standard Needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
No Standard Needed ![]() |
Security
(None) ![]() |
|
|
TransNet
|
|||
|
Access
Internet Subnet Alternatives ![]() |
|||
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 | Now |
| Spatial Context | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| 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 | Not Applicable | High | Moderate | |
| Basis | Time reference is intended to be univerally available. | Time must be highly coordinated for some applications. This support function must meet the highest requirement. | Time coordination must always be in place, but local mechanisms for tracking time should suffice to avoid catastrophic failures for known use cases, thus MODERATE. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |
