Connected Vehicle Roadside Equipment --> Service Monitor System:
RSE status

Definitions

RSE status (Information Flow): Monitoring of RSE device status including current mode, operational status, and configuration settings. It includes device housekeeping/heartbeat monitoring and includes network information, the status of installed applications, the configuration of managed devices, cybersecurity and physical security status of the RSE.

Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

Service Monitor System (Destination 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.

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

Communication Solutions

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) - Guaranteed Secure Internet (ITS)

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for I-I: Guaranteed Secure Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-I: Guaranteed Secure Internet (ITS) standards include lower-layer standards that support secure communications with guaranteed delivery between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity
Mind the gapMind the gapMind the gap

Development needed
Click gap icons for more info.
Mgmt
Facilities
Mind the gap

Development needed
Security
Mind the gapMind the gap
TransNet

IP Alternatives
IETF RFC 9293
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.

Characteristics

Characteristic Value
Time Context Recent
Spatial Context Local
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt True


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 Moderate Moderate High
Basis Will include some sort of identifier for the RSE and given the content of the flow this will indicate what operations the RSE is capable of. This should be considered actionable intelligence: if a hostile actor knows what field devices have particular capabilities, he can target an attack to maximum effect. Since this is used to monitor the health of the RSE, any corruption or modification of this information could lead to unnecessary maintenance activity, or delay necessary such activity. Impact will be limited to the RSEs who's flows were so affected. Local connections must be fully available, as it suggests the presence of maintenance personnel attempting to work on the RSE. Without this interface, there is little the field personnel can do, effectively making the RSE useless.


Security Characteristics Value
Authenticable True
Encrypt True