Traffic-management systems engineered for mixed road use, intermittent backhaul, constrained roadside power and the evidential duties of public authorities.
A road system is not made intelligent by sending every camera stream to a cloud dashboard. On a regional corridor, cellular backhaul may be expensive, variable or absent exactly when an incident matters. The operational boundary therefore starts at the roadside unit: frames are processed locally, only authorised events, signed evidence packages and aggregates are transmitted, and the site continues a defined local mode while disconnected.
The perception problem is also local. A useful taxonomy must distinguish the road users and objects that actually share East African carriageways: passenger cars, heavy goods vehicles, buses, matatus or minibus taxis, boda bodas and other motorcycles, bicycles, pedestrians, handcarts and livestock where the site requires them. Model acceptance is reported per class and operating condition. A single accuracy number can conceal failure on the smallest, most vulnerable or most frequently occluded classes.
The service joins perception to traffic operation. Depending on the mandate and approved scope, that can include adaptive signals and corridor coordination, queue and incident detection, wrong-way or stopped-vehicle alerts, public-transport priority, weigh-in-motion, overload workflow, toll reconciliation, travel-time analytics and road-asset condition monitoring. It does not transfer enforcement power to a supplier: the responsible authority owns policy, review, penalty, appeal and legal-metrology decisions.
Six connected capability areas cover perception, traffic control, evidence, freight and tolling, and the field infrastructure required to keep them operable.
Roadside units process video locally and transmit events, bounded evidence and aggregates instead of continuous streams.
The runtime is profiled on the target device, given an explicit latency and energy budget, and designed to retain authorised local behaviour when backhaul is lost.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Edge perception & local inferenceDataset and acceptance design for boda bodas, matatus, freight, pedestrians, handcarts and livestock in difficult local scenes.
Class definitions, local collection, annotation quality and field validation are designed around the road users that affect the operational decision—not a borrowed benchmark.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Mixed-traffic model engineeringAdaptive signals, corridor coordination, incident alerts and public-transport priority connected to an accountable operator workflow.
Perception becomes useful when it leads to a bounded, reviewable action. Control integrates safe signal plans, queue state, incident evidence, priorities and source-health context.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Traffic operations & corridor controlTamper-evident capture, calibration references, human review and appeal material without transferring enforcement authority to the vendor.
Evidence is packaged and governed from edge capture through review, issue, disclosure and challenge. The mandated agency retains every consequential decision.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Evidential enforcement supportWeigh-in-motion, overload workflow, toll transaction reconciliation and road-condition observations with explicit exceptions.
Freight and revenue systems are designed around measurement provenance, exemptions, failed reads, duplicated events and reconciliation—not a perfect happy path.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Freight, tolling & road assetsPower, thermal, physical-security, networking and maintenance design for cabinets that must survive outside the data centre.
The site is operated as a distributed production node: its energy, temperature, tamper state, software, keys, spares and safe maintenance procedures remain visible.
Acceptance boundary: Targets, authority roles and evidence obligations are confirmed for the site; no performance or compliance result is implied by this capability description.
Scope Resilient roadside operationsThe values below are configurable design ranges or authority-set inputs. Acceptance values require representative traffic, device, power, link and evidence assumptions.
Every named road, junction, corridor and border post below is an illustrative context only. None is a Wavelink installation, client or contract reference.
As public-geography examples only, the Jinja Road approach to Nakawa, the Clock Tower and Queen’s Way area, Kibuye and Bwaise illustrate short headways, boda boda filtering, pedestrian movement, minibus stopping and occlusion that a mixed-traffic taxonomy must handle. These names are design context, not Wavelink installation references.
A hypothetical coordination study could compare conditions on Entebbe Road, Bombo Road, Kira Road, Gayaza Road, Hoima Road and Masaka Road, while treating every junction survey, signal plan and authority decision as site-specific. No deployment, commission or proposal on those roads is asserted.
The Kampala Northern Bypass and the public Kampala Flyover and junction-improvement context are useful illustrations of diverted flow, changing lane geometry, work-zone incident detection and the need to re-survey camera sightlines after civil change. This is public context only and does not identify Wavelink work.
For an illustrative architecture on the Northern Corridor from Mombasa through Malaba or Busia to Kampala and onward toward Kigali, or on Kampala–Jinja, Kampala–Gulu via Luweero and Karuma, and Kampala–Masaka–Mbarara, backhaul cost and access time make edge inference, buffer autonomy and remote health first-order decisions. The corridor names do not imply that Wavelink operates equipment on them.
The One Stop Border Posts at Malaba, Busia, Mutukula, Elegu, Katuna and Mirama Hills provide public examples for separating corridor sensing, weigh-in-motion screening, approved verification, customs or revenue interfaces and overload disposition. They are not presented as Wavelink sites, counterparties or contracts.
Uganda’s Kampala–Entebbe Expressway is used here only as the public reference case for discussing lane or gantry siting, plaza-to-free-flow design choices, exemptions, passage-to-payment reconciliation and dispute evidence. The example neither claims a Wavelink system there nor claims that the expressway currently operates free-flow tolling.
A Ugandan site survey should explicitly record murram-shoulder dust, long wet-season rain, unlit rural sections, headlight glare, vegetation growth across sightlines, grid instability and dense boda boda movement in Kampala’s core. These are design conditions to verify at each candidate site, not reported conditions from a Wavelink deployment.
Select a context to inspect its capability cards, power and backhaul posture, evidence class, retention boundary and responsible authority.
Dense mixed flow needs lane, turning, pedestrian, motorcycle and public-transport state at junction timescales, with a fixed safe plan available when sensing or coordination is unavailable.
Queue and arrival estimates feed authority-approved phase plans, coordination offsets and spillback protection without allowing a model to bypass controller safety constraints.
Stopped vehicles, blocked lanes, wrong-way movement, abnormal queue growth and vulnerable-road-user conflicts enter an owned operator workflow with source-health context.
Authorised priority requests are bounded by lateness, occupancy or service policy, pedestrian timing and maximum disruption to conflicting approaches.
The labels show public road geography for a design discussion only. They do not mark an installed, contracted or proposed Wavelink system.
Long sites and weak backhaul favour local incident decisions, compact corridor aggregates and explicit catch-up behaviour instead of central dependency on continuous video.
Stopped vehicles, wrong-way movement, debris candidates and abnormal flow changes are detected locally and sent with a small evidence package and location confidence.
Purpose-limited observations are converted to corridor travel-time and movement aggregates, with identifier separation, minimum cohort rules and bounded retention.
Surface, marking, sign, drainage or vegetation observations create maintenance candidates with source, time and review state rather than silently updating the asset register.
This is a public-geography illustration of a long-backhaul design context, not a representation of a Wavelink deployment or client.
Measurement, capture, review and challenge must remain one evidence chain while the technical supplier remains outside the authority to approve or issue a penalty.
A measurement observation links to device identity, timestamp quality, calibration reference, scene evidence and rule version before entering human review.
Screening observations route vehicles according to the approved measurement and inspection procedure, retaining the relationship between sensor, static verification and disposition.
The case workflow exposes uncertainty, reviewer identity, reason, disclosure history and a controlled package for the documented appeal path.
The map anatomy illustrates movement through an enforcement workflow only; it contains no real installation pin, client or operational site.
Lane observations, vehicle class, plate or account match, exemptions, payment, settlement and disputes form one reconciled state machine whether capture is plaza-based or free-flow.
Authenticated lane devices create a signed passage event, with plate or tag confidence and a bounded evidence package where the approved scheme requires it.
Passage, class, account, payment, exemption and settlement records reconcile through stable references and control totals, with duplicated or missing states exposed.
Eligibility and exemption decisions follow the approved scheme. Corrections append a reason and authority instead of overwriting the original passage or financial record.
The Kampala–Entebbe Expressway is used only as Uganda’s public tolled-expressway context for discussing plaza and potential free-flow system boundaries. No Wavelink deployment, contract or free-flow installation is asserted.
The stepper shows the complete delivery sequence; the initial value marks the starting gate rather than project status.
Video is reduced to authorised events, signed evidence and aggregates at the edge. Local buffers preserve priority and provenance; the regional platform coordinates recovery, observability and controlled model delivery.
Cloud capacity is useful for fleet coordination, analytics and model operations. It is not a substitute for bounded local behaviour on a road whose backhaul and power can fail independently.
Inspect distributed-cloud patternsThe meters are example design parameters. The histogram is a synthetic diurnal shape and contains no observed road data.
Example design setting only. Site acceptance must measure the approved decision zone and record occlusion; this is not project performance.
Example configuration only. Every class and condition receives its own reviewed threshold; this is not achieved model confidence.
The bars demonstrate the existing histogram anatomy for a morning rise, midday reduction and evening rise. Values are synthetic shape inputs, not traffic counts, forecasts or measured performance.
Data classes, legal purpose, evidence custody, measurement obligations and authority roles are confirmed before an operational or enforcement workflow is enabled.
These are public institutional roles, not claims of a Wavelink relationship, approval, contract or deployment.
Current policy, standards, transport regulation and national-road functions are mapped to the Ministry. Following government rationalisation, the Ministry states that it has taken on national-road development, maintenance and vehicle-weighing functions formerly performed by UNRA.
Existing estate documents, identifiers, permits or systems may still carry Uganda National Roads Authority naming. They are treated as transition interfaces whose current custodian must be confirmed, not as proof that UNRA remains the contracting or enforcement authority.
Kampala city traffic organisation and management, urban-road operations and the traffic-control operating model are scoped with the Authority within its jurisdiction.
Traffic-law enforcement and road-safety operations remain with the Police Directorate. Technical alerts or evidence are inputs to its authorised procedures; the supplier cannot issue a penalty or direct an enforcement action.
Revenue and customs interfaces are limited to the confirmed tax, customs, account or payment purpose. Toll settlement and border workflow do not grant the road platform general access to tax or customs records.
NTSA’s road-transport safety, vehicle, inspection and public-service-vehicle responsibilities are separated from the road authority, concessionaire or operator responsible for a specific expressway and toll back office.
National trunk and regional road development and maintenance interfaces are scoped with TANROADS, while traffic enforcement, transport licensing, toll collection and revenue roles are confirmed separately for the use case.
RURA regulates transport of persons and goods, including service licensing, routes, service levels and operator compliance. Road-infrastructure ownership and police enforcement are separate interfaces.
The neutral placeholders below are deliberately non-asserting. Public road context elsewhere on this page is not evidence of this engagement.
TODO_VERIFY: Client-approved neutral summary required. Until supplied, this block makes no deployment, pilot, contract or outcome claim.
All links below resolve to existing routes; the Smart Roads route itself is registered by this specification.
Store-and-forward transfer, regional recovery, durable queues and observable partitions.
OpenFlow forecasting, governed model lifecycle, per-class evaluation and drift decisions.
OpenControl-room roles, event freshness, source-silence signals, evidence drill-down and extraction feeds.
OpenDevice identity, key custody, signed artefacts, network segmentation and security telemetry.
OpenCase, appeal, payment, reconciliation, permissions and authority workflows.
OpenCorridor, freight, border, fleet and field-connectivity context.
OpenMandate, public records, accountable decisions and accessible review.
OpenExisting operator status, map, stepper, evidence and exception-workflow anatomy.
OpenStore-and-forward delivery, compact synchronisation and explicit offline states.
OpenDurable receipt, backpressure, replay and idempotent downstream processing.
OpenFreshness, source silence, backlog and user-visible service objectives.
OpenConsistency, partitions and recovery choices across sites and regions.
OpenFor public-sector procurement, the technical schedule should make authority, evidence, calibration, data, support and acceptance boundaries inspectable.
Review acquisition informationThe service is framed around failure, ownership and decision constraints before a stack or delivery topology is selected.
Continuous upstream video consumes costly capacity and makes detection dependent on a link outside the roadside team’s control. Local inference, event-first transfer, bounded evidence queues and store-and-forward recovery keep the operational path useful during a partition.
Models trained mainly on European or North American road scenes can collapse motorcycles into background clutter, merge minibuses with larger buses, or miss pedestrians and handcarts under dense occlusion. The remedy is a locally governed taxonomy, representative data and per-class acceptance evidence.
Higher inference load draws more energy and produces more cabinet heat. Grid instability, solar yield, battery autonomy, thermal throttling, lightning and surge exposure must be modelled together rather than delegated to a late electrical drawing.
A stopped-vehicle alert is useful only when it identifies source, lane, age, confidence, corroborating frames and the operator expected to act. Dashboards must distinguish a quiet road from a silent source and keep acknowledgements, escalation and closure reasons.
An accurate detection is not automatically admissible evidence. Capture integrity, trusted time, signing keys, calibration records, operator review, chain of custody and appeal disclosure form one end-to-end system whose gaps become visible under challenge.
Number plates, faces and linked vehicle movements can identify people. Without purpose and retention boundaries, an operational lookup can become bulk movement surveillance. Collection, redaction, access, export and deletion controls must be designed per data class before capture begins.
Architecture decisions follow the consequences of failure and the evidence needed at handover.
Site discovery combines traffic engineering, civil and electrical survey, radio assessment, privacy mapping and maintainability review. The team records lane geometry, approach speeds, turning movements, occlusion sources, pedestrian desire lines, likely camera mounting points, sun angle, headlight direction, drainage, vegetation, dust, night lighting, grid behaviour, solar exposure, cabinet access and safe maintenance positions. A camera schedule states lens, field of view, mounting height, shutter and illumination assumptions rather than treating “camera coverage” as one requirement.
Perception design begins with the decision the system must support. Class definitions include inclusion and exclusion rules, difficult examples and the consequence of a miss or false alert. Local data is sampled across day, night, rain, dust, glare, congestion and free flow; labels pass documented quality review; and train, validation and field-acceptance sets are separated by site and time to reduce leakage. Reports show precision, recall, confusion and false-alert behaviour by class, condition and site, with an explicit review queue for uncertain cases.
The edge runtime is sized to a declared inference budget. Candidate models are profiled on the target accelerator, then pruned or quantised only after the team checks which classes lose performance. Frame sampling, region-of-interest processing and staged models can trade compute for decision latency. Model artefacts are signed, versioned and deployed over the air through a canary group, with compatibility checks, health signals and automatic or operator-approved rollback to the last accepted version.
Disconnected behaviour is a first-class state. The unit continues authorised local detection, ranks evidence by consequence and expiry, stores manifests separately from media, and exposes buffer pressure. A sizing model accounts for event rate, evidence-package size, retransmission and reserved headroom. On link recovery, critical evidence and control messages move before analytical aggregates; acknowledgements are durable; duplicates are safe; and operators can see the oldest unsynchronised item at each site.
Physical resilience is designed against the actual envelope. The power budget includes cameras, illuminators, compute, communications, cabinet cooling and battery conversion losses across expected operating modes. Solar and battery options are sized to the approved autonomy case. Thermal design considers solar gain and dust-clogged airflow. Surge protection, earthing, tamper sensing, secure fixings, replaceable modules and an access log treat lightning, theft, vandalism and vegetation growth as routine engineering constraints.
For any enforcement use, the system creates an evidence object rather than a screenshot. A capture hash, device identity, signed manifest, timestamp quality, model or rule version, calibration reference and custody events travel together. An authorised operator reviews the evidence before a penalty is issued, and the back office preserves the material needed for a documented challenge or appeal. The mandated authority—not Wavelink or another supplier—sets the offence policy, approves enforcement, determines disclosure and decides the case.
These are working options, not a mandatory product list. Selection follows client constraints, existing skills and support ownership.
Each phase leaves an inspectable output and a clearer operating decision for the next stage.
Observe traffic, sightlines, civil constraints, power, backhaul, safety, privacy and maintenance access.
Set taxonomy, camera and sensor schedule, edge budget, power envelope, network zones and evidence boundary.
Exercise representative sites, failure modes and operator workflows before estate-wide assumptions harden.
Review difficult local scenes, rebalance classes, profile constrained devices and retest every affected condition.
Commission in controlled waves with site acceptance, calibration references, inventory and operator readiness.
Maintain fields of view, power and clocks; watch model drift; replace spares; and recalibrate after relevant change.
The implementation is accompanied by the evidence and operating material needed to own it.
External dependencies, service ownership and recovery behaviour are part of the design—not post-launch additions.
Roadside systems integrate through explicit trust zones. Cameras and sensors do not receive a general route into the enterprise network. Each roadside unit has a provisioned identity, short-lived or rotated credentials, restricted outbound paths and a recorded software and model inventory. Key use, update approval and device replacement are auditable; a compromised unit can be isolated without disabling the complete corridor.
Traffic-control interfaces preserve the controller’s safety boundary. Adaptive recommendations are bounded by approved phase plans, intergreen constraints, pedestrian timing and a safe fallback. Public-transport or BRT priority is a policy input with limits and conflict rules, not an unconstrained model objective. Commands, acknowledgements and controller state share stable identifiers so the control room can reconstruct what was requested and what physically occurred.
Freight and toll interfaces use reconciliation rather than optimistic success. Weigh-in-motion observations link to the approved weighing and inspection workflow without replacing legally required measurement or operator steps. Toll events retain lane, class, payment reference, exemption or exception state and back-office acknowledgement. Revenue, customs or registration lookups exchange only the confirmed fields and return explicit unavailable or ambiguous states.
The service connects to Wavelink’s distributed-cloud patterns for local buffering and regional recovery, predictive systems for flow forecasting and drift monitoring, intelligence dashboards for control-room views and source-silence signals, enterprise security for device identity and network segmentation, and managed services for field maintenance, service objectives and spares. Each interface remains independently observable and can degrade without silently rewriting traffic or evidence state.
Authority integration begins with mandate, not an organisation chart copied from an earlier project. Uganda’s current national-road functions, city traffic management, traffic-law enforcement and revenue or customs duties remain distinct. Regional designs likewise separate road infrastructure, transport regulation, enforcement and toll-operation roles in Kenya, Tanzania and Rwanda before data or command authority is assigned.
A control room watches event age, detection volume by class, queue depth, oldest unsynchronised evidence, source silence, camera obstruction, clock quality, storage pressure, thermal throttling, battery state, link state and failed update cohorts. Traffic measures are always paired with sensor-health measures so a flat line cannot be mistaken for a clear road.
Model operations use a signed registry and an acceptance ledger. A candidate records dataset version, label policy, device profile, quantisation, per-class results and known limits. Deployment starts with a bounded cohort. Drift review distinguishes changes in traffic mix, camera position, lighting, weather and model behaviour before deciding whether to relabel, recalibrate, retrain or roll back.
Field maintenance combines scheduled cleaning and vegetation checks with condition-triggered visits. A technician can see safe isolation steps, cabinet inventory, last configuration, calibration dependencies and queued evidence before replacing equipment. Removed storage and cryptographic material follow controlled handling; the replacement unit receives a new identity rather than inheriting unreviewed credentials.
Evidence operations preserve separation of duties. Device and model administrators cannot issue penalties merely because they maintain the technical system. Reviewers see the complete evidence and uncertainty flags. Corrections never overwrite the original object; they append a reasoned event. Appeal requests use a controlled export that records the requester, authority, disclosed material and time.
Capacity review joins power, compute, storage and network budgets. Adding a class or increasing frame rate can reduce battery autonomy, increase heat and consume the evidence buffer. Change approval therefore includes a renewed site profile and rollback condition, not only a model-quality report.
Targets are defined with a measurement method, operating boundary and validated workload assumptions.
Service objectives are set per operational path: roadside detection, local alert delivery, evidence persistence, central synchronisation, controller acknowledgement, control-room freshness and case export. A central dashboard can be unavailable while an edge unit still detects and buffers; conversely, a healthy dashboard can display stale data. The measurement contract reports those states separately.
Numeric latency, buffer, retention and availability values are design targets only after the authority confirms traffic conditions, decision consequence, evidence size, power autonomy, carrier service, operator coverage and recovery ownership. Targets state the clock boundary, percentile or completion rule, excluded maintenance and what happens when a dependency is outside the service boundary.
Field service objectives identify access constraints, spares location, safe-work conditions, response coordination and recalibration triggers. Restoration of connectivity is not the same as complete evidence synchronisation, and camera replacement is not complete until field of view, clock, signing identity and any applicable calibration relationship have been revalidated.
Move from the service model to concrete architecture decisions, illustrative scenarios and deeper technical analysis.
Existing control-room anatomy for status, source evidence, workflow and operator action.
View scenarioMovement, corridor, freight, border and field-connectivity operating context.
View scenarioMandate, accountable decisions, public records and accessible appeal paths.
View scenarioStore-and-forward delivery, compact synchronisation and explicit offline states.
Read paperDurable receipt, backpressure, replay and idempotent downstream processing.
Read paperFreshness, source silence, backlog and user-visible service objectives.
Read paperConsistency, partitions and recovery choices across sites and regions.
Read paper