Session Management Network Element for Mobile Application Relocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile communication technologies lack a solution for handling application sessions when a terminal moves, particularly for applications that do not support relocation, as they require connection to an AF server at the old location, which may not be deployed at the new location or support context transfer.
Innovation Solution
A session processing method that selects appropriate network devices and splitting policies to route data flows for applications that do not support relocation, using multiple session management and user plane network elements to ensure continuous service by establishing new sessions and managing data flow splitting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the terminal moves to a new location, then the terminal can access local services, but applications that do not support relocation cannot connect to their AF servers
Solution Approach 1:
The patent segments the session management into multiple session management network elements (first SMF, second SMF, third SMF) that can independently handle different data flows. The first SMF manages the original session, while the second and third SMFs handle relocated sessions for different applications, allowing the terminal to maintain connections with both relocated and non-relocated applications simultaneously.
Solution Approach 2:
The patent applies local quality by deploying different session management strategies for different applications based on their relocation capabilities. Applications supporting relocation are handled by SMFs that can transfer context to new locations, while applications not supporting relocation are handled by SMFs that maintain original session parameters, optimizing service continuity for each application type.
2Adaptability or versatility
If a single session management network element is used, then the session management is simple, but it cannot simultaneously support both relocated and non-relocated applications
Solution Approach 1:
The session management function is segmented into multiple specialized SMF instances. The first SMF maintains the original session for non-relocatable applications, while the second and third SMFs are created to handle relocated sessions for different applications. This segmentation allows each SMF to be optimized for its specific function while collectively supporting diverse application requirements.
Solution Approach 2:
The patent creates a universal session management architecture where multiple SMF instances work together to handle both relocated and non-relocated applications. Each SMF can be configured with specific capabilities, but the overall system provides universal support for various application types through coordinated operation of multiple SMFs.
3Reliability
If the AF server is not deployed at the new location, then the terminal cannot access the application service, but deploying multiple AF servers increases network complexity
Solution Approach 1:
The patent introduces session management network elements as intermediaries between the terminal and AF servers. These SMFs manage the complexity of multi-location service delivery by handling session establishment, modification, and teardown, and by coordinating with multiple AF servers without requiring the terminal to directly manage the complexity of server locations and session states.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
This application provides a session processing method and an apparatus. The method includes: receiving, by an access management network element, access point information that is of an application of a first session and that is from a first session management network element; receiving a request message from a terminal, where the request message includes an identifier of the first session and an identifier of a second session; selecting a second session management network element based on the access point information of the application; selecting a third session management network element; sending a first request message to the second session management network element, where the first request message requests to establish the second session; and/or sending a second request message to the third session management network element, where the second request message requests to establish the second session. Based on this solution, the access management network element selects the second session management network element based on the received access point information of the application of the first session. The access point information may be from an AF server that corresponds to the application and that does not support application relocation. Therefore, the selected second session management network element may provide a service for the AF server.