<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>5gc on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/5gc/</link><description>Recent content in 5gc on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/5gc/index.xml" rel="self" type="application/rss+xml"/><item><title>5G Core (5GC)</title><link>https://lesitedefrancois.be/en/telco/5gc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/5gc/</guid><description>&lt;p&gt;The &lt;strong&gt;5G Core (5GC)&lt;/strong&gt; is the packet core network architecture defined by &lt;strong&gt;3GPP&lt;/strong&gt; from &lt;strong&gt;Release 15&lt;/strong&gt; onward as the control and user-plane backbone of standalone 5G deployments. It replaces the Evolved Packet Core (EPC) of 4G LTE not through incremental evolution but through a deliberate architectural break: where the EPC was built around monolithic, hardware-bound network functions interconnected by point-to-point interfaces, the 5GC is designed from the ground up around a &lt;strong&gt;Service-Based Architecture (SBA)&lt;/strong&gt; — every network function exposes its capabilities as a set of services over a &lt;strong&gt;common HTTP/2 bus&lt;/strong&gt; (the Service-Based Interface, SBI), and any authorised consumer NF can discover and invoke those services through the &lt;strong&gt;NRF (Network Repository Function)&lt;/strong&gt; without bilateral peering agreements or proprietary protocols. This shift reflects two structural requirements of 5G that EPC could not satisfy: &lt;strong&gt;network slicing&lt;/strong&gt; — the ability to run logically independent end-to-end networks (each with its own QoS, isolation, and lifecycle) on shared physical infrastructure — and &lt;strong&gt;cloud-native deployment&lt;/strong&gt;, where NFs run as containerised microservices on commodity compute, can be horizontally scaled, and are managed by standard Kubernetes-compatible orchestration rather than vendor-specific element managers. The 5GC also enforces a hard separation between &lt;strong&gt;Control Plane (CP)&lt;/strong&gt; and &lt;strong&gt;User Plane (UP)&lt;/strong&gt; — the &lt;strong&gt;CUPS&lt;/strong&gt; principle inherited from 3GPP Release 14 and fully operationalised here — so that the &lt;strong&gt;UPF (User Plane Function)&lt;/strong&gt; handling packet forwarding, QoS enforcement, and traffic anchoring can be distributed to the edge independently of the control logic, enabling ultra-low-latency and MEC scenarios without redesigning the control plane. The architecture is access-agnostic: the same 5GC serves &lt;strong&gt;NR (New Radio)&lt;/strong&gt;, &lt;strong&gt;eLTE&lt;/strong&gt;, &lt;strong&gt;Wi-Fi (untrusted/trusted non-3GPP access)&lt;/strong&gt;, and fixed-wireless access through a unified &lt;strong&gt;N2/N3&lt;/strong&gt; reference point toward the access network and a common &lt;strong&gt;UE context&lt;/strong&gt; model in the AMF.&lt;/p&gt;</description></item></channel></rss>