Research & Development

The hard problems behind cameras that reason.

Most of this industry assembles parts. We publish how the parts actually work: sensors, models, edge inference, plate science and ATMS architecture. This is the content moat behind Recon, GateGuard and EdgeTrack.

Topics

Seven briefs from the lab and the gantry.

Each card is a deep dive for buyers, SIs and technical evaluators who need more than a slogan.

Sensors

Global shutter vs rolling shutter

On a highway, the subject is moving. The sensor readout decides whether the plate is evidence or a smear.

Motion-smeared highway showing sequential rolling shutter distortion
Alternative

Rolling shutter

  • Lines of the frame are read sequentially
  • Fast vehicles, vibration and LED flicker warp geometry
  • Plates skew, characters bleed, IR lighting can stripe the image
  • Fine for parked cars and sidewalks
  • Risky for 80 to 180 km/h corridors
Sharp highway traffic showing whole-frame global shutter capture
Stellarview

Global shutter

  • The whole frame is exposed at once
  • Motion stays geometrically true
  • Recon uses a 2 MP global shutter sensor
  • Plate rectangles stay rectangular
  • OCR sees characters as they were on the metal
Models

Vision language models vs conventional analytics

Conventional analytics answer fixed questions. VLMs answer questions you have not hard-coded yet.

Fixed CCTV cameras representing closed-set video analytics
Conventional

Video analytics

  • Detectors and classifiers for a closed set
  • Wrong-way, stopped vehicle, helmet, seatbelt
  • Strong when the taxonomy is stable and training matches the site
  • Weak for open-ended, rare or unlabelled attribute queries
Natural-language search query over video for vision language models
Stellarview

Vision language models

  • Joint vision and language representations
  • Ask in natural language: truck with a festival sticker, orange turban, CNG badge
  • Structured events still run for tender line items
  • Search and investigation open up on the same camera

See AI Search on Recon

Architecture

Edge AI vs cloud AI

Latency, bandwidth, privacy and uptime decide where inference should live. Highways rarely forgive a round trip to a distant GPU.

Data center representing centralised cloud AI inference
Cloud-centric

Cloud AI

  • Raw or lightly compressed video goes upstream
  • Models run centrally for batch investigation and updates
  • Costly when every gantry streams continuously
  • Fragile when connectivity drops or milliseconds matter
On-device electronics representing edge AI at the camera
Stellarview

Edge-native AI

  • Models run on the camera or roadside unit
  • Events, evidence clips and metadata travel upstream
  • Bandwidth collapses and privacy improves
  • Local decisions survive WAN outages
Methodology

ANPR accuracy methodology

Accuracy is a published number, not a claim. How you measure it decides whether a tender number means anything in the rain at 2 a.m.

01

Define the population

State vehicle population, speed band, lane geometry, day vs night, weather and plate types. A lab set of clean plates is not a monsoon gantry at dusk.

02

Separate the metrics

Plate localisation, character recognition and end-to-end read are different numbers. Publish which one you mean. End-to-end read rate is what operators feel.

03

Hold out field data

Evaluate on held-out corridors and times of day. Retrain on leakage and you invent accuracy. Iterate on field telemetry and republish when the distribution shifts.

04

Report conditions

Day, night, rain, fog, glare and density move the number. A single headline without conditions is marketing. Segmented reporting is engineering.

05

Evidence package

A correct read without a usable evidence image is incomplete for enforcement. Methodology includes capture quality, not OCR alone.

06

Certification context

STQC, BIS and NATRAX pathways constrain how products are tested for Indian deployments.

Why STQC matters

Imaging

High-speed imaging

High-speed roads demand short exposure, enough light and a sensor that does not invent motion blur through readout.

Exposure vs light

Shorter exposure freezes motion but starves the sensor. Optics, IR illumination and global shutter must be co-designed so characters stay sharp without washing the plate.

Frame rate and concurrency

Recon is built to sustain high frame rate while running multiple analytics. High-speed imaging is useless if the pipeline drops frames when nine models are hot.

Radar and vision

Where speed enforcement combines radar and vision, imaging must keep the plate attachable to the measured vehicle under dense traffic. Timing and optics are systems work.

Field proof

NATRAX and corridor deployments are where high-speed claims meet asphalt. Lab benches do not vibrate like a gantry in crosswind.

Recon Global Shutter Camera

India

Indian plate challenges

India is not a cleaned European plate set. A stack that ignores local variation fails the first week on a real corridor.

  • Formats and fonts BH series, state codes, two-line layouts, non-standard fonts and handmade plates all appear in the same hour of traffic.
  • Condition and occlusion Dirt, bent plates, towbars, bike riders, stickers and decorative frames occlude characters. Models must tolerate partial evidence, not assume museum plates.
  • Language and glyphs Latin characters dominate many plates, but regional scripts and mixed markings still show up. Training and evaluation must include what the corridor actually shows.
  • Climate and lighting Monsoon glare, Himalayan fog, tropical heat haze and harsh IR at night change contrast. Illumination and exposure policy are part of plate science.
  • Proving ground thesis A platform proven across Indian density and weather transfers outward more easily than a platform proven only on tidy lanes.
  • VAHAN / NIC context Enforcement workflows often assume integration readiness. Plate read quality is upstream of any registry lookup.
Examples of Indian number plate formats and conditions: BH series, state codes, two-line layouts, handmade plates, dirty and bent plates, bike plates, decorative plates and stickers
Systems

ATMS architecture

Advanced Traffic Management Systems are not a single camera SKU. They are a layered system from gantry to command.

01

Sense

Edge cameras and sensors capture plates, classes, speeds and incidents with local context: lane role, thresholds, schedules.

02

Understand

On-camera models turn pixels into events. Deterministic detectors cover tender line items. VLMs extend search and explanation where needed.

03

Assemble evidence

Images, clips, timestamps, location and metadata form a package an operator or challan workflow can use.

04

Command

A corridor or city command layer aggregates health, events and proof across gantries. Operators prioritise and act without opening fifty video walls.

05

Integrate

Outputs feed ATMS software, enforcement back ends and partner systems through documented interfaces. ONVIF and registry integrations sit here when required.

06

Design as one

Optics, models and command schema must be designed together. Recon senses; VIDS / VSDS / ATCC / VIDES / MTES apply; EdgeTrack commands; AI Search investigates.

EdgeTrack command platform · VIDES suite

Talk to the team that builds the stack.

Whether you are writing an ATMS tender, evaluating ANPR methodology or scoping a corridor, we will walk through the engineering, not just the brochure.