Network Time Source --> Multi-Access Edge Computing:
time

This flow may also be implemented by Network Time Source --> Connected Vehicle Roadside Equipment: time

Definitions

time (Information Flow): Current time expressed in Universal Time Coordinated (UTC) format from a Stratum-2 time server.

Network Time Source (Source Physical Object): The 'Network Time Source' represents the external time source the Connected Vehicle Service Monitor System uses as the basis for time. This is likely implemented as a Stratum-2 Network Time Server that is 2 steps removed from a basic time source (e.g., atomic clock).

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)
Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

NTP - UDP/IP

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with NTP with those for I-I: UDP/IP. The NTP standards include standards required to reliably set time information in a subsystem. The I-I: UDP/IP standards include lower-layer standards that support the Network Time Protocol that allows NTP servers to provide time synchronization services to other NTP servers and clients.

ITS Application Entity
Mind the gap

No Standard Needed
Click gap icons for more info.
Mgmt
Facilities
Mind the gap

No Standard Needed
Security
Mind the gap

(None)
TransNet

IETF RFC 768
IP Alternatives
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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

CharacteristicValue
Time Context Now
Spatial Context Local
Acknowledgement True
CardinalityUnicast
InitiatorDestination
AuthenticableTrue
EncryptFalse


InteroperabilityDescription
NationalThis 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 CharacteristicsValue
AuthenticableTrue
Encrypt False