Method, base station and communication system for reducing access delay

By generating RRC release messages in the CU entity of the base station in the 5G NR network, including SDT-related configuration information, the problems of small packet transmission delay and resource configuration optimization are solved, the effective retention of resources and the stability of transmission channels are achieved, and the stability of transmission channels is improved. User experience.

CN115474287BActive Publication Date: 2024-11-19CHINA TELECOM CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110648205.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-06-10
Publication Date
2024-11-19
Estimated Expiration
2041-06-10

AI Technical Summary

Technical Problem

In 5G NR networks, existing protocols cannot effectively support the transmission of small data packets, resulting in long access delays and the inability to optimize resource configuration, resulting in waste of resources and loss of transmission channels.

Method used

The RRC release message is generated through the CU entity of the base station, which contains SDT-related configuration information, ensuring that the DU entity retains resources and configures appropriate ConfiguredGrant resources. The user terminal selects resources for uplink transmission when the user terminal is inactive, maintains resource configuration, and avoids resource waste and transmission Channel is lost.

Benefits of technology

It effectively reduces the transmission delay of small packets, optimizes resource configuration, reduces resource waste and delay in re-establishment of transmission channels, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115474287B_ABST
    Figure CN115474287B_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, base station and communication system for reducing access delay. The method for reducing access delay includes: when the CU entity determines whether the user terminal has the ability to support the transmission of small data packets in an inactive state according to the capability of the user terminal, if the user terminal is to enter the inactive state and has a service that can be configured as SDT, a first RRC release message is generated and sent to the DU entity; the DU entity determines part of the configuration information related to the cell and the underlying resource configuration, and adds the part of the configuration information to the first RRC release message to generate a second RRC release message; the DU entity sends the second RRC release message to the user terminal, and reserves the resources related to the user terminal, so that the user terminal performs resource configuration according to the second RRC release message, enters the inactive state, and selects the corresponding resources for uplink transmission and remains in the inactive state when uplink data needs to be sent.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a method, a base station, and a communication system for reducing access delay. Background Art

[0002] In 5G networks, NR (New Radio) non-IoT terminals can enter an inactive state to reduce terminal power consumption and reduce the signaling interaction process between the terminal and the core network, thereby improving the terminal's access latency.

[0003] In the existing scheme, if there are small data packets to be sent on the terminal side, it is still necessary to go through the RRC (Radio Resource Control) recovery process, first complete the control plane establishment, and then send and receive the data packet. Obviously, this method does not significantly improve the access delay on the one hand, and on the other hand, it causes the terminal to return to the inactive state after completing one or more data packets. For periodic small data transmission, it will still increase the excessive signaling interaction between the terminal and the network. In response to the above problems, 3GPP (3rd Generation Partnership Project) has carried out research on SDT (Small Data Transmission), the purpose of which is to reduce the access delay of the terminal sending small data packets in the inactive state. At present, the standard has determined to support data packet transmission based on RACH (Random Access Channel) and data packet transmission based on Configured Grant. Compared with the RACH-based solution, the Configured Grant-based solution reduces the RACH transmission process, so it is a method with the shortest delay. However, it should be pointed out that since the ConfiguredGrant-based approach pre-occupies some resources, long-term non-use of the terminal will lead to waste of resources. Therefore, the network side needs to consider whether to configure ConfigureGrant resources for the terminal when it enters the inactivated state and on which carrier to configure the ConfiguredGrant resources.

[0004] Uplink grant-free scheduling based on non-dynamic scheduling, that is, ConfiguredGrant is an uplink grant granted to the terminal by gNB (next generation NodeB) through activation once. If the terminal does not receive a deactivation instruction, it will always use the resources specified by the first uplink grant for uplink transmission. There are two types of transmission:

[0005] ●Configuration grant type 1: configured by RRC through high-level signaling (IE ConfiguredGrantConfig);

[0006] ●Configuration authorization type 2: The activation and deactivation of uplink authorization-free is indicated by DCI (Downlink Control Indicator). The required parameters are based on the pre-configured resources. The terminal side does not need to go through an uplink request and can directly transmit uplink data on the predefined resources, thereby reducing the uplink data transmission delay.

[0007] In addition, in the 5G system, in order to enhance the uplink coverage capability of the terminal, the SUL (Supplementary Uplink) method is also proposed. Based on this method, one downlink carrier of the terminal corresponds to two uplink carriers, namely SUL and NUL (Normal Uplink). According to the current protocol definition, both SUL and NUL can be configured with Configured Grant resources at the same time, and the terminal can select the Configured Grant resources of one of the carriers for transmission at different transmission times when both uplink carriers are configured.

[0008] In terms of network architecture, the 5G NR base station includes two logical network elements, CU (Centralized Unit) and DU (Distributed Unit), which can be deployed in one or separately according to the scenario and requirements. The network function reconstruction between 5G NR network elements, such as some core network functions are transferred to CU, and some functions of BBU (Baseband Unit) are moved to RRU (Remote Radio Unit) / AAU (Active Antenna Unit). CU mainly includes non-real-time wireless high-level protocol stack functions, and also supports the transfer of some core network functions and the deployment of edge application services. The main function of DU is to process physical layer functions and layer 2 functions with real-time requirements. Considering the saving of transmission resources between RRU and DU, some physical layer functions can also be moved to RRU for implementation. When the terminal enters the RRC inactive state from the RRC connected state, the CU needs to release the underlying resources through the UE Context Release message. Summary of the invention

[0009] The inventors note that the current standards have not yet developed a function for supporting the transmission of small data packets in a separation architecture. According to the definition in the current specifications, the implementation scheme involved in the transmission of small data packets and the resource allocation process, the current 5G protocol still has the following problems when supporting SDT transmission based on a separation architecture:

[0010] ● Unable to instruct the DU entity to reserve SDT resources for it: When receiving the RRC Release message, the DU entity cannot distinguish whether it is a normal inactive state transition or a transmission based on SDT. Therefore, according to the current process, it is necessary to release the relevant resources of the physical layer / MAC (Medium Access Control) layer / RLC (Radio Link Control) layer. From the perspective of the network side, the ConfiguredGrant has expired and cannot support the user's subsequent transmission.

[0011] ● The network side cannot determine which carrier's ConfiguredGrant resources need to be retained: During the connection release process, the network side can modify the uplink carrier resources configured for the terminal in the connected state and the ConfiguredGrant resources on these carriers based on coverage conditions and other reasons. However, the current protocol uses the configuration of releasing all uplink resources. The terminal needs to select appropriate resources and access methods to avoid waste caused by configuring ConfiguredGrant but not using it. At the same time, the terminal's access level and position may also change before the TA (Timing Advance) timer expires, thereby affecting the correctness of the pre-configured parameters. In addition, the current DU does not have any RSRP (Reference Signal Receiving Power) measurement information, so the network side is currently unable to determine on what basis to configure uplink access resources for the terminal.

[0012] ● Unable to maintain the user plane interface between CU and DU: Since different DRBs (Data Radio Bearers) have independent transmission channel interfaces between CU and DU, when entering the SDT state, the transmission channel interface between CU and DU needs to be maintained for SDT-supported bearers. Since the RRC connection release operation causes the channel between bearers to be deleted, the DU needs to re-establish the transmission channel with the CU due to the lack of transmission channel for subsequent small data packets, which results in additional transmission delay.

[0013] Based on the above requirements and reason analysis, the current 3GPP NR protocols cannot meet the requirements and need to be enhanced in new ways to meet the needs of network deployment and optimization.

[0014] To this end, the present disclosure provides a solution for reducing access delay, which can effectively reduce the delay in the process of sending small data packets and improve user experience and perception.

[0015] According to a first aspect of an embodiment of the present disclosure, a method for reducing access delay is provided, the method being executed by a base station, comprising: a CU entity of the base station determines whether the user terminal has the ability to support transmission of small data packets in an inactive state according to the capability of the user terminal; if the user terminal has the ability to support transmission of small data packets in an inactive state, when the user terminal is about to enter the inactive state and has a service that can be configured as SDT, a first RRC release message is generated; the CU entity sends a first terminal context release command message to a DU entity of the base station, wherein the first terminal context release command message includes the first RRC release message; after receiving the first terminal context release command message, the DU entity determines part of the configuration information related to the cell and underlying resource configuration, and adds the part of the configuration information to the first RRC release message to generate a second RRC release message; the DU entity sends the second RRC release message to the user terminal and reserves resources related to the user terminal so that the user terminal performs resource configuration according to the second RRC release message, enters the inactive state, and selects corresponding resources for uplink transmission and remains in the inactive state when uplink data needs to be sent.

[0016] In some embodiments, the first RRC release message includes configuring a bearer identifier list for SDT, selecting a data volume trigger threshold for SDT, selecting an RSRP threshold based on ConfiguredGrant and / or based on a RACH scheme, selecting an RSRP threshold for a SUL carrier based on ConfiguredGrantt and / or based on a RACH scheme, and at least one of a validity period threshold for ConfiguredGrant.

[0017] In some embodiments, after generating the first RRC release message, the CU entity also retains the context information of the user terminal and the PDCP layer related configuration.

[0018] In some embodiments, the first terminal context release command message also includes: RSRP measurement information of the user terminal, uplink carrier configuration information, underlying information configuration retention indication information, indication information on whether a transmitter switching function is supported, and at least one item in a DRB retention list, wherein the uplink carrier configuration information includes NUL, SUL, or both SUL and NUL carriers, and the underlying information configuration retention indication information includes a retention indication or a release indication, and the retention indication indicates that the DU entity needs to maintain the physical layer, MAC layer, and RLC layer resources of the user terminal. When the indication information on whether the transmitter switching function is supported is 1, it indicates that the user terminal can use the uplink resources of SUL and NUL at the same time during the access process, and the transmitter of the user terminal supports switching between SUL and NUL carriers. When it is 0 or not carried, it indicates that it only supports working on one uplink carrier, and the DRB retention list includes one or more DRB identifiers and at least one item in the channel address list of the maintained uplink F1 interface.

[0019] In some embodiments, the determination of partial configuration information related to the cell and underlying resource configuration includes: if at least one DRB bearer needs to be configured as SDT, the DU entity updates or reconfigures the uplink carrier used by the user terminal according to the uplink carrier configuration information, and generates physical layer configuration information corresponding to the uplink carrier.

[0020] In some embodiments, with respect to the uplink carrier configuration information, the DU entity determines a carrier for which ConfiguredGrant resources need to be configured or deleted, and adds the relevant configuration information to the first RRC release message.

[0021] In some embodiments, the DU entity determines the carrier that needs to configure or delete ConfiguredGrant resources, including: the DU entity determines the RSRP level strength of the user terminal; determines the RSRP range of the user terminal before timeout based on the RSRP level strength, the estimated movement speed of the user terminal and the remaining duration of the TA timer of the user terminal; determines the candidate uplink carrier for configuring ConfiguredGrant resources based on the uplink carrier configuration information; for each candidate uplink carrier, determines whether the lower limit value of the RSRP range is greater than the configuration threshold of the corresponding candidate uplink carrier; if the lower limit value of the RSRP range is not greater than the configuration threshold of the corresponding candidate uplink carrier, deletes the ConfiguredGrant resources on the candidate uplink carrier.

[0022] In some embodiments, the DU entity determines the RSRP level strength of the user terminal including: the DU entity calculates the RSRP level strength of the user terminal using the RSRP measurement information of the user terminal included in the first terminal context release command message or the signal strength received by the DU entity when the user terminal last sent uplink data.

[0023] In some embodiments, if both the SUL and the NUL meet the conditions for configuring ConfiguredGrant resources, whether it is necessary to configure ConfiguredGrant resources for the SUL and NUL at the same time is determined according to the indication information of whether the transmitter switching function is supported included in the first terminal context release command message; if it is necessary to configure ConfiguredGrant resources for the SUL and NUL at the same time, ConfiguredGrant resources are configured for the SUL and NUL; if it is not necessary to configure ConfiguredGrant resources for the SUL and NUL at the same time, one carrier is selected from the SUL and NUL according to the RSRP threshold for the SUL carrier in the first RRC release message, and the ConfiguredGrant resources in the unselected carrier are deleted.

[0024] In some embodiments, the DU entity utilizes the underlying information configuration maintenance indication information included in the first terminal context release command message to maintain or release the configuration resources of the physical layer, MAC layer and RLC layer corresponding to the user terminal, and clears the corresponding timers and caches.

[0025] In some embodiments, the DU entity uses the DRB retention list included in the first terminal context release command message to determine the bearers that do not need to be deleted, and the user plane transmission channel between the DU entity and the CU entity for the bearers that do not need to be deleted; deletes the configuration resources of the physical layer, MAC layer and RLC layer associated with the bearers not included in the DRB retention list, and clears the corresponding timers and interface resources.

[0026] In some embodiments, after completing resource configuration, the DU entity sends a terminal context release completion message to the CU entity, and the terminal context release completion message includes the resource configuration result.

[0027] In some embodiments, if one or more DRBs need to be configured as SDT, the DU entity determines whether the user terminal uses one uplink carrier or multiple uplink carriers based on the uplink carrier configuration information, and configures the relevant resources in the physical layer and MAC layer mapped to the uplink carrier used by the user terminal. For the physical layer, the uplink PRACH resources and GonfiguredGrant resources to be configured on the corresponding carrier are retained, and other timers and configuration resources of the physical layer are deleted; the user plane data of the MAC layer is reset, all caches are cleared and the timers are reset; for the RLC layer, only SRB1 is reconfigured, and the parameter configurations of other DRBs and SRBs are deleted; the configuration information related to SDT, SDT transmission and triggering thresholds and conditions are saved; and the CU entity suspends PDCP.

[0028] In some embodiments, after receiving the uplink data sent by the user terminal, the DU entity instructs the user terminal to update the TA timer through the MAC CE in the downlink direction; the DU entity determines the DRB corresponding to the uplink data according to the logical channel identifier of the user terminal related to the uplink transmission, and sends the uplink data to the CU entity using the DRB corresponding to the uplink data; after detecting that the TA timer of the user terminal has timed out, the DU entity releases the resources related to the SDT and sends a terminal context release request message to the CU entity; after the CU entity determines that the DU entity has released the resources related to the SDT according to the indication information included in the terminal context release request message, it releases the resource configuration information related to the SDT and only retains the context of the user terminal.

[0029] In some embodiments, the CU entity sends a second terminal context release command message to the DU entity and deletes the corresponding user plane transmission channel; after receiving the second terminal context release command message, the DU entity deletes the corresponding user plane transmission channel.

[0030] In some embodiments, after receiving the uplink data sent by the user terminal, the DU entity sends the uplink data to the CU entity through the reserved uplink F1 interface.

[0031] According to a second aspect of an embodiment of the present disclosure, a base station is provided, comprising: a memory configured to store instructions; a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on the instructions stored in the memory.

[0032] According to the third aspect of an embodiment of the present disclosure, a communication system is provided, comprising: a base station as described in any of the above embodiments; and a user terminal, configured to perform resource configuration according to a second RRC release message sent by a DU entity of the base station, and enter an inactivated state, and select corresponding resources for uplink transmission and maintain an inactivated state when uplink data needs to be sent.

[0033] In some embodiments, the user terminal is configured to determine whether the user terminal uses one uplink carrier or multiple uplink carriers according to the uplink carrier configuration information if the second RRC release message indicates that one or more DRBs are configured as SDT, and configure the relevant resources in the physical layer and MAC layer mapped to the uplink carrier used by the user terminal, retain the uplink PRACH resources and GondfiguredGrant resources to be configured on the corresponding carrier for the physical layer, delete other timers and configuration resources of the physical layer; reset the user plane data of the MAC layer, clear all caches and reset the timers; for the RLC layer, only re-set SRB1, delete the parameter configuration of other DRBs and SRBs; suspend PDCP; save the configuration information related to SDT, SDT transmission and triggering thresholds and conditions.

[0034] In some embodiments, the user terminal is also configured to trigger a corresponding SDT transmission when there is uplink data to be sent on a bearer configured as SDT and the TA timer has not timed out, if the amount of the uplink data is less than a corresponding threshold specified in the second RRC release message.

[0035] In some embodiments, the user terminal is further configured to select an uplink carrier for transmission during the process of triggering corresponding SDT transmission, and select a RACH access-based method or a ConfiguredGrant-based method for uplink data transmission.

[0036] In some embodiments, the user terminal is also configured to send terminal capability information to the core network via a NAS message, wherein the terminal capability information is used to indicate whether the user terminal has the ability to support the transmission of small data packets in an inactivated state, so that the core network sends the terminal capability information to the CU entity of the base station for storage during the context establishment process of the user terminal.

[0037] In some embodiments, the user terminal is also configured to determine whether it is necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time when both the SUL and the NUL meet the conditions for configuring ConfiguredGrant resources, based on the indication information of whether the transmitter switching function is supported included in the second terminal context release command message; if it is necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time, configure ConfiguredGrant resources for the SUL and the NUL; if it is not necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time, select a carrier between the SUL and the NUL based on the RSRP threshold for the SUL carrier in the first RRC release message, and delete the ConfiguredGrant resources in the unselected carrier.

[0038] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any of the above embodiments is implemented.

[0039] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 A flow chart of a method for reducing access delay according to an embodiment of the present disclosure;

[0042] Figure 2 A schematic diagram of a resource configuration method according to an embodiment of the present disclosure;

[0043] Figure 3 This is a schematic diagram of the structure of a base station according to an embodiment of the present disclosure;

[0044] Figure 4 A schematic diagram of the structure of a communication system according to an embodiment of the present disclosure;

[0045] Figure 5 A flowchart of a method for reducing access delay according to another embodiment of the present disclosure;

[0046] Figure 6 The present invention is a flowchart of a method for reducing access delay according to another embodiment of the present invention. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0048] The relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

[0049] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0050] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0051] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0052] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0053] Figure 1 The following is a flow chart of a method for reducing access delay according to an embodiment of the present disclosure. In some embodiments, the following method for reducing access delay is executed by a base station.

[0054] In step 101, a CU entity of a base station determines, based on the capability of the user terminal, whether the user terminal has the capability to support transmission of a small data packet in an inactive state.

[0055] In step 102, if the user terminal has the capability to support the transmission of small data packets in the inactive state, when the user terminal is about to enter the inactive state and has a service that can be configured as SDT, a first RRC release message is generated. In addition, the context information of the user terminal and the PDCP layer related configuration are also retained.

[0056] In some embodiments, the first RRC release message includes at least one of the following:

[0057] -Configure the SDT bearer identifier list: including one or more bearer identifiers

[0058] -Select the SDT data volume trigger threshold: integer type, when the user terminal uplink data volume is lower than the corresponding threshold, the SDT transmission is triggered, otherwise the data transmission is carried out according to the normal inactive process

[0059] -Selection of RSRP threshold based on ConfiguredGrant and / or based on RACH scheme: an integer RSRP value

[0060] -Selection of RSRP threshold for SUL carrier based on ConfiguredGrant and / or RACH scheme

[0061] -ConfiguredGrant validity threshold.

[0062] In step 103, the CU entity sends a first terminal context release command message to the DU entity of the base station, wherein the first terminal context release command message includes a first RRC release message.

[0063] In some embodiments, the first terminal context release command message further includes at least one of the following:

[0064] - RSRP measurement information of the user terminal: the latest RSRP measurement report collected by the CU entity

[0065] - Uplink carrier configuration information: enumeration type, including: NUL, SUL, or both SUL and NUL

[0066] - Lower layer information configuration retention indication information: enumeration type, including "keep" or "release", etc., where "keep" means that the DU entity needs to keep the physical layer, MAC layer, and RLC layer resources of the user terminal

[0067] - Indication of whether the transmitter switching (Tx Switching) function is supported: It is a Boolean or enumeration type. When it is 1, it means that the user terminal can use the uplink resources of SUL and NUL at the same time during the access process, and the user terminal's transmitter supports switching between SUL and NUL carriers. When it is 0 or not carried, it means that it only supports working on one uplink carrier.

[0068] -DRB maintains a list including at least one of the following

[0069] ●One or more DRB identifiers

[0070] ● List of channel addresses of the uplink F1 interface to be maintained: Each channel address is mapped one-to-one with the DRB to be maintained. The channel address includes: Transport Layer Address and port information GTP-TEID defined in TS38.473

[0071] In step 104, after receiving the first terminal context release command message, the DU entity determines part of the configuration information related to the cell and underlying resource configuration, and adds the part of the configuration information to the first RRC release message to generate a second RRC release message.

[0072] In some embodiments, if at least one DRB bearer needs to be configured as an SDT, the DU entity updates or reconfigures the uplink carrier used by the user terminal according to the uplink carrier configuration information, and generates physical layer configuration information corresponding to the uplink carrier. Otherwise, no cell and underlying resource configuration is added.

[0073] With respect to the uplink carrier configuration information, the DU entity determines the carrier for which the ConfiguredGrant resources need to be configured or deleted, and adds the relevant configuration information to the first RRC release message.

[0074] In some embodiments, the DU entity determines the RSRP level strength of the user terminal. For example, the DU entity calculates the RSRP level strength of the user terminal using the RSRP measurement information of the user terminal included in the first terminal context release command message or the signal strength received by the DU entity when the user terminal last sent uplink data.

[0075] Next, the RSRP range of the user terminal before timeout is determined based on the RSRP level strength, the estimated movement speed of the user terminal, and the remaining time of the TA timer of the user terminal. max , RSRP min ]. Determine the candidate uplink carrier for configuring the ConfiguredGrant resource according to the uplink carrier configuration information. For each candidate uplink carrier, determine whether the lower limit value of the RSRP range is greater than the configuration threshold of the corresponding candidate uplink carrier. If the lower limit value of the RSRP range is not greater than the configuration threshold of the corresponding candidate uplink carrier, delete the ConfiguredGrant resource on the candidate uplink carrier.

[0076] In some embodiments, if both SUL and NUL meet the conditions for configuring ConfiguredGrant resources, it is determined whether it is necessary to configure ConfiguredGrant resources for both SUL and NUL according to the indication information of whether the transmitter switching function is supported included in the first terminal context release command message. If it is necessary to configure ConfiguredGrant resources for both SUL and NUL, ConfiguredGrant resources are configured for SUL and NUL. If it is not necessary to configure ConfiguredGrant resources for both SUL and NUL, one carrier is selected from SUL and NUL according to the RSRP threshold for the SUL carrier in the first RRC release message, and the ConfiguredGrant resources in the unselected carrier are deleted.

[0077] In some embodiments, the DU entity utilizes the underlying information configuration maintenance indication information included in the first terminal context release command message to maintain or release the configuration resources of the physical layer, MAC layer and RLC layer corresponding to the user terminal, and clear the corresponding timer and cache.

[0078] In some embodiments, the DU entity uses the DRB retention list included in the first terminal context release command message to determine the bearers that do not need to be deleted, as well as the user plane transmission channel between the DU entity and the CU entity that does not need to be deleted. The configuration resources of the physical layer, MAC layer, and RLC layer associated with the bearers not included in the DRB retention list are deleted, and the corresponding timers and interface resources are cleared.

[0079] In some embodiments, after completing resource configuration, the DU entity sends a terminal context release completion message to the CU entity, and the terminal context release completion message includes the resource configuration result.

[0080] In step 105, the DU entity sends a second RRC release message to the user terminal and reserves resources related to the user terminal so that the user terminal performs resource configuration according to the second RRC release message and enters an inactivated state, and selects corresponding resources for uplink transmission and remains in an inactivated state when uplink data needs to be sent.

[0081] In some embodiments, if one or more DRBs need to be configured as SDT, the DU entity determines whether the user terminal uses one uplink carrier or multiple uplink carriers based on the uplink carrier configuration information, and configures the relevant resources in the physical layer and MAC layer mapped to the uplink carrier used by the user terminal. For the physical layer, the uplink PRACH resources and GonfiguredGrant resources to be configured on the corresponding carrier are retained, and other timers and configuration resources of the physical layer are deleted; the user plane data of the MAC layer is reset, all caches are cleared and the timers are reset; for the RLC layer, only SRB1 is reset, and the parameter configuration of other DRBs and SRBs is deleted; the configuration information related to SDT, SDT transmission and triggering thresholds and conditions are saved. The CU entity performs a suspend operation on the PDCP.

[0082] Figure 2 The following is a flow chart of a resource configuration method according to an embodiment of the present disclosure. In some embodiments, the following resource configuration method is executed by a base station.

[0083] In step 201, after receiving uplink data sent by a user terminal, the DU entity instructs the user terminal to update a TA timer via a MACCE (Control Element) in the downlink direction.

[0084] In step 202, the DU entity determines the DRB corresponding to the uplink data according to the logical channel identifier of the user terminal related to the uplink transmission, and sends the uplink data to the CU entity using the DRB corresponding to the uplink data.

[0085] In step 203, after detecting that the TA timer of the user terminal has timed out, the DU entity releases resources related to the SDT and sends a terminal context release request message to the CU entity.

[0086] In step 204, after the CU entity determines that the DU entity has released the resources related to the SDT according to the indication information included in the terminal context release request message, it releases the resource configuration information related to the SDT and only retains the context of the user terminal.

[0087] In step 205, the CU entity sends a second terminal context release command message to the DU entity, and deletes the corresponding user plane transmission channel.

[0088] In step 206, after receiving the second terminal context release command message, the DU entity deletes the corresponding user plane transmission channel.

[0089] In some embodiments, after receiving the uplink data sent by the user terminal, the DU entity sends the uplink data to the CU entity through the reserved uplink F1 interface.

[0090] Figure 3 FIG. 1 is a schematic diagram of the structure of a base station according to an embodiment of the present disclosure. Figure 3 As shown, the base station includes a memory 31 and a processor 32.

[0091] The memory 31 is used to store instructions. The processor 32 is coupled to the memory 31. The processor 32 is configured to execute the instructions stored in the memory to implement the following. Figure 1 or Figure 2 The method of any one of the embodiments.

[0092] like Figure 3 As shown, the base station also includes a communication interface 33 for information exchange with other devices. At the same time, the base station also includes a bus 34, through which the processor 32, the communication interface 33, and the memory 31 communicate with each other.

[0093] The memory 31 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. The memory 31 may also be a memory array. The memory 31 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0094] In addition, the processor 32 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.

[0095] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the following are implemented: Figure 1 or Figure 2 The method of any one of the embodiments.

[0096] Figure 4 FIG. 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present disclosure. Figure 4 As shown, the communication system includes a base station 41 and a user terminal 42. The base station 41 is Figure 3 A base station as described above.

[0097] The user terminal 42 is configured to perform resource configuration according to the second RRC release message sent by the DU entity of the base station, and enter an inactive state, and select corresponding resources for uplink transmission and remain in an inactive state when uplink data needs to be sent.

[0098] In some embodiments, the user terminal 42 is configured to determine whether the user terminal uses one uplink carrier or multiple uplink carriers according to the uplink carrier configuration information if the second RRC release message indicates that one or more DRBs are configured as SDT, and configure the relevant resources in the physical layer and MAC layer mapped by the uplink carrier used by the user terminal, retain the uplink PRACH resources and GondfiguredGrant resources to be configured on the corresponding carrier for the physical layer, delete other timers and configuration resources of the physical layer; reset the user plane data of the MAC layer, clear all caches and reset the timers; for the RLC layer, only re-set SRB1, delete the parameter configuration of other DRBs and SRBs; suspend the PDCP; save the configuration information related to SDT, SDT transmission and triggering thresholds and conditions. Otherwise, the user terminal 42 transmits data according to the normal inactivated process.

[0099] In some embodiments, the user terminal 42 is also configured to trigger a corresponding SDT transmission when there is uplink data to be sent on the bearer configured as SDT and the TA timer has not timed out, if the amount of uplink data is less than the corresponding threshold specified in the second RRC release message.

[0100] In addition, the user terminal 42 is further configured to select an uplink carrier for transmission during the process of triggering the corresponding SDT transmission, and select a RACH access-based method or a Configured Grant-based method for uplink data transmission.

[0101] In some embodiments, the user terminal 42 is also configured to send terminal capability information to the core network via a NAS (Non-Access Stratum) message, wherein the terminal capability information is used to indicate whether the user terminal has the ability to support the transmission of small data packets in an inactivated state, so that the core network sends the terminal capability information to the CU entity of the base station for storage during the context establishment process of the user terminal.

[0102] In some embodiments, the user terminal 42 is further configured to determine whether it is necessary to configure ConfiguredGrant resources for both SUL and NUL at the same time when both SUL and NUL meet the conditions for configuring ConfiguredGrant resources, based on the indication information of whether the transmitter switching function is supported included in the second terminal context release command message; if it is necessary to configure ConfiguredGrant resources for both SUL and NUL at the same time, configure ConfiguredGrant resources for SUL and NUL; if it is not necessary to configure ConfiguredGrant resources for both SUL and NUL at the same time, select one carrier between SUL and NUL based on the RSRP threshold for the SUL carrier in the first RRC release message, and delete the ConfiguredGrant resources in the unselected carrier.

[0103] In some embodiments, the functional unit module described above can be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components or any appropriate combination thereof for performing the functions described in the present disclosure.

[0104] The present disclosure is described below through specific examples.

[0105] Embodiment 1

[0106] like Figure 5 As shown, this embodiment mainly describes the process of initially configuring the inactive state in the CU / DU separation base station scenario, where the CU instructs the DU to configure DRB1 as SDT. In the F1 interface, each DRB between the CU and the DU has an independent user plane transmission channel. The UE (User Equipment) does not support the Tx Switching function.

[0107] In step 501, the CU entity determines, based on the terminal capabilities, that the UE has the ability to support transmission of small data packets in an inactivated state, and generates a first RRC release message when the UE is about to enter an inactivated state and has a service that can be configured as SDT, while keeping the UE context from being released.

[0108] The first RRC release message includes the following information in addition to the information defined by the protocol:

[0109] -Configure the bearer identifier list of SDT: DRB1

[0110] -Select the SDT data volume trigger threshold: 100Kbyte.

[0111] -Select ConfiguredGrant based and RACH based RSRP threshold: an integer RSRP value: -101dB

[0112] -Select RSRP threshold for ConfiguredGrant-based and RACH-based schemes (for SUL carrier): an integer RSRP value: -98dB

[0113] In step 502, the CU entity sends a UE Context Release Command message to the DU entity via the F1 interface between the CU entity and the DU entity. In addition to the first RRC release message, the UE Context Release Command message also includes:

[0114] -UE RSRP measurement information:

[0115] -Uplink carrier configuration information: NUL

[0116] - Bottom layer information configuration hold indication: hold

[0117] -DRB maintains a list including the following:

[0118] DRB1

[0119] ●List of uplink F1 interface channel addresses to be maintained

[0120] In step 503, after receiving the UE Context Release Command message, the DU entity determines part of the configuration information related to the cell and underlying resource configuration, and adds the part of the configuration information to the first RRC release message to generate a second RRC release message.

[0121] Since DRB1 needs to be configured as an SDT bearer, the uplink carrier configuration that can be used by the UE is updated according to the uplink carrier configuration information, and the physical layer configuration information corresponding to the uplink carrier is generated.

[0122] For each uplink carrier configuration information, the DU entity also needs to determine on which carrier the ConfiguredGrant resources need to be configured or deleted, and fill the relevant configuration information into the RRC release message sent to the UE. For example, first determine the UE's most recent level strength, which can be derived from the "terminal RSRP measurement result information" carried in the interface message. Then, based on the RSRP level strength, the terminal movement speed estimated by the base station side, and the remaining duration of the terminal TA timer timeout, determine the possible RSRP range before the terminal times out [RSRP max , RSRP min ]. If, for NUL, the lower limit value of the corresponding RSRP range is greater than the configuration threshold of the corresponding candidate uplink carrier, it is determined that NUL needs to be configured with ConfiguredGrant resources.

[0123] The DU entity determines whether to maintain the physical layer / MAC / RLC layer configuration corresponding to the UE according to the underlying information configuration retention indication information, and clears the relevant timers and caches. At the same time, the bearers that do not need to be deleted and the user plane transmission channels of these bearers between the CU entity and the DU entity are determined according to the DRB retention list, and the physical layer / MAC / RLC layer resources and related timers and interface resources involved in the bearers not in the list are deleted.

[0124] In step 504, after completing the configuration of related resources, the DU entity notifies the CU of the configuration result through a UE Context Release Complete message.

[0125] In step 505, the DU entity sends a second RRC Release message to the terminal.

[0126] In step 506, after receiving the second RRC release message, the UE performs corresponding resource configuration:

[0127] ■ Record SDT-related parameter configurations, determine whether the user terminal uses one uplink carrier or multiple uplink carriers according to the uplink carrier configuration information, and configure the relevant resources in the physical layer and MAC layer mapped to the uplink carrier used by the user terminal. For the physical layer, reserve the uplink PRACH resources and GonfiguredGrant resources to be configured on the corresponding carrier, and delete other timers and configuration resources in the physical layer

[0128] ■Reset the user plane data of the MAC layer, clear all caches and reset the timer

[0129] ■For the RLC layer, only reconfigure SRB1 and delete the parameter configurations of other DRBs and SRBs.

[0130] ■Suspend operation on PDCP

[0131] ■Save SDT-related configuration information, SDT transmission and triggering thresholds and conditions

[0132] Embodiment 2

[0133] like Figure 6 As shown, this embodiment describes the process of releasing the related SDT configuration between the DU entity and the CU entity after the TA timer expires in the CU / DU separation base station scenario. In the F1 interface, each DRB between the CU entity and the DU entity has an independent user plane transmission channel. The UE does not support the Tx Switching function.

[0134] In step 601, since DRB1 is configured as an SDT bearer with uplink data to be sent and the TA has not timed out, when the data volume is less than 100k bytes, the corresponding SDT transmission process is triggered. The UE first selects the uplink carrier to be transmitted according to the configuration information, and then selects the ConfiguredGrant method for uplink data transmission.

[0135] In step 602, after receiving the uplink data sent by the UE, the DU entity instructs the terminal to update the TA timer through the MAC CE in the downlink direction.

[0136] In step 603, the DU entity determines the DRB corresponding to the uplink data according to the received logical channel identifier of the user in the uplink transmission, and sends the uplink data to the CU entity through the corresponding DRB channel between the DU and the CU.

[0137] In step 604, when the TA timer of the UE configured in the DU entity times out, all physical layer / MAC / RLC layer configuration resources of the UE for SDT are deleted.

[0138] In step 605, the DU entity instructs the CU entity to release high-layer related resources through a UE CONTEXT RELEASE REQUEST message, wherein the message carries an indication information of 1, indicating that the SDT has been released.

[0139] In step 606, after receiving the UE CONTEXT RELEASE REQUEST message, the CU entity determines according to the indication information that the DU entity has released the SDT-related resources, and then the CU entity releases the SDT-related resource configuration information on the control plane and the PDCP side, and only retains the context information of the terminal.

[0140] In step 607, the CU entity sends a UE CONTEXT RELEASE COMMAND message to the DU entity without carrying any RRC Release message for sending to the UE. After the message is sent, the user plane transmission channel between the CU entity and the DU entity allocated by the CU entity to the terminal is recovered.

[0141] In step 608, after receiving the UE CONTEXT RELEASE COMMAND message, the DU entity deletes the user plane transmission channel between the CU entity and the DU entity allocated by the CU entity to the terminal.

[0142] By implementing the above embodiments of the present disclosure, the following beneficial effects can be obtained:

[0143] 1) In the CU / DU separation scenario, the present invention configures the CU and DU to ensure that the SDT-related configuration information can be configured between the CU / DU / UE, defines the relevant behaviors and information of the CU and DU in the SDT scenario, and solves the temporarily undefined parts in the current protocol.

[0144] 2) The present disclosure is used to solve the problem of how to reconfigure or configure multiple uplink carriers when the terminal returns to an inactive state, and how to avoid performance waste caused by the terminal not using the ConfiguredGrant configured on the network side.

[0145] 3) The present disclosure makes little change to the terminal, has good backward compatibility and deployment feasibility. The present disclosure enhances the existing protocol without introducing a new protocol process, and has low implementation difficulty.

[0146] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0147] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A method for reducing access delay, the method being performed by a base station, comprising: The CU entity of the base station determines, according to the capability of the user terminal, whether the user terminal has the capability to support transmission of small data packets in an inactive state; If the user terminal has a capability of supporting transmission of small data packets in an inactive state, when the user terminal is about to enter an inactive state and an SDT bearer is configured, generating a first RRC release message; The CU entity sends a first terminal context release command message to the DU entity of the base station, wherein the first terminal context release command message includes the first RRC release message; After receiving the first terminal context release command message, the DU entity determines part of the configuration information related to the cell and the underlying resource configuration, and adds the part of the configuration information to the first RRC release message to generate a second RRC release message; The DU entity sends the second RRC release message to the user terminal and reserves resources related to the user terminal, so that the user terminal performs resource configuration according to the second RRC release message, enters an inactivated state, and selects corresponding resources for uplink transmission and remains in an inactivated state when uplink data needs to be sent; The determining of part of the configuration information related to the cell and underlying resource configuration includes: If at least one DRB bearer needs to be configured as an SDT, the DU entity updates or reconfigures the uplink carrier used by the user terminal according to the uplink carrier configuration information, and generates physical layer configuration information corresponding to the uplink carrier; With respect to the uplink carrier configuration information, the DU entity determines the carrier for which the ConfiguredGrant resources need to be configured or deleted, and adds the relevant configuration information to the first RRC release message.

2. The method according to claim 1, wherein: The first RRC release message includes configuring a bearer identifier list for SDT, selecting a data volume trigger threshold for SDT, selecting an RSRP threshold based on ConfiguredGrant and / or based on a RACH scheme, selecting an RSRP threshold for a SUL carrier based on ConfiguredGrantt and / or based on a RACH scheme, and at least one of the validity period threshold of ConfiguredGrant.

3. The method according to claim 1, further comprising: After generating the first RRC release message, the CU entity also retains the context information of the user terminal and the PDCP layer related configuration.

4. The method according to claim 1, wherein: The first terminal context release command message also includes: RSRP measurement information of the user terminal, uplink carrier configuration information, underlying information configuration retention indication information, indication information of whether a transmitter switching function is supported, and at least one item in a DRB retention list, wherein the uplink carrier configuration information includes NUL, SUL, or both SUL and NUL carriers, and the underlying information configuration retention indication information includes a retention indication or a release indication, and the retention indication indicates that the DU entity needs to maintain the physical layer, MAC layer, and RLC layer resources of the user terminal. When the indication information of whether the transmitter switching function is supported is 1, it indicates that the user terminal can use the uplink resources of SUL and NUL at the same time during the access process, and the transmitter of the user terminal supports switching between SUL and NUL carriers. When it is 0 or not carried, it indicates that it only supports working on one uplink carrier, and the DRB retention list includes one or more DRB identifiers and at least one item in the channel address list of the maintained uplink F1 interface.

5. The method according to claim 4, wherein: The DU entity determines that the carrier for which the ConfiguredGrant resources need to be configured or deleted includes: The DU entity determines the RSRP level strength of the user terminal; Determine the RSRP range of the user terminal before timeout according to the RSRP level strength, the estimated movement speed of the user terminal and the remaining time length of the TA timer of the user terminal; Determine a candidate uplink carrier for configuring ConfiguredGrant resources according to the uplink carrier configuration information; For each candidate uplink carrier, determining whether a lower limit value of the RSRP range is greater than a configuration threshold of the corresponding candidate uplink carrier; If the lower limit value of the RSRP range is not greater than the configuration threshold of the corresponding candidate uplink carrier, the ConfiguredGrant resources on the candidate uplink carrier are deleted.

6. The method according to claim 5, wherein: The DU entity determines the RSRP level strength of the user terminal including: The DU entity calculates the RSRP level strength of the user terminal by using the RSRP measurement information of the user terminal included in the first terminal context release command message or the signal strength received by the DU entity when the user terminal last sent uplink data.

7. The method according to claim 5, further comprising: If both the SUL and the NUL meet the conditions for configuring the ConfiguredGrant resources, determining whether it is necessary to configure the ConfiguredGrant resources for the SUL and the NUL at the same time according to the indication information of whether the transmitter switching function is supported included in the first terminal context release command message; If it is necessary to configure ConfiguredGrant resources for both the SUL and the NUL, configure ConfiguredGrant resources for the SUL and the NUL; If it is not necessary to configure ConfiguredGrant resources for both the SUL and the NUL, a carrier is selected from the SUL and the NUL according to the RSRP threshold for the SUL carrier in the first RRC release message, and the ConfiguredGrant resources in the unselected carrier are deleted.

8. The method according to claim 4, further comprising: The DU entity uses the underlying information configuration retention indication information included in the first terminal context release command message to maintain or release the configuration resources of the physical layer, MAC layer and RLC layer corresponding to the user terminal, and clears the corresponding timer and cache.

9. The method according to claim 8, further comprising: The DU entity determines the bearer that does not need to be deleted and the user plane transmission channel between the DU entity and the CU entity by using the DRB retention list included in the first terminal context release command message; Delete the configuration resources of the physical layer, MAC layer and RLC layer associated with the bearer not included in the DRB retention list, and clear the corresponding timer and interface resources.

10. The method according to claim 1, further comprising: After completing resource configuration, the DU entity sends a terminal context release completion message to the CU entity, where the terminal context release completion message includes the resource configuration result.

11. The method according to claim 1, further comprising: If one or more DRBs need to be configured as SDT, the DU entity determines whether the user terminal uses one uplink carrier or multiple uplink carriers according to the uplink carrier configuration information, and configures the relevant resources in the physical layer and MAC layer mapped to the uplink carrier used by the user terminal, and reserves the uplink PRACH resources and GonfiguredGrant resources to be configured on the corresponding carrier for the physical layer, deletes other timers and configuration resources of the physical layer; resets the user plane data of the MAC layer, clears all caches and resets the timers; For the RLC layer, only SRB1 is reconfigured, and the parameter configurations of other DRBs and SRBs are deleted; configuration information related to SDT, SDT transmission, and the thresholds and conditions for triggering are saved; The CU entity performs a suspend operation on the PDCP.

12. The method according to any one of claims 1 to 11, further comprising: After receiving the uplink data sent by the user terminal, the DU entity instructs the user terminal to update the TA timer through the MAC CE in the downlink direction; The DU entity determines the DRB corresponding to the uplink data according to the logical channel identifier of the user terminal related to the uplink transmission, and sends the uplink data to the CU entity using the DRB corresponding to the uplink data; After detecting that the TA timer of the user terminal has timed out, the DU entity releases resources related to the SDT and sends a terminal context release request message to the CU entity; After the CU entity determines that the DU entity has released the resources related to the SDT according to the indication information included in the terminal context release request message, it releases the resource configuration information related to the SDT and only retains the context of the user terminal.

13. The method according to claim 12, further comprising: The CU entity sends a second terminal context release command message to the DU entity, and deletes the corresponding user plane transmission channel; After receiving the second terminal context release command message, the DU entity deletes the corresponding user plane transmission channel.

14. The method according to claim 12, further comprising: After receiving the uplink data sent by the user terminal, the DU entity sends the uplink data to the CU entity through the reserved uplink F1 interface.

15. A base station, comprising: a memory configured to store instructions; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 1 to 14 based on instructions stored in the memory.

16. A communication system comprising: The base station as claimed in claim 15; The user terminal is configured to perform resource configuration according to the second RRC release message sent by the DU entity of the base station, and enter an inactivated state, and select corresponding resources for uplink transmission and remain in an inactivated state when uplink data needs to be sent.

17. The system of claim 16, wherein: The user terminal is configured to determine whether the user terminal uses one uplink carrier or multiple uplink carriers according to the uplink carrier configuration information if the second RRC release message indicates that one or more DRBs are configured as SDT, and configure the relevant resources in the physical layer and MAC layer mapped by the uplink carrier used by the user terminal, and reserve the uplink PRACH resources and GonfiguredGrant resources to be configured on the corresponding carrier for the physical layer, and delete other timers and configuration resources of the physical layer; reset the user plane data of the MAC layer, clear all caches and reset the timers; For the RLC layer, only SRB1 is reconfigured and the parameter configurations of other DRBs and SRBs are deleted; Suspend PDCP; save SDT-related configuration information, SDT transmission, and triggering thresholds and conditions.

18. The system of claim 16, wherein: The user terminal is also configured to trigger corresponding SDT transmission when there is uplink data to be sent on the bearer configured as SDT and the TA timer has not timed out and if the data volume of the uplink data is less than the corresponding threshold specified in the second RRC release message.

19. The system of claim 18, wherein: The user terminal is further configured to select an uplink carrier for transmission during the process of triggering the corresponding SDT transmission, and select a RACH access-based method or a Configured Grant-based method for uplink data transmission.

20. The system of claim 16, wherein: The user terminal is also configured to send terminal capability information to the core network via a NAS message, wherein the terminal capability information is used to indicate whether the user terminal has the ability to support the transmission of small data packets in an inactivated state, so that the core network sends the terminal capability information to the CU entity of the base station for storage during the context establishment process of the user terminal.

21. The system of claim 16, wherein: The user terminal is also configured to determine whether it is necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time if the conditions for configuring ConfiguredGrant resources are met for both the SUL and the NUL according to the indication information of whether the transmitter switching function is supported included in the second terminal context release command message; if it is necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time, configure ConfiguredGrant resources for the SUL and the NUL; if it is not necessary to configure ConfiguredGrant resources for both the SUL and the NUL at the same time, select a carrier between the SUL and the NUL according to the RSRP threshold for the SUL carrier in the first RRC release message, and delete the ConfiguredGrant resources in the unselected carrier.

22. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 14 is implemented.