01
Standards-first.
Every implementation follows ETSI and 3GPP specifications. No proprietary extensions, no vendor lock-ins. Code that interoperates by design.
Professional V2X · C-ITS engineering
From protocol stack to street-side deployment. Day 1 awareness, Day 2 perception, MEC-V2X edge, PKI. Hardware-neutral by design.
Vehicular
CAM · DENM · CPM · VAM · MCM
Infrastructure
MAPEM · SPATEM · SREM · SSEM · IVIM
Use cases
RHS · ICRW · LCRW · T2G · GLOSA
Access
ETSI ITS-G5 · C-V2X
Security
TS 103 097 · CCMS · SCMS
How we work
003 / PRINCIPLES
01
Every implementation follows ETSI and 3GPP specifications. No proprietary extensions, no vendor lock-ins. Code that interoperates by design.
02
Our stack runs on any certified V2X platform — chipsets, modules, OBUs, RSUs — regardless of vendor or radio access technology.
03
Code that has run on actual deployments, not only in the lab. Validated against the same test suites used in ETSI interoperability events.
What we work on
Five practice areas — from the message bytes on the wire, to the application services those messages enable, to the security and compute layers around them.
Day 1, Day 1.5 and Day 2 vehicular protocols: cooperative awareness (CAM), environmental notifications (DENM), collective perception (CPM), VRU awareness (VAM) and maneuver coordination (MCM). Codecs validated bit-exact against vendor reference samples.
Roadside and information services per ETSI TS 103 301: MAPEM, SPATEM, SREM, SSEM, IVIM. Plus services and point-of-interest extensions — POIM, SAEM, RTCMEM. Conformance from the message bytes up.
The services those messages enable, organised by ETSI horizon. Day 1 safety — RHS, ICRW, LCRW, EEBL, roadworks, slow/stationary vehicle, hazardous location, wrong-way driving. Day 1 traffic & information — T2G, GLOSA, IVS, traffic jam ahead, probe vehicle data, emergency vehicle approaching, EV charging spot notification, public transport priority. Day 1.5 cooperative — CACC, platooning, cooperative merging. Day 2 advanced — collective perception (CPS), maneuver coordination (MCS), VRU awareness and clusters, sensor sharing.
ETSI TS 103 097 secured messages, TS 102 941 trust management, integration with CCMS / SCMS infrastructure. Certificate validation, pseudonym handling, enrolment and authorization flows.
Local Dynamic Map (LDM), low-latency cooperative applications and multi-access edge integration. The compute layer between radios and the V2X services that need it.
Who we work with
V2X happens where vehicles, platforms and infrastructure meet. We sit at the technical layer that makes all three speak the same protocol.
Automotive OEMs & integrators
OBU stack development, ITS-S layer integration, ADAS coupling. We bring V2X capability into vehicle programmes that need to ship — not into perpetual R&D loops.
V2X platform vendors
If you're looking for technical depth to bring your platform into real European projects, we operate as the integration and certification arm — across regions, vendors and roadside infrastructure.
Cities & traffic operators
We work alongside the systems municipalities already operate — adding V2X capability into operations, dispatch and infrastructure without forcing replacements nobody asked for.
Why us
The technology is standardized. What's still hard is getting it to work with what's already on the ground.
We know V2X in production, not only on paper.
We've worked across real deployments — vendors, regions, use cases. The kind of knowledge that comes from operating live systems, not from reading specification documents.
We are fully ETSI and 3GPP aligned.
Every V2X message family we handle follows European and 3GPP standards. Our implementations are validated against the same test suites used in official interoperability events.
We are hardware-neutral by design.
We work across every major V2X platform — chipsets, modules, OBUs, RSUs. Architecture decisions stay on the architecture side, not on the procurement one.
We build tools, not presentations.
Our V2X message decoder runs live on this website. Try it — a small sample of the engineering we bring to every project.
Behind SkyV2X
The practice is led by Miguel Fornell, V2X engineer working across deployments, standards and EU research projects since 2017 — collective perception, congestion control, smart-city mobility and edge V2X.
Experience
8+ years
V2X engineering since 2017
Domain
Day 1 — Day 2
GNSS · ADAS · 5G NR · MEC
Research
Peer-reviewed
CPM, congestion, smart-city
EU projects
Active
6G, smart-city, edge V2X
Selected research
A subset of publications co-authored by the lead engineer. Full record on Google Scholar.
V2X congestion control for multi-channel operation: a scalable validation in virtualized environments
M. Sepulcre, Y. Guadalcazar, M.A. Fornell, G. Thandavarayan, F.P. Vera et al.
AI-Driven Vehicle Condition Monitoring with Cell-Aware Edge Service Migration
C. Kalalas, P. Mulinka, G.C. Belmonte, M. Fornell, M. Dalgitsis, F.P. Vera et al.
Smart City Pilots: Advancing Sustainable Mobility and Urban Innovation
L. Bongiovanni, E. Armengaud, S.F. Jover, I.K. Yalcin, E. Rossini, M. Mamei et al.
ETSI standard-compliant Collective Perception Service for Connected Automated Driving
S. Lopez, M. Sepulcre, M. Fornell, D. Quiñones, J. Espinosa, J. Gozalvez et al.
Short first call, no deck. We scope around what you actually need — whether that's a stack component, an integration, or a deployment.