A resource management method, system and related devices

Abstract

The application discloses a resource management method, system and related equipment, and relates to the technical field of communication. The method is applied to a user equipment (UE), and comprises the following steps: the UE receives a configuration parameter sent by a base station, the configuration parameter being used for configuring a timer of the UE; then the UE initiates a small packet data transmission (SDT) session, starts the timer, and the timer is used for controlling the state of the SDT session; and when the timer expires, the UE releases resources occupied by the SDT session. The method can reduce resource waste.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a resource management method, system, terminal and base station BACKGROUND

[0002] In the fifth generation mobile communication (5th Generation Mobile Networks Or 5th Generation Wireless Systems, 5G) also known as New Radio (New Radio, NR) system, the above-mentioned inactive (INACTIVE) state is introduced at the radio resource control (radio resource control, RRC) level. The user equipment (User Equipment, UE) in the inactive (INACTIVE) state needs to be restored to the connected (CONNECTED) state before data transmission, for example, sending data to the network side.

[0003] In some examples, based on the small data transmission (small data transmisison, SDT) technology, the UE can send data to the network side in the inactive state by initiating an SDT session, thereby improving the transmission efficiency of data.

[0004] The SDT session needs to occupy configuration resources, and when the UE completes the SDT session, how to release the resources occupied by the SDT session is a problem that the industry focuses on. SUMMARY

[0005] The present application provides a resource management method, system, terminal and base station, which reduces the waste of resources.

[0006] To achieve the above-mentioned purpose, the present application adopts the following technical scheme:

[0007] In a first aspect, the present application provides a resource management method, which is applied to a UE, and the method comprises:

[0008] The UE receives a configuration parameter sent by a base station, the configuration parameter being used to configure a timer of the UE, then the UE initiates a small data transmission (SDT) session and starts the timer, the timer being used to control the state of the SDT session, for example, to control whether to continue the SDT session or to terminate the SDT session, and when the timer expires, the UE releases the resources occupied by the SDT session.

[0009] In the method, the configuration parameter of the timer at the UE side is provided by the network side (e.g., the base station as described above), which can be a preset configuration parameter, a configuration parameter confirmed after negotiation between the UE and the network side, or the like. Since the configuration parameter of the timer at the UE side is provided by the network side, the network side can know whether the UE has terminated the SDT session. After the network side knows that the UE has terminated the SDT session, the network side can release the resources configured for the SDT session without further interaction with the UE, thereby reducing the waste of resources.

[0010] The type of the base station is different, and the way of sending the configuration parameter to the UE is different.

[0011] In some possible implementation manners, the base station can be an anchor base station, and the anchor base station can send the configuration parameter to the UE through a radio resource control release message. The UE can receive the configuration parameter sent by the anchor base station through the radio resource control release message.

[0012] In some possible implementation manners, the base station can be a serving base station, and the serving base station can send the configuration parameter to the UE through a broadcast message. The UE can receive the configuration parameter sent by the serving base station through the broadcast message.

[0013] In some possible implementation manners, the UE can send a radio resource control resume request message and small packet data to the base station to initiate an SDT session.

[0014] Then, the UE can start the timer when starting to send the radio resource control resume request message; or,

[0015] The UE can also start the timer when completing to send the radio resource control resume request message; or,

[0016] The UE can start the timer when completing to send the radio resource control resume request message.

[0017] In some possible implementation manners, after the timer is started and before the timer is timed out, the method further includes: when the UE receives a radio resource control release message, a radio resource control resume message, a radio resource control setup message, or a radio resource control reject message, the UE terminates the timer.

[0018] In some possible implementation manners, after the timer is started and before the timer is timed out, the method further includes:

[0019] The UE restarts the timer when a preset condition is met.

[0020] In some possible implementation manners, the timer can be a session failure timer, and the UE can restart the session failure timer when sending the small packet data; or,

[0021] The UE can also restart the session failure timer upon receiving the small packet data; or the UE can also restart the session failure timer upon receiving the configuration of the dynamic scheduling resource.

[0022] In some possible implementation manners, the timer can also be a configured resource timer, the configured resource timer being used to control the state of the SDT session by controlling the remaining time during which the UE can use the configured resource again after using the configured resource, the configured resource timer being restarted upon the UE transmitting the small packet data using the configured resource.

[0023] In some possible implementation manners, the timer is a session failure timer, and the method further includes: entering, by the UE, an idle state or an inactive state when the session failure timer expires.

[0024] In some possible implementation manners, the method further includes:

[0025] The UE receives a control identifier sent by the base station, the control identifier being used to control the UE to enter an idle state or an inactive state when the session failure timer expires.

[0026] The UE enters the idle state or the inactive state, including:

[0027] The UE enters the idle state or the inactive state according to the control identifier sent by the base station.

[0028] In some possible implementation manners, the timer is a configured resource timer, the configured resource timer being used to control the state of the SDT session by controlling the remaining time during which the UE can use the configured resource again after using the configured resource, and the method further includes:

[0029] If the UE has uplink data to be transmitted or has not received feedback of correct data reception sent by the network, the UE triggers a process of reacquiring the configured resource; or

[0030] If the UE does not have uplink data to be transmitted, the UE terminates the configured resource timer.

[0031] In some possible implementation manners, the timer is a retransmission timer, the retransmission timer being used to control the time during which data (for example, the small packet data) can be retransmitted, and the method further includes:

[0032] If the UE has not received feedback of correct data reception sent by the network, the UE triggers a process of reacquiring the configured resource.

[0033] In some possible implementation manners, the timer is a retransmission timer, the retransmission timer is used to control a time during which the SDT session can perform retransmission, and the method further includes:

[0034] When the number of retransmissions of the UE exceeds a preset number, the UE triggers any one of a procedure of reacquiring a configuration resource, terminating the retransmission timer, or releasing a resource occupied by the SDT session.

[0035] In some possible implementation manners, the timer is a timing advance timer, the timing advance timer is used to control a state of the SDT session by controlling a remaining time during which the UE can use the configuration resource before using the configuration resource, and the method further includes:

[0036] The UE measures a single-sideband reference signal received power.

[0037] If the single-sideband reference signal received power is greater than or equal to a preset threshold value and the timing advance timer has not expired, the UE transmits uplink data by using the configuration resource.

[0038] If the single-sideband reference signal received power is less than the preset threshold value or the timing advance timer has expired, the UE triggers a procedure of reacquiring the configuration resource.

[0039] In a second aspect, a resource management method is provided, the method being applied to a serving base station, and the method includes:

[0040] The serving base station sends a configuration parameter to a UE, the configuration parameter being used to configure a timer of the UE.

[0041] The serving base station starts a protection timer of the serving base station according to an SDT session initiated by the UE, a timing time of the protection timer of the serving base station being greater than or equal to a timing time of the timer of the UE.

[0042] When the protection timer expires, the serving base station requests to release a resource occupied by the SDT session.

[0043] In some possible implementation manners, the serving base station sends a configuration parameter to a UE, including:

[0044] The serving base station sends the configuration parameter to the UE by using a broadcast message.

[0045] In some possible implementation manners, the serving base station starts a protection timer of the serving base station according to an SDT session initiated by the UE, including:

[0046] The service base station starts a guard timer of the service base station when receiving the radio resource control resume request message and the small packet data sent by the UE.

[0047] In some possible implementation manners, the method further includes:

[0048] restarting the guard timer when the service base station receives the small packet data; and / or,

[0049] restarting the guard timer when the service base station schedules the small packet data.

[0050] In some possible implementation manners, after the guard timer is started, before the guard timer expires, the method further includes:

[0051] The service base station sends a resume UE context request message to an anchor base station of the UE, and the resume UE context request message carries configuration parameters of the timer of the UE.

[0052] The service base station receives a resume UE context response message sent by the anchor base station, and the resume UE context response message carries part of the context of the UE.

[0053] The service base station requests to release resources occupied by the SDT session, including:

[0054] The service base station requests to release the resources occupied by the SDT session by sending a UE context release message to the anchor base station.

[0055] In some possible implementation manners, after the guard timer is started, before the guard timer expires, the method further includes:

[0056] The service base station sends a resume UE context request message to an anchor base station of the UE.

[0057] The service base station receives a resume UE context response message sent by the anchor base station, and the resume UE context response message carries all the context of the UE.

[0058] The service base station requests to release resources occupied by the SDT session, including:

[0059] The service base station requests to release the resources occupied by the SDT session by sending a UE context release message to the core network.

[0060] In some possible implementation manners, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer or a timing advance timer.

[0061] In a third aspect, the present application provides a resource management method, which is applied to an anchor base station, and the method comprises the following steps:

[0062] The anchor base station sends configuration parameters to the UE, and the configuration parameters are used for configuring a timer of the UE;

[0063] The anchor base station starts a protection timer of the anchor base station according to a recovery UE context request message sent by a serving base station, and the timing time of the protection timer of the anchor base station is greater than or equal to the timing time of the timer of the UE;

[0064] When the protection timer expires, the anchor base station triggers to release resources occupied by the SDT session.

[0065] In some possible implementation manners, the anchor base station sends the configuration parameters to the UE, and the configuration parameters comprise the following information:

[0066] The anchor base station sends the configuration parameters through a radio resource control release message.

[0067] In some possible implementation manners, the anchor base station triggers to release the resources occupied by the SDT session, and the triggering comprises the following steps:

[0068] The anchor base station triggers to release the resources occupied by the SDT session by sending a UE context release message to a core network.

[0069] In some possible implementation manners, the anchor base station triggers to release the resources occupied by the SDT session, and the triggering comprises the following steps:

[0070] The anchor base station triggers to release the resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0071] In some possible implementation manners, the timer of the UE comprises a session failure timer, a configured grant timer, a retransmission timer or a timing advance timer.

[0072] In a fourth aspect, the present application provides a resource management method, which is applied to an anchor base station, and the method comprises the following steps:

[0073] The anchor base station receives a recovery UE context request message sent by a serving base station, and the recovery UE context request message carries configuration parameters of a timer of a UE, wherein the configuration parameters of the timer of the UE are configured by the serving base station;

[0074] The anchor base station starts a protection timer of the anchor base station according to the recovery UE context request message, and the timing time of the protection timer of the anchor base station is greater than or equal to the timing time of the timer of the UE;

[0075] The anchor base station triggers release of resources occupied by the SDT session when the guard timer expires.

[0076] In some possible implementation ways, the configuration parameter of the timer of the UE is configured by the serving base station through a broadcast message.

[0077] In some possible implementation ways, the anchor base station triggers release of resources occupied by the SDT session, including:

[0078] The anchor base station triggers release of resources occupied by the SDT session by sending a UE context release message to a core network.

[0079] In some possible implementation ways, the anchor base station triggers release of resources occupied by the SDT session, including:

[0080] The anchor base station triggers release of resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0081] In some possible implementation ways, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer or a timing advance timer.

[0082] In a fifth aspect, the present application provides a resource management system, including a UE and a base station;

[0083] The base station is configured to send a configuration parameter to the UE.

[0084] The UE is configured to configure a timer of the UE according to the configuration parameter, initiate an SDT session and start the timer, and release resources occupied by the SDT session when the timer expires, wherein the timer is used to control a state of the SDT session.

[0085] In some possible implementation ways, the base station is a serving base station.

[0086] The serving base station is configured to send a configuration parameter to the UE through a broadcast message.

[0087] In some possible implementation ways, the base station is an anchor base station.

[0088] The anchor base station is configured to send a configuration parameter to the UE through an RRCRelease message.

[0089] In some possible implementation manners, the UE is configured to send a radio resource control resume request message and small packet data to the base station to initiate the SDT session, and start the timer when the UE starts sending the radio resource control resume request message, or when the UE finishes sending the radio resource control resume request message, or when the UE finishes sending a radio resource control resume request repetition message.

[0090] In some possible implementation manners, the UE is configured to terminate the timer when the UE receives a radio resource control release message, a radio resource control resume message, a radio resource control setup message or a radio resource control reject message before the timer expires after the timer is started.

[0091] In some possible implementation manners, the UE is configured to restart the timer when a preset condition is met before the timer expires after the timer is started.

[0092] In some possible implementation manners, the timer is a session failure timer, and the UE is configured to restart the session failure timer when the UE sends small packet data, or when the UE receives small packet data, or when the UE receives a configuration of a dynamically scheduled resource.

[0093] In some possible implementation manners, the timer is a session failure timer, and the UE is configured to restart the session failure timer when the UE receives small packet data, or when the UE receives a configuration of a dynamically scheduled resource.

[0094] In some possible implementation manners, the timer is a session failure timer, and the UE is configured to restart the session failure timer when the UE receives a configuration of a dynamically scheduled resource.

[0095] In some possible implementation manners, the timer is a configured resource timer, and the configured resource timer is configured to control a state of the SDT session by controlling a remaining time during which the UE can use a configured resource again after using the configured resource, and the UE is configured to restart the configured resource timer when the UE uses the configured resource to send small packet data.

[0096] In some possible implementation manners, the timer is a session failure timer, and the UE is configured to enter an idle state or an inactive state when the session failure timer expires.

[0097] In some possible implementation manners, the UE is configured to receive a control identifier sent by a base station, and the control identifier is configured to control the UE to enter an idle state or an inactive state when the session failure timer expires, and the UE is configured to enter the idle state or the inactive state according to the control identifier sent by the base station.

[0098] In some possible implementation manners, the timer is a configured resource timer, and when the configured resource timer expires, the UE is configured to trigger a procedure of reacquiring a configured resource if there is uplink data to be transmitted or if no feedback of correct data reception sent by the network is received; or, if there is no uplink data to be transmitted, the configured resource timer is terminated.

[0099] In some possible implementation manners, the timer is a retransmission timer, and the retransmission timer is used to control a time during which data can be retransmitted, and when the retransmission timer expires, the UE is configured to trigger a procedure of reacquiring a configured resource if no feedback of correct data reception sent by the network is received.

[0100] In some possible implementation manners, the timer is a retransmission timer, and the retransmission timer is used to control a time during which an SDT session can be retransmitted, and when the retransmission timer starts and before the retransmission timer expires, the UE is configured to trigger any one of the following: a procedure of reacquiring a configured resource, terminating the retransmission timer, or releasing resources occupied by the SDT session, if a retransmission number exceeds a preset number.

[0101] In some possible implementation manners, the timer is a timing advance timer, and the timing advance timer is used to control a state of an SDT session by controlling a remaining time during which the UE can use a configured resource before using the configured resource, and the UE is configured to measure a single sideband reference signal received power, use the configured resource to transmit uplink data if the single sideband reference signal received power is greater than or equal to a preset threshold value and the timing advance timer has not expired, and trigger a procedure of reacquiring a configured resource if the single sideband reference signal received power is less than the preset threshold value or the timing advance timer has expired.

[0102] In a sixth aspect, the present application provides a resource management system, a UE and a serving base station;

[0103] The serving base station is configured to send a configuration parameter to the UE.

[0104] The UE is configured to configure a timer of the UE according to the configuration parameter, initiate an SDT session and start the timer.

[0105] The serving base station is configured to start a protection timer of the serving base station according to the SDT session initiated by the UE, and request to release resources occupied by the SDT session when the protection timer expires, and a timing time of the protection timer is greater than or equal to a timing time of the timer of the UE.

[0106] In some possible implementation manners, the serving base station is configured to send the configuration parameter to the UE through a broadcast message.

[0107] In some possible implementation manners, the serving base station is configured to start a guard timer of the serving base station when the serving base station receives a radio resource control resume request message and small packet data sent by the UE.

[0108] In some possible implementation manners, the serving base station is configured to restart the guard timer when the serving base station receives the small packet data, and / or restart the guard timer when the serving base station schedules the small packet data.

[0109] In some possible implementation manners, before the guard timer expires after the guard timer is started, the serving base station is configured to send a resume UE context request message to an anchor base station of the UE, the resume UE context request message carrying a configuration parameter of a timer of the UE; receive a resume UE context response message sent by the anchor base station, the resume UE context response message carrying part of a context of the UE; and request to release resources occupied by the SDT session by sending a UE context release message to the anchor base station.

[0110] In some possible implementation manners, before the guard timer expires after the guard timer is started, the serving base station is configured to send a resume UE context request message to an anchor base station of the UE; receive a resume UE context response message sent by the anchor base station, the resume UE context response message carrying all of a context of the UE; and request to release resources occupied by the SDT session by sending a UE context release message to a core network.

[0111] In a seventh aspect, the present application provides a resource management system, comprising: a UE, a serving base station, and an anchor base station.

[0112] The anchor base station is configured to send a configuration parameter to the UE.

[0113] The UE is configured to configure a timer of the UE according to the configuration parameter, initiate an SDT session, and start the timer.

[0114] The serving base station is configured to send a resume UE context request message to the anchor base station.

[0115] The anchor base station is configured to start a guard timer of the anchor base station according to the resume UE context request message, and trigger to release resources occupied by the SDT session when the guard timer expires; and a timing time of the guard timer of the anchor base station is greater than or equal to a timing time of the timer of the UE.

[0116] In some possible implementation manners, the anchor base station is configured to send the configuration parameter through a radio resource control release message.

[0117] In some possible implementation manners, the anchor base station is configured to trigger release of the resource occupied by the SDT session by sending a UE context release message to a core network.

[0118] In some possible implementation manners, the anchor base station is configured to trigger release of the resource occupied by the SDT session by sending a UE context release message to the serving base station.

[0119] In the eighth aspect, the present application provides a resource management system, comprising: a UE, a serving base station and an anchor base station.

[0120] The serving base station is configured to send a configuration parameter to the UE.

[0121] The UE is configured to configure a timer of the UE according to the configuration parameter, initiate an SDT session and start the timer.

[0122] The serving base station is configured to send a resume UE context request message to the anchor base station, wherein the resume UE context request message carries a configuration parameter of a timer of the UE.

[0123] The anchor base station is configured to start a protection timer of the anchor base station according to the resume UE context request message, and trigger release of the resource occupied by the SDT session when the protection timer expires; the timing time of the protection timer of the anchor base station is greater than or equal to the timing time of the timer of the UE.

[0124] In some possible implementation manners, the serving base station is configured to send the configuration parameter to the UE through a broadcast message.

[0125] In some possible implementation manners, the anchor base station is configured to trigger release of the resource occupied by the SDT session by sending a UE context release message to a core network.

[0126] In some possible implementation manners, the anchor base station is configured to trigger release of the resource occupied by the SDT session by sending a UE context release message to the serving base station.

[0127] In the ninth aspect, the present application provides a user equipment, comprising: a communication module and a processing module.

[0128] The communication module is configured to receive a configuration parameter sent by a base station, wherein the configuration parameter is used to configure a timer of the UE, and is further configured to initiate an SDT session.

[0129] The processing module is configured to start the timer, and the timer is configured to control the state of the SDT session; and the processing module is further configured to release resources occupied by the SDT session when the timer expires.

[0130] In some possible implementation manners, the communication module is configured to receive the configuration parameter sent by the anchor base station through a radio resource control release message.

[0131] In some possible implementation manners, the communication module is configured to receive the configuration parameter sent by the serving base station through a broadcast message.

[0132] In some possible implementation manners, the communication module is configured to send a radio resource control resume request message and small packet data to the base station to initiate an SDT session.

[0133] In some possible implementation manners, the communication module is configured to receive a radio resource control release message, a radio resource control resume message, a radio resource control setup message, or a radio resource control reject message.

[0134] The processing module is configured to terminate the timer when the UE receives a radio resource control release message, a radio resource control resume message, a radio resource control setup message, or a radio resource control reject message.

[0135] In some possible implementation manners, the processing module is configured to restart the timer when a preset condition is met before the timer expires after the timer is started.

[0136] In some possible implementation manners, the processing module, the timer is a session failure timer, and the processing module is configured to restart the session failure timer when the UE sends small packet data, or restart the session failure timer when the UE receives small packet data, or restart the session failure timer when the UE receives configuration of a dynamically scheduled resource.

[0137] In some possible implementation manners, the timer is a configured resource timer, the configured resource timer is configured to control the state of the SDT session by controlling a remaining time during which the UE can use a configured resource again after using the configured resource, and the processing module is configured to restart the configured resource timer when the UE uses the configured resource to send small packet data.

[0138] In some possible implementation manners, the timer is a session failure timer, and the processing module is configured to control the UE to enter an idle state or an inactive state when the session failure timer expires.

[0139] In some possible implementation manners, the communication module is configured to receive a control identifier sent by the base station, and the control identifier is used to control the UE to enter an idle state or an inactive state when the session failure timer expires.

[0140] The processing module is configured to control the UE to enter the idle state or the inactive state according to the control identifier sent by the base station when the session failure timer expires.

[0141] In some possible implementation manners, the timer is a configured resource timer, and the processing module is configured to trigger a procedure of reacquiring a configured resource when the UE has uplink data to be transmitted or does not receive feedback of correct data reception sent by the network when the configured resource timer expires; or, terminate the configured resource timer when the UE does not have uplink data to be transmitted.

[0142] In some possible implementation manners, the retransmission timer is used to control a time during which data can be retransmitted, and the processing module is configured to trigger a procedure of reacquiring a configured resource when the UE does not receive feedback of correct data reception sent by the network when the retransmission timer expires.

[0143] In some possible implementation manners, the timer is a retransmission timer, the retransmission timer is used to control a time during which an SDT session can be retransmitted, and the processing module is configured to trigger a procedure of reacquiring a configured resource, terminate the retransmission timer, or release resources occupied by the SDT session when a retransmission number of the UE exceeds a preset number before the retransmission timer expires after the retransmission timer is started.

[0144] In some possible implementation manners, the timer is a timing advance timer, the timing advance timer is used to control a state of an SDT session by controlling a remaining time during which the UE can use a configured resource before using the configured resource, and the processing module is configured to measure a single sideband reference signal received power, use the configured resource to transmit uplink data when the single sideband reference signal received power is greater than or equal to a preset threshold value and the timing advance timer does not expire, and trigger a procedure of reacquiring a configured resource when the single sideband reference signal received power is less than the preset threshold value or the timing advance timer expires.

[0145] In a tenth aspect, the present application provides a serving base station, including a communication module and a processing module.

[0146] The communication module is configured to send a configuration parameter to a UE, and the configuration parameter is used to configure a timer of the UE.

[0147] The processing module is configured to start a guard timer of the serving base station according to the SDT session initiated by the UE, wherein the guard timer of the serving base station has a timing time greater than or equal to a timing time of the timer of the UE; and the serving base station is configured to request to release resources occupied by the SDT session when the guard timer expires.

[0148] In some possible implementation manners, the communication module is configured to send the configuration parameters to the UE through a broadcast message.

[0149] In some possible implementation manners, the communication module is configured to receive the radio resource control resume request message and the small packet data sent by the UE; and the processing module is configured to start the guard timer of the serving base station when the radio resource control resume request message and the small packet data sent by the UE are received.

[0150] In some possible implementation manners, the processing module is configured to restart the guard timer when the small packet data is received; and / or restart the guard timer when the small packet data is scheduled.

[0151] In some possible implementation manners, before the guard timer expires after being started, the communication module is configured to send a resume UE context request message to an anchor base station of the UE, wherein the resume UE context request message carries configuration parameters of the timer of the UE; receive a resume UE context response message sent by the anchor base station, wherein the resume UE context response message carries part of a context of the UE; and send a UE context release message to the anchor base station to request to release resources occupied by the SDT session.

[0152] In some possible implementation manners, before the guard timer expires after being started, the communication module is configured to send a resume UE context request message to an anchor base station of the UE; receive a resume UE context response message sent by the anchor base station, wherein the resume UE context response message carries all contexts of the UE; and send a UE context release message to a core network to request to release resources occupied by the SDT session.

[0153] In some possible implementation manners, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer or a timing advance timer.

[0154] In a first aspect, the present application provides a serving base station, comprising a communication module and a processing module.

[0155] The communication module is configured to send configuration parameters to the UE, the configuration parameters being used to configure a timer of the UE; and to receive a resume UE context request message sent by a serving base station;

[0156] The processing module is configured to start a protection timer of the anchor base station according to the resume UE context request message sent by the serving base station, the timing time of the protection timer of the anchor base station being greater than or equal to the timing time of the timer of the UE; and to trigger the anchor base station to release resources occupied by the SDT session when the protection timer expires.

[0157] In some possible implementation manners, the communication module is configured to send the configuration parameters through a radio resource control release message.

[0158] In some possible implementation manners, the communication module is configured to trigger the release of the resources occupied by the SDT session by sending a UE context release message to a core network.

[0159] In some possible implementation manners, the communication module is configured to trigger the release of the resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0160] In some possible implementation manners, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer, or a timing advance timer.

[0161] In a twelfth aspect, the present application provides an anchor base station, comprising: a communication module and a processing module.

[0162] The communication module is configured to receive a resume UE context request message sent by a serving base station, the resume UE context request message carrying configuration parameters of a timer of a UE, the configuration parameters of the timer of the UE being configured by the serving base station.

[0163] The processing module is configured to start a protection timer of the anchor base station according to the resume UE context request message, the timing time of the protection timer of the anchor base station being greater than or equal to the timing time of the timer of the UE, and to trigger the anchor base station to release resources occupied by the SDT session when the protection timer expires.

[0164] In some possible implementation manners, the configuration parameters of the timer of the UE are configured by the serving base station through a broadcast message.

[0165] In some possible implementation manners, the communication module is configured to trigger the release of the resources occupied by the SDT session by sending a UE context release message to a core network.

[0166] In some possible implementation manners, the communication module is configured to trigger release of resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0167] In some possible implementation manners, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer, or a timing advance timer.

[0168] In a thirteenth aspect, the present application provides an electronic device, including a memory and a processor;

[0169] The memory stores one or more computer programs including instructions, and when the instructions are executed by the processor, the electronic device performs the method according to any one of the first aspect.

[0170] In a fourteenth aspect, the present application provides a base station, including a memory and a processor;

[0171] The memory stores one or more computer programs including instructions, and when the instructions are executed by the processor, the base station performs the method according to any one of the second aspect, the third aspect, or the fourth aspect.

[0172] In a fifteenth aspect, the present application provides a computer storage medium, including computer instructions, and when the computer instructions are run on a computing device, the computing device performs the method according to any one of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0173] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in the present application does not imply that all features and advantages can be achieved in any single embodiment. On the contrary, it can be understood that the description of a feature or a beneficial effect means that the specific technical feature, technical solution or beneficial effect is included in at least one embodiment. Therefore, the description of technical features, technical solutions or beneficial effects in the specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in the embodiments can be combined in any appropriate manner. Those skilled in the art will understand that the embodiments can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects can be identified in specific embodiments that do not embody all embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0174] Figure 1 A communication network architecture diagram is provided for the embodiments of the present application;

[0175] Figure 2 A structural schematic diagram of a user equipment provided for an embodiment of the present application;

[0176] Figure 3 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0177] Figure 4 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0178] Figure 5 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0179] Figure 6 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0180] Figure 7 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0181] Figure 8 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0182] Figure 9 An interactive process schematic diagram of a UE requesting to resume RRC connection provided for an embodiment of the present application;

[0183] Figure 10 A structural schematic diagram of a user equipment provided for an embodiment of the present application;

[0184] Figure 11 A structural schematic diagram of a serving base station provided for an embodiment of the present application;

[0185] Figure 12 A structural schematic diagram of an anchor base station provided for an embodiment of the present application;

[0186] Figure 13 A structural schematic diagram of an anchor base station provided for an embodiment of the present application;

[0187] Figure 14 A schematic diagram of an electronic device provided for an embodiment of the present application;

[0188] Figure 15 A schematic diagram of a base station provided for an embodiment of the present application. DETAILED DESCRIPTION

[0189] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B; "and / or" in this document only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0190] Hereinafter, the terms "first" and "second" are only for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more of the features. In the description of the embodiments, unless otherwise specified, the meaning of "multiple" is two or more than two.

[0191] The embodiments of the present application can be applied to but not limited to the following communication systems: narrowband Internet of things (NB-IoT) system, wireless local area network (WLAN) system, long term evolution (LTE) system, 5th generation mobile communication (5G) also known as new radio (NR) system, or communication system after 5G, such as 6G system, device to device (D2D) communication system, Internet of vehicles, etc.

[0192] Please refer to Figure 1 , Figure 1 A communication network architecture diagram provided by the embodiments of the present application is shown. Among them, Figure 1The interaction relationship between network functions and entities and the corresponding interfaces are demonstrated by taking the network service architecture of a 5G system as an example. The 3rd Generation Partnership Project (3GPP) Service-Based Architecture (SBA) of the 5G system includes network functions and entities such as User Equipment (UE), Access Network (AN) or Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Policy Control Function (PCF), Application Function (AF), Network Slice Selection Function (NSSF), Unified Data Management (UDM), Network Exposure Function (NEF), and Network Repository Function (NRF).

[0193] Among them, the UE, AN / RAN, UPF, and DN are generally referred to as user plane network functions and entities (or user plane network elements), and the other parts are generally referred to as control plane network functions and entities (or control plane network elements). The control plane network element is defined by 3GPP as a processing function in a network, and has a 3GPP-defined function behavior and a 3GPP-defined interface. The network function can be a network element running on a dedicated hardware, or a software instance running on a dedicated hardware, or a virtual function instantiated on a suitable platform, such as a cloud infrastructure.

[0194] The main functions of each network element are described below.

[0195] AN / RAN: AN / RAN can be various forms of base stations, such as: macro base stations, micro base stations (also known as "small stations"), distribute unit-control unit (DU-CU), and the like. In addition, the above base stations can also be wireless controllers in a cloud radio access network (CRAN) scenario, or relay stations, access points, vehicle-mounted devices, wearable devices, or network devices in a future evolved public land mobile network (PLMN) network, and the like. AN / RAN can also be a broadband network gateway (BNG), a convergence switch, a non-3GPP access device, and the like. AN / RAN is mainly responsible for functions such as radio resource management on the air interface side, uplink and downlink data classification, quality of service (QoS) management, data compression and encryption, signaling processing with control plane network elements, or data forwarding with user plane function network elements, and the like. The specific form and structure of the AN / RAN are not limited in the embodiments of the present application. For example, in systems using different wireless access technologies, the names of devices with base station functions may be different. For example, the base station can be an evolved universal terrestrial radio access network (E-UTRAN) device in LTE, such as an evolutional node B (eNB or e-NodeB), or a next generation radio access network (NG-RAN) device (such as a gNB) in a 5G system, and the like.

[0196] UPF: mainly responsible for packet routing and forwarding, and QoS processing or charging information statistics of user plane data. The transmission resources and scheduling functions provided for the UE in the UPF are managed and controlled by the SMF.

[0197] DN: DN is a network used for transmitting data. For example: DN can be an operator service network, an Internet access, or a third-party service network, and the like.

[0198] AMF: mainly responsible for processing of control plane messages, such as: access control, mobility management, lawful interception, access authentication / authorization, etc. Specifically, the functions of AMF mainly include: 1) processing of access network control plane; 2) processing of NAS messages, responsible for NAS encryption protection and integrity protection; 3) registration management; 4) connection management; 5) access management; 6) mobility management; 7) lawful interception of information; 8) providing session management messages between UE and SMF; 9) implementing transparent transmission of routing session management (SM) messages, similar to a transparent proxy; 10) access authentication; 11) access authorization; 12) forwarding SMS messages (short messages) between UE and short message service function SMSF; 13) interacting with AUSF and UE to obtain UE authentication intermediate key; 14) calculating access network specific keys.

[0199] SMF: mainly used for session management, UE network interconnection protocol (Internet Protocol, IP) address allocation and management, selection of manageable user plane functions, terminal point of policy control and charging function interface, downlink data notification, etc.

[0200] PCF: mainly used to provide UE policy rules, AM policy rules and SM policy rules related parameters to UE, AMF or SMF respectively, manage user subscription information, access UDM to access subscription user information related to policy decision, etc.

[0201] NRF: mainly used to provide internal / external addressing functions, receive query requests of other network elements to certain network elements and return information of related network elements, etc.

[0202] AUSF: mainly responsible for network security, used to generate keys, implement bidirectional authentication for UEs, and support a unified authentication framework.

[0203] AF: used to provide services, mainly used for: 1) application influence on service routing; 2) access to network capability exposure; 3) interact with policy framework for policy control.

[0204] NSSF: mainly used for selection and management of network slice instances (Network Slice Instance, NSI), determining the mapping of allowed network slice information and used network slice information, and determining the mapping of configured network slice information and subscribed network slice information.

[0205] NEF: is an interface network element for bidirectional interaction of information between network internal and external entities, and is also a logical unit for internal information distribution and aggregation, mainly including three capabilities: monitoring capability, supply capability, and policy / charging capability.

[0206] UDM: consists of two parts, one part is called application front end (FE), and the other part is called user data warehouse (UDR).

[0207] Wherein, the to-be-transmitted data can be transmitted through a PDU session (i.e. a communication bearer described in the specification) established between the UE and the DN, the transmission will pass through two network function entities of (R)AN and UPF, the UE and the (R)AN communicate with each other by using a certain air interface technology, N1 is an interface between the UE and the AMF, N2 is an interface between the (R)AN and the AMF, N3 is an interface between the (R)AN and the UPF, N4 is an interface between the SMF and the UPF, N6 is an interface between the UPF and the DN; Namf is a service-based interface exhibited by the AMF, Nsmf is a service-based interface exhibited by the SMF, Nausf is a service-based interface exhibited by the AUSF, Nnssf is a service-based interface exhibited by the NSSF, Nnef is a service-based interface exhibited by the NEF, Nnrf is a service-based interface exhibited by the NRF, Npcf is a service-based interface exhibited by the PCF, Nudm is a service-based interface exhibited by the UDM, and Naf is a service-based interface exhibited by the AF.

[0208] For the functions of the UPF, the DN, the AUSF, the NSSF, the NEF, the NRF and the UDM, etc., reference can be made to the explanations and descriptions in the conventional technologies, and no further description is given here.

[0209] For the convenience of understanding, the following briefly introduces several terms involved in the present application.

[0210] 1. Connected (CONNECTED) state: also referred to as connected state. The connected state refers to that a radio resource control (RRC) connection has been established, and is also referred to as RRC_CONNECTED. When the UE is in the connected state, the connection between the UE and the access network (such as a base station) and the core network (such as an access management function (AMF) unit) is established, and if there is data to be transmitted, the data can be directly transmitted through the established connection. The RRC connection is used to process the control plane messages between the UE and the access network.

[0211] 2. Inactive (INACTIVE) state: also referred to as deactivated state (RRC_INACTIVE) or third state. The inactive state refers to that the RRC connection between the UE and the access network (such as a base station) has been disconnected, but the connection between the access network (such as a base station) and the core network (such as an AMF) of the UE has not been disconnected. When the UE is in the deactivated state, if there is data to be transmitted, the RRC connection between the UE and the access network (such as a base station) needs to be restored before the data transmission can be performed.

[0212] When the UE enters the INACTIVE state, the RRC context of the UE is suspended (e.g., saved) at the terminal and the base station side, for example, in the last cell camped by the UE before entering the INACTIVE state, or the last cell providing service to the UE (also referred to as the anchor cell). When there is a data transmission requirement, the UE can obtain the RRC context of the UE by initiating an RRC resume request (e.g., RRCResumeRequest) to resume the RRC connection according to the RRC context. In some examples, the UE can also initiate the RRC resume request when there is a signaling transmission requirement. The RRC context of the UE, such as the security context of the UE, UE capability information, etc.

[0213] 3. IDLE state: also referred to as RRC_IDLE. The IDLE state refers to that the RRC connection between the UE and the access network (e.g., base station) is not established, and the connection between the access network (e.g., base station) of the UE and the core network (e.g., AMF) is not established. When the UE is in the IDLE state, if there is data to be transmitted, the connection between the UE and the access network (e.g., base station) and the connection between the access network (e.g., base station) of the UE and the core network (e.g., AMF) need to be established first, and then the data transmission can be performed.

[0214] 4. Serving base station: the base station to which the cell currently camped by the UE belongs, or the base station currently providing service to the UE.

[0215] 5. Anchor base station: the base station to which the last cell camped by the UE before entering the INACTIVE state belongs, or the base station last providing service to the UE.

[0216] The terms "system" and "network" used in the embodiments of the present application can be used interchangeably.

[0217] In the embodiments of the present application, the terms "base station (BS)", "wireless base station", "eNB", "gNB", "cell", "sector", "cell group", "carrier", and "component carrier" can be used interchangeably. The base station is also sometimes referred to as a fixed station, a NodeB, an eNodeB (eNB), an access point, a transmission point, a reception point, a cell, a pico cell, a femto cell, a small cell, and the like. The base station can accommodate one or more (for example, three) cells (also referred to as sectors). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, each of which can also be provided with communication services by a base station subsystem (for example, an indoor small base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to a part or the entirety of the coverage area of the base station and / or the base station subsystem that provides communication services in the coverage.

[0218] In the embodiments of the present application, the terms "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" can be used interchangeably. The mobile station is also sometimes referred to by those skilled in the art as a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or a number of other appropriate terms.

[0219] Furthermore, the wireless base station in the embodiments of the present application can also be replaced with a user terminal. For example, for a structure in which the communication between the wireless base station and the user terminal is replaced with Device-to-Device (D2D) communication between a plurality of user terminals, the modes / embodiments of the present disclosure can also be applied. At this time, the functions possessed by the wireless base station can be regarded as the functions possessed by the user terminal. Furthermore, the words "uplink" and "downlink" and the like can be replaced with "side". For example, the uplink channel can be replaced with a side channel. Likewise, the user terminal in the embodiments of the present application can also be replaced with a wireless base station. At this time, the functions possessed by the user terminal described above can be regarded as the functions possessed by the wireless base station.

[0220] In the embodiments of the present application, the UE can be a desktop device, a laptop device, a handheld device, a wearable device, a smart home device, a computing device, a vehicle-mounted device, and the like with a wireless connection function. For example, a netbook, a tablet computer, a smart watch, a personal computer (PC), an ultra-mobile personal computer (UMPC), a smart camera, a netbook, a personal digital assistant (PDA), a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Portable Multimedia Player (PMP), an Augmented Reality (AR) / Virtual Reality (VR) device, a wireless device on an aircraft, a wireless device on a robot, a wireless device in industrial control, a wireless device in telemedicine, a wireless device in a smart grid, a wireless device in a smart city, a wireless device in a smart home, and the like. The specific type and structure of the UE are not limited in the embodiments of the present application.

[0221] Please refer to Figure 2 , Figure 2 A schematic diagram of a hardware structure of a UE is shown. As Figure 2 indicated, in some embodiments, the structure of the UE can be as Figure 2As shown, the UE can include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headset jack 270D, a sensor module 280, a key 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. The sensor module 280 can include a pressure sensor 280A, a gyroscope sensor 280B, a barometric pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0222] It can be understood that the structure shown in the embodiment does not constitute a specific limitation on the UE. In other embodiments, the UE can include more or fewer components than shown, or combine certain components, or split certain components, or different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0223] The processor 210 can include one or more processing units, for example: the processor 210 can include an application processor (AP), a Modem, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated in one or more processors.

[0224] The charging management module 240 is configured to receive a charging input from a charger. The charger can be a wireless charger or a wired charger.

[0225] The power management module 241 is configured to connect the battery 242 and the charging management module 240 to the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240 to power the processor 210, the internal memory 221, the display screen 294, the camera 293, and the wireless communication module 260.

[0226] The wireless communication function of the UE can be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem, and the baseband processor.

[0227] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the UE can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.

[0228] The mobile communication module 250 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the UE.

[0229] The wireless communication module 260 can provide a solution for wireless communication including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc. applied to the UE. The wireless communication module 260 can be one or more devices integrated with at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 260 can also receive signals to be sent from the processor 210, perform frequency modulation, amplification, and convert the signals to electromagnetic wave radiation via the antenna 2.

[0230] In the embodiments of the present application, the wireless communication module 260 can be used for the UE to send a request for resuming an RRC connection to a network node, and receive a response message from the network node.

[0231] The UE can realize the display function by the GPU, the display screen 294, and the application processor. The GPU is a microprocessor for image processing, connected to the display screen 294 and the application processor.

[0232] The display 294 is configured to display images, videos, and the like. A series of graphical user interfaces (GUIs) can be displayed on the display 294 of the UE.

[0233] The UE can implement a photographing function through the ISP, the camera 293, the video codec, the GPU, the display 294, and the application processor, and the like.

[0234] The camera 293 is configured to capture still images or videos.

[0235] The external memory interface 220 can be configured to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the UE.

[0236] The internal memory 221 can be configured to store computer-executable program codes including instructions. The processor 210 performs various functional applications and data processing of the UE by running the instructions stored in the internal memory 221.

[0237] The UE can implement an audio function through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the earphone interface 270D, the application processor, and the like. For example, music playing, voice recording, and the like. The UE can further include a pressure sensor 280A, an air pressure sensor 280C, a gyroscope sensor 280B, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, an ambient light sensor 280L, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, a bone conduction sensor 280M, a key 290, a motor 291, an indicator 292, and the like.

[0238] The SIM card interface 295 is configured to connect a SIM card. The SIM card can be inserted into or pulled out of the SIM card interface 295 to achieve contact and separation with the UE. The UE can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support a Nano SIM card, a Micro SIM card, a SIM card, and the like. The same SIM card interface 295 can simultaneously insert multiple cards. The SIM card interface 295 can also be compatible with external memory cards. The UE interacts with the network through the SIM card to implement functions such as calling and data communication.

[0239] In addition, an operating system, such as an iOS operating system, an Android operating system, a Windows operating system, and the like, is run on the above-mentioned components. Application programs can be installed and run on the operating system. In some embodiments, the operating system running in the UE can be multiple.

[0240] It should be understood that Figure 2 The hardware modules included in the UE are described only by way of example and do not limit the specific structure of the UE. In fact, the UE provided by the embodiments of the present application can also include other hardware modules that have an interaction relationship with the hardware modules shown in the figure, which are not specifically limited here. For example, the UE can also include a flashlight, a micro projection device, etc. For another example, if the UE is a PC, the UE can also include a keyboard, a mouse, etc.

[0241] In 5G NR, the above-mentioned inactive (INACTIVE) state is introduced at the RRC layer, and the UE in the inactive (INACTIVE) state needs to be restored to the connected (CONNECTED) state before data transmission, and the following will be introduced in combination with Figure 3 .

[0242] Taking the recovery of the radio resource control (RRC) connection process in 5G NR as an example, the UE in the inactive (INACTIVE) state requests the network side device to recover the RRC connection to enter the connected (CONNECTED) state for data transmission. Figure 3 An interaction process diagram for the UE to request the recovery of the RRC connection provided by the embodiments of the present application is shown in FIG. 1. As shown in FIG. 1, the UE can send a radio resource control recovery request message (such as an RRCResumeRequset message) to the current serving base station (such as a Serving-gNB) at S301. The UE can request the RRC context of the UE through the RRCResumeRequset message. In order to ensure that the RRCResumeRequset message is correctly identified at the network side device, the information carried in the RRCResumeRequset message includes a resume identity (i.e., a request identity), a resume message integrity authentication code (Message Authentication Code for Integrity, MAC-I) (or shortResumeMAC-I, hereinafter referred to as MAC-I), and a resume cause (i.e., a request reason). Figure 3

[0243] Among them, the resume identity is used for the network side device to identify the RRC context. For example, the resume identity can be an inactive radio network temporary identifier (Inactive Radio Network Temporary Identifier, I-RNTI).

[0244] ​In some cases, a reserved bit is also included in the RRCResumeRequset message. The I-RNTI can include a Short I-RNTI and a Full I-RNTI. The I-RNTI can be configured to the UE by a network side device (e.g., an anchor base station) in an RRCRelease message, or can be indicated by a network side device (e.g., a serving base station) in a broadcast message, such as a System Information Block (SIB) 1 message, through useFullResumeID. For example, if the SIB 1 message includes useFullResumeID, then the Full I-RNTI is used; if the SIB 1 message does not include useFullResumeID, then the Short I-RNTI is used. Illustratively, the Full I-RNTI is 40 bits, and the Short I-RNTI is 24 bits. Illustratively, the Full I-RNTI can be composed of a UE ID, a gNB ID, and a Public Land Mobile Network (PLMN).

[0245] The MAC-I is used for message legitimacy verification and message integrity verification by the network side device. Illustratively, the MAC-I can be calculated by the UE according to a security algorithm and an integrity protection algorithm. Illustratively, the MAC-I can be 16 bits. As an example, the UE can calculate the MAC-I based on the following parameters: KRRCint, KEY, BEARER, DIRECTION, COUNT, and MESSAGE. KRRCint is an integrity protection key. KEY can be set to the value of KRRCint. MESSAGE can be set to VarResumeMAC-Input, which can be calculated based on the following parameters: a source physical cell identification (PCI), a target cell-ID, and a source cell-Radio Network Temporary Identity (C-RNTI).

[0246] As a possible implementation, the UE can send the RRCResumeRequset message to the current serving base station (e.g., Serving-gNB) through a signaling radio bearer (SRB), such as SRB0. Further, if the serving base station (e.g., Serving-gNB) is not the anchor base station (e.g., Anchor-gNB) of the UE, the serving base station (e.g., Serving-gNB) determines the anchor base station (e.g., Anchor-gNB) of the UE according to the Resume Identity carried in the RRCResumeRequset message, and requests the RRC context of the UE from the anchor base station (e.g., Anchor-gNB) of the UE. For example, Figure 3 As shown in S302, the serving base station (e.g., Serving-gNB) sends a retrieve UE context request message (Retrieve UE CONTEXT REQUEST message) to the anchor base station (e.g., Anchor-gNB) of the UE, for requesting the RRC context of the UE. The Retrieve UE CONTEXT REQUEST message carries the target cell ID (cell-ID) and the Resume Identity, MAC-I, and Resume Cause from the UE.

[0247] The serving base station (e.g., Serving-gNB) can determine the anchor base station of the UE through the Resume Identity when the anchor base station of the UE is different from the serving base station according to the Resume Identity carried in the RRCResumeRequset message.

[0248] Further, after receiving the Retrieve UE CONTEXT REQUEST message from the serving base station (e.g., Serving-gNB), the anchor base station (e.g., Anchor-gNB) verifies the MAC-I to perform message legitimacy verification and message integrity verification. If the anchor base station (e.g., Anchor-gNB) passes the legitimacy and message integrity verification of the Retrieve UE CONTEXT REQUEST message, the anchor base station (e.g., Anchor-gNB) sends a retrieve UE context response message (e.g., Retrieve UE CONTEXT RESPONSE message) to the serving base station (e.g., Serving-gNB). For example, Figure 3 As shown in S303, the anchor base station (e.g., Anchor-gNB) sends the retrieve UE context response message (e.g., Retrieve UE CONTEXT RESPONSE message) to the serving base station (e.g., Serving-gNB). The Retrieve UE CONTEXT RESPONSE message carries the RRC context of the UE.

[0249] Further, as shown in S304, the serving base station (e.g., Serving-gNB) sends the RRCResume message to the UE through the SRB, such as SRB1. The RRCResume message carries the RRC context of the UE. Figure 3As shown in S304, the serving base station (such as the Serving-gNB) sends a Radio Resource Control (RRC) recovery message (such as an RRC Resume message) to the UE. For example, after obtaining the UE's RRC context, the serving base station sends an RRC Resume message to the UE to restore the UE's RRC connection (CONNECTED) state. Figure 3 As shown in S305, after receiving the RRC Resume message, the UE resumes the connected state. In S306, the UE sends a Radio Resource Control (RRC) recovery completion message (e.g., an RRC Resume Complete message) to the serving base station (e.g., the Serving-gNB) to notify it that the UE has resumed the connected state. Furthermore, after confirming that the UE has resumed the connected state, the serving base station (e.g., the Serving-gNB) can continue with subsequent workflows. For example, in S307, the serving base station can provide an interface address indication (Xn-U address indication) to the anchor base station; in S308, the core network can switch downlink routes according to the serving base station's request; and in S309, the serving base station sends a UE context release message (e.g., a UEContext Release message) to the anchor base station. After receiving the UE Context Release message, the anchor base station can release the UE's RRC context; and in S310, the UE performs data transmission, etc.

[0250] It can be seen that the above Figure 3 The process of a UE requesting to restore an RRC connection, as shown, requires frequent transmission of small data packets, resulting in excessive signaling overhead. In some examples, small data transmission (SDT) technology can be used to allow the UE to directly transmit data in an inactive state. The data transmission process based on SDT differs in different scenarios (e.g., anchor base station migration and anchor base station non-migration scenarios), which will be described below.

[0251] Anchor base station migration scenario:

[0252] like Figure 4 As shown in the figure, this figure is a schematic diagram of the interaction process of data transmission based on SDT in an anchor base station migration scenario provided by an embodiment of this application.

[0253] The interaction process includes:

[0254] S401, the UE sends a radio resource control recovery request message and the data to be transmitted to the serving base station.

[0255] For example, the UE can send an RRCResumeRequset message to the current serving base station (e.g., Serving-gNB) and data to be transmitted. The UE can initiate an SDT session in an INACTIVE state and send the RRCResumeRequset message and the data to the current serving base station. Further, if the serving base station is not the anchor base station (e.g., Anchor-gNB) of the UE, the serving base station can determine the anchor base station of the UE according to the Resume Identity carried in the RRCResumeRequset message and request the RRC context of the UE from the anchor base station of the UE.

[0256] S402, the serving base station sends a resume UE context request message (e.g., Retrieve UE CONTEXT REQUEST message) to the anchor base station of the UE.

[0257] The serving base station can send the Retrieve UE CONTEXT REQUEST message to the anchor base station of the UE to request the RRC context of the UE. The SDT session indicator (Indicator) can be carried in the Retrieve UE CONTEXT REQUEST message to inform the anchor base station that the current session is an SDT session.

[0258] S403, the anchor base station sends a resume UE context response message (e.g., Retrieve UE CONTEXT RESPONSE message) to the serving base station.

[0259] The anchor base station can also verify the legitimacy and message integrity of the Retrieve UE CONTEXT REQUEST message. If the verification is passed, the anchor base station can send the Retrieve UE CONTEXT RESPONSE message to the serving base station. The RRC context of the UE is carried in the Retrieve UE CONTEXT RESPONSE message. In this way, the RRC context of the UE is migrated from the anchor base station to the serving base station.

[0260] S404, the serving base station performs interface address indication (Xn-U address indication) to the anchor base station.

[0261] S405, the core network switches the downlink route according to the request of the serving base station.

[0262] S406, the serving base station transmits the received data (e.g., data sent by the UE) to the core network.

[0263] S407. The serving base station sends a UE context release message (such as a UE Context Release message) to the anchor base station.

[0264] After receiving the UE Context Release message, the anchor base station can release the UE's RRC context.

[0265] S408 and UE transmit data.

[0266] S409. The serving base station can send a radio resource control release message (such as an RRRCRelease message) to the UE.

[0267] The RRRCRelease message can carry a suspend configuration (SuspendConfig), thereby terminating the SDT session initiated by the UE. In some examples, the serving base station can configure the UE to be inactive or idle via SuspendConfig.

[0268] Anchor base station non-migration scenario:

[0269] like Figure 5 As shown in the figure, this is a schematic diagram of the interaction process of data transmission based on SDT in a non-migration scenario of an anchor base station according to an embodiment of this application. The difference from the anchor base station migration scenario is that the anchor base station does not need to send the entire RRC context of the UE to the serving base station.

[0270] The interaction process includes:

[0271] S501, the UE sends a radio resource control recovery request message and the data to be transmitted to the serving base station.

[0272] For example, a UE can send an RRRCResumeRequest message to the current serving base station (such as Serving-gNB) along with the data to be transmitted.

[0273] S502, The serving base station sends a UE context recovery request message (such as a Retrieve UECONTEXT REQUEST message) to the UE's anchor base station.

[0274] The Retrieve UE CONTEXT REQUEST message carries an SDT session indicator.

[0275] S503, the anchor base station sends a Retrieve UE CONTEXTRESPONSE message to the serving base station.

[0276] S504, the serving base station transmits the received data (e.g., data sent by the UE) to the anchor base station.

[0277] S505, the UE performs data transmission.

[0278] S506, the anchor base station can send a radio resource control release message (e.g., RRCRelease message) to the UE.

[0279] The RRCRelease message can carry a suspend configuration (SuspendConfig), thereby terminating the SDT session initiated by the UE. In some examples, the anchor base station can configure the UE to be in an inactive (INACTIVE) state or an idle (IDLE) state through the SuspendConfig.

[0280] In the anchor base station migration scenario, the serving base station can terminate the SDT session initiated by the UE and release the resources configured for the SDT session by sending an RRCRelease message to the UE; in the anchor base station non-migration scenario, the anchor base station can terminate the SDT session initiated by the UE and release the resources configured for the SDT session by sending an RRCRelease message to the UE. The above two ways of terminating the SDT session can be referred to as explicit ways, and the SDT session can also be terminated in an implicit way, for example, by setting a timer on the UE side to control the termination of the SDT session through the timer mechanism.

[0281] The UE terminates the SDT session in an implicit way, and the network side (e.g., the serving base station or the anchor base station) needs to ensure synchronization of the state with the UE. When the state of the SDT session is inconsistent between the UE side and the network side, resource waste can occur. For example, if the UE has terminated the SDT session in an implicit way, the network side will continue to reserve the resources configured for the SDT session, which will be wasted. Further, when the network side and the UE RRC state are out of synchronization, the network side sends an RRCRelease message to the UE to terminate the SDT session or schedules data to the UE, while the UE has terminated the SDT session beforehand, which can result in the resources used by the network side to send the RRCRelease message to the UE being wasted and the data scheduling failing.

[0282] Therefore, the resource management method provided in the embodiments of the present application is provided. In the method, a timer can be set at the UE side. The configuration parameter of the timer can be provided to the UE by the network side (for example, a serving base station or an anchor base station), can be a preset configuration parameter, or can be a configuration parameter confirmed after negotiation between the UE and the network side. The UE can configure the timer based on the configuration parameter, and the UE can control the SDT session (for example, terminate the SDT session) based on the configured timer. Since the configuration parameter of the timer of the UE is provided by the network side, or is a preset configuration parameter, or is a configuration parameter obtained after negotiation, the network side can know whether the UE has terminated the SDT session. After the network side knows that the UE has terminated the SDT session, the network side can release the resources configured for the SDT session, thereby reducing the waste of resources. Further, the network side does not need to send the RRCRelease message to the UE again to instruct the UE to terminate the SDT session, thereby further reducing the waste of resources.

[0283] The timer set at the UE side includes multiple types, which are introduced below.

[0284] Example 1

[0285] In example 1, the timer set at the UE side can be a session failure timer (SDT failure timer), which is referred to as T-SDT for brevity in the following description.

[0286] The network side can send the configuration parameter of the T-SDT to the UE. In some examples, the network side can carry the configuration parameter of the T-SDT in an RRCRelease message. The RRCRelease message carries a suspend configuration (SuspendConfig), and the SuspendConfig can carry the configuration parameter of the T-SDT. In other examples, the configuration parameter of the T-SDT can also be carried in other messages.

[0287] As an example, the configuration parameter carried by the SuspendConfig is as follows:

[0288] SuspendConfig::=SEQUENCE

[0289] {

[0290] T-SDT SDT-Failure-TimerValue

[0291] }

[0292] Wherein, "T-SDT" represents a timer for session failure timer, and "SDT-Failure-TimerValue" can be a configuration parameter of the T-SDT, which represents a timing time of the T-SDT.

[0293] Of course, the configuration parameter of the T-SDT can also be a preset configuration parameter, for example, a pre-set configuration parameter; and the configuration parameter of the T-SDT can also be a configuration parameter confirmed after negotiation between the UE and the network side, for example, a configuration parameter confirmed after negotiation between the UE and the serving base station.

[0294] It should be noted that the manner in which the UE obtains the configuration parameter of the T-SDT is not specifically limited in the embodiments of the present application, and can be selected by those skilled in the art according to actual needs.

[0295] After the UE obtains the configuration parameter of the T-SDT, the UE can configure the T-SDT based on the configuration parameter of the T-SDT.

[0296] Then, when the UE initiates an SDT session, the T-SDT can be started. As described above, the UE initiates an SDT session when the UE sends an RRCResumeRequset message and data to be transmitted to the network side. In some examples, the time at which the UE starts the T-SDT can be the time at which the UE sends the first symbol of the RRCResumeRequset message, or the time at which the UE sends the last symbol of the RRCResumeRequset message, or the time at which the UE sends the end of the RRCResumeReques Repetition message. In other examples, the time at which the UE starts the T-SDT can be the time at which the UE starts to send the data to be transmitted, or the time at which the UE completes sending the data to be transmitted.

[0297] It should be noted that the time at which the UE starts the T-SDT is only an exemplary description, and those skilled in the art can set the time at which the UE starts the T-SDT according to actual needs.

[0298] When the T-SDT is started, the T-SDT starts counting, for example, from 0 second. During the SDT session, the UE can receive a dynamic scheduling resource from the network side, and when the UE receives the dynamic scheduling resource from the network side, the UE can restart the T-SDT, that is, the T-SDT restarts counting, for example, from 0 second again. The dynamic scheduling resource includes but is not limited to a scheduling resource scrambled by a C-RNTI, a scheduling resource scrambled by a Configured Scheduling Radio Network Temporary Identifier (CS-RNTI), and a scheduling resource scrambled by an I-RNTI. The scheduling resource can include a scheduling resource for initial transmission and a scheduling resource for retransmission. The scheduling resource for initial transmission can be a scheduling resource for transmitting new data, and the scheduling resource for retransmission can be a scheduling resource for transmitting retransmission data.

[0299] After the UE obtains the dynamic scheduling resource allocated by the network side, the UE can perform data transmission based on the dynamic scheduling resource. In some examples, the UE restarts the T-SDT when the UE transmits uplink data. The UE transmitting uplink data can mean that the UE transmits uplink data to a serving base station, an anchor base station, a core network, and the like. In other examples, the UE restarts the T-SDT when the UE receives downlink data. The UE receiving downlink data can mean that the UE receives downlink data transmitted by a serving base station, an anchor base station, a core network, and the like.

[0300] It should be noted that the above is only an exemplary introduction of the UE restarting the T-SDT. In other embodiments, the UE can restart the T-SDT after performing any operation related to the SDT session.

[0301] In some embodiments, the UE terminates the SDT session when the T-SDT times out. In another embodiment, the UE can not restart the T-SDT after starting the T-SDT, but terminates the SDT session when the T-SDT times out.

[0302] Further, after the T-SDT times out, the UE can also reset the configuration information of a Media Access Control (MAC), for example, flush a Hybrid Automatic Repeat reQuest (HARQ) buffer. For example, the UE can clear the data stored in the HARQ buffer. The UE can also notify an upper layer that the SDT session fails and the reason for the SDT session failure (for example, the T-SDT times out). The upper layer can be a Non Access Stratum (NAS) or an Access Stratum (AS).

[0303] In some embodiments, after T-SDT expires, the UE can enter INACTIVE state or IDLE state. For example, the network side can carry a control identifier in the RRCRelease message, which can be used to indicate whether the UE is allowed to enter INACTIVE state or IDLE state after T-SDT expires. When the UE enters INACTIVE state, the security key will be derived based on the horizontal derivation method to derive a new security key when the UE initiates SDT traffic again.

[0304] In some embodiments, during the SDT session, when the UE receives an RRCRelease message, an RRCResume message, an RRC setup message (such as an RRCSetup message), or an RRC reject message (such as an RRCReject message), the UE can terminate T-SDT, i.e., stop timing.

[0305] Example two:

[0306] In example two, the timer set by the UE side can be a configured resource timer (SDT configured grant), which will be referred to as T-SDT-CG for convenience in the following description. The configured resource (Configured Grant) can be used by the UE to transmit uplink data in INACTIVE state. The configured resource timer is used to control the state of the SDT session by controlling the remaining time when the UE can use the configured resource again after using the configured resource.

[0307] The network side can send the configuration parameters of the T-SDT-CG to the UE. In some examples, the network side can carry the configuration parameters of the T-SDT-CG in the RRCRelease message. The RRCRelease message carries a suspend configuration (SuspendConfig), and the SuspendConfig can carry the configuration parameters of the T-SDT-CG. In other examples, the configuration parameters of the T-SDT-CG can also be carried in other messages.

[0308] As an example, the pseudo code for carrying the configuration parameters through SuspendConfig is as follows:

[0309] SuspendConfig::=SEQUENCE

[0310] {

[0311] T-SDT-CG SDT-configured grant-TimerValue

[0312] }

[0313] Wherein, "T-SDT-CG" represents that the configuration resource timer is a timer, and "SDT-configured grant-TimerValue" can be a configuration parameter of the T-SDT-CG described above, which represents the timing time of the T-SDT-CG.

[0314] Of course, the configuration parameter of the T-SDT-CG can also be a preset configuration parameter, for example, a pre-set configuration parameter; and the configuration parameter of the T-SDT-CG can also be a configuration parameter confirmed after negotiation between the UE and the network side, for example, a configuration parameter confirmed after negotiation between the UE and the serving base station.

[0315] It should be noted that the embodiments of the present application do not specifically limit the way in which the UE obtains the configuration parameter of the T-SDT-CG described above, and those skilled in the art can select according to actual needs.

[0316] After the UE obtains the configuration parameter of the T-SDT-CG described above, the UE can configure the T-SDT-CG based on the configuration parameter of the T-SDT-CG.

[0317] Then, when the UE initiates an SDT session, the T-SDT-CG can be started. As described above, the UE initiates an SDT session when the UE sends an RRCResumeRequset message and data to be transmitted to the network side. In some examples, the time when the UE starts the T-SDT-CG can be the time when the UE sends the first symbol of the RRCResumeRequset message, or the time when the UE sends the last symbol of the RRCResumeRequset message, or the time after the UE sends the RRCResumeReques Repetition message. In other examples, the time when the UE starts the T-SDT-CG can be the time when the UE starts to send the data to be transmitted, or the time when the UE completes the sending of the data to be transmitted.

[0318] It should be noted that the time when the UE starts the T-SDT-CG described above is only an exemplary introduction, and those skilled in the art can set the time when the UE starts the T-SDT-CG according to actual needs.

[0319] When the T-SDT-CG is started, the T-SDT-CG starts counting, for example, counting from 0 second. During the SDT session, the UE can send uplink data based on the configured grant (CG) provided by the network side. In some examples, when the UE sends uplink data, the UE restarts the T-SDT-CG, wherein the UE sending uplink data can be the UE sending uplink data to the serving base station, the anchor base station, the core network, and the like.

[0320] It should be noted that the above is only an exemplary introduction of the UE restarting the T-SDT-CG. In another embodiment, the UE can restart the T-SDT-CG after performing any operation related to the SDT session.

[0321] During the SDT session, if the time when the UE sends initial transmission data (such as new uplink data) based on the configured grant coincides with the time when the initial transmission resource is dynamically scheduled, the UE can use the dynamically scheduled initial transmission resource to send the initial transmission data; if the time when the UE sends retransmission data (such as uplink data that fails to be sent) based on the configured grant coincides with the time when the initial transmission resource is dynamically scheduled, the UE can use the dynamically scheduled initial transmission resource to send the retransmission data; if the time when the UE sends retransmission data (such as uplink data that fails to be sent) based on the configured grant coincides with the time when the retransmission resource is dynamically scheduled, the UE can use the dynamically scheduled retransmission resource to send the retransmission data.

[0322] In some embodiments, after the T-SDT-CG on the UE side times out, the UE terminates the SDT session. In another embodiment, after the UE starts the T-SDT-CG, the UE can no longer restart the T-SDT-CG, but instead terminates the SDT session after the T-SDT times out.

[0323] Further, after the T-SDT-CG on the UE side times out, the UE can also reset the configuration information of the media access control (MAC), for example, flush the hybrid automatic repeat request (HARQ) buffer (such as the HARQ buffer). For example, empty the error data packets stored in the HARQ buffer. The UE can also notify the upper layer that the SDT session fails and the reason for the SDT session failure (for example, it can be that the T-SDT-CG on the UE side times out).

[0324] After the T-SDT-CG timer expires at the UE side, if the UE still has data to be transmitted, which can be new data to be transmitted, uplink retransmission data (e.g., data to be retransmitted), or no feedback (e.g., feedback indicating that the network side correctly receives the data) received from the network side for the data transmitted by the UE, the UE can trigger a RACH-SDT procedure, i.e., the UE triggers a RACH procedure to reacquire a configuration resource for transmitting uplink data, and then transmits subsequent data based on the reacquired configuration resource. If the UE has no data to be transmitted, the UE can directly release the configuration resource.

[0325] In some embodiments, the network side can also set a T-SDT-CG. After the network side receives uplink data transmitted by the UE based on the configuration resource, the network side can start the T-SDT-CG to synchronize the configuration state of the configuration resource. After the T-SDT-CG timer expires at the network side, the network side can release or suspend the configuration resource. Then, the network side can activate the configuration resource again based on a request from the UE. For example, the network side can use a control information (Downlink Control Information, DCI) scrambled by a CS-RNTI, a DCI scrambled by a C-RNTI, a MAC control element (MAC Control Element, CE), or an RRCResumeRequset message to activate the configuration resource again.

[0326] In some embodiments, during an SDT session, when the UE receives an RRCRelease message, an RRCResume message, an RRC setup message (e.g., an RRCSetup message), or an RRC reject message (e.g., an RRCReject message), the UE can terminate the T-SDT-CG, i.e., stop the timer.

[0327] Example Three

[0328] In Example Three, the timer set at the UE side can be a retransmission timer (SDT Retransmission), which is referred to as T-SDT-Retr for brevity in the following description. The T-SDT-Retr controls the time for which the SDT service can be retransmitted.

[0329] The network side can send configuration parameters of the T-SDT-Retr to the UE. In some examples, the network side can carry the configuration parameters of the T-SDT-Retr in an RRCRelease message. The RRCRelease message carries a suspend configuration (SuspendConfig), and the SuspendConfig can carry the configuration parameters of the T-SDT-Retr. In other examples, the configuration parameters of the T-SDT-Retr can also be carried in other messages.

[0330] As an example, the pseudo code for carrying the configuration parameter through SuspendConfig is as follows:

[0331] SuspendConfig ::= SEQUENCE

[0332] {

[0333] T-SDT-Retr SDT-Retransmission-TimerValue

[0334] }

[0335] Wherein, “T-SDT-Retr” represents that the timer is a retransmission timer, and “SDT-Retransmission-TimerValue” can be a configuration parameter of the T-SDT-Retr, which represents the timing time of the T-SDT.

[0336] Of course, the configuration parameter of the T-SDT-Retr can also be a preset configuration parameter, for example, a pre-set configuration parameter; the configuration parameter of the T-SDT-Retr can also be a configuration parameter confirmed after negotiation between the UE and the network side, for example, a configuration parameter confirmed after negotiation between the UE and the serving base station.

[0337] In some other embodiments, the UE can also obtain a maximum retransmission number (Max-Retransmission-Numbers, MaxRetrNum), based on which the UE can monitor the SDT session in at least two ways. The first way can be that the T-SDT-Retr times out, and the SDT session is terminated; the second way can be that the T-SDT-Retr does not time out, but the number of retransmissions has reached MaxRetrNum, and the SDT session is terminated.

[0338] It should be noted that the UE can also obtain the MaxRetrNum in a similar manner as the UE obtains the configuration parameter of the T-SDT-Retr, which will not be described herein.

[0339] It should be noted that the embodiments of the present application do not specifically limit the manner in which the UE obtains the above-mentioned MaxRetrNum and the configuration parameter of the T-SDT-Retr, and a person skilled in the art can select according to actual needs.

[0340] After the UE obtains the configuration parameter of the T-SDT-Retr, the UE can configure the T-SDT-Retr based on the configuration parameter of the T-SDT-Retr.

[0341] Then, the UE initiates the SDT session, and the T-SDT-Retr is started. As introduced above, the UE initiates the SDT session when the UE sends the RRCResumeRequset message and the data to be transmitted to the network side. In some examples, the UE starts the T-SDT-Retr at the time when the UE sends the first symbol of the RRCResumeRequset message, or at the time when the UE sends the last symbol of the RRCResumeRequset message, or at the time when the UE finishes sending the RRCResumeRequset message. In other examples, the UE starts the T-SDT-Retr at the time when the UE starts sending the data to be transmitted, or at the time when the UE finishes sending the data to be transmitted.

[0342] It should be noted that the time when the UE starts the T-SDT-Retr is only illustrative, and the person skilled in the art can set the time when the UE starts the T-SDT-Retr according to actual needs.

[0343] When the T-SDT-Retr is started, the T-SDT-Retr starts timing, for example, from 0 seconds. During the SDT session, the UE can associate a T-SDT-Retr for each HARQ process. In some examples, for a HARQ process, if the UE receives the feedback (e.g., the feedback indicating that the network side correctly receives the data) sent by the network side before the T-SDT-Retr expires, the UE stops the T-SDT-Retr corresponding to the HARQ process. In other examples, for a HARQ process, if the UE does not receive the feedback (e.g., the feedback indicating that the network side correctly receives the data) sent by the network side after the T-SDT-Retr expires, the UE terminates the SDT session.

[0344] Of course, the UE can also associate a MaxRetrNum for each HARQ process. In some examples, for a HARQ process, if the number of retransmissions reaches the MaxRetrNum, and the UE does not receive the feedback (e.g., the feedback indicating that the network side correctly receives the data) sent by the network side, the UE terminates the SDT session.

[0345] In some embodiments, the UE can trigger the procedure of reacquiring the configured resource when the T-SDT-Retr does not expire, but the number of retransmissions reaches the MaxRetrNum, and continue the SDT session through the reacquired configured resource until the T-SDT-Retr expires, or the UE can terminate the SDT session and stop the T-SDT-Retr. For example, the UE can find and use the control information of the most recent configured resource to retransmit data, or use the control information of the latest configured resource to retransmit data. The control information can be redundancy version (RV) information.

[0346] In some embodiments, during the SDT session, when the UE receives an RRCRelease message, an RRCResume message, an RRC setup message (such as an RRCSetup message), or an RRC reject message (such as an RRCReject message), the UE can terminate the T-SDT, i.e., stop the timing.

[0347] Example Four:

[0348] In Example Four, the timer set by the UE side can be a timing advance timer (SDT Timing Advance Timer), which will be referred to as SDT-TAT hereinafter for convenience of description. The SDT-TAT is used to control the validity of the configured resource provided by the network side to the UE. When the SDT-TAT expires, the configured resource provided by the network side is invalid. The configured resource can be associated with a radio bearer (RB) allowed to be used. The RB can be SRB1, SRB2, or all RBs allowed for the SDT session, or part of the RBs allowed for the SDT session. The timing advance timer is used to control the state of the SDT session by controlling the remaining time during which the UE can use the configured resource before using the configured resource.

[0349] The network side can provide the UE with a configuration resource and send the UE the configuration parameter of the SDT-TAT. In some examples, the network side can carry the configuration resource and the configuration parameter of the SDT-TAT in an RRCRelease message. The configuration resource can be valid within an area, which can be a cell, a bandwidth part (BWP) or a single side band (SSB), or multiple BWPs / SSBs. The configuration resource can also be divided into one set and multiple sets, and when the configuration resource is in multiple sets, the configuration resource can also be distributed in different BWPs / SSBs. Correspondingly, the SDT-TAT can also be divided into one set or multiple sets, corresponding to the respective controlled configuration resource.

[0350] Of course, the configuration parameter of the SDT-TAT can also be a preset configuration parameter, for example, a pre-set configuration parameter; the configuration parameter of the SDT-TAT can also be a configuration parameter confirmed after negotiation between the UE and the network side, for example, a configuration parameter confirmed after negotiation between the UE and the serving base station.

[0351] It should be noted that the embodiments of the present application do not specifically limit the way the UE obtains the configuration parameter of the SDT-TAT, and those skilled in the art can select according to actual needs.

[0352] After the UE obtains the configuration parameter of the SDT-TAT, the UE can configure the SDT-TAT based on the configuration parameter of the SDT-TAT.

[0353] The SDT-TAT can be started after the UE enters the RRC INACTIVE state. However, the present application does not limit that the SDT-TAT can only be started when the UE enters the RRC INACTIVE state.

[0354] When the SDT-TAT is started, the SDT-TAT starts timing, for example, timing from 0 seconds. In some examples, the UE can also measure the reference signal receiving power (RSRP), for example, can measure the SSB-RSRP, or can measure the BWP-RSRP. Taking the measurement of the SSB-RSRP as an example, if the signal strength of the SSB-RSRP is greater than or equal to the first threshold value configured by the network side, and the SDT-TAT has not timed out, the UE transmits data using the configured resource; if the signal strength of the SSB-RSRP is less than the first threshold value configured by the network side, although the SDT-TAT has not timed out, the UE triggers a new process (for example, RACH-SDT) to reacquire the uplink transmission resource, and then continues the SDT session; in other examples, if the SDT-TAT times out, the UE can also implicitly release the configured resource, or can suspend the configured resource.

[0355] In some examples, the SSB-RSRP can include measurement results of multiple beams. Among them, the UE can select the beam with the best signal for data transmission; if multiple beams are below the second threshold value, the UE can also trigger a process to reacquire the configured resource, and then continue the SDT session through the reacquired configured resource.

[0356] In some embodiments, the UE can measure the SSB-RSRP before each data transmission, so that the UE can select to use the current configured resource for data transmission or trigger a process to reacquire the configured resource according to the measurement results of multiple beams included in the SSB-RSRP, and then continue the SDT session through the reacquired configured resource.

[0357] Among them, the number of multiple beams can be configured by the network side, or be a preset value, and different subcarrier spacing cells can have the same number of beams or different numbers of beams.

[0358] In some embodiments, the network side can set the retransmission parameters of the data that the UE needs to transmit and the RRCResumeRequset message, and the retransmission parameters can include the number of repeated transmissions (repK), the repeated redundancy version (repK-RV), and the like. Among them, the UE can use the configured resource and the retransmission parameters to retransmit the data that fails to be transmitted.

[0359] In some embodiments, during the SDT session, the UE can measure the SSB-RSRP, if the signal strength of the multiple SSB-RSRPs measured is lower than the first threshold value configured by the network side, the UE can trigger the process of re-acquiring the configured resource based on the retransmission parameter of the configured resource, and then continue the SDT session through the re-acquired configured resource, for example, retransmit the data. Wherein, the retransmitted data can be any uplink data that needs to be retransmitted, for example, the first uplink data or subsequent uplink data.

[0360] The above introduces an example of setting a timer at the UE side, and the following introduces an example of setting a timer at the network side. For example, the timer can be set at the serving base station or at the anchor base station, which will be introduced respectively.

[0361] Example five:

[0362] In example five, the timer can be set at the serving base station, which can be a session protection timer (T-SDT-guard Timer). In order to facilitate understanding, the following will be introduced in combination with Figure 6 .

[0363] S601, the serving base station sends a broadcast message.

[0364] The serving base station can set the session failure timer (such as T-SDT) of the UE through the broadcast message. For example, the serving base station can carry the configuration parameters of T-SDT in the SIB1 message or other broadcast messages, for example, the configuration parameters of T-SDT can be the timing time of T-SDT, the timing time can be 100ms, 200ms, etc., and when the timing time is 100ms, it means that T-SDT will expire after 100ms from the start of timing.

[0365] As an example, the pseudo code for sending the configuration parameters of T-SDT through the broadcast message is as follows:

[0366] UE-TimersAndConstants::=SEQUENCE

[0367] {

[0368] T-SDT ENUMERATED{ms100,ms200,ms300,ms400,ms600,ms1000,ms1500,ms2000}

[0369] }

[0370] Among them, the network side will select a timing time from the above ENUMERATED to issue to the UE as the configuration parameter of the UE side timer. It should be noted that the timing time included in the above ENUMERATED is only an example.

[0371] The UE reads the broadcast message, and the UE can obtain the configuration parameter of the T-SDT through the broadcast message, and then the UE can configure the T-SDT based on the configuration parameter of the T-SDT.

[0372] S602, the UE sends a radio resource control recovery request message and data that needs to be transmitted to the serving base station.

[0373] The UE can initiate an SDT session by sending the RRCResumeRequset message and the data that needs to be transmitted to the serving base station. After the UE initiates the SDT session, the UE starts the T-SDT. In some examples, the time when the UE starts the T-SDT can be the time when the UE sends the first symbol of the above RRCResumeRequset message, or the time when the UE sends the last symbol of the above RRCResumeRequset message, or the time after the UE stops sending the RRCResumeReques Repetition message. In other examples, the time when the UE starts the T-SDT can be the time when the UE starts sending the above data that needs to be transmitted, or the time when the UE completes sending the above data that needs to be transmitted.

[0374] S603, the serving base station starts the T-SDT-guard Timer.

[0375] In some examples, the serving base station can start the T-SDT-guard Timer when receiving the RRCResumeRequset message and the data sent by the UE. The time when the serving base station starts the T-SDT-guard Timer can be the time when the first symbol of the above RRCResumeRequset message is received, or the time when the last symbol of the above RRCResumeRequset message is received. In other examples, the time when the serving base station starts the T-SDT-guard Timer can be the time when the data that needs to be transmitted starts to be received, or the time when the data that needs to be transmitted is completed.

[0376] It should be noted that the time when the above serving base station starts the T-SDT-guard Timer is only an example, and those skilled in the art can set the time when the serving base station starts the T-SDT-guard Timer according to actual needs.

[0377] In some examples, the timing time of the T-SDT-guard Timer of the serving base station can be greater than the timing time of the T-SDT of the UE. In other examples, the timing time of the T-SDT-guard Timer of the serving base station can be equal to the timing time of the T-SDT of the UE.

[0378] S604, the serving base station sends a Retrieve UE Context Request message (e.g., Retrieve UE CONTEXT REQUEST message) to the anchor base station of the UE.

[0379] The Retrieve UE CONTEXT REQUEST message carries an SDT session indicator and a configuration parameter of a timer (T-SDT Timer). The anchor base station can perform explicit release of the resources configured for the SDT session based on the configuration parameter of the timer.

[0380] S605, the anchor base station sends a Retrieve UE Context Response message (e.g., Retrieve UE CONTEXT RESPONSE message) to the serving base station.

[0381] The Retrieve UE CONTEXT RESPONSE message carries a partial RRC context of the UE (Partial UE Context) to continue the SDT session.

[0382] S606, the serving base station transmits the received data (e.g., data sent by the UE) to the anchor base station.

[0383] S607, the UE performs data transmission.

[0384] S608, the serving base station determines that the T-SDT-guard Timer is expired.

[0385] In some embodiments, the serving base station can restart the T-SDT-guard Timer when it receives uplink data again; the serving base station can restart the T-SDT-guard Timer when it schedules downlink data. In other embodiments, the serving base station can not restart the T-SDT-guard Timer, but terminate the SDT session and release the resources occupied by the SDT session until the T-SDT is expired. In other examples, the expiration of the T-SDT-guard Timer can mean that the T-SDT-guard Timer reaches the timing time.

[0386] S609, the serving base station sends a UE Context Release message (e.g., UE Context Release message) to the anchor base station.

[0387] In some embodiments, when the T-SDT-guard Timer expires, if the serving base station does not receive the RRCRelease message sent by the anchor base station, the serving base station sends a UE Context Release message to the anchor base station, requesting the anchor base station to release the Xn interface and the RRC context of the UE. After receiving the UE Context Release message, the anchor base station can release the Xn interface and the RRC context of the UE, and the release reason is that the T-SDT-guard Timer expires.

[0388] S610, the anchor base station sends a UE context release message (such as a UE Context Release message) to the core network.

[0389] The UE Context Release message sent by the anchor base station to the core network can be a message similar to the UE Context Release message sent by the serving base station to the anchor base station. The message can carry a cause value, such as SDT session transmission failure, SDT session termination, non-active state UE unreachable, non-active state changing to idle state, etc.

[0390] Example six:

[0391] Example six is similar to example five, except that the anchor base station transfers all RRC contexts of the UE to the serving base station. Similarly, the serving base station sets a timer, which can be a session protection timer (T-SDT-guard Timer). For ease of understanding, the following will be introduced in combination with Figure 7 .

[0392] S701, the serving base station sends a broadcast message

[0393] S702, the UE sends a radio resource control resume request message (such as a RRCResumeRequset message) and data to be transmitted to the serving base station.

[0394] S703, the serving base station starts the T-SDT-guard Timer.

[0395] S704, the serving base station sends a resume UE context request message (such as a Retrieve UE CONTEXT REQUEST message) to the anchor base station of the UE.

[0396] S705, the anchor base station sends a resume UE context response message (such as a Retrieve UE CONTEXT RESPONSE message) to the serving base station.

[0397] The Retrieve UE CONTEXT RESPONSE message carries full UE Context of the UE, and the UE anchor point is migrated from the anchor base station to the serving base station to continue the SDT session.

[0398] S706, the core network can switch downlink path according to the request of the serving base station.

[0399] S707, the serving base station transmits the received data (such as data sent by the UE) to the core network.

[0400] S708, the serving base station determines that the T-SDT-guard Timer is timed out.

[0401] S709, the serving base station sends a radio resource control release message (such as RRCRelease message) to the core network.

[0402] Example seven:

[0403] Different from example five and example six, in example seven, a timer can be set at the anchor base station, which can be a session protection timer (T-SDT-guard Timer), in order to facilitate understanding, the following will be introduced in combination with Figure 8 .

[0404] S801, the serving base station sends a broadcast message.

[0405] Similarly, the serving base station can set the session failure timer (such as T-SDT) of the UE through the broadcast message. For example, the serving base station can carry the configuration parameters of T-SDT in SIB1 message or other broadcast messages, for example, the configuration parameters of T-SDT can be the timing time of T-SDT, the timing time can be 100ms, 200ms, etc., when the timing time is 100ms, it means that the T-SDT is timed out after 100ms from the start.

[0406] As an example, the pseudo code for sending the configuration parameters of T-SDT through the broadcast message is as follows:

[0407] UE-TimersAndConstants::=SEQUENCE

[0408] {

[0409] T-SDT ENUMERATED{ms100,ms200,ms300,ms400,ms600,ms1000,ms1500,ms2000}

[0410] }

[0411] Among them, the network side will select a timing time from the above ENUMERATED and issue it to the UE as the configuration parameter of the UE side timer within a certain time. It should be noted that the timing time included in the above ENUMERATED is only an example.

[0412] The UE reads the broadcast message. The UE can obtain the configuration parameter of the T-SDT through the broadcast message, and then the UE can configure the T-SDT based on the configuration parameter of the T-SDT.

[0413] S802, the UE sends a radio resource control resume request message (such as RRCResumeRequset message) and data to be transmitted to the serving base station.

[0414] The UE can initiate an SDT session by sending the RRCResumeRequset message and the data to be transmitted to the serving base station. After the UE initiates the SDT session, the UE starts the T-SDT. In some examples, the time when the UE starts the T-SDT can be the time when the UE sends the first symbol of the above RRCResumeRequset message, or the time when the UE sends the last symbol of the above RRCResumeRequset message, or the time after the UE stops sending the RRCResumeRequset message. In other examples, the time when the UE starts the T-SDT can be the time when the UE starts sending the above data to be transmitted, or the time when the UE completes sending the above data to be transmitted.

[0415] S803, the serving base station sends a resume UE context request message (such as Retrieve UE CONTEXT REQUEST message) to the anchor base station of the UE.

[0416] After the serving base station receives the RRCResumeRequset message and the data to be transmitted sent by the UE, the serving base station can send the Retrieve UE CONTEXT REQUEST message to the anchor base station. The Retrieve UE CONTEXT REQUEST message carries an SDT session indicator (Indicator) and the configuration parameter of the UE side timer.

[0417] S804, the anchor base station starts the T-SDT-guard Timer.

[0418] After the anchor base station receives the configuration parameter of the UE-side timer, the anchor base station can configure the T-SDT-guard Timer according to the configuration parameter of the UE-side timer. In some examples, the timing time of the T-SDT-guard Timer of the anchor base station can be greater than the timing time of the T-SDT of the UE. In other examples, the timing time of the T-SDT-guard Timer of the anchor base station can be equal to the timing time of the T-SDT of the UE.

[0419] The anchor base station can start the T-SDT-guard Timer. In some examples, the anchor base station can start the T-SDT-guard Timer when receiving the Retrieve UE CONTEXT REQUEST message sent by the UE. The time when the anchor base station starts the T-SDT-guard Timer can be the time when the first symbol of the Retrieve UE CONTEXT REQUEST message is received, or can be the time when the last symbol of the Retrieve UE CONTEXT REQUEST message is received.

[0420] S805, the anchor base station sends a resume UE context response message (such as a Retrieve UE CONTEXT RESPONSE message) to the serving base station.

[0421] The Retrieve UE CONTEXT RESPONSE message carries the partial RRC context (Partial UE Context) of the UE, and continues the SDT session.

[0422] S806, the serving base station transmits the received data (such as the data sent by the UE) to the anchor base station.

[0423] S807, the anchor base station determines that the T-SDT-guard Timer is timed out.

[0424] S808, the anchor base station sends a UE context release message (such as a UE Context Release message) to the serving base station.

[0425] When the anchor base station determines that the T-SDT-guard Timer is timed out, the anchor base station can send the UE Context Release message to the serving base station to trigger the release of the Xn interface and the RRC context of the UE.

[0426] S809, the anchor base station sends a UE context release message (such as a UE Context Release message) to the core network.

[0427] The anchor base station sends a message similar to the UE Context Release message to the core network, triggering the core network to release the RRC context of the UE. In some embodiments, the PDU session list, the cause value of the release (e.g., SDT session termination, SDT session transmission failure, non-active state UE unreachable, non-active state to idle state, etc.) can be carried in the message.

[0428] Example Eight:

[0429] In Example Eight, the serving base station can set the timing advance timer (SDT-TAT) of the UE through a broadcast message. The introduction of the SDT-TAT can be referred to Example Four, which will not be repeated here.

[0430] The serving base station can configure a set of configuration parameters of the SDT-TAT, or can configure multiple sets of configuration parameters of the SDT-TAT. Each set of configuration parameters of the SDT-TAT has a corresponding third threshold value of the SSB-index-RSRP.

[0431] When the UE starts the SDT-TAT, the SDT-TAT starts timing, for example, from 0 seconds. In some examples, the UE can measure each SSB-index-RSRP, and if the SDT-TAT has not timed out, the UE can use the configuration resources provided by the serving base station to transmit data when the SSB-index-RSRP is greater than the third threshold value. In other examples, when the serving base station configures a set of configuration parameters of the SDT-TAT, if the SDT-TAT times out, the UE cannot use the configuration resource or multiple sets of configuration resources to transmit uplink data. The configuration resource or multiple sets of configuration resources will be suspended, or can be released by the UE in an implicit manner. In other examples, after the UE receives the display timing advance (TA) command, the configuration resources provided by the serving base station can be used by the UE.

[0432] In some examples, the UE can measure the SSB-RSRP before each data transmission, so that the UE can select to use the current configuration resource for data transmission or trigger the process of re-acquiring the configuration resource according to the measurement results of multiple beams included in the SSB-RSRP, and then continue the SDT session through the re-acquired configuration resource.

[0433] Wherein, the number of multiple beams can be configured by the network side or be a preset value, and the beams measured by the UE can be SSB beams on the initial BWP or beams on the dedicated BWP.

[0434] As an example, the pseudo code for sending the configuration parameters of the SDT-TAT through a broadcast message is as follows:

[0435] UE-SDT-TAT ::= SEQUENCE

[0436] {

[0437] SDT-TAT ENUMERATED{ms500, ms750, ms1280, ms1920, ms2560, ms5120, ms10240, infinity}

[0438] },

[0439] CG-SDT-SSB-RSRP-r17 ::= SEQUENCE

[0440] {

[0441] rsrp-ThresholdSDT-r17 RSRP-Range

[0442] }

[0443] Wherein, the network side will select one timing time from the above ENUMERATED and issue it to the UE as the configuration parameter of the UE side SDT-TAT; The "rsrp-ThresholdSDT-r17" represents the third threshold value.

[0444] It should be noted that the timing time included in the above ENUMERATED is only an example.

[0445] Example nine:

[0446] In example five, example six and example seven, the T-SDT of the UE can be configured by the serving base station through the broadcast message, in example nine, the timer of the UE side can be T-SDT-CG, T-SDT-Retr, SDT-TAT, which is configured by the anchor base station through the RRCRelease message, when the timer of the UE side is T-SDT-Retr, the anchor base station can also configure MaxRetrNum through the RRCRelease message, when the timer of the UE side is SDT-TAT, the anchor base station can also provide the UE with a configuration resource through the RRCRelease message. In order to facilitate understanding, the following will be introduced in combination with Figure 9 .

[0447] S901, the anchor base station sends a radio resource control release message (such as RRCRelease message) to the UE.

[0448] The anchor base station can configure the UE to enter an INACTIVE state by sending an RRCRelease message to the UE. The RRCRelease message can also carry relevant parameters, such as a flag allowing the UE to initiate an SDT session, traffic types, RBs, SRBs, resources required for the SDT session process (e.g., ConfiguratedGrant), MaxRetrNum, redundancy version type, configuration parameters of timers, etc.

[0449] After the UE receives the RRCRelease message, the UE can configure the timer based on the configuration parameters of the timer carried in the RRCRelease message, and then start the timer.

[0450] S902, the UE sends a radio resource control resume request message (such as an RRCResumeRequset message) and data to be transmitted to the serving base station.

[0451] The UE can initiate an SDT session by sending an RRCResumeRequset message and data to be transmitted to the serving base station. After the UE initiates the SDT session, the UE starts the relevant timer, such as starting T-SDT, etc.

[0452] S903, the serving base station sends a Retrieve UE CONTEXT REQUEST message to the anchor base station of the UE.

[0453] The Retrieve UE CONTEXT REQUEST message carries an SDT session indicator.

[0454] S904, the anchor base station starts a T-SDT-guard Timer.

[0455] In some examples, the timing time of the T-SDT-guard Timer of the anchor base station can be greater than the timing time of the T-SDT of the UE. In other examples, the timing time of the T-SDT-guard Timer of the anchor base station can be equal to the timing time of the T-SDT of the UE.

[0456] S905, the anchor base station sends a Retrieve UE CONTEXT RESPONSE message to the serving base station.

[0457] In some examples, the anchor base station determines not to migrate as an anchor point, the Retrieve UE CONTEXT RESPONSE message carries a Partial UE Context of the UE, and the SDT session continues.

[0458] S906, the serving base station transmits the received data (e.g., data transmitted by the UE) to the anchor base station.

[0459] S907, the anchor base station determines that the T-SDT-guard Timer expires.

[0460] S908, the anchor base station sends a UE Context Release message (e.g., a UE Context Release message) to the serving base station.

[0461] When the anchor base station determines that the T-SDT-guard Timer expires, the anchor base station can send a UE Context Release message to the serving base station, which triggers the release of the Xn interface and the RRC context of the UE.

[0462] S909, the anchor base station sends a UE Context Release message to the core network.

[0463] The anchor base station sends a message similar to the UE Context Release message to the core network, which triggers the core network to release the RRC context of the UE. In some embodiments, the message can carry a Session list, a cause value (e.g., SDT session termination, SDT session transmission failure, non-active state UE unreachable, non-active state to idle state, etc.).

[0464] Based on the above description, the embodiments of the present application provide various resource management methods. The network side can configure the timer of the UE side through a broadcast message or through an RRC Release message. Since the configuration parameters of the timer of the UE side are provided by the network side, the network side can know that the UE has terminated the SDT session, i.e., the network side and the UE RRC state are synchronized. After the network side knows that the UE has terminated the SDT session, the network side can release the resources configured for the SDT session, thereby reducing resource waste. Further, the network side does not need to send an RRC Release message to the UE to instruct the UE to terminate the SDT session, thereby further reducing resource waste.

[0465] As Figure 10As shown, the figure is a structural schematic diagram of another user equipment provided by the embodiment of the present application, the user equipment 1000 comprises a communication module 1001 and a processing module 1002.

[0466] The communication module 1001 is configured to receive the configuration parameter sent by the base station, the configuration parameter is used for configuring the timer of the UE, and is further configured to initiate a small packet data transmission (SDT) session.

[0467] The processing module 1002 is configured to start the timer, the timer is used for controlling the state of the SDT session, and is further configured to release the resource occupied by the SDT session when the timer is timed out.

[0468] In some possible implementation manners, the communication module 1001 is configured to receive the configuration parameter sent by the anchor base station through a radio resource control (RRC) release message.

[0469] In some possible implementation manners, the communication module 1001 is configured to receive the configuration parameter sent by the serving base station through a broadcast message.

[0470] In some possible implementation manners, the communication module 1001 is configured to send a RRC resume request message and small packet data to the base station to initiate an SDT session.

[0471] In some possible implementation manners, the communication module 1001 is configured to receive a RRC release message, a RRC resume message, a RRC setup message or a RRC reject message.

[0472] The processing module 1002 is configured to terminate the timer when the RRC release message, the RRC resume message, the RRC setup message or the RRC reject message is received.

[0473] In some possible implementation manners, the processing module 1002 is configured to restart the timer when a preset condition is met before the timer is timed out after the timer is started.

[0474] In some possible implementation manners, the processing module 1002 is configured to set the timer as a session failure timer, and the session failure timer is restarted when the UE sends small packet data, or the session failure timer is restarted when the UE receives small packet data, or the session failure timer is restarted when the UE receives a configuration of a dynamic scheduling resource.

[0475] In some possible implementation manners, the timer is a configured resource timer, and the processing module 1002 is configured to control a state of the SDT session by controlling a remaining time during which the UE can use the configured resource again after using the configured resource, and restart the configured resource timer when the UE uses the configured resource to send small packet data.

[0476] In some possible implementation manners, the timer is a session failure timer, and the processing module is configured to control the UE to enter an idle state or an inactive state when the session failure timer expires.

[0477] In some possible implementation manners, the communication module 1001 is configured to receive a control identifier sent by the base station, and the control identifier is used to control the UE to enter an idle state or an inactive state when the session failure timer expires.

[0478] The processing module 1002 is configured to control the UE to enter an idle state or an inactive state according to the control identifier sent by the base station when the session failure timer expires.

[0479] In some possible implementation manners, the timer is a configured resource timer, and the processing module 1002 is configured to trigger a process of reacquiring a configured resource when the configured resource timer expires, if the UE has uplink data to be transmitted or has not received feedback of correct data reception sent by the network; or terminate the configured resource timer if the UE does not have uplink data to be transmitted.

[0480] In some possible implementation manners, the retransmission timer is used to control a time during which data can be retransmitted, and the processing module 1002 is configured to trigger a process of reacquiring a configured resource when the retransmission timer expires, if the UE has not received feedback of correct data reception sent by the network.

[0481] In some possible implementation manners, the timer is a retransmission timer, the retransmission timer is used to control a time during which an SDT session can be retransmitted, and the processing module 1002 is configured to trigger any one of the following: a process of reacquiring a configured resource, terminate the retransmission timer or release resources occupied by the SDT session, when the number of retransmissions of the UE exceeds a preset number before the retransmission timer expires after the retransmission timer is started.

[0482] In some possible implementation manners, the timer is a timing advance timer, the timing advance timer is used to control the state of the SDT session by controlling the remaining time that the UE can use the configured resource before using the configured resource; the processing module 1002 is configured to measure a single sideband reference signal received power; if the single sideband reference signal received power is greater than or equal to a preset threshold value and the timing advance timer does not time out, the UE transmits uplink data by using the configured resource; and if the single sideband reference signal received power is less than the preset threshold value or the timing advance timer times out, a process of reacquiring the configured resource is triggered.

[0483] As shown in Figure 11 the communication module 1101 is configured to send a configuration parameter to the UE, and the configuration parameter is used to configure a timer of the UE.

[0484] The communication module 1101 is configured to send a configuration parameter to the UE, and the configuration parameter is used to configure a timer of the UE.

[0485] The processing module 1102 is configured to start a guard timer of the serving base station according to an SDT session initiated by the UE, and the timing time of the guard timer of the serving base station is greater than or equal to the timing time of the timer of the UE; and the processing module 1102 is further configured to request the serving base station to release a resource occupied by the SDT session when the guard timer times out.

[0486] In some possible implementation manners, the communication module 1101 is configured to send the configuration parameter to the UE by using a broadcast message.

[0487] In some possible implementation manners, the communication module 1101 is configured to receive a radio resource control resume request message and small packet data sent by the UE; and the processing module 1102 is configured to start the guard timer of the serving base station when the radio resource control resume request message and the small packet data sent by the UE are received.

[0488] In some possible implementation manners, the processing module 1102 is configured to restart the guard timer when the small packet data is received; and / or restart the guard timer when the small packet data is scheduled.

[0489] In some possible implementation, before the protection timer expires, the communication module 1101 is configured to send a resume UE context request message to the anchor base station of the UE, the resume UE context request message carrying the configuration parameter of the timer of the UE; receive a resume UE context response message sent by the anchor base station, the resume UE context response message carrying part of the context of the UE; and send a UE context release message to the anchor base station to request to release the resource occupied by the SDT session.

[0490] In some possible implementation, before the protection timer expires, the communication module 1101 is configured to send a resume UE context request message to the anchor base station of the UE; receive a resume UE context response message sent by the anchor base station, the resume UE context response message carrying all the context of the UE; and send a UE context release message to the core network to request to release the resource occupied by the SDT session.

[0491] In some possible implementation, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer or a timing advance timer.

[0492] As shown in Figure 12 The anchor base station 1200 includes a communication module 1201 and a processing module 1202.

[0493] The communication module 1201 is configured to send a configuration parameter to the UE, the configuration parameter being used to configure the timer of the UE; and receive a resume UE context request message sent by the serving base station.

[0494] The processing module 1202 is configured to start a protection timer of the anchor base station according to the resume UE context request message sent by the serving base station, the timing time of the protection timer of the anchor base station being greater than or equal to the timing time of the timer of the UE; and when the protection timer expires, trigger the anchor base station to release the resource occupied by the SDT session.

[0495] In some possible implementation, the communication module 1201 is configured to send the configuration parameter through a radio resource control release message.

[0496] In some possible implementation, the communication module 1201 is configured to trigger the release of the resource occupied by the SDT session by sending a UE context release message to the core network.

[0497] In a possible implementation, the communication module 1201 is configured to trigger release of the resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0498] In a possible implementation, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer, or a timing advance timer.

[0499] As shown in FIG. 13, which is a structural schematic diagram of an anchor base station according to an embodiment of the present application, the anchor base station 1300 includes a communication module 1301 and a processing module 1302. Figure 13

[0500] The communication module 1301 is configured to receive a resume UE context request message sent by a serving base station, wherein the resume UE context request message carries configuration parameters of a timer of a UE, and the configuration parameters of the timer of the UE are configured by the serving base station.

[0501] The processing module 1302 is configured to start a protection timer of the anchor base station according to the resume UE context request message, wherein a timing time of the protection timer of the anchor base station is greater than or equal to a timing time of the timer of the UE, and the anchor base station is further configured to trigger release of the resources occupied by the SDT session when the protection timer expires.

[0502] In a possible implementation, the configuration parameters of the timer of the UE are configured by the serving base station through a broadcast message.

[0503] In a possible implementation, the communication module 1301 is configured to trigger release of the resources occupied by the SDT session by sending a UE context release message to a core network.

[0504] In a possible implementation, the communication module 1301 is configured to trigger release of the resources occupied by the SDT session by sending a UE context release message to the serving base station.

[0505] In a possible implementation, the timer of the UE includes a session failure timer, a configured resource timer, a retransmission timer, or a timing advance timer.

[0506] As shown in FIG. 13, which is a structural schematic diagram of an anchor base station according to an embodiment of the present application, the anchor base station 1300 includes a communication module 1301 and a processing module 1302. Figure 14 ​As shown in the figure, this is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device 1400 may include: a communication interface 1401; one or more processors 1402; a memory 1403; and one or more computer programs 1404. The above-mentioned devices can be connected via one or more communication buses 1405. The one or more computer programs 1404 are stored in the memory 1403 and configured to be executed by the one or more processors 1402. The one or more computer programs 1404 include instructions that can be used to perform actions such as... Figures 3-9 The various steps performed by the UE in the corresponding embodiment. Of course, Figure 14 The electronic device shown may also include other components such as a sensor module, an audio module, and a SIM card interface; however, this application does not impose any limitations on these components. Figure 14 When the electronic device shown also includes other components such as a sensor module, an audio module, and a SIM card interface, it can be... Figure 2 The user equipment shown. The communication interface 1401 can be used to receive configuration parameters, etc., sent by the base station.

[0507] like Figure 15 As shown in the figure, this is a schematic diagram of the structure of a base station provided in an embodiment of this application. The base station 1500 may include: a communication interface 1501; one or more processors 1502; a memory 1503; and one or more computer programs 1504. These devices can be connected via one or more communication buses 1505. The one or more computer programs 1504 are stored in the memory 1503 and configured to be executed by the one or more processors 1502. The one or more computer programs 1504 include instructions that can be used to perform actions such as... Figures 3-9 The corresponding embodiments describe the various steps performed by the serving base station or anchor base station. The communication interface 1501 can be used to send configuration parameters, etc., to the UE.

[0508] This application also provides a computer-readable storage medium including instructions that, when executed on a computing device, cause the computing device to perform... Figures 3-9 The relevant methods and steps are described in the above embodiments to implement the methods described.

[0509] This application also provides a computer program product containing instructions that, when run on a computing device, cause the computing device to perform actions such as... Figures 3-9 The relevant methods and steps are described in the above embodiments to implement the methods described.

[0510] Those skilled in the art can clearly understand the system, device and unit described above by the description of the embodiments, for the convenience and brevity of description, only the division of the above functional modules is exemplified, in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0511] In several embodiments provided in the embodiment, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0512] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0513] In addition, each functional unit in each embodiment of the embodiment can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0514] The integrated unit, if realized in the form of software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiment can be embodied in the form of software product in essence or the part of the technical solutions that make contributions to the prior art or all or part of the technical solutions. The computer software product is stored in a storage medium, including a plurality of instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the method described in each embodiment. The foregoing storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and various program code storage media.

[0515] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any change or replacement within the technical scope disclosed by the present application should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A resource management method, characterized in that, The method is applied to a user equipment (UE), and the method includes: The UE receives configuration parameters sent by the base station, and the configuration parameters are used to configure the UE's timer; After the timer is configured, the UE initiates a Small Packet Data Transmission (SDT) session. Start the timer, which is used to control the state of the SDT session; When the timer expires, the UE releases the resources occupied by the SDT session.

2. The method according to claim 1, characterized in that, The base station is an anchor base station, and the UE receives configuration parameters sent by the base station, including: The UE receives the configuration parameters sent by the anchor base station through the radio resource control release message.

3. The method according to claim 1, characterized in that, The base station is a serving base station, and the UE receives configuration parameters sent by the base station, including: The UE receives configuration parameters sent by the serving base station via broadcast messages.

4. The method according to claim 1, characterized in that, The UE initiates a small packet data transmission SDT session, including: The UE sends a Radio Resource Control Recovery Request message and small packet data to the base station to initiate an SDT session.

5. The method according to claim 1, characterized in that, After the timer is started and before the timer expires, the method further includes: When the UE receives a radio resource control release message, a radio resource control recovery message, a radio resource control setting message, or a radio resource control rejection message, the UE terminates the timer.

6. The method according to any one of claims 1-5, characterized in that, After the timer is started and before the timer expires, the method further includes: The UE restarts the timer when a preset condition is met.

7. The method according to claim 6, characterized in that, The timer is a session failure timer. When the UE meets preset conditions, it restarts the timer, including: When the UE sends small packet data, restart the session failure timer; or, When the UE receives small packet data, restart the session failure timer; or, When the UE receives the configuration of dynamically scheduled resources, the session failure timer is restarted.

8. The method according to claim 6, characterized in that, The timer is a configuration resource timer, which is used to control the state of the SDT session by controlling whether the UE can reuse the remaining time of the configuration resource after using it. The UE restarts the timer when a preset condition is met, including: When the UE uses the configuration resources to send small packet data, the configuration resource timer is restarted.

9. The method according to claim 1, characterized in that, The timer is a session failure timer, and when the session failure timer times out, the method further includes: The UE enters an idle state or an inactive state.

10. The method according to claim 9, characterized in that, The method further includes: The UE receives a control identifier sent by the base station. The control identifier is used to control the UE to enter an idle state or an inactive state when the session failure timer expires. The UE entering an idle or inactive state includes: The UE enters an idle state or an inactive state based on the control identifier sent by the base station.

11. The method according to claim 1, characterized in that, The timer is a configuration resource timer. When the configuration resource timer times out, the method further includes: If the UE has uplink data that needs to be transmitted or has not received feedback from the network that it has received correct data, the UE triggers a process to reacquire configuration resources; or, If the UE does not have uplink data to transmit, the UE terminates the configuration resource timer.

12. The method according to claim 1, characterized in that, The timer is a retransmission timer, which controls the time during which data can be retransmitted. When the retransmission timer times out, the method further includes: If the UE does not receive feedback from the network that the data has been received correctly, the UE triggers a process to reacquire configuration resources.

13. The method according to claim 1, characterized in that, The timer is a retransmission timer, which controls the time during which the SDT session can retransmit data. After the retransmission timer is started and before it expires, the method further includes: When the number of retransmissions by the UE exceeds a preset number, the UE triggers one of the following: a process to reacquire configuration resources, terminates the retransmission timer, or releases the resources occupied by the SDT session.

14. The method according to claim 1, characterized in that, The timer is a timed advance timer, which is used to control the state of the SDT session by controlling the UE to utilize the remaining time of the configuration resources before utilizing the configuration resources. The method further includes: The UE measures the single-sideband reference signal received power; If the single-sideband reference signal received power is greater than or equal to a preset threshold and the timing advance timer has not expired, the UE uses the configured resources to transmit uplink data. If the single-sideband reference signal received power is less than a preset threshold or the timing advance timer times out, the UE triggers the process of reacquiring configuration resources.

15. A resource management method, characterized in that, The method is applied to a serving base station, and the method includes: The serving base station sends configuration parameters to the UE, which are used to configure the UE's timer. After the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The serving base station starts its protection timer based on the SDT session initiated by the UE, and the timing period of the serving base station's protection timer is greater than or equal to the timing period of the UE's timer. When the protection timer expires, the serving base station requests the release of the resources occupied by the SDT session.

16. A resource management method, characterized in that, The method is applied to anchor point base stations, and the method includes: The anchor base station sends configuration parameters to the UE, which are used to configure the UE's timer. After the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The anchor base station starts its protection timer according to the UE context recovery request message sent by the serving base station. The timing period of the anchor base station's protection timer is greater than or equal to the timing period of the UE's timer. When the protection timer expires, the anchor base station triggers the release of the resources occupied by the SDT session.

17. A resource management method, characterized in that, The method is applied to anchor point base stations, and the method includes: The anchor base station receives a UE context recovery request message sent by the serving base station. The UE context recovery request message carries the configuration parameters of the UE's timer, which are configured by the serving base station. After the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The anchor base station starts its protection timer according to the recovery UE context request message, and the timing period of the anchor base station's protection timer is greater than or equal to the timing period of the UE's timer. When the protection timer expires, the anchor base station triggers the release of the resources occupied by the SDT session.

18. A resource management system, characterized in that, include: UE and base station; The base station is used to send configuration parameters to the UE; The UE is configured to configure a timer for the UE according to the configuration parameters, initiate an SDT session and start the timer, and release the resources occupied by the SDT session when the timer expires; wherein, the timer is used to control the state of the SDT session.

19. A resource management system, characterized in that, include: UE and serving base station; The serving base station is used to send configuration parameters to the UE; The UE is configured to configure a timer for the UE according to the configuration parameters, initiate an SDT session and start the timer; after the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The serving base station is configured to start a protection timer for the serving base station based on the SDT session initiated by the UE, and request the release of the resources occupied by the SDT session when the protection timer expires. The timing period of the protection timer is greater than or equal to the timing period of the UE's timer.

20. A resource management system, characterized in that, include: UE, serving base station, and anchor base station; The anchor base station is used to send configuration parameters to the UE; The UE is configured to configure a timer for the UE according to the configuration parameters, initiate an SDT session and start the timer; after the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The serving base station is used to send a UE context recovery request message to the anchor base station; The anchor base station starts a protection timer based on the UE context recovery request message. When the protection timer expires, it triggers the release of resources occupied by the SDT session. The timing period of the anchor base station's protection timer is greater than or equal to the timing period of the UE's timer.

21. A resource management system, characterized in that, include: UE, serving base station, and anchor base station; The serving base station is used to send configuration parameters to the UE; The UE is configured to configure a timer for the UE according to the configuration parameters, initiate an SDT session and start the timer; after the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The serving base station is used to send a restore UE context request message to the anchor base station, the restore UE context request message carrying the configuration parameters of the UE's timer; The anchor base station is configured to start a protection timer for the anchor base station according to the recovery UE context request message, and trigger the release of resources occupied by the SDT session when the protection timer expires; the timing period of the protection timer of the anchor base station is greater than or equal to the timing period of the UE's timer.

22. A user equipment, characterized in that, include: Communication module and processing module; The communication module is used to receive configuration parameters sent by the base station. The configuration parameters are used to configure the timer of the UE and to initiate a small packet data transmission SDT session. The processing module is used to start the timer, which is used to control the state of the SDT session and to release the resources occupied by the SDT session when the timer expires.

23. A serving base station, characterized in that, include: Communication module and processing module; The communication module is used to send configuration parameters to the UE, and the configuration parameters are used to configure the UE's timer; After configuration, the timer is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The processing module is used to start the protection timer of the serving base station according to the SDT session initiated by the UE, wherein the timing period of the protection timer of the serving base station is greater than or equal to the timing period of the UE's timer. It is also used to request the release of resources occupied by the SDT session when the protection timer expires.

24. An anchor point base station, characterized in that, include: Communication module and processing module; The communication module is used to send configuration parameters to the UE, and the configuration parameters are used to configure the UE's timer; It is also used to receive a UE context recovery request message sent by the serving base station; after the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session; The processing module is configured to start a protection timer for the anchor base station based on the UE context recovery request message sent by the serving base station, wherein the timing period of the protection timer for the anchor base station is greater than or equal to the timing period of the UE's timer. It is also used to trigger the release of resources occupied by the SDT session when the protection timer expires.

25. An anchor point base station, characterized in that, include: Communication module and processing module; The communication module is used to receive a UE context recovery request message sent by the serving base station. The UE context recovery request message carries the configuration parameters of the UE's timer, which are configured by the serving base station. After the timer is configured, it is used to control the state of the SDT session initiated by the UE, and when the timer expires, the UE releases the resources occupied by the SDT session. The processing module is configured to start a protection timer of the anchor base station according to the recovery UE context request message, wherein the timing period of the protection timer of the anchor base station is greater than or equal to the timing period of the UE's timer, and is further configured to trigger the release of resources occupied by the SDT session when the protection timer expires.

26. An electronic device, characterized in that, include: Memory and processor; The memory stores one or more computer programs, the one or more computer programs including instructions; when the instructions are executed by the processor, the electronic device performs the method as described in any one of claims 1 to 14.

27. A base station, characterized in that, include: Memory and processor; The memory stores one or more computer programs, the one or more computer programs including instructions; when the instructions are executed by the processor, the base station performs the method as described in any one of claims 15 to 17.

28. A computer storage medium, characterized in that, Includes computer instructions, which, when executed on a computing device, cause the computing device to perform the method as described in any one of claims 1 to 17.

Images