Resource management method, electronic device, and computer-readable storage medium

Abstract

The present disclosure provides a resource management method, an electronic device, and a computer-readable storage medium. [Solution] The resource management method includes a step of determining whether a remaining inactivity time of a user equipment UE with respect to a target bearer node has expired, and a step of releasing resources allocated to the UE if the remaining inactivity time of the UE with respect to the target bearer node has expired, wherein the remaining inactivity time includes a sum of preset inactivity times corresponding to the target bearer node minus a sum of persistent inactivity times accrued by the UE with all nodes.

Description

[Technical Field]

[0001] This application claims priority from Chinese Patent Application No. 202210710621.3, filed on June 22, 2022, and incorporates the contents of that Chinese patent application by reference.

[0002] The present disclosure relates to the field of communications, and more particularly to a resource management method, an electronic device, and a computer-readable storage medium. [Background technology]

[0003] The New Radio (NR) Dual Connectivity (NR-DC) feature allows standalone (SA) terminals to access the 5G Frequency Range 1 (FR1) side. At the same time, a 5G (FR1) radio connection is established. Downstream data can be transmitted via either the 5G (FR1) or 5G Frequency Range 2 (FR2) radio. Upstream data is transmitted to the NR via the 5G (FR1) or 5G (FR2) radio, and the NR is transmitted to the core network via the NG interface. There are two types of frameworks: (1) The UE connects to one NR as a master node (MN) and one NR as a secondary node (SN). The NR (FR1) connects to the 5G core network (5GC) via the NG interface and to the NR (FR2) via the XN interface. The NR (FR2) connects to the 5GC via the NG-U interface. (2) The UE is connected to one NR, which includes multiple distributed units (DUs), one DU (FR1) being an MN and one DU (FR2) being an SN, and the NR is connected to the 5GC via the NG interface. Summary of the Invention [Problem to be solved by the invention]

[0004] In the NR-DC system, like the standalone system (SA), access network resources are limited, and the number of users that can be accommodated is also limited. The following phenomenon often occurs during the operation of the current network: During the operation of the next generation base station (gNB, next generation Node B), a session or flow established by a user may have no user data for a long period of time. In order to save valuable system resources, especially when the system load is heavy, and to improve resource utilization and give limited resources to users who really need them, operators need to accurately and quickly release packet data unit (PDU) sessions, flows, and user connections that do not need to transmit any data. [Means for solving the problem]

[0005] In a first aspect, the present disclosure provides a resource management method comprising the steps of: determining whether a remaining inactivity time of a user equipment (UE) with respect to a target bearer node has expired; and releasing resources allocated to the UE if the remaining inactivity time of the UE with respect to the target bearer node has expired, wherein the remaining inactivity time comprises a sum of preset inactivity times corresponding to the target bearer node minus a sum of persistent inactivity times accrued by the UE with all nodes.

[0006] In a second aspect, the present disclosure provides an electronic device comprising at least one processor; a memory having stored therein at least one computer program, the at least one computer program, when executed by the at least one processor, causing the at least one processor to implement the resource management method described in the first aspect; and at least one I / O interface connected between the processor and the memory and configured to enable information interaction between the processor and the memory.

[0007] In a third aspect, the present disclosure provides a computer-readable storage medium having stored thereon a computer program that, when executed by a processor, causes the resource management method according to the first aspect to be implemented. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a flowchart of a resource management method according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a flowchart of a resource management method according to an embodiment of the present disclosure, which is centered on the MN. [Figure 3] FIG. 3 is a flowchart of a resource management method according to an embodiment of the present disclosure, which is centered on the MN. [Figure 4] FIG. 4 is a flowchart of an SN-based resource management method according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a flowchart of an SN-based resource management method according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a flowchart of NR-DC current user inactivity processing according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart of a UE's persistent inactivity time transmission in an NR-DC scenario according to an embodiment of the present disclosure (taking SN addition as an example). [Figure 8]FIG. 8 is a flowchart illustrating a change from an MCG bearer to an SCG bearer according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a flowchart illustrating a change from an MN terminal bearer to an SN terminal bearer according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a flowchart illustrating a change from an SN terminal bearer to an MN terminal bearer according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is a flowchart of a UE's persistent inactivity time signaling when changing SN according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a schematic diagram of an electronic device according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0009] It should be understood that specific examples described herein are illustrative of the disclosure only and are not intended to be limitations of the disclosure.

[0010] In the following description, the suffixes "module," "component," or "unit" used to refer to components are used only to facilitate the description of the present disclosure and do not have any special meaning in themselves. Therefore, the terms "module," "component," or "unit" may be used interchangeably.

[0011] In conventional SA systems, the high power consumption of both terminals and system devices is an urgent issue. Especially when an NR-DC system is networked using low and high frequencies, the NR power consumption at high frequencies and the terminal power consumption must be reduced as quickly as possible. When a PDU session or flow has no data on the high frequency side, it must be released as quickly as possible to achieve the purpose of system energy saving or terminal power saving. Sessions and flows with no data can be handled by the user inactivity function, but currently, the NR-DC scenario has the following three problems, as shown in Figure 6.

[0012] 1) The MN initiates an SN addition request message with content including information on bearer type and PDCP bearer type (e.g., MN terminal, SN terminal). The MN initiates an SN addition request measurement trigger and maintains the UE inactivity timer for UE sessions or flows that already existed before the SN addition, but does not convey the remaining inactivity timer time to the SN in the message at the time of SN addition.

[0013] 2) The SN receives the bearer service message of the MN, establishes the corresponding bearer, and returns an acknowledgement to the MN. In the case of an SN terminal bearer, the service may have changed from a Master Cell Group (MCG) bearer to a Secondary Cell Group (SCG) bearer, restarting the UE inactivity timer at the target bearer node.

[0014] 3) The SN reports the UE inactivity state periodically or event-triggered based on a local inactivity timer mechanism. If the reported SN Activity Notification message carries a UE inactivity indication, the MN determines the UE inactivity release policy. If the reported SN Activity Notification message carries a UE reactivation indication, the state is reversed and the MN reactivates the SN-side service bearers. Since the SN inactivity timer is maintained by the SN, it is unknown how long the UE on the MN remains in the inactive state and is not updated according to the UE inactivity state before the SN addition, so the problem of the UE inactive state remaining too long in total may occur.

[0015] To address the above issue, several studies have found that related NR-DC dual connectivity technologies do not transmit the inactivity time experienced by the UE during bearer change to the new bearer node, resulting in the UE's inactivity state being reset after the bearer change, resulting in increased service power consumption and wasted radio resources. In NR-DC scenarios, the MN bearer controls the user inactivity timer, and the SN only reports whether the UE's state is active or inactive, with the MN deciding whether to release it. When a bearer changes from an MCG bearer to an SCG bearer (or from an MN terminal bearer to an SN terminal bearer), the UE inactivity timer cannot continue to be transmitted by the original MN bearer, so the timer must be restarted after the bearer change. However, the user inactivity timer (ue-InactiveTime) specified in the protocol ranges from 1 s to over 30 days. Failure to inherit the relevant counters during the dual connectivity bearer change process can have a significant impact on the user experience. For example, if the user inactivity timer is set too long, it not only consumes power but also consumes valuable radio system radio resources.

[0016] The current standard protocol specifies that for Xn radio switching in an SA system, the source gNB transmits the ue-InactiveTime information element to the target gNB via the Xn radio container, and the target gNB receives it and continues the UE inactive state, improving radio resource utilization and terminal power saving. However, the 3GPP protocol does not take this issue into consideration. A UE simultaneously maintains connections with two NR-DC base stations, and when a service bearer is changed from one base station to another, the user inactive time mechanism cannot be effectively conveyed. Therefore, service transition to a new bearer requires the establishment of a new counter, which is likely to increase the UE connected state time. In the absence of a user service request, this increases the UE connected state time and consumes radio resources.

[0017] Based on the above analysis, this disclosure proposes optimizing radio resource management using ue-InactiveTime transmission via NR-DC dual connection to achieve the effects of saving radio resources and reducing power consumption.

[0018] As a first aspect of the present disclosure, an embodiment of the present disclosure provides a resource management method, and as shown in FIG. 1, the resource management method includes the following steps S100 and S200.

[0019] In step S100, it is determined whether the remaining inactivity time of the user equipment (UE) for the target bearer node has expired.

[0020] In step S200, if the remaining inactivity time of the UE with respect to the target bearer node has expired, release the resources allocated to the UE, where the remaining inactivity time comprises the sum of the preset inactivity times corresponding to the target bearer node minus the sum of the persistent inactivity times generated by the UE with all nodes.

[0021] Regardless of whether the MN or the SN bears the current UE service, in the case of bearer change, the persistent inactivity time of the UE at the source bearer node is transmitted to the target bearer node, and the target bearer node subtracts the persistent inactivity time of the UE at the source bearer node from the total time of the preset inactivity time to obtain the remaining inactivity time of the UE at the target bearer node. The MN can transmit the UE inactivity timer to the SN and continue the timer configured on the MN side, and similarly, the SN can transmit the UE inactivity timer to the MN and continue the timer configured on the SN side.

[0022] Since the UE inactivity time is transmitted and inherited each time a bearer is changed, the target bearer node subtracts the sum of the sustained inactivity times of all source bearer nodes that have previously borne the UE service. If the result of the subtraction is already less than or equal to 0, the UE's remaining inactivity time for the target bearer node is directly considered to have expired. If the result of the subtraction is greater than 0, the result is considered to be the UE's remaining inactivity time for the target bearer node, and timing continues. When this remaining inactivity time expires, a decision is triggered in the MN to release the resources allocated to the UE.

[0023] Figure 7 shows the flowchart of the UE's persistent inactivity time transmission in the NR-DC scenario (taking SN addition as an example). Compared with the current NR-DC scenario process described above, 1) The MN initiates an SN Addition Request message with content including information on bearer type and PDCP bearer type (MN terminal, SN terminal). The MN initiates an SN Addition Request measurement trigger, maintains the UE inactivity timer for sessions or flows that already existed before the SN addition, and conveys the remaining inactivity timer time of the UE to the SN at the time of SN addition. 2) The SN receives the bearer service message of the MN, establishes the corresponding bearer, and returns a response to the MN. For the SN terminal bearer, the service is changed from the MCG bearer to the SCG bearer, which the SN side can determine. The SN can inherit the remaining inactivity timer of the UE and can set a new timer time by itself. 3) The SN reports the UE inactivity state periodically or with an event trigger based on the UE inactivity timer transmitted from the MN. If a UE inactivity indication is carried, the MN determines the UE inactivity release policy. If a UE reactivation indication is carried, the state is reversed and the MN reactivates the SN-side service bearer. The SN inactivity timer is uniformly maintained by the MN, and the remaining inactivity timer is inherited after SN addition, allowing for more accurate control of the overall UE inactivity time.

[0024] In addition to the above-mentioned SN addition scenario, other bearer change flows in the NR-DC dual connection scenario, such as the bearer change flow between MCG, Split, and SCG, the bearer type change from MN Terminal bearer to SN Terminal bearer, the bearer type change from SN Terminal bearer to MN Terminal bearer, and the change flow from one SN to another SN, as shown in Tables 1 and 2, can also adopt the resource management method proposed in this disclosure, and by adopting the ue-InactiveTime transmission method, not only can the management of radio resources be optimized, but also power consumption can be reduced.

[0025] [Table 1]

[0026] [Table 2]

[0027] In the process of transmitting the inherited UE's persistent inactivity time, the calculation principle in Table 3 below can be used, where T1 is the total time of the preset inactivity time in the MN, T2 is the total time of the preset inactivity time in the SN, and t is the persistent inactivity time transmitted when the bearer is changed.

[0028] [Table 3]

[0029] In some embodiments, as shown in FIG. 2 , the current node is a master node (MN), the source bearer node of the UE's service is the MN, and the target bearer node is a target secondary node (SN), and before the UE's remaining inactivity time for the target bearer node expires, the resource management method further includes steps S310 and S320.

[0030] In step S310, the UE determines the sustained inactivity time generated by the source bearer node.

[0031] In step S320, the target SN sends a message carrying the persistent inactivity time of the UE at the source bearer node to the target SN, so that the target SN determines the remaining inactivity time of the UE with respect to the target bearer node based on the persistent inactivity time of the UE at the source bearer node.

[0032] For an MN, as far as the UE service bearer change flow is concerned, the persistent inactivity time generated by the UE at the source bearer node can be transmitted to the target bearer node. The UE transmits the persistent inactivity time generated by the source bearer node through a message previously exchanged between the source bearer node and the target bearer node during bearer change, thereby realizing synchronization of the length of the UE persistent inactivity time between the source bearer node and the target bearer node.

[0033] In some embodiments, the step of sending a message conveying a persistent inactivity time of the UE at the source bearer node to the target SN comprises: The method includes sending an SN addition request message to the target SN, the SN adding request message carrying a persistent inactivity time of the UE at the source bearer node.

[0034] As the SN addition scenario has been explained above in the explanation of FIG. 7, a detailed explanation will be omitted here.

[0035] In some embodiments, the step of sending a message conveying a persistent inactivity time of the UE at the source bearer node to the target SN comprises: The method includes sending an SN change request message to the target SN, the SN change request message carrying a persistent inactivity time of the UE at the source bearer node.

[0036] In some embodiments, as shown in FIG. 3 , the current node is an MN, the source bearer node of the UE's service is a target SN, the target bearer node is the MN, and before the remaining inactivity time of the UE to the target bearer node expires, the resource management method further includes steps S330 and S340.

[0037] In step S330, a message carrying a persistent inactivity time of the UE at a source bearer node is received from a target SN.

[0038] In step S340, obtain the remaining inactivity time of the UE to the target bearer node based on the sum of the preset inactivity times in the MN minus the persistent inactivity time in the source bearer node.

[0039] For the MN, this may involve a change in service from being borne by the MN to being borne by the SN (as explained above), or a change in service from being borne by the SN back to being borne by the MN, with the SN acting as the source bearer node and the MN acting as the target bearer node. Although the MN is the master node, because the service is borne by the SN, the MN cannot know in real time how long the UE's service has been idle at the SN, and the SN needs to communicate the UE's persistent inactivity time to the MN, and the MN obtains the UE's remaining inactivity time at the MN by subtracting the persistent inactivity time at the source bearer node from the total preset inactivity time at the MN.

[0040] In addition, when a service is changed from being borne by a first SN to being borne by a second SN, since there is no message interaction between SNs, the first SN must first transmit the persistent inactivity time to the MN, and then the MN must transmit the persistent inactivity time to the newly added second SN.

[0041] These flows remain the same as described above, that is, as far as the UE service bearer change flow is concerned, the persistent inactivity time generated by the UE at the source bearer node can be transmitted to the target bearer node. By transmitting the persistent inactivity time generated by the UE at the source bearer node through a message previously exchanged between the source bearer node and the target bearer node during bearer change, synchronization of the length of the UE persistent inactivity time between the source bearer node and the target bearer node can be achieved.

[0042] In some embodiments, the step of receiving from a target SN a message conveying a persistent inactivity time for the UE at a source bearer node comprises: The method includes receiving an SN change request message from a target SN, the SN change request message carrying a persistent inactivity time of the UE at a source bearer node.

[0043] In some embodiments, the step of receiving from a target SN a message conveying a persistent inactivity time for the UE at a source bearer node comprises: The method includes receiving an SN release request message from a target SN, the SN release request message carrying a persistent inactivity time of the UE at a source bearer node.

[0044] In some embodiments, the step of determining whether a remaining inactivity time of the user equipment UE with respect to the target bearer node has expired comprises: If the service of the UE is currently being bearered by the MN, the MN may detect whether the remaining inactivity time of the UE for the target bearer node has expired.

[0045] In some embodiments, the step of determining whether a remaining inactivity time of the user equipment UE with respect to the target bearer node has expired comprises: If the UE's service is currently being bearered by the target SN, when the MN receives an SN activity notification message carrying an inactivity indication for the UE, it is determined that the UE's remaining inactivity time with respect to the target bearer node has expired.

[0046] In an NR-DC scenario, the UE's service may undergo bearer changes between nodes, so the UE's service may currently be borne by either the MN or the SN.

[0047] If the service of the UE is currently being carried by the MN, the MN is the master node and can decide to release the UE, so the MN can decide to release the resources allocated to the UE as long as it locally detects that the remaining inactivity time of the UE in the MN has expired.

[0048] If the UE's service is currently being carried by the SN, the MN cannot know in real time whether the UE is active or whether the remaining inactivity time has expired. Therefore, when the SN detects that the UE's remaining inactivity time has expired, the SN needs to notify the MN. Here, the existing SN activity notification message carrying the UE inactivity indication can be used to indicate that the UE's remaining inactivity time has expired in the SN, and other message information elements carrying specific fields can also be used to indicate that the UE's remaining inactivity time has expired in the SN, thereby notifying the MN in a timely manner that the UE's resources may be released.

[0049] In some embodiments, the resource management method further comprises: The method further includes canceling the release decision made for the UE when receiving an SN activity notification message from the target SN, the SN activity notification message carrying a reactivation instruction for the UE, before releasing resources allocated to the UE.

[0050] In some special timing scenarios, if the SN sends an SN activity notification message carrying an inactivity indication for the UE to the MN, but the MN does not release the resources allocated to the UE for some reasons (e.g., the UE has multiple sessions or flows, and some of the existing sessions or flows are still active), the SN should receive a service flow related to the UE indicating that the service of the UE, which is bearered by the SN, will be reactivated, reset the remaining inactivity time for the UE, set the persistent inactivity time to zero, and simultaneously send a reactivation indication to the MN to notify the MN to cancel the release decision made for the UE.

[0051] In some embodiments, as shown in FIG. 4 , the current node is a target SN, the source bearer node of the UE's service is an MN, the target bearer node is the target SN, and before the remaining inactivity time of the UE for the target bearer node expires, the resource management method further includes steps S410 and S420.

[0052] In step S410, receive a message from the MN, carrying a persistent inactivity time of the UE at a source bearer node.

[0053] In step S420, obtain the remaining inactivity time of the UE to the target bearer node based on the sum of the preset inactivity times in the target SN minus the persistent inactivity time of the UE at the source bearer node.

[0054] As for the SN, as mentioned above, insofar as the UE service bearer modification flow is concerned, the persistent inactivity time generated by the UE at the source bearer node can be transmitted to the target bearer node. The UE transmits the persistent inactivity time generated by the source bearer node through a message previously exchanged between the source bearer node and the target bearer node during bearer modification, thereby realizing synchronization of the length of the UE's persistent inactivity time between the source bearer node and the target bearer node.

[0055] When the service of the UE is changed from that bearered by the MN to that bearered by the SN, the message sent from the MN to the SN carries the persistent inactivity time of the UE at the MN, and after receiving the message carrying the persistent inactivity time of the UE at the MN, the SN subtracts the persistent inactivity time of the UE at the MN from the total time of the locally preset inactivity time to obtain the remaining inactivity time of the UE for the SN, and the SN continues to detect whether the remaining inactivity time has expired.

[0056] In some embodiments, the step of receiving from the MN a message conveying a persistent inactivity time of the UE at a source bearer node comprises: The method includes receiving an SN addition request message from the MN, the SN addition request message carrying a persistent inactivity time of the UE at a source bearer node.

[0057] In some embodiments, the step of receiving from the MN a message conveying a persistent inactivity time of the UE at a source bearer node comprises: The method includes receiving an SN change request message from the MN, the SN change request message carrying a persistent inactivity time of the UE at a source bearer node.

[0058] In some embodiments, the resource management method further comprises: The method further includes the step of, when the SN detects that the remaining inactivity time of the UE with respect to the target bearer node has expired, sending an SN activity notification message to the MN, carrying an inactivity indication of the UE.

[0059] After receiving the message carrying the persistent inactivity time of the UE in the MN, the SN subtracts the persistent inactivity time of the UE in the MN from the total time of the locally preset inactivity time to obtain the remaining inactivity time of the UE for the SN, and the SN continues to detect whether the remaining inactivity time has expired through a timer.

[0060] If the subtraction result is already less than or equal to 0, the UE's remaining inactivity time with respect to the target bearer node is directly considered to have expired. If the subtraction result is greater than 0, the result is considered to be the UE's remaining inactivity time with respect to the target bearer node, and timing continues. When the SN detects that the remaining inactivity time has expired, it sends the UE inactivity indication to the MN, which triggers an MN decision to release the resources allocated to the UE.

[0061] In some embodiments, after sending an SN activity notification message to the MN carrying an inactivity indication of the UE, the resource management method comprises: If service data of the UE appears before the resources allocated to the UE are released, resetting the remaining inactivity time to zero and setting the total time of the preset inactivity time as the remaining inactivity time of the UE for the target bearer node; and sending an SN activity notification message to the MN, carrying a reactivation indication for the UE.

[0062] In some special timing scenarios, when the SN has sent an SN activity notification message to the MN carrying an inactivity indication for the UE, but the MN does not release the resources allocated to the UE for some reasons, the SN should receive a service flow related to the UE indicating that the UE will be activated again, reset the remaining inactivity time of the UE, set the persistent inactivity time to zero, and simultaneously send a reactivation indication to the MN to notify the MN to cancel the release decision made for the UE.

[0063] In some embodiments, as shown in FIG. 5 , the current node is a target SN, the source bearer node of the service of the UE is the target SN, and the target bearer node is the MN, and before the remaining inactivity time of the UE with respect to the target bearer node expires, the resource management method further includes steps S430 and S440.

[0064] In step S430, the UE determines the sustained inactivity time generated by the source bearer node.

[0065] In step S440, the MN sends a message carrying the persistent inactivity time of the UE at the source bearer node to the MN, so that the MN determines the remaining inactivity time of the UE to the target bearer node based on the persistent inactivity time of the UE at the source bearer node.

[0066] In addition to the above-mentioned change of service from one borne by the MN to one borne by the SN, it may also involve a change of service from one borne by the SN to one borne by the MN, or a change of service from one borne by one SN to one borne by a second SN. The latter two flows, as described above, both have the SN as the source bearer node and the MN as the target bearer node. That is, as long as they involve a UE service bearer change flow, the persistent inactivity time generated by the UE at the source bearer node may be transmitted to the target bearer node. By transmitting the persistent inactivity time generated by the UE at the source bearer node through a message previously exchanged between the source bearer node and the target bearer node during bearer change, synchronization of the length of the UE's persistent inactivity time between the source bearer node and the target bearer node can be achieved.

[0067] In some embodiments, the step of sending a message to the MN conveying a persistent inactivity time of the UE at a source bearer node comprises: The method includes sending an SN change request message to the MN, the SN change request message carrying a persistent inactivity time of the UE at a source bearer node.

[0068] In some embodiments, the step of sending a message to the MN conveying a persistent inactivity time of the UE at a source bearer node comprises: The method includes sending an SN release request message to the MN, the SN release request message carrying a persistent inactivity time of the UE at a source bearer node.

[0069] Hereinafter, specific applications of the resource management method according to the first aspect of the present disclosure in four types of flows will be described in combination with four examples.

[0070] Example 1 As shown in FIG. 8, Example 1 describes a UE persistent inactivity time transmission flow in a bearer modification flow from an MCG to an SCG.

[0071] Step 101: In an NR-DC scenario, the MN establishes an MCG bearer, issues an SN measurement control, and triggers an SN addition flow. Before the SN is added, the MN starts a UE-InactiveTime T1, such as 10 minutes (< infinity) depending on the service type.

[0072] Step 102: The UE reports a B1 / B2 measurement report, and the MN triggers an SN addition flow.

[0073] Step 103: Establish an SCG bearer for the SN terminal in an SN addition message, trigger a change from an MCG bearer to an SCG bearer, and carry the UE's persistent inactivity time t (e.g., 2 minutes, < infinity), assuming that the UE inactivity state on the MCG bearer has been maintained for 8 minutes.

[0074] Step 104: The SN receives the Add Request message and establishes the associated bearer. If the T2 timer configured by the SN is greater than t, the SN starts the timer as (T2-t). Refer to the timer setting principle in Table 3.

[0075] Steps 105-106: After the bearer is changed to an SCG bearer, the SN continues the remaining UE inactivity time. The CU-C in the SN transmits the timer (T2-t) to the CU-U and DU.

[0076] If the UE is always in the inactive state, after the (T2-t) timer times out, the SN sends an SN activity notification to the MN, carrying a UE inactive state indication.

[0077] If a Session or Flow reappears in the UE at this point, the state is reversed and the SN immediately sends an SN active notification to the MN, carrying a UE re-activated state indication.

[0078] Steps 107-108: The UE is always in the inactive state and continues to trigger the MN to send an SN activity notification, carrying a UE inactive state indication. The MN decides whether to release the resources allocated to the UE, and if the MN bearer also meets the release conditions, initiates radio resource release.

[0079] Example 2 As shown in FIG. 9, Example 2 describes a transfer flow of UE persistent inactivity time in the flow of bearer type change from MN Terminal bearer to SN Terminal bearer.

[0080] Step 201: In an NR-DC scenario, the MN establishes an MCG bearer, issues an SN measurement control, and triggers an SN addition flow. Before the SN is added, the MN starts a UE-InactiveTime T1, such as 10 minutes (< infinity) depending on the service type.

[0081] Step 202: The UE reports a B1 / B2 measurement report, and the MN triggers an SN addition flow.

[0082] Step 203: Assume that an MN terminal bearer is established in the SN Add message, carrying the UE's persistent inactivity time t1 (eg, 7 minutes, <infinity) in the MN, and the UE inactivity timer on the MCG bearer is maintained for 3 minutes.

[0083] Step 204: The SN receives the Add Request message and establishes the associated bearer. If the T2 timer of the SN is greater than t1, the SN starts the timer as (T2-t1). Refer to the timer setting principle.

[0084] Steps 205-206: Due to resource allocation reasons, the MN triggers a change request from the MN terminal bearer to the SN terminal bearer, carrying the UE's sustained inactivity time t2 in the MN.

[0085] Steps 207-208: After the bearer is changed to the SN terminal, if the T2 timer configured by the SN is greater than t2, the SN starts the timer as (T2-t2). Refer to the timer setting principle in Table 3.

[0086] If the UE is always in the inactive state, after the (T2-t2) timer times out, it will send an SN active notification to the MN, carrying a UE inactive state indication.

[0087] When the UE state is reversed, an SN activation notification is sent to the MN immediately, carrying the UE re-activated state.

[0088] Steps 209-210: The UE is always in an inactive state and continuously triggers the MN to send an SN activity notification, carrying a UE inactive state indication. The MN determines whether to release the resources allocated to the UE, and if the MN bearer also meets the release conditions, initiates radio resource release.

[0089] Example 3 As shown in FIG. 10, Example 3 describes a process for transmitting UE persistent inactivity time in a process for changing the type of bearer from SN Terminal bearer to MN Terminal bearer.

[0090] Step 301: In an NR-DC scenario, the MN establishes a bearer side and issues an SN measurement control, triggering an SN addition flow. Before the SN is added, the MN starts a UE-InactiveTime T1, such as 60 seconds (< infinity) depending on the service type.

[0091] Step 302: The UE reports a B1 / B2 measurement report, and the MN triggers an SN addition flow.

[0092] Step 303: The MN sends an SN Add message to the SN to establish an MN terminal bearer, carrying the persistent inactivity time t1 (eg, 30 seconds, <infinity) of the UE in the MN.

[0093] Step 304: The SN receives the Add Request message and establishes the associated bearer, and sets a new time T2 (for example, 40 seconds) according to the service bearer type.

[0094] If T2 is equal to or less than t1, the timer is not started, and the SN immediately notifies the MN that the session or flow is in the user inactive state.

[0095] If T2 is greater than t1, start the timer and the time is (T2-t1).

[0096] Steps 305-306: Due to resource allocation reasons, the SN triggers a change request from the SN terminal to the MN terminal, carrying the sustained inactivity time t2 (for example, 6 seconds) of the UE in the SN.

[0097] Steps 307-308: After the bearer is changed to the MN terminal, the MN sets a new time T1 (for example, 60 seconds) according to the service bearer type, and activates the timer (T1-t2).

[0098] If T1 is less than or equal to t2, the MN does not start the timer. Because a UE may have multiple services in the SN, when transferring a bearer, the SN immediately notifies the MN that the session or flow is in the user inactive state.

[0099] If T1 is greater than t2, start the timer and the time is (T1-t).

[0100] If the UE is always in the inactive state, after the (T1-t) timer times out, it will send an SN active notification to the MN, carrying a UE inactive state indication.

[0101] When the UE state is reversed, an SN activation notification is sent to the MN immediately, carrying the UE re-activated state.

[0102] Steps 309-310: The UE is always in an inactive state and triggers the MN to send an SN activity notification, carrying a UE inactive state indication. The MN determines whether to release the resources allocated to the UE, and if the MN bearer also meets the release conditions, initiates radio resource release.

[0103] Example 4 As shown in FIG. 11, Example 4 describes a process for transmitting a UE persistent inactivity time in an SN change process.

[0104] Step 401: In an NR-DC scenario, service initiation establishes an MCG bearer, issues an SN1 measurement control, and triggers an SN1 addition flow. Before the SN1 is added, the MN starts a ue-InactiveTime T1, such as 5 minutes depending on the service type.

[0105] Step 402: The UE reports a B1 / B2 measurement report, and the MN triggers an SN Add flow, and carries the UE's sustained inactivity time t1 (eg, 2 minutes, <infinity) in the SN1 Add message.

[0106] Step 403: Due to radio measurements, the original SN1 cannot provide service and needs to change to a new SN2. The MN releases the SN1. Because the MN does not know the UE's persistent inactivity time in the SN1, the SN1 needs to convey the UE's persistent inactivity time in the SN1, t2 (e.g., 3 minutes, < infinity), in the release request message interaction.

[0107] Step 404: Since the bearer does not move to the MN and then to the SN2, but moves directly from the SN1 to the SN2, the MN conveys the UE's persistent inactivity time t2 in the SN1 in the new SN2 addition process, and the SN2 sets an updated inactivity timer (T3-t2). If T3 is less than or equal to t2, the timer is not started, and the SN2 immediately notifies the MN that the Session or Flow is in the user inactive state. If T3 is greater than t2, the timer is started, and the time is (T3-t2).

[0108] Step 405: If the UE is always in an inactive state, after the (T3-t2) timer times out, send an SN active notification to the MN, carrying a UE Inactive state indication.

[0109] Step 406: When the UE state is reversed, the SN immediately sends an active notification to the MN, carrying a UE re-activated state indication. The subsequent steps are similar to those in the previous embodiment, and therefore will not be described in detail here.

[0110] In a second aspect, an embodiment of the present disclosure provides an electronic device, as shown in FIG. 12 , comprising: at least one processor 501; a memory 502 having stored therein at least one computer program, the memory 502 causing the at least one processor to implement the resource management method described in the first aspect above, when the at least one computer program is executed by the at least one processor; and at least one I / O interface 503 connected between the processor and the memory and configured to enable information interaction between the processor and the memory.

[0111] The processor 501 is a device having data processing capabilities, and includes, but is not limited to, a central processing unit (CPU). The memory 502 is a device having data storage capabilities, and includes, but is not limited to, random access memory (RAM, more specifically, SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH). The I / O interface (read / write interface) 503 is connected between the processor 501 and the memory 502 and is configured to enable information interaction between the processor 501 and the memory 502, and includes, but is not limited to, a data bus (Bus).

[0112] In some embodiments, the processor 501, memory 502, and I / O interface 503 are connected to each other and to other components of the computing device via a bus 504.

[0113] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium, as shown in FIG. 13, storing a computer program that, when executed by a processor, causes the resource management method described in the first aspect above to be implemented.

[0114] The UE-InactiveTime transmission method for NR-DC dual connection proposed in the embodiments of the present disclosure transmits the UE's persistent inactive time between the source bearer node and the target bearer node when the Session or Flow flow has no data, synchronizes the UE's idle time length between the source bearer node and the target bearer node, realizes timely release of UE resources, optimizes radio resource management, saves valuable system resources, and significantly reduces the power consumption of terminals and system equipment. Those skilled in the art will understand that all or some of the steps of the methods disclosed above and the functional modules / units in the equipment can be implemented as software, firmware, hardware, or an appropriate combination thereof.

[0115] In hardware embodiments, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components. For example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processor, digital signal processor, or microprocessor, or may be implemented as hardware, or as an integrated circuit, such as a dedicated integrated circuit. Such software may be located on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and that can be accessed by a computer. Additionally, those skilled in the art will know that communication media generally include computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and can include any information delivery media.

[0116] Although some embodiments of the present disclosure have been described above with reference to the drawings, they are not intended to limit the scope of the present disclosure. Any modifications, equivalent replacements, and improvements made within the scope and essence of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. determining whether a remaining inactivity time of a user equipment (UE) for a target bearer node has expired; and releasing resources allocated to the UE when a remaining inactivity time of the UE with respect to the target bearer node expires, The remaining inactivity time includes a sum of preset inactivity times corresponding to the target bearer node minus a sum of persistent inactivity times generated by the UE in all nodes; When the current node is a target secondary node (SN), the source bearer node of the UE's service is a master node (MN), and the target bearer node is the target SN, the resource management method comprises: receiving a message from the MN before the remaining inactivity time of the UE towards the target bearer node expires, the message conveying a persistent inactivity time of the UE at a source bearer node; obtaining a remaining inactivity time of the UE to the target bearer node based on a sum of preset inactivity times at the target SN minus a persistent inactivity time of the UE at a source bearer node; sending an SN activity notification message to the MN, carrying an inactivity indication of the UE, when the target SN detects that the remaining inactivity time of the UE towards the target bearer node has expired; If service data for the UE appears before resources allocated to the UE are released after sending an SN activity notification message to the MN, carrying an inactivity indication for the UE, resetting the remaining inactivity time to zero and setting the total time of the preset inactivity time as the remaining inactivity time for the UE with respect to the target bearer node; sending an SN activity notification message to the MN, the SN activity notification message carrying a reactivation indication for the UE. Resource management methods.

2. If the current node is the MN, the source bearer node of the UE's service is the MN, and the target bearer node is the target SN, the resource management method comprises: determining a sustained inactivity time that the UE has experienced with a source bearer node before the UE's remaining inactivity time with respect to the target bearer node expires; and sending a message to the target SN, carrying a persistent inactivity time of the UE at the source bearer node, so that the target SN determines a remaining inactivity time of the UE with respect to the target bearer node based on the persistent inactivity time of the UE at the source bearer node. The resource management method of claim 1 .

3. The step of sending a message carrying a persistent inactivity time of the UE at the source bearer node to the target SN includes: sending an SN addition request message to the target SN, the message carrying a persistent inactivity time of the UE at a source bearer node; The resource management method according to claim 2 .

4. The step of sending a message carrying a persistent inactivity time of the UE at the source bearer node to the target SN includes: sending an SN change request message to the target SN, the SN change request message carrying a persistent inactivity time of the UE at a source bearer node. The resource management method according to claim 2 .

5. When the current node is the MN, the source bearer node of the UE service is the target SN, and the target bearer node is the MN, the resource management method comprises: receiving a message from the target SN before the remaining inactivity time of the UE towards the target bearer node expires, the message conveying a persistent inactivity time of the UE at a source bearer node; and obtaining a remaining inactivity time of the UE with respect to the target bearer node based on a sum of preset inactivity times at the MN minus the persistent inactivity time at the source bearer node. The resource management method of claim 1 .

6. The step of receiving from the target SN a message carrying a persistent inactivity time of the UE at a source bearer node comprises: receiving an SN change request message from the target SN, the SN change request message carrying a persistent inactivity time for the UE at a source bearer node; The resource management method according to claim 5 .

7. The step of receiving from the target SN a message carrying a persistent inactivity time of the UE at a source bearer node comprises: receiving an SN release request message from the target SN, the SN release request message carrying a persistent inactivity time of the UE at a source bearer node; The resource management method according to claim 5 .

8. The step of determining whether the UE's remaining inactivity time towards a target bearer node has expired comprises: If the service of the UE is currently being bearered by the MN, the MN detects whether the remaining inactivity time of the UE with respect to the target bearer node has expired. The resource management method according to claim 2 .

9. The step of determining whether the UE's remaining inactivity time towards a target bearer node has expired comprises: If the UE's service is currently being bearered by the target SN, when the MN receives an SN Activity Notification message carrying an inactivity indication for the UE, it determines that the UE's remaining inactivity time with respect to the target bearer node has expired. The resource management method according to claim 2 .

10. and canceling the release decision made for the UE upon receiving an SN activity notification message from the target SN, the SN activity notification message carrying a reactivation instruction for the UE, before releasing the resources allocated to the UE. The resource management method of claim 9.

11. The step of receiving from the MN a message carrying a persistent inactivity time of the UE at a source bearer node, receiving an SN addition request message from the MN, the SN addition request message carrying a persistent inactivity time of the UE at a source bearer node; The resource management method of claim 1 .

12. The step of receiving from the MN a message carrying a persistent inactivity time of the UE at a source bearer node, receiving an SN change request message from the MN, the SN change request message carrying a persistent inactivity time for the UE at a source bearer node; The resource management method of claim 1 .

13. If a current node is the target SN, a source bearer node of the UE's service is the target SN, and the target bearer node is the MN, the resource management method comprises: determining a sustained inactivity time that the UE has experienced with a source bearer node before the UE's remaining inactivity time with respect to the target bearer node expires; and sending a message to the MN, carrying a persistent inactivity time of the UE at the source bearer node, so that the MN determines a remaining inactivity time of the UE with respect to the target bearer node based on the persistent inactivity time of the UE at the source bearer node. The resource management method of claim 1 .

14. The step of sending a message to the MN carrying a persistent inactivity time of the UE at a source bearer node comprises: sending an SN change request message to the MN, the SN change request message carrying a persistent inactivity time of the UE at a source bearer node. The resource management method of claim 13.

15. The step of sending a message to the MN carrying a persistent inactivity time of the UE at a source bearer node comprises: sending an SN release request message to the MN, the SN release request message carrying a persistent inactivity time of the UE at a source bearer node. The resource management method of claim 13.

16. The method of claim 15, further comprising: determining whether a remaining inactivity time of a user equipment (UE) with respect to a target bearer node has expired; and releasing resources allocated to the UE when a remaining inactivity time of the UE with respect to the target bearer node expires, The remaining inactivity time includes a sum of preset inactivity times corresponding to the target bearer node minus a sum of persistent inactivity times generated by the UE in all nodes; If the current node is a target secondary node (SN), the source bearer node of the service of the UE is the target SN, and the target bearer node is a master node (MN), the resource management method comprises: determining a sustained inactivity time that the UE has experienced with a source bearer node before the UE's remaining inactivity time with respect to the target bearer node expires; and sending a message to the MN, carrying a persistent inactivity time of the UE at the source bearer node, so that the MN determines a remaining inactivity time of the UE with respect to the target bearer node based on the persistent inactivity time of the UE at the source bearer node. Resource management methods.

17. at least one processor; a memory having stored therein at least one computer program, the at least one computer program being configured to cause the at least one processor to implement the resource management method of any one of claims 1 to 16 when executed by the at least one processor; at least one I / O interface coupled between the processor and the memory and configured to enable information interaction between the processor and the memory; electronic equipment.

18. A computer program is stored which, when executed by a processor, implements the resource management method according to any one of claims 1 to 16. A computer-readable storage medium.

Images