Network function — A named part of the core, defined by the services it offers

5G Systems Notes · Concept map · Network function Route · Hierarchy · Index · All concepts · Hub

The core network

Where it sits

Sits atLevel 1 of the hierarchy · The core network · explained
Also writtenNF
Learn first5G Core
UnlocksService-based architecture · AMF · SMF · UDM · PCF
Primary clauseTS 23.501 §6.2
Used inref-core 12 · ref-ue-state 2 · index 2
Scanned from the notes at page load and joined with terms.json; nothing on this card is typed by hand.

What it is

What it is. The unit the 5G core is built from: a named function that offers one or more services to other functions, listed with its functionality in TS 23.501 §6.2. The specification defines more than thirty of them; six carry almost all of the traffic of an ordinary connection, and the rest are specialised.

The six that matter for a first pass:

Function Clause The one sentence
AMF §6.2.1 The device's single contact point — registration, reachability, mobility
SMF §6.2.2 Owns a PDU session: addresses, UPF selection, steering
UPF §6.2.3 Forwards the packets; the only function on the data path
PCF §6.2.4 The operator's rules, as policy
UDM §6.2.7 The subscription, the credentials, and SUCI de-concealment
AUSF §6.2.8 Authentication

Add NRF (§6.2.6) for discovery, NEF (§6.2.5) for exposure outward and NSSF (§6.2.14) for slice selection and you have the set this folder uses.

A network function is not a server. TS 23.501 §6.2.1 is careful about this: "Some or all of the AMF functionalities may be supported in a single instance of an AMF." The specification describes a function, and says nothing about how many processes implement it, on how many machines, or in how many places. An operator may run one AMF instance or a hundred; may split the function across a region; may run instances that support only part of the list.

This is the difference from a node. An MME was a box you bought. An AMF is a set of behaviours something must exhibit, addressed by the services it registers.

The functionality lists are worth reading literally. They are terse and they are exhaustive, and each line is a claim about a seam. The AMF list contains "Provide transport for SM messages between UE and SMF" and "Transparent proxy for routing SM messages" — two lines that between them say the AMF carries session-management signalling without reading it, which is the whole reason 5GSM is a separate protocol from 5GMM.

Read on

This concept is read as part of one argument in ref-core, alongside the rest of its group.

Widget not found: sim_status

Before this concept, the hierarchy says to learn the following — the full chain, in order:

To understand Network function (level 1) you first need 1 other concepts. Read them in this order — everything on one line can be read in any order, but no line before the one above it:
Level Learn these
0 5G Core
Immediately before Network function: 5G Core.
Keep going — where this sits on the route
The route is every concept in the folder ordered by level, so nothing here needs anything after it. Computed at page load from terms.json; the same numbering as the route page.
5G Systems Notes · Concept map · Network function Top · Concept map · Hub