Description
The Auto-Configuration Server (ACS) is a core component in the management architecture for broadband devices, standardized by the Broadband Forum in TR-069 (CPE WAN Management Protocol) and widely adopted and referenced within 3GPP specifications for managing fixed and converged network elements. It operates as a central server that communicates with a large population of Customer Premises Equipment (CPE) devices over a secure connection, typically using SOAP/HTTP(S) over an IP network. The ACS initiates sessions to the CPE, which acts as a client, to perform a wide range of management functions. The protocol defines a robust RPC (Remote Procedure Call) mechanism where the ACS can invoke methods on the CPE to get or set parameter values, upload/download files, and receive asynchronous event notifications from the device.
Architecturally, the ACS interfaces with other backend systems such as provisioning systems, fault management platforms, and service activation systems. It uses a data model, often based on the Broadband Forum's TR-181 (Device Data Model), which provides a standardized hierarchical tree of parameters representing the device's configuration, status, and capabilities. This model allows the ACS to interact with diverse CPE types from different vendors in a uniform way. Key components of the ACS include the northbound interfaces (NBI) for integration with OSS/BSS, the core session management and protocol engine for handling TR-069 communications, and a database for storing device information, session history, and configuration policies.
In operation, the ACS manages the entire lifecycle of the CPE. During initial boot-up (provisioning phase), the CPE discovers the ACS URL, establishes a secure connection, and informs the ACS of its capabilities. The ACS then pushes the necessary configuration (e.g., VLAN settings, SSID, VoIP parameters) to enable services. For ongoing management, the ACS can perform periodic diagnostics, monitor performance metrics, and push firmware updates. It also handles fault management by receiving and processing event notifications (like 'value change' or 'transfer complete') from the CPE, allowing for proactive troubleshooting. The ACS's role is pivotal in enabling zero-touch provisioning, reducing truck rolls, ensuring service consistency, and maintaining the health of the deployed device fleet.
Purpose & Motivation
The ACS was created to solve the critical operational challenges faced by service providers in managing millions of remotely deployed CPE devices. Prior to TR-069 and ACS, configuring home gateways and routers required either manual, on-site technician visits or reliance on less standardized, vendor-specific management tools. This approach was costly, slow, error-prone, and did not scale with the rapid growth of broadband subscriptions. The ACS provides a standardized, automated, and remote management framework that eliminates the need for physical access to the customer premises for most configuration and update tasks.
The historical context lies in the early 2000s with the mass adoption of DSL and the proliferation of complex home networking devices offering triple-play services (data, voice, video). Managing service quality, deploying new features, and troubleshooting issues across a heterogeneous device ecosystem became a major bottleneck. The TR-069 protocol and the ACS server concept were developed to provide a vendor-neutral, interoperable solution. It addresses limitations of previous ad-hoc methods by offering a secure, transactional, and model-driven approach to device management, which is essential for rapid service rollout, consistent customer experience, and efficient network operations.
Within the 3GPP ecosystem, the ACS is referenced in contexts like Fixed-Mobile Convergence (FMC), management of residential gateways in 5G networks, and the broader scope of network management and automation. It solves problems related to device onboarding, policy enforcement, and software lifecycle management in a scalable and automated fashion, which aligns with 3GPP's goals for network automation and reduced operational expenditure (OPEX).
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the ACS (Adjacent Channel Selectivity) function was refined through clarifications on the application of interfering signal offsets for both conducted and Over-The-Air (OTA) test requirements. Specific corrections were made to define the type of interfering signal used for ACS, in-band blocking, and In-Channel Selectivity (ICS) measurements. Additionally, updates were introduced to clarify the interfering Resource Block (RB) frequency for narrowband blocking scenarios which are related to ACS testing.
- CR to TS 38.104 Combined updates from RAN4 #90bis and RAN4#91 From RAN4 #90bis: - R4-1903105, "Draft CR to TS 38.104: Corrections on terminologies and editorial errors" - R4-1903319, "Draft CR to TS 38.104: removal of unused definition: "minimum EIRP level under extreme condition"" - R4-1903320, "Draft CR to TS 38.104: OSDD information correction" - R4-1903457, "Draft CR to TS 38.104: Removal of FFS for FR2 TDD OFF power level requirement in clause 9.5" - R4-1903499, "Draft CR to 38.104: Correction to unwanted emissions mask for bands n7 and n38" - R4-1903836, "Draft CR to TS 38.104: Correction on description on multi-band operation in section 4.8" - R4-1904024, "Draft CR to TS 38.104 Applicability rules for BS demodulation" - R4-1904234, "draftCR: Correlation matrix for 8Rx in TS 38.104" - R4-1904723, "Draft CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH" - R4-1904726, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1" - R4-1904729, "Draft CR on PRACH performance requirements in TS38.104" - R4-1904734, "Draft CR on TS 38.104 Performance requirement for PUCCH format 1" - R4-1904735, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104" - R4-1904739, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements" - R4-1904745, "draftCR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104" - R4-1904799, "Draft CR to TS 38.104: FRC update for PUSCH FR1 mapping type B and FR2 DMRS 1+1" - R4-1904816, "Draft CR : Clarification on step 5 and step 6 for delay profiles calculation (38.104)" - R4-1904842, "Draft CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements" - R4-1905126, "draft CR to 38.104 for TAE requirements" - R4-1905139, "draft CR to TS 38.104 on EVM measurement (Annex B and C)" - R4-1905140, "Draft CR: editorial correction on FR1 spurious emission requirement in TS38.104" - R4-1905143, "Draft CR for TS 38.104: Addition of NOTE for transmitter intermodulation requirements in certain regions" - R4-1905144, "Draft CR to TS 38.104: FRC reference corrections for the Rx requirements" - R4-1905145, "Draft CR to TS 38.104: Clarification on application of interfering signal offsets for ACS, blocking and intermodulation requirements" - R4-1905148, "Draft CR to TS 38.104: Corrections on out-of-band blocking requirement" From RAN4 #91: - R4-1906002, "Draft CR to 38.104: Subclause 6.7 and 9.8 transmitter intermodulation – correction of interfering signal type" - R4-1906096, "Draft CR to 38.104: Correction of frequency range for OTA spurious emissions" - R4-1906311, "Draft CR to 38.104: Correction on FRC (Annex A)" - R4-1906346, "Removal of n65 in Rel-15 38.104" - R4-1906915, "Draft CR to TS 38.104: Clarification on application of interfering signal offsets for OTA ACS, blocking and intermodulation requirements" - R4-1906918, "Draft CR to TS 38.104: Clarification on type of interfering signal for ACS, in-band blocking and ICS requirements" - R4-1907110, "Draft CR to TS 38.104: correction of the fundamental frequency limit of 2.55GHz for the spurious emissions" - R4-1907246, "Draft CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH" - R4-1907249, "Draft CR to TS 38.104: Correction on the terminology in PUSCH FRC tables" - R4-1907252, "Draft CR to TS38.104: Updates of PRACH performance requirements" - R4-1907255, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104" - R4-1907258, "Draft CR on NR UCI on PUSCH performance requirements for TS 38.104" - R4-1907261, "draftCR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104" - R4-1907266, "Draft CR on TS 38.104 Performance requirement for PUCCH format 1" - R4-1907267, "Draft CR on TS 38.104 Performance requirement for multi-slot PUCCH format 1" - R4-1907272, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements" - R4-1907275, "Draft CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements" - R4-1907277, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1" - R4-1907629, "Draft CR to 38.104: Term “reference signal” replacing by term “ideal signal” in EVM context" - R4-1907634, "Draft CR to 38.104: corrections to the EVM annex" - R4-1907659, "Draft CR to TS 38.104 on Spurious emission Category B in FR2" - R4-1907661, "Draft CR to 38.104 Definition of contiguous transmission bandwidth" - R4-1907662, "Draft CR to 38.104: BS TAE requirements" - R4-1907664, "Draft CR to 38.104: Clarification of interferer RB frequency for narrowband blocking" - R4-1907672, "Draft CR for TS 38.104: Correction on EVM" - R4-1907689, "Correction to CA carrier spacing" TS 38.104CR0029
In Release 16, the ACS (Auto-Configuration Server) function was enhanced with new methods for provisioning ACS information to devices, specifically via the DHCP protocol and within the ParameterProvision procedure. Furthermore, a new coordination mechanism between the PCF (Policy Control Function) and the ACS was introduced to support Fixed Network Residential Gateway (FN RG) scenarios. These updates were complemented by technical corrections to Over-The-Air (OTA) ACS receiver requirements and test parameters in the RAN4 specifications.
- Usage of ACS information PCO parameter TS 24.501CR0938
- ACS information via DHCP TS 24.501CR1919
- ACS information in ParameterProvision TS 29.503CR0290
- ACS information TS 29.503CR0291
- Coordination between PCF and ACS (for FN RG) TS 23.316CR0034
- TS 37.145-2: Corrections OTA SEM, OTA Rx intermod and OTA ACS TS 37.145CR0266
+ 2 more changes
In Release 17, the enhancements to the Auto-Configuration Server (ACS) function specifically introduced support for the configuration of PSNB handset receivers. This update defined the necessary procedures and capabilities for the ACS to manage these particular devices.
- CR for 37.880: ACS of PSNB handset receivers TS 37.880CR0002
In Release 19, the Auto-Configuration Server (ACS) function was updated with corrections and clarifications to its technical specifications. Specifically, a correction was made to the interfering signal type used for ACS in the 3MHz channel bandwidth within the NR radio interface specifications. Additionally, a Change Request was applied to the technical report detailing the ACS feature, providing further study and refinement of its capabilities.
Explore further
Broader topics and technologies where ACS plays a role.
Defining Specifications
3GPP specifications that define or reference ACS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.153 vj00 | Out-of-Band Transcoder Control Stage 2 | Rel-19 |
| TS 23.316 vj30 | Wireline and Wireless Convergence Access Support | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 25.101 vj00 | UTRA FDD UE RF Requirements | Rel-19 |
| TS 25.102 vj00 | UTRA TDD RF Characteristics | Rel-19 |
| TS 25.104 vj00 | UTRA FDD Base Station RF Characteristics | Rel-19 |
| TS 25.105 vj00 | UTRA TDD Base Station RF Requirements | Rel-19 |
| TS 25.111 vj00 | LMU RF Characteristics for UTRA FDD | Rel-19 |
| TS 25.141 vj00 | UTRA FDD Base Station RF Conformance Testing | Rel-19 |
| TS 25.212 vj00 | UTRA FDD Layer 1 Multiplexing & Channel Coding | Rel-19 |
| TS 25.703 vc00 | HNB Emergency Warning Area Study for UTRA | Rel-12 |
| TS 25.866 v1900 | 1.28Mcps TDD Home NodeB Study Report | Rel-9 |
| TR 25.942 vj00 | UTRA RF System Scenarios Specification | Rel-19 |
| TS 26.102 vj00 | Mapping of AMR and other codecs to interfaces | Rel-19 |
| TS 26.103 vj00 | 3GPP Codec Lists for OoBTC and TrFO | Rel-19 |
| TS 26.202 vj00 | AMR-WB Speech Codec Mapping Specification | Rel-19 |
| TS 28.062 vj00 | Tandem Free Operation (TFO) Service Description | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 29.522 vj40 | 5G NEF Northbound APIs Stage 3 | Rel-19 |
| TS 32.821 v1900 | SON OAM Architecture for Home NodeB | Rel-9 |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 |
| TS 36.101 vj30 | LTE UE Radio Transmission & Reception Requirements | Rel-19 |
| TS 36.102 vj10 | E-UTRA UE Satellite Access RF Requirements | Rel-19 |
| TS 36.104 vj10 | Base Station (BS) radio transmission and reception | Rel-19 |
| TS 36.108 vj10 | Satellite Access Node RF Requirements | Rel-19 |
| TS 36.111 vj00 | LMU Requirements for UTDOA Positioning | Rel-19 |
| TS 36.112 vj00 | E-UTRAN LMU Conformance Requirements | Rel-19 |
| TS 36.116 vj00 | E-UTRA Relay RF Requirements | Rel-19 |
| TS 36.117 vj00 | E-UTRA Relay RF Test Methods & Requirements | Rel-19 |
| TS 36.141 vj00 | E-UTRA BS Conformance Testing | Rel-19 |
| TS 36.181 vj30 | E-UTRA RF Test Methods for Satellite Access Node | Rel-19 |
| TS 36.521 vj00 | E-UTRA UE Conformance ICS Proforma | Rel-19 |
| TS 36.790 vf00 | LAA/eLAA for CBRS 3.5GHz Band in US | Rel-15 |
| TR 36.942 vj00 | E-UTRA System Scenarios Specification | Rel-19 |
| TS 37.104 vj10 | MSR Base Station RF Characteristics | Rel-19 |
| TS 37.105 vj10 | AAS Base Station Transmission & Reception Requirements | Rel-19 |
| TS 37.141 vj10 | RF Test Methods for Multi-Standard Radio Base Stations | Rel-19 |
| TS 37.145 vj10 | AAS Base Station Conducted Conformance Testing | Rel-19 |
| TS 37.802 va10 | MSR BS RF Requirements for Non-Contiguous Spectrum | Rel-10 |
| TS 37.809 vb00 | E-UTRA & MSR BS Class Requirements | Rel-11 |
| TS 37.812 vb30 | Multi-band Multi-standard Radio BS Requirements | Rel-11 |
| TS 37.814 vc00 | L-band Supplemental Downlink for UTRA/E-UTRA | Rel-12 |
| TR 37.843 vf70 | AAS BS Radiated RF Requirement Background | Rel-15 |
| TR 37.880 vh20 | High-power UE for fixed-wireless/vehicle use | Rel-17 |
| TR 37.900 vj00 | Multi-Standard Radio (MSR) Base Station Requirements | Rel-19 |
| TR 37.941 vj20 | RF Conformance Testing Background for Radiated BS Requirements | Rel-19 |
| TS 38.101 vj31 | NR User Equipment Radio Transmissions | Rel-19 |
| TS 38.104 vj20 | NR Base Station RF Requirements | Rel-19 |
| TS 38.108 vj20 | NTN NR Satellite Access Node RF Requirements | Rel-19 |
| TS 38.115 vj20 | NR Repeater RF Conformance Testing Part 1 | Rel-19 |
| TS 38.141 vj20 | NR Base Station RF Conformance Testing Part 1 | Rel-19 |
| TS 38.174 vj10 | NR Integrated Access and Backhaul Radio Spec | Rel-19 |
| TS 38.176 vj20 | IAB Conformance Testing Specification | Rel-19 |
| TS 38.181 vj10 | NR Satellite Access Node RF Testing | Rel-19 |
| TS 38.191 vj00 | NR Ambient IoT RF Characteristics | Rel-19 |
| TS 38.194 vj00 | Ambient IoT Base Station RF Spec | Rel-19 |
| TS 38.521 vj20 | NR Physical Layer UE Conformance Testing | Rel-19 |
| TS 38.741 vj00 | NTN L-/S-band for NR Technical Specification | Rel-19 |
| TS 38.755 vj10 | NR FR1 DL Fragmented Carriers Study | Rel-19 |
| TS 38.774 vj00 | Rel-19 LP-WUS/WUR RF Requirements TR | Rel-19 |
| TR 38.785 vh00 | UE radio transmission for enhanced NR sidelink | Rel-17 |
| TR 38.786 vi20 | Technical Report for NR Sidelink Evolution | Rel-18 |
| TS 38.787 vj00 | UE Radio Transmission for Sidelink CA in ITS Band | Rel-19 |
| TS 38.793 vj00 | Simultaneous Rx/Tx Band Combinations TR | Rel-19 |
| TR 38.815 vf10 | NR Frequency Range 24.25-29.5 GHz Study | Rel-15 |
| TS 38.817 | 3GPP TR 38.817 | R99 |
| TR 38.828 vg10 | CLI and RIM for NR | Rel-16 |
| TR 38.839 vh00 | Simultaneous Rx/Tx band combinations | Rel-17 |
| TR 38.844 vi00 | Efficient utilization of licensed spectrum | Rel-18 |
| TR 38.847 vh20 | NR 47.2-48.2 GHz Frequency Range | Rel-17 |
| TR 38.849 vi50 | Technical Report | Rel-18 |
| TR 38.858 vi20 | Technical Report on Evolution of NR Duplex Operation | Rel-18 |
| TS 38.863 vj10 | NR NTN RF and Co-existence Spec | Rel-19 |
| TR 38.868 vh00 | Optimizations of pi/2 BPSK uplink power in NR | Rel-17 |
| TR 38.869 vi00 | Study on low-power wake up signal and receiver for NR | Rel-18 |
| TS 38.870 vj20 | Enhanced OTA Test Methods for NR FR1 TRP/TRS | Rel-19 |
| TR 38.877 vi10 | Technical Report | Rel-18 |
| TR 38.881 vi00 | Technical Report on Lower MSD for Inter-band CA/EN-DC/DC | Rel-18 |
| TR 38.886 vg30 | NR V2X UE Radio Transmission & Reception | Rel-16 |
| TS 38.887 vg00 | NR Band n259 Specification (39.5-43.5 GHz) | Rel-16 |
| TR 38.894 vi00 | Technical Report | Rel-18 |
| TR 38.903 vj00 | Test Tolerances & Measurement Uncertainties | Rel-19 |
| TR 38.921 vj00 | IMT Parameters Study for 6.4-7.1 & 10-10.5 GHz | Rel-19 |
| TR 38.922 vj20 | Study on IMT Parameters for NR in Higher Bands | Rel-19 |
| TS 45.009 vj00 | GSM AMR Link Adaptation & Control | Rel-19 |
