Start with what the application actually claims, not the title. The failure mode Mobileye is fencing against in U.S. patent application US 2026/0168816 A1 — published June 18, 2026 and still pending — is one every camera-first driving stack quietly dreads: a multi-lane junction where several traffic lights are visible at once and the car has to know which light is talking to its lane. The independent claim is directed to a method of generating a crowd-sourced map for vehicle navigation in which at least one processor receives drive information collected from vehicles that traversed a junction, aggregates it to determine the positions of traffic lights and spline representations of the drivable paths, and feeds those positions and splines into a trained model that outputs a "traffic light relevancy mapping" — an indicator, for each traffic-light-to-drivable-path pair, of whether that light governs that path.

The claim does not stop at a static lookup. It recites inputting an observed vehicle behavior into the trained model to generate an updated relevancy mapping, storing those relevancy indicators in the crowd-sourced map, and transmitting the map to a vehicle for use in navigating the road segment. In plain terms, the claimed method watches how human and machine drivers actually treat each light at a junction, and uses that behavior to revise which light it tells future vehicles to obey. That is the limitation worth reading twice: the relevancy assignment is learned and behavior-corrected, not hand-labeled.

Systems and methods are provided for generating a crowd-sourced map for use in vehicle navigation. In one implementation, a system may include at least one processor configured to receive drive information collected from vehicles that traversed a junction; aggregate the received drive information to determine positions of traffic lights and spline representations for drivable paths; input the determined positions and the spline representations to a trained model configured to generate a traffic light relevancy mapping indicating a traffic light relevancy for traffic light to drivable path pairs of the junction.— Machine Learning-Based Traffic Light Relevancy Mapping, US 2026/0168816 A1

Where the claim lands in the patent landscape

The application carries the classifications G01C 21/3841 and G01C 21/3819 — both subclasses of G01C 21/38, the class for constructing or updating the map databases that navigation systems consume. That placement is itself a statement of intent. Mobileye is not claiming a perception sensor here; it is claiming the map layer that sits between perception and the driving decision. The relevancy mapping is map metadata — a learned attribute attached to each junction — rather than a real-time camera output, which is why the filing sits in the cartography class rather than the computer-vision class. For a company whose Road Experience Management (REM) crowd-sourced mapping is its signature asset, an independent claim directed to what the map encodes about traffic lights is consistent with where its disclosed work has been heading.

The classification choice also marks the camp line. Mapped-autonomy approaches encode the world's structure in advance and localize against it; the relevancy mapping is exactly that kind of pre-computed structure, distributed to the vehicle before it arrives at the junction. The claim's reliance on aggregated multi-vehicle drive information — rather than on a single vehicle's instantaneous perception — is the mapped-side answer to the traffic-light-association problem, and it is fenced here as a pending application, not a granted patent.

The cluster around it

The hero application does not arrive alone. This week's pub drop contains four Mobileye Vision Technologies applications, and read together they describe a coherent map-and-camera navigation stack rather than scattered ideas. US 2026/0168815 A1, "Estimation of Road Surface and Object Altitude," claims aggregating drive information from harvesting vehicles — including altitude associated with each road surface — to build a map that distinguishes multiple road surfaces at different altitudes, the kind of disambiguation a stacked-interchange junction demands. It shares the G01C 21/38 map-building lineage of the hero, extending the crowd-sourced map from two dimensions into vertical structure.

The other two reach from the map into the moment of driving. US 2026/0168807 A1, "Map With Sensing for 3D Object Detection and Drivable Paths for Detection of Occluded Objects," is directed to using a localized position plus three-dimensional topography from the map to derive 3D information about an object that appears in the camera image but is not represented in the map — the disclosed mechanism for handling the unmapped obstacle, the recurring edge case in mapped autonomy. It is classified across both the map-building class and computer-vision classes such as G06V 20/588, marking the seam where the prior map meets live perception. US 2026/0167225 A1, "Trained Network for Identifying Vehicle Paths," claims a host-vehicle system that runs a camera image through a trained model to identify two or more target trajectories per feature and selects a navigational action; it carries B60W 60/0011, the autonomous-driving control class, alongside the vision classes.

Mapped end to end, the cluster reads as: harvest drive data and build the map (815, 816), use that map plus the camera to reason about what is and is not on it (807), and convert the result into a trajectory and a navigational action (225). The two map-building applications share inventors and the G01C 21/38 spine; the perception-and-control pair pull in G06V computer-vision classes and the B60W driving-control class. The relevancy-mapping application is the one that fences the specific, legible problem — which light owns which lane — and it does so in the map layer where Mobileye's disclosed portfolio is concentrated.

Two cautions a claims reader should keep in view. First, all four are published applications, the A1 kind code — their independent-claim language is what was filed and examined to the publication point, not what has been allowed; the scope that ultimately issues, if any, can narrow during prosecution. Second, the relevancy-mapping claim's center of gravity is the learned, behavior-updated association between lights and paths; that limitation, not the broad "crowd-sourced map" framing, is what the independent claim is actually directed to. Read claim 1, watch the trained-model and observed-behavior elements, and the four-application cluster resolves into a single thesis about owning the map metadata that camera-first driving has to trust.