πŸ“‘ Architecture Manual & Live Blueprint

5G Standalone (SA) & Service-Based Architecture (SBA) System

πŸ‘¨β€πŸ’» Designed & Engineered by Dilshad Abdulla | Designer & Software Engineer

Explore end-to-end 5G-RAN gNodeB topologies, Service-Based Architecture (SBA) REST microservices, SUCI/SUPI identity encryption, dynamic Network Slicing (eMBB, URLLC, mMTC), and high-throughput CUPS User Plane routing engines.

πŸ‘οΈ 87 Total Page Views
πŸ’³

Private Enterprise Repository β€” PayPal / Bank Wire Payment

The GitHub repository (DilshadGit/5g_system) displays the public README.md overview, 5G SA core flowcharts, and SBA specs for buyers to evaluate. Full production source code access, private repository invitation, and turn-key deployment rights require verified Commercial Payment via PayPal or Bank Wire Transfer to Lead Software Engineer & Architect Dilshad Abdulla.

🏷️ Suggested Pricing Tiers:
β€’ Source Code License: $20,000 – $35,000 USD
β€’ Cloud Setup & Deployment: +$5,000 USD
πŸ“‘ Section Pagination & Navigation

Interactive 5G System Flowchart Sections

Active: Section 1.1 of 1.8
Section 1 of 8
πŸ“– Official System Architecture Manual & Technical Spec Repository: DilshadGit/5g_system

5G Standalone (SA) Core & Service-Based Architecture (SBA)

Engineered & Authored by Dilshad Abdulla β€” Senior Software Engineer & Lead System Architect.

⚑ Executive System Overview

The 5G Standalone (SA) Core System (DilshadGit/5g_system) is a cloud-native, microservices-driven 3GPP Release 16/17 compliant mobile core platform. Built with Python 3.13, Django 5.2 Enterprise, gRPC, and Docker/Kubernetes container orchestrations, the platform implements a Service-Based Architecture (SBA) decoupling control plane functions from edge user plane routing (CUPS).

πŸ›οΈ Core Technical Architecture Stack

Component Layer Technologies & Protocols Architectural Purpose
Control Plane Core Python 3.13, Django 5.2, FastAPI, gRPC AMF, SMF, NRF, NUDM, AUSF, NSSF microservices
User Plane (UPF) DPDK, eBPF / XDP, Linux Kernel Offload Ultra-low latency N3/N4/N6 packet processing (up to 100 Gbps)
Service-Based Interface HTTP/2, RESTful JSON, TLS 1.3, OpenAPI 3.0 SBI inter-NF communication over Namf, Nsmf, Nudm, Nausf, Nnrf
Radio Access Network 5G NR, O-RAN CU/DU/RU Split, 64T64R Massive MIMO, Beamforming, Option 7-2x Front-haul
Subscriber Privacy ECIES Curve25519, SUPI/SUCI Encryption Anonymized over-the-air subscriber identifier protection
Authentication Engine 5G-AKA, EAP-AKA', Key Derivation Mutual authentication & integrity protection

πŸ“Š Master 5G SA Core Operational Flowchart

flowchart TD
    subgraph RAN ["1. Radio Access Network (5G NR)"]
        UE[5G User Equipment / SIM] -->|NR Uu Air Interface| RU[Radio Unit - RU]
        RU -->|eCPRI Fronthaul| DU[Distributed Unit - DU]
        DU -->|F1 Interface| CU[Centralized Unit - CU]
    end

    subgraph ControlPlane ["2. 5G SA Core - Service Based Architecture (SBA)"]
        CU -->|N1 / N2 NAS| AMF[Access & Mobility Mgmt Function - AMF]
        AMF <-->|Nausf| AUSF[Authentication Server Function - AUSF]
        AUSF <-->|Nudm| UDM[Unified Data Management - UDM]
        AMF <-->|Nnssf| NSSF[Network Slice Selection Function - NSSF]
        AMF <-->|Nsmf| SMF[Session Management Function - SMF]
        SMF <-->|Npcf| PCF[Policy Control Function - PCF]
        AMF & SMF <-->|Nnrf| NRF[Network Repository Function - NRF]
    end

    subgraph UserPlane ["3. CUPS User Plane Routing"]
        SMF -->|N4 PFCP Control| UPF[User Plane Function - UPF]
        CU -->|N3 GTP-U Tunnel| UPF
        UPF -->|N6 Interface| DN[Data Network / Internet / MEC Edge]
    end

    subgraph Security ["4. Security & Privacy Engine"]
        SUCI[SUCI ECIES Encryption] --> AMF
        AKA[5G-AKA Key Exchange] --> AUSF
    end
                
πŸ’Ό Enterprise Source Code Access & Turn-Key Deployment
Official License Purchase & Pro-Forma Bank Wire Invoices.
Section 1.1
πŸ‘οΈ 310 Views

1.1 Executive Summary & Architecture Overview

flowchart TD
    subgraph Overview ["5G System Architectural Pillars"]
        NR["5G New Radio (5G NR)
CU / DU / RU Split & 64T64R Massive MIMO"] SBA["Service-Based Architecture (SBA)
HTTP/2 REST APIs (Namf, Nsmf, Nudm, Nausf, Nnrf)"] CUPS["Control & User Plane Separation (CUPS)
Session Control (SMF) decoupled from Edge UPF"] SEC["SUCI / SUPI Privacy Engine
Subscription Concealed ID & 5G-AKA Auth"] end NR --- SBA SBA --- CUPS CUPS --- SEC

πŸ’‘ How It Works:

The 5G System (5GS) operates as a cloud-native, microservices-driven Service-Based Architecture (SBA). Decoupled via Control and User Plane Separation (CUPS), the platform delivers up to 20 Gbps throughput, sub-5ms latency, and multi-tenant slicing across eMBB, URLLC, and mMTC domains.

Section 1.2
πŸ‘οΈ 285 Views

1.2 End-to-End 5G System Architecture Flowchart

flowchart TD
    subgraph UE_Domain ["User Equipment (UE)"]
        UE["UE Terminal
(SUCI / 5G NR / S-NSSAI)"] end subgraph RAN_Domain ["5G Radio Access Network (5G-RAN)"] RU["Radio Unit (RU)
(RF Transceiver / Massive MIMO)"] DU["Distributed Unit (DU)
(RLC / MAC / High-PHY)"] CU["Centralized Unit (CU)
(PDCP / SDAP / RRC)"] end subgraph SBA_Control_Plane ["5G Core (5GC) Control Plane - Service Based Architecture (SBA)"] AMF["AMF
(Access & Mobility)"] SMF["SMF
(Session Management)"] NRF["NRF
(Service Discovery)"] NSSF["NSSF
(Slice Allocation)"] UDM["UDM / AUSF
(Subscriber Auth)"] PCF["PCF
(Policy & QoS)"] end subgraph User_Plane ["5G Core User Plane"] UPF["UPF
(Packet Forwarding / QoS)"] DN["Data Network / Internet
(Multi-Gigabit IP)"] end %% Air Interface Connections UE -->|NR-Uu Air Interface| RU RU -->|eCPRI / ORAN FH| DU DU -->|F1 Interface| CU %% RAN to Core Connections CU -->|N1 NAS / N2 NG-AP| AMF CU -->|N3 GTP-U| UPF %% Control Plane Microservice Interactions (HTTP/2 REST API) AMF -->|N11 REST| SMF AMF -->|N8 / N10 REST| UDM AMF -->|N22 REST| NSSF AMF -->|Nnrf REST| NRF SMF -->|Npcf REST| PCF SMF -->|Nnrf REST| NRF %% CUPS Interface SMF -->|N4 PFCP Protocol| UPF %% User Plane Data Path UPF -->|N6 IP Gateway| DN %% Styling classDef ue fill:#1e293b,stroke:#3b82f6,stroke-width:2px,color:#fff; classDef ran fill:#0f172a,stroke:#10b981,stroke-width:2px,color:#fff; classDef sba fill:#312e81,stroke:#6366f1,stroke-width:2px,color:#fff; classDef up fill:#064e3b,stroke:#10b981,stroke-width:2px,color:#fff; class UE ue; class RU,DU,CU ran; class AMF,SMF,NRF,NSSF,UDM,PCF sba; class UPF,DN up;

πŸ’‘ How It Works:

The End-to-End 5G Architecture flowchart maps packet flow from User Equipment across radio split nodes (RU → DU → CU), into the 5GC Control Plane microservices via HTTP/2 REST APIs, while keeping high-speed GTP-U traffic routed straight through the User Plane Function (UPF) to the Data Network.

Section 1.3
πŸ‘οΈ 260 Views

1.3 5G SA Registration & PDU Session Setup Flowchart

sequenceDiagram
    autonumber
    actor UE as UE Terminal
    participant gNB as gNodeB (CU/DU)
    participant AMF as AMF
    participant NRF as NRF
    participant UDM as UDM / AUSF
    participant NSSF as NSSF
    participant SMF as SMF
    participant UPF as UPF

    Note over UE, UPF: Phase 1: 5G Registration & Mutual Authentication
    UE->>gNB: 5G-RRC Setup Complete + Registration Request (SUCI)
    gNB->>AMF: NG-AP Initial UE Message (NAS Registration Request)
    AMF->>UDM: Nausf_UEAuthentication_Authenticate (SUCI)
    UDM->>UDM: Decrypt SUCI to SUPI & Generate 5G-AKA Vectors
    UDM-->>AMF: Auth Vector Response (RAND, AUTN, HXRES)
    AMF->>UE: NAS Auth-Request (RAND, AUTN)
    UE->>UE: Validate AUTN & Calculate RES_star
    UE-->>AMF: NAS Auth-Response (RES_star)
    AMF->>AMF: Verify RES_star (Authentication Success)

    Note over UE, UPF: Phase 2: Service Discovery & Slice Selection
    AMF->>NRF: Nnrf_NFDiscovery (Discover SMF Microservices)
    NRF-->>AMF: Available SMF Instances List
    UE->>AMF: PDU Session Establishment Request (S-NSSAI: eMBB)
    AMF->>NSSF: Nnssf_NSSelection_Get (Validate S-NSSAI)
    NSSF-->>AMF: Approved Network Slice Instance & Target SMF

    Note over UE, UPF: Phase 3: PDU Session & GTP-U Tunnel Creation
    AMF->>SMF: Nsmf_PDUSession_CreateSMContext
    SMF->>UPF: N4 Session Establishment Request (PFCP Rules & 5QI)
    UPF-->>SMF: N4 Session Establishment Response (Allocates N3 GTP-U IP)
    SMF-->>AMF: Nsmf_PDUSession_CreateSMContext Response
    AMF->>gNB: NG-AP PDU Session Resource Setup Request
    gNB->>UE: RRC Reconfiguration (5G Bearer Ready)
    UE-->>gNB: RRC Reconfiguration Complete

    Note over UE, UPF: Data Path Active: UE -- gNB -- UPF -- Internet
                

πŸ’‘ How It Works:

This sequence flowchart tracks registration, identity privacy encryption, mutual 5G-AKA authentication, microservice discovery, network slice allocation, and GTP-U data plane session establishment step-by-step.

Section 1.4
πŸ‘οΈ 245 Views

1.4 Network Slicing & QoS Management Flowchart

flowchart LR
    subgraph Network_Slices ["Network Slices (S-NSSAI)"]
        S1["eMBB Slice
(5QI: 6/8/9)
4K/8K Streaming, AR/VR
High Bandwidth (10+ Gbps)"] S2["URLLC Slice
(5QI: 80/82/83)
Autonomous Driving, Telemedicine
Ultra-Low Latency (1 ms)"] S3["mMTC Slice
(5QI: 70/79)
Smart Grid, Mass IoT Sensors
High Density (1M devices/sq km)"] end subgraph Slice_Allocation ["NSSF & SMF Control Engine"] NSSF_Eng["NSSF Slice Allocation
(SST: 1=eMBB, 2=URLLC, 3=mMTC)"] PCF_Pol["PCF Policy Control
(5QI QoS Mapping & Dynamic Bandwidth)"] end subgraph Data_Routing ["UPF User Plane Enforcement"] UPF_eMBB["UPF Slice Instance A
(High Throughput Pipeline)"] UPF_URLLC["UPF Slice Instance B
(Edge Compute / Low Latency Anchor)"] UPF_mMTC["UPF Slice Instance C
(Massive Session Handler)"] end S1 --> NSSF_Eng S2 --> NSSF_Eng S3 --> NSSF_Eng NSSF_Eng --> PCF_Pol PCF_Pol -->|PFCP Policy Rules| UPF_eMBB PCF_Pol -->|PFCP Policy Rules| UPF_URLLC PCF_Pol -->|PFCP Policy Rules| UPF_mMTC classDef slice1 fill:#0369a1,stroke:#38bdf8,stroke-width:2px,color:#fff; classDef slice2 fill:#b91c1c,stroke:#f87171,stroke-width:2px,color:#fff; classDef slice3 fill:#047857,stroke:#34d399,stroke-width:2px,color:#fff; class S1,UPF_eMBB slice1; class S2,UPF_URLLC slice2; class S3,UPF_mMTC slice3;

πŸ’‘ How It Works:

Network Slicing segments physical infrastructure into isolated virtual slices with tailored 5QI QoS rules enforced by PCF policy controls across separate edge UPF routing pipelines.

Section 1.5
πŸ‘οΈ 230 Views

1.5 Platform Application Flow & API Workflow

flowchart TD
    subgraph Frontend ["CMS Admin & Dashboard Web Interface"]
        UI_Dash["Dashboard Controller
(/)"] UI_Sub["Subscriber Management
(/subscribers)"] UI_Slice["Network Slice Hub
(/slices)"] UI_Calc["Throughput Calculator
(/calculator)"] UI_Admin["CMS Documentation Viewer
(/admin)"] end subgraph API_Layer ["REST API Engine (app.py)"] API_Sub["/api/subscribers"] API_Upgrade["/api/subscribers/:id/upgrade"] API_Slice["/api/slices"] API_Calc["/api/calculator/compute"] API_Spec["/api/spectrum"] end subgraph Service_Layer ["Core Python Service Modules"] Sub_Svc["subscriber_service.py
(Subscriber Lifecycle & Upgrades)"] Slice_Svc["slice_service.py
(S-NSSAI Allocation & Monitor)"] Calc_Svc["throughput_calc.py
(5G NR Speed & Latency Math Engine)"] Spec_Svc["spectrum_service.py
(Spectrum Refarming Roadmap)"] end subgraph Documentation_Engine ["CMS Docs Renderer (accounts/views.py)"] Docs_Scan["Possible Dirs Scanner
(docs/ *.md)"] MD_Render["Markdown Renderer
(index_cms.html)"] end UI_Dash --> API_Sub UI_Dash --> API_Slice UI_Sub --> API_Upgrade UI_Slice --> API_Slice UI_Calc --> API_Calc API_Sub --> Sub_Svc API_Upgrade --> Sub_Svc API_Slice --> Slice_Svc API_Calc --> Calc_Svc API_Spec --> Spec_Svc UI_Admin --> Docs_Scan --> MD_Render classDef fe fill:#1e1b4b,stroke:#818cf8,stroke-width:2px,color:#fff; classDef api fill:#4c1d95,stroke:#a78bfa,stroke-width:2px,color:#fff; classDef svc fill:#065f46,stroke:#34d399,stroke-width:2px,color:#fff; class UI_Dash,UI_Sub,UI_Slice,UI_Calc,UI_Admin fe; class API_Sub,API_Upgrade,API_Slice,API_Calc,API_Spec api; class Sub_Svc,Slice_Svc,Calc_Svc,Spec_Svc svc;

πŸ’‘ How It Works:

The platform architecture routes web UI interactions through clean REST API endpoints in app.py to underlying modular services (subscriber_service, slice_service, throughput_calc, spectrum_service) and CMS markdown engines.

Section 1.6
πŸ‘οΈ 218 Views

1.6 Core 5G Architectural Component Matrix

flowchart TD
    UE[User Equipment] <-->|NR-Uu| gNB[gNodeB CU/DU/RU]
    gNB <-->|N1 NAS / N2 NG-AP| AMF[AMF - Access & Mobility]
    gNB <-->|N3 GTP-U| UPF[UPF - User Plane Function]
    AMF <-->|N11 HTTP/2| SMF[SMF - Session Management]
    AMF <-->|N8 / N10| UDM[UDM / AUSF Subscriber Vault]
    AMF <-->|N22| NSSF[NSSF Slice Selection]
    AMF <-->|Nnrf| NRF[NRF Service Registry]
    SMF <-->|Npcf| PCF[PCF Policy Control]
    SMF <-->|N4 PFCP Protocol| UPF
    UPF <-->|N6 IP Gateway| DN[Data Network / Internet]
                

πŸ’‘ How It Works:

The Architectural Component Matrix provides full protocol transparency for every node in the 5G core control plane and user plane forwarding pipeline.

Section 1.7
πŸ‘οΈ 205 Views

1.7 Operational Advice & Technical Best Practices

flowchart TD
    subgraph Control_Plane ["Centralized Cloud Control Plane"]
        AMF_CP["AMF Microservice"]
        SMF_CP["SMF Microservice"]
        NRF_CP["NRF Registry"]
        UDM_CP["UDM / AUSF Vault"]
    end

    subgraph Edge_MEC ["Edge Computing / Multi-Access Edge (MEC)"]
        UPF_MEC["Edge UPF Router
(< 5ms Latency for URLLC)"] Local_App["MEC Edge Application"] end AMF_CP --> SMF_CP SMF_CP -->|N4 PFCP Signal| UPF_MEC UPF_MEC --> Local_App

πŸ’‘ How It Works:

Operational best practices detail how MEC deployment, HTTP/2 distributed tracing, subscriber identity protection (SUCI), and spectrum refarming are realized in production 5G networks.

Section 1.8
πŸ‘οΈ 192 Views

1.8 Summary of File Location & Access

flowchart TD
    Root["5g_system/"] --> Docs["docs/"]
    Root --> Services["services/"]
    Root --> Templates["templates/"]
    Root --> AppPy["app.py"]

    Docs --> ArchMD["5g_system_architecture.md"]
    Docs --> AdvMD["5g_system_advice.md"]

    Services --> SubSvc["subscriber_service.py"]
    Services --> SliceSvc["slice_service.py"]
    Services --> CalcSvc["throughput_calc.py"]
    Services --> SpecSvc["spectrum_service.py"]
                

πŸ’‘ How It Works:

File locations and documentation paths provide full reference access for local development and CMS document browsing.