Network Node Access Request Processing for 5G Core
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current core networks designed for LTE/LTE-Advanced struggle to accommodate high-speed data services expected in 5th generation mobile communication, necessitating a redesign to efficiently manage sessions and allocate resources.
Innovation Solution
A network architecture and operating procedure that allows for the selection and switching of network slices, enabling efficient session management by sharing and allocating CP function nodes among multiple slice instances, and using service-specific and basic CP function nodes to manage user plane functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the core network is redesigned to accommodate high-speed data services in 5th generation mobile communication, then data service speed and network capacity are improved, but network architecture complexity increases
Solution Approach 1:
The core network is segmented into multiple network slices, each independently designed to handle specific service types (e.g., high-speed data, low-latency control, bulk transfer). This segmentation allows each slice to be optimized for particular performance requirements without redesigning the entire network, thus improving data service speed while managing architecture complexity through modular design.
Solution Approach 2:
The patent implements a universal session management architecture where a single session management entity can serve multiple network slices with different service requirements. This multi-functional design allows the same core network infrastructure to support diverse 5G services (enhanced mobile broadband, ultra-reliable low-latency communication, massive machine type communication) simultaneously, improving overall network capacity without proportionally increasing architecture complexity.
2Productivity
If multiple network slices are created to manage different service types, then service specialization and resource allocation efficiency are improved, but management complexity increases
Solution Approach 1:
The patent introduces a session management entity that acts as an intermediary between the access network and multiple network slices. This mediator consolidates the management of session establishment, modification, and release across all slices, reducing management complexity by providing a unified control point rather than requiring separate management for each slice while maintaining resource allocation efficiency.
Solution Approach 2:
Multiple network slices are merged under a common session management framework, where the session management entity combines handling of different service types (data services, control services, bulk transfer services) into a unified process. This merging approach maintains resource allocation efficiency by allowing simultaneous service delivery while reducing management complexity through consolidated control mechanisms.
3Productivity
If session management is centralized in a CP node, then resource allocation and session control are improved, but network flexibility and scalability are reduced
Solution Approach 1:
The session management entity is designed with dynamic capabilities that allow it to adapt its behavior based on service type and network conditions. The entity can dynamically allocate resources, modify session parameters, and scale its operations to handle varying loads across different network slices, thus maintaining session management efficiency while improving network flexibility and scalability for 5G services.
Data Source
Figure 1a~1b
Figure 2
Figure 3
AI summary
A disclosure of the present specification provides a method in which a network node processes an access request from a user equipment (UE). The method may comprise the steps of: receiving an access request message from a UE; and selecting a control plane (CP) function node on the basis of information associated with the UE, in response to the access request message. Here, the selected CP function node may perform a common or basic function, which is shared among slice instances of a network. Each slice instance may include a service-specific or non-common CP function node, which is not shared with other slice instances. The method may include a step of transferring the access request message to the selected CP function node.