AI-RAN and Open RAN
Interoperability testing
Pairwise testing of radio units and distributed units from different suppliers.
We integrate and support.
O-RAN WG4 Interoperability Test Specification · O-RAN WG5 specifications
Multi-vendor integration: radios, compute and sensors from different makers speaking one protocol. The loop, step by step: 1. Radio, compute and three sensors from different vendors. 2. The chain from source to console stands ready. 3. Each sensor speaks its own protocol. 4. Each reading is stamped with time and place. 5. Adapters translate each into one record. 6. The relay forwards sealed packets untouched. 7. The edge verifies every signature first. 8. The edge checks every record against one schema. 9. Only a confirmed result leaves the edge. 10. A vendor ships a firmware update. 11. The adapter absorbs the change without a break. 12. Sensors check that the response worked. 13. The operator sees one consistent stream. 14. The alert arrives with its evidence attached. 15. The whole chain is archived for audit. 16. Everything settles back to idle.
01 / 16
Radio, compute and three sensors from different vendors
Nexus Observatory/
Design and integration/
Multi-vendor integrationMany suppliers, one interface contract.
Multi-vendor integration, inside Design and integration: interoperability testing, end-to-end performance testing, model-driven management, streaming telemetry and flow export and more. Every item is traced to its specification, from O-RAN WG4 Interoperability Test Specification to O-RAN WG5 specifications, and runs on the open Observatory Protocol.
Plan with usArchitectureThe protocol- Technologies
- 6
- At the frontier
- 0
- Protocol functions
- 4 of 12
- Industries served
- 4
At a glance
Interoperability testing
Pairwise testing of radio units and distributed units from different suppliers. In multi-vendor integration, part of Design and integration, the testing, integration and security layer holds interoperability testing, drawn against O-RAN WG4 Interoperability Test Specification and O-RAN WG5 specifications and used beside asset administration shell on the same sites.
Tatizo
Many suppliers, one interface contract
Large observing programmes buy from many suppliers. Without one design and one interface contract, every boundary becomes a dispute and every site a one-off. Programmes slip at the interfaces, not in the components, and nobody can say where the delay comes from.
Key facts
- Specification
- O-RAN WG4 Interoperability Test Specification · O-RAN WG5 specifications
- Specification
- OpenConfig gNMI specification · IETF RFC 7011 (IPFIX)
- Specification
- IEC 62541 series · OPC UA companion specifications
- Specification
- O-RAN End-to-End Test Specification · 3GPP TS 28.552
- Specification
- IETF RFC 7950 (YANG 1.1) · IETF RFC 6241 (NETCONF)
Components
- Small props, switch panel, nameplate and noticeboard
- Overhead line sensor on a distribution span
- Automatic weather station (AWS) to WMO siting practice
- Distribution pole transformer and meter cabinet
- Private LTE mast on a solar skid
- “AI tower in a box”
- Data hall row pair with cold-aisle containment
- Operations console with a video wall
Interfaces
- Radio
- Ethernet · LoRaWAN
Where it works
- Streaming telemetry and flow export
- End-to-end performance testing
In the story below
- The system, part by part
- Assembly
- Installation
- Deployment
- Connections
- Operation
- Failure and recovery
- Scale and federation
- What you get
Scenes · 13
Next steps
Plan a deploymentOpen the Field Deployment StudioSee Design and integrationTalk to salesDesign and integration · Multi-vendor integration
Many suppliers, one interface contract
Large observing programmes buy from many suppliers. Without one design and one interface contract, every boundary becomes a dispute and every site a one-off. Programmes slip at the interfaces, not in the components, and nobody can say where the delay comes from.
What it does
Interoperability testing
Pairwise testing of radio units and distributed units from different suppliers. In multi-vendor integration, part of Design and integration, the testing, integration and security layer holds interoperability testing, drawn against O-RAN WG4 Interoperability Test Specification and O-RAN WG5 specifications and used beside asset administration shell on the same sites.
- Specification
- O-RAN WG4 Interoperability Test Specification · O-RAN WG5 specifications
Network automation and intent
Streaming telemetry and flow export
Push-based state and flow data that replace slow polling. In multi-vendor integration, part of Design and integration, the network automation and intent layer holds streaming telemetry and flow export, drawn against OpenConfig gNMI specification and IETF RFC 7011. We build it into every site for multi-vendor integration against that standard, and keep its version and its test results on the site’s record.
- Specification
- OpenConfig gNMI specification · IETF RFC 7011 (IPFIX)
Open standards and interoperability
OPC UA information models
Industrial information models and companion specifications for equipment data. In multi-vendor integration, part of Design and integration, the open standards and interoperability layer holds OPC UA information models, drawn against IEC 62541 series and OPC UA companion specifications. We build it into every site for multi-vendor integration against that standard, and keep its version and its test results on the site’s record.
- Specification
- IEC 62541 series · OPC UA companion specifications
Testing, integration and security
End-to-end performance testing
Throughput, latency, mobility and application-level tests on a full RAN and core chain. In multi-vendor integration, part of Design and integration, the testing, integration and security layer holds end-to-end performance testing, drawn against O-RAN End-to-End Test Specification and 3GPP TS 28.552.
- Specification
- O-RAN End-to-End Test Specification · 3GPP TS 28.552
Time and place
When and where, on every record
Every record made for multi-vendor integration carries its time, from a clock disciplined by satellite time or a PTP grandmaster, with the position and siting record of the station that made it. When time or position degrades, the record for multi-vendor integration says so, and every user downstream sees the same warning.
Network automation and intent
Model-driven management
YANG models with NETCONF and RESTCONF for repeatable, machine-checked configuration. In multi-vendor integration, part of Design and integration, the network automation and intent layer holds model-driven management, drawn against IETF RFC 7950 and IETF RFC 6241. We build it into every site for multi-vendor integration against that standard, and keep its version and its test results on the site’s record.
- Specification
- IETF RFC 7950 (YANG 1.1) · IETF RFC 6241 (NETCONF)
Imani
Proved before it is trusted
A node joins a network for multi-vendor integration only after its hardware root of trust answers an attestation challenge. Its keys stay in secure hardware, its software arrives signed and every record it makes for multi-vendor integration carries a signature, so anyone downstream can check where a value came from.
Ushahidi
Traced to its specifications
We trace each part of multi-vendor integration to its specification: O-RAN WG4 Interoperability Test Specification, O-RAN WG5 specifications and IETF RFC 7950. We keep the versions, configurations and test results of multi-vendor integration as signed records, so a buyer or an auditor can check what was delivered against what was specified.
- Viwango
- O-RAN WG4 Interoperability Test Specification · O-RAN WG5 specifications · IETF RFC 7950 · IETF RFC 6241
Taarifa mpya
Updates in rings, with rollback
Software and configuration reach a fleet for multi-vendor integration in rings: one canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave, and each node for multi-vendor integration returns to its last good release without a site visit.
How it scales
One base unit, repeated
A network for multi-vendor integration starts with one base node and the instruments it reads. A station adds power and radio, a site adds a relay and a fleet repeats the proven site, so capacity for multi-vendor integration grows by adding units, never by replacing what works.
What you get
Programmes, integration and management
The reference architecture and interface contracts are open. National observing network programmes, systems integration and programme management are contracted. Pricing follows the programme’s scale and phases, with one point of accountability from design to acceptance; the documentation, models and records stay yours at the end.
Talk to salesNext step
Multi-vendor integration, planned with you
Tell us the sites, the systems multi-vendor integration must work with and the outcome you need, with a map or a list of addresses if you have one. An engineer replies with a survey proposal, a design and a scope for multi-vendor integration, and the plan grows from one site to the network you need.
Plan a deploymentOpen the Field Deployment StudioSee Design and integration
More presentations
See it from every side.
Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.
All presentationsIn depth
ISIC section · ISIC O Public administration and defence; compulsory social securityUse case Utility grid-edge private LTE and wildfire weatherUse case Street flood observatoryUse case GBON gap-filler stationExplainers
Explainer · Government and public safety Government and public safetyWildfire cameras on real terrain, GBON station density, street-flood alert thresholds, CAP alerting with the authority in the loop and the radio horizon of a deployable cell.Explainer · Cities MijiHybrid air-quality calibration, street-flood and heat sensing, privacy-first traffic counts and the city-wide radio layer.Jukwaa Design and integrationMany suppliers, nobody accountableJukwaa Field servicesSites fail between contractorsStories
Story · Federation across agencies Many agencies, one pictureNo single agency observes everything it needs. Federation lets each keep its own systems and still share: common interfaces, common catalogues and common…Story · Resilient operations When the links failObserving systems matter most on the days infrastructure fails. Designing for that day means local autonomy, stored power, store-and-forward delivery and…Story · Airspace and drones A shared sky below 120 metresFlying beyond visual line of sight turns a drone from a camera on a stick into infrastructure. It needs a command link that holds, an identity others can…Places and networks
Guided tour · Guided 3D tour Open-pit mineGNSS slope monitors on the benches, a blast seismograph at the boundary and a private cell for the fleet, around a benched pit cut into the ground.Guided tour · Guided 3D tour Mountain valley siteA private 5G tower, an automatic weather station, a compact radar and a seismic vault on real alpine terrain, joined to an edge data centre that admits, times and publishes every…Guided tour · Guided 3D tour River basinWater-level gauges along a river valley floor, a weather station and an edge node: the red isoline is the ground that lies within a few metres of the lowest point of the reach.Network scene · NTN · Satellite Satellite direct to device in a mountain valleyWhere the valley cell cannot reach, phones on the pass road connect straight to a low-orbit satellite, which relays through its feeder link to a gateway.Network scene · Backhaul · Fresnel zone Microwave backhaul across a river valleyAn 18 GHz hop from the church tower to a mast on the far side of the flood plain: its first Fresnel zone, clearance over the town and trees, and what a new building in the path…Heritage observatories
Heritage observatory · United States · 1961 World-Wide Standardized Seismograph NetworkIn the early 1960s the United States put identical seismographs, calibrated the same way, in more than a hundred places around the world and published the records on film for…Heritage observatory · United States · 1921 Caltech Seismological LaboratoryA laboratory in Pasadena that gave earthquakes a number. The Richter magnitude scale of 1935 depended on one instrument type in many places, a lesson as relevant to networks today…Interactive tools
Interactive tool · Plan a site Field Deployment StudioTerrain, devices, coverage, viewshed, power and the best spot for a station, then a deployment request with the plan attached.01Ni nini
Testing, integration and security.
Disaggregated, software-defined and AI-assisted radio access: the O-RAN architecture and its open interfaces, 7.2x fronthaul, RAN intelligent controllers with xApps and rApps, SMO and O-Cloud, accelerated L1, shared GPU infrastructure for RAN and AI, AI/ML in the 3GPP air interface, energy saving, and the test and integration work that makes multi-supplier RAN deployable. The networks behind the radio: the 5G core and its functions, slicing and edge breakout, IMS voice and emergency calling, fronthaul, midhaul and backhaul over microwave, E-band, fibre, free-space optics and satellite, IP/MPLS and segment routing, IPv6, automation and intent, and the security that holds it together. How observations move from the edge into stores, catalogues and APIs with their provenance, licence and residency attached, and how they interoperate through open standards and the open Observatory Protocol. Each technology below carries what it is, what we do with it, and the standard it is drawn against.
AI-RAN and Open RAN
End-to-end performance testing
Throughput, latency, mobility and application-level tests on a full RAN and core chain.
We integrate and operate.
O-RAN End-to-End Test Specification · 3GPP TS 28.552
Core and transport networks
Model-driven management
YANG models with NETCONF and RESTCONF for repeatable, machine-checked configuration.
We design, integrate and operate.
IETF RFC 7950 (YANG 1.1) · IETF RFC 6241 (NETCONF) · IETF RFC 8040 (RESTCONF)
Core and transport networks
Streaming telemetry and flow export
Push-based state and flow data that replace slow polling.
We design, integrate and operate.
OpenConfig gNMI specification · IETF RFC 7011 (IPFIX)
Data, software and interoperability
OPC UA information models
Industrial information models and companion specifications for equipment data.
We design and integrate.
IEC 62541 series · OPC UA companion specifications
Data, software and interoperability
Asset administration shell
Standard digital representation of an industrial asset and its submodels.
We integrate.
IEC 63278-1 (asset administration shell structure)
02Architecture
Where it sits, and what it speaks.
Multi-vendor integration draws on the spectrum below; the highlighted layers carry this area, and the protocol functions it speaks are marked.
5G core functions
10
Network slicing, edge UPF and local breakout
8
IMS, voice and mission-critical services
6
Fronthaul, midhaul and backhaul
8
Fibre and optical transport
8
IP/MPLS, segment routing, SD-WAN and IPv6
8
Network automation and intent
7
Core security and resilience
5
Generation
9
Storage
9
Microgrids and distribution
9
Energy management and monitoring
7
Thermal design and ingress
8
Environmental and EMC testing
7
Lightning, grounding and structures
8
Safety and transport
7
01Jiunge Identity, attestation quote, signed policy.
02Admit Admitted for a stated scope, nothing wider.
03Eleza What, where, how and by whom, with calibration.
04Time One clock across the grid, with its error bound.
05Observe Every value with quality and provenance.
06Qualify Tested against the specification, state on record.
07Federate Signed exchange across grids and trust domains.
08Orchestrate Software and configuration by signed plan.
09Correct A correction marks what depends on it and publishes a new version.
10Exchange Products reach people and applications through versioned interfaces.
11Prove Signed proof receipts that an independent verifier can check.
12Exit and decommission An open exit path, and a record that closes.
03On the grid
Every site joins one observing grid.
The open networks on the grid today, over real relief and the geodesic cells we count them into. A site built here enrols into the same grid.
The observing grid
- Open instruments on the observing grid.
04In the field
Where this runs, sector by sector.
Deployment scenarios from the sector research that rely on multi-vendor integration.
Government and public safetyAlerting integration with the Common Alerting Protocol and cell broadcast
Software-heavy: sensor triggers feed an alert origination tool; the alert authority keeps every decision.Government and public safetyNational GBON surface and upper-air network
WMO-grade stations reporting through WIS 2.0, funded through the systematic-observations financing pathway.Communities and ruralInterim public-safety broadband where no national network exists
Private LTE or 5G for fire and medical services in territories without a national public-safety network.ScientificStream gauges
A low-cost tier beside national gauge networks.ScientificOcean and coastal low-cost buoy arrays
Satellite-backhauled wave buoys accepted in a national programme trial.Defence-adjacent (civil dual-use)Civil observatories supporting northern infrastructure
Weather and ionospheric observatories, communications and power at remote sites that surveillance programmes may share.05Open and enterprise
Open by default. Enterprise by contract.
The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.
Open, on the main site
- Reference architecture
- Interface contracts
Enterprise, on this site
- National observing network programmes
- Systems integration
- Programme management
06The rest of the line
Design and integration, area by area.
Design and integrationSystem design
Requirements to architecture, drawn against the standards.Design and integrationUhandisi
Design packs, bills of materials and drawings.Design and integrationProgramme delivery
Many sites, one plan and one schedule.Design and integrationAcceptance
Tested against the plan, signed off on evidence.Bring us the site.
Survey, design, deployment and operation for multi-vendor integration. The form names who receives your details.
Talk to usAsk for a quote