Revisions

The audit covers every service

The official ETSI suite now runs against all five deployed APIs, not the V2X Information Service alone: 236 test cases, 201 passing under the suite's own seeded fixtures and 196 against a clean server. Timing, traffic rules, DNS rules and the radio-information API pass in full.

Two of the five suites do not run against an independent implementation as distributed; they arrive wired to a hosted instance and need their environment redirected first. Both the overrides and every residual are documented, including one defect of ours: the Location header omits a non-empty deployment API root.

Application mobility

MEC 021 §8 lands under /amsi/v1/: application mobility service registrations, mobility-procedure and adjacent-application subscriptions with notifications, and adjacent-instance queries. This is the handover layer for a vehicle crossing between edge zones without dropping its session.

Fifth ETSI service, completing the V2X-relevant MEC platform alongside the V2X Information Service, Location, RNIS and App Support.

Application support API

MEC 011 §7 lands under /mec_app_support/v2/: application lifecycle (confirm-ready, confirm-termination), traffic and DNS rules, timing, registrations, and app-termination subscriptions. Forty-five of forty-five test cases pass against the official ETSI MEC 032-3 suite.

Fourth ETSI service alongside the V2X Information Service, Location and RNIS. This is the platform a V2X application registers on and runs within.

Live on the public edge

Talaia is deployed at mec.skyv2x.com behind TLS, with the conformance verdict and operational status published live. The container serves the full MEC surface; the broker and store stay internal.

Messages on the wire

The publish path distributes V2X messages to the MQTT v5 broker on the Annex A topic, with ASN.1 UPER validation in line. A Local Dynamic Map (ETSI EN 302 895) indexes received messages by station, type and geographic cell, completing the server-side subscribe-to-notify that the spec defines.

Validated end to end with real traffic: a CAM generated by the facilities stack crosses the wire, is relayed to the broker, and is ingested into the map.

Location and radio information

MEC 013 Location (location/v3) and MEC 012 RNIS (rni/v2) join the V2X Information Service: UE and zone location lookups, and radio network information feeding QoS and handover. Both served from the SkyV2X testbed RAN.

Control plane on real ground

Dependency injection wired through every V2XIS resource; the platform swaps real adapters for mocks at boot. The Uu unicast provisioning serves data from the SkyV2X testbed cell (mcc/mnc 001/01, cellId 0x19B01, EARFCN 3350/21350, bw50, PCI 1. MBMS and PC5 remain declared mocks pending the real sources.)

The QoS task returns the spec-conformant qos.stream[].qosKpi[] shape with named KPIs and confidence. The distribution server discovery declares msgProtocol=2 for MQTT v5.

69 of 69 unit and contract tests pass. The ETSI MEC 032-3 Robot suite ported and runs against the platform, two of forty-seven tests green at the baseline. See the verdict.

The platform is on its feet

A FastAPI application factory, a lifespan hook, eight V2XIS resources stubbed under /vis/v2/. Data models pinned to the spec §6 types. Every CHOICE, every constraint, no shortcuts.

Error responses speak RFC 7807 ProblemDetails per ETSI GS MEC 009. The four required fields plus instance, content type application/problem+json, no exceptions. 52 contract tests assert the wire shape against the spec.

The knowledge base picked up the nine relevant MEC specs (003, 009, 011, 012, 013, 016, 021, 030, 033).