File Transfer Protocol

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.