An illustrative, standards-aligned architecture showing how network-assisted sensing may extend a vehicle's observation horizon in an occluded roadway scenario.
A US, right-hand-traffic, four-lane divided corridor (two lanes each direction). Both vehicles hold their own lane the entire time — the difference is timing. A parked van creates geometric occlusion no onboard sensor can see through, in any condition; the network-assisted vehicle corroborates the blind spot across two terrestrial nodes and eases off early and smoothly. The onboard-only vehicle has no external read and must wait for its own sensors to clear the occlusion — a wait that lengthens further when fog or low light also degrade onboard modalities.
3GPP TR 22.837, Clause 5.28 — "Vehicles Sensing for ADAS" (Release 19, finalized 2024).
The clause describes network-assisted sensing supporting a vehicle's ADAS earlier than onboard
perception alone — the terrestrial hand-off Steps 1–2 and 4–8 below demonstrate. Steps 3 and 5
illustrate a non-terrestrial network (NTN) continuity role, general to 3GPP Release 20 NTN
resilience/backhaul work (TR 22.870, approved TSG SA#111, March 2026) rather than a specific clause —
NTN is shown here providing resilient transport for an already-corroborating terrestrial event, not
resolving pedestrian-level detail directly. Clause 5.28 also names two existing terrestrial features —
V2X applications (PR 5.28.6-1) and Sidelink positioning (§5.28.5) — anchored here to
v2xsensing.com and sidelinksensing.com, shown as the vehicle's continuous broadcast layer
running alongside the sequential steps. Downstream implementers of clause-5.28-class ADAS features
typically include Tier-1 automotive suppliers alongside RAN vendors.
Citations current as of Aug 2026 — TR 22.837/TR 22.870 clause and version references should be re-checked against the controlled document before further distribution
LJP Asset Group LLC is not affiliated with, sponsored by, or endorsed by 3GPP, ETSI, 5GAA, the
AI-RAN Alliance, or any standards body or company referenced on this page. Use-case terminology is
referenced descriptively from publicly available 3GPP Technical Reports; no specification text is
reproduced. "3GPP" is a trademark of ETSI, registered for the benefit of its members and the 3GPP
Organizational Partners.
Why the Names Matter
Each domain below represents a stable architectural role, not a website the vehicle visits. The namespace can stay constant while the operational service, provider, API, or endpoint behind that role changes over time — sensing, transport, fusion, and the vehicle's decision continue to happen in the appropriate operational systems. The namespace is the identifier for the role, not a participant in the real-time decision loop: nothing below implies a vehicle waits on a domain lookup before braking.
Terrestrial ISACNTN / space relayDecision & vehicle actionNetwork vehicle — same lane, eases earlyOnboard-only vehicle — same lane, brakes lateV2X / Sidelink — always broadcasting
NETWORK-ASSISTED VEHICLE
Cruising — nominal
Detects via the corridor's network sensing + NTN resilience fabric — less dependent on optical visibility than camera-led perception. Vehicle-side V2X + Sidelink positioning (v2xsensing.com, sidelinksensing.com) broadcasts continuously — the network fabric is what turns that broadcast into an early, corroborated advisory. The fabric also covers the oncoming lane, not just this vehicle's own path.
ONBOARD-ONLY VEHICLE
Cruising — onboard sensors only
Baseline capability already on the vehicle — autonomousperception.ai (Onboard Perception Baseline).
EARLY-ADVISORY LEAD, THIS CONDITION0.6sillustrative — this animation's timeline, not a physical stopping-distance calculation
RUN COMPLETE — MODELED OUTCOME, THIS CONDITION
Network advisoryEARLIER, CORROBORATED
Onboard detectionLATER — OCCLUSION LIMITED
Modeled benefitADDITIONAL RESPONSE MARGIN
00:00 / 00:16
SENSING EVENT LEDGER · sensingexchange.com — provenance & authorized-use record (illustrative, not a price)
0 uses
STEP 01 — PERCEIVErfsensing.ai
Detect the Ambient Signal
Loading…
Scenario Narrative & Sources (Text Version)
The interactive corridor above shows this sequence in motion. This section is the same nine-step scenario in plain text, plus the vehicle-side layer that runs throughout — provided so the scenario and its sources are readable without running the animation.
Continuous, runs the whole time: Vehicle-side V2X + Sidelink positioning
(v2xsensing.com, sidelinksensing.com) —
3GPP TR 22.837 §5.28.6-1 and §5.28.5.
Detect an ambient signal — rfsensing.ai. As a vehicle approaches, a roadside sensing node reads reflections in the same 6G signal used for connectivity — radio sensing layered onto existing communications infrastructure, without dedicated radar hardware. Near a parked van, the node picks up an anomalous reflection: unconfirmed, not yet a hazard.
Network Sensing Fabric · ISAC Layer 1 anchor, consistent with 3GPP/ETSI ISG ISAC study material.
Reshape the signal around an obstruction — intelligentsurfaces.ai. The van blocks direct line-of-sight to the sidewalk beyond it. A network-controlled intelligent surface nearby reshapes the signal's propagation path — it alters propagation without operating as a conventional base station — returning a partial, still-unconfirmed reflection from behind the obstruction.
Network Sensing Fabric · RIS/ISAC anchor, ETSI ISG RIS vocabulary.
Keep the read from being lost — ntngateway.ai. Local terrestrial backhaul in this segment is degraded — congestion, a fiber fault, thin coverage. A non-terrestrial network gateway supplies resilient transport so the sensing read still reaches the fusion layer without dropping. NTN's role here is continuity, not detection — it does not resolve what's behind the van.
NTN Resilience Layer · illustrative of 3GPP Release 20 NTN resilience/backhaul work (TR 22.870) — a general area, not a specific clause citation.
A second terrestrial source reports in — networkasasensor.com. A second, independently-positioned roadside sensing node — or a cooperative V2X-equipped vehicle nearby — reports a reflection consistent with the first. Two independent terrestrial sources, not one, now describe the same anomaly.
Network Sensing Fabric · consistent with Nokia's public "network as a sensor" framing for distributed ISAC sensing.
Present one event, regardless of path — unifiedntn.com. Whether the corroborating read arrived over local terrestrial backhaul or the NTN continuity path, it needs to resolve to a single event record — not two, and not one lost because it happened to travel the NTN leg. unifiedntn.com's role is unifying that identity across transport paths, not reconciling sensor content itself.
NTN Resilience Layer · transport-path unification — one event identity, whether backhaul is terrestrial or NTN-assisted.
Triangulate a position — multistaticsensing.com. Multistatic triangulation across the corroborating nodes produces a high-confidence position and closing speed for the object — precise enough to support an early advisory, not just a general warning.
Network Sensing Fabric · multistatic positioning vocabulary, consistent with distributed radar/ISAC sensing literature.
Compute an early advisory — autonomoussensing.com. The AI-RAN decision layer scores the corroborated event and computes an early, gradual speed-reduction advisory — supporting a smoother, earlier response than onboard-only perception can provide on its own, without ever leaving its lane. Nearby, the onboard-only vehicle still has no read on the object at all.
Network Sensing Fabric · edge/RAN-local decision timing, consistent with AI-RAN Alliance latency-reduction goals.
Deliver the advisory to the vehicle — closedloopsensing.com. The advisory is delivered to the network-assisted vehicle's ADAS over a V2X interface, supporting a smooth, early deceleration rather than a last-second brake. In the adjacent lane, the onboard-only vehicle is now braking hard, reacting only once its own sensors finally have a clear view.
Network Sensing Fabric · alert delivery consistent with the V2X interface referenced in clause 5.28.
Record provenance and authorized use — sensingexchange.com. The event's provenance and timing advantage are recorded, along with which parties are authorized to consume the record downstream — the vehicle OEM's safety analytics, the road authority, the driver's insurer. A provenance record, not a hypothetical invoice.
Sensing Data Economy · GSMA / ETSI ISG ISAC commercial working groups; Next G Alliance data-exposure track.
Source: 3GPP TR 22.837, Clause 5.28, "Vehicles Sensing for ADAS" (Release 19, finalized 2024); 3GPP TR 22.870,
Study on 6G Use Cases and Service Requirements (Release 20, approved TSG SA#111, March 2026). Not affiliated
with, sponsored by, or endorsed by 3GPP, ETSI, 5GAA, the AI-RAN Alliance, or any standards body or company
referenced above.
What This Demonstrates
The corridor is not a proposed product architecture. It demonstrates how stable semantic namespaces can
organize distinct sensing, resilience, localization, decision, control, and provenance roles into an
interoperable reference model. A buyer can retain those canonical identities while implementing the
underlying capabilities with its own networks, APIs, vendors, policies, and operational systems.