A RedCap PDCCH Resource Allocation Method and Related Devices

Abstract

The present application discloses a RedCap PDCCH resource allocation method and related devices, relating to the field of 5G private networks, including: based on the terminal information of the terminal waiting for scheduling, determining whether the terminal is a RedCap terminal; if so, allocating a target C-RNTI to the terminal, and the first candidate CCE in the CCE candidate set associated with the target C-RNTI is the USS CCE within the preset bandwidth supported by the RedCap terminal; if not, allocating a spare C-RNTI to the terminal, and the first candidate CCE in the CCE candidate set associated with the spare C-RNTI is the CCE outside the preset bandwidth. The present application preferentially allocates C-RNTIs associated with CCEs of different bandwidth types to different types of terminals, enabling RedCap terminals to be preferentially allocated CCEs within the preset bandwidth, reducing the probability of CCEs within the bandwidth being preempted, and improving the allocation success rate of RedCap terminals.

Description

Technical Field

[0001] This application relates to the technical field of 5G private networks, and more specifically, to a RedCap PDCCH resource allocation method and related devices. Background Art

[0002] In a 5G private network base station, the PDCCH (Physical Downlink Control Channel) is a set of physical resource particles used to carry the control information (DCI) of the PUSCH (Physical Uplink Shared Channel) and PDSCH (Physical Downlink Shared Channel). This control information guides the transmission and reception of data. The DCI requires the base station to find idle CCEs on the PDCCH channel to carry the DCI. If no idle CCEs can be found, the data transmission between the base station and the user fails this time.

[0003] However, the CCE is the basic physical resource unit of the PDCCH, and the number of CCEs in the PDCCH is limited by the size of the BWP (Bandwidth Part). Therefore, the number of CCEs in the PDCCH has become a resource bottleneck for the base station to schedule user data, especially for narrowband IoT user terminals. For example, to meet the medium and low demands of the market, RedCap terminals support a relatively small BWP, which means that the available bandwidth resources are limited. Since the PDCCH needs to occupy a certain amount of bandwidth resources to transmit DCI, when the BWP is small, the bandwidth that the PDCCH can occupy will also decrease accordingly, and the available number of CCEs in the PDCCH will also decrease. When the number of available CCEs for RedCap terminals is small, they also have to face the preemption of CCE resources by the CSS (Common Search Space) and nonRedCap USS (User Search Space), resulting in a reduced success rate of allocating idle CCEs to RedCap terminals and a corresponding reduction in the success rate of data transmission.

[0004] Based on this, how to improve the success rate of allocating idle CCEs to RedCap terminals has become an urgent problem to be solved. Summary of the Invention

[0005] In view of the above problems, this application provides a RedCap PDCCH resource allocation method and related devices to achieve the purpose of improving the success rate of allocating idle CCEs to RedCap terminals. The specific solutions are as follows:

[0006] The first aspect of this application provides a RedCap PDCCH resource allocation method applied to a base station. The RedCap PDCCH resource allocation method includes:

[0007] Obtain the terminals waiting for scheduling and the terminal information of the terminals;

[0008] Based on the terminal information, determine whether the terminal is a RedCap terminal;

[0009] When the terminal is the RedCap terminal, allocate a pre-partitioned target cell radio network temporary identifier C-RNTI to the RedCap terminal, so that the RedCap terminal performs PDCCH blind detection on a target CCE candidate set associated with the target C-RNTI. The target CCE candidate set is a set of CCEs with the available USS CCE within a preset bandwidth as the first candidate CCE, and the preset bandwidth is the bandwidth supported by the RedCap terminal;

[0010] When the terminal is not the RedCap terminal, allocate a pre-partitioned spare C-RNTI to the terminal, so that the terminal performs PDCCH blind detection on a spare CCE candidate set associated with the spare C-RNTI. The spare CCE candidate set is a set of CCEs with the CCE outside the preset bandwidth as the first candidate CCE.

[0011] In a possible implementation, the process of pre-partitioning the target C-RNTI and the spare C-RNTI includes:

[0012] Determine the USS CCE with the USS available state within the preset bandwidth supported by the RedCap terminal as the available USS CCE;

[0013] Query the first candidate CCE in the CCE candidate set associated with each C-RNTI in the base station;

[0014] Determine the C-RNTI associated with the CCE candidate set whose first candidate CCE is the available USS CCE as the target C-RNTI;

[0015] Classify the target C-RNTI to obtain at least one target C-RNTI set, and the first candidate CCE of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set is the same USS CCE;

[0016] Generate a spare C-RNTI set based on the C-RNTI other than the target C-RNTI among all C-RNTIs in the base station.

[0017] In a possible implementation, the step of allocating a pre-partitioned target cell radio network temporary identifier (C-RNTI) to the RedCap terminal includes:

[0018] Determine a target C-RNTI set from the at least one target C-RNTI set;

[0019] Identify the usage status of the candidate CCE set associated with each target C-RNTI in the target C-RNTI set, and obtain at least one target C-RNTI with an unused status;

[0020] Allocate the target C-RNTI ranked first among the at least one target C-RNTIs with an unused status to the RedCap terminal.

[0021] In a possible implementation, after allocating the target C-RNTI ranked first among the at least one target C-RNTIs with an unused status to the RedCap terminal, the following steps are further included:

[0022] Mark the target C-RNTI allocated to the RedCap terminal as being in use;

[0023] After the resource scheduling of the RedCap terminal is completed, mark the target C-RNTI allocated to the RedCap terminal as being unused.

[0024] In a possible implementation, the step of determining the USS CCE with an available USS status within the preset bandwidth supported by the RedCap terminal as the available USS CCE includes:

[0025] Initialize all USS CCEs within the preset bandwidth supported by the RedCap terminal to obtain USS CCEs with an initial status of available USS;

[0026] Obtain the PDCCH parameters in the base station configuration data for characterizing the CCE occupancy situation

[0027] Based on the PDCCH parameters, determine the REG Bundle occupied by the CSS;

[0028] Mark the initial status of the USS CCE containing the REG Bundle occupied by the CSS as unavailable USS;

[0029] Determine the remaining USS CCEs except for the USS CCEs with an unavailable USS status among all the USS CCEs within the preset bandwidth of the RedCap terminal as the available USS CCEs.

[0030] In a possible implementation, it further includes:

[0031] In response to the PDCCH blind detection result of not finding an idle CCE sent by the RedCap terminal, mark the priority of the RedCap terminal and put the RedCap terminal into a cache, where the cache is used to store terminals waiting for scheduling, and the priority represents the priority degree of the RedCap terminal being scheduled.

[0032] The second aspect of this application provides a RedCap PDCCH resource allocation device, which is applied to a base station. The RedCap PDCCH resource allocation device includes:

[0033] A terminal information acquisition unit, configured to acquire terminals waiting for scheduling and the terminal information of the terminals;

[0034] A terminal type determination unit, configured to determine whether the terminal is a RedCap terminal based on the terminal information;

[0035] A C-RNTI allocation first unit, configured to, when the terminal is the RedCap terminal, allocate a pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal, so that the RedCap terminal performs PDCCH blind detection on a target CCE candidate set associated with the target C-RNTI, where the target CCE candidate set is a set of CCEs with the available USS CCE within a preset bandwidth as the first candidate CCE, and the preset bandwidth is the bandwidth supported by the RedCap terminal;

[0036] A C-RNTI allocation second unit, configured to, when the terminal is not the RedCap terminal, allocate a pre-divided spare C-RNTI to the terminal, so that the terminal performs PDCCH blind detection on a spare CCE candidate set associated with the spare C-RNTI, where the spare CCE candidate set is a set of CCEs with the CCE outside the preset bandwidth as the first candidate CCE.

[0037] The third aspect of this application provides a RedCap PDCCH resource allocation device, including at least one processor and a memory connected to the processor, where:

[0038] The memory is used to store a computer program;

[0039] The processor is used to execute the computer program, so that the RedCap PDCCH resource allocation device can implement the RedCap PDCCH resource allocation method in the first aspect or any implementation manner of the first aspect.

[0040] The fourth aspect of the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by a RedCap PDCCH resource allocation device, the RedCap PDCCH resource allocation device can implement the RedCap PDCCH resource allocation method of the above-mentioned first aspect or any implementation method of the first aspect.

[0041] A fifth aspect of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the RedCap PDCCH resource allocation method of the above-mentioned first aspect or any implementation manner of the first aspect.

[0042] It can be seen from the above technical solution that the RedCap PDCCH resource allocation method and related equipment provided in the embodiment of the present application take into account that the USS CCEs within the bandwidth supported by the RedCap terminal are relatively small and there is a situation where they are preempted by non-RedCap terminals or CSS. Therefore, when the terminal accesses the base station, the base station allocates different CCE candidate sets to the terminal according to the type of terminal.

[0043] If the access terminal is a RedCap terminal, the target C-RNTI associated with the CCE candidate set with the USS CCE within the preset bandwidth supported by the RedCap terminal as the first candidate CCE is allocated to the RedCap terminal; if the terminal is not a RedCap terminal, the standby C-RNTI associated with the CCE candidate set with the CCE outside the preset bandwidth as the first candidate CCE is allocated to the terminal. Based on this, CCE candidate sets of different bandwidth types are preferentially allocated to different terminals, so that RedCap terminals can be preferentially allocated to the CCE candidate set within the preset bandwidth, reducing the probability of CCE being preempted within the bandwidth and improving the allocation success rate of RedCap terminals.

[0044] In addition, after the target CCE candidate set is allocated to the RedCap terminal, since the USS CCE candidate positions within the preset bandwidth in the target CCE candidate set are ranked first, the RedCap terminal blind detection can demodulate to the available USS CCE faster, thereby improving the terminal's blind detection efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present application 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 embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0046] Figure 1 An example diagram of a PDCCH resource allocation method provided by an embodiment of the present application;

[0047] Figure 2 A schematic flowchart of implementing a RedCap PDCCH resource allocation method provided by an embodiment of the present application;

[0048] Figure 3 An example diagram showing the CCE occupancy provided by an embodiment of the present application;

[0049] Figure 4 An example diagram of a RedCap PDCCH resource allocation method provided by an embodiment of the present application;

[0050] Figure 5 A schematic structural diagram of a RedCap PDCCH resource allocation device provided by an embodiment of the present application;

[0051] Figure 6 A schematic structural diagram of a RedCap PDCCH resource allocation device provided by an embodiment of the present application. Detailed implementation manners

[0052] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0053] It should be noted that the terminal in the embodiments of the present application represents a user equipment (UE), and nonRedCap UE represents a non-Narrowband Internet of Things user terminal. For example, a user terminal with a bandwidth greater than that of a RedCap terminal.

[0054] Referring to Figure 1 , an example diagram of a PDCCH resource allocation method provided by an embodiment of the present application is used to illustrate the conventional PDCCH resource allocation method. The base station sequentially allocates the C-RNTIs in the C-RNTI set CRNTI_POOL according to the access order of the terminals. Among them, C-RNTI (Cell Radio Network Temporary Identifier) is used for dynamically scheduling PDSCH transmission, and each C-RNTI is associated with a different CCE candidate set. As Figure 1, according to the access order of terminals UE1, UE2, UE3, and UE4, the base station sequentially assigns C-RNTI_0 to C-RNTI_3 to UE1 to UE4. Further, the base station sequentially checks the occupancy status of the CCEs in the candidate set of PDCCH CCE resources associated with the C-RNTI assigned to the terminal, and sends the C-RNTI associated with the idle CCE obtained from the check to the terminal, so as to use the idle CCE obtained from the check to send DCI to the terminal. The terminal needs to first perform blind detection on the PDCCH to demodulate the DCI information sent by the base station on the PDCCH channel before it can obtain the time-frequency resources for its uplink or downlink data transmission.

[0055] Compared with the BWP of traditional terminals, the total number of resources that can be allocated for USS CCE of RedCap terminals is less. When the base station allocates PDCCH resources to RedCap terminals, it also needs to face resource preemption by CSS and nonRedCap USS, resulting in fewer available CCE resources for RedCap terminals and a lower success rate of allocating idle CCEs, increasing the resource scheduling failure rate between RedCap terminals and the base station.

[0056] To solve the above problems, the embodiments of the present application provide a RedCap PDCCH resource allocation method, which is applied to a base station. Referring to Figure 2 , a schematic flowchart of a process for implementing the RedCap PDCCH resource allocation method provided by the embodiments of the present application is used to illustrate the implementation process of the RedCap PDCCH resource allocation method. Specifically, refer to the following content:

[0057] Step S110, obtain the terminals waiting for scheduling and the terminal information of the terminals.

[0058] The terminals waiting for scheduling can be the terminals accessing the base station at the current moment, or the terminals stored in the cache that failed the previous scheduling and are waiting for re-scheduling. The terminal information can at least include: terminal identification information, an identifier representing the terminal type, the network type requested by the terminal to access, terminal location information, security information, etc.

[0059] If the terminal waiting for scheduling is the terminal accessing the base station at the current moment, the base station will receive a handshake message sent by the terminal. Here, the handshake message refers to a signal or message used to establish a reliable connection or confirm the status of each other between the two communication parties. Based on this handshake message, the base station can receive the connection request of the terminal, as well as information such as the identifier of the terminal, the network type requested to access, and the initial sequence number of the terminal.

[0060] For example, in the field of wireless communication, in the RACH (Random Access Channel) process for establishing an initial connection or re - establishing a connection between a UE and a base station (such as a gNB), the terminal establishes a connection with the base station by sending a handshake message to the base station. When the terminal has an uplink data transmission requirement, it sends Msg1 to the base station to request access to the base station. After receiving Msg1, the base station prepares Msg2 to be sent to the terminal based on the terminal information carried in Msg1 and the current resource usage situation, to achieve PDCCH resource allocation.

[0061] If the terminal waiting for scheduling is the terminal that failed the previous scheduling and is waiting for re - scheduling and is stored in the buffer, since the terminal in the buffer is the terminal that failed the previous scheduling and has obtained terminal information during the previous allocation process, the terminal information can be directly obtained from the buffer without the terminal sending handshake information again.

[0062] Step S120, based on the terminal information, determine whether the terminal is a RedCap terminal. If the determination result is yes, execute step S130; if the determination result is no, execute step S131.

[0063] Based on the identification information indicating the terminal type in the terminal information, such as Preamble ID, identify the terminal type of the terminal waiting for scheduling. The embodiments of the present application are mainly used to solve the problem of resource allocation for RedCap terminals. Therefore, identify whether the terminal waiting for scheduling is a RedCap terminal.

[0064] It can be understood that if the embodiments of the present application solve the problem of low success rate of PDCCH resource allocation for narrow - band Internet of Things user terminals, then the terminal type or terminal bandwidth in the terminal information can be used to identify whether the terminal waiting for scheduling is a narrow - band Internet of Things user terminal, and the PDCCH resource allocation method for narrow - band Internet of Things user terminals is also applicable below.

[0065] Step S130, allocate the pre - divided target C - RNTI to the RedCap terminal.

[0066] Step S131, allocate the pre - divided spare C - RNTI to the terminal.

[0067] It can be understood that the base station contains multiple C - RNTIs, each C - RNTI is associated with a CCE candidate set, and the CCE candidate set contains at least one candidate CCE. In the embodiments of the present application, the first candidate CCE of the CCE candidate set associated with the target C - RNTI is the available USS CCE within the preset bandwidth, and the first candidate CCE of the CCE candidate set associated with the spare C - RNTI is the CCE outside the preset bandwidth, where the preset bandwidth is the bandwidth supported by the RedCap terminal.

[0068] It can be understood that the RedCap terminal can only use the USS CCE within the preset bandwidth, while there is no special restriction on the bandwidth attribute of the CCE for the non-RedCap terminal. Therefore, the CCEs that meet the bandwidth of the RedCap terminal in the base station are limited, and the CCEs within the preset bandwidth are also preempted by the CSS and non-RedCap terminals, resulting in the RedCap terminal being unable to successfully allocate the idle CCE within the preset bandwidth. In the embodiments of the present application, the idle CCE can be understood as the available CCE. Similarly, the available USS CCE is the idle and unoccupied USS CCE.

[0069] Based on this, in the embodiments of the present application, the CCE candidate set including the available USS CCE within the preset bandwidth is pre-listed as the target CCE candidate set, the C-RNTI associated with the target CCE candidate set is used as the target C-RNTI, the CCE candidate set including the CCE outside the preset bandwidth is listed as the standby CCE candidate set, and the C-RNTI associated with the standby CCE candidate set is used as the standby C-RNTI. When performing resource allocation, the target CCE candidate set associated with the target C-RNTI is preferentially allocated to the RedCap terminal, while the non-RedCap terminal is preferentially allocated the standby CCE candidate set associated with the standby C-RNTI, avoiding the situation where the non-RedCap terminal preempts the limited USS CCE within the preset bandwidth, reducing the possibility of the non-RedCap terminal preempting the USS CCE within the preset bandwidth, and improving the success rate of the RedCap terminal in preempting the USS CCE within the preset bandwidth.

[0070] Moreover, since the target candidate sets associated with the target C-RNTI selected in the embodiments of the present application all use the available USS CCE within the preset bandwidth as the first candidate CCE, when the base station checks the resources in the target candidate set, it can quickly find and preempt the CCE that meets the requirements, improving the preemption speed and further improving the success rate of the RedCap terminal in allocating the USS CCE within the preset bandwidth.

[0071] It can be understood that the CCE candidate set contains multiple candidate CCEs. When the base station performs PDCCH search, it checks the status in the order of the candidate CCEs in the CCE candidate set. If the available CCE is arranged in the first place, the PDCCH search only needs one status check to lock the available CCE and allocate this CCE to the terminal. However, if the sorting order of the available CCE is relatively backward, the PDCCH search needs to perform multiple status checks to lock the available CCE. And if other terminals access the base station during the PDCCH search process, this available CCE may be preempted by other terminals, and finally the PDCCH search result for this CCE candidate set is empty, that is, the scheduling of the terminal data fails. Therefore, determining the target C-RNTI associated with the CCE candidate set of the target CCE, which is the USS CCE within the preset bandwidth, as the first candidate CCE, can improve the success rate of the base station preempting CCEs for RedCap terminals.

[0072] In addition, since the USS CCE within the preset bandwidth in the target candidate set is the first candidate CCE, after the target C-RNTI associated with the target CCE candidate set is allocated to the RedCap terminal, the terminal can lock the idle CCE with only one check during the PDCCH blind detection process, reducing the number of blind detections and the blind detection time, and reducing the possibility of the idle CCE being preempted by other terminals, thereby improving the success rate of the RedCap terminal being allocated an idle CCE.

[0073] Furthermore, the base station performs PDCCH resource check on the target CCE candidate set or the spare CCE candidate set associated with the C-RNTI allocated to the terminal. Under normal circumstances, it sequentially checks the status of the CCEs in the CCE candidate set. If an idle CCE is detected, it can be determined that the CCE candidate set associated with this C-RNTI is available, and the C-RNTI is allocated to the terminal for subsequent operations such as DCI demodulation and resource scheduling of the idle CCE. If the number of checks reaches the maximum number of checks, or no idle CCE is detected after traversing the checks, then this PDCCH check fails, and the terminal cannot be allocated a CCE, and the resource scheduling fails.

[0074] In the embodiment of this application, the target C-RNTI is sent to the RedCap terminal, and the RedCap terminal performs PDCCH blind detection on the target CCE candidate set associated with the target C-RNTI. After obtaining an idle CCE through blind detection, resource allocation and scheduling with the base station are realized based on the idle CCE.

[0075] However, there is also a possibility that the terminal fails to detect an idle CCE from the target CCE candidate set associated with the allocated target C-RNTI, and resource scheduling fails. In response to the PDCCH blind detection result sent by the RedCap terminal that no idle CCE is found, the base station marks the priority of the RedCap terminal and puts the RedCap terminal into a cache. The cache is used to store terminals waiting for scheduling, and the priority is used to represent the priority of the RedCap terminal to be scheduled.

[0076] When the base station needs to start processing the terminals that failed to be scheduled last time and stored in the cache, or the terminals that are waiting to be scheduled and stored in the cache, first, the base station identifies whether each terminal has a priority mark, and the base station will give priority to resource allocation to the terminals with priority marks. In the embodiment of the present application, only the RedCap terminals that failed to be scheduled last time are prioritized, so that when the RedCap terminals reallocate resources, they are still allocated before the non-RedCap terminals, thereby increasing the probability of successful allocation.

[0077] In summary, the RedCap PDCCH resource allocation method provided in the embodiment of the present application takes into account that there are fewer USS CCEs within the bandwidth supported by the RedCap terminal, and there is a situation where it is preempted by a non-RedCap terminal or CSS. Therefore, in the embodiment of the present application, when the terminal accesses the base station, the base station allocates different CCE candidate sets to the terminal according to the type of the terminal. Among them, if the access terminal is a RedCap terminal, the target C-RNTI associated with the CCE candidate set with the USS CCE within the preset bandwidth supported by the RedCap terminal as the first candidate CCE is allocated to the RedCap terminal; and if the terminal is not a RedCap terminal, the standby C-RNTI associated with the CCE candidate set with the CCE outside the preset bandwidth as the first candidate CCE is allocated to the terminal. Based on this, CCE candidate sets of different bandwidth types are preferentially allocated to different terminals, so that the RedCap terminal can be preferentially allocated to the CCE candidate set within the preset bandwidth, reducing the probability of CCE being preempted within the bandwidth and improving the success rate of RedCap terminal allocation.

[0078] In addition, after the target CCE candidate set is allocated to the RedCap terminal, since the USS CCE candidate positions within the preset bandwidth in the target CCE candidate set are ranked first, the RedCap terminal blind detection can demodulate to the available USS CCE faster, thereby improving the terminal's blind detection efficiency.

[0079] Next, other possible implementations of the above RedCap PDCCH resource allocation method are described.

[0080] In a possible implementation, the process of pre-dividing the target CCE candidate set and the spare CCE candidate set may include: determining the USS CCE of the available USS status within the preset bandwidth supported by the RedCap terminal as the available USS CCE; querying the first candidate CCE in the CCE candidate set associated with each C-RNTI in the base station; taking the C-RNTI associated with the CCE candidate set whose first candidate CCE is the available USS CCE as the target C-RNTI; classifying the target C-RNTI to obtain at least one target C-RNTI set, where the first candidate CCE of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set is the same USS CCE; generating a spare C-RNTI set based on the C-RNTIs in all C-RNTIs in the base station except the target C-RNTI.

[0081] RedCap belongs to the narrowband Internet of Things technology. The capabilities of the terminal are reduced based on the requirements of the application scenario. The bandwidths of different frequency bands are different, and the corresponding PDCCH resources are also different. Taking the TDD FR1 frequency band as an example, the maximum BWP bandwidth of the RedCap terminal can only support 20 MHz. Without increasing the number of PDCCH symbols, the PDCCH resources corresponding to the RedCap terminal are only 8 CCEs. Therefore, the PDCCH resources corresponding to narrowband Internet of Things user terminals with different bandwidths are also different. Therefore, the process of dividing the target CCE candidate set and the spare CCE candidate set can also be executed after identifying the terminal type to improve the accuracy of candidate set division.

[0082] In the embodiment of the present application, the RedCap terminal is taken as an example. For example, the base station checks the status, bandwidth attribute, etc. of each CCE through resource inspection to determine the available USS CCE among the 8 CCEs corresponding to the RedCap terminal BWP bandwidth. Here, "available" in the embodiment of the present application can be understood as the CCE not occupied by the CSS or non-RedCap terminal.

[0083] Optionally, the process of determining the USS CCE within the bandwidth supported by the RedCap terminal may further include: initializing all USS CCEs within the preset bandwidth supported by the RedCap terminal to obtain USS CCEs with an initial state of USS available; obtaining PDCCH parameters for characterizing CCE occupancy in the base station configuration data; determining the REG Bundle occupied by the CSS based on the PDCCH parameters; marking the initial state of the USS CCE containing the REG Bundle occupied by the CSS as the USS unavailable state; and determining the remaining USS CCEs other than the USS CCEs in the USS unavailable state among all the USS CCEs within the preset bandwidth of the RedCap terminal as the available USS CCEs.

[0084] When the base station performs PDCCH resource allocation, it usually prioritizes the resource allocation of the CSS. Since the CSS PDCCH is in an interleaved mode and the CCE resources it occupies are discontinuously distributed, the available CCEs for the USS PDCCH of the RedCap terminal are reduced. Refer to Figure 3 , the example diagram showing the CCE occupancy provided in the embodiment of the present application. Under normal circumstances, the CCE occupancy is as shown in Figure 3 Pattern1. Coreset p is 8 USS CCEs in the frequency domain of the RedCap BWP. Coreset 0 is the arrangement of the REG Bundles corresponding to the CCEs of the CSS. The CSS and the USS share the same CCE resource pool. Coreset 0 used by the CSS occupies 4 REG Bundles, namely REG Bundle0, REG Bundle1, REG Bundle4, and REG Bundle5. Since Coreset0 is aligned with the starting CRB position in the frequency domain of the RedCap BWP, the corresponding CCE0, 1, 4, 5 of Coreset p are occupied, and the remaining available USS CCEs are: CCE2, CCE3, CCE6, and CCE7. Refer to Pattern2. Since the starting CRB position in the frequency domain of Coresrt 0 and the starting CRB position in the frequency domain of Coresrt p are not aligned, and Coreset 0 also occupies REG Bundle0, 1, 4, 5, CCE0, 1, 2, 4, 5, 6 in Coreset p will all be unavailable, and only 2 USS CCEs are left available, resulting in a reduction in the number of available USS CCEs.

[0085] Therefore, when determining the availability of the USS CCE, it is also necessary to consider the occupancy of the CCE by the REG Bundle corresponding to the CSS. Refer to Figure 4, An example diagram of a RedCap PDCCH resource allocation method provided by an embodiment of the present application, which illustrates the process of dividing and allocating C-RNTI based on CCE. First, an array RedCap Uss Cce List is established, representing the list of CCEs available for the RedCap terminal USS. The array contains 8 elements, representing 8 CCEs respectively. The status of each element is initialized to USS_AVAILABLE, that is, the USS available status.

[0086] Read the PDCCH-related parameters from the base station configuration data. The related parameters at least include: the number of PDCCH symbols, the number of BWPPRB, the number of PDCCH REGs, the REG Bundle size, the PDCCH interleaving Shift sequence number, and the PDCCH interleaving block size. Calculate the REG Bundle sequence numbers occupied by the CSS based on the PDCCH parameter configuration, and the USSCCEs containing these REG Bundle sequence numbers occupied by the CSS are indicated as occupied. For example, Figure 3 in Pattern2, the CRB sequence numbers of CCE1 occupied by the CCS are CRB9-14. If CCE1 and CCE2 in Coreset p respectively contain the occupied CRB9-14, then CCE1 and CCE2 are also in the occupied state, that is, CCE1 and CCE2 in Coreset p can both be confirmed as CCEs that are not available for the USS.

[0087] Modify the initial status of the CCEs that are not available for the USS to USS_NOT_AVAILABLE, indicating the USS not available status. In the array RedCap Uss Cce List, remove the CCEs marked with USS_NOT_AVAILABLE. Then the remaining CCEs marked with USS_AVAILABLE are in the USS available status, denoted as CCE_INDEX_X, that is, the available USS CCEs. In this example, there are two available USS CCEs remaining in the array RedCap Uss Cce List, denoted as: CCE_INDEX_1 and CCE_INDEX_2.

[0088] Further, search for CCE_INDEX_X in the CCE candidate sets associated with all C-RNTIs of the base station. The C-RNTI whose first candidate CCE is CCE_INDEX_X in the associated CCE candidate set is determined as the target C-RNTI, and the target C-RNTIs whose first candidate CCE is the same CCE_INDEX_X are grouped into the target C-RNTI set, denoted as CRNTI_POOL_X.

[0089] For example, find the first candidate CCE in the CCE candidate set associated with each C-RNTI in the base station. The C-RNTIs for which the first candidate CCE in the associated CCE candidate set is CCE_INDEX_1 are: C-RNTI-1 and C-RNTI-2. Then, take C-RNTI-1 and C-RNTI-2 as the target C-RNTIs respectively, and group C-RNTI-1 and C-RNTI-2 into the target C-RNTI set, denoted as CRNTI_POOL_1. Similarly, the combination of C-RNTIs for which CCE_INDEX_2 is the first candidate CCE in the associated CCE candidate set can be denoted as CRNTI_POOL_2.

[0090] When the base station allocates a C-RNTI to a terminal, if the terminal is a RedCap terminal, it can select a target C-RNTI from the target C-RNTI set at random and allocate it to the RedCap terminal. In another possible implementation, first determine a target C-RNTI set from the at least one target C-RNTI set; identify the usage status of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set to obtain at least one target C-RNTI with an unused status; allocate the target C-RNTI ranked first among the at least one target C-RNTIs with an unused status to the RedCap terminal.

[0091] Since each C-RNTI is not distinguished by whether the associated CCE candidate set has been allocated during C-RNTI partitioning, to avoid the situation where the CCE candidate set selected by the RedCap terminal has been used, resulting in the failure of RedCap terminal allocation, in the embodiments of this application, before allocating the target C-RNTI, the target C-RNTIs belonging to the already used CCE candidate sets in the target C-RNTI set are pre-screened, and one is selected from the target C-RNTIs corresponding to the unused CCE candidate sets for allocation. In the embodiments of this application, according to the arrangement order of the target C-RNTIs with an unused status in the target C-RNTI set CRNTI_POOL_X, the one with the smallest arrangement serial number, that is, the first target CCE candidate set, is selected and allocated to the RedCap terminal.

[0092] It can be understood that the target C-RNTI assigned to the RedCap terminal has been used. Therefore, the target C-RNTI assigned to the RedCap terminal is marked as the used state. After the resource scheduling for the RedCap terminal is completed, the target C-RNTI assigned to the RedCap terminal is marked as the unused state to track the usage status of each target C-RNTI and ensure the accuracy of the status of the C-RNTI waiting to be assigned and the assigned C-RNTI. Additionally, the spare C-RNTIs in the spare C-RNTI set are used to be assigned to non-RedCap terminals, and the assignment method can refer to the above-mentioned assignment method for the target C-RNTI set, which will not be elaborated here.

[0093] Refer to Figure 4 , four terminals UE1, UE2, UE3, and UE4 access the base station. Among them, UE1 and UE2 are RedCap terminals, and UE3 and UE4 are non-RedCap terminals. Optionally, one target C-RNTI is selected from CRNTI_POOL_0 and CRNTI_POOL_1 respectively and assigned to UE1 and UE2. Considering that if the target C-RNTIs assigned to UE1 and UE2 both come from the same target C-RNTI set, there may be a possibility that the two terminals preempt the USS CCE within the same preset bandwidth, resulting in one of the terminals being unable to successfully allocate the CCE. Therefore, the target C-RNTIs are selected from two different target C-RNTI sets, that is, the target C-RNTI assigned to UE1 comes from CRNTI_POOL_0, and the target C-RNTI assigned to UE2 comes from CRNTI_POOL_1, improving the success rate of the two RedCap terminals in allocating the CCE.

[0094] Additionally, two unused spare CCE candidate sets are selected from the spare C-RNTI set CRNTI_POOL_2 and assigned to UE3 and UE4 respectively. It can be understood that the nonRedCap terminal supports a larger bandwidth. For example, in TDD FR1, there is a total bandwidth of 100 MHz. After removing 20 MHz for the RedCap terminal to use, there are still CCEs available within the remaining 80M. Therefore, the PDCCH CCE resources of the nonRedCap terminal are relatively rich, and there are more available spare C-RNTIs in CRNTI_POOL_2. Therefore, although the embodiment of the present application preempts the CCE resources within the preset bandwidth in advance and only uses them to be assigned to the RedCap terminal, due to the rich resources within the bandwidth of the nonRedCap terminal, generally there will be no problem of insufficient CCEs. Therefore, while improving the allocation success rate of the RedCap in the embodiment of the present application, it will not reduce the allocation success rate of the nonRedCap.

[0095] In summary, for the RedCap PDCCH resource allocation method provided in the embodiments of the present application, the available USS PDCCH resource positions for the RedCap terminal are pre-calculated, and several CRNTI_Pools are divided accordingly. The C-RNTIs in these Pools are preferentially allocated to the RedCap terminal. Since the available USS CCEs that the terminal can use are strongly correlated with the C-RNTI, using the C-RNTIs in these Pools can highly probably associate with the available USS CCE resources. Moreover, when the RedCap terminal performs PDCCH blind detection, the CCE position that is preferentially demodulated is also the first candidate CCE associated with the C-RNTI allocated by this method, reducing the number of its blind detection attempts.

[0096] Compared with the conventional PDCCH resource allocation method, this method can improve the allocation success rate of RedCap PDCCH resources, which is beneficial for the base station to timely schedule the terminal data. At the same time, it can also improve the blind detection efficiency of the RedCap terminal's PDCCH, which is beneficial for the terminal to save energy.

[0097] Next, the RedCap PDCCH resource allocation device provided in the embodiments of the present application will be described. The RedCap PDCCH resource allocation device described below can be correspondingly referred to the RedCap PDCCH resource allocation method described above.

[0098] First, in combination with Figure 5 , the RedCap PDCCH resource allocation device applied to the base station side will be introduced. As Figure 5 shown, the RedCap PDCCH resource allocation device may include:

[0099] A terminal information acquisition unit 100, configured to acquire the terminal waiting for scheduling and the terminal information of the terminal;

[0100] A terminal type determination unit 200, configured to determine whether the terminal is a RedCap terminal based on the terminal information;

[0101] A first C-RNTI allocation unit 300, configured to, when the determination result of the terminal type determination unit 200 is yes, allocate a pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal, so that the RedCap terminal performs PDCCH blind detection on a target CCE candidate set associated with the target C-RNTI. The target CCE candidate set is a set of CCEs with the available USS CCE within a preset bandwidth as the first candidate CCE, and the preset bandwidth is the bandwidth supported by the RedCap terminal;

[0102] The second C-RNTI allocation unit 400 is used to allocate a pre-allocated spare C-RNTI to the terminal when the judgment result of the terminal type judgment unit 200 is no, so that the terminal performs PDCCH blind detection on the spare CCE candidate set associated with the spare C-RNTI, and the spare CCE candidate set is a CCE set that uses the CCE outside the preset bandwidth as the first candidate CCE.

[0103] To summarize, the embodiments of the present application take into account that the USS CCEs within the bandwidth supported by RedCap terminals are relatively small and may be preempted by non-RedCap terminals or CSS. Therefore, when a terminal accesses a base station, the base station allocates different CCE candidate sets to the terminal according to the type of the terminal.

[0104] If the access terminal is a RedCap terminal, the target C-RNTI associated with the CCE candidate set with the USS CCE within the preset bandwidth supported by the RedCap terminal as the first candidate CCE is allocated to the RedCap terminal; if the terminal is not a RedCap terminal, the standby C-RNTI associated with the CCE candidate set with the CCE outside the preset bandwidth as the first candidate CCE is allocated to the terminal. Based on this, CCE candidate sets of different bandwidth types are preferentially allocated to different terminals, so that RedCap terminals can be preferentially allocated to the CCE candidate set within the preset bandwidth, reducing the probability of CCE being preempted within the bandwidth and improving the allocation success rate of RedCap terminals.

[0105] In addition, after the target CCE candidate set is allocated to the RedCap terminal, since the USS CCE candidate positions within the preset bandwidth in the target CCE candidate set are ranked first, the RedCap terminal blind detection can demodulate to the available USS CCE faster, thereby improving the terminal's blind detection efficiency.

[0106] In a possible implementation, the functional unit for pre-dividing the target C-RNTI and the standby C-RNTI includes:

[0107] an in-band CCE determining unit, configured to determine a USS CCE in a USS available state within the preset bandwidth supported by the RedCap terminal as an available USS CCE;

[0108] A CCE query unit, used to query the first candidate CCE in the CCE candidate set associated with each C-RNTI in the base station;

[0109] a target C-RNTI determining unit, configured to determine the C-RNTI associated with the CCE candidate set in which the first candidate CCE is the available USS CCE as a target C-RNTI;

[0110] A target C-RNTI set unit, configured to classify the target C-RNTIs to obtain at least one target C-RNTI set, and for each target C-RNTI in the target C-RNTI set, the first candidate CCE in the CCE candidate set associated therewith is the same USS CCE;

[0111] A spare C-RNTI set unit, configured to generate a spare C-RNTI set based on the C-RNTIs other than the target C-RNTIs among all the C-RNTIs in the base station.

[0112] In a possible implementation, the C-RNTI allocation first unit 300 includes:

[0113] A target set determination subunit, configured to determine a target C-RNTI set from the at least one target C-RNTI set;

[0114] A status identification subunit, configured to identify the usage status of the CCE candidate sets associated with each target C-RNTI in the target C-RNTI set, and obtain at least one target C-RNTI with an unused status;

[0115] A first-position allocation subunit, configured to allocate the target C-RNTI ranked first among the at least one target C-RNTIs with an unused status to the RedCap terminal.

[0116] In a possible implementation, after the first-position allocation subunit finishes the step of allocating the target C-RNTI ranked first among the at least one target C-RNTIs with an unused status to the RedCap terminal, it jumps to a status marking subunit, configured to mark the target C-RNTI allocated to the RedCap terminal as being in a used status;

[0117] A status modification subunit, configured to mark the target C-RNTI allocated to the RedCap terminal as being in an unused status after the resource scheduling of the RedCap terminal is completed.

[0118] In a possible implementation, the in-band CCE determination unit includes:

[0119] An initializing CCE subunit, configured to initialize all USS CCEs within the preset bandwidth supported by the RedCap terminal to obtain USS CCEs in an initial USS available status;

[0120] A parameter acquisition subunit, configured to acquire PDCCH parameters for characterizing CCE occupancy in the base station configuration data;

[0121] An occupied REG determination subunit, configured to determine a REG Bundle occupied by a CSS based on the PDCCH parameter;

[0122] A state switching subunit, configured to mark an initial state of the USS CCE including the REG Bundle occupied by the CSS as a USS unavailable state;

[0123] An unavailable CCE screening subunit, configured to determine, among all USS CCEs within the preset bandwidth, the remaining USS CCEs except the USS CCEs in the USS unavailable state as available USS CCEs.

[0124] In a possible implementation, the RedCap PDCCH resource allocation device further includes:

[0125] A priority marking subunit, configured to, in response to a PDCCH blind detection result indicating that no idle CCE is found sent by the RedCap terminal, mark a priority for the RedCap terminal and place the RedCap terminal in a cache, where the cache is used to store terminals waiting for scheduling, and the priority characterizes the priority degree of the RedCap terminal to be scheduled.

[0126] The RedCap PDCCH resource allocation device provided by the embodiments of the present application can be applied to a RedCap PDCCH resource allocation device.

[0127] Figure 6 Shows a schematic structural diagram of a RedCap PDCCH resource allocation device. Referring to Figure 6 , the structure of the RedCap PDCCH resource allocation device may include: at least one processor 10, at least one memory 20, at least one communication bus 30, and at least one communication interface 40.

[0128] In the embodiments of the present application, the number of the processor 10, the memory 20, the communication bus 30, and the communication interface 40 is at least one, and the processor 10, the memory 20, and the communication interface 40 complete mutual communication through the communication bus 30.

[0129] The processor 10 may be a central processing unit CPU, or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present invention, etc.

[0130] The memory 20 may include a high-speed RAM memory and may also include a non-volatile memory, such as at least one disk memory.

[0131] Among them, the memory stores a program, and the processor can call the program stored in the memory. The program is used to implement each processing flow in the foregoing RedCap PDCCH resource allocation method.

[0132] The embodiments of the present application further provide a computer storage medium. The storage medium can store a program suitable for being executed by a processor. The program is used to implement each processing flow in the foregoing RedCap PDCCH resource allocation method.

[0133] The embodiments of the present application further provide a computer program product, including a computer program. When the computer program is executed by a processor, it implements each step of the foregoing RedCap PDCCH resource allocation method.

[0134] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0135] Finally, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements but also other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0136] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the various embodiments can be referred to each other.

[0137] The foregoing description of the disclosed embodiments enables those skilled in the art to practice or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A RedCap PDCCH resource allocation method, characterized in that: Applied to a base station, the RedCap PDCCH resource allocation method includes: Acquire the terminal waiting for scheduling and the terminal information of the terminal; Based on the terminal information, determining whether the terminal is a RedCap terminal; In the case where the terminal is the RedCap terminal, a pre-divided target cell radio network temporary identifier C-RNTI is allocated to the RedCap terminal, so that the RedCap terminal performs PDCCH blind detection on a target CCE candidate set associated with the target C-RNTI, the target CCE candidate set being a CCE set that uses an available USS CCE within a preset bandwidth as a first candidate CCE, and the preset bandwidth is a bandwidth supported by the RedCap terminal; When the terminal is not the RedCap terminal, a pre-allocated spare C-RNTI is allocated to the terminal so that the terminal performs PDCCH blind detection on the spare CCE candidate set associated with the spare C-RNTI, and the spare CCE candidate set is a CCE set that takes the CCE outside the preset bandwidth as the first candidate CCE.

2. The RedCap PDCCH resource allocation method according to claim 1, characterized in that: The process of pre-dividing the target C-RNTI and the standby C-RNTI includes: Determine a USS CCE in a USS available state within the preset bandwidth supported by the RedCap terminal as an available USS CCE; Querying a first candidate CCE in a CCE candidate set associated with each C-RNTI in the base station; Determine the C-RNTI associated with the CCE candidate set in which the first candidate CCE is the available USS CCE as a target C-RNTI; Classifying the target C-RNTI to obtain at least one target C-RNTI set, wherein the first candidate CCE of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set is the same USS CCE; A spare C-RNTI set is generated based on C-RNTIs other than the target C-RNTI among all C-RNTIs in the base station.

3. The RedCap PDCCH resource allocation method according to claim 2, characterized in that: The step of allocating the pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal comprises: Determining a target C-RNTI set from the at least one target C-RNTI set; Identify the usage status of the CCE candidate set associated with each of the target C-RNTIs in the target C-RNTI set, and obtain at least one target C-RNTI whose usage status is unused; The target C-RNTI ranked first among the at least one target C-RNTI whose usage status is unused is allocated to the RedCap terminal.

4. The RedCap PDCCH resource allocation method according to claim 3, characterized in that: After allocating the target C-RNTI ranked first among the at least one target C-RNTI in the unused state to the RedCap terminal, the method further includes: Marking the target C-RNTI allocated to the RedCap terminal as in use; After the resource scheduling of the RedCap terminal is completed, the target C-RNTI allocated to the RedCap terminal is marked as unused.

5. The RedCap PDCCH resource allocation method according to claim 2, characterized in that: The determining, as the available USS CCE, of the USS available status within the preset bandwidth supported by the RedCap terminal, includes: Initialize all USS CCEs within the preset bandwidth supported by the RedCap terminal to obtain USS CCEs whose initial state is USS available state; Obtaining PDCCH parameters used to characterize CCE occupancy in base station configuration data; Determine a REG Bundle occupied by a CSS based on the PDCCH parameters; Marking the initial state of the USS CCE including the REG Bundle occupied by the CSS as a USS unavailable state; Among all the USS CCEs within the preset bandwidth of the RedCap terminal, except for the USS CCEs in the USS unavailable state, the remaining USS CCEs are determined as available USS CCEs.

6. The RedCap PDCCH resource allocation method according to claim 1, characterized in that: Also includes: In response to the PDCCH blind detection result sent by the RedCap terminal that no idle CCE is found, the priority of the RedCap terminal is marked and the RedCap terminal is put into a cache, the cache is used to store terminals waiting for scheduling, and the priority represents the priority of the RedCap terminal to be scheduled.

7. A RedCap PDCCH resource allocation device, characterized in that: Applied to a base station, the RedCap PDCCH resource allocation device comprises: A terminal information acquisition unit, used to acquire a terminal waiting for scheduling and terminal information of the terminal; A terminal type determination unit, configured to determine whether the terminal is a RedCap terminal based on the terminal information; A first C-RNTI allocation unit is used to allocate a pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal when the terminal is the RedCap terminal, so that the RedCap terminal performs PDCCH blind detection on a target CCE candidate set associated with the target C-RNTI, wherein the target CCE candidate set is a CCE set that uses an available USSCCE within a preset bandwidth as a first candidate CCE, and the preset bandwidth is a bandwidth supported by the RedCap terminal; The C-RNTI allocation second unit is used to allocate a pre-allocated spare C-RNTI to the terminal when the terminal is not the RedCap terminal, so that the terminal performs PDCCH blind detection on the spare CCE candidate set associated with the spare C-RNTI, and the spare CCE candidate set is a CCE set that takes the CCE outside the preset bandwidth as the first candidate CCE.

8. A RedCap PDCCH resource allocation device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program so that the RedCap PDCCH resource allocation device can implement the RedCap PDCCH resource allocation method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that: The storage medium carries one or more computer programs, and when the one or more computer programs are executed by the RedCap PDCCH resource allocation device, the RedCap PDCCH resource allocation device can implement the RedCap PDCCH resource allocation method according to any one of claims 1 to 6.

10. A computer program product, characterized in that It comprises a computer program, which implements each step of the RedCap PDCCH resource allocation method according to any one of claims 1 to 6 when executed by a processor.

Images