← Back to AcsFlow
(KB)
Knowledge base

The protocols behind AcsFlow — from CPE to backbone

From CPE management to backbone routing — the standards AcsFlow speaks, on the ACS side and the IPLANS side.

(01)
CPE management · ACS

Speaking to every customer device

Provisioning, firmware, diagnostics and real-time control of CPEs — TR-069 and USP.

TR-069 — session & eventsCWMP
ACS TR-069 / CWMP server CPE CWMP agent NAT / firewall Periodic Inform · Event 2 PERIODIC (polling) + Event 1 BOOT / 0 BOOTSTRAP at startup · Event 4 VALUE CHANGE Connection Request → CPE reports Event 6 XMPP · STUN NAT traversal · Annex K / G or HTTP direct (CR URL) Session HTTP(S) / SOAP — GetParameterValues · SetParameterValues · AddObject · Download · Reboot
USP — multi-controllerTR-369
Multiple Controllers Controller A ACS / OSS Controller B App / 3rd-party roles & permissions per controller MTP MQTT broker · WebSocket STOMP · CoAP USP Agent on CPE / Device Device:2 (TR-181) USP messages: Get · Set · Add · Delete · Operate · Notify · GetSupportedDM
01

TR-069 / CWMP

The classic broadband CPE WAN Management Protocol (Broadband Forum). SOAP/HTTP between an ACS and the CPE: auto-provisioning, firmware, diagnostics, connection requests. The workhorse of carrier CPE fleets.

02

USP / TR-369

The successor to TR-069. Multi-controller, microservice data model (Device:2), running over MQTT/STOMP/WebSocket/CoAP. Built for IoT-scale and real-time CPE control.

03

Transports

XMPP for NAT-traversed connection requests, plus MQTT, STOMP, WebSocket and CoAP as USP message transports (MTPs).

(02)
Routing · IPLANS

The backbone control plane

The IGPs that carry the core and the BGP that connects it to the world.

IGP + BGP topologyACTIVE
Internet / Peer AS eBGP Route Reflector RR P P PE PE IS-IS / OSPF — loopback reachability iBGP · VPNv4/VPNv6 AGG RAN backhaul 2G→5G · VRF/plane: User·Ctrl·Mgmt 2G3G4G5G BTS · 2MNodeB · 45MeNB · 600MgNB · 3G
01

OSPF

Open Shortest Path First — link-state IGP. Areas, LSAs, fast SPF convergence. OSPFv2 (IPv4) and OSPFv3 (IPv6).

02

IS-IS

Intermediate System to Intermediate System — link-state IGP favored in large SP cores. Level-1/Level-2 hierarchy, protocol-agnostic (TLVs), scales to thousands of nodes.

03

BGP

Border Gateway Protocol — the routing protocol of the Internet. eBGP/iBGP, address families (VPNv4/VPNv6, EVPN), route reflectors, policy with communities.

(03)
MPLS, transport & VPN · IPLANS

Label-switched services

MPLS and Segment Routing for transport; L3VPN, L2VPN and EVPN for customer services.

MPLS LSP / VPNLSP
Services: L3VPN (RFC 4364) · L2VPN (VPWS / VPLS) · EVPN-VXLAN LSP · transport label (LDP / RSVP-TE / SR) MP-BGP · VPNv4/VPNv6 — RD · RT · VPN label CE PE P PE CE VRF VRF PE–CE: eBGP / OSPF / static PHP (pop transport label) LSP VPN IP label stack
Transport
01

MPLS

Multiprotocol Label Switching — label-switched forwarding underpinning VPNs and traffic engineering.

02

LDP / RSVP-TE

Label distribution: LDP for hop-by-hop LSPs, RSVP-TE for explicit, bandwidth-aware traffic-engineered tunnels.

03

Segment Routing (SR-MPLS / SRv6)

Source routing with the SR-MPLS or SRv6 data plane — TE without per-flow state, programmable paths, fast reroute (TI-LFA).

VPN services
04

L3VPN (MPLS VPN)

RFC 4364: per-customer VRFs, VPNv4/VPNv6 with route-distinguishers and route-targets over MP-BGP. The backbone of enterprise services.

05

L2VPN — VPWS / VPLS

VPWS (point-to-point pseudowires) and VPLS (multipoint Ethernet) to extend L2 across the backbone.

06

EVPN-VXLAN

Ethernet VPN with a BGP control plane over MPLS or VXLAN — modern, active-active L2/L3 services for data center and metro.

(04)
Automation & telemetry · IPLANS

Model-driven config & telemetry

The foundation of IPLANS' transactional multi-vendor push and live weathermap.

01

NETCONF / YANG

Model-driven configuration over SSH with candidate/commit and rollback — the foundation of IPLANS' transactional, multi-vendor push.

02

gNMI / gRPC

Streaming telemetry and config over gRPC — subscribe to counters at sub-second cadence for the live weathermap and capacity dimensioning.

03

SNMP

Ubiquitous legacy monitoring (MIBs, traps) — still used for breadth of coverage across older gear.