BGP Service-to-Slice Routing for Accurate 5G Traffic Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in the 5G network era is efficiently allocating different services to network slices that meet diverse service requirements such as latency, bandwidth, security, and reliability across various devices and scenarios.
Innovation Solution
A routing information transmission method and apparatus that utilizes Border Gateway Protocol (BGP) routing information to determine forwarding table entries based on service identifiers and network slice identifiers, enabling service traffic to be forwarded through appropriate network slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slicing technology is used to divide physical network into virtual networks, then the network can flexibly respond to different application scenarios, but it becomes challenging to allocate different services to appropriate network slices that meet service requirements
Solution Approach 1:
The patent applies preliminary action by pre-establishing the correspondence between service identifiers and network slice identifiers in the routing information before traffic forwarding. The BGP routing information is updated in advance to include this mapping relationship, enabling network devices to automatically determine the appropriate network slice for each service without complex real-time allocation decisions.
Solution Approach 2:
The patent uses service identifiers as an intermediary element that bridges service requirements and network slice selection. By introducing this intermediate mapping layer in the routing information, the system simplifies the allocation process while maintaining flexibility, as devices can follow the pre-defined service-to-slice mappings without needing to understand complex service requirements.
2Reliability
If BGP routing information is updated to include service identifiers and network slice identifiers, then service traffic can be forwarded through appropriate network slices, but the routing information structure becomes more complex
Solution Approach 1:
The patent applies universality by extending the existing BGP routing information structure to serve multiple functions. The same routing information carries both traditional routing parameters and the new service identifier to network slice identifier correspondence. This multi-functional approach ensures reliable service traffic forwarding while avoiding the need for separate complex routing protocols.
Solution Approach 2:
The patent implements nesting by embedding the service identifier and network slice identifier correspondence within the existing BGP routing information structure. Rather than creating a separate complex system, the patent nests the service allocation information inside the familiar BGP framework, maintaining structural integrity while adding functionality.
3Manufacturing precision
If network devices determine forwarding table entries based on service identifiers and network slice identifiers, then service requirements can be met, but the processing complexity increases
Solution Approach 1:
The patent applies self-service by enabling network devices to automatically determine forwarding table entries using the service identifier to network slice identifier mapping provided in the routing information. Devices independently perform the matching and determination without requiring centralized control or complex external coordination, achieving precise service requirement fulfillment through autonomous operation.
Data Source
AI summary
A routing information transmission method includes before forwarding a service traffic packet, a first network device receives first Border Gateway Protocol (BGP) routing information from a second network device to determine a first forwarding table entry based on a service identifier and an identifier of a first network slice that are in the first BGP routing information. The first forwarding table entry indicates to forward, to the second network device using the first network slice, the service traffic. When receiving the service traffic packet corresponding to the service identifier, the first network device determines the first network slice based on the first forwarding table entry, and then sends the service traffic to the second network device using the first network slice.