Description
The Fixed Part Beacon Identity (FPBI) is an identifier defined in 3GPP specifications, particularly TS 43.052, for Fixed Parts (FPs) within cellular networks, especially in contexts like cordless telephony systems (e.g., DECT/GSM interworking) or fixed wireless access. The FPBI serves as a beacon signal that broadcasts the identity of a Fixed Part, enabling User Equipment (UE) to detect, identify, and potentially camp on that FP. It is a critical component for network discovery, cell selection, and synchronization procedures.
Architecturally, the FPBI is broadcast by the Fixed Part over the air interface as part of its beacon or pilot signals. This identifier is unique within a certain administrative domain (like an operator's network or a geographic area) and is used by UEs to distinguish between different FPs. When a UE scans for available networks, it detects these beacon signals, decodes the FPBI, and uses it to determine whether the FP is suitable for connection based on pre-configured preferences or network policies. The FPBI may be structured hierarchically, incorporating elements like network operator code, location area, or FP type.
The FPBI works in conjunction with other system information broadcast by the Fixed Part. Upon detecting the beacon, the UE reads additional parameters such as synchronization codes, channel information, and access rights. The FPBI itself does not carry security credentials but acts as a public label. Its primary role is to facilitate initial attachment and mobility—for example, a UE moving within a building with multiple FPs can use FPBI to identify the best-serving FP. In some implementations, the FPBI may be mapped to higher-layer identities like Cell Global Identity (CGI) or used in location-based services.
Key components include the Fixed Part's transmitter that broadcasts the FPBI, the UE's receiver that detects it, and network management systems that assign and manage FPBI values to avoid conflicts. The FPBI is essential for scenarios with dense deployment of small cells or private networks, where clear identification of each access point is necessary. It supports functions like handover, load balancing, and network optimization by providing a stable reference for cell identification.
Purpose & Motivation
FPBI was created to address the need for unique identification of fixed infrastructure in hybrid or multi-vendor cellular networks, particularly in cordless telephony and early fixed-mobile convergence systems. Before standardized identifiers like FPBI, proprietary schemes led to interoperability issues, making it difficult for UEs to seamlessly roam between different manufacturers' equipment. FPBI provided a uniform way for Fixed Parts to announce their presence, enabling consistent network discovery across diverse deployments.
Historically, as cellular networks expanded to include residential base stations, enterprise femtocells, and cordless telephony interworking, there was a growing proliferation of fixed access points. Managing these required a clear identification mechanism to avoid confusion and ensure correct UE attachment. FPBI solved this by offering a standardized identity format that could be recognized by any compliant UE. It also supported network planning by allowing operators to assign structured identities reflecting geographic or logical groupings.
The motivation for FPBI stemmed from the desire to improve user experience in environments with multiple overlapping coverage areas, such as office buildings or homes with several cordless handsets. It addressed limitations of using only radio frequency or channel numbers for identification, which were insufficient in dense deployments. By providing a unique beacon identity, FPBI enabled faster cell search, reduced ping-pong effects during mobility, and facilitated advanced features like preferred access point selection. It laid groundwork for later small cell identifiers in LTE and 5G.
Key Features
- Unique identifier broadcast by Fixed Parts (base stations)
- Used for network discovery and cell selection by UEs
- Supports synchronization and initial access procedures
- Enables mobility between fixed infrastructure points
- Facilitates network management and planning
- Standardized format for interoperability across vendors
Evolution Across Releases
Defining Specifications
| Specification | Title |
|---|---|
| TS 43.052 | 3GPP TR 43.052 |