Wayside Equipment --> Multi-Access Edge Computing:
arriving train information

This flow may also be implemented by Wayside Equipment --> Connected Vehicle Roadside Equipment: arriving train information

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

arriving train information (Information Flow): Information for a train approaching a highway-rail intersection that may include direction and allow calculation of approximate arrival time and closure duration.

Wayside Equipment (Source Physical Object): 'Wayside Equipment' represents train interface equipment (usually) maintained and operated by the railroad and (usually) physically located at or near a grade crossing. It is a source and destination for information for, or about, approaching trains and their crews (e.g. the time at which the train will arrive and the time it will take to clear a crossing, crossing status or warnings, etc.). Generally one wayside equipment interface would be associated with one highway rail intersection. However, multiple crossings may be controlled using information based on data from one wayside equipment interface.

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

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

MEC Rail Crossing Warning

This Triple is described by the following Functional View Data Flows:

None

This Triple has the following triple relationships:

None

Communication Solutions

(None-Data) - Secure Wireless Internet (EU) (43)
(None-Data) - Secure Wireless Internet (ITS) (43)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Secure Wireless Internet (ITS)

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for I-M: Secure Wireless Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-M: Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

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	Adjacent
Acknowledgement	True
Cardinality	Unicast
Initiator	Source
Authenticable	True
Encrypt	False

Interoperability	Description
Local	In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Low	High	Moderate
Basis	Trains arriving should be visible, viewable and certainly not concealed. Reception of this information may indicate position or intended position of the recipient, which is slightly sensitive; thus LOW and not N/A.	While there are other mechanisms for receiving this information, this data flow needs to be accurate lest a catastrophic mistake be made.	While the data is critically important, there are other mechanisms for noting an approaching train (crossing gates, the train itself).

Security Characteristics	Value
Authenticable	True
Encrypt	False

Wayside Equipment --> Multi-Access Edge Computing:arriving train information