en_alt:c-its
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en_alt:c-its [2026/08/10 10:40] – Draft of the restructured page (community-approved structure) hajo | en_alt:c-its [2026/09/08 08:34] (current) – [Further reading] idahoenigmann | ||
|---|---|---|---|
| Line 31: | Line 31: | ||
| ===== Message types ===== | ===== Message types ===== | ||
| - | Several standardised message types travel over C-ITS. | + | Several standardised message types travel over C-ITS. |
| - | ^ Type ^ Full name ^ In one sentence ^ | + | All messages share a common header. This header includes the messageId, which specifies the type of message. |
| - | | [[en_alt: | + | |
| - | | [[en_alt: | + | ^ Message Id ^ Type ^ Full name ^ In one sentence ^ |
| - | | [[en_alt: | + | | 1 | [[en_alt: |
| - | | [[en_alt: | + | | 2 | [[en_alt: |
| - | | [[en_alt: | + | | 4 | [[en_alt: |
| + | | 5 | [[en_alt: | ||
| + | | 6 | [[en_alt: | ||
| + | | 9 | SREM | Signal Request Extended Message | Request message for green light at intersection | | ||
| + | | 10 | SSEM | Signal request Status Extended Message | Reply message to SREM | | ||
| + | | 14 | CPM | Collective Perception Message | Sensor information | | ||
| + | |||
| + | Other, less common, message types are: | ||
| + | * VRU Awareness Message (VAM), | ||
| + | * Point of Interest Message (POIM), | ||
| + | * Parking Information Message (PIM), | ||
| + | * Interference Management Zone Message (IMZM), | ||
| + | * Service Announcement Essential Message (SAEM), | ||
| + | * Electric Vehicle Charging Spot Notification (EVCSN), | ||
| + | * Electric Vehicle Recharging Spot Reservation messages (EV-RSR), | ||
| + | * Maneuver Coordination Message (MCM), | ||
| + | * Marshalling Infrastructure Message (MIM), | ||
| + | * Marshalling Vehicle Message (MVM) | ||
| + | |||
| + | While ETSI defines the structure of C-ITS messages and their permitted value ranges, some values remain open to interpretation—for example, a role may be represented as an integer without specifying what a value such as 42 actually means. ETSI can also be vague about when and how often messages should be transmitted, | ||
| + | |||
| + | C-Roads (https:// | ||
| ==== CAM ==== | ==== CAM ==== | ||
| Line 50: | Line 71: | ||
| - Vehicle length and width | - Vehicle length and width | ||
| - Status of the lights, e.g. indicators, low beam, rear fog light | - Status of the lights, e.g. indicators, low beam, rear fog light | ||
| + | |||
| + | The specification for message content is given by ETSI EN 302 637-2 and ETSI TS 103 900. | ||
| Since 2019 more and more cars have been equipped with C-ITS and transmit this data, as long as Car2X is enabled in the vehicle' | Since 2019 more and more cars have been equipped with C-ITS and transmit this data, as long as Car2X is enabled in the vehicle' | ||
| - | {{: | + | {{: |
| ==== DENM ==== | ==== DENM ==== | ||
| - | DENMs are **event-driven** warning messages (ETSI EN 302 637-3). While CAMs are broadcast continuously, | + | DENMs are **event-driven** warning messages (ETSI EN 302 637-3 and ETSI TS 103 831). While CAMs are broadcast continuously, |
| Typical triggers: | Typical triggers: | ||
| Line 100: | Line 123: | ||
| IVIMs are sent by RSUs, for example along the ASFINAG motorway network. Unlike a DENM, an IVIM applies to a defined section of road rather than to a single point. | IVIMs are sent by RSUs, for example along the ASFINAG motorway network. Unlike a DENM, an IVIM applies to a defined section of road rather than to a single point. | ||
| + | ===== Further reading ===== | ||
| + | |||
| + | Background on the technology and on the policy behind it. Sources for individual deployments are listed with the regions themselves, on [[en_alt: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
en_alt/c-its.1786351217.txt.gz · Last modified: by hajo
