IPv6 Slice Identifier Encoding for Low-Latency Packet Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network slicing implementations require deep packet inspection for slice identification by transport domain elements, leading to increased latency and computational costs.
Innovation Solution
Encoding a slice identifier, such as S-NSSAI, within an IPv6 address allows transport domain elements to identify network slices without deep packet inspection, enabling reduced latency and computational costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If deep packet inspection is performed for slice identification, then network slicing can be implemented, but latency increases and computational costs increase
Solution Approach 1:
The slice identifier is extracted from the packet payload and placed in the packet header (specifically in the IPv6 address or extension header). This allows transport domain elements to identify network slices by examining only the header without performing deep packet inspection of the payload, thereby reducing latency and computational costs while maintaining network slicing capability
Solution Approach 2:
The slice identifier is pre-encoded into the packet header (IPv6 address) before the packet is transmitted through the network. This preliminary encoding ensures that transport domain elements can immediately identify the network slice upon receiving the packet header, eliminating the need for time-consuming deep packet inspection later in the processing chain
2Adaptability or versatility
If deep packet inspection is performed for slice identification, then network slicing can be implemented, but computational costs increase
Solution Approach 1:
The slice identifier is extracted from the packet payload and placed in the packet header (specifically in the IPv6 address or extension header). This allows transport domain elements to identify network slices by examining only the header without performing deep packet inspection of the payload, thereby reducing latency and computational costs while maintaining network slicing capability
Solution Approach 2:
Instead of performing complete deep packet inspection of the entire packet, the system performs only partial inspection by examining the packet header where the slice identifier is encoded. This partial action is sufficient for slice identification purposes and significantly reduces computational overhead and energy consumption
3Loss of time
If slice identifier is encoded in IPv6 address, then latency is reduced, but device complexity increases
Solution Approach 1:
The slice identifier is nested within the existing IPv6 address structure by encoding it into specific fields of the IPv6 address (such as the flow label or other reserved fields). This nesting approach allows the slice identifier to be carried along with the packet routing information without requiring separate signaling mechanisms, and the encoding/decoding can be performed using standard IPv6 processing functions already present in network devices
Data Source
AI summary
Embodiments described herein allow reduced latency and computational costs by identifying a slice associated with a packet and determining an action to be performed with respect to the packet without having to perform deep packet inspection on the packet. An aspect of the present disclosure is a method comprising receiving a packet including a slice identifier corresponding to a slice of a network, the slice identifier having a plurality of bits; determining a bit value for each bit in a subset of the plurality of bits; and performing an action with respect to the packet based on the bit value of at least one bit in the subset.