FSA

Frequency Selection Area

Radio Access Network →
Introduced in Rel-17 Also in: User Equipment, Services, Radio Access Network

FSA is an identifier for a Frequency Selection Area that defines a logical area where specific frequency selection policies apply for Multimedia Broadcast Multicast Service delivery in 5G networks.

Category
Radio Access Network
Introduced
Rel-17
Where
Core Network › 5G Core
Also touches
3 segments
Specifications
8 specs
FSA Description Purpose Related Classification Detected Changes Specifications

Description

The Frequency Selection Area (FSA) is a logical concept and identifier introduced in 3GPP Release 17 as part of the enhanced Multimedia Broadcast Multicast Service (MBS) framework for 5G networks. An FSA defines a geographical or logical area within which specific frequency selection policies and configurations are applied for the delivery of broadcast and multicast services. It is a key component in managing radio resources efficiently for MBS, enabling the network to direct User Equipment (UE) to optimal frequencies for receiving multicast/broadcast content based on their location and network conditions.

Architecturally, an FSA is configured and managed by the network, typically by the 5GC Core Network and the NG-RAN. The FSA ID is a unique identifier that is broadcasted in system information or provided via dedicated signaling to UEs interested in MBS. The network maps FSAs to specific frequency layers, cell lists, or MBS session areas. When a UE enters an FSA, it uses the associated FSA ID to determine which frequency to monitor or camp on for MBS reception, potentially involving reselection or handover procedures optimized for multicast flows.

How FSA works involves several steps. First, the network plans and configures FSAs, assigning FSA IDs and associating them with MBS services and frequency resources. This information is communicated to RAN nodes (gNBs). For UEs, the FSA ID is acquired either from broadcast system information blocks (SIBs) or via dedicated RRC signaling when joining an MBS session. The UE then uses this ID, possibly in conjunction with a pre-configured or network-provided mapping, to select the appropriate carrier frequency for MBS reception. This mechanism allows for load balancing, interference mitigation, and efficient use of spectrum dedicated to broadcast/multicast. Key specifications like TS 23.247 (MBS architecture) and TS 38.300 (NR overall description) detail its integration into service and RAN procedures.

The role of FSA in the network is crucial for scalable and efficient MBS delivery in 5G. It enables frequency-domain resource management for broadcast services, separating MBS traffic from unicast traffic where beneficial. This supports use cases like public safety communications, live event streaming, and software updates over the air. By defining FSAs, the network can optimize coverage, capacity, and UE battery life for multicast reception, making 5G MBS a viable and efficient technology for group communications.

Purpose & Motivation

FSA was created in Release 17 to address specific challenges in deploying efficient Multimedia Broadcast Multicast Services (MBS) in 5G NR networks. Prior to Rel-17, MBS in 4G LTE (eMBMS) had mechanisms like MBSFN areas, but 5G introduced a more flexible architecture. The motivation for FSA stems from the need for dynamic and efficient frequency resource management for broadcast/multicast traffic, which can have different coverage and capacity requirements compared to unicast.

The historical context is the 3GPP's work on enhancing MBS for 5G to support new use cases like V2X group communications, IoT software updates, and TV broadcasting. A key problem was how to efficiently direct UEs to the correct frequency for MBS without excessive signaling overhead or suboptimal resource usage. FSA solves this by providing a logical identifier that encapsulates frequency selection policy for an area, simplifying UE procedures and enabling network-controlled optimization. It addresses limitations of static configurations by allowing network planning to adapt MBS frequency usage per area, improving spectrum efficiency and service reliability for multicast applications in diverse deployment scenarios.

Classification

Part ofMBSFN
Specific typesMBS

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 2 changes

In Release 17, the MBS Frequency Selection Area (FSA) function was newly introduced to guide UE frequency selection for broadcast Multicast/Broadcast Service sessions. Specifically, the MBS FSA ID is a preconfigured identifier announced by RAN nodes in System Information Blocks, and its mapping to frequencies is provided via OAM. The function involves the MB-SMF determining or receiving these IDs, which are then communicated to the UE via service announcement and to the NG-RAN via the AMF to determine the appropriate cells and frequencies for broadcasting the session data.

  • MBS Frequency Selection Area Identifier TS 29.532CR0008
  • MBS Frequency Selection Area Identifier TS 23.247CR0092
Rel-18 1 change

In Release 18, the FSA function was enhanced to explicitly address the frequency selection for MBS sessions involving both RedCap and non-RedCap UEs. The specification clarifies that when an MBS session can be received by any kind of UE, a single MBS FSA ID is applicable for both device types. However, if separate frequency guidance is necessary for RedCap and non-RedCap UEs, the standard now stipulates that two separate MBS sessions, each with their own MBS FSA ID(s), must be used.

  • FSA ID used for MBS session involving RedCap and non-RedCap UE TS 23.247CR0363

Explore further

Broader topics and technologies where FSA plays a role.

Defining Specifications

3GPP specifications that define or reference FSA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.247 vj30 5G Multicast/Broadcast Service Architecture Rel-19
TS 24.578 vj00 UE policies for A2X services in 5GS Rel-19
TS 24.587 vj30 V2X Services Protocols for 5G System Rel-19
TS 24.588 vj00 UE Policies for V2X Services in 5GS Rel-19
TS 26.517 vj10 5G MBS User Service Protocols and Formats Rel-19
TS 29.532 vj30 MB-SMF Service Based Interface Protocol Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.