Central Mobility Manager for 5G Network Slice Segregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
5G communication networks face challenges in managing mobility procedures efficiently due to the diverse requirements of different services, leading to increased signaling overhead, resource contention, and unsatisfactory user experience, especially in ultra-dense networks with frequent handovers.
Innovation Solution
Implementing a Central Mobility Manager (CMM) that creates and manages mobility schemas based on device capabilities and Network Slice Selection Assistance Information (NSSAI), segregating resources across network slices to differentiate and optimize mobility procedures for various 5G services such as eMBB, URLLC, and mMTC, thereby reducing unnecessary handovers and resource contention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a single unified mobility management approach is used for all 5G services, then the system complexity is low, but the resource utilization efficiency deteriorates due to service-specific requirements not being met
Solution Approach 1:
The patent segments mobility management into service-specific schemas: eMBB mobility schema for enhanced mobile broadband services, URLLC mobility schema for ultra-reliable low-latency communication services, and mMTC mobility schema for massive machine type communication services. Each schema contains tailored parameters and procedures optimized for its service type, allowing differentiated resource allocation and mobility handling without requiring a completely separate management system for each service.
Solution Approach 2:
The patent creates a universal mobility management framework that handles multiple service types through a common architecture. The Central Mobility Manager (CMM) serves as a multi-functional entity that can generate and manage different mobility schemas (eMBB, URLLC, mMTC) within a single system, providing both service-specific optimization and system-wide coordination through unified resource pool management.
2Reliability
If frequent handovers are performed in ultra-dense networks, then the connectivity reliability is improved, but the signaling overhead increases
Solution Approach 1:
The patent applies local quality by configuring handover parameters specifically for each service type and network slice. The URLLC mobility schema enables faster handover execution with optimized timing and threshold parameters for reliability-critical services, while the mMTC mobility schema uses more conservative handover parameters for latency-tolerant services. This localized optimization ensures each service receives appropriate handover aggressiveness without uniformly increasing signaling across all services.
Solution Approach 2:
The Central Mobility Manager performs preliminary actions by pre-generating service-specific mobility schemas before devices require them. The CMM anticipates mobility needs by maintaining ready-configured schemas for different service types, allowing devices to quickly apply appropriate handover parameters without real-time computation, thereby reducing signaling overhead while maintaining reliability.
3Ease of operation
If service-specific mobility schemas are implemented, then the user experience is improved, but the device complexity increases
Solution Approach 1:
The Central Mobility Manager acts as an intermediary that handles the complexity of service-specific mobility schema generation and management. Devices receive pre-configured schemas from the CMM based on their service requirements, eliminating the need for devices to independently determine appropriate mobility parameters. This mediator approach improves user experience through optimized service-specific handling while keeping device complexity low by offloading schema management to the network side.
Data Source
AI summary
A method and Network function for controlling an operation of a device based on a service provided to the device is provided. The method includes obtaining at least one of information about the service requested by the device, movement information of the device, or capability information of the device, determining a characteristic of the service provided to the device based on at least one of the information about the service, the movement information of the device, or the capability information of the device, generating service setting information for the service provided to the device based on the determined characteristic of the service, and transmitting, to an Access and Mobility Function (AMF), the service setting information.