5G Northbound

The reference implementation of the CAMARA private-asset profile: the location of assets in a private venue, such as tools, pallets and forklifts, served through the CAMARA Device Location APIs. Positions come from on-site sources such as WiFi, UWB or a vendor's positioning cloud, and are fused at the edge. The overview introduces the model and its terms.

Where to start

Goal	Pages
Understand the system	Overview, then Architecture
Run it on a laptop	the repository README
Build a CAMARA client	the profile, then Data contracts
Add a positioning source	Adapters, then Integrating a vendor REST API
Register assets	Asset registry
Describe a venue	Blueprint and bindings, then Georeferencing
Deploy on Kubernetes	Deployment

Documentation map

Each topic has one page that owns it. The other pages link to it and do not restate it.

Topic	Owner
The model and its terms	Overview
Services, request flow, coordinate frame, time	Architecture
The private-asset profile: identity, extensions, authorisation, conformance	Profile
Endpoints beside CAMARA, diagnostics vocabulary	Profile extensions
Browser sign-in	Authentication
The adapter contract, declarations, writing an adapter	Adapters
The schema-driven vendor adapter	Integrating a vendor REST API
Adapter registration, health and routing	Adapter registry
The asset map and onboarding	Asset registry
Venue blueprint, WiFi bindings and calibration	Blueprint and bindings
Tie between the venue frame and WGS84	Georeferencing
Fusion in the engine and the gateway	Fusion strategies
Images, configuration, storage, probes	Deployment
Published contract files, surface governance, naming	Machine-readable contracts
An example of every body	Data contracts
Every route of every service	API reference
Per-hop latency log	Latency instrumentation
Environment contract format	deploy/contracts
Code conventions and commits	AGENTS.md at the repository root
Repository layout	STRUCTURE.md at the repository root

The Kubernetes manifests of the testbed are in the KELT repository.