Service Chain Routing via Directory Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communication networks, particularly in 4G and 5G architectures, there is a challenge in directing user packets to the correct service function instances associated with user plane anchors, as conventional methods lack awareness of the packet's destination, leading to sub-optimal routing and increased latency due to unawareness of the user plane anchor locations by customer premises equipment (CPEs) and user equipment (UEs).
Innovation Solution
The solution involves configuring directory records to include indications of service chain locations and IP addresses, allowing CPEs and UEs to obtain and use these indications to direct packets to the appropriate service function instances associated with their user plane anchors, using methods like DNS, DHCPv6, and NAS signaling, ensuring packets are routed through the closest or optimally associated service chains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If conventional routing methods are used without directory records, then device complexity is reduced, but routing optimality deteriorates leading to sub-optimal packet delivery
Solution Approach 1:
The patent applies preliminary action by pre-configuring directory records with service chain location information and IP addresses before packet transmission. The CPE/UE obtains these indications in advance through DNS, DHCPv6, or NAS signaling, enabling optimal routing decisions without real-time computation complexity.
Solution Approach 2:
The patent introduces directory records as an intermediary between the network infrastructure and CPE/UE devices. These records mediate the routing process by providing pre-processed location information, eliminating the need for complex real-time path calculations at the edge devices.
2Loss of time
If packets are routed without awareness of user plane anchor locations, then device complexity is minimized, but latency increases due to sub-optimal routing paths
Solution Approach 1:
The system performs preliminary action by obtaining service chain location indications and IP addresses before packet transmission through DNS queries, DHCPv6 interactions, or NAS signaling. This advance preparation eliminates real-time routing computation delays while maintaining operational simplicity at the CPE/UE level.
Solution Approach 2:
The CPE/UE performs self-service routing by autonomously obtaining and using directory record information to direct packets to the appropriate service function instances. This self-directed approach reduces latency without requiring complex centralized control for each packet routing decision.
3Loss of information
If service chain locations are not indicated in directory records, then information complexity is reduced, but service function instance identification becomes impossible
Solution Approach 1:
The patent applies universality by making directory records serve multiple functions: storing service chain location indications, containing IP addresses for service function instances, and enabling both DNS and DHCPv6 protocols to utilize the same data structure. This multi-functionality maximizes information utility without proportionally increasing complexity.
Solution Approach 2:
The patent changes the parameter structure of directory records by incorporating specific fields for service chain location indications and associated IP addresses. This parameter transformation enables the records to convey precise routing information while maintaining a structured format that can be processed by existing network protocols.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one embodiment an apparatus comprising networking circuitry, and processing circuitry, the processing circuitry adapted to receive, via the networking circuitry, at least one indication of at least one service chain that is associated with a user plane anchor selected for anchoring a user equipment, out of a plurality of service chains in a network, the apparatus being the user equipment or being a host behind the user equipment, and the at least one service chain being fewer in number than the plurality of service chains, and use the at least one indication to direct at least one packet to at least one service function in the at least one service chain.