Science
Serverless5GC: Private 5G Core Deployment via a Procedure-as-a-Function Architecture
Key Points
arXiv:2603.27618v2 Announce Type: replace Abstract: Open-source 5G core implementations deploy network functions as always-on processes that consume resources even when idle. This inefficiency is most problematic in private and edge deployments with sporadic traffic. Serverless5GC is an architecture that maps each 3GPP control-plane procedure to an independent Function-as-a-Service invocation, allowing scale-to-zero operation without modifying the standard N2 interface.
arXiv:2603.27618v2 Announce Type: replace
Abstract: Open-source 5G core implementations deploy network functions as always-on processes that consume resources even when idle. This inefficiency is most problematic in private and edge deployments with sporadic traffic. Serverless5GC is an architecture that maps each 3GPP control-plane procedure to an independent Function-as-a-Service invocation, allowing scale-to-zero operation without modifying the standard N2 interface. The architecture decomposes 12 network functions (3GPP Release 15-17) into 31 serverless procedures, fronted by an SCTP/NGAP proxy that bridges unmodified RAN equipment to an HTTP-based serverless backend. Evaluation against Open5GS and free5GC across five traffic scenarios (idle to 50 registrations/s burst) shows that Serverless5GC achieves median registration latency of 406-522 ms, on par with the C-based Open5GS baseline (403-606 ms), while maintaining 100% success across 3,000 registrations. A resource-time cost model shows that the serverless deployment (0.002 GB-seconds per registration) is cheaper than the always-on baseline when the cluster operates below a 0.65 duty cycle, when two or more tenants share the platform, or on managed FaaS platforms up to 595 reg/s. Under worst-case cold-start conditions where all 31 function pods are evicted simultaneously, the system sustains zero failures and converges to warm-start latency within 4-5 seconds.