Glossary

A device management platform that provides centralized configuration, monitoring, and control of network devices using protocols such as TR-069, MQTT, and USP.

SOAP-based web services provided by the ACS platform for external application integration and service orchestration.

Open-source message broker that implements the Java Message Service (JMS) API. Used by ACS for MQTT message handling.

Open-source column-oriented database management system optimized for analytics and time-series data. Used by ACS for storing historical device data and QoE metrics.

Component that enables inter-database communication between ClickHouse and the main relational database (Oracle/MySQL), allowing data synchronization and cross-database queries.

Specialized web transfer protocol for use with constrained nodes and networks in the Internet of Things. Supported as a USP message transport protocol (MTP).

Network devices located at customer premises, such as routers, gateways, and set-top boxes, managed by the ACS platform via TR-069 protocol.

See TR-069. The official protocol name for TR-069.

HTTP authentication method that applies a hash function to credentials before transmission, providing better security than Basic authentication. One of the TR-069 authentication modes supported by ACS.

Platform for developing, shipping, and running applications in containers. Provides the recommended deployment method for ACS.

Protocol that provides security for datagram-based applications, used for securing CoAP communications in USP protocol.

Open-source XMPP/Jabber server written in Erlang. Used by ACS as the XMPP server for managing device connections and routing messages between ACS and CPE devices.

Open-source analytics and monitoring platform used for visualizing ACS performance metrics, device statistics, and QoE data.

Open-source in-memory data grid providing distributed caching and computation capabilities. Used by ACS for distributed caching across multiple instances to improve performance and ensure consistency.

High-performance JDBC connection pool library used by ACS for managing database connections efficiently.

Application protocol for distributed, collaborative, hypermedia information systems. Foundation protocol for web services and TR-069 communications.

Extension of HTTP with encryption using TLS/SSL for secure communication.

Simple authentication scheme built into the HTTP protocol using base64-encoded username and password. One of the TR-069 authentication modes supported by ACS.

Initial message sent by a TR-069 device to the ACS to establish a session and report device state. The most time-critical message type in TR-069 protocol, with a target response time of 5 seconds in the current ACS version.

Original name for XMPP protocol. Often used interchangeably with XMPP.

Unique identifier for XMPP users and resources. Format: username@domain/resource. In ACS context, devices are assigned JIDs for XMPP-based connection requests.

Java framework for mapping Java objects to XML and vice versa. Used in previous ACS versions for XML parsing, replaced by StAX in the current version for better performance.

Java API for connecting and executing queries with databases. Used by ACS through HikariCP for database operations.

Software development kit for Java platform. ACS requires JDK 25 for runtime and development.

Java API for sending messages between two or more clients. Used by ActiveMQ for message broker functionality.

Open-source database schema change management tool. Embedded in ACS to handle automatic database migrations during application startup, ensuring schema consistency across environments.

Lightweight publish-subscribe messaging protocol designed for constrained devices and low-bandwidth networks. One of the device management protocols supported by ACS.

Open-source relational database management system. One of two database platforms supported by ACS for primary data storage.

Commercial relational database management system. One of two database platforms supported by ACS for primary data storage.

Measurement of device and service performance from the end-user perspective. ACS collects and stores QoE data from devices, now using direct pass-through to ClickHouse for improved performance.

Open-source job scheduling library for Java applications. Used by ACS for scheduling periodic tasks and cron jobs, with dedicated database tables for persistence.

Architectural style for distributed systems. ACS provides RESTful APIs for subscription management and external integration.

Publication series from the Internet Engineering Task Force (IETF) containing technical specifications and organizational notes about the Internet.

Framework for authentication and data security in Internet protocols. Used by XMPP for device authentication with multiple mechanism support (SCRAM-SHA-256, DIGEST-MD5, PLAIN, etc.).

Modern authentication mechanism that provides mutual authentication without transmitting passwords. Supported variants in ACS XMPP: SCRAM-SHA-512, SCRAM-SHA-256, SCRAM-SHA-1.

Protocol specification for exchanging structured information in web services. ACS provides SOAP web services (ACSWS) for external application integration.

Java-based framework for building production-ready applications with minimal configuration. The core application framework used by ACS.

Java API for processing XML documents using a pull-parsing mechanism. Replaced JAXB in the current ACS version for improved XML parsing performance with lower memory consumption.

Text-based protocol for message-oriented middleware. Supported as a USP message transport protocol (MTP) by ACS.

Framework for API documentation and testing. ACS REST API is documented and accessible through Swagger UI.

Core protocol of the Internet Protocol Suite providing reliable, ordered, and error-checked delivery of data. Used as transport layer for HTTP, MQTT, and other ACS protocols.

Cryptographic protocol for secure communication over networks. Used by ACS for securing HTTPS, MQTT, and other protocol communications.

Open-source Java servlet container. ACS uses embedded Tomcat 10.x for HTTP/HTTPS services, replacing the external JBoss/WildFly server used in previous versions.

CPE WAN Management Protocol (CWMP) standardized by the Broadband Forum for remote management of customer premises equipment. One of the primary device management protocols supported by ACS.

Connectionless protocol in the Internet Protocol Suite. Used as transport layer for CoAP in USP communications.

Next-generation protocol for management, monitoring, and control of connected devices, standardized as TR-369 by the Broadband Forum. One of the device management protocols supported by ACS.

Lightweight threads introduced in Java (Project Loom) that enable high concurrency with minimal resource overhead. Used by ACS for asynchronous request processing, dramatically reducing thread count compared to traditional threading models.

Protocol providing full-duplex communication channels over a single TCP connection. Used as a message transport protocol for USP communications.

WebSocket protocol over TLS/SSL, providing encrypted communication. Used as a secure message transport protocol for USP communications.

Open-source Java application server (formerly JBoss). Used in previous ACS versions, replaced by embedded Tomcat in the current version for simplified deployment.

XML-based interface description language for describing the functionality offered by web services. ACS SOAP services provide WSDL documents for client integration.

Markup language for encoding documents in a format that is both human-readable and machine-readable. Used extensively in TR-069, SOAP, XMPP, and configuration files.

Open-standard communications protocol for message-oriented middleware based on XML. Used by ACS as an alternative transport for TR-069 connection requests, providing persistent bidirectional connections and improved NAT traversal. Formerly known as Jabber.