Core Network Switching via Application Function Anchor
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies fail to seamlessly switch between on-premises and on-cloud core network installations, making it difficult to meet varying network quality requirements for user services.
Innovation Solution
A control device with a control unit that acquires a switching request based on measured latency and switches the core network from an on-cloud installation to an on-premises installation using an application function as an anchor, allowing seamless switching between different network slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If on-premises installation is used, then latency is reduced and deployment near base station is achieved, but device complexity and deployment cost increase
Solution Approach 1:
The patent implements dynamic switching between on-premises and on-cloud core network installations based on real-time latency measurements and service requirements. The system can transition from a static deployment choice to a dynamic, adaptable architecture that selects the optimal installation mode depending on current network conditions and service needs, thereby reducing latency for time-sensitive applications while maintaining cost-effectiveness for other services.
Solution Approach 2:
The system changes the deployment parameter (on-premises vs. on-cloud) based on measured latency parameters and service quality requirements. By monitoring latency as a key parameter and adjusting the core network installation location accordingly, the system optimizes performance for different service scenarios without requiring permanent complex on-premises deployment for all cases.
2Ease of manufacture
If on-cloud installation is used, then cost is reduced and computing capability is enhanced, but latency increases and deployment near user is lost
Solution Approach 1:
The system dynamically adjusts the core network deployment location between on-cloud and on-premises based on real-time latency measurements and service requirements. This dynamic approach allows the system to leverage cost-effective on-cloud installation for non-time-critical services while switching to low-latency on-premises deployment when required, optimizing both cost and performance across different service scenarios.
Solution Approach 2:
The patent changes the deployment parameter (cloud vs. on-premises) based on latency parameter thresholds and service quality requirements. By monitoring latency as a key performance indicator and adjusting the installation location parameter accordingly, the system achieves cost efficiency through cloud deployment while ensuring low latency for services that require it.
3Device complexity
If core network switching technology is not available, then system simplicity is maintained, but seamless switching between installation modes cannot be achieved
Solution Approach 1:
The patent introduces a control device as an intermediary that manages the switching between on-premises and on-cloud core network installations. This mediator monitors latency, receives switching requests, and coordinates the transition process, thereby enabling seamless switching capability without requiring complex modifications to the existing simple network architecture. The control device acts as a bridge that adds adaptability while maintaining overall system simplicity.
Solution Approach 2:
The system segments the core network functionality into switchable components that can be independently deployed in on-premises or on-cloud installations. By dividing the core network into modular, switchable units rather than a monolithic structure, the system enables seamless switching between installation modes while maintaining manageable complexity through modular design.
Data Source
AI summary
A control device (15a) includes a control unit configured to: acquire a switching request based on a latency measured in a first application function (AF) (30) disposed in a first network slice (5) or in a terminal device (40) communicating with the first AF (30); and switch, based on the acquired switching request, a core network to be connected to the terminal device (40) from a first core network (10a) disposed in the first network slice (5) to a second core network (10b) disposed in a second network slice (6) by using the first AF (30), or using the first AF (30) and the terminal device (40), as an anchor.