Description
The Fixed Network Cable Residential Gateway Globally Unique AMF Identifier (FN-CRG GUAMI) is a critical identifier defined in 3GPP Release 16 within the context of 5G fixed access over cable networks. It is a specific application of the broader GUAMI concept (defined in TS 23.003) for the Cable Residential Gateway (FN-CRG), which is the customer premises equipment for cable-based fixed broadband (e.g., DOCSIS) integrated into the 5G System. The FN-CRG GUAMI uniquely and globally identifies the specific Access and Mobility Management Function (AMF) instance that is responsible for the control plane mobility and connection management of a given FN-CRG device.
Architecturally, when an FN-CRG device (a type of Fixed Network Residential Gateway for cable) initializes and registers with the 5G Core Network, it needs to be assigned to an AMF. The network selection function (e.g., Network Slice Selection Function - NSSF) helps select an appropriate AMF based on subscription, network slice, and local policies. Once selected, that AMF's identity—its GUAMI—is associated with the FN-CRG. The FN-CRG GUAMI is structured according to the GUAMI format: it includes a PLMN Identifier (Mobile Country Code and Mobile Network Code) to ensure global uniqueness across operators, followed by an AMF Region ID, AMF Set ID, and AMF Pointer, which together identify the specific AMF instance within the operator's network.
How it works: The FN-CRG GUAMI is used in control plane signaling messages between network functions. For instance, when a Session Management Function (SMF) needs to communicate with the AMF managing a particular FN-CRG for PDU session establishment, it uses the FN-CRG GUAMI to route the N11 message correctly. It is also crucial during mobility events; if an FN-CRG's context needs to be relocated from one AMF to another (e.g., for load balancing or failure recovery), the GUAMI identifies the source and target AMFs. The identifier is stored in the Unified Data Management (UDM) as part of the subscriber's context, ensuring that subsequent registration updates or service requests can find the correct serving AMF. This precise routing is essential for the scalability and reliability of 5G core networks supporting millions of fixed devices.
Purpose & Motivation
The FN-CRG GUAMI was introduced to solve the addressing and routing challenges inherent in scaling the 5G core to support massive numbers of fixed residential gateways (like cable modems). In earlier generations and non-3GPP fixed networks, management of CPE was often done through proprietary or domain-specific protocols (like TR-069) with less granular, non-globally-unique identifiers. As cable access was integrated into the 5G core via the FN-CRG (starting Rel-16), it became necessary to manage these devices with the same principles of scalability, redundancy, and cloud-native statelessness applied to mobile user equipment.
The primary problem addressed is the need for unambiguous identification and efficient routing to the correct control plane entity (AMF) in a decomposed, service-based architecture where AMFs can be dynamically instantiated and scaled. Without a globally unique identifier, routing failures could occur in multi-vendor deployments or when operators merge networks. The GUAMI framework, applied specifically to the FN-CRG, ensures that any network function (SMF, UDM, another AMF) can precisely determine and communicate with the AMF instance serving a specific cable gateway, anywhere in the world. This enables advanced 5G features for fixed access: efficient mobility management (even for 'fixed' devices, there can be logical mobility or re-assignment), seamless AMF relocation for load balancing, and reliable service continuity during network function failures. It is a foundational element for treating fixed access as a true peer to mobile access within the 5G core.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the FN-CRG function was enhanced with the introduction of a globally unique PEI (Portable Equipment Identifier) for identification, alongside specific provisions for applying Service Area Restrictions to it. The release also included alignment for the stop of enforcement of mobility restrictions when a W-AGF acts on behalf of an FN-CRG. Technically, for an FN-CRG accessing the 5GC via a Wireline 5G Cable Access Network (W-5GCAN), its User Location information is defined as an HFC Node ID, and it is associated with a GCI (Generic Cable Identifier) that uniquely identifies its connecting line to the 5GS.
Explore further
Broader topics and technologies where FN-CRG plays a role.
Defining Specifications
3GPP specifications that define or reference FN-CRG, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.003 vj50 | Numbering, addressing and identification in 3GPP | Rel-19 |
| TS 23.316 vj30 | Wireline and Wireless Convergence Access Support | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.716 vg00 | Wireline and Trusted Non-3GPP Access to 5G Core | Rel-16 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 29.507 vj40 | 5G Access & Mobility Policy Control Service | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |
| TS 29.561 vj30 | 5G Interworking with External Data Networks | Rel-19 |
