Session synchronization method, device and system and readable storage medium

By determining the valid session set of user equipment in the 5GC core network and deleting invalid sessions, combined with the collaborative work of AMF, SMF, and UPF and the session synchronization functions, the problems of session out-synchronization and resource occupation between 5GC network elements are solved, and session synchronization is realized and improve service quality.

CN118945903APending Publication Date: 2024-11-12CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411074221.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-06
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the 5GC core network, due to message transmission failure, network element processing exceptions, terminal failure and other reasons, residual garbage sessions accumulate in a single network element, resulting in the out-of-synchronization of the sessions between network elements and occupying system resources.

Method used

By determining the user equipment UE is considered to be a valid session set and deleting invalid sessions, using the collaborative work between AMF, SMF, and UPF, setting a timer and notification mechanism to ensure that invalid sessions are cleaned up in time, and introducing session synchronization function to monitor and Compare the sessions of each network element, filter out invalid sessions and delete them.

Benefits of technology

It realizes session synchronization between various network elements of 5GC, releases system resources, improves service quality and user experience, and solves the problems of session out-of-synchronization and resource occupation caused by garbage conversations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945903A_ABST
    Figure CN118945903A_ABST
Patent Text Reader

Abstract

The invention provides a session synchronization method, device and system and a readable storage medium, and the method comprises the steps: determining a session set which regards UE as valid, and deleting invalid sessions; and sending the session set in which the UE is regarded as valid to the SMF, so that the SMF judges whether each session stored by the SMF about the UE is the session in which the UE is regarded as valid, deletes the corresponding invalid session, and sends the session set in which the UE is regarded as valid to the UPF, so that the UPF judges whether each session stored by the UPF about the UE is the session in which the UE is regarded as valid, and deletes the corresponding invalid session. According to the method, the device, the system and the readable storage medium, the problems that some residual junk sessions are gradually accumulated in a single network element in the 5GC due to message transmission failure, network element processing abnormity, terminal failure and the like in the actual operation of the 5GC core network, the sessions among the network elements are asynchronous due to the existence of the junk sessions, and the service life of the 5GC core network is influenced can be solved. And system resources of the network element are occupied.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of network technology, and in particular to a session synchronization method, device, system and readable storage medium. Background Art

[0002] In order to provide users with data, voice and other services, 5GC (5G Core) needs to establish a control plane signaling connection for the user and create a PDU (Protocol Data Unit) session. Figure 1 As shown in the figure, when the user needs to transmit data, AMF (Access and Mobility Management Function, Access and Mobility Management Function) / SMF (Session Management Function, Session Management Function) / UPF (User plane Function, User plane function) will establish and store the user's PDU session related information. When the user does not need to transmit data, AMF / SMF / UPF will delete the stored PDU session related information to release the occupied resources.

[0003] However, in the actual operation of the 5GC core network, due to reasons such as message transmission failure, abnormal network element processing, and terminal failure, some residual junk sessions gradually accumulate in a single network element within the 5GC. These sessions are in a suspended state, with no related signaling or data processing for a long time, and occupy considerable resources. The existence of these junk sessions causes the sessions between network elements to be out of sync and occupies the system resources of the network elements. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a session synchronization method, device, system and readable storage medium in view of the above-mentioned deficiencies in the prior art, so as to solve the problem that in the actual operation of the existing 5GC core network, due to message transmission failure, network element processing abnormality, terminal failure and the like, some residual junk sessions gradually accumulate in a single network element within the 5GC. The existence of these junk sessions causes the sessions between the network elements to be out of synchronization and occupies the system resources of the network elements.

[0005] In a first aspect, the present invention provides a session synchronization method, applied to an access and mobility management function AMF, the method comprising:

[0006] Determine a session set that regards the user equipment UE as valid, and delete invalid sessions;

[0007] The session set considered by the UE to be valid is sent to the session management function SMF, so that the SMF determines whether each session stored by it about the UE is a session considered by the UE to be valid, and deletes the corresponding invalid sessions, and the SMF sends the session set considered by the UE to the user plane function UPF, so that the UPF determines whether each session stored by it about the UE is a session considered by the UE to be valid, and deletes the corresponding invalid sessions.

[0008] Further, the determining to regard the user equipment UE as a valid session set and deleting invalid sessions specifically includes:

[0009] Determining a session set considered as valid by the UE according to a periodic registration request, a mobility registration request, or a service request sent by the UE and received within a predetermined time;

[0010] Determine whether each session about the UE stored by the AMF belongs to a session set considered valid by the UE, confirm the session that does not belong to the session set considered valid by the UE as an invalid session, and delete the invalid session.

[0011] Furthermore, the method further comprises:

[0012] If no periodic registration request, mobility registration request, or service request of the UE is received within a predetermined time, setting an implicit deregistration timer for the UE;

[0013] In response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit deregistration timer expires, deleting all sessions of the UE;

[0014] A first notification for deleting all sessions of the UE is sent to the SMF, so that the SMF deletes all sessions of the UE according to the first notification, and the SMF sends a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

[0015] Furthermore, the method further comprises:

[0016] When creating a session of the UE, start an inactivity timer for each session of the UE, where the duration of the inactivity timer is greater than the sum of the period of the periodic registration of the UE and the duration of the implicit deregistration timer;

[0017] When any session activity of the UE is detected, the corresponding inactivity timer is cleared and restarted, and when the inactivity timer of a session of the UE is detected to have timed out, it is determined whether the UE is a registered UE;

[0018] In response to the UE not being a registered UE, the session whose inactivity timer has expired is deleted or all sessions of the UE are deleted, and a third notification for deleting the certain session or deleting all sessions of the UE is sent to the SMF, so that the SMF deletes the certain session or deletes all sessions of the UE according to the third notification, and the SMF sends a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

[0019] Furthermore, the method further comprises:

[0020] When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold;

[0021] According to the query request, all local sessions are fed back to the SSF, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

[0022] Furthermore, the method further comprises:

[0023] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and enables the SSF to uniformly analyze and compare all sessions in the AMF, SMF and UPF, and use the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

[0024] In a second aspect, the present invention provides a session synchronization method, which is applied to a session management function SMF, and the method comprises:

[0025] receiving a session set considered as valid by the user equipment UE, sent by the access and mobility management function AMF after determining that the session set considered as valid by the user equipment UE and deleting the invalid session;

[0026] Determine, according to the set of sessions considered valid by the UE, whether each session about the UE stored therein is a session considered valid by the UE, and delete the corresponding invalid session;

[0027] The session set considered valid by the UE is sent to the user plane function UPF, so that the UPF determines whether each session stored by it about the UE is a session considered valid by the UE, and deletes the corresponding invalid session.

[0028] Furthermore, the method further comprises:

[0029] receiving a first notification sent by the AMF for deleting all sessions of the UE, wherein the first notification is sent by the AMF after setting an implicit de-registration timer for the UE when the AMF fails to receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and in response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit de-registration timer expires, and deleting all sessions of the UE;

[0030] Delete all sessions of the UE according to the first notification, and send a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

[0031] Furthermore, the method further comprises:

[0032] Receive a third notification sent by the AMF for deleting a certain session or deleting all sessions of the UE; wherein, when creating a session of the UE, the AMF starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the AMF clears and restarts the corresponding inactivity timer, and, when detecting that the inactivity timer of a certain session of the UE has timed out, determines whether the UE is a registered UE; the third notification is sent by the AMF in response to the UE not being a registered UE, deleting the certain session whose inactivity timer has timed out or deleting all sessions of the UE;

[0033] Delete the certain session or delete all sessions of the UE according to the third notification, and send a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

[0034] Furthermore, the method further comprises:

[0035] When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold;

[0036] Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF;

[0037] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0038] Furthermore, the method further comprises:

[0039] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF;

[0040] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0041] In a third aspect, the present invention provides a session synchronization method, applied to a user plane function UPF, the method comprising:

[0042] The receiving session management function SMF determines whether each session stored about the UE is a session regarded as valid by the UE according to the session set regarded as valid by the user equipment UE, and deletes the corresponding invalid session, and then sends the session set regarded as valid by the UE, wherein the session set regarded as valid by the UE is sent to the SMF by the access and mobility management function AMF after determining the session set regarded as valid by the UE and deleting the invalid session;

[0043] According to the session set regarded as valid by the UE, it is judged whether each session about the UE stored therein is a session regarded as valid by the UE, and the corresponding invalid session is deleted.

[0044] Furthermore, the method further comprises:

[0045] receiving a second notification for deleting all sessions of the UE after the SMF deletes all sessions of the UE according to the first notification; wherein the first notification is sent to the SMF after the AMF sets an implicit de-registration timer for the UE when the AMF does not receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and responds to the implicit de-registration timer before the timeout of the implicit de-registration timer. After not receiving a periodic registration request, a mobility registration request, or a service request from the UE, and deleting all sessions of the UE;

[0046] All sessions of the UE are deleted according to the second notification.

[0047] Furthermore, the method further comprises:

[0048] Receiving a fourth notification for deleting a certain session or deleting all sessions of the UE after the SMF deletes a certain session or deletes all sessions of the UE according to the third notification; wherein, when the AMF creates a session of the UE, it starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the corresponding inactivity timer is cleared and restarted, and when it is detected that the inactivity timer of a certain session of the UE has timed out, it determines whether the UE is a registered UE; the third notification is sent to the SMF by the AMF in response to the UE not being a registered UE, deleting the certain session with the inactivity timer timed out or deleting all sessions of the UE;

[0049] Delete the certain session or delete all sessions of the UE according to the fourth notification.

[0050] Furthermore, the method further comprises:

[0051] When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold;

[0052] Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF;

[0053] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0054] Furthermore, the method further comprises:

[0055] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF;

[0056] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0057] In a fourth aspect, the present invention provides a session synchronization device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the session synchronization method described in the first aspect, the second aspect, or the third aspect.

[0058] In a fifth aspect, an embodiment of the present invention provides a session synchronization system, including an access and mobility management function AMF, a session management function SMF and a user plane function UPF;

[0059] The AMF is used to execute the session synchronization method described in the first aspect above;

[0060] The SMF is used to execute the session synchronization method described in the second aspect above;

[0061] The UPF is used to execute the session synchronization method described in the third aspect above.

[0062] In a sixth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the session synchronization method described in the first aspect, the second aspect, or the third aspect is implemented.

[0063] The session synchronization method, device, system and readable storage medium provided by the present invention. First, determine the session set that the UE is considered valid, and delete invalid sessions; then send the session set that the UE is considered valid to SMF, so that the SMF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions, and the SMF sends the session set that the UE is considered valid to UPF, so that the UPF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions. Through the present invention, junk sessions in each network element of 5GC can be cleaned up, session synchronization in each network element of 5GC can be achieved, and the service quality and service experience of UE can be taken into account. It solves the problem that in the actual operation of the existing 5GC core network, due to message transmission failure, network element processing abnormality, terminal failure and other reasons, some residual junk sessions are gradually accumulated in a single network element within 5GC, and the existence of these junk sessions causes the sessions between each network element to be out of sync, and occupies the system resources of the network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 This is a diagram of the 5G network architecture;

[0065] Figure 2 This is a flow chart of a session synchronization method according to Embodiment 1 of the present invention;

[0066] Figure 3This is a flow chart of a normal UE-triggered session synchronization according to an embodiment of the present invention;

[0067] Figure 4 This is another flow chart of normal UE-triggered session synchronization according to an embodiment of the present invention;

[0068] Figure 5 This is a flow chart of session synchronization triggered by UE abnormality according to an embodiment of the present invention;

[0069] Figure 6 A flowchart of a session synchronization triggered by an AMF exception according to an embodiment of the present invention;

[0070] Figure 7 Another AMF abnormality-triggered session synchronization flow chart of an embodiment of the present invention;

[0071] Figure 8 A flowchart of junk session processing in SMF / UPF according to an embodiment of the present invention;

[0072] Fig. 9 Another flow chart of junk session processing in SMF / UPF according to an embodiment of the present invention;

[0073] Fig.10 This is a flow chart of a session synchronization method according to Embodiment 2 of the present invention;

[0074] Fig.11 This is a flow chart of a session synchronization method according to Embodiment 3 of the present invention;

[0075] Fig.12 This is a structural diagram of a session synchronization device according to Embodiment 4 of the present invention;

[0076] Fig.13 This is a structural diagram of a session synchronization system according to Embodiment 5 of the present invention. DETAILED DESCRIPTION

[0077] In order to enable those skilled in the art to better understand the technical solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0078] It should be understood that the specific embodiments and drawings described herein are only used to explain the present invention rather than to limit the present invention.

[0079] It can be understood that, in the absence of conflict, the various embodiments of the present invention and the various features in the embodiments can be combined with each other.

[0080] It can be understood that, for the convenience of description, the drawings of the present invention only show the parts related to the present invention, while the parts irrelevant to the present invention are not shown in the drawings.

[0081] It can be understood that each unit and module involved in the embodiments of the present invention may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0082] It can be understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of the present invention may occur in an order different from that marked in the drawings.

[0083] It is understood that the flowcharts and block diagrams of the present invention illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present invention. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or may be implemented by a combination of hardware and computer instructions.

[0084] It can be understood that the units and modules involved in the embodiments of the present invention can be implemented by software or hardware. For example, the units and modules can be located in a processor.

[0085] Application Overview

[0086] In the actual operation of 5GC, due to reasons such as message transmission failure, network element processing abnormalities, and terminal failures, some residual junk sessions gradually accumulate in a single network element within the 5GC core network. These sessions are in a suspended state, with no related signaling or data processing for a long time, and occupy considerable resources.

[0087] For example, there are PDU sessions 1, 2, and 3 in AMF; there are PDU sessions 2, 3, and 4 in SMF; there are PDU sessions 3, 4, and 5 in UPF, among which only session 3 is a valid session, and 1, 2, 4, and 5 are all invalid sessions. It can be seen that the existence of junk sessions causes the sessions between network elements to be out of sync and occupies the system resources of the network elements.

[0088] When the number of these junk sessions is small, they will not have much impact on the efficiency of a single network element. However, as the number of junk sessions increases, the resources they occupy are also increasing, causing a single network element to be overloaded. In serious cases, it affects the processing of normal sessions, resulting in the inability to establish new sessions or inefficient processing of established sessions. In addition, the asynchrony of sessions between network elements will cause a network element to frequently send request messages to another network element for a certain session, while the data of the session does not exist in the other network element at all, further increasing the network burden. Moreover, a single network element cannot delete a PDU session at will, which may cause the deletion of valid sessions and aggravate the asynchrony of sessions between network elements.

[0089] The 3GPP specification only specifies the process of establishing a control plane signaling connection and creating a PDU session in the 5GC core network, but does not specify how to detect junk sessions in each 5GC network element, how to clean up junk sessions in each network element, and how to achieve session synchronization between network elements.

[0090] In response to the above technical problems, the idea of ​​the present application is to provide a session synchronization method, device, system and readable storage medium, which triggers the deletion of invalid sessions from top to bottom (UE->AMF->SMF->UPF), thereby cleaning up junk sessions in each 5GC network element and realizing session synchronization in each 5GC network element.

[0091] After introducing the basic principles of the present application, various non-limiting embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0092] Embodiment 1:

[0093] This embodiment provides a session synchronization method, which is applied to access and mobility management function AMF, such as Figure 2 As shown, the method includes:

[0094] Step S101: Determine that a UE (User Equipment) is regarded as a valid session set, and delete invalid sessions.

[0095] Step S102: Send the session set that the UE considers to be valid to the session management function SMF, so that the SMF determines whether each session stored about the UE is a session considered valid by the UE, and deletes the corresponding invalid sessions, and the SMF sends the session set that the UE considers to be valid to the user plane function UPF, so that the UPF determines whether each session stored about the UE is a session considered valid by the UE, and deletes the corresponding invalid sessions (i.e., junk sessions).

[0096] In this embodiment, considering the service quality and service experience of the UE, the session existing in the UE is used as the initial benchmark for evaluating whether a session is valid. Since the AMF is closest to the UE, the session in the AMF is synchronized with the session in the UE to make the session in the AMF a valid session. At the same time, the SMF and UPF use the session in the AMF as a benchmark to determine the validity of the session, thereby achieving session synchronization in each network element of the 5GC.

[0097] Optionally, the determining to regard the user equipment UE as a valid session set and deleting invalid sessions specifically includes:

[0098] Determining a session set considered as valid by the UE according to a periodic registration request, a mobility registration request, or a service request sent by the UE and received within a predetermined time;

[0099] Determine whether each session about the UE stored by the AMF belongs to a session set considered valid by the UE, confirm the session that does not belong to the session set considered valid by the UE as an invalid session, and delete the invalid session.

[0100] In this embodiment, a normal UE will send a periodic registration request, a mobility registration request, or a service request to the AMF. These three messages contain a valid session set on the UE side, so the AMF can confirm the valid session on the UE side based on these three messages.

[0101] In an optional embodiment, after AMF determines that the UE is regarded as a valid session set and deletes invalid sessions, AMF may also send the invalid session set consisting of invalid sessions to SMF, and SMF determines whether each session stored by it related to the UE belongs to the invalid session set. If so, SMF deletes the session, if not, SMF retains the session; at the same time, SMF sends the invalid session set received from AMF to UPF, and UPF determines whether each session stored by it related to the UE belongs to the invalid session set. If so, UPF deletes the session, if not, UPF retains the session.

[0102] It should be noted that replacing the "valid session set" with the "invalid session set" requires all parties AMF / SMF / UPF to execute relevant processes, so that absolute synchronization can be approached as a whole.

[0103] Optionally, the method further comprises:

[0104] If no periodic registration request, mobility registration request, or service request of the UE is received within a predetermined time, setting an implicit deregistration timer for the UE;

[0105] In response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit deregistration timer expires, deleting all sessions of the UE;

[0106] A first notification for deleting all sessions of the UE is sent to the SMF, so that the SMF deletes all sessions of the UE according to the first notification, and the SMF sends a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

[0107] In this embodiment, considering that the UE is abnormal (such as disconnection, failure), no periodic registration request, mobility registration request, or service request will be sent to the AMF. If the AMF does not receive the periodic registration request, mobility registration request, or service request from the UE within the predetermined time, the AMF sets an implicit deregistration timer for the UE; if the periodic registration request, mobility registration request, or service request from the UE is not received before the implicit deregistration timer expires, the AMF deletes all sessions of the UE and notifies the SMF to delete all sessions of the UE; after receiving the notification from the AMF, the SMF deletes all sessions of the UE and notifies the UPF to delete all sessions of the UE; after receiving the notification from the SMF, the UPF deletes all sessions of the UE.

[0108] Optionally, the method further comprises:

[0109] When creating a session of the UE, start an inactivity timer for each session of the UE, where the duration of the inactivity timer is greater than the sum of the period of the periodic registration of the UE and the duration of the implicit deregistration timer;

[0110] When any session activity of the UE is detected, the corresponding inactivity timer is cleared and restarted, and when the inactivity timer of a session of the UE is detected to have timed out, it is determined whether the UE is a registered UE;

[0111] In response to the UE not being a registered UE, the session whose inactivity timer has expired is deleted or all sessions of the UE are deleted, and a third notification for deleting the certain session or deleting all sessions of the UE is sent to the SMF, so that the SMF deletes the certain session or deletes all sessions of the UE according to the third notification, and the SMF sends a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

[0112] In this embodiment, for each session of the UE, after each activity, the AMF clears its inactivity timer and restarts it. When the inactivity timer of a session times out, the AMF determines whether the UE of the session is a registered UE: if it is not a registered UE, the AMF determines that the session is an invalid session or determines that all sessions of the UE are invalid sessions, the AMF deletes the invalid session, and instructs the SMF to delete the session or delete all sessions of the UE, and the SMF instructs the UPF to delete the session or delete all sessions of the UE; if it is a registered UE, the AMF is temporarily unable to determine the validity of the session. If the UE of the session is a normal UE, the UE will subsequently send a periodic registration request message, or a mobility registration request message, or a service request message to the AMF, and the AMF determines the validity of the session based on these messages. If the UE of the session is an abnormal UE, the AMF can determine the validity of the session based on the implicit deregistration timer.

[0113] Optionally, the method further comprises:

[0114] receiving a query request sent by a session synchronization function (SSF) when the load of the SMF or UPF exceeds a threshold;

[0115] According to the query request, all local sessions are fed back to the SSF, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

[0116] In this embodiment, SSF subscribes to the load status of SMF and UPF from NWDAF (Network Data Analytics Function), and NWDAF periodically notifies SSF of the load status of SMF / UPF; when SSF detects that the load of SMF or UPF exceeds the threshold, SSF simultaneously initiates queries to AMF, SMF, and UPF to query the local sessions of AMF, SMF, and UPF respectively; AMF, SMF, and UPF feedback all local sessions to SSF in turn; SSF uniformly analyzes and compares the sessions in AMF / SMF / UPF, and takes the sessions in AMF as the benchmark to screen out invalid sessions in SMF and invalid sessions in UPF, and send them to SMF and UPF respectively; after receiving them, SMF and UPF each delete the local invalid sessions.

[0117] Optionally, the method further comprises:

[0118] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and enables the SSF to uniformly analyze and compare all sessions in the AMF, SMF and UPF, and use the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

[0119] In this embodiment, the scheduled time can be a time in a relatively idle period of each day (for example, 3 am). When the scheduled time arrives, AMF / SMF / UPF sends all local sessions to NWDAF; NWDAF notifies SSF of the sessions in AMF / SMF / UPF; SSF uniformly analyzes and compares the sessions in AMF / SMF / UPF, and uses the sessions in AMF as a benchmark to screen out invalid sessions in SMF and invalid sessions in UPF, and send them to SMF and UPF respectively; after receiving them, SMF and UPF delete their respective local invalid sessions.

[0120] In a specific embodiment, in order to clean up the junk sessions in each 5GC network element and realize the session synchronization in each 5GC network element, it is considered that the junk sessions in AMF / SMF / UPF are cleaned up in time when the UE is normal and the UE is abnormal, and the monitoring, judgment and cleaning of the junk sessions generated by the internal abnormalities of AMF / SMF / UPF are considered. The session synchronization method may include the following 4 processes:

[0121] Process 1) is a session synchronization process triggered by a normal UE.

[0122] Process 2) is a session synchronization process triggered by a UE abnormality (eg, disconnection, failure).

[0123] Process 3) is the session synchronization process triggered by an AMF exception (a timed-out session).

[0124] Process 4) is the junk session cleanup process in SMF / UPF.

[0125] Among them, the execution of process 1) and process 2) is the basis of process 3);

[0126] The execution of process 1), process 2), and process 3) is the basis of process 4);

[0127] By executing process 1), process 2), and process 3), the session in AMF can be synchronized with the session in UE to ensure that the session in AMF is a valid session. In this way, SMF and UPF can determine the validity of the session based on the session in AMF;

[0128] Process 4) introduces the network element SSF (session synchronization function) to collect sessions in AMF / SMF / UPF, and uses the AMF sessions as a benchmark to screen out and delete invalid sessions in SMF and UPF.

[0129] It should be noted that the idea of ​​the session synchronization method is as follows:

[0130] a) Considering the UE's service quality and service experience, the existing sessions in the UE are used as the initial benchmark for evaluating whether a session is valid;

[0131] b) Since AMF is closest to UE, the session in AMF is synchronized with the session in UE to ensure that the session in AMF is a valid session;

[0132] c)SMF and UPF use the session in AMF as a benchmark to determine the validity of the session;

[0133] d) While deleting invalid sessions in a certain network element, the sessions in other network elements are also processed (deleting invalid sessions and re-establishing missing sessions);

[0134] e) Introduce network element SSF to collect sessions in AMF / SMF / UPF, and use AMF sessions as a benchmark to filter out and delete invalid sessions in SMF and UPF.

[0135] Specifically, each process is described in detail as follows:

[0136] Process 1) Normal UE processing flow

[0137] Basic plan

[0138] A normal UE will send a periodic registration request, a mobility registration request, or a service request to the AMF. The AMF determines whether each session stored about the UE is considered a valid session by the UE based on these three messages. If not, it is determined to be an invalid session, and the AMF deletes the invalid session.

[0139] It should be noted that the three messages of periodic registration request, mobility registration request and service request contain valid session sets on the UE side, so the valid sessions on the UE side can be confirmed based on these three messages.

[0140] Other messages do not contain a valid session set on the UE side.

[0141] AMF sends the session set that the UE considers to be valid to SMF. SMF determines whether each session stored by it about the UE is a session that the UE considers to be valid. If not, it is determined to be an invalid session, and SMF deletes the invalid session.

[0142] SMF sends the set of sessions that the UE considers to be valid to UPF. UPF determines whether each session stored by it about the UE is a session that the UE considers to be valid. If not, it is determined to be an invalid session, and UPF deletes the invalid session.

[0143] Specifically, Figure 3 As shown, a normal UE-triggered session synchronization process includes: AMF receives a periodic registration request message, a mobility registration request message, or a service request message from the UE; AMF determines a set of sessions that the UE considers to be valid based on the periodic registration request message, the mobility registration request message, or the service request message; AMF determines whether each session related to the UE stored therein belongs to the set of sessions that the UE considers to be valid; if so, AMF determines that the session is a valid session and retains the session, if not, AMF determines that the session is an invalid session and deletes the session. AMF determines whether the current session is the last session about the UE in AMF; if so, AMF notifies SMF of the session set that the UE considers valid, SMF receives the session set that the UE considers valid, SMF determines whether each session related to the UE stored by it belongs to the session set that the UE considers valid, if so, SMF retains the session, if not, SMF deletes the session, SMF determines whether the current session is the last session about the UE in SMF, if so, SMF sends the session set that the UE considers valid received from AMF to UPF, UPF receives the session set that the UE considers valid, UPF determines whether each session related to the UE stored by it belongs to the session set that the UE considers valid, if so, UPF retains the session, if not, UPF deletes the session, UPF determines whether the current session is the last session about the UE in UPF, if so, then ends.

[0144] Options

[0145] Replace the sending of the "valid session set" in the above basic scenario with sending the "invalid session set".

[0146] Specifically, Figure 4As shown, another normal UE-triggered session synchronization process includes: AMF receives a periodic registration request message, a mobility registration request message, or a service request message from the UE; AMF determines the session set that the UE considers to be valid based on the periodic registration request message, the mobility registration request message, or the service request message; AMF determines whether each session related to the UE stored therein belongs to the session set that the UE considers to be valid; if so, AMF determines that the session is a valid session and retains the session, if not, AMF determines that the session is an invalid session and deletes the session. AMF determines whether the current session is the last session about the UE in AMF; if so, AMF sends the invalid session set consisting of invalid sessions to SMF, and instructs SMF to delete the invalid sessions. SMF receives the invalid session set sent by AMF, and SMF determines whether each session related to the UE stored in it belongs to the invalid session set. If so, SMF deletes the session, if not, SMF retains the session; SMF determines whether the current session is the last session about the UE in SMF. If so, SMF sends the invalid session set received from AMF to UPF, and instructs UPF to delete the invalid session. UPF receives the invalid session set sent by SMF, and UPF determines whether each session related to the UE stored in it belongs to the invalid session set. If so, UPF deletes the session, if not, UPF retains the session. UPF determines whether the current session is the last session about the UE in UPF, and if so, ends.

[0147] It should be noted that process 1 can promptly clean up the PDU sessions that are considered invalid by the UE in AMF / SMF / UPF, and keep the session synchronization in AMF / SMF / UPF.

[0148] Process 2) Abnormal UE processing process

[0149] For abnormal UEs, AMF deletes the PDU session of the UE after the implicit deregistration timer expires, and instructs SMF to delete the PDU session of the UE. SMF instructs UPF to delete the PDU session of the UE.

[0150] Specifically, the session synchronization process triggered by UE abnormality (e.g., disconnection, failure) is as follows: Figure 5As shown, including: if AMF does not receive the periodic registration request, mobility registration request, or service request of the UE within the predetermined time, AMF sets an implicit de-registration timer for the UE; AMF still does not receive the periodic registration request, mobility registration request, or service request of the UE before the implicit de-registration timer expires; when the implicit de-registration timer of the UE times out, AMF deletes all sessions of the UE and notifies SMF to delete all sessions of the UE; after receiving the notification from AMF, SMF deletes all sessions of the UE and notifies UPF to delete all sessions of the UE; after receiving the notification from SMF, UPF deletes all sessions of the UE.

[0151] It should be noted that Figure 5 The duration of the predetermined time can be equal to the sum of the durations of the periodic registration timer and the mobile reachable timer. Through process 2), the PDU session of the abnormal UE in AMF / SMF / UPF can be cleaned up in time to keep the session synchronization in AMF / SMF / UPF.

[0152] Process 3) Session timeout processing process in AMF

[0153] Basic plan

[0154] When AMF establishes each session, it starts an inactivity timer for the session. The duration of the inactivity timer is greater than the sum of the period of UE periodic registration and the duration of the UE implicit deregistration timer. After each activity of the session, AMF clears its inactivity timer and restarts it. When the inactivity timer of a session times out, AMF determines whether the UE of the session is a registered UE:

[0155] If it is not a registered UE, it is determined to be an invalid session, then AMF deletes the invalid session and instructs SMF to delete the session, and SMF instructs UPF to delete the session.

[0156] If it is a registered UE, AMF is temporarily unable to determine the validity of the session. If the UE of the session is a normal UE, the UE will subsequently send a periodic registration request message, a mobility registration request message, or a service request message to the AMF, and the AMF can use process 1) to determine the validity of the session. If the UE of the session is an abnormal UE, the AMF can use process 2) to determine the validity of the session. Therefore, at this time, AMF determines that the session is a temporarily valid session and sets a temporary valid timer for the session. If a periodic registration request message, a mobility registration request message, or a service request message is received from the UE before the temporary valid timer expires, the AMF determines that the UE is normal and executes process 1); if a periodic registration request message, a mobility registration request message, or a service request message is not received from the UE before the temporary valid timer expires, the AMF determines that the UE is faulty and executes process 2).

[0157] Specifically, Figure 6 As shown, a session synchronization process triggered by an AMF exception includes: when AMF creates a session, AMF sets an inactivity timer for the session; before the inactivity timer times out, whether AMF performs a processing action on the session, if so, AMF clears the inactivity timer of the session and restarts it; if not, the inactivity timer of the session times out, then AMF determines whether the UE of the session is in a registered state, if so, AMF determines that the session is a temporarily valid session, sets a temporarily valid timer, and before the temporary valid timer times out, whether AMF receives a periodic registration request message, a mobility registration request message, or a service request message from the UE, if so, AMF determines that the UE is normal and processes it according to the normal UE processing flow; if not, AMF determines that the UE is abnormal and processes it according to the abnormal UE processing flow; if AMF determines that the UE of the session is not in a registered state, AMF determines that the session is an invalid session, deletes the session, and notifies SMF to delete the session; after receiving the notification from AMF, SMF deletes the session and notifies UPF to delete the session, and after receiving the notification from SMF, UPF deletes the session.

[0158] It should be noted that Figure 6 The duration of the temporary valid timer in process 2) can be equal to the duration of the predetermined time in process 2).

[0159] Options

[0160] When AMF establishes each session, it starts an inactivity timer for the session. The duration of the inactivity timer is greater than the sum of the period of UE periodic registration and the duration of the UE implicit deregistration timer. After each activity of the session, AMF clears its inactivity timer and restarts it. When the inactivity timer of a session times out, AMF determines whether the UE of the session is a registered UE:

[0161] If it is not a registered UE, it is determined that all sessions of the UE are invalid sessions, then the AMF deletes all sessions of the UE and instructs the SMF to delete all sessions of the UE, and the SMF instructs the UPF to delete all sessions of the UE.

[0162] If it is a registered UE, AMF is temporarily unable to determine the validity of the session. If the UE of the session is a normal UE, the UE will subsequently send a periodic registration request message, a mobility registration request message, or a service request message to the AMF, and the AMF can use process 1) to determine the validity of the session. If the UE of the session is a faulty UE, the AMF can use process 2) to determine the validity of the session. Therefore, at this time, AMF determines that the session is a temporarily valid session and sets a temporary valid timer for the session. If a periodic registration request message, a mobility registration request message, or a service request message is received from the UE before the temporary valid timer expires, the AMF determines that the UE is normal and executes process 1); if a periodic registration request message, a mobility registration request message, or a service request message is not received from the UE before the temporary valid timer expires, the AMF determines that the UE is faulty and executes process 2).

[0163] Specifically, Figure 7 As shown, another session synchronization process triggered by AMF exception includes: when AMF creates a session, AMF sets an inactivity timer for the session; before the inactivity timer times out, whether AMF performs a processing action on the session, if so, AMF clears the inactivity timer of the session and restarts it; if not, the inactivity timer of the session times out, then AMF determines whether the UE of the session is in a registered state, if so, AMF determines that the session is a temporarily valid session, sets a temporarily valid timer, and before the temporary valid timer times out, whether AMF receives a periodic registration request message, a mobility registration request message, or a service request message from the UE, if so, AMF determines that the UE is normal and processes it according to the normal UE processing flow; if not, AMF determines that the UE is abnormal and processes it according to the abnormal UE processing flow; if AMF determines that the UE of the session is not in a registered state, AMF determines all sessions of the UE as invalid sessions, deletes all sessions of the UE, and notifies SMF to delete all sessions of the UE; after receiving the notification from AMF, SMF deletes all sessions of the UE and notifies UPF to delete all sessions of the UE; after receiving the notification from SMF, UPF deletes all sessions of the UE.

[0164] It should be noted that process 3 can timely clean up the junk sessions in AMF to ensure that the sessions in AMF are valid sessions.

[0165] Process 4) Process of handling junk sessions in SMF / UPF

[0166] By executing the above process 1), process 2), and process 3), it can be ensured that the session in AMF is a valid session, which can be used as a basis for SMF and UPF to judge the validity of the session.

[0167] Basic plan

[0168] Figure 8 A junk session processing flow in SMF / UPF is shown, including:

[0169] SSF subscribes to NWDAF for the load status of SMF and UPF, and NWDAF periodically notifies SSF of the load status of SMF / UPF;

[0170] When SSF detects that the load of SMF or UPF exceeds the threshold, SSF simultaneously initiates queries to AMF, SMF, and UPF to query their respective local sessions;

[0171] AMF reports all local sessions to SSF;

[0172] SMF reports all local sessions to SSF;

[0173] UPF reports all local sessions to SSF;

[0174] SSF uniformly analyzes and compares the sessions in AMF / SMF / UPF, and uses the sessions in AMF as a benchmark to filter out invalid sessions in SMF and UPF, and sends them to SMF and UPF respectively;

[0175] After receiving the message, SMF and UPF will delete the invalid session locally.

[0176] Options

[0177] Fig. 9 Another process of handling junk sessions in SMF / UPF is shown, including:

[0178] SSF subscribes to the session information of AMF / SMF / UPF from NWDAF (5G network data analysis function);

[0179] During a relatively idle period every day (e.g. 3 a.m.), AMF sends all local sessions to NWDAF. At the same time, SMF and UPF also send all local sessions to NWDAF.

[0180] NWDAF notifies SSF of the session in AMF / SMF / UPF;

[0181] SSF uniformly analyzes and compares the sessions in AMF / SMF / UPF, and uses the sessions in AMF as a benchmark to filter out invalid sessions in SMF and UPF, and sends them to SMF and UPF respectively;

[0182] After receiving the message, SMF and UPF delete their respective local invalid sessions.

[0183] It should be noted that process 4 can be used to clean up invalid sessions in SMF and UPF when SMF / UPF is overloaded (or during daily idle periods), and keep sessions in SMF / UPF and AMF synchronized.

[0184] It should be noted that the session synchronization method provided by the present invention has the following beneficial effects:

[0185] a) AMF determines the valid session on the UE side based on the UE's periodic registration request message, mobility registration request message, and service request message as the benchmark for whether the session is valid (according to this, it not only synchronizes the sessions within the network element, but also takes into account the UE's service experience). After AMF determines the valid session on the UE side, it not only screens out invalid sessions locally, but also notifies SMF and UPF of the valid sessions on the UE side, so that SMF and UPF can judge the validity of their local sessions based on the valid sessions on the UE side (reducing the burden of downstream network elements in processing invalid sessions and improving the efficiency of screening out invalid sessions).

[0186] b) Comprehensively consider the screening of invalid sessions in AMF (delete corresponding invalid sessions in SMF and UPF at the same time) in three cases: normal UE (process 1 is triggered by UE sending a message), abnormal UE (process 2 is triggered by implicit deregistration timer), and internal abnormal AMF (process 3 is triggered by session inactivity timer timeout). Among them, the normal UE and abnormal UE processes can accurately screen out invalid sessions in various network elements from the UE source, and the AMF internal abnormal process calls the normal UE and abnormal UE processes when necessary. Therefore, the execution of these three cases can reliably ensure that the session in AMF is a valid session. Based on this, the session in AMF can be used as a reliable benchmark for judging the validity of the SMF and UPF sessions (based on this, it is not necessary to query the UE through the air interface every time the session validity is judged. It is only necessary to query the session in AMF to reliably determine the validity of the session).

[0187] c) When judging the validity of sessions in SMF and UPF, SSF (session synchronization function) is introduced, and combined with NWDAF to obtain the load status in AMF / SMF / UPF, a new architecture is designed to filter out invalid sessions through a third-party network element (SSF). Specifically, SSF subscribes to the load status of SMF / UPF from NWDAF, and SSF monitors the load status of SMF / UPF. When the load of SMF / UPF exceeds the threshold, SSF initiates a query for all sessions of AMF / SMF / UPF. SSF compares all sessions of AMF / SMF / UPF, and filters out invalid sessions in SMF / UPF based on AMF. In this process, the new architecture of filtering out invalid sessions through a third-party network element (SSF) can delete invalid sessions in SMF / UPF at one time when necessary (load exceeds the threshold) or at an appropriate time (relative idle period), eliminating the burden of SMF / UPF to judge and filter out each invalid session, and more efficiently and stably handles invalid sessions in the network, improving the efficiency and flexibility of network maintenance.

[0188] d) The integrated processes 1, 2, 3, and 4 not only provide a top-down (UE->AMF->SMF->UPF) mode for triggering the deletion of invalid sessions, but also provide a new architecture for filtering invalid sessions through a third-party network element (SSF) when the 5GC network element load exceeds the threshold. Various abnormal and fault conditions are covered, and the invalid sessions in each network element can be effectively cleaned up.

[0189] The session synchronization method provided by the embodiment of the present invention first determines the session set that the UE is considered valid and deletes invalid sessions; then sends the session set that the UE is considered valid to the SMF, so that the SMF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions, and enables the SMF to send the session set that the UE is considered valid to the UPF, so that the UPF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions. The present invention can clean up junk sessions in each network element of 5GC, realize session synchronization in each network element of 5GC, and take into account the service quality and service experience of UE. It solves the problem that in the actual operation of the existing 5GC core network, due to message transmission failure, network element processing abnormality, terminal failure and other reasons, some residual junk sessions gradually accumulate in a single network element within 5GC, and the existence of these junk sessions causes the sessions between each network element to be out of sync, and occupies the system resources of the network element.

[0190] Embodiment 2:

[0191] like Fig.10 As shown, this embodiment provides a session synchronization method, which is applied to a session management function SMF. The method includes:

[0192] Step S201: receiving a session set that is considered as valid by the user equipment UE, sent by the access and mobility management function AMF after determining that the session set is considered as valid by the user equipment UE and deleting invalid sessions;

[0193] Step S202: judging whether each session about the UE stored therein is a session regarded as valid by the UE according to the session set regarded as valid by the UE, and deleting the corresponding invalid session;

[0194] Step S203: Send the session set considered valid by the UE to the user plane function UPF, so that the UPF determines whether each session stored about the UE is a session considered valid by the UE, and deletes the corresponding invalid session.

[0195] Optionally, the method further comprises:

[0196] receiving a first notification sent by the AMF for deleting all sessions of the UE, wherein the first notification is sent by the AMF after setting an implicit de-registration timer for the UE when the AMF fails to receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and in response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit de-registration timer expires, and deleting all sessions of the UE;

[0197] Delete all sessions of the UE according to the first notification, and send a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

[0198] Optionally, the method further comprises:

[0199] Receive a third notification sent by the AMF for deleting a certain session or deleting all sessions of the UE; wherein, when creating a session of the UE, the AMF starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the AMF clears and restarts the corresponding inactivity timer, and, when detecting that the inactivity timer of a certain session of the UE has timed out, determines whether the UE is a registered UE; the third notification is sent by the AMF in response to the UE not being a registered UE, deleting the certain session whose inactivity timer has timed out or deleting all sessions of the UE;

[0200] Delete the certain session or delete all sessions of the UE according to the third notification, and send a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

[0201] Optionally, the method further comprises:

[0202] When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold;

[0203] Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF;

[0204] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0205] Optionally, the method further comprises:

[0206] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF;

[0207] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0208] Embodiment 3:

[0209] like Fig.11 As shown, this embodiment provides a session synchronization method, which is applied to a user plane function UPF, and the method includes:

[0210] Step S301: The receiving session management function SMF determines whether each session stored about the UE is a session regarded as valid by the UE according to the session set regarded as valid by the user equipment UE, and deletes the corresponding invalid session, and then sends the session set regarded as valid by the UE, wherein the session set regarded as valid by the UE is sent to the SMF by the access and mobility management function AMF after determining the session set regarded as valid by the UE and deleting the invalid session;

[0211] Step S302: judging whether each session about the UE stored therein is a session regarded as valid by the UE according to the session set regarded as valid by the UE, and deleting the corresponding invalid session.

[0212] Optionally, the method further comprises:

[0213] receiving a second notification for deleting all sessions of the UE after the SMF deletes all sessions of the UE according to the first notification; wherein the first notification is sent to the SMF after the AMF sets an implicit de-registration timer for the UE when the AMF does not receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and responds to the implicit de-registration timer before the timeout of the implicit de-registration timer. After not receiving a periodic registration request, a mobility registration request, or a service request from the UE, and deleting all sessions of the UE;

[0214] All sessions of the UE are deleted according to the second notification.

[0215] Optionally, the method further comprises:

[0216] Receiving a fourth notification for deleting a certain session or deleting all sessions of the UE after the SMF deletes a certain session or deletes all sessions of the UE according to the third notification; wherein, when the AMF creates a session of the UE, it starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the corresponding inactivity timer is cleared and restarted, and when it is detected that the inactivity timer of a certain session of the UE has timed out, it determines whether the UE is a registered UE; the third notification is sent to the SMF by the AMF in response to the UE not being a registered UE, deleting the certain session with the inactivity timer timed out or deleting all sessions of the UE;

[0217] Delete the certain session or delete all sessions of the UE according to the fourth notification.

[0218] Optionally, the method further comprises:

[0219] When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold;

[0220] Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF;

[0221] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0222] Optionally, the method further comprises:

[0223] When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF;

[0224] Receive the invalid session sent by the SSF, and delete the invalid session locally.

[0225] Embodiment 4:

[0226] refer to Fig.12 This embodiment provides a session synchronization device, including a memory 21 and a processor 22, wherein the memory 21 stores a computer program, and the processor 22 is configured to run the computer program to execute the session synchronization method in embodiment 1, embodiment 2, or embodiment 3.

[0227] The memory 21 is connected to the processor 22. The memory 21 may be a flash memory, a read-only memory or other memory. The processor 22 may be a central processing unit or a single-chip microcomputer.

[0228] Embodiment 5:

[0229] refer to Fig.13 , this embodiment provides a session synchronization system, including an access and mobility management function AMF31, a session management function SMF32 and a user plane function UPF33;

[0230] The AMF31 is used to execute the session synchronization method in Example 1;

[0231] The SMF32 is used to execute the session synchronization method in Example 2;

[0232] The UPF33 is used to execute the session synchronization method in Example 3.

[0233] Embodiment 6:

[0234] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the session synchronization method in the above-mentioned embodiment 1, embodiment 2 or embodiment 3 is implemented.

[0235] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0236] In summary, the session synchronization method, device and readable storage medium provided by the embodiment of the present invention first determine the session set that the UE is considered valid and delete invalid sessions; then send the session set that the UE is considered valid to the SMF, so that the SMF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions, and causes the SMF to send the session set that the UE is considered valid to the UPF, so that the UPF determines whether each session stored about the UE is a session that the UE considers valid, and deletes the corresponding invalid sessions. Through the present invention, junk sessions in each network element of 5GC can be cleaned up, session synchronization in each network element of 5GC can be achieved, and the service quality and service experience of UE can be taken into account. It solves the problem that in the actual operation of the existing 5GC core network, due to message transmission failure, network element processing abnormality, terminal failure and other reasons, some residual junk sessions gradually accumulate in a single network element within 5GC, and the existence of these junk sessions causes the sessions between the network elements to be out of sync, and occupies the system resources of the network element.

[0237] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present invention, but the present invention is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A session synchronization method, It is characterized in that Applied to an access and mobility management function AMF, the method comprises: Determine a session set that regards the user equipment UE as valid, and delete invalid sessions; The session set considered by the UE to be valid is sent to the session management function SMF, so that the SMF determines whether each session stored by it about the UE is a session considered by the UE to be valid, and deletes the corresponding invalid sessions, and the SMF sends the session set considered by the UE to the user plane function UPF, so that the UPF determines whether each session stored by it about the UE is a session considered by the UE to be valid, and deletes the corresponding invalid sessions.

2. The method according to claim 1, It is characterized in that The determining to regard the user equipment UE as a valid session set and deleting invalid sessions specifically includes: Determining a session set considered as valid by the UE according to a periodic registration request, a mobility registration request, or a service request sent by the UE and received within a predetermined time; Determine whether each session about the UE stored by the AMF belongs to a session set considered valid by the UE, confirm the session that does not belong to the session set considered valid by the UE as an invalid session, and delete the invalid session.

3. The method according to claim 1, It is characterized in that The method further comprises: If no periodic registration request, mobility registration request, or service request of the UE is received within a predetermined time, setting an implicit deregistration timer for the UE; In response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit deregistration timer expires, deleting all sessions of the UE; A first notification for deleting all sessions of the UE is sent to the SMF, so that the SMF deletes all sessions of the UE according to the first notification, and the SMF sends a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

4. The method according to claim 3, It is characterized in that The method further comprises: When creating a session of the UE, start an inactivity timer for each session of the UE, where the duration of the inactivity timer is greater than the sum of the period of the periodic registration of the UE and the duration of the implicit deregistration timer; When any session activity of the UE is detected, the corresponding inactivity timer is cleared and restarted, and when the inactivity timer of a session of the UE is detected to have timed out, it is determined whether the UE is a registered UE; In response to the UE not being a registered UE, the session whose inactivity timer has expired is deleted or all sessions of the UE are deleted, and a third notification for deleting the certain session or deleting all sessions of the UE is sent to the SMF, so that the SMF deletes the certain session or deletes all sessions of the UE according to the third notification, and the SMF sends a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

5. The method according to claim 1, It is characterized in that The method further comprises: When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold; According to the query request, all local sessions are fed back to the SSF, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

6. The method according to claim 1, It is characterized in that The method further comprises: When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and enables the SSF to uniformly analyze and compare all sessions in the AMF, SMF and UPF, and use the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF, and send them to the SMF and UPF respectively, so that the SMF and UPF can delete the local invalid sessions.

7. A session synchronization method, applied to a session management function SMF, It is characterized in that The method comprises: receiving a session set considered as valid by the user equipment UE, sent by the access and mobility management function AMF after determining that the session set considered as valid by the user equipment UE and deleting the invalid session; Determine, according to the set of sessions considered valid by the UE, whether each session about the UE stored therein is a session considered valid by the UE, and delete the corresponding invalid session; The session set considered valid by the UE is sent to the user plane function UPF, so that the UPF determines whether each session stored by it about the UE is a session considered valid by the UE, and deletes the corresponding invalid session.

8. The method according to claim 7, It is characterized in that The method further comprises: receiving a first notification sent by the AMF for deleting all sessions of the UE, wherein the first notification is sent by the AMF after setting an implicit de-registration timer for the UE when the AMF fails to receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and in response to not receiving a periodic registration request, a mobility registration request, or a service request from the UE before the implicit de-registration timer expires, and deleting all sessions of the UE; Delete all sessions of the UE according to the first notification, and send a second notification for deleting all sessions of the UE to the UPF, so that the UPF deletes all sessions of the UE according to the second notification.

9. The method according to claim 8, It is characterized in that The method further comprises: Receive a third notification sent by the AMF for deleting a certain session or deleting all sessions of the UE; wherein, when creating a session of the UE, the AMF starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the AMF clears and restarts the corresponding inactivity timer, and, when detecting that the inactivity timer of a certain session of the UE has timed out, determines whether the UE is a registered UE; the third notification is sent by the AMF in response to the UE not being a registered UE, deleting the certain session whose inactivity timer has timed out or deleting all sessions of the UE; Delete the certain session or delete all sessions of the UE according to the third notification, and send a fourth notification for deleting the certain session or deleting all sessions of the UE to the UPF, so that the UPF deletes the certain session or deletes all sessions of the UE according to the fourth notification.

10. The method according to claim 7, It is characterized in that The method further comprises: When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold; Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF; Receive the invalid session sent by the SSF, and delete the invalid session locally.

11. The method according to claim 7, It is characterized in that The method further comprises: When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF; Receive the invalid session sent by the SSF, and delete the invalid session locally.

12. A session synchronization method, applied to a user plane function UPF, It is characterized in that The method comprises: The receiving session management function SMF determines whether each session stored about the UE is a session regarded as valid by the UE according to the session set regarded as valid by the user equipment UE, and deletes the corresponding invalid session, and then sends the session set regarded as valid by the UE, wherein the session set regarded as valid by the UE is sent to the SMF by the access and mobility management function AMF after determining the session set regarded as valid by the UE and deleting the invalid session; According to the session set regarded as valid by the UE, it is judged whether each session about the UE stored therein is a session regarded as valid by the UE, and the corresponding invalid session is deleted.

13. The method according to claim 12, It is characterized in that The method further comprises: receiving a second notification for deleting all sessions of the UE after the SMF deletes all sessions of the UE according to the first notification; wherein the first notification is sent to the SMF after the AMF sets an implicit de-registration timer for the UE when the AMF does not receive a periodic registration request, a mobility registration request, or a service request from the UE within a predetermined time, and responds to the implicit de-registration timer before the timeout of the implicit de-registration timer. After not receiving a periodic registration request, a mobility registration request, or a service request from the UE, and deleting all sessions of the UE; All sessions of the UE are deleted according to the second notification.

14. The method according to claim 13, It is characterized in that The method further comprises: Receiving a fourth notification for deleting a certain session or deleting all sessions of the UE after the SMF deletes a certain session or deletes all sessions of the UE according to the third notification; wherein, when the AMF creates a session of the UE, it starts an inactivity timer for each session of the UE, and the duration of the inactivity timer is greater than the sum of the period of the UE periodic registration and the duration of the implicit deregistration timer; when the AMF detects that any session of the UE is active, the corresponding inactivity timer is cleared and restarted, and when it is detected that the inactivity timer of a certain session of the UE has timed out, it determines whether the UE is a registered UE; the third notification is sent to the SMF by the AMF in response to the UE not being a registered UE, deleting the certain session with the inactivity timer timed out or deleting all sessions of the UE; Delete the certain session or delete all sessions of the UE according to the fourth notification.

15. The method according to claim 12, It is characterized in that The method further comprises: When receiving the query request sent by the session synchronization function SSF detecting that the load of the SMF or UPF exceeds a threshold; Feedback all local sessions to the SSF according to the query request, so that the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and filters out invalid sessions in the SMF and UPF based on the sessions in the AMF; Receive the invalid session sent by the SSF, and delete the invalid session locally.

16. The method according to claim 12, It is characterized in that The method further comprises: When the scheduled time arrives, all local sessions are sent to the network data analysis function NWDAF, so that the NWDAF notifies the SSF of all sessions in the AMF, SMF and UPF, and the SSF uniformly analyzes and compares all sessions in the AMF, SMF and UPF, and uses the sessions in the AMF as a benchmark to filter out invalid sessions in the SMF and UPF; Receive the invalid session sent by the SSF, and delete the invalid session locally.

17. A conversation synchronization device, It is characterized in that It includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to implement the session synchronization method as described in any one of claims 1 to 6, or to implement the session synchronization method as described in any one of claims 7 to 11, or to implement the session synchronization method as described in any one of claims 12 to 16.

18. A session synchronization system, It is characterized in that Includes access and mobility management function AMF, session management function SMF and user plane function UPF; The AMF is used to execute the session synchronization method described in any one of claims 1 to 6; The SMF is used to execute the session synchronization method described in any one of claims 7 to 11; The UPF is used to execute the session synchronization method described in any one of claims 12-16.

19. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the session synchronization method according to any one of claims 1 to 6, or implements the session synchronization method according to any one of claims 7 to 11, or implements the session synchronization method according to any one of claims 12 to 16.

Citation Information

Cited By

  • Systems and methods for dynamic load management in telecommunications networks

    US12634757B2