TR-369 / USP integration for GenieACS

Keep GenieACS.
Add USP.

CPEBridge adds a production-focused TR-369 / USP management layer to existing GenieACS deployments. Keep your current TR-069 estate, provisions, firmware workflow and OSS/BSS integrations while introducing USP-capable CPE alongside it.

Request beta access View architecture

USP 1.5 MQTT 5 TR-181 GenieACS native + Docker

cpebridge-installer

$ sudo cpebridge install Detecting GenieACS... ✓ GenieACS 1.2.x detected ✓ Native systemd installation ✓ NBI reachable on :7557 ✓ FS reachable on :7567 ✓ MongoDB detected Pre-install checks... ✓ Configuration snapshot created ✓ MongoDB backup verified ✓ Existing UI customisations preserved Installing CPEBridge... ✓ USP controller online ✓ GenieACS adapter connected ✓ MQTT transport ready CPEBridge is ready.

Architecture

A second protocol path, not a replacement ACS.

CPEBridge sits alongside GenieACS. TR-069 devices remain on the existing CWMP path. USP agents are handled by CPEBridge and projected back into the management environment your team already uses.

Existing stack

CRM / OSS / BSS

↓

GenieACS UI + NBI

↓

genieacs-cwmp

↓

TR-069 CPE

CPEBridge layer

GenieACS Adapter

↓

Compatibility Gateway

↓

USP Controller

↓

Device Profiles + Event Engine

USP path

MQTT 5 / TLS

↓

USP Record + Protobuf

↓

TR-181 Data Model

↓

TR-369 / USP Agent

What it does

Designed around existing GenieACS operations.

The objective is not to introduce another isolated dashboard. CPEBridge is built around compatibility: device visibility, tasks, provisioning, firmware and automation should continue to fit the operational model already in place.

USP controller

Native TR-369 message handling with MQTT 5, Get, Set, Add, Delete, Operate, GetSupportedDM, subscriptions and notifications.

GenieACS device visibility

USP-only devices can be represented alongside TR-069 devices, with protocol, Endpoint ID, connectivity and TR-181 state exposed to operators.

Dual-protocol matching

Link CWMP and USP identities for the same physical CPE rather than creating duplicate devices when both protocols are active.

Provision compatibility

Translate compatible GenieACS provision intent into USP Get, Set, Add, Delete and Operate actions while retaining the existing JavaScript provisioning model.

Firmware workflow

Reuse GenieACS firmware inventory while CPEBridge handles USP download, activation, verification, staged rollouts and failure thresholds.

API compatibility

Provide a GenieACS-compatible API path so existing CRM, provisioning and support tooling can work across TR-069 and USP estates.

Real-time events

Use USP subscriptions and Notify messages for near-real-time parameter changes, boot events, operation completion and device state.

Device profiles

Model-specific behaviour for WAN, Wi-Fi, VoIP, firmware, diagnostics and vendor objects without forcing operators to hard-code every implementation quirk.

Safe install and rollback

Detect native or Docker installations, back up MongoDB and integration state, preserve custom UI configuration and maintain a reversible install manifest.

Compatibility

Keep the parts of GenieACS you already depend on.

Compatibility is assessed feature-by-feature. CPEBridge does not pretend every historic TR-098 or vendor-specific script can be translated automatically. Unsupported paths are surfaced clearly rather than silently guessed.

GenieACS capability	CPEBridge handling for USP	Status
Device list / TR-181 values	USP device projection + live state	Supported
Get / refreshObject	USP Get	Supported
setParameterValues	USP Set	Supported
Reboot / factory reset	USP Operate	Supported
AddObject / DeleteObject	USP Add / Delete	Supported
Provisions using TR-181 paths	Compatibility runtime	Compatibility checked
Presets / events	USP event translation + scheduler	Compatibility checked
Virtual Parameters	Executed against USP-backed values	Compatibility checked
Extensions via ext()	Controlled extension runner	Compatibility checked
Firmware files	Existing file source + USP download/activate	Supported
Legacy TR-098/vendor paths	Device profile translation where defined	Profile dependent

Deployment

Install beside the GenieACS deployment you already run.

CPEBridge detects how GenieACS is deployed and adapts its installation accordingly. The default behaviour is additive: no replacement binaries, no reset of existing UI configuration and no automatic rewrite of customer Compose files.

Native / systemd

Detect GenieACS services, environment files, ports, MongoDB, NBI, FS and reverse proxy configuration before installing CPEBridge as separate services.

$ sudo cpebridge install

✓ genieacs-cwmp
✓ genieacs-nbi
✓ genieacs-fs
✓ genieacs-ui
✓ MongoDB
✓ nginx

Installing without replacing GenieACS...

Docker / Compose

Discover the existing project, networks, mounts and environment. CPEBridge runs in its own stack and joins the existing Docker network where appropriate.

services:
  cpebridge:
    image: cpebridge/controller
    networks:
      - genieacs

networks:
  genieacs:
    external: true

Packages

Priced by managed USP estate.

All commercial plans include the controller, GenieACS integration, device profiles, software updates and the core management API. Larger deployments add scale, rollout controls and support options rather than locking basic protocol functions behind add-ons.

Plan	Community	Starter	ISP	ISP Plus	Carrier
Managed USP devices	100	1,000	5,000	25,000	100,000
Monthly	Free	£99	£249	£599	£1,199
TR-369 / USP controller	✓	✓	✓	✓	✓
GenieACS integration	✓	✓	✓	✓	✓
Device profiles	Core	Core	Full	Full	Full
Staged firmware rollout	-	Basic	✓	✓	✓
Priority support	Community	Email	Email	Priority	Carrier SLA
HA / clustering	-	-	Optional	✓	✓

Illustrative launch pricing. Prices shown exclude VAT. Enterprise deployments above 100,000 managed USP devices are quoted separately.

Operational design

Built for change control, not just protocol support.

Adding a new management protocol to an ISP estate is an operational change. CPEBridge treats backups, rollback, compatibility checks and version awareness as product features.

Pre-install backups

Configuration snapshots and MongoDB backup are taken before CPEBridge changes integration state.

Version-aware adapters

GenieACS versions are detected and integration is enabled only for known-compatible layouts and schemas.

Non-destructive UI changes

CPEBridge adds namespaced fields, status indicators and panels without resetting existing customised views.

Install manifest

Every resource created or changed is recorded, allowing CPEBridge to remove its own changes cleanly.

Protocol fallback

Dual-stack CPE can prefer USP while retaining CWMP fallback for supported actions if the USP path is unavailable.

Compatibility reporting

Existing provisions and automation can be scanned and classified before an operator enables them against USP devices.

FAQ

Common deployment questions.

Does CPEBridge replace GenieACS?

No. GenieACS remains responsible for its existing TR-069 estate. CPEBridge adds a separate USP management path and integration layer.

Can one router use both TR-069 and USP?

Yes. CPEBridge can link the CWMP identity and USP Endpoint ID and represent them as one physical CPE with separate protocol state.

Will existing provisions work?

Compatible TR-181-based provisions can be translated through the CPEBridge runtime. Legacy TR-098 and vendor-specific paths are reported and may require a device profile.

Does installation change our Docker Compose file?

Not by default. CPEBridge runs as a separate stack and can join the existing GenieACS network rather than rewriting the customer's Compose project.

What happens if CPEBridge is offline?

Your existing GenieACS TR-069 service continues operating. USP management pauses until the controller returns.

Can we use our own MQTT broker?

Yes. CPEBridge is designed to work with customer-managed MQTT infrastructure or an optional bundled broker deployment.

Early access

Running GenieACS and planning a move to USP?

We are looking for ISPs and network operators with real TR-369-capable CPE to participate in early compatibility testing. Tell us what you run today, which CPE vendors you deploy and what GenieACS workflows you need to preserve.

Request beta access Technical enquiry