Description
Within the 3GPP architecture, File Transfer Protocol (FTP) refers to the use of the standard IETF FTP (and its secure variants like FTPS) as a reliable data delivery mechanism for operations, administration, and management (OAM) functions, as well as for certain service-related data transfers. It is not a 3GPP-invented protocol but is profiled and mandated for specific use cases across various network interfaces. FTP operates on a client-server model, using separate control (TCP port 21) and data connections to facilitate the listing, uploading, and downloading of files.
Key architectural applications include the transfer of Performance Measurement (PM) files from Network Elements (NEs) like NodeBs, eNodeBs, or gNBs to a central Network Management System (NMS) or Element Management System (EMS). These files contain counters and measurements crucial for network monitoring and optimization. FTP is also specified for the delivery of Lawfully Intercepted (LI) content, where intercepted communication content and intercept-related information (IRI) are packaged into files and sent from the Mediation Function (MF) to the Law Enforcement Monitoring Facility (LEMF). Furthermore, FTP is used for software management, such as downloading new software versions or patches to base stations and core network elements.
The protocol works by the client establishing a control connection to the server, authenticating, and issuing commands (e.g., LIST, RETR, STOR). For data transfer, a separate data connection is established. In 3GPP contexts, security is paramount; therefore, the use of FTP over TLS (FTPS) or within secured VPN tunnels is often mandated, especially for sensitive data like LI or software. The specifications detail the directory structures, file naming conventions, compression requirements, and triggering mechanisms (e.g., schedule-based or event-based) for the FTP sessions to ensure interoperability between equipment from different vendors.
Purpose & Motivation
FTP was adopted into 3GPP standards to solve the fundamental problem of automated, reliable, and standardized bulk file transfer between network entities. As cellular networks grew in complexity and automation, there was a critical need to move large datasets—performance logs, configuration backups, intercepted data, and software images—without manual intervention. Pre-standardization, vendors used proprietary methods, hindering multi-vendor interoperability and increasing operational costs for operators.
Its inclusion from Release 99 onwards provided a well-understood, widely implemented protocol for these OAM data flows. It addressed the limitations of ad-hoc transfer methods by offering features like authentication, directory listing, and restart capabilities for interrupted transfers. For Lawful Interception, FTP provided a robust and auditable delivery mechanism for evidence collection. For performance management, it enabled the consolidation of data from thousands of network elements into central systems for analysis. The choice of FTP was motivated by its maturity, simplicity for automated scripting, and ability to handle large files reliably over sometimes unstable IP links, forming the backbone for many automated provisioning, assurance, and compliance processes in modern mobile networks.
Key Features
- Standardized mechanism for bulk file transfer in OAM and LI contexts
- Supports both push and pull models for file delivery
- Defines specific directory structures and file naming conventions for interoperability
- Often used with TLS (FTPS) or within secure tunnels for data protection
- Enables automated transfer of Performance Measurement, Fault Management, and software files
- Provides restart capability to resume interrupted transfers
Evolution Across Releases
Initially adopted for basic file transfer needs, particularly in the context of network management data collection (e.g., performance counters) from GSM and UMTS network elements to management systems. Established its use as a common OAM protocol.
Expanded usage into the Lawful Interception domain, specifying FTP as a delivery mechanism for intercepted content and IRI from the Mediation Function to the Law Enforcement Agency, formalizing secure file-based evidence transfer.
Further solidified FTP roles with the introduction of IP Multimedia Subsystem (IMS), where it found application in areas like configuration delivery and log retrieval for IMS nodes, integrating it into the all-IP core network architecture.
With the advent of LTE (EPS), FTP was profiled for the transfer of extensive performance measurement files from eNodeBs to the Operations Support System (OSS), handling the increased volume of data from flat-IP architecture.
In the 5G era, FTP/FTPS continues to be specified for similar OAM purposes with gNBs and 5GC elements. Emphasis increased on security, often mandating FTPS or secure transport for all management file transfers, aligning with stronger overall network security requirements.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.125 | 3GPP TS 23.125 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.297 | 3GPP TR 32.297 |
| TS 32.341 | 3GPP TR 32.341 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.406 | 3GPP TR 32.406 |
| TS 32.411 | 3GPP TR 32.411 |
| TS 32.583 | 3GPP TR 32.583 |
| TS 32.593 | 3GPP TR 32.593 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.117 | 3GPP TR 33.117 |
| TS 36.825 | 3GPP TR 36.825 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 37.976 | 3GPP TR 37.976 |
| TS 37.977 | 3GPP TR 37.977 |
| TS 38.864 | 3GPP TR 38.864 |
| TS 45.903 | 3GPP TR 45.903 |
| TS 45.913 | 3GPP TR 45.913 |
| TS 45.926 | 3GPP TR 45.926 |
| TS 46.085 | 3GPP TR 46.085 |
| TS 52.402 | 3GPP TR 52.402 |