Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Identifier

FN-CRG

Fixed Network Cable Residential Gateway Globally Unique AMF Identifier

Identifier →

FN-CRG is a globally unique identifier for the Access and Mobility Management Function serving a Cable Residential Gateway in a 5G fixed network.

Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
9 specs
FN-CRG Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define FN-CRG. Each summary describes the whole specification, not only this term.

TS 23.003Rel-18 → Rel-19

Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.

Full comparison in TS 23.003 →
TS 23.316Rel-18 → Rel-19

Rel-19 adds text to TS 23.316 for W-5GAN support of ECN marking for L4S, plus PDU Set based handling. Related procedures and references are also updated.

Full comparison in TS 23.316 →

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-16 3 changes
  • PEI for 5G-CRG and FN-CRG TS 24.501CR0937
  • Service Area Restrictions applicability for FN-CRG, and not FN-BRG TS 23.316CR0056
  • Alignment for stop of enforcement of mobility restrictions in 5G-RG and W-AGF acting on behalf of FN-CRG TS 24.501CR1876

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.316 vj30 Wireless and wireline convergence access support Rel-19 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.716 vg00 Wireline and Trusted Non-3GPP Access to 5G Core Rel-16 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read