Connected Vehicle Roadside Equipment --> Other Connected Vehicle Roadside Equipment:
wrong way vehicle detected

This triple is bi-directional. See also Other Connected Vehicle Roadside Equipment --> Connected Vehicle Roadside Equipment: wrong way vehicle detected

Definitions

wrong way vehicle detected (Information Flow): Notification that a vehicle has been detected traveling in the wrong direction. This can be a direct report by an equipped vehicle that is being driven in the wrong direction or a report of a non-equipped vehicle that has been detected traveling in the wrong direction. It includes the current location, speed, acceleration, and heading of the wrong way vehicle.

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.

Other Connected Vehicle Roadside Equipment (Destination Physical Object): Representing another Connected Vehicle Roadside Equipment, 'Other Connected Vehicle Roadside Equipment' supports peer to peer communication and direct coordination between RSEs. It provides a source and destination for information that may be exchanged between RSEs.

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:

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

EU: DEN Service - BTP/GeoNetworking/G5

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with EU: DEN Service with those for V-X: BTP/GeoNetworking/G5. The EU: DEN Service standards include upper-layer standards required to implement V2x decentralized environmental notification information flows. The V-X: BTP/GeoNetworking/G5 standards include lower-layer standards that support broadcast, near constant, low latency vehicle-to-vehicle and vehicle-to-infrastructure communications using the ETSI GeoNetworking Bundle over the 5.9GHz spectrum.

ITS Application Entity
Mind the gap

ETSI 102 894-2
ETSI 102 638
Click gap icons for more info.

Mgmt
Mind the gapMind the gap

ETSI 302 890-1
Addressed Elsewhere
Facilities

ETSI 302 637-3
Security
Mind the gapMind the gap
TransNet
Mind the gap
Access
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

CharacteristicValue
Time Context Now
Spatial Context Adjacent
Acknowledgement True
CardinalityBroadcast
InitiatorSource
AuthenticableTrue
EncryptFalse


InteroperabilityDescription
LocalIn 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 Not Applicable Moderate Moderate
Basis This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This information could lead directly to an severe incident, however other mechanisms exist to confirm this data, thus availability and integrity are set to MODERATE instead of HIGH. This information could lead directly to an severe incident, however other mechanisms exist to confirm this data, thus availability and integrity are set to MODERATE instead of HIGH.


Security CharacteristicsValue
AuthenticableTrue
Encrypt False