RAN Slice Awareness via CN-to-RAN Identifier Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP networks face challenges in supporting network slicing within the Radio Access Network (RAN) due to unclear requirements for RAN design, resource utilization, slice awareness, traffic differentiation, isolation, and management, which hinders efficient deployment of 5G use cases with diverse performance needs.
Innovation Solution
The implementation of a method for the RAN to associate network slice identifiers by obtaining a mapping of Core Network (CN) slice identifiers to RAN slice identifiers, enabling slice registration and configuration, and providing slice-specific RAN configuration during connection setup, while minimizing signaling overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the RAN implements network slice awareness with explicit identification and mapping mechanisms, then slice isolation and traffic differentiation are improved, but device complexity and signaling overhead increase
Solution Approach 1:
The patent introduces network slice identifiers (S-NSSAI) as an intermediary element that mediates between the core network and RAN. This identifier acts as a bridge to convey slice information without requiring complex direct mapping mechanisms between core network slices and RAN resources, thereby achieving slice isolation while managing complexity through a standardized identification layer
Solution Approach 2:
The patent segments the network slicing implementation into distinct functional components: core network slice identification, RAN slice mapping, and resource allocation. By dividing the complex task of network slicing into separate modular functions, the system achieves reliable slice isolation while reducing overall system complexity through functional decomposition
2Adaptability or versatility
If the RAN supports multiple network slices with different configurations, then adaptability to diverse 5G use cases is improved, but resource management complexity increases
Solution Approach 1:
The patent implements a universal RAN configuration framework that can handle multiple network slices through a common set of tools and procedures. The RAN is configured with a universal slice identification and mapping mechanism that works across different slice types (e.g., eMBB, URLLC, mMTC), allowing the same resource management infrastructure to serve diverse 5G use cases without requiring slice-specific management systems
Solution Approach 2:
The patent utilizes parameter changes in the network slice identifier (S-NSSAI) to differentiate between various network slices. By changing the identifier parameters rather than creating fundamentally different management systems, the RAN can adapt to diverse use cases while maintaining a consistent resource management approach, thus improving versatility without proportionally increasing complexity
3Reliability
If the RAN performs slice registration and configuration during connection setup, then slice awareness is improved, but signaling overhead increases
Solution Approach 1:
The patent performs slice registration and configuration mapping actions in advance during network setup and initialization phases, rather than during every connection establishment. The RAN pre-configures slice identification and mapping tables, so that during actual user connection setup, only lightweight slice-awareness checks are needed, significantly reducing real-time signaling overhead while maintaining reliable slice awareness
Data Source
AI summary
According to some embodiments, a method for use in a core network node comprises: obtaining a mapping of core network (CN) slice identifiers to radio access network (RAN) slice identifiers; receiving a slice registration request from a user equipment (UE); determining a slice identifier associated with the slice registration request; and sending a slice registration response to the UE. The slice registration response includes the determined slice identifier. According to some embodiments, a method for use in a network node comprises obtaining a mapping of CN slice identifiers to RAN slice identifiers. The method may further comprise receiving a connection request from a UE that includes a network slice identifier; determining a RAN slice identifier based on the network slice identifier; and applying a policy of a network slice associated with the determined network slice identifier to the requested connection.