INFRASTRUCTURE & TALKING TRAFFIC

​

In vehicle infrastructure

 

• Network layer routing table: The routing table stores information about the location of neighboring nodes in combination with a timestamp of the node’s latest update. The table entries are created based on position and time information from incoming messages. It is assumed that the geographic routing is executed on network layer of the communication stack. This also implies that the network header of the message has to contain mobility information (i.e. node ID, position, timestamp). Manipulation of the table content may cause routing attacks as wormhole or relay attacks, or possibly facilitate DoS (e.g., black- or gray-hole attacks).

• Local Dynamic Map (LDM) on facilities layer: The LDM can be assumed to be a container that collects and manages all incoming messages. All applications running on the ITS-S can access this central storage in order to use a consistent base of data. It is assumed that this LDM is responsible for filtering duplicates or deleting outdated messages. As applications on application layer accesses this system, it is assumed that the LDM is operated on facilities layer. Manipulation of the LDM content may cause attacks related to traffic safety and traffic efficiency application.

​

• Local station information on facilities layer (VIN, manufacturer, model, etc.):It is assumed that local station information is available and accessible to the application layer. Manipulation of this data may cause problems to the applications running at neighboring nodes. If, for example, local station dimensions at vehicle A are manipulated and subsequently broadcasted, traffic safety applications on vehicle B receiving this data may calculate false advice, warning, or reaction. Furthermore accessing sensitive, identifying information by malicious applications can cause privacy infringements.

​

• Application Unit (AU) / Head Unit (HU): It is assumed that the HU consists of an HMI, the navigation system and telephone applications. Additionally, it is reasonable that Consumer Electronic devices are connected to the HU. Manipulation of the HU by attacks could cause bogus advisories for the driver.

 

• Communication & Control Unit (CCU): The CCU is a central router for different communication links such as ITS G5A/B/C and ITS IMT Public.

​

• Electronic Control Unit (ECU): An ECU combines an on-board sensor concentrator for some components as Power train, Chassis & Safety or Body Electronics.

​

• Sensor: On-board sensors are controlled and managed by ECUs.

Nomadic devices are stand-alone systems that can be used either in vehicles or by other traffic participants like bicyclists as a sender of regular position information and as a receiver of V2X messages. It is further assumed that such a device has no connection to the ITS-S on-board system. Here-I-Am devices would only be able to send CAMs with the current position and timestamp.

From the view point of the security, a nomadic device that is actively participating in the V2X communication may be more attractive for attackers that attempt to extract secret keys in order to use them afterwards for different attacks.

​

Road side Infrastructure 

​

A Roadside Unit consists in general of the same elements as a vehicle. The communication stack and the applications are probably very comparable with the vehicle station but the internal network may look different. A vehicle is connected with its Powertrain, Chassis & Safety and Body Electronic whereby a RSU is connected to road sensors (e.g. induction loops, cameras) and a back-end control center.

​

• Network layer routing table.

• Local Dynamic Map (LDM) on facilities layer.

• Local station information on facilities layer (serial number, operator..)

• Application Unit (AU)

• Communication and control Unit (CCU)

• Electronic Control Unit (ECU) combines on-board sensor concentrator such as Powertrain, Chassis & Safety and Body Electronic.

• Sensors.

​

Data processing hub

​

Back-end Systems

• Public key infrastructure (PKI)

• Traffic Management Centre.

• Roadside unit Management.

• E-call service center.

​

Communication Protocol

​

IEEE 802.11p based G5A, G5B & G5C protocols with G5A and G5B frequencies reserved for traffic   

Safety and efficiency relevant message exchange.

• G5A and G5B for V2V and V2I interactions.

• G5A for I2I interactions.

• G5C for non-safety critical functions.

• IMT public.

​