Fixed Mobile Convergence

Description

Fixed Mobile Convergence (FMC) is a service architecture defined by 3GPP that unifies fixed network services (such as DSL, fiber, or cable) with mobile network services (like 4G LTE or 5G) to deliver a cohesive user experience. It works by abstracting the underlying access technologies through common core network functions and service layers, allowing users to access voice, data, and multimedia services seamlessly regardless of whether they are connected via a fixed or mobile link. The architecture typically involves convergence points in the core network, such as the IP Multimedia Subsystem (IMS), which handles session control and service delivery across diverse access networks.

Key components of FMC include access-agnostic service platforms, policy control functions (like PCRF or PCF), and unified authentication mechanisms. For instance, when a user initiates a voice call, FMC enables handover between Wi-Fi (fixed access) and cellular networks without interruption, using technologies like Voice over Wi-Fi (VoWiFi) or Single Radio Voice Call Continuity (SRVCC). The network employs session continuity protocols and quality of service (QoS) management to maintain service levels during transitions. This involves coordinating between the fixed broadband gateway (e.g., residential gateway) and mobile core elements like the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF).

In practice, FMC leverages common subscriber databases, such as the Home Subscriber Server (HSS) or Unified Data Management (UDM), to store user profiles and policies that apply across both fixed and mobile domains. This integration allows for features like single sign-on, consistent billing, and unified messaging. By bridging fixed and mobile infrastructures, FMC enhances network utilization, reduces operational costs through shared resources, and supports innovative services like converged IPTV and smart home applications. It is a foundational concept for 5G networks, enabling scenarios where fixed wireless access (FWA) complements traditional mobile services.

Purpose & Motivation

Fixed Mobile Convergence was created to address the fragmentation between fixed and mobile networks, which historically operated as separate silos with distinct services, billing systems, and user experiences. As consumers demanded more flexible and integrated communications, operators faced challenges in providing seamless mobility and service continuity. FMC solves these problems by enabling a unified approach, allowing users to switch between networks transparently, which improves convenience and customer satisfaction.

The motivation for FMC stemmed from the convergence of voice and data services over IP networks, driven by the adoption of IMS and the decline of circuit-switched technologies. It addresses limitations such as service duplication, where operators maintained separate infrastructures for fixed and mobile, leading to inefficiencies and higher costs. By integrating networks, FMC reduces capital and operational expenditures through resource sharing and simplifies service deployment. Historically, early attempts at convergence were proprietary, but 3GPP standardization in Release 8 provided a interoperable framework that spurred widespread adoption.

FMC also tackles the growing demand for broadband everywhere, as fixed networks offer high capacity while mobile networks provide mobility. It enables operators to offload traffic to fixed networks (e.g., via Wi-Fi), alleviating congestion on cellular networks. This is particularly relevant with the rise of 5G, where FMC supports fixed wireless access as a substitute for traditional broadband, expanding coverage and service options. Ultimately, FMC paves the way for fully converged networks that support emerging use cases like smart cities and industrial IoT.

Key Features

• Seamless service continuity across fixed and mobile access
• Integration with IP Multimedia Subsystem (IMS) for unified control
• Unified authentication and subscriber management
• Policy-based QoS and traffic management
• Support for voice and data handover (e.g., VoWiFi, SRVCC)
• Converged billing and service provisioning

Evolution Across Releases

Defining Specifications