Communication method and related device

By updating the session context to exclude the anchor network device's identification information, the method addresses inefficient resource use in RRC inactive state transitions, optimizing communication efficiency and reducing resource waste.

CN119095126APending Publication Date: 2024-12-06HUAWEI TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202411026462.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In 5G communication systems where the RAN device and the CN device are not directly connected, existing connection recovery schemes fail to address how to handle the connection recovery in the RRC inactive state, resulting in wasted communication resources and inefficient communication due to invalid interactions between the session management function network element and the anchor network device, the anchor network device, the existing connection recovery schemes are not sufficient for communication architectures where the RAN device and the session management function network element are directly connected, leading to inefficient use of communication resources.

Method used

The proposed solution involves updating the target session context by removing or replacing the identification information of the anchor network device in the session management function network element, thereby avoiding unnecessary interactions and optimizing resource usage.

Benefits of technology

This approach reduces the waste of communication resources by preventing invalid interactions between the session management function network element and the anchor network device, ensuring timely updates to the session context, and enhancing the efficiency of communication in RRC inactive state transitions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095126A_ABST
    Figure CN119095126A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of wireless communication, in particular to a communication method and a related device. The method comprises: a first session management function network element receiving a first message; the first message is used for indicating that the terminal equipment is subjected to wireless access network replacement and comprises at least one of first identification information of first network equipment currently accessed by the terminal equipment and wireless access network replacement indication of the terminal equipment. Or the first message is used for requesting to update the first session and comprises the first identification information of the first network device. The first network device is directly connected with the first session management function network element. And the first session management function network element updates the target session context according to the first message, and the updated target session context does not include identification information of anchor point network equipment of the terminal equipment. By adopting the method provided by the invention, the problem of invalid interaction between the session management function network element and the anchor point network equipment caused by wireless access network replacement of the terminal equipment can be solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a communication method and related devices. Background Art

[0002] With the rapid development of wireless communication technology, the fifth generation (5G) wireless communication technology has become a hot topic in the industry. In 5G technology, a new state is introduced in the terminal device, called the radio resource control (RRC) inactive state. The RRC inactive state can be considered as an intermediate state between the RRC connected state and the RRC idle state. For a terminal device in the RRC inactive state, the radio access network (RAN) side and the core network (CN) side maintain a connection for the terminal device, and both the RAN side and the CN side save the context of the terminal device. The RAN device that maintains the control plane connection between the RAN side of the terminal device and the CN side can be called an anchor network device. The anchor network device saves the context of the terminal device so that when the terminal device needs to restore the connection due to uplink requirements, it can quickly establish a channel for communication with the CN side.

[0003] In actual work, terminal devices in the RRC inactive state can also move freely and access other RAN devices except the anchor network device, that is, the terminal device will undergo a radio access network change (RAN change). The existing connection recovery scheme provides a specific process for how a terminal device in the RRC inactive state should trigger the transition from the RRC inactive state to the RRC connected state (that is, RRC connection recovery) in the event of a radio access network change. However, this connection recovery scheme is only applicable to communication system architectures in which the RAN device and the session management function (SMF) network element are not directly connected. For the communication system architecture in which the RAN device is directly connected to the session management function network element, there is no clear regulation on how to restore the connection when the radio access network of the terminal device in the RRC inactive state is changed. This results in the session management function network element still interacting with the anchor network device after the terminal device changes its radio access network, resulting in a waste of communication resources. Summary of the invention

[0004] In order to solve the above problems, the present application provides a communication method and related devices. In the scenario where the wireless access network of the terminal device is changed, the method can avoid the invalid interaction between the session management function network element and the anchor network device, thereby reducing the waste of communication resources.

[0005] The present application is introduced below from multiple aspects. It is easy to understand that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.

[0006] In a first aspect, the present application provides a communication method. The method can be executed by a first session management function network element, or by a component of the first session management function network element (such as a processor, a chip, or a chip system, etc.). The first session management function network element is used to manage a first session of a terminal device. The method includes: the first session management function network element receives a first message. Among them, the first message can be used to indicate that a radio access network has been changed for the terminal device, and the first message includes at least one of the first identification information of the first network device and the radio access network change indication (RAN change notification) of the terminal device. Alternatively, the first message can be used to request an update of the first session and the first message includes the first identification information of the first network device. Here, the first network device is a network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element. The first session management function network element updates the target session context according to the first message, so that the updated target session context does not include the second identification information of the second network device. Among them, the target session context is the session context of the first session, the second network device is the anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element.

[0007] In the above implementation, the first session management function network element receives a first message indicating that the terminal device has changed its wireless access network or requests to update the first session it manages, and updates the target session context stored in it, so that the updated target session context no longer contains the identification information of the anchor network device of the terminal device, so that the first session management function network element no longer interacts with the anchor network device. This method can solve the problem of invalid interaction between the session management function network element and the anchor network device caused by the change of the wireless access network of the terminal device in the RRC connection state, and reduce the waste of communication resources.

[0008] In combination with the first aspect, in a possible implementation method, when a first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of first identification information of a first network device and an indication of wireless access network change of the terminal device, the first session management function network element updates the target session context according to the first message, which may include: the first session management function network element deletes the second identification information of the second network device included in the target session context according to the first message to obtain an updated target session context.

[0009] Exemplarily, when the first message includes an indication of a wireless access network change of the terminal device, the first session management function network element may delete the second identification information of the second network device included in the target session context to obtain an updated target session context.

[0010] In combination with the first aspect, in a possible implementation method, when a first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of first identification information of the first network device and an indication of wireless access network change of the terminal device, the first session management function network element updates the target session context according to the first message, which may include: the first session management function network element replaces the second identification information of the second network device included in the target session context with the first identification information of the first network device according to the first message to obtain an updated target session context.

[0011] Exemplarily, the first session management function network element may replace the second identification information of the second network device included in the target session context with the first identification information of the first network device when the first message includes the first identification information of the first network device, so as to obtain an updated target session context.

[0012] In conjunction with the first aspect, in a possible implementation, when a first message is used to indicate that a terminal device has a radio access network change and the first message includes at least one of first identification information and a radio access network change indication, the first message may come from a first network element. The first network element is used to store a terminal device context of the terminal device or to be responsible for access management of the terminal device.

[0013] In the above implementation, the first message is provided by the first network element that stores the terminal device context of the terminal device or is responsible for the access management of the terminal, so that the first session management function network element can update the target session context in a timely manner, thereby effectively avoiding invalid interaction between the first session management function network element and the second network device.

[0014] In combination with the first aspect, in a possible implementation, the first session management function network element may send a second message to the first network element when the first condition is met. The second message may be used to subscribe to a mobility event of the terminal device. In other words, the second message may be used to trigger the first network element to send the first message to the first session management function network element.

[0015] In the above implementation, the first session management function network element obtains the first message by subscription, which can avoid frequent interactions between the first session management function network element and the first network element on the one hand, and ensure the timeliness of the first message by subscription on the other hand.

[0016] Optionally, the mobility event subscribed to by the second message may include: a change of radio access network of the terminal device.

[0017] Optionally, the above-mentioned first condition may include at least one of the following: the first session is established, the first session is in an activated state, and the terminal device enters an RRC inactivated state.

[0018] Optionally, when the first condition includes the terminal device entering an RRC inactive state, the method further includes: the first session management function network element receives an RRC inactive state indication of the terminal device. Here, the RRC inactive state indication of the terminal device is used to indicate that the terminal device is in an RRC inactive state. The first session management function network element determines that the terminal device is in an RRC inactive state based on the RRC inactive state indication, and further determines that the first condition is satisfied.

[0019] Further, the RRC inactive state indication may come from the second network device. Furthermore, the RRC inactive state indication may be sent by the second network device when it is determined that the terminal device enters the RRC inactive state.

[0020] In combination with the first aspect, in a possible implementation manner, the second message may include a radio access network change notification request of the terminal device. Further, the second message may also include fifth identification information of the terminal device.

[0021] In conjunction with the first aspect, in a possible implementation, the method may further include: when the second condition is met, the first session management function network element sends a third message to the first network element, wherein the third message is used to cancel the subscription to the mobility event of the terminal device.

[0022] In the above implementation, if the second condition is met, the subscription to the mobility event of the terminal device is cancelled, which can avoid the situation where the first network element still provides the first message to the first session management function network element when there is no demand from the first session management function network element, thereby avoiding invalid interaction between the first session management function network element and the first network element.

[0023] Optionally, the second condition may include at least one of the following: the first session is released, the first session is in a deactivated state, and the terminal device leaves the RRC inactive state. Here, the terminal device leaving the RRC inactive state can also be understood as the terminal device moving out of the RRC inactive state.

[0024] In combination with the first aspect, in a possible implementation manner, the first network element may include a first access and mobility management function (AMF) network element or a unified data repository (UDR) network element.

[0025] Optionally, in the case where the first network element is a unified database network element, the first message may be generated by the unified database based on a mobility information notification message (mobility information notification message) provided by the first access and mobility management function network element.

[0026] Optionally, the mobile information notification message may include the fifth identification information of the terminal device, and at least one of the first identification information of the first network device and the wireless access network change indication of the terminal device.

[0027] In combination with the first aspect, in a possible implementation method, when the first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of the first identification information of a first network device and an indication of a wireless access network change of the terminal device, the first message may also include fifth identification information of the terminal device.

[0028] In combination with the first aspect, in a possible implementation manner, when the first message is used to request updating of the first session and the first message includes first identification information of the first network device, the first message may come from the first network device.

[0029] In the above implementation, since the first network device is a network device newly connected to the terminal device, the first network device provides the first message to request updating the first session, which can also make the target session context updated in a timely manner, thereby effectively avoiding invalid interactions between the first session management function network element and the anchor network device.

[0030] In combination with the first aspect, in a possible implementation method, when the first message is used to request an update of a first session and the first message includes first identification information of a first network device, the first session management function network element updates the target session context according to the first message, including: replacing the second identification information of the second network device in the target session context with the first identification information of the first network device to obtain an updated target session context.

[0031] In this case, the first message may also include access network tunnel information (AN tunnel info) of the first network device. The method also includes: the first session management function network element sends the access network tunnel information of the first network device to the user plane function (UPF) network element, so that the user plane function network element replaces the access network tunnel information corresponding to the second network device stored by it with the access network tunnel information corresponding to the first network device.

[0032] In combination with the first aspect, in a possible implementation, the method may further include: the first session management function network element sends a session context release (release SM context) message to the second network device to instruct the second network device to release or delete the target session context stored therein. Optionally, the session context release message may include third identification information of the first session.

[0033] In combination with the first aspect, when the first message is used to request to update the first session and the first message includes the first identification information of the first network device, the first message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication (session modification) of the first session or a session modification message of the first session.

[0034] With reference to the first aspect, in a possible implementation manner, the first session is in an activated state.

[0035] In a second aspect, the present application provides a communication method. The method can be executed by a first network element, or by a component of the first network element (such as a processor, a chip, or a chip system, etc.). The method includes: the first network element receives a second message from a first session management function network element. The second message is used to subscribe to the mobility event of the terminal device. The first network element is used to store the terminal device context of the terminal device or to be responsible for the access management of the terminal device. The first session management function network element is used to manage the first session of the terminal device. The first network element sends a first message to the first session management function network element. The first message is used to indicate that the terminal device has a wireless access network change and the first message includes at least one of the first identification information of the first network device and the wireless access network change indication of the terminal device. The first network device is the network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element.

[0036] In the above implementation, when the first session management function network element subscribes to the mobility event of the terminal device, the first network element will send a first message so that the first session management function network element can be informed that the wireless access network of the terminal device has been changed. In this way, some invalid operations that may be performed by the first session management function network element due to the fact that the first session management function network element is unaware that the wireless access network of the terminal device has been changed can be avoided.

[0037] Optionally, the first message can be used by the first session management function network element to update the target session context of the first session so that the updated target session context does not include the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element.

[0038] In the above implementation, the first network element sends the first message so that the first session management function network element can update the target session context stored therein, and the updated target session context no longer contains the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device, thereby reducing the waste of communication resources caused by invalid interactions. In addition, the first network element that stores the terminal device context of the terminal device or is responsible for the access management of the terminal device provides the first message, which can also enable the first session management function network element to update the target session context in a timely manner.

[0039] In conjunction with the second aspect, in a possible implementation manner, the second message may include a radio access network change notification request of the terminal device. Optionally, the second message also includes fifth identification information of the terminal device.

[0040] In conjunction with the second aspect, in a possible implementation, sending the first message to the first session management function network element may include: sending the first message to the first session management function network element when a third condition is met. The third condition may include at least one of the following: receiving a fourth message from the first network device and the fourth message is used to update the location information of the terminal device, determining that the terminal device has a radio access network change in a non-RRC connection recovery situation, and determining that the terminal device has a radio access network change in a non-switching scenario.

[0041] Optionally, the fourth message may be a mobility registration updating (MRU) message sent by the terminal device through the first network device.

[0042] In combination with the second aspect, in a possible implementation manner, the first network element may include a first access and mobility management function network element.

[0043] In conjunction with the second aspect, in a possible implementation, the first network element may include a unified database network element. It should be understood that this implementation is applicable to the case where the first access and mobility management function network element and the first session management function network element cannot communicate directly (eg, there is no interface).

[0044] Optionally, when the first network element includes a unified database network element, the first message may be generated by the unified database network element based on a mobility information notification message sent by the first access and mobility management function network element. Exemplarily, the mobility information notification message may include fifth identification information of the terminal device, and at least one of the first identification information of the first network device and a radio access network change indication of the terminal device.

[0045] Further, the first access and mobility management function network element sends a mobile information notification message to the unified database network element when determining that the third condition is satisfied. Here, the specific content of the third condition is described above and will not be repeated here.

[0046] Furthermore, before sending the first message, the unified database network element may also determine that the first session is in an activated state.

[0047] In a third aspect, the present application provides a communication method. The method can be executed by a first network device, or by a component of the first network device (such as a processor, a chip, or a chip system, etc.). The method includes: the first network device obtains a terminal device context of a terminal device. Among them, the terminal device context of the terminal device includes the third identification information of the first session of the terminal device and the fourth identification information of the first session management function network element, and the first session management function network element is used to manage the first session. The first network device sends a first message to the first session management function network element. The first message is used to request an update of the above-mentioned first session, and the first message includes the first identification information of the first network device. Here, the first network device is a network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element.

[0048] In the above implementation, the first network device will send a first message to the first session management function network element according to the terminal device context of the terminal device to request the first session management function network element to update the first session. This can avoid some invalid operations that may be performed by the first session management function network element due to the failure to update the session context of the first session in time.

[0049] Further, the first message can be used by the first session management function network element to update the target session context of the first session so that the updated target session context does not include the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element.

[0050] In the above implementation, the first message enables the first session management function network element to update the target session context stored therein, and the updated target session context no longer contains the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device, thereby reducing the waste of communication resources caused by invalid interactions.

[0051] In conjunction with the third aspect, in a possible implementation, the first network device obtains the terminal device context of the terminal device, which may include: the first network device sends a fifth message to the first network element. The fifth message is used to request the terminal device context of the terminal device. The first network device may receive a sixth message from the first network element. The sixth message includes the terminal device context of the terminal device. The first network element is used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device.

[0052] Optionally, the fifth message may be a mobile registration update message of the terminal device.

[0053] In the above implementation, the first network device will actively request the terminal device context of the terminal device from the first network element, which can ensure the timeliness and reliability of obtaining the terminal device context.

[0054] In conjunction with the third aspect, in a possible implementation, the first network device may send the fifth message to the first network element when the RRC connection recovery of the terminal device fails. Alternatively, the first network device may send the fifth message to the first network element when an RRC connection is established between the first network device and the terminal device.

[0055] Optionally, the first network device may determine that the RRC connection recovery of the terminal device has failed based on a target RRC message provided by the terminal device. The target RRC message may include an RRC connection recovery failure indication of the terminal device and a mobile registration update message of the terminal device.

[0056] In combination with the third aspect, in a possible implementation manner, the terminal device context of the terminal device may be provided by the second network device to the first network element.

[0057] Optionally, the terminal device context of the terminal device may be sent by the second network device to the first network element when the second network device determines that the terminal device enters an RRC inactive state.

[0058] In combination with the third aspect, in a possible implementation manner, the first network element may include a first access and mobility management function network element or a unified database network element.

[0059] In conjunction with the third aspect, in a possible implementation, when the first network element is a first access and mobility management function network element, the terminal device context of the terminal device may be actively pushed to the first network device by the first access and mobility management function network element. For example, after receiving the mobile registration update message of the terminal device, the first access and mobility management function network element may actively send the terminal device context of the terminal device to the first network device.

[0060] In combination with the third aspect, in a possible implementation, the first network device obtains the terminal device context of the terminal device, which may include: when the RRC connection of the terminal device is successfully restored, the first network device sends a context retrieval request (retrieveUEcontext request) of the terminal device to the second network device. Here, the second network device is an anchor network device of the terminal device. The first network device receives a context retrieval response (retrieveUEcontext response) from the second network device. The context retrieval response includes the terminal device context of the terminal device.

[0061] Optionally, the context retrieval request may include fifth identification information of the terminal device.

[0062] In conjunction with the third aspect, in a possible implementation, the first message may further include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may further include a session modification indication of the first session or a session modification message of the first session.

[0063] In combination with the third aspect, in a possible implementation manner, the first session is in an activated state.

[0064] In combination with the third aspect, in a possible implementation, the method may further include: the first network device sends an eighth message to the second session management function network element. The eighth message is used to request the second session management function network element to update the session context of the second session, and the updated session context of the second session does not include the second identification information of the second network device. The eighth message includes the sixth identification information of the second session.

[0065] Furthermore, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the eighth message may also include a session modification indication corresponding to the second session or a session modification message of the second session.

[0066] In combination with the third aspect, in a possible implementation manner, the second session is in an activated state.

[0067] In a fourth aspect, the present application provides a communication method. The method can be executed by a terminal device, or by a component of the terminal device (such as a processor, a chip, or a chip system, etc.). The method includes: in the event that the radio resource control RRC connection recovery fails, the terminal device sends a fourth message to the first network device. Among them, the fourth message can be used to update the location information of the terminal device, the first network device is the network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element. The terminal device also sends a seventh message to the first network device. Among them, the seventh message can be used to request an update of the first session of the terminal device, and the seventh message includes the third identification information of the first session, and the first session is managed by the first session management function network element.

[0068] In the above implementation, when the wireless resource control RRC connection recovery fails, the terminal device will actively send the seventh message to the first network device to prompt or trigger the update of the first session of the terminal device, thereby avoiding some invalid operations that may be caused by the failure to update the first session in time.

[0069] Further, the seventh message can be used to enable the first network device to send a first message to the first session management function network element. The first message can be used by the first session management function network element to update the target session context of the first session so that the updated target session context does not include the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element.

[0070] In the above implementation, the first message enables the first session management function network element to update the target session context stored therein, and the updated target session context no longer contains the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device, thereby reducing the waste of communication resources caused by invalid interactions.

[0071] In conjunction with the fourth aspect, in a possible implementation manner, the first session may be in an activated state.

[0072] In combination with the fourth aspect, in a possible implementation manner, the seventh message may also include a session modification indication corresponding to the first session.

[0073] In conjunction with the fourth aspect, in a possible implementation, the first message may further include fifth identification information of the terminal device and access network tunnel information of the first network device. Optionally, the first message may further include a session modification indication corresponding to the first session or a session modification message of the first session.

[0074] In combination with the fourth aspect, in a possible implementation, the seventh message may also include sixth identification information of the second session of the terminal device. It should be understood that the second session may be managed by a second session management function network element other than the first session management function network element. Optionally, the seventh message may also include a session modification indication of the second session or a session modification message corresponding to the second session.

[0075] Alternatively, the terminal device may also send a twelfth message to the first network device. The twelfth message is used to request to update the second session of the terminal device. The twelfth message includes the sixth identification information of the second session, and the second session is managed by a second session management function network element other than the first session management function network element. Optionally, the twelfth message may also include a session modification indication of the second session or a session modification message corresponding to the second session.

[0076] Here, the first network device, the second network device and the second session management function network element are also directly connected.

[0077] In this case, the first network device also sends an eighth message to the second session management function network element. The eighth message is used to request the second session management function network element to update the session context of the second session, and the updated session context of the second session does not include the second identification information of the second network device. The eighth message includes the sixth identification information of the second session.

[0078] Furthermore, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication corresponding to the second session or a session modification message of the second session.

[0079] In a fifth aspect, the present application provides a communication method. The method can be executed by a first network device, or by a component of the first network device (such as a processor, a chip, or a chip system, etc.). The method includes: the first network device receives a fourth message sent by the terminal device when the RRC connection recovery fails. Among them, the fourth message can be used to update the location information of the terminal device, the first network device is the network device currently connected to the terminal device, and the first network device is directly connected to the first session management function network element. The first network device receives a seventh message from the terminal device. Among them, the seventh message can be used to request an update of a first session of the terminal device, and the seventh message includes the third identification information of the first session, and the first session is managed by the first session management function network element. The first network device sends a first message to the first session management function network element, wherein the first message can be used to request an update of the first session and the first message includes the first identification information of the first network device.

[0080] In the above implementation, the first network device will send a first message for requesting to update the first session to the first session management function network element based on the seventh message sent by the terminal device, thereby avoiding some invalid operations that may be caused by the first session management function network element not being updated in time.

[0081] In combination with the fifth aspect, in a possible implementation manner, the seventh message may also include a session modification indication corresponding to the first session.

[0082] In conjunction with the fifth aspect, in a possible implementation, the first message may also include fifth identification information of the terminal device and access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication corresponding to the first session or a session modification message corresponding to the first session.

[0083] In conjunction with the fifth aspect, in a possible implementation, the first network device may send a ninth message to a unified database network element or a network function repository (NRF) network element. The ninth message may include third identification information of the first session. The first network device may receive a tenth message from the unified database network element or the network function repository network element, wherein the tenth message includes fourth identification information of a first session management function network element that manages the first session.

[0084] In combination with the fifth aspect, in a possible implementation manner, the seventh message also includes fourth identification information of the first session management function network element.

[0085] In conjunction with the fifth aspect, in a possible implementation, the first network device may receive an eleventh message from the first access and mobility management function network element. The eleventh message includes identification information of multiple sessions and identification information of multiple session management function network elements that manage the multiple sessions. It should be understood that the multiple sessions include at least the first session, and the identification information of the multiple session management function network elements includes at least fourth identification information of the first session management function network element that manages the first session. The first network device obtains the fourth identification information according to the eleventh message.

[0086] In conjunction with the fifth aspect, in a possible implementation, the seventh message may also include sixth identification information of the second session of the terminal device. It should be understood that the second session may be managed by a second session management function network element other than the first session management function network element, and the first network device is also directly connected to the second session management function network element.

[0087] Alternatively, the first network device may receive a twelfth message from the terminal device, and the twelfth message may be used to request an update of a second session of the terminal device. The twelfth message includes sixth identification information of the second session. The second session is managed by a second session management function network element, and the first network device is also directly connected to the second session management function network element.

[0088] In this case, the method may further include: the first network device sends an eighth message to the second session management function network element. The eighth message is used to request the second session management function network element to update the session context of the second session, and the updated session context of the second session does not contain the second identification information of the second network device. The eighth message includes the sixth identification information of the second session. Furthermore, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the eighth message may also include a session modification indication corresponding to the second session or a session modification message corresponding to the second session.

[0089] Optionally, in this case, the seventh message may further include a session modification indication of the second session or a session modification message corresponding to the second session.

[0090] In conjunction with the fifth aspect, in a possible implementation manner, the ninth message may further include sixth identification information of the second session. The tenth message may further include seventh identification information of a second session management function network element that manages the second session.

[0091] In combination with the fifth aspect, in a possible implementation manner, the seventh message may also include seventh identification information of the second session management function network element.

[0092] In combination with the fifth aspect, in a possible implementation manner, the multiple sessions in the eleventh message also include the second session, and the identification information of the multiple session management function network elements may also include the seventh identification information of the second session management function network element.

[0093] In a sixth aspect, the present application provides a communication method. The method can be executed by a terminal device, or by a component of the terminal device (such as a processor, a chip, or a chip system). The method includes: obtaining target information. The target information includes tracking area information of a second network device, and the second network device is an anchor network device of the terminal device. Send the target information to the first network device. Among them, the first network device is the network device currently connected to the terminal device, and the tracking area information in the target information can be used to enable the first network device to obtain the terminal device context of the terminal device.

[0094] In the above implementation, the terminal device will actively provide the tracking area information of the anchor network device to the first network device currently connected. When RRC connection recovery is required and the terminal device has changed its wireless access network, even if the first network device cannot directly obtain the terminal device context of the terminal device from the anchor network device, the first network device can still obtain the terminal context of the terminal device through the tracking area information, thereby avoiding the failure of RRC connection recovery caused by the inability of the first network device to obtain the terminal device context of the terminal device. By adopting this method, the success rate of RRC connection recovery of the terminal device can be improved, thereby reducing the impact of the failure of RRC connection recovery.

[0095] In combination with the sixth aspect, in a possible implementation manner, the target information may be an inactive radio network temporary identifier (I-RNTI) of the terminal device.

[0096] In combination with the sixth aspect, in a possible implementation manner, the target information may also include fifth identification information of the terminal device and second identification information of the second network device.

[0097] In combination with the sixth aspect, in a possible implementation method, the target information may be carried in an RRC connection recovery request sent by the terminal device to the first network device.

[0098] In a seventh aspect, the present application provides a communication method. The method can be executed by a first access and mobility management function network element, or by a component (such as a processor, a chip, or a chip system) in the first access and mobility management function network element. The method includes: the first access and mobility management function network element receives target information from a first network device. The target information may include tracking area information of a second network device, the first network device is a network device currently accessed by the terminal device, and the second network device is an anchor network device of the terminal device. The first access and mobility management function network element obtains a terminal device context of the terminal device according to the tracking area information, and sends the obtained terminal device context to the first network device.

[0099] In the above implementation, the first access and mobility management function network element obtains the terminal device context of the terminal device based on the tracking area information of the anchor network device provided by the first network device, and provides it to the first network device. With this method, when the first network device cannot directly obtain the terminal device context of the terminal device from the anchor network device, the first network device can still obtain the terminal context of the terminal device through the first access and mobility management function network element, thereby avoiding the failure of RRC connection recovery caused by the first network device being unable to obtain the terminal device context of the terminal device.

[0100] In combination with the seventh aspect, in a possible implementation, the first access and mobility management function network element obtains the terminal device context of the terminal device according to the tracking area information, which may include: when the first tracking area information range corresponding to the first access and mobility management function network element includes the tracking area information, or when the first access and mobility management function network element manages the second network device, the first access and mobility management function network element may send a context retrieval request for the terminal device to the second network device. The context retrieval request may include the above-mentioned target information. The first access and mobility management function network element may receive a context retrieval response from the second network device. The context retrieval response may include the terminal device context of the terminal device.

[0101] It can be understood that the terminal context of the terminal device can be determined by the second network device based on the target information. Exemplarily, the target information can also include the fifth identification information of the terminal device. The second network device can query the terminal device context of the terminal device based on the fifth identification information.

[0102] In combination with the seventh aspect, in a possible implementation, the first access and mobility management network element obtains the terminal device context of the terminal device based on the tracking area information, and may also include: when the first tracking area information range corresponding to the first access and mobility management function network element does not include the tracking area information, or when the first access and mobility management function network element does not manage the second network device, the first access and mobility management function network element may send the target information to the second access and mobility management function network element. Here, the second tracking area information range corresponding to the second access and mobility management function network element includes the tracking area information in the target information. In other words, the second access and mobility management function network element manages the second network device. The first access and mobility management function network element may receive the terminal device context from the second access and mobility management function network element.

[0103] In combination with the seventh aspect, in a possible implementation, the target information may be an I-RNTI of the terminal device.

[0104] In combination with the seventh aspect, in a possible implementation manner, the target information may also include fifth identification information of the terminal device and second identification information of the second network device.

[0105] In an eighth aspect, the present application provides a communication method. The method may be executed by a first network device, or by a component of the first network device (such as a processor, a chip, or a chip system). The method includes: the first network device receives target information from a terminal device. The target information may include tracking area information of a second network device. Here, the first network device is a network device currently accessed by the terminal device, and the second network device is an anchor network device of the terminal device. The first network device sends target information to a first access and mobility management function network element. The first network device may receive a terminal device context from the first access and mobility management function network element. It should be understood that the terminal device context of the terminal device may be obtained by the first access and mobility management function network element based on the target information.

[0106] In the above implementation, the first network device provides the tracking area information of the anchor network device provided by the terminal device to the first access and mobility management function network element, so that the first access and mobility management function network element provides it with the terminal device context of the terminal device. With this method, when the first network device cannot directly obtain the terminal device context of the terminal device from the anchor network device, it can still obtain the terminal context of the terminal device through the first access and mobility management function network element, thereby avoiding the failure of RRC connection recovery caused by the first network device being unable to obtain the terminal device context of the terminal device.

[0107] In conjunction with the eighth aspect, in a possible implementation, the first network device may send the target information to the first access and mobility management function network element when the terminal device context of the terminal device cannot be directly obtained from the second network device. It should be understood that the target information is sent only when it cannot be directly obtained from the second network device, so that the situation of repeatedly obtaining the terminal device context can be avoided, and communication resources can be saved.

[0108] In combination with the eighth aspect, in a possible implementation manner, the target information may be an I-RNTI of the terminal device.

[0109] In combination with the eighth aspect, in a possible implementation manner, the target information may also include fifth identification information of the terminal device and second identification information of the second network device.

[0110] In a ninth aspect, the present application provides a communication device, which includes various modules or units for executing the method provided by any aspect of the first to eighth aspects above or any possible implementation of any aspect.

[0111] In the tenth aspect, the present application provides a computer program product, which includes instructions. When the instructions are executed on a computer, the computer executes the communication method provided by any aspect of the first to eighth aspects or any possible implementation of any aspect.

[0112] In the eleventh aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed, it executes the communication method provided by any aspect of the first to eighth aspects or any possible implementation of any aspect.

[0113] In a twelfth aspect, the present application provides a communication device, at least one processor and a memory. The memory is used to store a computer program. The processor is used to execute the computer program stored in the memory, so that the communication device performs the communication method provided by any aspect of the first to eighth aspects or any possible implementation of any aspect.

[0114] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0115] It should be understood that the relevant data interaction process, such as sending information, can be a process of outputting information from a processor, and receiving information can be a process of receiving information by a processor. Specifically, the data output by the processor can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0116] In a thirteenth aspect, the present application provides a chip, the chip comprising at least a processor. The processor is used to execute computer execution instructions so that a device equipped with the chip executes the communication method provided by any aspect of the first to eighth aspects or any possible implementation of any aspect.

[0117] In conjunction with the thirteenth aspect, in a possible implementation, the chip may further include an interface circuit. The interface circuit is used to receive computer execution instructions and transmit them to the processor.

[0118] In a fourteenth aspect, the present application provides a communication system, which may include the terminal device, the first network device, the second network device, the first network element, and the first session management function network element as described above.

[0119] Optionally, the communication system may further include a second session management function network element.

[0120] It should be understood that the communication method provided by any one of the first to fifth aspects above or any possible implementation of any one of the aspects is applicable to the communication system.

[0121] In a fifteenth aspect, the present application provides a communication system, which may include the terminal device, the first network device, the second network device, and the first access and mobility management function network element as described above.

[0122] Optionally, the communication system may further include a second access and mobility management function network element.

[0123] It should be understood that the communication method provided by any one of the sixth to eighth aspects above or any possible implementation of any one of the aspects is applicable to the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0124] Figure 1 It is a schematic diagram of a network architecture provided by this application;

[0125] Figure 2 It is a structural diagram of a communication system provided by the present application;

[0126] Figure 3 It is a structural diagram of another communication system provided by the present application;

[0127] Figure 4 It is a flow chart of a communication method provided by the present application;

[0128] Figure 5 It is another flow chart of a communication method provided by the present application;

[0129] Figure 6 It is another flow chart of a communication method provided by the present application;

[0130] Figure 7 It is another flow chart of a communication method provided by the present application;

[0131] Figure 8 It is another flow chart of a communication method provided by the present application;

[0132] Fig. 9 It is another flow chart of a communication method provided by the present application;

[0133] Fig.10 It is another flow chart of a communication method provided by the present application;

[0134] Fig.11 It is another flow chart of a communication method provided by the present application;

[0135] Fig.12 It is another flow chart of a communication method provided by the present application;

[0136] Fig.13 It is a structural schematic diagram of a communication device provided by the present application;

[0137] Fig.14 This is a structural diagram of another communication device provided by the present application. DETAILED DESCRIPTION

[0138] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings provided in the embodiments of the present application.

[0139] It should be understood that the technical solution provided in the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), in addition, it can also be applicable to the use of subsequent evolution systems, such as sixth generation communication systems and even more advanced seventh generation communication systems.

[0140] See also Figure 1 , Figure 1 This is a network architecture diagram provided by this application. It should be understood that Figure 1 The network architecture shown can be called a network architecture in which access network equipment and session management function network elements are directly connected. Figure 1 As shown in FIG. 1 , the network architecture may include three parts: a terminal device (UE) 10, an access network (AN) device, and a core network (CN). The access network device is mainly used to implement functions related to wireless access of the UE 10, and may include Figure 1 The RAN device 11 shown in the figure and other devices that may be accessed through the air interface. The core network mainly includes one or more of the following: user plane function (UPF) network element 12, data network (DN) 13, session management function network element 14, registration function network element 15, policy control function (PCF) network element 16, short message service function (SMSF) network element 17, selection function network element 18, identification storage function network element 19 and unified data management (UDM) network element 20. It should be understood that there are interfaces between each network element to achieve distributed connection. For example, the network architecture can be a network architecture after the introduction of RAN service, and the interfaces between the RAN device 11 and each network element can all be service-oriented interfaces.

[0141] To facilitate understanding of the functions of the network architecture, the functions of each network element are briefly described below.

[0142] The user plane function network element 12 is mainly responsible for processing user messages, such as forwarding, billing, etc. It can be used as an anchor point for the protocol data unit (PDU) session (i.e., PDU session) connection, that is, it can be used as a PDU session anchor (PSA), responsible for filtering data messages of UE10, data transmission or forwarding, rate control, generating billing information, quality of service (QoS) processing of user plane sessions, uplink transmission authentication, transmission level verification, downlink data packet caching and downlink data notification triggering, etc. The user plane function network element 12 can also serve as a branch point for multi-homed PDU sessions.

[0143] The data network 13 is a network that provides data transmission services for users, such as the Internet Protocol (IP) Multimedia Service (IMS), the Internet, etc. The data network 13 may include an application server (AS), which is a software framework that provides an environment for application program operation and is used to provide security, data, transaction support, load balancing, large-scale distributed system management, and other services for the application program. The terminal device obtains the application message by communicating with the application server.

[0144] The session management function network element 14 is mainly responsible for all control plane functions of session management of terminal devices, including selection and control of the user plane function network element 12, IP address allocation and management, QoS management of sessions, and obtaining policy and charging control (PCC) policies from the policy control function network element 16. The session management function network element 14 also serves as the termination point of the session management part in the non-access stratum (NAS) message.

[0145] The registration function network element 15 may be used to provide access and authentication functions for the UE 10 (or user). Exemplarily, the registration function network element 15 may include an access and mobility management function network element 151 .

[0146] The policy control function network element 16 has the function of providing policy rules to the control plane function entity.

[0147] The SMS function network element 17 is responsible for processing SMS services in the network, such as SMS registration and deregistration, SMS forwarding, SMS call buffering, etc.

[0148] The selection function network element 18 can be used to select a core network element for the UE 10. Specifically, the core network elements in the network can be registered with the selection function network element 18, and then the selection function network element 18 can select a target core network element for the UE 10 from the registered core network elements. The selection function network element 18 can also obtain the subscription data of the UE 10 from the unified data management network element 20, and then select the target core network element for the terminal device 10 based on the core network element registration information and the subscription data. Exemplarily, the selection function network element 18 may include a network function repository function (NFR) network element 181.

[0149] The identification storage function network element 19 may be used to store the correspondence between the temporary identification and the permanent identification of the UE 10, wherein after the network function registration function network element 181 obtains the correspondence between the temporary identification and the permanent identification of the UE 10, the correspondence between the temporary identification and the permanent identification of the UE 10 may be stored in the identification storage function network element 19. Exemplarily, the identification storage function network element 19 may be a unified database network element 191.

[0150] The unified data management network element 20 is mainly responsible for the subscription data management of the UE 10 , including the storage and management of the identification of the UE 10 , the access authorization of the UE 10 , etc.

[0151] It should be noted that the naming of each network element in the core network in the embodiment of the present application is exemplary and not limiting. With the evolution of technology, entities with corresponding functions of each network element may also adopt other naming methods, and there is no specific limitation on this. For example, for access and mobility management network elements, they may be named access management function network element, mobility management function network element, registration management function network element, etc.

[0152] It should be understood that the wireless access network provided in the present application may be a cellular system related to the third generation partnership project (3GPP), for example, a 4G, 5G mobile communication system, or a future-oriented evolution system. The wireless access network may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. Alternatively, the wireless access network may also be a communication system that integrates two or more of the above systems.

[0153] It should be understood that in the embodiments of the present application, the wireless access network device may sometimes be referred to as a RAN node, an access network device, a network device, a RAN entity or an access node, etc. For ease of understanding, the embodiments of the present application will be described uniformly as a network device. In actual work, the network device is mainly used to help the terminal device achieve wireless access.

[0154] In one possible scenario, the network device may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. Optionally, the network device may also be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. Optionally, the network device may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the network device in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The network device may also be provided with a communication module, circuit or chip that performs the corresponding communication function. The network device may also be configured with program instructions for performing the corresponding communication function and corresponding program instructions. The network device in this application may also be a logical node, a logical module or software that can implement all or part of the network device functions.

[0155] In another possible scenario, multiple network devices may collaborate to assist the terminal in achieving wireless access, and different network devices may respectively implement part of the functions of the base station. For example, the network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be separately configured, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0156] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0157] It should be understood that in the embodiments of the present application, the terminal device may be a device or module with a corresponding communication function. The terminal device may also be referred to as a terminal, a user equipment, a mobile station, a mobile terminal, etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, a transport vehicle with wireless communication function, a communication module, etc. It should be understood that the embodiments of the present application do not limit the device form of the terminal device. In addition, a communication module, a circuit or a chip for performing a corresponding communication function is usually provided in the terminal device. The terminal device is also configured with program instructions for performing the corresponding communication function.

[0158] The foregoing briefly describes the network architecture applicable to the method provided by the present application. The following describes the structures of various communication systems applicable to the embodiments of the present application. It should be understood that the various communication systems applicable to the embodiments of the present application can adopt Figure 1 The network architecture is shown.

[0159] See also Figure 2 , Figure 2 This is a schematic diagram of the structure of a communication system provided by this application, which is applicable to the communication method provided by this application. Figure 2As shown, the communication system may include a terminal device, a first network device and a second network device on the wireless access network side, and a first session management function network element and a first network element on the core network side. In an embodiment of the present application, the first network element refers to a core network element for storing a terminal device context of the terminal device or for being responsible for access management of the terminal device. Exemplarily, the first network element may be an access and mobility management function network element or a unified database network element, etc.

[0160] Optional, such as Figure 2 As shown, the communication system may further include a second session management function network element.

[0161] Among them, the terminal device, the first network device, the second network device, the first session management function network element and the possible second session management function network element can work together to implement the various steps of the communication method provided in this application. For specific implementation, please refer to the corresponding description below.

[0162] See also Figure 3 , Figure 3 is a schematic diagram of the structure of another communication system provided by the present application, which is also applicable to the communication method provided by the present application. Figure 3 As shown, the communication system may include a terminal device, a first network device and a second network device on the wireless access network side, and a first access and mobility management function network element on the core network side.

[0163] Optional, such as Figure 3 As shown, the communication system may further include a second access and mobility management function network element.

[0164] Among them, the terminal device, the first network device, the second network device, the first access and mobility management function network element and the possible second access and mobility management function network element can work together to implement the various steps of the communication method provided in this application. For the specific implementation, please refer to the corresponding description below.

[0165] It should be understood that in the embodiments of the present application, Figure 2 or Figure 3 The communication systems shown are based on Figure 1 The network architecture shown is implemented.

[0166] The previous article is based on Figure 1-Figure 3 The network architecture and communication system structure applicable to the communication method provided in this application are described below. Figure 1-Figure 3 The network architecture and communication system structure shown provide a detailed description of the implementation process of the communication method provided in this application.

[0167] To facilitate understanding, several concepts involved in the embodiments of the present application are first briefly described.

[0168] 1. RRC connection recovery of terminal equipment (RRCResume)

[0169] In the 5G network, a new state is introduced for terminal devices, called the RRC inactive state. The RRC inactive state can be considered as an intermediate state between the RRC connected state (RRC connected state) and the RRC idle state (RRC idle state). Normally, when a terminal device moves out of the coverage of a currently connected network device and enters the coverage of a new network device, if the terminal device has not established a connection with the new network device, the terminal device will enter the RRC inactive state. For terminal devices in the RRC inactive state, the radio access network side and the core network side maintain a connection for the terminal device, and both the radio access network side and the core network side will save the context of the terminal device so that when the terminal device needs to restore the connection due to uplink requirements, it can quickly establish a channel for communication with the core network side.

[0170] In an embodiment of the present application, the RRC connection recovery of the terminal device refers to the transition process from the RRC inactive state to the RRC connected state triggered by the terminal device. In general, the process may include: (1) When the terminal device is in the RRC inactive state, it may trigger the need for RRC connection recovery due to receiving instructions from the network device or the need to send data. (2) The terminal device sends an RRC connection recovery request (RRC Resume Request) to the network device to request to restore to the RRC connected state. This RRC connection recovery request usually contains the identity information of the terminal device and necessary context information. (3) After receiving the RRC connection recovery request, the network device will perform operations such as verifying the identity of the terminal device and checking the status of network resources. If the network device determines that all conditions are met, it will inform the terminal device of the success of the RRC connection recovery through an RRC connection recovery response (RRC Resume Response) and re-establish the RRC connection with the terminal device. If the network device finds that there are insufficient resources, security issues or other technical failures, the network device will send an RRC connection recovery failure (RRC Resume failure) response to the terminal device to prompt the terminal device that the RRC connection recovery has failed, and may require the terminal device to retry the RRC connection recovery or take other corresponding measures.

[0171] Combination Figure 2 or Figure 3 It can be seen from the communication system structure shown that in the embodiment of the present application, the RRC connection recovery of the terminal device can specifically be the RRC connection recovery requested by the terminal device to the first network device. If the first network device cannot obtain the terminal device context of the terminal device for some reason, the RRC connection recovery fails.

[0172] 2. RAN change

[0173] In the embodiment of the present application, the replacement of the wireless access network refers to the process in which the terminal device disconnects from the old network device and connects to the new network device due to reasons such as movement. Figure 2 or Figure 3 In the communication system shown, the first network device and the second network device both belong to different access networks. As the terminal device moves, it moves from the coverage of the second network device to the coverage of the first network device, so the network device accessed by the terminal device is replaced by the second network device to the first network device, that is, the terminal device undergoes a network device replacement. In this case, the second network device can also be referred to as the anchor network device of the terminal device. It should be understood that in the embodiment of the present application, the anchor network device can be understood as a network device that stores the control plane connection between the radio access network side and the core network side of the terminal device in the RRC inactive state. Alternatively, the anchor network device can be a radio access network device that stores the terminal device context of the terminal device when the terminal device is in the RRC inactive state. Alternatively, the anchor network device can be a radio access network device of the terminal device stored by the control plane network element on the core network side when the terminal device is in the RRC inactive state. It should also be understood that after the radio access network replacement is completed, the anchor network device of the terminal device will be replaced by the second network device to the first network device.

[0174] 3. Direct connection between network equipment and session management function network elements

[0175] It should be understood that in the network architecture to which the communication method provided in the embodiment of the present application is applicable, the network device and the session management function network element may be directly connected. Figure 1 The RAN device 11 and the session management function network element 14 are directly connected. The network device and the session management function network element are directly connected, which can be understood as the network device and the session management function network element can communicate directly. For example, the directly connected network device and the session management function network element can directly transmit messages or signaling through the NG interface (i.e., the interface between the wireless access network and the 5G core network) or the service-oriented interface.

[0176] Correspondingly, the network device and the session management function network element are not directly connected, which means that the network device and the session management function network element cannot communicate directly, and need to communicate indirectly through other network elements. For example, the network device and the session management function network element can communicate indirectly through the access and mobility management function network element.

[0177] Combination Figure 2 In the communication system shown in the embodiment of the present application, the first network device is directly connected to the first session management function network element. Similarly, the second network device is also directly connected to the first session management function network element.

[0178] At present, terminal devices in the RRC inactive state can move freely and access other RAN devices except the anchor network device, that is, the terminal device will undergo a change of radio access network. The existing RRC connection recovery solution is only applicable to the communication system architecture where the RAN device and the session management function network element are not directly connected. For the communication system architecture where the RAN device and the session management function network element are directly connected, there is no clear regulation on how to perform RRC connection recovery when the radio access network of the terminal device in the RRC inactive state is changed. This results in that after the RAN of the terminal device is changed, the session management function network element will still interact with the anchor network device, resulting in a waste of communication resources.

[0179] Therefore, the technical problem to be solved by this application is: in a scenario where RRC connection recovery is required and the wireless access network of the terminal device is changed, how to avoid invalid interaction between the session management function network element and the anchor network device, thereby reducing the waste of communication resources.

[0180] To solve the above problems, the present application provides a communication method. In the communication method, the first session management function network element receives a first message indicating that a terminal device has changed its wireless access network, and updates the target session context of the first session so that the updated target session context no longer contains the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device of the terminal device. Therefore, by using this method in the RRC connection recovery process, the problem of invalid interaction between the session management function network element and the anchor network device caused by the change of the wireless access network of the terminal device can be solved, and the waste of communication resources can be reduced.

[0181] See also Figure 4 , Figure 4 It is a flow chart of a communication method provided by this application. It should be understood that Figure 4 The communication method shown is applicable to the previous Figure 2 The communication system shown in FIG. Figure 4 As shown, the method comprises the following steps:

[0182] S415: The first network element sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0183] In some feasible implementations, the first network element may send a first message to the first session management function network element. The first message may be used to indicate that a radio access network has been changed for the terminal device, and the first message includes at least one of the first identification information of the first network device and the radio access network change indication of the terminal device. Here, the first network device is a network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element. It should be understood that the radio access network change indication of the terminal device is information that can be directly used to indicate that a radio access network has been changed for the terminal device, such as a radio access network change notification (RAN change notification) of the terminal device. The first message may be used by the first session management function network element to update the target session context of the first session, so that the updated target session context no longer includes the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device that has undergone a radio access network change, and the second network device is also directly connected to the first session management function network element. In an embodiment of the present application, the first network element may be used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device.

[0184] It should be noted that, in the embodiment of the present application, the first network element may be implemented in a variety of different ways. The specific implementation process of step S415 will be described in detail below in combination with different implementation ways of the first network element.

[0185] Implementation method 1 of the first network element:

[0186] In a possible implementation, the first network element may be a first access and mobility management function network element. It can be understood that this implementation is applicable to the case where the first session management function network element and the first access and mobility management function network element can communicate directly (eg, an interface exists between the two).

[0187] In this implementation, the first network element may send a first message to the first session management function network element when determining that a preset third condition is satisfied. Here, the third condition may include at least one of the following: receiving a fourth message from the first network device and the fourth message is used to update the location information of the terminal device, determining that the terminal device has a radio access network change in a non-RRC connection recovery situation, and determining that the terminal device has a radio access network change in a non-switching scenario.

[0188] That is to say, if the first access and mobility management function network element receives the fourth message from the first network device and determines that the fourth message is used to update the location information of the terminal device, the first message will be sent to the first session management function network element. Alternatively, if the first access and mobility management function network element determines that the terminal device has undergone a radio access network change in a non-RRC connection recovery situation, the first message will be sent to the first session management function network element. Alternatively, if the first access and mobility management function network element determines that the terminal device has undergone a radio access network change in a non-switching scenario, the first message will be sent to the first session management function network element. Alternatively, if the first access and mobility management function network element determines that two or three of the above third conditions occur, the first message will be sent to the first session management function network element.

[0189] It should be understood that the description of the third condition here is only exemplary. In actual implementation, the third condition may also include other possible implementation methods, and this application does not impose any specific restrictions on this.

[0190] Implementation method 2 of the first network element:

[0191] In a possible implementation, the first network element may include a unified database network element. It can be understood that this implementation is applicable to the case where the first session management function network element and the first access and mobility management function network element cannot communicate directly (eg, there is no interface between the two).

[0192] In this implementation, the first message may be generated by the first network element and sent to the first session management function network element.

[0193] Optionally, the first message may be generated and sent by the unified database network element based on the mobile information notification message sent by the first access and mobility management function network element.

[0194] Specifically, the first access and mobility management function network element may send a mobile information notification message to the unified database network element when determining that the third condition is satisfied, and the mobile information notification message is used to inform the terminal device that a wireless access network change has occurred. Here, the specific content of the third condition can be found in the corresponding description in the first implementation method above, and will not be repeated here.

[0195] Exemplarily, if the first access and mobility management function network element receives a fourth message from the first network device and determines that the fourth message is used to update the location information of the terminal device, a mobile information notification message will be sent to the unified database network element. Alternatively, if the first access and mobility management function network element determines that the terminal device has undergone a change of wireless access network in a non-RRC connection recovery situation, a mobile information notification message will be sent to the unified database network element. Alternatively, if the first access and mobility management function network element determines that the terminal device has undergone a change of wireless access network in a non-switching scenario, a mobile information notification message will be sent to the unified database network element. Alternatively, if the first access and mobility management function network element determines that two or three of the third conditions occur, the above-mentioned mobile information notification message will be sent to the unified database network element.

[0196] Further, the unified database network element determines that the mobile information notification message from the first access and mobility management function network element is received, and can generate and send the above-mentioned first message to the first session management function network element.

[0197] Optionally, in an embodiment of the present application, the unified database network element may also send the above-mentioned first message only to the session management function network element used to manage the session in the activated state. For example, the first session management function network element will send the session state indication of the first session to the unified database network element. Then, if the unified database network element determines that the first session is in the activated state according to the session state indication of the first session, and also determines that the mobile information notification message from the first access and mobility management function network element is received, the above-mentioned first message will be sent to the first session management function network element. Correspondingly, if the unified database network element determines that the first session is not in the activated state according to the session state indication of the first session, even if it receives the mobile information notification message from the first access and mobility management function network element, it will not send the above-mentioned first message to the first session management function network element. In other words, in an embodiment of the present application, the first session is an activated session.

[0198] Optionally, the above-mentioned mobile information notification message may include the fifth identification information of the terminal device, and at least one of the first identification information of the first network device mentioned above and the wireless access network change indication of the terminal device.

[0199] In the above implementation, the first message is provided by the first network element that stores the terminal device context of the terminal device or is responsible for the access management of the terminal, so that the first session management function network element can update the target session context in a timely manner, thereby effectively avoiding invalid interaction between the first session management function network element and the second network device.

[0200] In one possible implementation, the fourth message may be a mobile registration update message (ie, an MRU message) of the terminal device, or may be other messages that can be used to indicate an update of the location information of the terminal device. The present application does not limit the implementation of the fourth message.

[0201] Exemplarily, for the first implementation mode of the first network element, the first access and mobility management function network element may send a first message to the first session management function network element when receiving a mobile registration update message of the terminal device. For the second implementation mode of the first network element, the first access and mobility management function network element may send a mobile information notification message to the unified database network element when receiving a mobile registration update message of the terminal device, so that the unified database network element can send the first message to the first session management function network element based on the mobile information notification message.

[0202] In a possible implementation, the above-mentioned non-RRC connection recovery situation may refer to scenarios other than RRC connection recovery triggered by the terminal device, such as a scenario where the RRC connection recovery of the terminal device fails. In this scenario, the terminal device will send a mobile registration update message to the network device so that the network device updates the latest location information of the terminal device. In the embodiment of the present application, non-RRC connection recovery can also be understood as RRC connection recovery failure.

[0203] In a possible implementation, the non-switching scenario may refer to a scenario other than the terminal device sending an access network device switching message to the network device, such as a scenario where the terminal device sends a mobile registration update message to the network when the RRC connection recovery of the terminal device fails.

[0204] Exemplarily, for the first implementation mode of the first network element, if the first access and mobility management function network element determines that the terminal device has undergone a radio access network change in a non-RRC connection recovery situation or a non-handover scenario, a first message may be sent to the first session management function network element. For the second implementation mode of the first network element, if the first access and mobility management function network element determines that the terminal device has undergone a radio access network change in a non-RRC connection recovery situation or a non-handover scenario, a mobile information notification message may be sent to the unified database network element.

[0205] In a possible implementation, the first message may further include fifth identification information of the terminal device. In this case, the first message may specifically be a mobile information notification message of the terminal device.

[0206] S416: The first session management function network element updates the target session context according to the first message, and the updated target session context does not include the second identification information of the second network device.

[0207] In some feasible implementations, after receiving the first message, the first session management function network element may update the target session context according to the first message so that the updated target session context does not include the second identification information of the second network device. The target session context is the session context corresponding to the first session of the terminal device. The first session management function network element is used to manage the first session. The second network device is an anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element. Before the terminal device changes its wireless access network, the terminal device accesses the second network device.

[0208] In a possible implementation, when the first message includes the first identification information of the first network device, the first session management function network element may replace the second identification information of the second network device in the target session context with the first identification information to obtain an updated target session context. That is, if the first session management function network element determines that the first message contains the first identification information of the first network device, the second identification information of the second network device in the target session context stored by the first network device may be replaced with the first identification information of the first network device, so that the updated target session context no longer contains the second identification information of the second network device. Alternatively, the first session management function network element updates the identification information of the access network device in the target session context, and replaces the second identification information of the second network device with the first identification information to obtain an updated target session context.

[0209] In a possible implementation, when the first message includes the radio access network change indication of the terminal device, the first session management function network element may delete the second identification information of the second network device in the target session context to obtain an updated target session context. That is, if the first session management function network element determines that the first message includes the radio access network change indication of the terminal device, the second identification information of the second network device in the target session context stored therein may be deleted, so that the updated target session context no longer includes the second identification information of the second network device.

[0210] In one possible implementation, when the first message includes both the first identification information of the first network device and the radio access network change indication of the terminal device, the first session management function network element may replace the second identification information of the second network device in the target session context with the first identification information to obtain an updated target session context.

[0211] It is also necessary to add that, when the first message includes the radio access network change indication of the terminal device but does not include the first identification information of the first network device, the first session management function network element may also request the first network element to provide it with the first identification information of the first network device. Then, after deleting the second identification information of the second network device in the target session context, the first identification information of the first network device may be saved, thereby obtaining an updated target session context.

[0212] In the above scheme, the first network element sends a first message to the first session management function network element to indicate that the terminal device has undergone a radio access network change, and the first session management function network element updates its stored target session context based on the first message, so that the updated target session context no longer contains the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device. By adopting this communication method during the RRC connection recovery process, the problem of invalid interaction between the session management function network element and the anchor network device caused by the replacement of the radio access network of the terminal device can be solved, and the waste of communication resources can be reduced.

[0213] In some possible implementations, the first session management function network element can obtain the first message in a subscription manner. In this case, Figure 4 As shown, the method also includes the steps of:

[0214] S411, when the first condition is met, the first session management function network element sends a second message to the first network element, where the second message is used to subscribe to the mobility event of the terminal device.

[0215] In some feasible solutions, the first session management function network element may send a second message to the first network element when determining that the first condition is satisfied. The second message may be used to request subscription to the mobility event of the terminal device, or the second message may be used to trigger the first network to feedback the first message. In an embodiment of the present application, the mobility event subscribed by the first session management function network element may include the replacement of the radio access network or the identification information of the radio access network. Optionally, the second message may be used to request subscription to the mobility event of the terminal device in a non-RRC connection recovery or non-switching scenario.

[0216] In an optional implementation, the first condition may include at least one of the following: a first session is established, the first session is in an activated state, and the terminal device enters an RRC inactivated state.

[0217] Exemplarily, the first session management function network element may send the second message to the first network element when the first session described above is established. Alternatively, the first session management function network element may send the second message to the first network element when it is determined that the first session is in an activated state. Alternatively, the first session management function network element sends the second message to the first network element when it is determined that the terminal device enters an RRC inactive state.

[0218] Optionally, when the first condition includes the terminal device entering the RRC inactive state, the first session management function network element may determine that the terminal device has entered the RRC inactive state based on an instruction from the second network device. Figure 4 As shown, before step S411, the method may also include the following steps: S410, the second network device sends an RRC inactive state indication of the terminal device to the first session management function network element. Specifically, the second network device may first determine whether the terminal device has entered the RRC inactive state. If it is determined to be yes, the RRC inactive state indication of the terminal device may be sent to the first session management function network element to inform the first session management function through the RRC inactive state indication of the terminal device that the terminal device has entered the RRC inactive state. It should be understood that the second network device may also notify the first session management function to determine that the terminal device has entered the RRC inactive state in other possible ways, and this application does not limit this.

[0219] Correspondingly, the first network element receives the second message from the first session management function network element. Then, the first network element may perform the relevant operations of step S415 when it is determined based on the second message that the first session management function network element has subscribed to the mobility event of the terminal device. It should be understood that when the second message is used to request subscription to the mobility event of the terminal device in a non-RRC connection recovery or non-switching scenario, the first network element does not need to perform step S415 even if a radio access network device replacement is sent in a connection recovery success process or a switching scenario.

[0220] In the above implementation, the first session management function network element obtains the first message by subscription, which can avoid frequent interactions between the first session management function network element and the first network element on the one hand, and ensure the timeliness of the first message by subscription on the other hand.

[0221] In some possible implementations, when the third condition described above includes receiving a fourth message from the first network device, the fourth message may be generated by the terminal device when determining that the RRC connection recovery triggered by the terminal device has failed, and sent to the first network element through the first network device. For example, Figure 4As shown, before step S415, the communication method may further include the following steps: S412, the terminal device generates and sends a fourth message to the first network element through the first network device, and the fourth message is used to update the location information of the terminal device. Specifically, when the terminal device determines that the RRC connection recovery fails, it may generate and send a fourth message to the first network device. For example, in the case of RRC connection recovery failure, the access layer of the terminal device will send an RRC connection recovery failure indication to the non-access layer, and then the non-access layer will trigger the terminal device to generate and send a fourth message to the first network device. Then, the first network device may forward the fourth message to the first network element.

[0222] Correspondingly, the first network element receives the fourth message and determines, based on the fourth message, that the terminal device requires updating the location information of the terminal device. Optionally, in the implementation method 1 or implementation method 2 of the first network element described above, the first access and mobility management function network element receives the fourth message and determines that the terminal device requires updating the location information of the terminal device.

[0223] Optional, such as Figure 4 As shown, after step S412, the method may further include the following steps:

[0224] S413: The first network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0225] Exemplarily, after receiving the fourth message and determining that the fourth message is used to update the location information of the terminal device, the first network element may generate and send an access network release message (AN Release message) to the second network device. It should be understood that for the implementation method 1 and implementation method 2 of the first network element described above, the first access and mobility management function network element generates and sends the access network release message.

[0226] Optionally, the access network release message may include the fifth identification information of the terminal device.

[0227] S414: The second network device deletes the terminal device context of the terminal device.

[0228] Exemplarily, after receiving the access network release message from the first network element, the second network device may delete the terminal device context of the terminal device.

[0229] In some possible implementations, such as Figure 4 As shown, after step S416, the method may further include the following steps:

[0230] S417, the first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0231] Optionally, after updating the target session context, the first session management function network element sends a session context release message (Release Session context message) to the second network device. Here, the session context release message may include the third identification information of the first session. Correspondingly, the second network device may receive the context release message from the first session management function network element and delete the session context related to the first session stored therein.

[0232] In some possible implementations, such as Figure 4 As shown, after step S416, the method may further include the following steps:

[0233] S418, the first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0234] Optionally, after determining that the update of the target session context is completed, the first session management function network element may generate and send a session resource establishment message to the first network device. Exemplarily, the session resource establishment message may include the third identification information of the first session, the fifth identification information of the terminal device, and the target session context information (such as QoS parameter information).

[0235] S419, the first network device sends the access network tunnel information of the first network device to the first session management function network element. Correspondingly, the first session management function network element receives the access network tunnel information of the first network device.

[0236] Optionally, after determining that the session resource establishment message from the first session management function network element has been received, the first network device may obtain access network tunnel information of the first network device and send the access network tunnel information of the first network device to the first session management function network element. The access network tunnel information of the first network device may be used by the first network device to receive data.

[0237] In some possible implementations, such as Figure 4 As shown, after step S416, the method may further include the following steps:

[0238] S420: When the second condition is met, the first session management function network element sends a third message to the first network element, where the third message is used to cancel the subscription to the mobility event of the terminal device. Correspondingly, the first network element receives the third message.

[0239] Optionally, in the case where the first session management function network element has subscribed to the mobility event of the terminal device from the first network element, the first session management function network element may also cancel the subscription to the mobility event of the terminal device.

[0240] Specifically, the first session management network element may send a third message to the first network element when determining that the second condition is satisfied, so as to unsubscribe from the mobility event of the terminal device through the third message. Accordingly, upon receiving the third message, the first session management function network element may determine that the first session management function network element unsubscribes from the mobility event of the terminal device, and stop executing the operation of sending the first message to the first session management function network element.

[0241] The second condition includes at least one of the following: the first session is released, the first session is in a deactivated state, and the terminal device leaves the RRC inactive state. Here, the terminal device leaves the RRC inactive state, which can also be understood as the terminal device moving out of the RRC inactive state.

[0242] It should be noted that, when the first network element adopts the implementation method 1 described above, the first session management network element may send a third message to the first access and mobility management function network element when determining that the second condition is met. Accordingly, the first access and mobility management function network element may determine that the first session management function network element cancels the subscription of the mobility event of the terminal device based on the third message.

[0243] When the first network element adopts the second implementation mode described above, the first session management network element can send a third message to the unified database network element when determining that the second condition is met. Accordingly, the unified database network element can determine that the first session management function network element cancels the subscription of the mobility event of the terminal device based on the third message.

[0244] In the above implementation, if the second condition is met, the subscription to the mobility event of the terminal device is cancelled, which can avoid the situation where the first network element still provides the first message to the first session management function network element when there is no demand from the first session management function network element, thereby avoiding invalid interaction between the first session management function network element and the first network element.

[0245] It should also be noted that, when the second condition includes the terminal device leaving the RRC inactive state, the first session management function network element may determine that the terminal device has left the RRC inactive state based on an indication of the first network device or the second network device.

[0246] It should be understood that the above Figure 4The description of the execution sequence between the steps in is only exemplary. In actual implementation, the execution sequence between certain steps can be adjusted according to actual application requirements, and this application does not limit this. For example, step S417 can be executed before step S418 or after step S418. For another example, step S420 can be executed before step S419 or after step S419. Those skilled in the art should understand that the execution sequence between the steps can be adjusted according to actual requirements. Figure 4 Solutions obtained by adjusting the execution timing of each step of the communication method shown belong to the protection scope of this application.

[0247] For the convenience of Figure 4 The communication method shown in the figure is understood. The following will combine the specific scenario that the RRC connection recovery triggered by the terminal device fails and the terminal device undergoes a radio access network switch. Figure 4 The implementation procedures of the communication method shown are briefly described. Figure 5 , Figure 5 It is another flow chart of a communication method provided by the present application. It should be understood that Figure 5 The example in which the first network element adopts the implementation method one described above (i.e., the first network element includes a first access and mobility management function network element) is used to illustrate. These processes are also applicable to the scenario in which the first network element adopts the implementation method two described above. In order to avoid redundancy, they will not be repeated.

[0248] like Figure 5 As shown, the communication method may include the following steps:

[0249] S50, the terminal device, the second network device, the first access and mobility management function network element and the first session management function network element interact to complete the registration of the terminal device and the establishment of the first session.

[0250] The terminal device will register with the first access and mobility management function network element, and the first session will be managed by the first session management function network element.

[0251] It should be understood that, since the terminal device resides in the second network device at this time, what is stored in the target session context of the first session in the first session management function network element is the second identification information of the second network device.

[0252] S51, the terminal device enters the RRC inactive state and the radio access network is changed. Correspondingly, the first network device and the second network device learn that the terminal device enters the RRC inactive state.

[0253] S52, the second network device sends an RRC inactive status indication of the terminal device to the first session management function network element. Correspondingly, the first session management function network element receives the RRC inactive status indication of the terminal device.

[0254] S53, when the terminal device enters the RRC inactive state, the first session management function network element sends a second message to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the second message.

[0255] S54, when the RRC connection recovery fails, the terminal device sends a mobile registration update message to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the mobile registration update message.

[0256] S55, the first access and mobility management function network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0257] S56: The second network device deletes the terminal device context of the terminal device.

[0258] S57, when the first session management function network element initiates subscription and the third condition is met, the first access and mobility management function network element sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0259] S58: The first session management function network element updates the target session context according to the first message.

[0260] S59, the first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0261] S60: The first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0262] S61: The first network device sends access network tunnel information of the first network device to the first session management function network element. The first session management function network element receives the access network tunnel information of the first network device.

[0263] Here, the specific implementation process of step S52 to step S61 can refer to the corresponding process described in the previous step S410 to step S419, which will not be repeated here.

[0264] S62, when there is uplink data to be transmitted, the terminal device sends a service request to the first session management function network element through the first network device. Correspondingly, the first session management function network element receives the service request.

[0265] Specifically, when there is uplink data to be transmitted, the terminal device can generate and send a service request to the first session management function network element through the first network device to request the first session management function network element to activate the first session. Correspondingly, after receiving the service request, the first session management function network element can activate the first session.

[0266] S63: When the second condition is met, the first session management function network element sends a third message to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the third message.

[0267] Here, the specific implementation process of step S63 can refer to the corresponding process described in the previous step S420, which will not be repeated here.

[0268] To solve the above problem, the present application provides another communication method. In the communication method, the terminal device actively sends a seventh message to the first network device for requesting to update the first session of the terminal device, so as to trigger the first network device to send a first message to the first session management function network element for updating the first session. The first session management function network element can update the target session context of the first session based on the first message, and make the updated target session context no longer contain the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device of the terminal device.

[0269] See also Figure 6 , Figure 6 It is another flow chart of a communication method provided by the present application. It should be understood that Figure 6 The communication method shown is also applicable to the previous Figure 2 The communication system shown in FIG. Figure 6 As shown, the method comprises the following steps:

[0270] S613: The terminal device sends a seventh message to the first network device for requesting to update the first session of the terminal device. Correspondingly, the first network device receives the seventh message.

[0271] In some feasible implementations, the terminal device may generate and send a seventh message to the first network device. The seventh message may be used to request an update of the first session of the terminal device. The seventh message may include third identification information of the first session, and the first session may be managed by the first session management function network element. The first network device is the network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element.

[0272] Optionally, the seventh message may further include a session modification indication of the first session or a session modification message of the first session.

[0273] Optionally, the seventh message may specifically be an RRC message (RRCmessage) sent by the terminal device to the first network device. It should be understood that this is only an example, and in actual implementation, the seventh message may also be other possible implementation forms, and this application does not limit this.

[0274] Optionally, the terminal device may first determine whether the first session is in an activated state. If the terminal device determines that the first session is in an activated state, the seventh message may be generated and sent to the first network device. Correspondingly, if the terminal device determines that the first session is in an inactive state, the seventh message will not be sent to the first network device. It can also be understood that in the embodiment of the present application, the first session is in an activated state.

[0275] S614: The first network device sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0276] In some feasible implementations, after receiving the seventh message from the terminal device, the first network device may generate a first message for requesting to update the first session based on the seventh message, and send the first message to the first session management function network element. Correspondingly, the first session management function network element will receive the first message. The first message includes at least the first identification information of the first network device.

[0277] In an optional implementation, before sending the first message to the first session management function network element, the first network device needs to first obtain the fourth identification information of the first session management function network element. The process of the first network device obtaining the fourth identification information of the first session management function network element is described below.

[0278] Optionally, the seventh message may include the fourth identification information of the first session management function network element, and the first network device may obtain the fourth identification information of the first session management function network element through the seventh message. It should be understood that in this case, the terminal device will save the fourth identification information of the first session management function network element when establishing the first session.

[0279] Optionally, the first network device may query a unified database network element or a network function repository (network function repository function, NRF) network element to obtain the fourth identification information of the first session management function network element.

[0280] Exemplarily, the first network device may send a ninth message to a unified database network element or a network function library network element. The ninth message may include the third identification information of the first session, and the ninth message may be used to request the unified database network element or the network function library network element to provide the identification information of the session management function network element that manages the first session. After receiving the ninth message, the unified database network element or the network function library network element may query and obtain the second session management function network element that manages the first session, generate and send a tenth message to the first network device. The tenth message includes the fourth identification information for the first session management function network element. The first network device may receive the tenth message from the unified database network element or the network function library network element, and obtain the fourth identification information of the first session management function network element.

[0281] Optionally, the fourth identification information of the first session management function network element may also be actively provided by the first access and mobility management function network element.

[0282] Exemplarily, the first access and mobility management function network element may generate and send an eleventh message to the first network device. The eleventh message includes identification information of multiple sessions and identification information of multiple session management function network elements that manage the multiple sessions. It should be understood that the multiple sessions are all activated sessions and at least include the above-mentioned first session. The identification information of the multiple session management function network elements includes at least the fourth identification information of the first session management function network element. Further, the first network device may receive the eleventh message from the first access and mobility management function network element, and obtain the fourth identification information of the first session management function network element used to manage the first session according to the eleventh message.

[0283] It should be noted that the identification information of the above-mentioned multiple sessions and the identification information of multiple session management function network elements managing the multiple sessions can be included in a container, and the container can be provided by the unified database network element to the first access and mobility management function network element.

[0284] It should be understood that the first network device may also adopt other possible implementation methods to obtain the fourth identification information of the first session management function network element, and this application does not limit this.

[0285] In an optional implementation, the first message may also include fifth identification information of the terminal device and access network tunnel information of the first network device.

[0286] In an optional implementation manner, the first message may further include a session modification indication corresponding to the first session or a session modification message of the first session.

[0287] S615: The first session management function network element updates the target session context according to the first message, and the updated target session context does not include the second identification information of the second network device.

[0288] In some feasible implementations, after receiving the first message, the first session management function network element may update the target session context according to the first message so that the updated target session context does not include the second identification information of the second network device. Here, the target session context is the session context of the first session. The second network device is an anchor network device of the terminal device, and the second network device is directly connected to the first session management function network element. Before the terminal device changes its radio access network, the terminal device accesses the second network device.

[0289] In a possible implementation, after receiving the first message, the first session management function network element may replace the second identification information of the second network device in the target session context with the first identification information of the first network device, thereby obtaining an updated target session context.

[0290] Optionally, when the first message also includes access network tunnel information of the first network device, the first session management function network element may also send the access network tunnel information of the first network device to the user plane function network element, so that the user plane function network element replaces the access network tunnel information corresponding to the second network device it stores with the access network tunnel information corresponding to the first network device.

[0291] In the above scheme, the terminal device sends the seventh message for requesting to update the first session of the terminal device to the first network device, so as to trigger the first network device to send the first message for updating the first session to the first session management function network element. After receiving the first message, the first session management function network element can update the target session context of the first session according to the first message, and make the updated target session context no longer contain the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device of the terminal device. Using this method in the RRC connection recovery scenario can solve the problem of invalid interaction between the session management function network element and the anchor network device caused by the replacement of the wireless access network of the terminal device, and can reduce the waste of communication resources.

[0292] In some possible implementations, the terminal device may execute the above step S613 when the RRC connection recovery triggered by it fails and the radio access network is changed.

[0293] In this case, if Figure 6 As shown, the method may also include the following steps:

[0294] S610: The terminal device sends a fourth message to the first access and mobility management function network element through the first network device. Correspondingly, the first access and mobility management function network element receives the fourth message.

[0295] In some feasible implementations, if the terminal device determines that the RRC connection recovery triggered by it fails, a fourth message may be generated and sent to the first network device. The first network device may forward the fourth message to the first access and mobility management function network element. Here, the fourth message is used to update the location information of the terminal device.

[0296] Optionally, the fourth message may be a mobile registration update message of the terminal device. It should be understood that the fourth message may also be other messages that can be used to update the location information of the terminal device, and the present application does not limit the implementation of the fourth message.

[0297] Exemplarily, if the terminal device determines that the RRC connection recovery triggered by it has failed, it can generate a mobile registration update message and send the mobile registration update message to the first access and mobility management function network element through the first network device to request the first access and mobility management function network element to update the location information of the terminal device.

[0298] In some possible implementations, such as Figure 6 As shown, the method may also include the following steps:

[0299] S611, the first access and mobility management function network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0300] Exemplarily, after receiving the fourth message and determining that the fourth message is used to update the location information of the terminal device, the first access and mobility management function network element may generate and send an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0301] Optionally, the access network release message may include the fifth identification information of the terminal device.

[0302] S612: The second network device deletes the terminal device context of the terminal device.

[0303] Exemplarily, after receiving the access network release message from the first access and mobility management function network element, the second network device may delete the terminal device context of the terminal device.

[0304] In some possible implementations, such as Figure 6 As shown, after step S615, the method may further include the following steps:

[0305] S616: The first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0306] In some possible implementations, such as Figure 6 As shown, after step S615, the method may further include the following steps:

[0307] S617: The first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0308] S618: The first network device sends the access network tunnel information of the first network device to the first session management function network element. Correspondingly, the first session management function network element receives the access network tunnel information of the first network device.

[0309] Here, the specific implementation process of steps S616 to S618 can be found in the corresponding descriptions of steps S417 to S419 above, and will not be repeated here.

[0310] It should be understood that Figure 6 The description of the timing of step S616 and step S617 is only exemplary. In actual implementation, step S616 can be performed before step S617 or after step S617, and this application does not limit this.

[0311] In some possible implementations, the terminal device can also establish other sessions other than the first session with other session management function network elements other than the first session management function network element. Then, when the RRC connection recovery of the terminal device fails and the radio access network is replaced, the problem of invalid interaction between these other session management function network elements and the second network device also needs to be solved. Therefore, in the communication method provided in the present application, the terminal device can also actively trigger these other session management function network elements to update the session context to avoid invalid interaction with the second network device. The following takes the second session management function network element other than the first session management function network element as an example. The second session management function network element is used to manage the second session of the terminal device, and the second session is different from the first session described above. It should be understood that the second session management function network element is directly connected to the first network device, and the second session management function network element is also directly connected to the second network device.

[0312] See also Figure 7 , Figure 7 FIG. 1 is another flow chart of a communication method provided by the present application. Figure 7 As shown, the communication method may further include the steps of:

[0313] S619: The terminal device sends a twelfth message to the first network device for requesting to update the second session of the terminal device. Correspondingly, the first network device receives the twelfth message.

[0314] In some feasible implementations, after sending the fourth message, the terminal device may further send a twelfth message to the first network device. The twelfth message is used to request to update the twelfth message of the second session of the terminal device. The twelfth message includes at least the sixth identification information of the second session.

[0315] Optionally, the twelfth message may also include a session modification indication of the second session or a session modification message of the second session.

[0316] Optionally, the twelfth message may also be an RRC message sent by the terminal device to the first network device. It should be understood that this is only an example, and in actual implementation, the twelfth message may also adopt other possible implementation forms, and this application does not limit this.

[0317] Optionally, the terminal device may also first determine whether the second session is in an activated state. If the terminal device determines that the second session is in an activated state, the twelfth message may be generated and sent to the first network device. Correspondingly, if the terminal device determines that the second session is in an inactive state, the twelfth message will not be sent to the first network device. It can also be understood that in the embodiment of the present application, the second session is also in an activated state.

[0318] S620: The first network device sends an eighth message to the second session management function network element. Correspondingly, the second session management function network element receives the eighth message.

[0319] In some feasible implementations, after receiving the twelfth message from the terminal device, the first network device may generate an eighth message for requesting to update the second session based on the twelfth message, and send the eighth message to the second session management function network element. Correspondingly, the second session management function network element will receive the eighth message. The eighth message includes at least the first identification information of the first network device.

[0320] Similarly, before sending the eighth message to the second session management function network element, the first network device also needs to first obtain the seventh identification information of the second session management function network element. The following will describe the process of the first network device obtaining the seventh identification information of the second session management function network element in conjunction with the process of the first network device obtaining the fourth identification information of the first session management function network element in step S614 above.

[0321] Optionally, the first network device may also query the unified database network element or the network function library network element to obtain the seventh identification information.

[0322] Exemplarily, the ninth message sent by the first network device to the unified database network element or the network function library network element may also include the sixth identification information of the second session. Further, the tenth message received by the first network device may also include the seventh identification information of the second session management function network element for managing the second session.

[0323] Optionally, the seventh identification information of the second session management function network element may also be actively provided by the first access and mobility management function network element.

[0324] Exemplarily, the eleventh message received by the first network device from the first access and mobility management function network element includes identification information of multiple sessions and identification information of multiple session management function network elements that manage the multiple sessions. The identification information of the multiple sessions includes the sixth identification information of the second session, and the identification information of the multiple session management function network elements also includes the seventh identification information of the second session management function network element. The first network device can also obtain the seventh identification information for the second session management function network element according to the eleventh message.

[0325] It should be understood that the first network device may also adopt other possible implementation methods to obtain the seventh identification information of the second session management function network element, and this application does not limit this.

[0326] In an optional implementation, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Further, the eighth message may also include a session modification indication corresponding to the second session or a session modification message corresponding to the second session.

[0327] In some feasible implementations, the terminal device may not execute the above step S619, but instead request to update the second session of the terminal device through the seventh message.

[0328] Exemplarily, the seventh message may further include the sixth identification information of the second session, and is also used to request to update the second session. Here, requesting to update two different sessions through the same message can save communication resources.

[0329] Optionally, in this case, the seventh message may further include a session modification indication of the second session or a session modification message of the second session.

[0330] Optionally, in this case, the seventh message may also include the seventh identification information of the second session management function network element. It should be understood that the seventh identification information may be saved by the terminal device when establishing the second session. In this case, before sending the eighth message to the second session management function network element, the first network device may obtain the seventh identification information of the second session management function network element according to the seventh message.

[0331] S621: The second session management function network element updates the session context of the second session according to the eighth message, and the updated session context of the second session does not include the second identification information of the second network device.

[0332] In some feasible implementations, after receiving the eighth message, the second session management function network element may update the session context of the second session according to the eighth message, so that the updated session context of the second session does not include the second identification information of the second network device.

[0333] In a possible implementation, after receiving the eighth message, the second session management function network element may replace the second identification information of the second network device in the session context of the second session with the first identification information of the first network device, thereby obtaining an updated session context of the second session.

[0334] What needs to be understood is that Figure 7 Although not directly shown Figure 6 , but the implementation of steps S611 to S618 is also applicable to Figure 7 To avoid redundancy, the scheme shown will not be described again here.

[0335] It should also be understood that the above description of the execution sequence between the steps is only exemplary. In actual implementation, the execution sequence between certain steps can be adjusted according to actual application requirements, and this application does not limit this. For example, step S611 can be executed before step S613 or after step S613. For another example, step S616 can be executed before step S617 or after step S617. Those skilled in the art should understand that the execution sequence between the steps can be adjusted based on actual requirements. Figure 6 or Figure 7 Solutions obtained by adjusting the execution timing of each step of the communication method shown belong to the protection scope of this application.

[0336] For the convenience of Figure 6 or Figure 7 The following will combine the scenario where the RRC connection recovery triggered by the terminal device fails and the terminal device undergoes a radio access network switch to understand the communication method shown in the figure. Figure 6 or Figure 7 The various steps of the communication method shown are exemplified. Figure 8 , Figure 8 It is another flow chart of a communication method provided by the present application. It should be understood that Figure 8 The example is shown by taking the coexistence of the first session management function network element and the second session management function network element.

[0337] like Figure 8 As shown, the communication method may include the following steps:

[0338] S80, the terminal device, the second network device, the first access and mobility management function network element, the first session management function network element and the second session management function network element interact to complete the registration of the terminal device and the establishment of the first session and the second session.

[0339] It should be understood that, since the terminal device resides on the second network device at this time, the second identification information of the second network device is stored in both the target session context of the first session and the session context of the second session.

[0340] S81, the terminal device enters the RRC inactive state and the radio access network is changed. Correspondingly, the first network device and the second network device learn that the terminal device enters the RRC inactive state.

[0341] S82, when the RRC connection recovery fails, the terminal device sends a mobile registration update message to the first access and session management function network element through the first network device. Correspondingly, the first access and session management function network element receives the mobile registration update message.

[0342] S83, the first access and mobility management function network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0343] S84: The second network device deletes the terminal device context of the terminal device.

[0344] S85: The terminal device sends a seventh message to the first network device for requesting to update the first session and the second session of the terminal device. Correspondingly, the first network device receives the seventh message.

[0345] S86: The first network device sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0346] S87: The first session management function network element updates the target session context according to the first message.

[0347] Here, the specific implementation process of steps S82 to S87 can refer to the corresponding description in steps S610 to S615 above, and will not be repeated here.

[0348] S88, the first network device sends an eighth message to the second session management function network element. Correspondingly, the second session management function network element receives the eighth message.

[0349] S89: The second session management function network element updates the session context of the second session according to the eighth message.

[0350] Here, for the specific implementation process of steps S88 to S89, please refer to the corresponding description in steps S620 to S621 above, which will not be repeated here.

[0351] S90, the first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0352] S91, the first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0353] S92: The first network device sends access network tunnel information of the first network device to the first session management function network element. The first session management function network element receives the access network tunnel information of the first network device.

[0354] Here, the specific implementation process of steps S90 to S92 can refer to the corresponding process described in steps S616 to S618 above, and will not be repeated here.

[0355] S93, when there is uplink data to be transmitted, the terminal device sends a service request to the first session management function network element through the first network device. Correspondingly, the first session management function network element receives the service request.

[0356] Specifically, when there is uplink data corresponding to the first session to be transmitted, the terminal device can generate and send a service request to the first session management function network element through the first network device to request the first session management function network element to activate the first session. Correspondingly, after receiving the service request, the first session management function network element can activate the first session.

[0357] It should be understood that after executing step S89, the second session management function network element may also perform operations similar to steps S90 to S93, which will not be repeated here to avoid redundancy.

[0358] To solve the above problem, the present application provides another communication method. In the communication method, the first network device will actively send a first message to the first session management function network element according to the context of the terminal device to request the first session management function network element to update the first session. The first session management network element will update the target session context of the first session based on the first message, and make the updated target session context no longer contain the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device of the terminal device.

[0359] See also Fig. 9 , Fig. 9 It is another flow chart of a communication method provided by the present application. It should be understood that Fig. 9 The communication method shown is also applicable to the previous Figure 2 The communication information shown. Fig. 9 As shown, the method comprises the following steps:

[0360] S910, the first network device obtains a terminal device context of a terminal device.

[0361] In some possible implementations, the first network device may obtain the terminal device context of the terminal device. Here, the terminal device context of the terminal device includes at least the third identification information of the first session of the terminal device and the fourth identification information of the first session management function network element. The first session management function network element is used to manage the first session. The first network device is the network device currently accessed by the terminal device. The first network device is directly connected to the first session management function network element.

[0362] Optionally, the terminal device context of the terminal device may further include fifth identification information of the terminal device and session state information of the first session.

[0363] Optionally, the terminal device context of the terminal device may also include identification information of at least one other session except the first session, identification information of at least one session management function network element except the first session management function network element, and session state information of each session in the at least one session. Here, the at least one session management function network element is used to manage the at least one session.

[0364] S911, the first network device sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0365] In some feasible implementations, after acquiring the terminal device context of the terminal device, the first network device may generate and send a first message to the first session management function network element based on the terminal device context. The first message is used to request to update the target session context of the first session and the first message includes at least the first identification information of the first network device. Accordingly, the first session management function network element receives the first message.

[0366] Exemplarily, after acquiring the terminal device context of the terminal device, the first network device may determine whether the first session is in an active state according to the terminal device context of the terminal device. If it is determined that the first session is in an active state, and it is determined that the terminal device has changed its radio access network, the first network device may determine the first session management function network element that manages the first session according to the terminal device context of the terminal device, and send a first message to the first session management function network element.

[0367] In an optional implementation, the first message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Further, the first message may also include a session modification indication corresponding to the first session or a session modification message corresponding to the first session.

[0368] S912: The first session management function network element updates the target session context according to the first message, and the updated target session context does not include the second identification information of the second network device.

[0369] In some feasible implementations, after receiving the first message, the first session management function network element may update the target session context according to the first message so that the updated target session context does not include the second identification information of the second network device. Here, the target session context is the session context of the first session. The second network device is an anchor network device of the terminal device. The second network device is directly connected to the first session management function network element. Before the terminal device changes its radio access network, the terminal device accesses the second network device.

[0370] Here, the specific implementation process of step S912 can be found in the corresponding description of step S615 above, and will not be repeated here.

[0371] In the above scheme, the first network device sends a first message to the first session management function network element according to the context of the terminal device to request the first session management function network element to update the first session. The first session management network element updates the target session context of the first session based on the first message, and makes the updated target session context no longer contain the identification information of the anchor network device of the terminal device. In this way, the first session management function network element will no longer interact with the anchor network device of the terminal device. By using this method during the RRC connection recovery process, the problem of invalid interaction between the session management function network element and the anchor network device caused by the replacement of the wireless access network of the terminal device can be solved, and the waste of communication resources can be reduced.

[0372] In some possible implementations, the first network device may obtain the terminal device context of the terminal device in a variety of ways. For example, the first network device obtains the terminal device context of the terminal device from the second network device or the first network element. The specific implementation of step S910 will be described below in conjunction with the two scenarios of RRC connection recovery failure and RRC connection recovery success.

[0373] Scenarios where RRC connection recovery fails:

[0374] Optional, such as Fig. 9 As shown, in the scenario where the RRC connection recovery fails, the communication method may further include the following steps:

[0375] S9101, the terminal device sends a target RRC message to the first network device. Correspondingly, the first network device receives the target RRC message.

[0376] In some feasible implementations, when determining that the RRC connection recovery has failed, the terminal device may generate and send a target RRC message to the first network device. The target RRC message may be used to indicate that the RRC connection recovery of the terminal device has failed, and the target RRC message may include an RRC connection recovery failure indication of the terminal device. Accordingly, the first network device may receive the target RRC message and determine the RRC connection recovery failure triggered by the terminal device according to the RRC connection recovery failure indication of the terminal device.

[0377] Optionally, the target RRC message may also include a mobile registration update message of the terminal device.

[0378] S9102: The first network device sends a fifth message to the first network element. Correspondingly, the first network element receives the fifth message.

[0379] In some feasible implementations, after the first network device determines that the RRC connection recovery triggered by the terminal device fails, it can generate and send a fifth message to the first network element. The fifth message can be used to request a terminal device context of the terminal device. The first network element can be used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device. Accordingly, the first network element can receive the fifth message and determine that the first network device requests the terminal device context of the terminal device.

[0380] Optionally, the fifth message may include fifth identification information of the terminal device.

[0381] Optionally, the fifth message may be a mobile registration update message of the terminal device.

[0382] Optionally, the first network element may be a first access and mobility management function network element or a unified database network element.

[0383] In some feasible implementations, step S9101 may not be performed. In this case, the first network device may send the fifth message to the first network element when establishing an RRC connection with the terminal device. That is, the first network device does not need to know whether the RRC connection recovery of the terminal device fails. As long as the RRC connection established with the terminal device is established, the first network device actively requests the terminal device context of the terminal device from the first network element.

[0384] S9103: The first network element sends a sixth message to the first network device. Correspondingly, the first network device receives the sixth message.

[0385] In some feasible implementations, after receiving the fifth message from the first network device, the first network element may generate a sixth message based on the terminal device context stored therein, and send the sixth message to the first network device, wherein the sixth message includes the terminal device context of the terminal device.

[0386] In the above implementation, the first network device will actively request the terminal device context of the terminal device from the first network element, which can ensure the timeliness and reliability of obtaining the terminal device context.

[0387] Optionally, when the first network element is a first access and mobility management function network element, the first network element may also actively send the sixth message to the first network device. Exemplarily, it is not necessary to determine whether the fifth message is received. When the first network element determines that the mobile registration update message of the terminal device is received, the sixth message may be sent to the first network device.

[0388] In some possible implementations, such as Fig. 9 As shown, the method may also include the following steps:

[0389] S9100: The second network device sends a terminal device context of the terminal device to the first network element. Correspondingly, the first network element receives the terminal device context of the terminal device.

[0390] In some feasible implementations, the second network device may actively send the terminal device context of the terminal device to the first network element. Optionally, the second network device may send the terminal device context of the terminal device to the first network element when determining that the RRC connection recovery of the terminal device fails. Accordingly, the first network element receives and saves the terminal device context of the terminal device.

[0391] Scenarios where the RRC connection is successfully restored:

[0392] Optional, such as Fig. 9 As shown, in the scenario where the RRC connection is successfully restored, the communication method may further include the following steps:

[0393] S9104, the terminal device sends an RRC connection recovery request to the first network device. The first network device receives the RRC connection recovery request.

[0394] In some feasible implementations, the terminal device sends an RRC connection recovery request to the first network device. The first network device may receive the RRC connection recovery request and establish a communication connection with the second network device.

[0395] S9105: The first network device sends a context retrieval request to the second network device. Correspondingly, the second network device receives the context retrieval request.

[0396] In some feasible implementations, after establishing a communication connection with the second network device, the first network device may send a context retrieval request to the second network device. Accordingly, the second network device receives the context retrieval request and determines that the first network device needs it to provide the terminal device context of the terminal device.

[0397] Optionally, the context retrieval request may include fifth identification information of the terminal device.

[0398] S9106: The second network device sends a context retrieval response to the first network device. Correspondingly, the first network device receives the context retrieval response.

[0399] In some feasible implementations, after receiving the context retrieval request sent by the first network device, the second network device may generate a context retrieval response based on the terminal device context of the terminal device, and send the context retrieval response to the first network device. The context retrieval response includes the terminal device context of the terminal device.

[0400] Correspondingly, the first network device may receive the context retrieval response and extract the terminal device context of the terminal device.

[0401] In some possible implementations, such as Fig. 9 As shown, the method may also include the following steps:

[0402] S913: The first network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0403] S914: The second network device deletes the terminal device context of the terminal device.

[0404] Here, the specific implementation process of step S913 to step S914 can refer to the corresponding description of step S611 to step S612, which will not be repeated here.

[0405] In some possible implementations, such as Fig. 9As shown, after step S912, the method may further include the following steps:

[0406] S915: The first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0407] In some possible implementations, such as Fig. 9 As shown, after step S915, the method may further include the following steps:

[0408] S916: The first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0409] S917: The first network device sends the access network tunnel information of the first network device to the first session management function network element. Correspondingly, the first session management function network element receives the access network tunnel information of the first network device.

[0410] Here, the specific implementation process of steps S915 to S917 can refer to the corresponding descriptions in the previous steps S616 to S618, which will not be repeated here.

[0411] In some possible implementations, the terminal device can also establish other sessions other than the first session with other session management function network elements other than the first session management function network element. Then, when the RRC connection recovery of the terminal device fails and the radio access network is replaced, the problem of invalid interaction between these other session management function network elements and the second network device also needs to be solved. Therefore, in the communication method provided in the present application, the terminal device can also actively trigger these other session management function network elements to update the session context to avoid invalid interaction with the second network device. The following takes the second session management function network element other than the first session management function network element as an example. The second session management function network element is used to manage the second session of the terminal device, and the second session is different from the first session described above. It should be understood that the second session management function network element is directly connected to the first network device, and the second session management function network element is also directly connected to the second network device.

[0412] See also Fig.10 , Fig.10 FIG. 1 is another flow chart of a communication method provided by the present application. Fig.10 As shown, the communication method may further include the steps of:

[0413] S918: The first network device sends an eighth message to the second session management function network element. Correspondingly, the second session management function network element receives the eighth message.

[0414] In some feasible implementations, after the first network device obtains the terminal context of the terminal device, it can determine that the second session is also in an activated state based on the terminal context of the terminal device. Further, the first network device can query the second session management function network element that manages the second session based on the terminal context of the terminal device. Then, the first network device generates an eighth message for requesting to update the second session, and sends the eighth message to the second session management function network element. Correspondingly, the second session management function network element receives the eighth message. Among them, the eighth message includes at least the first identification information of the first network device.

[0415] Optionally, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Further, the eighth message may also include a session modification indication corresponding to the second session or a session modification message corresponding to the second session.

[0416] S919: The second session management function network element updates the session context of the second session according to the eighth message, and the updated session context of the second session does not include the second identification information of the second network device.

[0417] The specific implementation process can be found in the description of step S621 above, and will not be repeated here.

[0418] What needs to be understood is that Fig.10 Although not directly shown Fig. 9 , but the implementation of steps S913 to S917 is also applicable to Fig.10 To avoid redundancy, the scheme shown will not be described again here.

[0419] It should also be understood that the above description of the execution sequence between the steps is only exemplary. In actual implementation, the execution sequence between certain steps can be adjusted according to actual application requirements, and this application does not limit this. For example, step S913 can be executed before step S912 or after step S912. For another example, step S915 can be executed before step S916 or after step S916. Those skilled in the art should understand that the execution sequence between the steps can be adjusted according to actual requirements. Fig. 9 or Fig.10 Solutions obtained by adjusting the execution timing of each step of the communication method shown belong to the protection scope of this application.

[0420] For the convenience of Fig. 9 or Fig.10 The following will combine the scenario where the RRC connection recovery triggered by the terminal device fails and the terminal device switches to a wireless access network to understand the communication method shown in the figure. Fig. 9 or Fig.10 The various steps of the communication method shown are exemplified. Fig.11 , Fig.11 It is another flow chart of a communication method provided by the present application. It should be understood that Fig.11 The example in which the first session management function network element and the second session management function network element coexist is taken as an example, and the first network element is assumed to be a first access and mobility management function network element.

[0421] like Fig.11 As shown, the communication method may include the following steps:

[0422] S111, the terminal device, the second network device, the first access and mobility management function network element, the first session management function network element and the second session management function network element interact to complete the registration of the terminal device and the establishment of the first session and the second session.

[0423] It should be understood that, since the terminal device resides on the second network device at this time, the second identification information of the second network device is stored in both the target session context of the first session and the session context of the second session.

[0424] S112, the terminal device enters the RRC inactive state and the radio access network is changed. Correspondingly, the first network device and the second network device learn that the terminal device enters the RRC inactive state.

[0425] S113, when the RRC connection recovery fails, the second network device sends the terminal device context of the terminal device to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives and saves the terminal device context of the terminal device.

[0426] S114, when the RRC connection recovery fails, the terminal device sends an RRC connection recovery failure indication to the first network device. Correspondingly, the first network device receives the RRC connection recovery failure indication and determines that the RRC connection recovery of the terminal device fails.

[0427] S115: The first network device sends a fifth message to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the fifth message.

[0428] S116: The first access and mobility management function network element sends a sixth message to the first network device. Correspondingly, the first network device receives the sixth message.

[0429] Here, the specific implementation process of steps S113 to S116 can refer to the corresponding descriptions in the previous steps S9100 to S9103, which will not be repeated here.

[0430] S117: The first network device sends a first message to the first session management function network element. Correspondingly, the first session management function network element receives the first message.

[0431] S118: The first session management function network element updates the target session context according to the first message, and the updated target session context does not include the second identification information of the second network device.

[0432] Here, the specific implementation process of step S117 to step S118 can refer to the corresponding description of step S911 to step S912 above, and will not be repeated here.

[0433] S119, the first network device sends an eighth message to the second session management function network element. Correspondingly, the second session management function network element receives the eighth message.

[0434] S120: The second session management function network element updates the session context of the second session according to the eighth message, and the updated session context of the second session does not include the second identification information of the second network device.

[0435] Here, the specific implementation process of step S119 to step S120 can refer to the corresponding description in the previous step S918 to step S919, which will not be repeated here.

[0436] S121, the first access and mobility management function network element sends an access network release message to the second network device. Correspondingly, the second network device receives the access network release message.

[0437] S122: The second network device deletes the terminal device context of the terminal device.

[0438] S123, the first session management function network element sends a session context release message to the second network device. Correspondingly, the second network device receives the session context release message.

[0439] S124, the first session management function network element sends a session resource establishment message to the first network device. Correspondingly, the first network device receives the session resource establishment message.

[0440] S125, the first network device sends the access network tunnel information of the first network device to the first session management function network element. The first session management function network element receives the access network tunnel information of the first network device.

[0441] Here, the specific implementation process of steps S121 to S125 can refer to the corresponding descriptions in the previous steps S913 to S917, which will not be repeated here.

[0442] S126, when there is uplink data to be transmitted, the terminal device sends a service request to the first session management function network element through the first network device. Correspondingly, the first session management function network element receives the service request.

[0443] Specifically, when there is uplink data corresponding to the first session to be transmitted, the terminal device can generate and send a service request to the first session management function network element through the first network device to request the first session management function network element to activate the first session. Correspondingly, after receiving the service request, the first session management function network element can activate the first session.

[0444] It should be understood that after executing step S120, the second session management function may also perform operations similar to the above steps S121 to S126, which will not be repeated here to avoid redundancy.

[0445] It should be additionally noted that, in the embodiment of the present application, both the first session and the second session may be protocol data unit (PDU) sessions in an activated state.

[0446] It should also be noted that, in the embodiment of the present application, the unified database network element can also be replaced by an unstructured data storage function (UDSF) network element. That is to say, in the embodiment of the present application, each step performed by the unified database network element can also be performed by the unstructured data storage function network element. The process described in the above step S415, in which the unified database network element determines that it has received a mobile information notification message from the first access and mobility management function network element, and sends a first message to the first session management function network element, can be performed by the unstructured data storage function network element.

[0447] It should also be noted that, in the embodiment of the present application, the identification information of a session can be the unique identification of the session (i.e., session ID), or the unique identification of the session context corresponding to the session (i.e., sessioncontext ID), and the present application does not impose any specific restrictions on this. As described above, the third identification information of the first session can be the session ID of the first session, or the sessioncontext ID corresponding to the target session context of the first session.

[0448] After the terminal device triggers the RRC connection recovery, the first network device to which the terminal device is currently connected needs to obtain the terminal device context of the terminal device to ensure that the RRC connection recovery is successful. Normally, the first network device needs to request the anchor network device of the terminal device to provide the terminal device context. However, there may be a situation where the first network device and the anchor network device of the terminal device cannot communicate, such as the first network device and the anchor network device interface of the terminal device are not connected, which can easily lead to the failure of the RRC connection recovery triggered by the terminal device.

[0449] Therefore, the technical problem that the present application needs to solve is: how to improve the success rate of RRC connection recovery of terminal devices.

[0450] To solve this problem, the present application provides another communication method. In this communication method, the terminal device will actively provide the tracking area (TA) information of the anchor network device to the first network device it is currently connected to. Therefore, even if the first network device wirelessly directly obtains the terminal device context of the terminal device from the anchor network device, the first network device can still obtain the terminal context of the terminal device through the tracking area information. In this way, the failure of RRC connection recovery caused by the inability of the first network device to obtain the terminal device context can be avoided, thereby improving the success rate of RRC connection recovery of the terminal device.

[0451] See also Fig.12 , Fig.12 It is another flow chart of a communication method provided by the present application. It should be understood that Fig.12 The communication method shown is applicable to the previous Figure 3 The communication system shown in FIG. Fig.12 As shown, the method comprises the following steps:

[0452] S1201, the terminal device obtains target information, where the target information includes tracking area information of the second network device.

[0453] In some feasible implementations, the terminal device may obtain target information when determining that RRC connection recovery is required. The target information may include tracking area information of the second network device. It should be understood that in the embodiment of the present application, the tracking area information of the second network device can be understood as the TA information corresponding to the cell covered by the second network device. In addition, in this embodiment, the terminal device has a radio access network change, and it is currently connected to the first network device, and the second network device is its anchor network device.

[0454] In a possible implementation, the target information may be an inactivated radio network temporary identifier (ie, I-RNTI) of the terminal device.

[0455] Furthermore, the target information may be provided or allocated by the second network device to the terminal device, that is, the second network device sends the target information to the terminal device.

[0456] Furthermore, in the case where the target information is a temporary identification of a non-activated wireless network of a terminal device, the target information may also include fifth identification information of the terminal device and second identification information of the second network device.

[0457] Furthermore, the target information may also include radio access technology (RAT) information and public land mobile network (PLMN) information.

[0458] S1202: The terminal device sends target information to the first network device. Correspondingly, the first network device receives the target information.

[0459] In some feasible implementations, after acquiring the target information, the terminal device may send the target information to the first network device. Correspondingly, the first network device receives the target information.

[0460] In an optional implementation, the terminal device may send the target information to the first network device when triggering RRC connection state recovery.

[0461] Further, in this case, the terminal device may send an RRC connection resumption request (RRC resume request) including the target information to the first network device. The first network device receives the RRC connection resumption request and obtains the target information.

[0462] S1203: The first network device sends target information to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the target information.

[0463] In some feasible implementations, after acquiring the target information, the first network device may send the target information to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the target information. Here, the first access and mobility management function network element is responsible for access and mobility management of the terminal device.

[0464] In an optional implementation, the first network device may send target information to the first access and mobility management function network element when it is determined that it cannot directly obtain the terminal device context of the terminal device from the second network device.

[0465] For example, when the first network device determines that its interface with the second network device is blocked, and it determines that it cannot directly obtain the terminal device context of the terminal device from the second network device, it can then send target information to the first access and mobility management function network element.

[0466] For another example, if the first network device sends a context retrieval request to the second network device but the second network device does not respond, it can be determined that it cannot directly obtain the terminal device context of the terminal device from the second network device, and then the target information can be sent to the first access and mobility management function network element.

[0467] Here, the target information is sent only when it cannot be directly obtained from the second network device, which can avoid repeated acquisition of the terminal device context and save communication resources.

[0468] S1204: The first access and mobility management function network element obtains the terminal device context of the terminal device according to the tracking area information of the second network device.

[0469] In some feasible implementations, after acquiring the target information, the first access and mobility management function network element may extract the tracking area information of the second network device contained in the target information, and acquire the terminal device context of the terminal device based on the tracking area information.

[0470] S1205: The first access and mobility management function network element sends the terminal device context of the terminal device to the first network device. Correspondingly, the first network device receives the terminal device context of the terminal device.

[0471] In some feasible implementations, after acquiring the context of the terminal device, the first access and mobility management function network element may send the terminal device context of the terminal device to the first network device. Correspondingly, the first network device receives the terminal device context.

[0472] Optionally, the terminal device context of the terminal device may include the fifth identification information of the terminal device, identification information of at least one session of the terminal device, identification information of at least one session management function network element, and session state information of each session in at least one session of the terminal device. Here, the at least one session management function network element is used to manage at least one session of the terminal device.

[0473] Optionally, the terminal device context of the terminal device may also include authorization information of the terminal device, quality of service QoS flow information of the terminal device, etc.

[0474] In the above solution, the terminal device will actively provide the tracking area information of the anchor network device to the first network device it is currently connected to. Therefore, even if the first network device wirelessly obtains the terminal device context of the terminal device directly from the anchor network device, the first network device can still obtain the terminal context of the terminal device through the tracking area information. In this way, the failure of RRC connection recovery caused by the inability of the first network device to obtain the terminal device context can be avoided, the success rate of RRC connection recovery of the terminal device can be improved, and the impact of the failure of RRC connection recovery can be reduced.

[0475] In some possible implementations, the first access and mobility management function network element may adopt multiple methods to obtain the terminal device context of the terminal device according to the tracking area information of the second network device, which will be explained below respectively.

[0476] Optional, such as Fig.12 As shown, the first method for obtaining the terminal device context may include the following steps:

[0477] S12041: The first access and mobility management function network element determines that a first tracking area information range of the first access and mobility management function network element includes tracking area information of a second network device.

[0478] In some feasible implementations, the first access and mobility management function network element may obtain the first tracking area information range it manages. Then, the first access and mobility management function network element may determine whether the first tracking area information range includes the tracking area information of the second network device. If it is determined to include, the following step S12042 may be executed.

[0479] It should be understood that in the embodiment of the present application, the first tracking area information range includes the tracking area information of the second network device, which can also be understood as the first access and mobility management function network element managing the second network device.

[0480] S12042: The first access and mobility management function network element sends a context retrieval request to the second network device. Correspondingly, the first network device receives the context retrieval request.

[0481] In some feasible implementations, the first access and mobility management function network element may send a context retrieval request of the terminal device to the second network device. The context retrieval request may include the above-mentioned target information. The context retrieval request may be used to request the second network device to provide the terminal device context of the terminal device.

[0482] Correspondingly, the second network device receives the context retrieval request and obtains the target information.

[0483] S12043: The second network device sends a context retrieval response to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the context retrieval response.

[0484] In some feasible implementations, after acquiring the target information, the second network device may query the terminal device context of the terminal device according to the fifth identification information of the terminal device included in the target information. Then, the second network device may generate a context retrieval response including the terminal device context of the terminal device, and send the context retrieval response to the first access and mobility management function network element.

[0485] Correspondingly, the first access and mobility management function network element receives the context retrieval response and obtains the terminal device context of the terminal device.

[0486] Optional, such as Fig.12 As shown, the second method for obtaining the terminal device context may include the following steps:

[0487] S12044: The first access and mobility management function network element determines that the first tracking area information range of the first access and mobility management function network element does not include the tracking area information of the second network device.

[0488] In some feasible implementations, after the first access and mobility management function network element obtains the first tracking area information range it manages, if it determines that the first tracking area information range does not include the tracking area information of the second network device, it can execute the following step S12045.

[0489] It should be understood that in the embodiment of the present application, the first tracking area information range does not include the tracking area information of the second network device, which can also be understood as the first access and mobility management function network element does not manage the second network device.

[0490] S12045: The first access and mobility management function network element sends target information to the second access and mobility management function network element. Correspondingly, the second access and mobility management function network element receives the target information.

[0491] In some feasible implementations, after determining that the first tracking area information range does not include the tracking area information of the second network device, the first access and mobility management function network element may send target information to the second access and mobility management function network element. Correspondingly, the second access and mobility management function network element receives the target information.

[0492] In a feasible implementation, the second access and mobility management function network element can be discovered by the first access and mobility management function network element, and the second tracking area information range corresponding to the second access and mobility management function network element includes the tracking area information of the second network device. In other words, the second network device is managed by the second access and mobility management function network element.

[0493] It should be understood that the first access and mobility management function network element may discover the second access and mobility management function network element in various possible ways, and the present application does not limit this.

[0494] S12046: The second access and mobility management function network element determines that a second tracking area information range of the second access and mobility management function network element includes the tracking area information of the second network device.

[0495] In some feasible implementations, the second access and mobility management function network element may obtain the second tracking area information range it manages and determine whether the second tracking area information range includes the tracking area information of the second network device. If the determination is yes, the following step S12047 may be executed.

[0496] S12047: The second access and mobility management function network element sends a context retrieval request to the second network device. Correspondingly, the second network device receives the context retrieval request.

[0497] In some feasible implementations, the second access and mobility management function network element may send a context retrieval request of the terminal device to the second network device, wherein the context retrieval request includes the above-mentioned target information, and is used to request the second network device to provide the terminal device context of the terminal device.

[0498] Correspondingly, the second network device receives the context retrieval request and obtains the target information.

[0499] S12048: The second network device sends a context retrieval response to the second access and mobility management function network element. Correspondingly, the second access and mobility management function network element receives the context retrieval response.

[0500] In some feasible implementations, after acquiring the target information, the second network device may query the terminal device context of the terminal device according to the fifth identification information of the terminal device included in the target information. Then, the second network device may generate a context retrieval response including the terminal device context of the terminal device, and send the context retrieval response to the second access and mobility management function network element.

[0501] Correspondingly, the first access and mobility management function network element receives the context retrieval response and obtains the terminal device context of the terminal device.

[0502] S12049: The second access and mobility management function network element sends the terminal device context of the terminal device to the first access and mobility management function network element. Correspondingly, the first access and mobility management function network element receives the terminal device context of the terminal device.

[0503] In some possible implementations, such as Fig.12 As shown, the method may also include the steps of:

[0504] S1206: The first network device sends an RRC connection recovery indication to the terminal device. Correspondingly, the terminal device receives the RRC connection recovery indication.

[0505] In some feasible implementations, after acquiring the terminal device context of the terminal device, the first network device may send an RRC connection recovery indication to the terminal device to instruct the terminal device to complete the recovery of the RRC connection state. Correspondingly, the terminal device receives the RRC connection recovery indication and continues to complete the recovery of the RRC connection state.

[0506] S1207, the terminal device sends an RRC connection recovery completion indication to the first network device. Correspondingly, the first network device receives the RRC connection recovery completion indication.

[0507] In some feasible implementations, after completing the recovery of the RRC connection state, the terminal device may send an RRC connection recovery completion indication to the first network device. Accordingly, the first network device receives the RRC connection recovery completion indication and determines that the terminal device has completed the recovery of the RRC connection state based on the RRC connection recovery completion indication.

[0508] Above, combined Figures 1 to 12 The communication method provided by the embodiment of the present application is described in detail. Fig.13 and Fig.14 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the embodiment of the communication device corresponds to the description of the embodiment of the communication method, so the parts not described in detail can refer to the previous method embodiment.

[0509] It can be understood that in order to realize the functions in the above embodiments, Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The first network device in the method shown includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is executed in the form of hardware, software, or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0510] See also Fig.13 , Fig.13 Schematic diagram of a communication device provided by this application. Fig.13 As shown, the communication device 130 may include a processing unit 131 and a transceiver unit 132. The processing unit 131 and the transceiver unit 132 may be software, hardware, or a combination of software and hardware.

[0511] The transceiver unit 132 may include a sending unit and a receiving unit. The sending unit is used to implement a sending function, and the receiving unit is used to implement a receiving function. The transceiver unit 132 may implement a sending function and / or a receiving function. The transceiver unit may also be described as a communication unit.

[0512] Optionally, the transceiver unit 132 may be used to receive information sent by other devices, and may also be used to send information to other devices. The processing unit 131 may be used to perform internal processing of the device.

[0513] In one possible design, the communication device 130 may correspond to Figures 4 to 11 The method shown in the figure involves a first session management function network element, such as the communication device 130, which may be a first session management function network element or a chip in the first session management function network element. The communication device 130 may include a device for executing Figures 4 to 11 The unit of the operation performed by the first session management function network element in the method shown, and the units in the communication device 130 are respectively for implementing Figures 4 to 11 The operations in the method shown are performed by the first session management function network element.

[0514] Exemplarily, the transceiver unit 132 can be used to receive a first message. The first message can be used to indicate that a wireless access network has been changed for a terminal device and the first message includes at least one of the first identification information of the first network device and the wireless access network change indication of the terminal device. Alternatively, the first message can be used to request an update of a first session and the first message includes the first identification information of the first network device. Here, the first network device is a network device currently accessed by the terminal device, and the first network device is directly connected to a first session management function network element. The processing unit 131 is used to update the target session context according to the first message so that the updated target session context does not include the second identification information of the second network device. The target session context is the session context of the first session, and the second network device is the anchor network device of the terminal device.

[0515] Exemplarily, when the first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of first identification information of the first network device and an indication of wireless access network change of the terminal device, the processing unit 131 is used to delete the second identification information of the second network device included in the target session context according to the first message to obtain an updated target session context.

[0516] Exemplarily, the processing unit 131 may be configured to delete the second identification information of the second network device included in the target session context when the first message includes an indication of a change of the radio access network of the terminal device, so as to obtain an updated target session context.

[0517] Exemplarily, when the first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of the first identification information of the first network device and an indication of wireless access network change of the terminal device, the processing unit 131 is used to replace the second identification information of the second network device included in the target session context with the first identification information of the first network device according to the first message to obtain an updated target session context.

[0518] Exemplarily, when the first message includes the first identification information of the first network device, the processing unit 131 is used to replace the second identification information of the second network device included in the target session context with the first identification information of the first network device to obtain an updated target session context.

[0519] Exemplarily, when the first message is used to indicate that a wireless access network change occurs to a terminal device and the first message includes at least one of the first identification information and the wireless access network change indication, the first message may come from a first network element. The first network element is used to store a terminal device context of the terminal device or to be responsible for access management of the terminal device.

[0520] Exemplarily, the transceiver unit 132 may send a second message to the first network element when the first condition is satisfied. The second message may be used to subscribe to the mobility event of the terminal device. In other words, the second message may be used to trigger the first network element to send the first message to the first session management function network element.

[0521] Exemplarily, the above-mentioned first condition may include at least one of the following: the first session is established, the first session is in an activated state, and the terminal device enters an RRC inactivated state.

[0522] Exemplarily, when the first condition includes the terminal device entering the RRC inactive state, the transceiver unit 132 is used to receive the RRC inactive state indication of the terminal device. Here, the RRC inactive state indication of the terminal device is used to indicate that the terminal device is in the RRC inactive state. The processing unit 131 is used to determine that the terminal device is in the RRC inactive state based on the RRC inactive state indication, and then determine that the first condition is satisfied.

[0523] Exemplarily, the second message may include a radio access network change notification request corresponding to the terminal device. Further, the second message may also include fifth identification information of the terminal device.

[0524] Exemplarily, when the second condition is met, the transceiver unit 132 is used to send a third message to the first network element, wherein the third message is used to cancel the subscription to the mobility event of the terminal device.

[0525] Exemplarily, the second condition may include at least one of the following: the first session is released, the first session is in a deactivated state, and the terminal device leaves the RRC inactive state. Here, the terminal device leaves the RRC inactive state, which can also be understood as the terminal device moving out of the RRC inactive state.

[0526] Exemplarily, the first network element may include a first access and mobility management function network element or a unified database network element.

[0527] Exemplarily, when the first message is used to indicate that a wireless access network of a terminal device has been changed and the first message includes at least one of the first identification information of a first network device and an indication of a wireless access network change of the terminal device, the first message may also include fifth identification information of the terminal device.

[0528] Exemplarily, when the first message is used to request updating of the first session and the first message includes first identification information of the first network device, the first message may come from the first network device.

[0529] Exemplarily, when the first message is used to request an update of the first session and the first message includes first identification information of the first network device, the processing unit 131 is used to replace the second identification information of the second network device in the target session context with the first identification information of the first network device to obtain an updated target session context.

[0530] Exemplarily, the first message may also include access network tunnel information of the first network device. The transceiver unit 132 is used to send the access network tunnel information of the first network device to the user plane function network element, so that the user plane function network element replaces the access network tunnel information corresponding to the second network device stored by it with the access network tunnel information corresponding to the first network device.

[0531] Exemplarily, the transceiver unit 132 is configured to send a session context release message to the second network device to instruct the second network device to release the target session context stored therein. Optionally, the session context release message may include the third identification information of the first session.

[0532] Exemplarily, when the first message is used to request to update the first session and the first message includes the first identification information of the first network device, the first message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication of the first session or a session modification message corresponding to the first session.

[0533] In one possible design, the communication device 130 may correspond to Figure 4 to Figure 5 The first network element in the method shown, such as the communication device 130, can be the first network element, or a chip in the first network element. The communication device 130 can include a device for executing Figure 4 to Figure 5 The units of the operation performed by the first network element in the method shown in the figure are respectively for implementing Figure 4 to Figure 5 The operations performed by the first network element in the method are shown.

[0534] Exemplarily, the transceiver unit 132 is used to receive a second message from the first session management function network element. The second message is used to subscribe to the mobility event of the terminal device. The above-mentioned first network element is used to store the terminal device context of the terminal device or to be responsible for the access management of the terminal device. The first session management function network element is used to manage the first session of the above-mentioned terminal device. The transceiver unit 132 is also used to send a first message to the first session management function network element. The first message is used to indicate that the terminal device has a radio access network change and the first message includes at least one of the first identification information of the first network device and the radio access network change indication of the above-mentioned terminal device. The first network device is the network device currently accessed by the terminal device.

[0535] Exemplarily, the first message may be used by the first session management function network element to update the target session context of the first session so that the updated target session context does not include the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device.

[0536] Exemplarily, the second message may include a radio access network change notification request corresponding to the terminal device. Optionally, the second message may also include fifth identification information of the terminal device.

[0537] Exemplarily, the transceiver unit 132 may be configured to send a first message to the first session management function network element when the third condition is satisfied. The third condition includes at least one of the following: receiving a fourth message from the first network device and the fourth message is used to update the location information of the terminal device, determining that the terminal device has changed the radio access network in a non-RRC connection recovery situation, and determining that the terminal device has changed the radio access network in a non-switching scenario.

[0538] Exemplarily, the fourth message may be a mobile registration update message sent by the terminal device through the first network device.

[0539] Exemplarily, the first network element may include a first access and mobility management function network element.

[0540] Exemplarily, the first network element may include a unified database network element.

[0541] Exemplarily, in the case where the first network element includes a unified database network element, the first message is sent by the unified database network element.

[0542] In one possible design, the communication device 130 may correspond to Figures 9 to 11 The first network device in the method shown, such as the communication device 130, can be the first network device, or a chip in the first network device. The communication device 130 can include a device for executing Figures 9 to 11 The units of the operation performed by the first network device in the method shown in the figure are respectively for implementing Figures 9 to 11 The operations in the method shown are performed by the first network device.

[0543] Exemplarily, the processing unit 131 is used to obtain a terminal device context of the terminal device. The terminal device context of the terminal device includes third identification information of the first session and fourth identification information of a first session management function network element, and the first session management function network element is used to manage the first session. The transceiver unit 132 is used to send a first message to the first session management function network element. The first message is used to request an update of the first session, and the first message includes first identification information of a first network device. The first network device is a network device to which the terminal device is currently connected.

[0544] Exemplarily, the first message may be used by the first session management function network element to update the target session context of the first session so that the updated target session context does not include the second identification information of the second network device. Here, the second network device is an anchor network device of the terminal device.

[0545] Exemplarily, the transceiver unit 132 is used to send a fifth message to the first network element. The fifth message is used to request a terminal device context of the terminal device. The transceiver unit 132 is used to receive a sixth message from the first network element. The sixth message includes the terminal device context of the terminal device. The first network element is used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device.

[0546] Exemplarily, the fifth message may be a mobile registration update message of the terminal device.

[0547] Exemplarily, the sixth message may also include fifth identification information of the terminal device.

[0548] Exemplarily, the transceiver unit 132 may be used to send the fifth message to the first network element when the RRC connection recovery of the terminal device fails. Alternatively, the transceiver unit 132 may be used to send the fifth message to the first network element when an RRC connection is established between the first network device and the terminal device.

[0549] Exemplarily, the terminal device context of the terminal device may be provided by the second network device to the first network element. For example, the terminal device context of the terminal device may be sent by the second network device to the first network element when determining that the terminal device enters the RRC inactive state.

[0550] Exemplarily, the first network element may include a first access and mobility management function network element or a unified database network element.

[0551] Exemplarily, when the RRC connection of the terminal device is successfully restored, the transceiver unit 132 may be used to send a context retrieval request of the terminal device to the second network device. The second network device is an anchor network device of the terminal device. The transceiver unit 132 may be used to receive a context retrieval response from the second network device. The context retrieval response includes the terminal device context of the terminal device.

[0552] Exemplarily, the first message may further include fifth identification information of the terminal device and access network tunnel information of the first network device. Optionally, the first message may further include a session modification indication of the first session or a session modification message corresponding to the first session.

[0553] Exemplarily, the transceiver unit 132 is further configured to send an eighth message to the second session management function network element. The eighth message is used to request the second session management function network element to update the session context of the second session, and the updated session context of the second session does not include the second identification information of the second network device. The eighth message includes the sixth identification information of the second session.

[0554] In one possible design, the communication device 130 may correspond to Figures 6 to 8 The terminal device in the method shown, such as the communication device 130, can be a terminal device or a chip in the terminal device. The communication device 130 can include a device for executing Figures 6 to 8 The units of the operation performed by the terminal device in the method shown in the figure are respectively for implementing Figures 6 to 8 The operations performed by the terminal device in the method shown.

[0555] Exemplarily, in the case where the radio resource control RRC connection recovery fails, the transceiver unit 132 is used to send a fourth message to the first network device. The fourth message can be used to update the location information of the terminal device, and the first network device is the network device currently connected to the terminal device. The transceiver unit 132 is used to send a seventh message to the first network device. The seventh message can be used to request to update the first session of the terminal device, and the seventh message includes the third identification information of the first session, and the first session is managed by the first session management function network element.

[0556] Exemplarily, the seventh message may also include a session modification indication corresponding to the first session.

[0557] Exemplarily, the first message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication corresponding to the first session or a session modification message corresponding to the first session.

[0558] Exemplarily, the seventh message may also include the sixth identification information of the second session of the terminal device. It should be understood that the second session may be managed by a second session management function network element other than the first session management function network element. The optional seventh message may also include a session modification indication of the second session or a session modification message corresponding to the second session.

[0559] Exemplarily, the transceiver unit is further used to send a twelfth message to the first network device. The twelfth message is used to request to update the second session of the terminal device. The twelfth message includes the sixth identification information of the second session, and the second session is managed by the second session management function network element.

[0560] In one possible design, the communication device 130 may correspond to Figures 9 to 11 The first network device in the method shown, such as the communication device 130, can be the first network device, or a chip in the first network device. The communication device 130 can include a device for executing Figures 9 to 11 The units of the operation performed by the first network device in the method shown in the figure are respectively for implementing Figures 9 to 11 The operations in the method shown are performed by the first network device.

[0561] Exemplarily, the transceiver unit 132 is used to receive a fourth message sent by the terminal device when the RRC connection session fails. The fourth message can be used to update the location information of the terminal device, and the first network device is the network device currently connected to the terminal device. The transceiver unit 132 is used to receive a seventh message from the terminal device. The seventh message can be used to request an update of a first session of the terminal device, and the seventh message includes the third identification information of the first session, and the first session is managed by the first session management function network element. The first network device sends a first message to the first session management function network element, and the first message can be used to request an update of the first session.

[0562] Exemplarily, the seventh message may further include a session modification indication corresponding to the first session.

[0563] Exemplarily, the first message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Optionally, the first message may also include a session modification indication corresponding to the first session or a session modification message corresponding to the first session.

[0564] Exemplarily, the transceiver unit 132 may be used to send a ninth message to the unified database network element or the network function library network element. The ninth message may include the third identification information of the first session. The transceiver unit 132 may be used to receive a tenth message from the unified database network element or the network function library network element, wherein the tenth message includes the fourth identification information of the first session management function network element that manages the first session.

[0565] Exemplarily, the seventh message also includes fourth identification information of the first session management function network element.

[0566] Exemplarily, the transceiver unit 132 may receive an eleventh message from the first access and mobility management function network element. The eleventh message includes identification information of multiple sessions and identification information of multiple session management function network elements that manage the multiple sessions. It should be understood that the multiple sessions include at least the above-mentioned first session, and the identification information of the multiple session management function network elements includes at least the fourth identification information of the first session management function network element. The processing unit 131 may be used to determine the fourth identification information of the first session management function network element used to manage the first session according to the eleventh message.

[0567] Exemplarily, the seventh message may also include the sixth identification information of the second session of the terminal device. It should be understood that the second session may be managed by a second session management function network element other than the first session management function network element. Alternatively, the transceiver unit 132 may be used to receive a twelfth message from the terminal device, the twelfth message may be used to request an update of the second session of the terminal device, the twelfth message includes the sixth identification information of the second session, and the second session is managed by the second session management function network element.

[0568] Exemplarily, the transceiver unit 132 may be used to send an eighth message to the second session management function network element. The eighth message is used to request the second session management function network element to update the session context of the second session, and the updated session context of the second session does not contain the second identification information of the second network device. The eighth message includes the sixth identification information of the second session. Furthermore, the eighth message may also include the fifth identification information of the terminal device and the access network tunnel information of the first network device. Furthermore, the eighth message may also include a session modification indication corresponding to the second session or a session modification message corresponding to the second session.

[0569] Exemplarily, the ninth message may further include sixth identification information of the second session. The tenth message may further include seventh identification information of a second session management function network element that manages the second session.

[0570] Exemplarily, the seventh message may further include seventh identification information of the second session management function network element.

[0571] Exemplarily, the multiple sessions in the above eleventh message also include the second session, and the identification information of the multiple session management function network elements may also include the seventh identification information of the second session management function network element.

[0572] In one possible design, the communication device 130 may correspond to Fig.12 The terminal device in the method shown, such as the communication device 130, can be a terminal device or a chip in the terminal device. The communication device 130 can include a device for executing Fig.12 The units of the operation performed by the terminal device in the method shown in the figure are respectively for implementing Fig.12 The operations performed by the terminal device in the method shown.

[0573] Exemplarily, the processing unit 131 is used to obtain target information. The target information includes tracking area information of a second network device, and the second network device is an anchor network device of the terminal device. The transceiver unit 132 is used to send the target information to the first network device. The first network device is the network device currently connected to the terminal device, and the tracking area information in the target information can be used to enable the first network device to obtain the terminal device context of the terminal device.

[0574] Exemplarily, the target information may be a temporary identifier of an inactivated wireless network of the terminal device.

[0575] Exemplarily, the target information may also include fifth identification information of the terminal device and second identification information of the second network device.

[0576] Exemplarily, the above-mentioned target information may be carried in an RRC connection recovery request sent by the terminal device to the first network device.

[0577] In one possible design, the communication device 130 may correspond to Fig.12 The first access and mobility management function network element in the method shown, such as the communication device 130, can be the first access and mobility management function network element, or can be a chip in the first access and mobility management function network element. The communication device 130 may include a chip for executing Fig.12 The unit of the operation performed by the first access and mobility management function network element in the method shown, and the units in the communication device 130 are respectively for implementing Fig.12 The operations in the method shown are performed by the first access and mobility management function network element.

[0578] Exemplarily, the transceiver unit 132 may be used to receive target information from the first network device. The target information may include tracking area information of the second network device, the first network device is the network device currently accessed by the terminal device, and the second network device is the anchor network device of the terminal device. The processing unit 131 may be used to obtain the terminal device context of the terminal device according to the tracking area information. The transceiver unit 132 is also used to send the obtained terminal device context to the first network device.

[0579] Exemplarily, when the first tracking area information range corresponding to the first access and mobility management function network element includes the tracking area information, or when the first access and mobility management function network element manages the second network device, the transceiver unit 132 may be used to send a context retrieval request of the terminal device to the second network device. The context retrieval request may include the above-mentioned target information. The transceiver unit 132 may be used to receive a context retrieval response from the second network device. The context retrieval response may include the terminal device context of the terminal device.

[0580] Exemplarily, when the first tracking area information range corresponding to the first access and mobility management function network element does not include the tracking area information, or in other words, when the first access and mobility management function network element does not manage the second network device, the transceiver unit 132 may be used to send the target information to the second access and mobility management function network element. Here, the second tracking area information range corresponding to the second access and mobility management function network element includes the tracking area information in the target information. In other words, the second access and mobility management function network element manages the above-mentioned second network device. The transceiver unit 132 may be used to receive the terminal device context from the second access and mobility management function network element.

[0581] In one possible design, the communication device 130 may correspond to Fig.12 The first network device in the method shown, such as the communication device 130, can be the first network device, or a chip in the first network device. The communication device 130 can include a device for executing Fig.12 The units of the operation performed by the first network device in the method shown in the figure are respectively for implementing Fig.12 The operations in the method shown are performed by the first network device.

[0582] Exemplarily, the transceiver unit 132 may be used to receive target information from a terminal device. The target information may include tracking area information of a second network device. Here, the first network device is a network device to which the terminal device is currently connected, and the second network device is an anchor network device of the terminal device. The transceiver unit 132 may be used to send target information to a first access and mobility management function network element. The transceiver unit 132 may be used to receive a terminal device context from the first access and mobility management function network element. It should be understood that the terminal device context of the terminal device may be obtained by the first access and mobility management function network element based on the target information.

[0583] Exemplarily, the transceiver unit 132 may send the above-mentioned target information to the first access and mobility management function network element when the processing unit 131 determines that the first network device cannot directly obtain the terminal device context of the terminal device from the second network device.

[0584] See also Fig.14 , Fig.14 This is a schematic diagram of the structure of another communication device provided by the present application. The communication device 140 can be used to implement the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The operation performed by the first network device in the method shown, or the communication device 140 can be the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The first network device in the method shown. The communication device 140 includes: a processor 141, a memory 142 and a bus system 143.

[0585] The memory 142 is used to store relevant instructions and data. The memory 142 stores the following elements, executable modules or data structures, or their subsets, or their extended sets:

[0586] Operation instructions: include various operation instructions, used to implement various operations.

[0587] Operating system: includes various system programs used to implement various basic businesses and handle hardware-based tasks.

[0588] Fig.14 Only one memory is shown in the figure, of course, the memory can also be set to multiple as needed.

[0589] The communication device 140 may further include a transceiver 144. The transceiver 144 may be a communication module or a transceiver circuit. Figures 4 to 12 The message or information sending and receiving operations involved in the method shown.

[0590] The processor 141 may be a controller, a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The processor 141 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0591] In a specific application, the components of the communication device 140 are coupled together through the bus system 143, wherein the bus system 143 may include a power bus, a control bus, and a status signal bus in addition to a data bus. Fig.14 In the figure, various buses are labeled as bus system 143. For convenience of representation, Fig.14 The drawing is only schematic.

[0592] In a specific implementation, the communication device 140 may execute the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12Specifically, when the communication device 140 is used to implement the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 When the first network device in the method is performing each step, the processor 141 may be used to implement the function of the processing unit 131 , and the transceiver 144 is used to implement the function of the transceiver unit 132 .

[0593] It should be noted that in practical applications, the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application may be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in a decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0594] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rateSDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (directrambus RAM, DR RAM). It should be noted that the memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0595] The present application also provides a computer-readable medium on which a computer program is stored, which, when executed by a computer, implements the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The method steps are performed by the first network device in the method shown.

[0596] The present application also provides a computer program product, which, when executed by a computer, implements Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The method steps are performed by the first network device in the method shown.

[0597] The present application also provides a chip, comprising at least a processor. The processor is used to execute computer execution instructions so that a device equipped with the chip can implement the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The method steps are performed by the first network device in the method shown.

[0598] Optionally, the chip may further include an interface circuit, which is used to receive computer execution instructions and transmit them to the processor.

[0599] The present application also provides a chip system, which includes a processor for supporting a device equipped with the chip system to implement the above Figures 4 to 11 The first session management function network element in the method shown, Figures 4 to 5 The first network element in the method shown, Figures 9 to 11 The first network device in the method shown, Figures 6 to 8 The terminal device in the method shown, Figures 6 to 8 The first network device in the method shown, Fig.12 The terminal device in the method shown, Fig.12 The first access and mobility management function network element or Fig.12 The method steps performed by the first network device in the method shown. For example, generating or processing the data and / or information involved in the above method. In one possible design, the chip system also includes a memory, and the memory is used to store program instructions and data necessary for the data sending device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0600] In the above method embodiment, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD), or a semiconductor medium (e.g., a solid state disk (SSD), etc.).

[0601] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0602] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process or an execution thread, and a component may be located on a computer or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. Components may communicate, for example, through local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals).

[0603] It should be understood that the "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0604] It should be understood that in the embodiments of the present application, the numbers "first", "second"... are only for distinguishing different objects, such as distinguishing different network devices, and do not constitute a limitation on the scope of the embodiments of the present application. The embodiments of the present application are not limited to this.

[0605] It should also be understood that in the present application, "when", "if" and "if" all mean that the network element will take corresponding actions under certain objective circumstances, and do not limit the time, nor do they require the network element to have a judgment action when implementing it, nor do they mean that there are other limitations.

[0606] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0607] It should also be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0608] The meaning of expressions similar to "the project includes one or more of the following: A, B, and C" in this application, unless otherwise specified, generally means that the project can be any of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. The above is an example of three elements, A, B and C, to illustrate the optional items of the project. When it is expressed as "the project includes at least one of the following: A, B, ..., and X", that is, when there are more elements in the expression, the items that can be applied to the project can also be obtained according to the above rules.

[0609] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0610] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0611] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0612] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0613] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0614] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories ROM, random access memories RAM, magnetic disks or optical disks.

[0615] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, It is characterized in that Applicable to a first session management function network element, the first session management function network element is used to manage a first session of a terminal device, the method comprising: Receiving a first message, wherein the first message is used to indicate that a radio access network change occurs to the terminal device and the first message includes at least one of first identification information of a first network device and a radio access network change indication of the terminal device, or the first message is used to request an update of the first session and the first message includes first identification information of a first network device, the first network device is a network device currently accessed by the terminal device, and the first network device is directly connected to the first session management function network element; The target session context is updated according to the first message, wherein the target session context is the session context of the first session, and the updated target session context does not include the second identification information of the second network device, and the second network device is the anchor network device of the terminal device.

2. The method according to claim 1, It is characterized in that When the first message is used to indicate that the wireless access network of the terminal device has been changed and the first message includes at least one of the first identification information and the wireless access network change indication, the first message comes from a first network element, and the first network element is used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device.

3. The method according to claim 2, It is characterized in that The method further comprises: When a first condition is met, a second message is sent to the first network element, wherein the second message is used to subscribe to the mobility events of the terminal device, and the first condition includes at least one of the following: the first session is established, the first session is in an activated state, and the terminal device enters a radio resource control RRC inactivated state.

4. The method according to claim 3, It is characterized in that The first condition includes: the terminal device enters an RRC inactive state, and the method further includes: Receiving an RRC inactive state indication of the terminal device; Determining that the first condition is satisfied based on the RRC inactive state indication.

5. The method according to claim 3 or 4, It is characterized in that The second message includes a radio access network change notification request corresponding to the terminal device.

6. The method according to any one of claims 2 to 5, It is characterized in that The updating of the target session context according to the first message includes: In the case where the first message includes the first identification information, the second identification information in the target session context is replaced with the first identification information to obtain an updated target session context.

7. The method according to any one of claims 2 to 6, It is characterized in that The updating of the target session context according to the first message includes: In a case where the first message includes the radio access network change indication, the second identification information in the target session context is deleted to obtain an updated target session context.

8. The method according to any one of claims 2 to 7, It is characterized in that The method further comprises: When the second condition is met, a third message is sent to the first network element, wherein the third message is used to cancel the subscription to the mobility event of the terminal device, and the second condition includes at least one of the following: the first session is released, the first session is in a deactivated state, and the terminal device leaves the RRC inactivated state.

9. The method according to claim 1, It is characterized in that In a case where the first message is used to request updating of the first session and the first message includes first identification information of the first network device, the first message comes from the first network device.

10. A communication method, It is characterized in that Applicable to a first network element, the first network element is used to store a terminal device context of a terminal device or to be responsible for access management of the terminal device, the method comprising: receiving a second message from a first session management function network element, wherein the second message is used to subscribe to a mobility event of the terminal device, and the first session management function network element is used to manage a first session of the terminal device; Send a first message, wherein the first message is used to indicate that the terminal device has a change in the wireless access network and the first message includes at least one of first identification information of a first network device and an indication of a change in the wireless access network of the terminal device, and the first network device is a network device to which the terminal device is currently connected.

11. The method according to claim 10, It is characterized in that The second message includes a radio access network change notification request corresponding to the terminal device.

12. The method according to claim 10 or 11, It is characterized in that The sending of the first message comprises: A first message is sent when a third condition is met, wherein the third condition includes at least one of the following: receiving a fourth message from the first network device and the fourth message is used to update the location information of the terminal device, and determining that the terminal device has a radio access network change when the non-RRC connection is restored.

13. A communication method, It is characterized in that Applicable to a first network device, the method comprises: Acquire a terminal device context of the terminal device, wherein the terminal device context includes third identification information of the first session and fourth identification information of a first session management function network element, and the first session management function network element is used to manage the first session; A first message is sent to the first session management function network element, wherein the first message is used to request updating of the first session, and the first message includes first identification information of a first network device, and the first network device is a network device to which the terminal device is currently connected.

14. The method according to claim 13, It is characterized in that The obtaining of the terminal device context of the terminal device includes: Sending a fifth message to the first network element, wherein the fifth message is used to request a terminal device context of the terminal device, and the first network element is used to store the terminal device context of the terminal device or to be responsible for access management of the terminal device; Receive a sixth message from the first network element, wherein the sixth message includes a terminal device context of the terminal device.

15. The method according to claim 14, It is characterized in that The fifth message is sent by the first network device when the radio resource control RRC connection recovery of the terminal device fails; Alternatively, the fifth message is sent by the first network device when an RRC connection is established between the terminal device and the first network device.

16. The method according to claim 13, It is characterized in that The obtaining of the terminal device context of the terminal device includes: When the RRC connection of the terminal device is successfully restored, sending a context retrieval request of the terminal device to a second network device, wherein the second network device is an anchor network device of the terminal device; A context retrieval response is received from the second network device, wherein the context retrieval response includes a terminal device context of the terminal device.

17. A communication method, It is characterized in that The method is applicable to a terminal device, and the method comprises: In the case where the radio resource control RRC connection recovery fails, sending a fourth message to the first network device, wherein the fourth message is used to update the location information of the terminal device, and the first network device is the network device currently accessed by the terminal device; A seventh message is sent to the first network device, wherein the seventh message is used to request updating of the first session of the terminal device, and the seventh message includes third identification information of the first session.

18. The method according to claim 17, It is characterized in that The first session is in an activated state.

19. A communication method, It is characterized in that The method is applicable to a terminal device, and the method comprises: Acquire target information, wherein the target information includes tracking area information of a second network device, where the second network device is an anchor network device of the terminal device; The target information is sent to a first network device that is currently connected, wherein the tracking area information is used to enable the first network device to obtain a terminal device context of the terminal device.

20. A communication method, It is characterized in that The method is applicable to a first access and mobility management function network element, and the method includes: Receiving target information from a first network device, wherein the target information includes tracking area information of a second network device, the first network device is a network device currently accessed by a terminal device, and the second network device is an anchor network device of the terminal device; Acquire a terminal device context of the terminal device according to the tracking area information; The terminal device context is sent to the first network device.

21. The method according to claim 20, It is characterized in that The acquiring the terminal device context of the terminal device according to the tracking area information includes: In a case where the first tracking area information range corresponding to the first access and mobility management function network element includes the tracking area information, sending a context retrieval request of the terminal device to the second network device, wherein the context retrieval request includes the target information; A context retrieval response is received from the second network device, wherein the context retrieval response includes a terminal device context of the terminal device.

22. The method according to claim 20, It is characterized in that The acquiring the terminal device context of the terminal device according to the tracking area information includes: In a case where a first tracking area information range corresponding to the first access and mobility management function network element does not include the tracking area information, sending the target information to a second access and mobility management function network element, wherein a second tracking area information range corresponding to the second access and mobility management function network element includes the tracking area information; Receive a terminal device context of the terminal device from the second access and mobility management function network element.

23. A communication method, It is characterized in that Applicable to a first network device, the method comprises: Receiving target information from a terminal device, wherein the target information includes tracking area information of a second network device, the first network device is a network device currently accessed by the terminal device, and the second network device is an anchor network device of the terminal device; Sending the target information to the first access and mobility management function network element; Receive a terminal device context of the terminal device from the first access and mobility management function network element.

24. The method according to claim 23, It is characterized in that The sending the target information to the first access and mobility management function network element includes: When the terminal device context of the terminal device cannot be directly obtained from the second network device, the target information is sent to the first access and mobility management function network element.

25. A communication device, It is characterized in that The communication device includes: a module or a unit for implementing the communication method as claimed in any one of claims 1-9, any one of claims 10-12, any one of claims 13-16, claim 17 or 18, claim 19, any one of claims 20-22, or claim 23 or 24.

26. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, which, when executed, implements the communication method as described in any one of claims 1 to 9, any one of claims 10 to 12, any one of claims 13 to 16, any one of claims 17 or 18, any one of claims 19, any one of claims 20 to 22, or any one of claims 23 or 24.

27. A chip, It is characterized in that Including processors; The processor is used to execute computer-executable instructions so that the device equipped with the chip performs the communication method as described in any one of claims 1-9, any one of claims 10-12, any one of claims 13-16, any one of claims 17 or 18, claim 19, any one of claims 20-22, or any one of claims 23 or 24.

28. The chip according to claim 27, It is characterized in that The chip further comprises an interface circuit, wherein the interface circuit is used for receiving the computer execution instruction and transmitting the instruction to the processor.

29. A computer program product, wherein the computer program product is executed by a computer according to any one of claims 1 to 9, any one of claims 10 to 12, any one of claims 13 to 16, any one of claims 17 or 18, any one of claims 19, any one of claims 20 to 22, or any one of claims 23 or 24.

30. A communication device, It is characterized in that include: at least one processor and memory; The memory is used to store computer programs; The processor is used to execute the computer program stored in the memory so that the communication device performs the communication method as described in any one of claims 1 to 9, any one of claims 10 to 12, any one of claims 13 to 16, any one of claims 17 or 18, any one of claims 19, any one of claims 20 to 22, or any one of claims 23 or 24.

Citation Information

Cited By

  • Communication method and related apparatus

    WO2026026391A1

  • Context acquisition method and apparatus, communication device and readable storage medium

    WO2026138570A1