Open standards end to end — scored openly.
Netxol One speaks the protocols you already run: TR-069 CWMP and TR-369 USP for customer routers and ONTs, RADIUS with RadSec and RADIUS/1.1 (RFC 9765) for subscribers, NETCONF, RESTCONF and gNMI for the network. Every service exposes OpenAPI 3.1 contracts and AsyncAPI events, so you never trade portability for depth.
- 68 standards audited
- 91% of Netxol Core Standards Baseline
- 100% on TR-069, syslog, OpenAPI, webhooks, AsyncAPI, OAuth 2, OpenID Connect
TR-069 and TR-369 in one ACS.
Every TR-069 RPC in both directions; USP 1.3 over MQTT 5 and WebSocket with TLS 1.3. Zero-touch provisioning, firmware rollouts, backups and TR-143 / TR-471 diagnostics against your own servers.
TR-069 / CWMP
HTTP/HTTPS with every RPC in both directions, STUN and XMPP connection requests; TR-098 and TR-181 data models.
TR-369 / USP 1.3
MQTT 5 and WebSocket with TLS 1.3, subscriptions and per-agent accounts, in the same ACS as TR-069.
TR-181 device model
Normalised views across vendors, with data-model version per device.
TR-143 & TR-471 diagnostics
Ping, traceroute, download/upload, UDP echo, DNS tests; TR-471 IP capacity against your own OB-UDPST server.
Next-generation subscriber AAA.
FreeRADIUS 3.2 with RadSec, RADIUS/1.1 and CoA / Disconnect — on classic UDP, TLS and TCP in parallel. Vendor-aware RADIUS replies for MikroTik, Huawei, Cisco, Juniper and Nokia BNGs.
RADIUS (RFC 2865, 2866, 5176)
Classic RADIUS auth, accounting and CoA / Disconnect across MikroTik, Huawei, Cisco, Juniper and Nokia BNGs.
RadSec (RFC 6614)
RADIUS over TCP 2083 with mutual TLS and certificate revocation.
RADIUS/1.1 (RFC 9765)
TLS 1.3, no MD5, a token per packet — on TCP 2084, ready for the BNGs that support it.
802.1X EAP-TLS, PEAP, TTLS
A certificate per subscriber, with EAP-TLS, PEAP and TTLS.
PPPoE, IPoE / DHCP option 82
IPv6 prefix delegation, VLAN and QinQ attributes in RADIUS replies.
Interoperability-tested against real servers.
SNMPv3 next to NETCONF, RESTCONF, gNMI and OpenConfig — with a per-device protocol order and automatic fall-back. Syslog RFC 5424, IPFIX, NetFlow and sFlow collectors; OpenTelemetry traces and metrics from every service.
SNMPv3
SHA-2 and AES, traps and informs, alongside SNMPv2c.
NETCONF (RFC 6241) · YANG
Candidate commit, YANG discovery; tested against netopeer2.
RESTCONF (RFC 8040)
Interoperability-tested against a real RESTCONF server.
gNMI / OpenConfig
Get, Set and streaming Subscribe for interface counters and health.
Syslog RFC 5424
UDP, TCP and TLS; chained with case references for lawful look-up.
IPFIX · NetFlow · sFlow
IPFIX collectors, NetFlow v5 / v9 and sFlow v5.
OpenTelemetry
Traces and metrics emitted from every Netxol One service.
GPON, XG-PON, XGS-PON, EPON — on real OLTs.
GPON provisioning on Huawei, ZTE, C-Data, VSOL and FiberHome; EPON on BDCOM; XG-PON and XGS-PON port and optical-class awareness. OMCI-driven ONT provisioning through the OLT.
GPON (ITU-T G.984)
ONT provisioning on Huawei, ZTE, C-Data, VSOL and FiberHome OLTs.
XG-PON · XGS-PON
Port and optical-class awareness with link budgets per class.
EPON · 10G-EPON
MAC authorisation and CTC VLAN on BDCOM.
OMCI (G.988)
OMCI-driven ONT provisioning through the OLT, optical levels and ONU states.
TM Forum Open APIs, OpenAPI, AsyncAPI, OAuth 2.
22 TM Forum Open APIs on live data, two TM Forum ODA component descriptors generated from code, OpenAPI 3.1 and AsyncAPI 3.1 contracts for every service, and a Standard Webhooks delivery with HMAC-SHA256.
22 TM Forum Open APIs
TMF620 Catalog, TMF622 Ordering, TMF678 Bill, TMF676 Payment, TMF642 Alarm… on live data.
TM Forum ODA components
Two ODA component descriptors (CoreCommerce, Production) generated from the code.
OpenAPI 3.1
For the Core API, network API and ACS, built from routes, permissions and validation schemas.
AsyncAPI 3.1
Describes every webhook event, downloadable from Administration → Applications.
Standard Webhooks
HMAC-SHA256 signatures with id and timestamp, retries from 5 seconds to 10 hours, delivery log with re-send.
OAuth 2 · OpenID Connect · SAML 2.0 · LDAP · SCIM 2.0
Netxol One is its own authorisation server and OpenID Connect provider; SAML / LDAP sign-in for staff and SCIM provisioning.
68 standards audited. 91% implemented. Gaps published.
We audit Netxol One against 68 standards and publish the result, gaps included. Today: 91% of the Netxol Core Standards Baseline, 80% priority-weighted, 100% for TR-069 / CWMP, syslog, OpenAPI, webhooks, AsyncAPI, OAuth 2 and OpenID Connect.
What we do not do yet: IPTV (IGMP / MLD) and VoIP line provisioning, a full OMCI managed-entity view, Nokia OLT adapters and XGS-PON ONT provisioning commands. These are planned with our lab partners. We say 'implements' and 'interoperability-tested' — certification is granted by accredited bodies, and Broadband Forum certification applies to devices rather than controllers.
第一次通话中我们经常收到的问题。
What is the difference between TR-069 and TR-369?
TR-069 (CWMP) is the established Broadband Forum protocol for managing routers and ONTs over HTTP. TR-369 (USP) is its successor, using MQTT or WebSocket for faster, event-driven management. Netxol One runs both in one ACS, so old and new devices share one view.
Does Netxol One support RADIUS over TLS?
Yes. Netxol One supports RadSec (RFC 6614) on TCP 2083 and RADIUS/1.1 (RFC 9765) on TCP 2084, both with mutual certificates issued by the installation’s own RADIUS certificate authority.
What is RADIUS/1.1 (RFC 9765)?
RADIUS/1.1 runs RADIUS over TLS 1.3 and drops the old MD5-based obfuscation, using a token per packet instead. Netxol One implements it next to classic RADIUS and RadSec.
Can Netxol One manage devices with NETCONF and gNMI?
Yes. It configures devices over NETCONF and RESTCONF with YANG discovery, and reads streaming telemetry over gNMI using OpenConfig models, alongside SNMPv3.
Is Netxol One certified by the Broadband Forum or TM Forum?
Netxol One implements TR-069, TR-369 and 22 TM Forum Open APIs. Broadband Forum certification applies to devices, and TM Forum conformance testing is planned; we do not claim certification we do not hold.
Which PON technologies does Netxol One support?
GPON provisioning on Huawei, ZTE, C-Data, VSOL and FiberHome OLTs, EPON on BDCOM, and XG-PON / XGS-PON port and optical-class awareness.
Does Netxol One support IPv6?
Yes: IPv6 pools, static prefixes and DHCPv6 prefix delegation through RADIUS, IPv6 in accounting and lawful look-ups, and RADIUS on IPv6.
Verify the scorecard. Pick what you need. Keep what you have.
See the full capability grid or jump straight into the Open APIs page to generate a client in any language. Netxol engineers can walk you through the matrix line by line under NDA.