RAN Architecture with NSH Packet Steering for Containerized Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The 3GPP RAN architecture is difficult to virtualize due to its reliance on infrastructure-based IP address steering, limiting the ability to fully leverage container technology and virtualization benefits.
Innovation Solution
Implementing a service-oriented approach with Network Service Header (NSH) to encapsulate networking information, allowing packet steering independent of infrastructure, and using service function chaining to enable containerized BPU, RAN, and UPF functions that remain compatible with 3GPP interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP address-based packet steering is used in 3GPP RAN architecture, then infrastructure-based routing is maintained, but virtualization capability is limited
Solution Approach 1:
The patent introduces NSH (Network Service Header) as an intermediary layer between the infrastructure and the virtualized network functions. The NSH carries service path identifiers and metadata that enable service-based routing independent of IP addresses, allowing containers to be virtualized while maintaining compatibility with existing IP-based infrastructure through the translation function
2Productivity
If containerization is implemented for BPU, RAN, and UPF, then virtualization benefits are achieved, but compatibility with non-containerized interfaces must be maintained
Solution Approach 1:
The translation function acts as an intermediary between containerized network functions and non-containerized interfaces. It translates service-based NSH packets into IP-based packets for communication with external systems, enabling containers to achieve deployment efficiency while maintaining compatibility with existing 3GPP interfaces that were not designed for containerization
3Adaptability or versatility
If service function chaining with NSH is implemented, then service-based routing is enabled, but translation overhead is introduced
Solution Approach 1:
The translation function performs packet translation in advance at the network edge, converting service-based NSH packets to IP-based packets before they need to traverse the core network. This preliminary action reduces latency by avoiding repeated translation operations downstream, while still enabling service portability through the NSH framework
Data Source
AI summary
A method for steering an original packet transmitted by a UE. The method includes receiving a first packet, wherein the first packet encapsulates the original packet. The method also includes extracting networking information (e.g., IP source, IP destination, tunnel identifier) from the first packet. The method also includes generating an SFC header (e.g., an NSH header), wherein the SFC header comprises: i) an SPI that identifies a service path and ii) metadata, wherein the metadata comprises the networking information extracted from the first packet. The method also includes generating a second packet comprising the SFC header and the original packet. The method also includes providing the second packet to an SFF that is configured to select a service path based on the SPI included in the SFC header of the second packet and forward the second packet based on the selected service path.