Interlux™
Roadside sensing, edge processing and project-specific connectivity to support a better understanding of intersection activity.
Add context where roads and people meet.
Vehicles and road users do not share the same view of an intersection. Roadside sensing can add useful viewpoints and information about movement, objects and events. Interlux brings that sensing and processing layer closer to the roadway, with integration defined around the agency’s operational question and the installed infrastructure.
Sense the intersection
Plan sensor placement and coverage around approaches, turning movements, vulnerable road users and potential occlusions. Validate performance in representative conditions.
Process at the edge
Turn supported sensor inputs into information for traffic operations. Confirm the supplied sensors, compute, communications and software as a complete configuration.
Connect with clear boundaries
Define data exchange, controller interfaces and any V2X use case. Distinguish analytics, recommendations and approved control authority during engineering and acceptance.
Information from the roadside. Context for the network.
Interlux brings roadside observations and edge processing into intersection-level information. A project can evaluate how that information supports traffic analytics or a defined connected-vehicle use case.
The system design must identify the supplied sensors, computing, communications and receiving interfaces. Coverage and interoperability need validation for the actual intersection, road users and operating conditions.
See the U.S. deployment and validation context
LEOTEK is a member of NVIDIA Inception.
Test the use case in the real world.
LEOTEK’s Interlux deployment at Curiosity Lab provides a setting for real-world testing and validation in the U.S. smart-city ecosystem. Use the project to understand the deployment context, then establish evidence for your own intersection geometry, interfaces and operating conditions.
Define success before rollout.
Set the operational question, baseline and acceptance criteria. Include sensing quality, controller interfaces, communications, data handling, maintenance and recovery in the review.
Request current configuration-specific documents for environmental ratings, latency and detection performance.
Interlux FAQ
Evaluate roadside sensing, controller integration, V2X interoperability and the evidence needed for an intersection pilot.
System scope
How is Interlux different from replacing a conventional LED signal module?
An LED signal module provides a visible indication within a specified signal system. Interlux adds a roadside sensing and edge-processing layer for intersection information, traffic analytics and project-specific connected applications. A deployment may involve sensors, computing, communications, controller interfaces and management software. Define which layers are supplied and integrated; the Interlux name does not mean a lamp module alone performs traffic optimization or V2X communication.
Interlux Deployment at Curiosity LabCurrent Technical Documents
Can Interlux eliminate blind spots or guarantee detection of every road user?
Roadside sensing can add viewpoints that are unavailable to an individual vehicle, but it does not remove every occlusion or guarantee every detection. Coverage depends on sensor placement, geometry, weather, visibility, road-user classes and the operating configuration. A pilot should test representative approaches, turning movements and challenging conditions against agreed criteria. Document limitations and operational handling of incomplete or uncertain observations.
Integration and interoperability
Will Interlux work with our existing controller and cabinet?
Compatibility must be evaluated for the installed controller model, firmware, cabinet interfaces and the proposed data exchange. Document power, mounting, networking, timing responsibilities and the boundary between analytics and signal control. Test the planned integration in the agency’s approved process. A modular architecture is useful for planning, but it is not proof that every legacy controller, cabinet or protocol is supported.
Current Technical DocumentsInterlux Deployment at Curiosity Lab
What should a V2X interoperability review cover?
Identify the required use case, communications technology, message types and versions, timing, coverage, security responsibilities and compatible receiving systems. Decide how data quality and unavailable messages will be handled. Validate the proposed roadside-to-vehicle and platform interfaces with the relevant partners. A successful demonstration at one location does not establish interoperability with every vehicle, RSU, carrier or signal controller.
Does Interlux automatically take over safety-critical signal decisions?
Do not assume that analytics or a demonstration capability grants automatic control authority. State which functions provide information, which propose a strategy and which can change controller operation in the approved configuration. The traffic agency must define authorization, operating limits, monitoring, fallback and acceptance requirements. Any operational-control integration needs project-specific engineering and validation before it is relied on.
Interlux Deployment at Curiosity LabCurrent Technical Documents
Deployment and operations
How should an agency define an Interlux pilot?
Begin with a specific operational question, such as the quality of road-user classification or the usefulness of intersection-event information. Establish a baseline, representative conditions, ground-truth review method and acceptance criteria. Include controller and platform interfaces, communications loss, data quality and maintenance workflow. Agree on responsibilities and the observation period before the pilot starts so the results can support a rollout decision.
What should we ask about video, privacy and cybersecurity?
Ask what each sensor collects, whether raw observations or derived events are transmitted, where information is processed and stored, who can access it and how retention is configured. Request the security and support documentation for the complete proposed system. Do not infer a privacy guarantee, facial-recognition capability or certification from a general AI description. City policy and the documented deployment should govern data handling.
Smart Streetlight Cybersecurity ChecklistSmart-City Lighting Data: Contract Questions
Evidence and procurement
Does the Curiosity Lab deployment establish a universal performance specification?
No. The article describes Interlux deployment in a real-world smart-city environment for testing and validation. It supports the existence and context of that project. It does not replace model-specific evidence for detection accuracy, latency, environmental ratings, controller compatibility or regulatory acceptance. Request the current technical package and a validation plan that match your intersection and intended use.
Interlux Deployment at Curiosity LabCurrent Technical Documents
Start with the needs of your project.
Share your site, equipment and operating objectives with the LEOTEK team.
