5G and Data Challenges
summary
Claims that 5G core data must hit <1 ms latency and often need <50 µs per I/O, with control-plane TPH rising from HSS’s ~5–20 to AMF >100 TPS, creating race conditions and interoperability gaps between stateful and stateless designs. Proposes a low-level standard called 5G DBCI (schema + SBI) and a distributed SQL deployment (Gigabyte) to place databases at edge slices, enforce strong consistency, enable zero-downtime scaling and self-healing, and close specific 3GPP race-condition failure modes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:11Evaluation of Mobile Network Generations
- 2:405G Service Based Architecture
- 3:2956 Core Functions and Their Relations
- 7:065G Data Challenges III: Throughput Falls Throughput per data size
- 7:38Flexibility in Stateless Approach is Stateful
- 11:04Protect from the Repeating Patterns of Partitioning
- 12:49Keep Balance in CAP Theorem
- 13:41Define Standards When Things are Contradicting
- 16:56Data Interoperability for 5G Core Functions
- 19:42Service Logic for 5G Core Functions yugabyteDB
- 20:56Distributed SQL Approach for 5G Core Functions
related talks
40mWhy 5G Demands a New Approach to Cybersecurity
30mKeynote: 5G is Now
55mUnleashing the 5G value
36m5G's Impact on Commerce
19mKeynote: Network of Tomorrow - 5G and Edge
25mKeynote: Five Trends Enabled By 5G That Will Change Networking Forever
21mThe Future is 5G: Unleashing Possibilities for Developers
13m5G, 15’ to understand almost everything
