NL, Extended Sensors, Extended sensors with CPM messages

Open data API in a single place

Provided by Zenodo

Get early access to NL, Extended Sensors, Extended sensors with CPM messages API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.11.23 00:00
Created
2022.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

Use Case Category: Extended Sensors User Story: Extended sensors with CPM messages Location: Dutch (NL) trial site According to 3GPP TS 22.186 R16, Extended Sensors “enable the exchange of raw or processed data gathered through local sensors or live video data among vehicles, RSUs, devices of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation”. User Story: Extended sensors with CPM messages The objective of this user story is to enhance the environmental perception of vehicles by enabling the real-time data exchange between vehicles and RSU. AD vehicles with Level 4 capability require predictive information of environment sufficiently ahead in time. AD vehicles are equipped with on-board sensors, however, with limited range to detect objects and obstacles. CPE extends this range by providing perception of areas not visible to the vehicle sensors due to curves, corners or obstacles in the roads. AD vehicles equipped with 5G technology could share raw sensor data from cameras, LIDAR, etc. or share pre-processed data such as dynamic objects and planned trajectories as the Collective Perception Message (CPM). Additionally, other driving condition data such as weather situation and traffic information can be shared. gNodeB can act as a hub to relay pre-processed data in low resolution or raw data in high resolution, or (in case of MEC) combined data from different vehicles. Exchanging high resolution perception data in real-time requires high bandwidth and low latency communication as promised by 5G (eMBB, uRLLC). In the NL trial, CPE will be evaluated in a cooperative merging scenario at the on-ramp from Nuenen to A270 motorway on the route from Helmond to Eindhoven. Traffic information from the roadside sensors (fixed cameras from SISSBV) will be utilized for a safe merging scenario. There are two connected vehicles in this scenario. The first vehicle is driving from Helmond on A270 and arriving close to the on-ramp from Nuenen while the second vehicle is driving from Nuenen and is arriving close to the ramp to finally merge in the A270. The second vehicle has no information about the traffic situation on the A270 due to its limited field-of-view. The vehicles are connected to two different networks; namely KPN and TNO. Both vehicles send requests to their respective gNodeBs to obtain each other’s environmental information. Collective Perception Service aggregates/fuses CPM messages from vehicles and roadside sensors. The gNodeBs send aggregated CPM messages from the Collective Perception Service to the vehicles. Both vehicles will therefore be aware of each other’s presence and anticipate on it accordingly. When in proximity vehicles also receive CPM messages over C-V2V. Upon request, vehicles can ask for more detailed data about a region, by exchanging pre-processed or raw sensor. The second vehicle can now evaluate and determine its merging possibilities in real time considering safety and traffic situation. When the second vehicle is on the on-ramp, it sends its decision to the first vehicle to make it aware about its merging action. Hence, a safe and efficient merging manoeuvre can be achieved using CPE and exploiting the capabilities of 5G.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks