KAOKAB Edge
Local intelligence. Controlled lifecycle.
KAOKAB Edge brings the private mobile runtime close to the site it serves, with a controlled path for installation, activation, validation, monitoring and recovery.
- Site-local runtime
- Validated activation
- Recovery-aware design
The site foundation
Built to operate where the network lives
The Edge hosts and connects the local functions required by the private network. Its operational lifecycle is handled as a transaction: candidate state is prepared, validated and committed only after the runtime proves healthy.
Deterministic deployment
Apply network and runtime changes in a defined, testable sequence instead of an improvised installation.
Health before commit
Validate essential services, sockets and RAN connectivity before accepting the new runtime state.
Independent recovery
Maintain a protected rollback path that does not depend on the mutable deployment checkout.
Controlled activation
Prepare. Validate. Activate. Prove.
The lifecycle separates candidate configuration from committed runtime state.
- 01
Prepare
Install candidate files and capture the previous operational baseline.
- 02
Validate
Check network configuration and required runtime contracts before activation.
- 03
Activate
Apply networking, forwarding, core services and the RAN in a defined order.
- 04
Commit
Accept the transaction only after health and connectivity checks pass.
Edge responsibilities
A focused runtime for the local service
Private core
Run the required mobile-core control and user-plane services near the site.
RAN integration
Coordinate the local radio access runtime and validate its core connectivity.
Network activation
Manage the intended host networking, forwarding and local data-path dependencies.
Runtime health
Verify the service set and expose the Edge state to authorised operations.
Transaction checkpoints
Preserve the baseline needed to reject or recover an incomplete activation.
Support path
Enable controlled remote diagnosis without making the Edge publicly reachable.
Resilient by design
The local service does not depend on a public webpage.
KAOKAB separates the public website, authenticated NOC and site-local Edge runtime. The Edge continues to serve its designed local function even when central management connectivity is interrupted.
Edge runtime
- Core and user-plane services
- RAN connectivity
- Local data path
- Health validation and rollback
Central operations
- Customer and inventory view
- License context
- Events and operational status
- Authorised remote support
KAOKAB
Build a repeatable Edge deployment.
Move from a one-off telecom installation to a controlled operational lifecycle.