<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>5g on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/5g/</link><description>Recent content in 5g 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/5g/index.xml" rel="self" type="application/rss+xml"/><item><title>3GPP SCAS</title><link>https://lesitedefrancois.be/en/compliance/scas/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/compliance/scas/</guid><description>&lt;p&gt;&lt;strong&gt;3GPP Security Assurance Specifications (SCAS)&lt;/strong&gt; are technical specifications developed by &lt;strong&gt;3GPP&amp;rsquo;s SA3 working group&lt;/strong&gt; (Security) that define security requirements and associated test cases for specific network product classes — each 3GPP-defined network function (AMF, SMF, UPF, gNB, MME, etc.) has its own SCAS document. 3GPP is the &lt;strong&gt;international&lt;/strong&gt; standards body responsible for mobile telecommunications standards (comprising seven organizational partners covering Europe, US, China, Japan, Korea, India), making SCAS a globally recognized specification set rather than a national or regional scheme. Each SCAS document follows a structured approach: it identifies the &lt;strong&gt;assets&lt;/strong&gt; of the network product class that require protection, performs a &lt;strong&gt;threat analysis&lt;/strong&gt; describing how those assets can be exploited, defines &lt;strong&gt;security requirements&lt;/strong&gt; (objectives) that mitigate the identified threats, and specifies concrete &lt;strong&gt;test cases&lt;/strong&gt; to verify that a product implementation meets those requirements. SCAS specifications serve as the technical foundation for the &lt;strong&gt;GSMA NESAS&lt;/strong&gt; scheme — when a vendor submits a network product for NESAS evaluation, accredited test laboratories evaluate it against the applicable SCAS test cases. Compliance is &lt;strong&gt;voluntary&lt;/strong&gt; (there is no legal mandate to pass SCAS tests), but SCAS/NESAS evaluation results are increasingly used as a procurement requirement by telecom operators and are referenced by the EU 5G Security Toolbox and national security assessments. The list of adopted SCAS documents is maintained by the GSMA in FS.63 and continues to expand as 3GPP defines new network functions.&lt;/p&gt;</description></item><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><item><title>AI-RAN Alliance</title><link>https://lesitedefrancois.be/en/telco/ai-ran-alliance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/ai-ran-alliance/</guid><description>&lt;p&gt;The &lt;strong&gt;AI-RAN Alliance&lt;/strong&gt; is a global industry consortium, launched at &lt;strong&gt;MWC Barcelona in February 2024&lt;/strong&gt; and governed by a &lt;strong&gt;Technical Steering Committee (TSC)&lt;/strong&gt;, whose mission is to accelerate the integration of artificial intelligence into Radio Access Networks and to define what an &lt;strong&gt;AI-native RAN&lt;/strong&gt; looks like in practice for 5G Advanced and 6G. The alliance deliberately positions itself as &lt;strong&gt;neither a marketing organisation nor a demo factory&lt;/strong&gt;: it pursues pioneering, pre-competitive work — reference architectures, blueprints, and &lt;strong&gt;credible benchmarking&lt;/strong&gt; — without getting mired in formal standards processes or IP negotiations. Its work spans three complementary objectives — &lt;strong&gt;AI-for-RAN&lt;/strong&gt; (using AI/ML to improve RAN performance and efficiency), &lt;strong&gt;AI-and-RAN&lt;/strong&gt; (co-locating RAN and AI workloads on shared accelerated infrastructure), and &lt;strong&gt;AI-on-RAN&lt;/strong&gt; (hosting tenant-facing AI applications at the network edge for differentiated, monetisable connectivity). Founding members include &lt;strong&gt;Ericsson&lt;/strong&gt;, &lt;strong&gt;Nokia&lt;/strong&gt;, &lt;strong&gt;NVIDIA&lt;/strong&gt;, &lt;strong&gt;T-Mobile&lt;/strong&gt;, &lt;strong&gt;SoftBank&lt;/strong&gt;, &lt;strong&gt;Samsung&lt;/strong&gt;, &lt;strong&gt;AWS&lt;/strong&gt;, &lt;strong&gt;Microsoft&lt;/strong&gt;, and &lt;strong&gt;Arm&lt;/strong&gt;; membership grew from a handful at launch to &lt;strong&gt;130+ organisations&lt;/strong&gt; by MWC 2026, spanning operators, NEPs, hyperscalers, silicon vendors, universities, and government research bodies across more than 17 countries.&lt;/p&gt;</description></item><item><title>Edge Computing</title><link>https://lesitedefrancois.be/en/telco/edge-computing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/edge-computing/</guid><description>&lt;p&gt;&lt;strong&gt;Edge computing&lt;/strong&gt; in telecommunications places &lt;strong&gt;compute, storage, and application execution&lt;/strong&gt; close to users and devices — at &lt;strong&gt;cell sites&lt;/strong&gt;, &lt;strong&gt;regional points of presence&lt;/strong&gt;, or &lt;strong&gt;on-prem enterprise locations&lt;/strong&gt; — rather than only in distant &lt;strong&gt;hyperscale data centres&lt;/strong&gt;. The goal is to reduce &lt;strong&gt;end-to-end latency&lt;/strong&gt;, limit &lt;strong&gt;backhaul&lt;/strong&gt; load, satisfy &lt;strong&gt;data residency&lt;/strong&gt;, and enable &lt;strong&gt;real-time&lt;/strong&gt; applications (AR/VR, industrial control, V2X, video analytics) that are impractical with &lt;strong&gt;50–100 ms&lt;/strong&gt; round trips to central clouds. In &lt;strong&gt;5G&lt;/strong&gt;, edge is tightly coupled to the &lt;strong&gt;user plane&lt;/strong&gt;: a &lt;strong&gt;local UPF&lt;/strong&gt; on &lt;strong&gt;N6&lt;/strong&gt; breakout forwards traffic to an &lt;strong&gt;edge data network (DN)&lt;/strong&gt; hosting &lt;strong&gt;MEC applications&lt;/strong&gt; without hairpinning through the operator’s core hub.&lt;/p&gt;</description></item><item><title>EU5G Certification Scheme</title><link>https://lesitedefrancois.be/en/compliance/eu5g/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/compliance/eu5g/</guid><description>&lt;p&gt;The &lt;strong&gt;EU5G cybersecurity certification scheme&lt;/strong&gt; is a certification framework being developed under the EU Cybersecurity Act (Regulation 2019/881), intended to provide harmonized security assurance for 5G network products and components across the European Union. ENISA established an Ad Hoc Working Group (AHWG) on EU5G in Q4 2021 following a European Commission request. As of mid-2026, the scheme &lt;strong&gt;has not been formally adopted&lt;/strong&gt; and no complete public draft is available — making it the least mature of the three schemes requested under the CSA (after EUCC, adopted in January 2024, and EUCS, still stalled). Current work has focused on specific components: in June 2024, ENISA launched a public consultation on technical specifications for eUICC (embedded Universal Integrated Circuit Card) certification, which will be handled under the existing EUCC framework rather than a new standalone scheme. A broader EU NESAS scheme for 5G network products is under development, leveraging the existing GSMA NESAS/3GPP SCAS methodology. The scheme is expected to be &lt;strong&gt;voluntary&lt;/strong&gt; once adopted, with assurance levels aligned to the CSA&amp;rsquo;s basic/substantial/high structure. Its practical significance will be shaped by the revised Cybersecurity Act (CSA2), proposed in January 2026, which strengthens ENISA&amp;rsquo;s mandate and may provide additional impetus for adoption.&lt;/p&gt;</description></item><item><title>GSMA NESAS</title><link>https://lesitedefrancois.be/en/compliance/gsma-nesas/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/compliance/gsma-nesas/</guid><description>&lt;p&gt;The &lt;strong&gt;GSMA Network Equipment Security Assurance Scheme (NESAS)&lt;/strong&gt; is a &lt;strong&gt;voluntary, global&lt;/strong&gt; security assurance framework jointly led by the &lt;strong&gt;GSMA&lt;/strong&gt; and &lt;strong&gt;3GPP&lt;/strong&gt;. It was established to provide a universal, industry-driven security evaluation for mobile network equipment — primarily targeting 4G/LTE and 5G infrastructure — that avoids the fragmentation of country-specific security requirements. NESAS operates through two complementary components: first, an &lt;strong&gt;audit of the vendor&amp;rsquo;s development and product lifecycle processes&lt;/strong&gt; (covering secure design, implementation, testing, and vulnerability handling), conducted by GSMA-appointed auditing organizations; second, a &lt;strong&gt;product evaluation&lt;/strong&gt; against 3GPP-defined Security Assurance Specifications (SCAS), performed by ISO/IEC 17025 accredited security test laboratories. The GSMA manages scheme governance (accreditation, dispute resolution, publication of results), while 3GPP&amp;rsquo;s SA3 working group defines the technical security requirements and test cases in SCAS documents. The scheme is currently at &lt;strong&gt;NESAS v3.0&lt;/strong&gt; (specifications published early 2025), which introduces revised security requirements and expands coverage to include virtualized network functions. NESAS is &lt;strong&gt;voluntary&lt;/strong&gt; — no government mandates it — but it is increasingly referenced by national 5G security reviews and procurement requirements (including the EU 5G Toolbox), and major operators use NESAS assessment results as a procurement criterion. Evaluated vendors and their results are publicly listed on the GSMA website.&lt;/p&gt;</description></item><item><title>O-RAN Alliance</title><link>https://lesitedefrancois.be/en/telco/o-ran-alliance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/o-ran-alliance/</guid><description>&lt;p&gt;The &lt;strong&gt;O-RAN Alliance&lt;/strong&gt; is an operator-led global industry alliance, formed in February 2018 through the merger of the C-RAN Alliance and the xRAN Forum, whose mission is to reshape how radio access networks are designed, built, and operated. Where traditional RAN stacks are vertically integrated — baseband software, radio hardware, and management tools delivered as a single vendor bundle — O-RAN promotes &lt;strong&gt;disaggregation&lt;/strong&gt;: separating the RAN into open, standardised functional blocks connected by published interfaces, so a mobile operator can mix DU, CU, RU, and management software from different suppliers. The alliance&amp;rsquo;s core objectives are &lt;strong&gt;multi-vendor interoperability&lt;/strong&gt;, &lt;strong&gt;cloud-native and virtualised deployment&lt;/strong&gt;, &lt;strong&gt;programmable RAN intelligence&lt;/strong&gt; through the RIC (RAN Intelligent Controller), and &lt;strong&gt;operational automation&lt;/strong&gt; at scale. These goals address vendor lock-in, slow innovation cycles, and the cost structure of legacy RAN, while aligning with 5G and beyond requirements for network slicing, edge deployment, and AI/ML-driven optimisation.&lt;/p&gt;</description></item><item><title>Private 5G</title><link>https://lesitedefrancois.be/en/telco/private-5g/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/private-5g/</guid><description>&lt;p&gt;&lt;strong&gt;Private 5G&lt;/strong&gt; (also &lt;strong&gt;non-public 5G&lt;/strong&gt;, &lt;strong&gt;dedicated 5G&lt;/strong&gt;, or &lt;strong&gt;campus/industrial 5G&lt;/strong&gt;) denotes &lt;strong&gt;3GPP-conformant 5G systems&lt;/strong&gt; operated for a &lt;strong&gt;defined organisation or site&lt;/strong&gt; — factory, port, mine, hospital, stadium, or utility — rather than as a nationwide public mobile service. &lt;strong&gt;3GPP Release 16+&lt;/strong&gt; formalised &lt;strong&gt;Non-Public Networks (NPN)&lt;/strong&gt; with two principal models: &lt;strong&gt;Standalone NPN (SNPN)&lt;/strong&gt; — an isolated PLMN (dedicated &lt;strong&gt;MCC/MNC&lt;/strong&gt; or &lt;strong&gt;PLMN ID&lt;/strong&gt;) with its own &lt;strong&gt;5GC and NG-RAN&lt;/strong&gt;; and &lt;strong&gt;Public Network Integrated NPN (PNI-NPN)&lt;/strong&gt; — a &lt;strong&gt;slice&lt;/strong&gt; or dedicated &lt;strong&gt;DNN&lt;/strong&gt; on a &lt;strong&gt;public operator’s 5G&lt;/strong&gt; with contractual isolation. Private 5G delivers &lt;strong&gt;URLLC-capable&lt;/strong&gt; connectivity, &lt;strong&gt;local breakout&lt;/strong&gt; (traffic stays on-site via &lt;strong&gt;local UPF&lt;/strong&gt;), &lt;strong&gt;deterministic QoS&lt;/strong&gt;, and &lt;strong&gt;control&lt;/strong&gt; over upgrades and security policies — advantages over &lt;strong&gt;Wi-Fi 6/7&lt;/strong&gt; in mobility, scheduling, and industrial &lt;strong&gt;TSN&lt;/strong&gt; integration scenarios, at higher cost and regulatory complexity.&lt;/p&gt;</description></item><item><title>PTP (Precision Time Protocol)</title><link>https://lesitedefrancois.be/en/telco/ptp-precision-time-protocol/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/ptp-precision-time-protocol/</guid><description>&lt;p&gt;&lt;strong&gt;Precision Time Protocol (PTP)&lt;/strong&gt;, standardised as &lt;strong&gt;IEEE 1588&lt;/strong&gt;, distributes a common &lt;strong&gt;reference time&lt;/strong&gt; across packet networks so that distributed nodes share a clock with &lt;strong&gt;sub-microsecond to nanosecond&lt;/strong&gt; accuracy — far beyond what &lt;strong&gt;NTP&lt;/strong&gt; typically achieves over IP. PTP operates in a &lt;strong&gt;master–slave hierarchy&lt;/strong&gt;: a &lt;strong&gt;Grandmaster Clock (GM)&lt;/strong&gt; holds traceability to &lt;strong&gt;GNSS&lt;/strong&gt; (GPS, Galileo, etc.) or a &lt;strong&gt;Primary Reference Time Clock (PRTC)&lt;/strong&gt;; &lt;strong&gt;Boundary Clocks (BC)&lt;/strong&gt; terminate and regenerate timing on hops; &lt;strong&gt;Transparent Clocks (TC)&lt;/strong&gt; correct residence time in switches without terminating the protocol. Messages (&lt;strong&gt;Sync&lt;/strong&gt;, &lt;strong&gt;Follow_Up&lt;/strong&gt;, &lt;strong&gt;Delay_Req/Resp&lt;/strong&gt;, optional &lt;strong&gt;Announce&lt;/strong&gt;) implement a &lt;strong&gt;delay request–response&lt;/strong&gt; mechanism to estimate path asymmetry and offset each &lt;strong&gt;Ordinary Clock (OC)&lt;/strong&gt; slave relative to the grandmaster.&lt;/p&gt;</description></item></channel></rss>