RedCap PDCCH (Physical Downlink Control Channel) resource allocation method and related equipment

Abstract

The invention discloses a RedCap PDCCH (Physical Downlink Control Channel) resource allocation method and related equipment, and relates to the field of 5G private networks, comprising the following steps: judging whether a terminal is a RedCap terminal based on terminal information of a terminal waiting for scheduling; if yes, the target C-RNTI is allocated to the terminal, and a first candidate CCE in a CCE candidate set associated with the target C-RNTI is a USS CCE in a preset bandwidth supported by the RedCap terminal; and if not, the standby C-RNTI is allocated to the terminal, and the first candidate CCE in the CCE candidate set associated with the standby C-RNTI is the CCE outside the preset bandwidth. According to the method and the device, the C-RNTIs associated with the CCEs of different bandwidth types are preferentially allocated to the terminals of different types, so that the RedCap terminal can preferentially allocate the CCEs in the preset bandwidth, the probability that the CCEs in the bandwidth are preempted is reduced, and the RedCap terminal allocation success rate is improved.

Description

Technical Field

[0001] The present application relates to the field of 5G private network technology, and more specifically, to a RedCap PDCCH resource allocation method and related equipment. Background Art

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

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

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

[0005] In view of the above problems, the present application provides a RedCap PDCCH resource allocation method and related devices to achieve the purpose of improving the success rate of allocating RedCap terminals to idle CCEs. The specific scheme is as follows: In a first aspect, the present application provides a RedCap PDCCH resource allocation method, which is 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.

[0006] In a possible implementation, 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; Query the first candidate CCE in the 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; Classify 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 USSCCE; 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.

[0007] In a possible implementation, allocating the pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal includes: 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.

[0008] In a possible implementation, after allocating the target C-RNTI ranked first among the at least one target C-RNTI whose usage status is unused 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.

[0009] In a possible implementation, determining the USS CCE in the USS available state within the preset bandwidth supported by the RedCap terminal as the available USS CCE 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; Get the PDCCH parameters used to characterize CCE occupancy in the 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.

[0010] In a possible implementation, the method further 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.

[0011] A second aspect of the present application provides a RedCap PDCCH resource allocation device, which is applied to a base station. The RedCap PDCCH resource allocation device includes: 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 USS CCE 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.

[0012] The third aspect of the present application provides a RedCap PDCCH resource allocation device, comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; 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 of the above-mentioned first aspect or any implementation manner of the first aspect.

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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

[0018] 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.

[0019] Figure 1 An example diagram of a PDCCH resource allocation method provided in an embodiment of the present application; Figure 2 A flowchart of a method for implementing RedCap PDCCH resource allocation provided in an embodiment of the present application; Figure 3 An example diagram showing CCE occupancy provided in an embodiment of the present application; Figure 4 An example diagram of a RedCap PDCCH resource allocation method provided in an embodiment of the present application; Figure 5 A schematic diagram of the structure of a RedCap PDCCH resource allocation device provided in an embodiment of the present application; Figure 6 A structural diagram of a RedCap PDCCH resource allocation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

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

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

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

[0024] To solve the above problems, the present application embodiment provides a RedCap PDCCH resource allocation method, which is applied to a base station, referring to Figure 2 , a flow chart of a method for implementing a RedCap PDCCH resource allocation method provided in an embodiment of the present application is provided, and the implementation process of the RedCap PDCCH resource allocation method is described, and specific reference is made to the following contents: Step S110, obtaining the terminal waiting for scheduling and the terminal information of the terminal.

[0025] The terminal waiting for scheduling can be a terminal currently accessing the base station, or a terminal stored in the cache that failed in the last scheduling and is waiting for scheduling again. The terminal information may at least include: terminal identification information, an identifier representing the terminal type, the type of network the terminal requests to access, terminal location information, security information, etc.

[0026] If the terminal waiting for scheduling is the terminal currently connected to the base station, the base station will receive a handshake message sent by the terminal, where a handshake message refers to a signal or message used to establish a reliable connection between the communicating parties or confirm each other's status. Based on the handshake message, the base station can receive the terminal's connection request, as well as the terminal's identification, the type of network requested to be accessed, and the terminal's initial sequence number and other information.

[0027] For example, in the field of wireless communications, in the RACH (Random Access Channel) process used to establish or reestablish an initial 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 to send Msg2 to the terminal based on the terminal information carried in Msg1 and the current resource usage to implement PDCCH resource allocation.

[0028] If the terminal waiting for scheduling is a terminal stored in the cache that failed to be scheduled last time and is waiting to be scheduled again, since the terminal in the cache is the terminal that failed to be scheduled last time and the terminal information has been obtained during the last allocation process, the terminal information can be obtained directly from the cache without the terminal sending handshake information.

[0029] 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.

[0030] Based on the identification information representing the terminal type in the terminal information, such as the Preamble ID, the terminal type of the terminal waiting for scheduling is identified. The embodiment of the present application is mainly used to solve the problem of resource allocation of RedCap terminals. Therefore, it is identified whether the terminal waiting for scheduling is a RedCap terminal.

[0031] It can be understood that if the embodiment of the present application solves the problem of low success rate of PDCCH resource allocation for narrowband Internet of Things user terminals, it is possible to identify whether the terminal waiting for scheduling is a narrowband Internet of Things user terminal based on the terminal type or terminal bandwidth in the terminal information, and the same is true for the PDCCH resource allocation method under the narrowband Internet of Things user terminal.

[0032] Step S130: Allocate the pre-divided target C-RNTI to the RedCap terminal.

[0033] Step S131: Allocate the pre-allocated standby C-RNTI to the terminal.

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

[0035] It is understandable that RedCap terminals can only use USS CCEs within the preset bandwidth, while nonRedCap terminals have no special restrictions on the bandwidth attributes of CCEs. Therefore, the CCEs in the base station that meet the bandwidth of RedCap terminals are limited, and the CCEs within the preset bandwidth may be occupied by CSS and nonRedCap terminals, resulting in the RedCap terminal being unable to successfully allocate idle CCEs within the preset bandwidth. In the embodiment of the present application, idle CCE can be understood as available CCE. Similarly, available USSCCE is an idle, unoccupied USS CCE.

[0036] Based on this, the embodiment of the present application pre-lists the CCE candidate set including the available USS CCE within the preset bandwidth as the target CCE candidate set, and the C-RNTI associated with the target CCE candidate set as the target C-RNTI, and lists the CCE candidate set including CCE outside the preset bandwidth as the standby CCE candidate set, and the C-RNTI associated with the standby CCE candidate set as the standby C-RNTI. When allocating resources, the target CCE candidate set associated with the target C-RNTI is preferentially allocated to the RedCap terminal, while the nonRedCap terminal is preferentially allocated the standby CCE candidate set associated with the standby C-RNTI, so as to avoid the situation where the npnRedCap terminal preempts the USS CCE within the limited preset bandwidth, reduce the possibility of the nonRedCap terminal preempting the USS CCE within the preset bandwidth, and improve the success rate of the RedCap terminal preempting the USS CCE within the preset bandwidth.

[0037] Moreover, since the target candidate sets associated with the target C-RNTI selected in the embodiments of the present application are all candidate sets that use the available USS CCE within the preset bandwidth as the first candidate CCE, the base station can find and seize the CCE that meets the requirements as quickly as possible during the process of checking the resources in the target candidate set, thereby improving the seizure speed and further improving the success rate of the RedCap terminal being allocated to the USS CCE within the preset bandwidth.

[0038] It is understandable that the CCE candidate set contains multiple candidate CCEs. When the base station performs a PDCCH search, it performs a status check according to the order of the candidate CCEs in the CCE candidate set. If the available CCE is ranked first, the PDCCH search only requires one status check to lock the available CCE and allocate the CCE to the terminal. However, if the available CCE is ranked later, the PDCCH search requires multiple status checks before the available CCE can be locked. If other terminals access the base station during the PDCCH search, the available CCE may be preempted by other terminals, and the final PDCCH search result for the CCE candidate set is empty, that is, the scheduling of the terminal data fails. Therefore, the USS CCE within the preset bandwidth is used as the first candidate CCE. The target CCE candidate set associated C-RNTI is determined as the target C-RNTI, which can improve the success rate of the base station in preempting CCE for the RedCap terminal.

[0039] 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 only needs to check once during the PDCCH blind detection process to lock the idle CCE, reducing the number of blind detections and blind detection time, and reducing the possibility of idle CCE being preempted by other terminals, thereby improving the success rate of RedCap terminals allocated to idle CCE.

[0040] Furthermore, the base station performs a PDCCH resource check on the target CCE candidate set or the standby CCE candidate set associated with the C-RNTI allocated to the terminal. Under normal circumstances, the status of the CCEs in the CCE candidate set is checked in turn. If an idle CCE is detected, it can be determined that the CCE candidate set associated with the C-RNTI is available, and the C-RNTI is allocated to the terminal, and subsequent DCI demodulation and resource scheduling operations are performed on the idle CCE. If the number of checks reaches the maximum number of checks, or no idle CCE is detected after traversal checks, the PDCCH check fails, the terminal cannot be allocated to CCE, and resource scheduling fails.

[0041] In an embodiment of the present application, the target C-RNTI is sent to the RedCap terminal, and the RedCap terminal performs a PDCCH blind check on the target CCE candidate set associated with the target C-RNTI. After the blind check obtains the idle CCE, resource allocation and scheduling with the base station are implemented based on the idle CCE.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

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

[0047] In one possible implementation, the process of pre-dividing the target CCE candidate set and the backup CCE candidate set may include: determining the USS CCE in the USS available state 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 in which the 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, the first candidate CCE of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set being the same USS CCE; and generating a backup C-RNTI set based on the C-RNTIs other than the target C-RNTI in all C-RNTIs in the base station.

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

[0049] The embodiment of the present application is illustrated by taking the RedCap terminal as an example. For example, the base station checks the status, bandwidth attributes, etc. of each CCE through resource checking, and determines the available USSCCE among the 8 CCEs corresponding to the BWP bandwidth of the RedCap terminal. In the embodiment of the present application, "available" can be understood as CCE not occupied by CSS or nonRedCap terminals.

[0050] Optionally, the process of determining the USS CCE within the bandwidth supported by the RedCap terminal may also include: initializing all USS CCEs within the preset bandwidth supported by the RedCap terminal to obtain USS CCEs whose initial state is a USS available state; obtaining PDCCH parameters used to characterize the CCE occupancy status in the base station configuration data, and determining the REGBundle occupied by the CSS based on the PDCCH parameters; marking the initial state of the USS CCE of the REG Bundle occupied by the CSS as a USS unavailable state; and determining the remaining USSCCEs, except for the USS CCEs in the USS unavailable state, as available USS CCEs among all USS CCEs within the preset bandwidth of the RedCap terminal.

[0051] When allocating PDCCH resources, the base station usually gives priority to CSS resource allocation. Since CSS PDCCH is in interleaved mode, the CCE resources it occupies are discontinuously distributed, which will reduce the CCE available for USS PDCCH of RedCap terminals. Figure 3 , the example diagram showing the CCE occupancy provided in the embodiment of the present application, the CCE occupancy under normal circumstances is as follows Figure 3In Pattern1, Coreset p is the 8 USS CCEs in the frequency domain of RedCap BWP, and Coreset 0 is the arrangement of REG Bundles corresponding to the CCEs of CSS. CSS and USS share the same CCE resource pool. Coreset 0 used by CSS will occupy 4 REG Bundles, namely REG Bundle0, REG Bundle1, REG Bundle4, and REG Bundle5. Since the starting CRB positions of Coreset0 and RedCap BWP in the frequency domain are aligned, they occupy CCE0, 1, 4, and 5 of Coreset p respectively. The remaining available USS CCEs are: CCE2, CCE3, CCE6, and CCE7. Referring to Pattern 2, since the frequency domain starting CRB position of Coresrt 0RedCap BWP is not aligned with the frequency domain starting CRB position of Coresrt p, Coreset 0 also occupies REG Bundle 0, 1, 4, 5, which will cause CCE 0, 1, 2, 4, 5, 6 in Coreset p to be unavailable, and only 2 CCEs are left for the remaining USS, resulting in a reduction in the number of available USS CCEs.

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

[0053] Read PDCCH related parameters from the base station configuration data, which include at least: number of PDCCH symbols, number of BWPPRBs, number of PDCCH REGs, REG Bundle size, PDCCH interleaving Shift number, and PDCCH interleaving block size. Calculate the REG Bundle number occupied by the CSS based on the PDCCH parameter configuration, and the USSCCE containing the REG Bundle number occupied by these CSS indicates that it has been occupied. For example, Figure 3In Pattern 2, the CRB sequence number of CCE1 occupied by CCS is CRB9-14, and CCE1 and CCE2 in Coreset p respectively include occupied CRB9-14, so CCE1 and CCE2 are also in the occupied state, that is, CCE1 and CCE2 in Coreset p can be confirmed as CCEs that are unavailable to USS.

[0054] The initial state of the USS unavailable CCE is changed to USS_NOT_AVAILABLE, indicating the USS unavailable state. In the array RedCap Uss Cce List, remove the CCE marked with USS_NOT_AVAILABLE, and the remaining CCE marked with USS_AVAILABLE is in the USS available state, which is recorded as CCE_INDEX_X, that is, the available USS CCE. In this example, there are two available USS CCEs remaining in the array RedCap Uss Cce List, which are recorded as: CCE_INDEX_1 and CCE_INDEX_2.

[0055] Furthermore, CCE_INDEX_X is searched in the CCE candidate set associated with all C-RNTIs of the base station, and the C-RNTI whose first candidate CCE in the associated CCE candidate set is CCE_INDEX_X is determined as the target C-RNTI, and the target C-RNTIs whose first candidate CCE is the same CCE_INDEX_X are summarized into a target C-RNTI set, denoted as CRNTI_POOL_X.

[0056] For example, the first candidate CCE in the CCE candidate set associated with each C-RNTI in the base station is searched, and the C-RNTIs whose first candidate CCE in the associated CCE candidate set is CCE_INDEX_1 are: C-RNTI-1, C-RNTI-2, then C-RNTI-1 and C-RNTI-2 are respectively used as target C-RNTIs, and C-RNTI-1 and C-RNTI-2 are summarized as the target C-RNTI set, recorded as CRNTI_POOL_1. Similarly, CCE_INDEX_2 is a combination of the C-RNTIs of the first candidate CCE in the associated CCE candidate set, which can be recorded as CRNTI_POOL_2.

[0057] When the base station allocates C-RNTI to the terminal, if the terminal is a RedCap terminal, one target C-RNTI can be selected from the target C-RNTI set and allocated to the RedCap terminal. In another possible implementation, a target C-RNTI set is first determined from the at least one target C-RNTI set; the use status of the CCE candidate set associated with each target C-RNTI in the target C-RNTI set is identified to obtain at least one target C-RNTI whose use status is unused; and the target C-RNTI ranked first among the at least one target C-RNTI whose use status is unused is allocated to the RedCap terminal.

[0058] Since when dividing C-RNTI, it is not distinguished whether the CCE candidate set associated with each C-RNTI has been allocated. Therefore, in order to avoid the RedCap terminal being assigned a CCE candidate set that has been used, resulting in the RedCap terminal allocation failure, the embodiment of the present application pre-screens the CCE candidate set that has been used in the target C-RNTI set before allocating the target C-RNTI, and selects one from the target C-RNTI corresponding to the unused CCE candidate set for allocation. In the embodiment of the present application, according to the arrangement order of the target C-RNTIs with unused usage status in the target C-RNTI set CRNTI_POOL_X, the one with the smallest arrangement number, that is, the first target CCE candidate set, is selected and allocated to the RedCap terminal.

[0059] It can be understood that the target C-RNTI allocated to the RedCap terminal has been used, therefore, the target C-RNTI allocated to the RedCap terminal is marked 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 to track the use status of each target C-RNTI and ensure the accuracy of the status of the C-RNTIs waiting for allocation and being allocated. In addition, the spare C-RNTI in the spare C-RNTI set is used to allocate to non-RedCap terminals, and its allocation method can refer to the above-mentioned allocation method of the target C-RNTI set, which will not be repeated here.

[0060] Reference Figure 4, four terminals UE1, UE2, UE3, and UE4 access the base station, among which UE1 and UE2 are RedCap terminals, and UE3 and UE4 are non-RedCap terminals. Optionally, a target C-RNTI is selected from CRNTI_POOL_0 and CRNTI_POOL_1 to be allocated to UE1 and UE2 respectively. Considering that if the targets allocated to UE1 and UE2 are from the same target C-RNTI set, there may be a possibility that the two terminals will occupy the USS CCE within the same preset bandwidth, resulting in one of the terminals being unable to be successfully allocated to the CCE, therefore, the target C-RNTI is selected from two different target C-RNTI sets, that is, the target C-RNTI allocated to UE1 is from CRNTI_POOL_0, and the target C-RNTI allocated to UE2 is from CRNTI_POOL_1, so as to improve the success rate of the two RedCap terminals being allocated to the CCE.

[0061] In addition, two unused standby CCE candidate sets are selected from the standby C-RNTI set CRNTI_POOL_2 and allocated to UE3 and UE4 respectively. It is understandable that the bandwidth supported by nonRedCap terminals is larger. For example, TDD FR1 has a total bandwidth of 100MHz. After excluding 20MHz for RedCap terminals, there are still 80MHz of CCE available. Therefore, the PDCCH CCE resources of nonRedCap terminals are relatively abundant, and there are more standby C-RNTIs available in CRNTI_POOL_2. Therefore, although the embodiment of the present application pre-occupies CCE resources within the preset bandwidth and is only used for allocation to RedCap terminals, due to the abundant resources within the bandwidth of nonRedCap terminals, the problem of insufficient CCE generally does not occur. Therefore, while the embodiment of the present application improves the success rate of RedCap allocation, it does not reduce the success rate of nonRedCap allocation.

[0062] In summary, a RedCap PDCCH resource allocation method provided in an embodiment of the present application pre-calculates the USS PDCCH resource positions available to the RedCap terminal, divides them into several CRNTI_Pools, and preferentially allocates the C-RNTIs in these Pools to the RedCap terminal. Since the USS CCE that the terminal can use is strongly related to the C-RNTI, the use of the C-RNTIs in these Pools can be associated with the available USS CCE resources with a greater probability. 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, which reduces the number of blind detection attempts.

[0063] Compared with the conventional PDCCH resource allocation method, this method can improve the allocation success rate of RedCap PDCCH resources, which is conducive to the timely scheduling of terminal data by the base station. At the same time, it can also improve the blind detection efficiency of RedCap terminal PDCCH, which is conducive to terminal energy saving.

[0064] The following describes a RedCap PDCCH resource allocation device provided in an embodiment of the present application. The RedCap PDCCH resource allocation device described below and the RedCap PDCCH resource allocation method described above can correspond to each other.

[0065] First, combine Figure 5 , the RedCap PDCCH resource allocation device applied to the base station side is introduced, such as Figure 5 As shown, the RedCap PDCCH resource allocation device may include: The terminal information acquisition unit 100 is used to acquire the terminal waiting for scheduling and the terminal information of the terminal; The terminal type determination unit 200 is used to determine whether the terminal is a RedCap terminal based on the terminal information; The first C-RNTI allocation unit 300 is used to allocate the pre-divided target cell radio network temporary identifier C-RNTI to the RedCap terminal when the judgment result of the terminal type judgment unit 200 is yes, so that the RedCap terminal performs PDCCH blind detection on the target CCE candidate set associated with the target C-RNTI, the target CCE candidate set is a CCE set that uses an available USS CCE within a preset bandwidth as the first candidate CCE, and the preset bandwidth is a bandwidth supported by the RedCap terminal; 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] In a possible implementation, the functional unit for pre-dividing the target C-RNTI and the standby C-RNTI includes: 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; 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; 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; A target C-RNTI set unit, configured to classify 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; The spare C-RNTI set unit is used to generate a spare C-RNTI set based on C-RNTIs other than the target C-RNTI in all C-RNTIs in the base station.

[0070] In a possible implementation, the C-RNTI allocation first unit 300 includes: a target set determination subunit, configured to determine a target C-RNTI set from the at least one target C-RNTI set; A state identification subunit, configured to identify a usage state of a 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 state is an unused state; The first allocation subunit is used to allocate the target C-RNTI ranked first among the at least one target C-RNTI whose usage status is unused to the RedCap terminal.

[0071] In a possible implementation, after the first allocation subunit completes the step of allocating the target C-RNTI ranked first among the at least one target C-RNTI in an unused state to the RedCap terminal, the subunit jumps to the state marking subunit, which is used to mark the target C-RNTI allocated to the RedCap terminal as being in a used state; The state modification subunit is used to mark the target C-RNTI allocated to the RedCap terminal as unused after the resource scheduling of the RedCap terminal is completed.

[0072] In a possible implementation, the in-band CCE determination unit includes: Initialize the CCE subunit, used to initialize all USS CCEs within the preset bandwidth supported by the RedCap terminal, and obtain USS CCEs whose initial state is USS available state; A parameter acquisition subunit, used to acquire PDCCH parameters used to characterize CCE occupancy in base station configuration data; An occupied REG determination subunit, used to determine the REG Bundle occupied by the CSS based on the PDCCH parameters; A state switching subunit is used to mark the initial state of the USS CCE including the REG Bundle occupied by the CSS as a USS unavailable state; The unavailable CCE screening subunit is configured to determine the remaining USS CCEs, among all the USS CCEs within the preset bandwidth, except the USS CCEs in the USS unavailable state, as available USS CCEs.

[0073] In a possible implementation, the RedCap PDCCH resource allocation device further includes: The priority marking subunit is used to mark the priority of the RedCap terminal in response to the PDCCH blind detection result sent by the RedCap terminal that no idle CCE is found, and put the RedCap terminal 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.

[0074] The RedCap PDCCH resource allocation apparatus provided in the embodiment of the present application can be applied to a RedCap PDCCH resource allocation device.

[0075] Figure 6 The structure diagram of the RedCap PDCCH resource allocation device is shown. 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.

[0076] In the embodiment 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 communicate with each other through the communication bus 30 .

[0077] The processor 10 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

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

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

[0080] An embodiment of the present application further provides a computer storage medium, which may store a program suitable for execution by a processor, wherein the program is used to implement each processing flow in the aforementioned RedCap PDCCH resource allocation method.

[0081] The embodiment of the present application further provides a computer program product, including a computer program, which implements each step of the aforementioned RedCap PDCCH resource allocation method when executed by a processor.

[0082] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, 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.

[0083] Finally, it should be noted that, in this article, relational terms such as first and second, etc. 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 terms "include", "comprise" or any other variants thereof are 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 explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0084] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0085] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be 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. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to 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, which, when executed by a RedCap PDCCH resource allocation device, enable the RedCap PDCCH resource allocation device to 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