Connected Vehicle Roadside Equipment --> Center:
RSE application status

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

RSE application status (Information Flow): Monitoring of RSE application status including current mode, operational status, and configuration settings. It includes the status of installed applications and the application-specific data provided by 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.

Center (Destination Physical Object): This general physical object is used to model core capabilities that are common to any center.

Included In

This Triple is in the following Service Packages:

SU01: Connected Vehicle System Monitoring and Management

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

(None-Data) - Secure Internet (ITS) (43)
(None-Data) - Apache Kafka (44)
(None-Data) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
(None-Data) - OASIS AMQP (61)

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) - OASIS AMQP

Solution Description

This solution is used within Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for OASIS AMQP. The (None-Data) standards include an unspecified set of standards at the upper layers. The OASIS AMQP standards include lower-layer standards that support data distribution of specific types of data.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities Development needed OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	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.

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	Low
Basis	Device status information should not be viewable by third parties, as those with criminal intent may use this information toward their own ends.	A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.	A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Connected Vehicle Roadside Equipment --> Center:RSE application status