One integration surface, not four.
Your app team wants to show a subscriber their WiFi. Between them and the answer sit an ACS, a topology store, and an optimisation engine — three APIs, three auth models, three failure modes. Edge Mobility collapses that into one.
A controller in the middle, an SDK at the edge.
Two components. The controller holds every credential and every backend quirk; the SDK gives the app one typed API and nothing else to think about.
-
Mobile app
Yours, or built by us. Talks only to the SDK.
-
Edge Mobility SDK
Domain-oriented API — auth, customer, cpe, wan, lan, wifi, task, maintenance. Zero runtime dependencies. Handles tokens, refresh, retry and task polling so the app doesn't.
-
Edge Controller
Versioned REST API with consistent JSON envelopes and typed error codes. Verifies CPE ownership on every request, translates to the backend calls, enriches responses.
-
Operator backends
Axiros Axess for TR-069 device management, AXTRACT for topology and WiFi analytics, AXWIFI for optimisation. Swappable behind a driver interface.
What an app can do through it.
Every capability below depends on the corresponding logic existing on your ACS. Where it doesn't yet, implementing it is scoped work — see dependencies.
Device
CPE inventory, status, uptime, firmware, model and MAC. Reboot and factory reset, both asynchronous and task-tracked.
Connectivity
WAN status — connection type, IP, subnet, gateway, DNS, uptime. VoIP line registration. Bandwidth tests with async start and result polling: download, upload, latency, packet loss.
LAN & WiFi
Paginated LAN host inventory with active state. WiFi networks per band, SSID and password update, radio restart. Connected clients with RSSI, band, SSID and IP.
WiFi quality
Per-band report: coverage score, neighbour count, channel, channel utilisation, interference level. Optimisation trigger per band. Wired and wireless topology tree from AXTRACT.
Enrichment
MAC vendor (OUI) lookup with Redis caching, applied to LAN hosts and WiFi clients — so a list of MAC addresses becomes a list of recognisable devices.
Customer
Profile read and update, multi-account support, scheduled maintenance window listing.
The part your app team actually touches.
Sessions handled for you
Pluggable token storage with in-memory and secure Keychain/Keystore implementations included. Automatic token refresh and request retry on 401, auto-clear on refresh failure.
Long operations awaited
Built-in task polling with exponential backoff — 2s to 10s, two-minute timeout. Reboot, factory reset, WiFi restart, optimise and bandwidth tests can each be awaited with a single flag.
Errors you can branch on
Typed error model: Authentication, SessionExpired, Forbidden, NotFound, Validation with field-level detail, DeviceOffline, DeviceBusy, Server, Network. No string parsing.
No dependency drag
Zero runtime dependencies; secure storage is an optional peer dependency. Configurable base URL, request timeout, optional request logging, per-request cancellation.
Built to be run, not just installed.
Observability
Prometheus endpoint with per-route request counters and latency histograms, plus backend call metrics. Grafana dashboards, MySQL and Redis exporters, all pre-provisioned.
Deployment
Single-command Docker Compose stack: Traefik with automatic Let's Encrypt TLS, MySQL, Redis, Prometheus, Grafana. Optional VPN/SSH-tunnel profile for reaching backends over a private network.
Security
Per-request CPE ownership verification — a customer reaches only their own devices. Service-account credentials to the ACS never leave the controller. Authentication is fitted to what you already run.
Documentation & tests
Auto-generated OpenAPI documentation. Feature and integration test suites (PHPUnit). A mock ACS driver runs the whole stack with no backend attached, for demos and app development.
What it needs from your side.
Edge Mobility exposes CPE management logic; it does not invent it. If a capability isn't implemented on your ACS, it isn't available through the SDK until it is — DHCP settings management, for example, has to exist on the ACS first.
- ACS capability. Each feature maps to logic on the ACS. Where that logic is missing, adding it is scoped work.
- Data models. Axess and AXTRACT APIs may need endpoint additions or adjustments for your specific CPE models and schemas.
- Authentication. An open integration point: provided by you, or developed to your requirements.
- Network reachability. The controller needs a path to your backends — direct, or over the bundled VPN/SSH-tunnel profile.
How it is licensed.
Installation
A one-off charge for installing and integrating the controller against your backends.
Annual licence
Based on the number of managed CPEs, covering both the controller and the SDK.
App development
Costed separately. Use the SDK with your own team, or have us build the app.
Proof of concept
A PoC can be evaluated and deployed at relatively low cost, using the mock driver or a limited slice of your live estate.
Ask for a quote with your managed-CPE count and we will size it.
See it running against a mock ACS.
No backend access needed for the first conversation — the stack ships with a mock driver that presents the identical API surface.