Systems and methods for pdcch repetition reception

CN116724623BActive Publication Date: 2026-10-09APPLE INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202180090471.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-01-14
Publication Date
2026-10-09
Estimated Expiration
2041-01-14

Smart Images

  • Figure CN116724623B_ABST
    Figure CN116724623B_ABST
Patent Text Reader

Abstract

A user equipment (UE) monitors a physical downlink control channel (PDCCH). The UE receives a configuration of a physical downlink control channel (PDCCH) including repetitions of PDCCH candidates including first PDCCH data, where the PDCCH candidates repeat across multiple durations of a DL resource grid; detects each of the PDCCH candidates based on a repetition detection scheme and combines soft bits from each of the PDCCH candidates, where the combined soft bits are jointly decoded to determine the first PDCCH data; and calculates a number of blind decodes (BDs) of the durations of the DL resource grid carrying the PDCCH candidates, where at least one BD value of the PDCCH candidates is scaled by a scaling factor for calculating the number of BDs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates in general to wireless communication, and more particularly to systems and methods for repeated PDCCH reception. Background Technology

[0002] The Physical Downlink Control Channel (PDCCH) search space refers to the area within the downlink resource grid that can carry PDCCHs. For a User Equipment (UE) to decode a PDCCH, the UE needs to know the PDCCH's location (Control Channel Element (CCE) aggregation level and index of each CCE), structure, scrambling code, etc. However, each PDCCH supports multiple DCI formats and aggregation levels. The UE is not informed which DCI format or aggregation level to use and therefore needs to perform blind decoding across the entire search space to find the transmitted downlink control information (DCI). The maximum number of blind decodes or CCEs to search can be defined in 3GPP standards, for example, on a per-slot or per-span basis.

[0003] To improve the reliability of PDCCH decoding, multiple repetitions of the same PDCCH payload can be transmitted. The UE can attempt to decode each repetition independently or combine the soft bits from each repetition and decode the combined bits. The UE's processing burden can be unevenly distributed across multiple time slots carrying PDCCH repetitions. Summary of the Invention

[0004] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. These operations include: receiving a configuration of a physical downlink control channel (PDCCH) including repetitions of PDCCH candidates that include first PDCCH data, wherein these PDCCH candidates repeat for multiple durations across a DL resource grid; detecting each of these PDCCH candidates based on a repetition detection scheme, and combining soft bits from each of these PDCCH candidates, wherein the combined soft bits are jointly decoded to determine the first PDCCH data; and calculating the number of blind decodings (BDs) for these durations of the DL resource grid carrying the PDCCH candidates, wherein at least one BD value of the PDCCH candidates is scaled by a scaling factor to be used in calculating the number of BDs.

[0005] Other exemplary embodiments relate to a user equipment (UE) having: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform operations. These operations include: receiving a configuration for a physical downlink control channel (PDCCH) including repetitions of PDCCH candidates comprising first PDCCH data, wherein these PDCCH candidates repeat for multiple durations across a DL resource grid; detecting each of these PDCCH candidates based on a repetition detection scheme, and combining soft bits from each of these PDCCH candidates, wherein the combined soft bits are jointly decoded to determine the first PDCCH data; and calculating the number of blind decodings (BDs) for these durations of the DL resource grid carrying the PDCCH candidates, wherein at least one BD value of the PDCCH candidates is scaled by a scaling factor to be used in calculating the number of BDs.

[0006] Another exemplary embodiment relates to a processor of a base station configured to perform operations. These operations include: configuring a physical downlink control channel (PDCCH) for a user equipment (UE), the PDCCH including repetitions of PDCCH candidates including first PDCCH data, wherein these PDCCH candidates repeat across multiple durations of a DL resource grid, wherein the UE uses a repetition detection scheme to detect each of these PDCCH candidates, and combines soft bits from each of these PDCCH candidates, wherein the combined soft bits are jointly decoded to determine the first PDCCH data; and signaling to the UE a scaling factor for calculating the number of blind decodings (BDs) for the durations of the DL resource grid carrying these PDCCH candidates, wherein the UE scales at least one BD value of these PDCCH candidates by the scaling factor to calculate the number of BDs. Attached Figure Description

[0007] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0008] Figure 2 Exemplary UEs according to various exemplary implementations are shown.

[0009] Figure 3 Exemplary network cells according to various exemplary implementations are shown.

[0010] Figure 4a An exemplary PDCCH transmission using time slot repetition is shown.

[0011] Figure 4bAn exemplary PDCCH transmission using time slot repetition is shown.

[0012] Figure 5 Illustrations are shown of various exemplary embodiments described herein for counting blind decoding (BD) during an exemplary PDCCH repetition operation.

[0013] Figure 6 Illustrations are shown of various exemplary embodiments described herein for counting blind decoding (BD) in an exemplary PDCCH repetition operation for a search space oversubscription case.

[0014] Figure 7 Illustrations are shown of various exemplary embodiments described herein for counting blind decoding (BD) in an exemplary PDCCH repetition operation based on multiple time slots.

[0015] Figure 8 Methods for counting blind decoding (BD) in an exemplary PDCCH repetition operation are illustrated according to various exemplary embodiments described herein. Detailed Implementation

[0016] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments describe operations for counting the number of blind decoding (BD) or control channel elements (CCE) of PDCCH data when some or all of the PDCCH data are repeatedly transmitted using the physical downlink control channel (PDCCH). The BD / CCE count may be determined by the user equipment (UE) and compared with a specified maximum BD / CCE limit for a given duration (e.g., per time slot, multiple time slots, or per span) to ensure that the BD / CCE does not exceed the specified limit for that duration. In cases where the BD / CCE limit is exceeded, indicating that the duration has been oversubscribed, operations are described for reducing the BD count by discarding certain search spaces (SS) or control resource sets (CORESET) available for the UE to search and recalculating the BD / CCE count until the count is within the specified limit.

[0017] Network / Device

[0018] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a plurality of UEs 110, 112. Those skilled in the art will understand that the UEs can be any type of electronic component configured to communicate via a network, such as components of a connected car, mobile phone, tablet computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that a practical network arrangement can include any number of UEs used by any number of users. Therefore, the example with two UEs 110, 112 is provided only for illustrative purposes.

[0019] UEs 110 and 112 can communicate directly with one or more networks. In the example of network configuration 100, the networks with which UEs 110 and 112 can communicate wirelessly are 5G NR radio access network (5G NR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. Therefore, UEs 110 and 112 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124. However, UEs 110 and 112 can also communicate with other types of networks (e.g., traditional cellular networks), and UE 110 can also communicate with the network via a wired connection. Referring to an exemplary embodiment, UEs 110 and 112 can establish connections with 5G NR-RAN 120 and / or LTE-RAN 122.

[0020] 5G NR-RAN 120 and LTE-RAN 122 may be portions of a cellular network that can be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0021] UEs 110 and 112 can connect to 5G NR-RAN 120 via at least one of next-generation node B (gNB) 120A and / or gNB 120B. gNBs 120A and 120B can be configured with the necessary hardware (e.g., antenna arrays), software, and / or firmware to perform massive MIMO functionality. Massive MIMO can refer to a base station configured to generate multiple beams for multiple UEs. Reference to the two gNBs 120A and 120B is for illustrative purposes only. Exemplary implementations can be applied to any suitable number of gNBs. For example, UEs 110 and 112 can simultaneously connect to and exchange data with multiple gNBs in a multi-cell CA configuration. UEs 110 and 112 can also connect to LTE-RAN 122, or any other type of RAN, as described above, via either or both of eNBs 122A and 122B. In network configuration 100, UE 110 is shown to have a connection to gNB 120A, while UE 112 is shown to have a connection to gNB 120B.

[0022] In addition to networks 120, 122, and 124, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of the cellular network (e.g., NR's 5GC). The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140.

[0023] IMS 150 can generally be described as an architecture for delivering multimedia services to UE 110 using the IP protocol. IMS 150 can communicate with cellular core network 130 and Internet 140 to provide multimedia services to UE 110. Network service backbone 160 communicates directly or indirectly with Internet 140 and cellular core network 130. Network service backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of UE 110 to communicate with various networks.

[0024] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory layout 210, display device 215, input / output (I / O) device 220, transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing a limited power source, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, sensors for detecting the status of UE 110, etc. Figure 2 The UE 110 shown can also represent UE 112.

[0025] Processor 205 may be configured to execute multiple engines of UE 110. For example, these engines may include a PDCCH detection engine 235 for performing operations including: selecting a decoding scheme for PDCCH repetitions in a repetition set; and determining a scaling factor for the search space (SS) or control resource set (CORESET) used to carry PDCCH repetitions. These operations may also include: calculating the number of blind decodes (BDs) to be used for PDCCH reception, in part based on the scaling factor of the SS / CORESET used to carry PDCCH repetitions; and performing an oversubscription operation to reduce the BD count to within the specified limit when the number of BDs exceeds a specified limit, as described in further detail below.

[0026] The engine described above, as an application (e.g., a program) executed by processor 205, is merely exemplary. The functionality associated with the engine may also be represented as a separate integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuitry for receiving signals and a processing circuitry for processing signals and other information. The engine may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0027] Memory 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G-NR RAN 120, LTE RAN 122, etc. Therefore, transceiver 225 can operate on various frequencies or channels (e.g., consecutive frequency groups).

[0028] Figure 3 An exemplary network cell according to various exemplary embodiments is shown, in this example being gNB 120A. As described above with reference to UE 110, gNB 120A may represent a cell that provides services as a PCell or SCell or is configured independently of UE 110. gNB 120A may represent any access node of a 5G NR network through which UEs 110 and 112 can establish connections and manage network operations. Figure 3 The gNB 120A shown can also represent gNB 120B.

[0029] The gNB 120A may include a processor 305, a memory arrangement 310, input / output (I / O) devices 320, a transceiver 325, and other components 330. Other components 330 may include, for example, audio input devices, audio output devices, a battery, data acquisition devices, and ports for electrically connecting the gNB 120A to other electronic devices.

[0030] Processor 305 may be configured to execute multiple engines of gNB 120A. For example, these engines may include a PDCCH transmission engine 335 for performing operations such as transmitting PDCCH to the UE using PDCCH repetition operations, as will be described in further detail below. These operations also include: determining one or more scaling factors to be used by the UE to calculate the number of BDs for PDCCH reception; and signaling the scaling factors to the UE.

[0031] The engines described above, each acting as an application (e.g., a program) executed by processor 305, are merely exemplary. The functionality associated with the engines may also be represented as a separate integrated component of gNB 120A, or as a modular component coupled to gNB 120A, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuitry for receiving signals and a processing circuitry for processing signals and other information. Furthermore, in some gNBs, the functionality described for processor 305 is split among multiple processors (e.g., a baseband processor, an application processor, etc.). Exemplary implementations may be implemented according to any of these or other configurations of the gNB.

[0032] Memory 310 may be a hardware component configured to store data related to operations performed by UEs 110 and 112. I / O device 320 may be a hardware component or port enabling a user to interact with gNB 120A. Transceiver 325 may be a hardware component configured to exchange data with UEs 110, 112, and any other UE in system 100. Transceiver 325 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). Therefore, transceiver 325 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0033] PDCCH repeated reception

[0034] A control resource set (CORESET) is a group of resource elements (REGs) (each REG includes a resource block in the frequency domain and an OFDM symbol in the time domain) in which the UE attempts to blindly decode downlink control information (DCI) from the PDCCH. A CORESET can be viewed as a set of physical resources, such as a specific area on the NR downlink resource grid, and a set of parameters used to carry PDCCH data, such as downlink control information (DCI).

[0035] Each CORESET can have one or more defined search spaces (SS). The PDCCH search space refers to the area in the downlink resource grid that can carry PDCCH. Downlink control channels are transmitted by aggregation of one or more consecutive control channel elements (CCEs), each CCE comprising multiple resource element groups (REGs), for example, 6 REGs (72 resource elements (REs)). The number of REs in the control resource set (CORESET) used to carry PDCCH downlink control information (DCI) messages is called the aggregation level (AL) and is represented by CCEs. In 5G NR, five different PDCCH CCE ALs (AL 1, 2, 4, 8, and 16) are currently supported, which specify the number of CCEs used to carry PDCCH DCI messages.

[0036] The PDCCH search space comprises a UE-dedicated search space and a public (cell-specific) search space for the UE to monitor potential DCI formats, including, for example, downlink (DL) grants and uplink (UL) grants. The UE-dedicated search space is configured for the UE via Radio Resource Control (RRC) signaling and is reserved for a specific UE, while the public search space is for all or at least a group of UEs in a cell with an RRC connection to the network / gNB. The CCE index is the CCE number assigned to the PDCCH. For the UE to decode the PDCCH, it needs to know the PDCCH's location (CCE index), structure, scrambling code, etc. However, the UE is not informed of the exact aggregation level (AL) or DCI format used for PDCCH reception. Instead, it is configured with a set of ALs and multiple DCI formats to ensure scheduling flexibility on the gNB side, and therefore the UE performs blind decoding throughout the search space to find the PDCCH data (e.g., DCI).

[0037] In the 3GPP standard Rel-17, to improve the reliability of PDCCH decoding, PDCCH can be transmitted using different beams through multiple repetitions. Each repetition can be transmitted via a SS and an associated CORESET, where the SS provides time-domain resources and the CORESET provides frequency-domain resources and beam information. Repetitions can be transmitted within a time slot (intra-time slot repetition) or across time slots (inter-time slot repetition). Figure 4a An exemplary PDCCH transmission 400 using intra-slot repetition is shown, wherein the first repetition and the second repetition are located in the same time slot. Figure 4b An exemplary PDCCH transmission 450 using inter-slot repetition is shown, wherein a first repetition is located within a first time slot and a second repetition is located within a second time slot. Additionally, as will be further described below, intra-slot repetition can be transmitted across spans within the time slot (inter-span repetition), these spans having a smaller granularity relative to that time slot.

[0038] Various schemes exist for detecting PDCCH repetitions. In the first scheme, the UE may attempt to detect each PDCCH repetition independently. If either of the two repetitions is successfully decoded, the PDCCH is considered "detected". In the second scheme, the UE combines the soft bits of each repetition and uses the combined soft bits to jointly decode the PDCCH.

[0039] When using the first scheme, the UE blindly detects the PDCCH candidates for each CORESET / SS. The number of blind decodings (BD) per slot is counted based on the control channel element (CCE) aggregation level (AL), the number of RBs in the CORESET, etc., and should not exceed the predefined upper limit as currently specified in Section 10.1 of 3GPP TS 38.213.

[0040] When using the second scheme, the UE performs demodulation independently for each PDCCH candidate in the PDCCH candidate pair. The UE performs soft combination on the demodulation soft bits of each PDCCH in the PDCCH candidate pair. The number of BDs can be counted at the PDCCH candidate pair level. That is, each pair of PDCCH candidates carrying the same repetition is counted as one BD attempt. It should be understood that although the term PDCCH candidate pair means 2 repetitions, those skilled in the art will understand that the exemplary implementation is applicable to schemes with more than 2 repetitions (e.g., 3 or more repetitions).

[0041] Search space (SS) oversubscription can occur when the number of BD / CCEs configured for PDCCH decoding exceeds the upper limit defined for the primary serving cell (PCell) as currently in Tables 10.2 and 10.3 of TS 38.213. When oversubscription occurs, some SSs may need to be dropped from the UE's blind detection operation. In this case, the UE first starts detecting CSSs from the lowest common search space (CSS) ID and continues detecting CSSs in ascending order of CSS ID, then starts detecting USSs from the lowest UE-specific SS (USS) ID and continues detecting USSs in ascending order of USS ID. For example, when the total number of BD / CCEs considering the number of USSs (e.g., j) exceeds the upper limit, the UE drops all USSs with IDs equal to or greater than j. If the total number of BD / CCEs considering each configured USS exceeds the upper limit, the UE then drops CSSs starting from the largest CSS ID.

[0042] The UE behavior for detecting PDCCH repetition is unclear for the following scenarios. First, it is not specified how to count the BD limit for PDCCH repetition for different reception schemes (independent detection and soft combination), particularly for inter-slot PDCCH repetition with soft combination-based detection. Furthermore, oversubscription effects should be considered regarding BD counting for different reception schemes. Second, regarding oversubscription effects, it is not specified how to determine the DCI drop rules and scheduling offsets or action delays based on repetition operations.

[0043] Based on the various exemplary embodiments described herein, a framework for BD / CCE counting and oversubscription for repeated PDCCH operations is described.

[0044] For repetition within a time slot (as described above) Figure 4a Similar to Rel-15, the number of BDs can be counted per time slot. If the first reception scheme (independent detection) is used, the number of BDs can be counted independently at the PDCCH candidate level, for example, counting for each candidate from a candidate pair. If the second reception scheme (soft combining) is used, the number of BDs can be counted at the PDCCH candidate pair level, for example, counting once for each candidate pair. In another implementation, a scaling factor can be used to scale the count value of candidate pairs, similar to the second option with soft combining and inter-slot repetition, which will be explained in detail below.

[0045] For time slot repetition (as mentioned above) Figure 4b If the first receiving scheme (independent detection) is used, the number of BDs can be counted per time slot. If the second receiving scheme (soft combining) is used, the number of BDs can be counted according to the following options.

[0046] In the first option, which will be explained in detail below, for inter-slot repetitions using a soft combination detection scheme, BDs can be counted per slot, wherein different slots from a set of PDCCH repetitions can be counted differently according to a scaling factor, as described below. In the second option, which will be explained in detail below, BDs are counted at a multi-slot level, wherein the granularity of the BD count can be based on the duration of a set of PDCCH repetitions, as described below.

[0047] BD counting with soft-combined inter-slot PDCCH repetition—first option

[0048] The UE can choose different schemes to repeatedly perform soft combination for a set of PDCCHs in N time slots (e.g., N=2). In the first scheme, the UE first detects the soft bits of each PDCCH candidate in the first N-1 time slots, and then detects the soft bits of each PDCCH candidate in the last time slot. Then, the UE performs soft combination on the soft bits of the corresponding PDCCH candidates in the candidate pair, and performs channel decoding with the combined soft bits. That is, when a PDCCH is received, the UE processes the PDCCH candidates to detect the soft bits, and when all candidates of the candidate pair are received, soft combination and decoding are performed in the last time slot. In the second scheme, the UE buffers the corresponding data of each PDCCH candidate in the first N-1 time slots, and detects the soft bits of all PDCCH candidates in the last time slot. Similar to the above, when all candidates are received, the UE performs soft combination and channel decoding in the last time slot.

[0049] For each of the above schemes, the UE complexity for a given time slot can be different. For example, the UE may perform a reduced number of calculations in an earlier time slot relative to the last time slot, such as combining and decoding soft bits of PDCCH candidates in the last time slot. BD limits are partially imposed to limit the UE complexity of searching and decoding PDCCH. Therefore, in some embodiments described herein, a scaling factor is introduced to count the number of BDs in a time slot, thereby taking into account the different UE complexities across multiple time slots.

[0050] As described in the first option above, the BD count of the SS in the PDCCH repeat set is scaled by scaling factors N1 and N2. The value of N1 can be used for the SS in the first N-1 slots, and N2 can be used for the SS in the last slot (N). In some exemplary embodiments, N2 > N1 to account for the increased processing burden imposed in the last slot for performing soft combination and channel decoding (the processing burden is not imposed in the earlier slots). The value of N2 can be configured based on the total number of candidate PDCCH repeat pairs.

[0051] The N1 and N2 values ​​can be determined for the UE and the network in the following ways. In some exemplary implementations, the UE may have N1 and N2 values ​​configured based on its capabilities, and may report these values ​​to the network. N1 and N2 may be different or the same for different configurations of the CORESET / SS group and PDCCH candidate link schemes; for example, N1 and N2 for a CORESET with different bandwidths may differ from N1 and N2 for a CORESET with the same bandwidth. Multiple schemes may be reported to the network, allowing the network to select a scheme for the UE based on the SS / CORESET to be used for PDCCH transmission.

[0052] In other exemplary embodiments, N1 and N2 can be configured for the UE via RRC signaling from the network. N1 and N2 can be configured per serving cell, per BWP, or per CORESET / SS group of PDCCH repeat sets. In other exemplary embodiments, N1 and N2 can be predefined and known to both the UE and the network.

[0053] Figure 5 Illustration 500 illustrates a method for counting blind decoding (BD) during an exemplary PDCCH repetition operation, according to various exemplary embodiments described herein. Illustration 500 relates to inter-slot PDCCH repetition using soft combination to decode the PDCCH as described above. Figure 5 In the exemplary operation, N1 = 0.5, N2 = 1.5, and two repetitions are used in each repetition set. PDCCH candidates are mapped 1:1 in the repetition sets.

[0054] Figure 500 includes six time slots, namely slots 0-5. In this exemplary operation, the UE is configured with three UE-specific search spaces (USS), namely USS 1, USS 2, and USS 3. The first PDCCH repetition set includes 10 BDs in USS 1 in slot 0 and 10 BDs in USS 2 in slot 1. The second PDCCH repetition set includes 22 BDs in USS 2 in slot 2 and 22 BDs in USS 1 in slot 3. The third PDCCH repetition set includes 20 BDs in USS 2 in slot 4 and 20 BDs in USS 1 in slot 5. USS 3 is configured for 20 BDs in slots 0 and 1, 18 BDs in slot 2, 16 BDs in slots 3 and 4, and 20 BDs in slot 5, which are not configured for PDCCH repetition.

[0055] To count the BDs (Browser Dividers) to ensure that the BDs in each slot are within the maximum specified BD limit, factors N1 and N2 are applied to the SS (Slots) carrying PDCCH repetitions. As noted above, for the earlier slots in the repetition scheme (slots 0, 2, and 4), N1 = 0.5, and for the last slot in the repetition scheme (slots 1, 3, and 5), N2 = 1.5. Therefore, the total number of BDs in slot 0 is equal to 20 (for USS 3) + 10 * 0.5 (for USS 1) = 25. The total number of BDs in slot 1 is equal to 20 (for USS 3) + 10 * 1.5 (for USS 1) = 35. The total number of BDs in slot 2 is equal to 18 (for USS 3) + 22 * ​​0.5 (for USS 2) = 29. The total number of BDs in slot 3 is equal to 16 (for USS 3) + 22 * ​​1.5 (for USS 1) = 49. The total number of BDs in time slot 4 is 16 (for USS3) + 20 * 0.5 (for USS 2) = 26. The total number of BDs in time slot 5 is 20 (for USS 3) + 20 * 1.5 (for USS 1) = 50.

[0056] Over-order processing

[0057] If the number of Business Controllers (BDs) configured for a time slot exceeds the maximum specified BD limit, the time slot is considered oversubscribed. In the case of oversubscription, some Service Controllers (SSs) can be prioritized for searching (e.g., PDCCH detection), while other SSs are discarded (not searched), so that the UE does not exceed the BD limit. The following options are available to the UE for handling oversubscribed time slots.

[0058] In the first option, priority can be determined based on the highest or lowest priority SS / CORESET in the PDCCH repeating SS / CORESET group. That is, identify the SS / CORESET configured to carry PDCCH repeating from the PDCCH candidate pair, and determine the priority among these one or more SS / CORESETs based on their SS / CORESET IDs. These SS / CORESETs are discarded based on the determined priority until BD / CCE is within the specified limits. When discarding one SS from an SS group, the entire SS group can be discarded.

[0059] In the second option, priority can be counted per SS / CORESET level. That is, regardless of which SS / CORESET carries a duplicate PDCCH, priority is determined among all SS / CORESETs configured for the UE. These SS / CORESETs are dropped based on the determined priority until BD / CCE is within the specified limit. Similar to the first option, if one SS is dropped, the entire SS group should be dropped.

[0060] In the third option, priority can be counted per SS level. If an SS is dropped, the other SSs in that SS group remain usable. In this case, the number of BDs can be recalculated because the UE can change its reception scheme. An additional or predefined set of N1 and N2 can be applied to recalculate the BDs; for example, N1=1, N2=1, which implies that the UE will use a soft-combined reception scheme. In some implementations, scheduling offsets and DCI action delays can be counted based on the last actual transmitted PDCCH repetition, while in other implementations, they can be counted based on the most recent nominal PDCCH repetition. References will follow below. Figure 6 Please explain the third option in more detail.

[0061] In the fourth option, the UE can be configured with different priority orders for different search space sets by a higher layer. In the case of oversubscription, PDCCH candidates are discarded starting from the lower priority search space set in ascending or descending order of the PDCCH candidate index. In some designs, to further reduce UE complexity, PDCCH candidates can be discarded based on the aggregation level (AL), that is, once a candidate is discarded for a given AL, all candidates associated with that AL are discarded.

[0062] Figure 6Illustration 600 illustrates a method for counting blind decoding (BD) in an exemplary PDCCH repetition operation for search space oversubscription, according to various exemplary embodiments described herein. Illustration 600 relates to inter-slot PDCCH repetitions for decoding PDCCHs using soft combination, as described above, for oversubscription processing according to a third option (priority counted per SS level, where if an SS is discarded, the other SSs in the group are still used). Figure 6 In the exemplary operation, N1 = 0.5, N2 = 1.5, and two repetitions are used in each repetition set. PDCCH candidates are mapped 1:1 in the repetition sets.

[0063] Figure 600 includes six time slots, namely slots 0-5. In this exemplary operation, the UE is configured with one common search space (CSS 0) and two UE-specific search spaces (USS), namely USS 1 and USS 2. The first PDCCH repetition set includes 10 BDs in USS 1 in slot 0 and 10 BDs in USS 2 in slot 1. The second PDCCH repetition set includes 22 BDs in USS 2 in slot 2 and 22 BDs in USS 1 in slot 3. The third PDCCH repetition set includes 20 BDs in USS 2 in slot 4 and 20 BDs in USS 1 in slot 5. CSS 0 is configured for 20 BDs in slots 0 and 1, 18 BDs in slot 2, 16 BDs in slots 3 and 4, and 20 BDs in slot 5, which are not configured for PDCCH repetition.

[0064] exist Figure 6 In the example above, the maximum number of BDs is 44 per time slot. Similar to the above... Figure 5 To count the BDs to ensure that the BDs per slot are within the maximum specified BD limit (44), factors N1 and N2 are applied to the SSs carrying PDCCH repetitions. As noted above, N1 = 0.5 for the earlier slots in the repetition scheme (slots 0, 2, and 4), and N2 = 1.5 for the last slot in the repetition scheme (slots 1, 3, and 5). Therefore, the total number of BDs for slot 0 is equal to 20 (for CSS 0) + 10 * 0.5 (for USS 1) = 25. The total number of BDs for slot 1 is equal to 20 (for CSS 0) + 10 * 1.5 (for USS 1) = 35. The total number of BDs for slots 0 and 1 is within the maximum BD limit of 44, so no oversubscription operation is required to reduce the BDs to an acceptable limit.

[0065] However, for slots 2-5, oversubscription is applied as follows. For slot 3, regardless of the BD limit, the total number of BDs would be 16 (for CSS 0) + 22 * ​​1.5 (for USS1) = 49. However, considering the BD limit of 44, slot 3 will be oversubscribed. Therefore, as... Figure 5 As shown, USS 1 is discarded in slot 3. Discarding USS 1 means that the second repetition of PDCCH repetition set 2 is not detected, leaving only the first repetition of set 2 for detection in USS 2 within slot 2. Because soft combination operation cannot be performed, the UE reverts to the independent detection scheme for the payload of PDCCH repetition set 2. Therefore, the total number of BDs in slot 2 is equal to 18 (for CSS 0) + 22 (for USS 2) = 40. As shown in the calculation above, because the detection scheme has changed, the BDs of USS 2 are not scaled (as would be scaled if soft combination operation were used). Given that USS 1 is discarded, the total number of BDs in slot 3 is equal to 16 (for CSS 0). Therefore, the BD counts for slots 2 and 3 are within the BD limit of 44.

[0066] Similar to the above, for slot 5, ignoring the BD limit, the total number of BDs would be 20 (for CSS 0) + 20 * 1.5 (for USS1) = 50. However, considering the BD limit of 44, slot 5 will be oversubscribed. Therefore, as... Figure 5 As shown, USS 1 is discarded from slot 5. Discarding USS 1 means that the second repetition of PDCCH repetition set 3 is not detected, leaving only the first repetition of set 3 for detection in USS 2 in slot 4. Similar to the above, the UE reverts to an independent detection scheme for the payload of PDCCH repetition set 3. Therefore, the total number of BDs in slot 4 is equal to 16 (for CSS 0) + 20 (for USS 2) = 36. Given that USS 1 is discarded, the total number of BDs in slot 5 is equal to 20 (for CSS 0). Therefore, the BD counts in slots 4 and 5 are within the BD limit of 44.

[0067] BD Counting with Soft-Combined Inter-Slot PDCCH Repetition—Second Option

[0068] For soft combination with N PDCCH repetitions, the UE still needs to perform some additional steps, such as N-1 repetitions of resource demapping, channel estimation, demodulation, etc. According to the second option of inter-slot repetition using the soft combination detection scheme, the number of BDs is counted based on the maximum duration of the SSs in the group. For this option, each SS in the group should not span the BD granularity (e.g., the frequency subband of the SS group).

[0069] For SSs within a group, the number of BDs is scaled by a factor X. In some implementations, the UE may report the X value based on its capabilities. In other implementations, the value of X can be configured via RRC signaling, for example, per serving cell, per BWP, or per CORESET / SS group per PDCCH repeat set. In yet another implementation, X may be predefined. The maximum number of BDs for a given duration can also be predefined, configured by the gNB, or reported by the UE. For oversubscription processing, when an SS / CORESET is discarded, the BDs can be recalculated using the four options discussed above.

[0070] Figure 7 Illustration 700 illustrates a method for counting blind decoding (BD) in an exemplary multi-slot-based PDCCH repetition operation according to various exemplary embodiments described herein. Illustration 700 relates to inter-slot PDCCH repetition using soft combination to decode the PDCCH as described above. Figure 7 In the exemplary operation, X = 1.5 and two repetitions are used in each repetition set. PDCCH candidates are mapped 1:1 in the repetition sets.

[0071] Figure 700 includes six time slots, namely slots 0-5. In this exemplary operation, the UE is configured with one common search space (CSS 0) and two UE-specific search spaces (USS), namely USS 1 and USS 2. The first PDCCH repetition set includes 10 BDs in USS 1 in slot 0 and 10 BDs in USS 2 in slot 1. The second PDCCH repetition set includes 22 BDs in USS 2 in slot 2 and 22 BDs in USS 1 in slot 3. The third PDCCH repetition set includes 20 BDs in USS 2 in slot 4 and 20 BDs in USS 1 in slot 5. CSS 0 is configured for 20 BDs in slots 0 and 1, 18 BDs in slot 2, 16 BDs in slots 3 and 4, and 20 BDs in slot 5, which are not configured for PDCCH repetition.

[0072] To count the BDs and ensure they remain within the maximum specified BD limit based on multi-slot considerations, a factor X is applied to the BD count of the SSs in the SS group carrying PDCCH repetitions. As noted above, X = 1.5. Therefore, the total number of BDs for slots 0-1 is equal to 20 (for CSS 0 slot 0) + 20 (for CSS 0 slot 1) + 10 * 1.5 (for repetition set 1 including USS 1 in slot 0 and USS 2 in slot 1) = 45. The total number of BDs for slots 2-3 is equal to 18 (for CSS 0 slot 2) + 16 (for CSS 0 slot 3) + 22 * ​​1.5 (for repetition set 2 including USS 2 in slot 2 and USS 1 in slot 3) = 45. The total number of BDs in slots 4-5 is equal to 16 (for CSS 0 slot 4) + 20 (for CSS 0 slot 5) + 20 * 1.5 (for the repeating set 3 including USS 2 in slot 4 and USS 1 in slot 5) = 66.

[0073] Span-based monitoring

[0074] Section 10.1 of TS 38.213 supports PDCCH monitoring based on each span. Compared to slots based on the same SCS, a span is a smaller granularity and is defined as (X,Y) symbols, where X is the number of consecutive symbols in the span and Y indicates the number of symbols used for PDCCH within the span.

[0075] The two options discussed above for slot-based operations can be extended to span-based operations. That is, the two options for inter-slot repetition using a soft-combination detection scheme can be equivalently applied to inter-span repetition using a soft-combination detection scheme. Therefore, when repetition spans a span, the exemplary implementation extends to intra-slot PDCCH repetition.

[0076] method

[0077] Figure 8 A method 800 for counting blind decoding (BD) in an exemplary PDCCH repetition operation is illustrated according to various exemplary embodiments described herein. Method 800 relates to using soft combination to decode inter-slot or inter-span PDCCH repetitions of the PDCCH, as discussed above.

[0078] In 805, the network configures a PDCCH configuration to the User Equipment (UE), which includes at least one repetition set of first PDCCH data (e.g., first DCI). As discussed above, the PDCCH payload can be subject to repeated configurations, where the same payload is transmitted multiple times within a time slot (intra-time slot) or across time slots (inter-time slot), or within a span (intra-span) or across a span (inter-span). Figure 8In an exemplary PDCCH operation, the repetition configuration is configured between time slots or spans. The first PDCCH data can be configured with two or more repetitions spanning multiple time slots / spans.

[0079] In 810, the UE selects a repetition reception scheme for decoding the first PDCCH data. As discussed above, the UE can attempt to decode each repetition independently, or it can perform soft combination on the detection bits from each repetition. Figure 8 In an exemplary PDCCH operation, the UE selects soft combining as the repetitive reception scheme for decoding the first PDCCH data.

[0080] In 815, the UE selects a soft combination scheme for decoding the first PDCCH data. As discussed above, in the first soft combination scheme, the UE can detect the soft bits of each PDCCH candidate in the first N-1 time slots / spans, and then detect the soft bits of each PDCCH candidate in the last time slot / span. The UE then performs soft combination on the soft bits of the corresponding PDCCH candidates in the candidate pairs and performs channel decoding using the combined soft bits. In the second soft combination scheme, the UE can buffer the corresponding data of each PDCCH candidate in the first N-1 time slots / spans and detect the soft bits of all PDCCH candidates in the last time slot / span. Similar to the above, when all candidates are received, the UE performs soft combination and channel decoding in the last time slot / span.

[0081] In 820, the UE and / or network determine one or more scaling factors to apply to the BD count for time slots carrying repeated PDCCH candidates. The BD count can be on a per-slot basis (e.g., as described above). Figure 5 ), on the basis of multiple time slots (for example, the above) Figure 7 Alternatively, it can be determined on a per-span basis, as discussed above. Depending on the configured BD counting operation (per slot, multiple slots, per span), different scaling factors may be used.

[0082] In per-slot or per-span BD counting operations, scaling factors N1 and N2 can be used. Scaling factor N1 can be used for earlier slots / spans (e.g., the first N-1 slots / spans of N slots / spans carrying the first PDCCH data), and scaling factor N2 can be used for the last slot / span (e.g., slot / span N). In multi-slot BD counting operations, scaling factor X can be used.

[0083] The scaling factor can be determined in the following ways. In some implementations, the UE may have a scaling factor value configured based on its capabilities and may report these values ​​to the network. If multiple potential scaling factor value options are reported, the network may select one of these options and signal this configuration to the UE. In other implementations, the network configures the scaling factor value via, for example, RRC signaling. In other implementations, the scaling factor value is predefined.

[0084] In 825, the UE determines the BD count for the configured BD count duration (per slot, multiple slots, or per span). Typically, the BD is summed for each SS / CORESET configured for PDCCH reception within this duration. For example, multiple SSs can be configured, each carrying a number of PDCCH candidates that are blindly decoded to locate PDCCH data. However, when some of the PDCCH candidates are configured to carry PDCCH repetitions from a repetition set, a scaling factor is applied to these PDCCH candidates.

[0085] Regarding BD counts per slot or per span, as discussed above, N1 applies to SS / CORESETs configured in earlier slots / spans, and N2 applies to SS / CORESETs configured in the last slot / span. Therefore, if an SS is configured to carry repetition in a given slot / span, the PDCCH candidates for that SS are scaled for that slot / span. Regarding multi-slot BD counts, as discussed above, the BD value of a PDCCH candidate repeating across multiple slots is equal to the number of PDCCH candidates in a single slot among those slots scaled by a scaling factor X.

[0086] In 830, the UE determines whether the duration has been oversubscribed by comparing the BD count of the duration with the maximum specified BD limit of the time slot.

[0087] In 835, when the UE determines that the duration has been oversubscribed, the UE performs an oversubscription operation to reduce the number of BDs. The oversubscription operation typically involves dropping certain SSs based on priority order until the BD count is within a specified limit. Various options are available for determining the priority, which can be based on, for example, the SS IDs of the configured set of SSs, as discussed in detail above.

[0088] Example

[0089] In a first embodiment, a user equipment (UE) is provided, comprising: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform operations. These operations include: receiving a configuration for a physical downlink control channel (PDCCH) including repetitions of PDCCH candidates comprising first PDCCH data, wherein these PDCCH candidates repeat for multiple durations across a DL resource grid; detecting each of these PDCCH candidates based on a repetition detection scheme, and combining soft bits from each of these PDCCH candidates, wherein the combined soft bits are jointly decoded to determine the first PDCCH data; and calculating the number of blind decodings (BDs) for the durations of the DL resource grid carrying the PDCCH candidates, wherein at least one BD value of the PDCCH candidates is scaled by a scaling factor to calculate the number of BDs.

[0090] In the second embodiment, according to the UE of the first embodiment, the duration is a time slot or span, and the first BD value of the PDCCH candidate from the earlier duration N-1 of these durations is scaled by a first scaling factor, and the second BD value of the PDCCH candidate from the last duration N is scaled by a second scaling factor different from the first scaling factor.

[0091] In the third embodiment, according to the UE of the second embodiment, the second scaling factor for the last duration N is greater than the first scaling factor for the earlier durations N-1.

[0092] In the fourth embodiment, according to the UE of the third embodiment, the first scaling factor and the second scaling factor depend on a soft combination scheme used by the UE for the PDCCH candidate decoding, wherein the first soft combination scheme includes: detecting soft bits from each of the earlier durations N-1 and the last duration N, and combining the soft bits in the last duration N, and wherein the second soft combination scheme includes: buffering data from each of the earlier durations N-1, detecting soft bits from each of the earlier durations in the last duration N, and combining the soft bits in the last duration N.

[0093] In the fifth embodiment, according to the UE of the third embodiment, the first scaling factor and the second scaling factor depend on the configuration of the multiple duration control source set (CORESET) and search space (SS) of the DL source grid used to carry these PDCCH candidates.

[0094] In the sixth embodiment, according to the UE of the first embodiment, the duration is a time slot, and the BD value is calculated on an inter-time slot basis for the plurality of time slots, the BD value of the PDCCH candidates that repeat across the plurality of time slots is equal to the number of PDCCH candidates in a single time slot among the time slots scaled by a scaling factor.

[0095] In the seventh embodiment, according to the UE of the first embodiment, the number of BDs for these durations is calculated by adding at least one BD value of these PDCCH candidates to the additional BD value of additional PDCCH candidates carried in the DL resource grid, and the number of BDs is compared with a maximum BD limit to determine whether one or more of these durations include a number of BDs exceeding the maximum BD limit.

[0096] In the eighth embodiment, according to the UE of the seventh embodiment, the operations further include: performing an oversubscription operation when one or more of the durations include a number of BDs exceeding the maximum BD limit.

[0097] In the ninth embodiment, according to the UE of the eighth embodiment, the oversubscription operation includes: discarding some of the configured PDCCH candidates such that these candidates are not searched, and recalculating the number of BDs without including these discarded PDCCH candidates.

[0098] In the tenth embodiment, according to the UE of the ninth embodiment, the oversubscription operation further includes: determining the priority of each SS in a plurality of search spaces (SS), wherein the lowest priority SS is discarded until the number of BDs is within the maximum BD limit.

[0099] In the eleventh embodiment, the UE according to the tenth embodiment, wherein the priority is determined based on an SS group and an SS identifier, wherein the SS group includes either a common search space (CSS) or a UE-specific search space (USS).

[0100] In the twelfth embodiment, according to the eleventh embodiment of the UE, when one SS from a given SS group is discarded, the entire SS group is discarded.

[0101] In the thirteenth embodiment, according to the eleventh embodiment, when one of these PDCCH candidates that repeats across the plurality of durations is discarded, the other PDCCH candidates among these PDCCH candidates are not discarded.

[0102] In the fourteenth embodiment, according to the UE of the thirteenth embodiment, when one of these PDCCH candidates that repeats across the plurality of durations is discarded, the other PDCCH candidates among these PDCCH candidates are not discarded, and when only a single PDCCH candidate from a set of PDCCH candidates that has undergone repetition has not yet been discarded, these operations also include decoding the PDCCH candidate without soft combining and without using the scaling factor to calculate the BD value.

[0103] In the fifteenth embodiment, according to the UE of the thirteenth embodiment, the scheduling offset and DCI action delay are counted based on the last actually transmitted PDCCH repetition or the most recent nominal PDCCH repetition.

[0104] In the sixteenth embodiment, the UE according to the ninth embodiment is wherein the priority is determined based on higher-layer signaling.

[0105] In the seventeenth embodiment, the UE according to the first embodiment is provided, wherein the scaling factor is based on the UE capability, and the operations further include reporting at least one potential scaling factor to the network.

[0106] In the eighteenth embodiment, the UE according to the seventeenth embodiment, wherein these operations further include a configuration for receiving the scaling factor from the network, wherein the scaling factor is selected from at least one reported potential scaling factor.

[0107] In the nineteenth embodiment, according to the UE of the first embodiment, these operations further include receiving the scaling factor from the network via Radio Resource Control (RRC) signaling.

[0108] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, desktop platforms with operating systems or mobile devices with operating systems. In yet another example, an exemplary embodiment of the above methods may be embodied as a program containing lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0109] Although this patent application describes various combinations of aspects, each with different features, those skilled in the art will understand that any feature of one aspect can be combined with features of other aspects or features that are not functionally or logically inconsistent with the operation or function of the device of the aspect disclosed in this invention in any manner not disclosed to be denied.

[0110] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0111] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor for a user equipment (UE), the processor being configured to perform operations including: Configuration for receiving physical downlink control channel (PDCCH), the PDCCH including repetition of PDCCH candidates including first PDCCH data, wherein the PDCCH candidates are repeated for multiple durations across DL resource grids; Each PDCCH candidate in the PDCCH candidates is detected based on a duplicate detection scheme, and the soft bits from each PDCCH candidate in the PDCCH candidates are combined, wherein the combined soft bits are jointly decoded to determine the first PDCCH data. Calculate the number of blind decodings (BDs) for the duration of the DL resource grid carrying the PDCCH candidate, wherein at least one BD value of the PDCCH candidate is scaled by a scaling factor to be used to calculate the number of BDs; Compare the number of BDs with the maximum BD limit; Determine whether one or more of the durations include the number of BDs exceeding the maximum BD limit; When one or more of the durations comprise a number of BDs exceeding the maximum BD limit, an oversubscription operation is performed; and The priority of each SS in a plurality of search spaces (SS) is determined, wherein the lowest priority SS is discarded until the number of BDs is within the maximum BD limit, wherein the priority is determined based on SS groups and SS identifiers, wherein the SS groups include one of a common search space (CSS) or a UE-specific search space (USS).

2. The processor of claim 1, wherein the duration is a time slot or a span, and The first BD value of the PDCCH candidate from the earlier duration N-1 of the durations is scaled by a first scaling factor, and the second BD value of the PDCCH candidate from the last duration N is scaled by a second scaling factor different from the first scaling factor.

3. The processor of claim 2, wherein the second scaling factor for the last duration N is greater than the first scaling factor for the earlier duration N-1.

4. The processor of claim 3, wherein the first scaling factor and the second scaling factor depend on a soft combination scheme used by the UE for PDCCH candidate decoding. The first soft combination scheme includes: Detect the soft bits from each of the earlier duration N-1 and the last duration N, and combine the soft bits in the last duration N. The second soft combination scheme includes: buffering data from each of the earlier durations N-1, detecting the soft bits from each of the earlier durations in the last duration N, and combining the soft bits in the last duration N.

5. The processor of claim 3, wherein the first scaling factor and the second scaling factor depend on the configuration of the control resource set (CORESET) and search space (SS) for the plurality of durations of the DL resource grid that carries the PDCCH candidate.

6. The processor of claim 1, wherein the duration is a time slot, and The BD value is calculated on a time-slot basis for multiple time slots, and the BD value of the PDCCH candidate that repeats across the multiple time slots is equal to the number of PDCCH candidates in a single time slot scaled by a scaling factor.

7. The processor of claim 1, wherein the number of BDs for the duration is calculated by adding the at least one BD value of the PDCCH candidate to the additional BD value of an additional PDCCH candidate carried in the DL resource grid.

8. The processor of claim 7, wherein the oversubscription operation comprises: Discard some of the configured PDCCH candidates so that the candidates are not searched; as well as The number of BDs is recalculated without including the discarded PDCCH candidates.

9. The processor of claim 1, wherein when one SS from a given SS group is discarded, the entire SS group is discarded.

10. The processor according to claim 1, wherein, When one of the PDCCH candidates that repeats across the plurality of durations is discarded, the other PDCCH candidates in the PDCCH candidate list are not discarded.

11. The processor according to claim 10, wherein, When one of the PDCCH candidates that repeats across the plurality of durations is discarded, the other PDCCH candidates in the PDCCH candidate set are not discarded, and The operation also includes decoding the PDCCH candidate without soft combining and without using the scaling factor to compute the BD value when only a single PDCCH candidate from a set of repeated PDCCH candidates has not been discarded.

12. The processor of claim 10, wherein the scheduling offset and DCI action delay are counted based on the last actual transmitted PDCCH repetition or the most recent nominal PDCCH repetition.

13. The processor of claim 1, wherein the priority is determined based on higher-layer signaling.

14. The processor of claim 1, wherein the scaling factor is based on UE capabilities, and the operation further comprises: Report at least one potential scaling factor to the network.

15. The processor of claim 14, wherein the operation further comprises: The configuration of receiving the scaling factor from the network, wherein the scaling factor is selected from at least one reported potential scaling factor.

16. The processor of claim 1, wherein the operation further comprises: The scaling factor is received from the network via Radio Resource Control (RRC) signaling.

17. A user equipment (UE), comprising: A transceiver configured to communicate with a network; and A processor, communicatively coupled to the transceiver and configured to perform operations including: Configuration for receiving physical downlink control channel (PDCCH), the PDCCH including repetition of PDCCH candidates including first PDCCH data, wherein the PDCCH candidates are repeated for multiple durations across DL resource grids; Each PDCCH candidate in the PDCCH candidates is detected based on a duplicate detection scheme, and the soft bits from each PDCCH candidate in the PDCCH candidates are combined, wherein the combined soft bits are jointly decoded to determine the first PDCCH data. Calculate the number of blind decodings (BDs) for the duration of the DL resource grid carrying the PDCCH candidate, wherein at least one BD value of the PDCCH candidate is scaled by a scaling factor to be used to calculate the number of BDs; Compare the number of BDs with the maximum BD limit; Determine whether one or more of the durations include the number of BDs exceeding the maximum BD limit; When one or more of the durations comprise a number of BDs exceeding the maximum BD limit, an oversubscription operation is performed; and The priority of each SS in a plurality of search spaces (SS) is determined, wherein the lowest priority SS is discarded until the number of BDs is within the maximum BD limit, wherein the priority is determined based on SS groups and SS identifiers, wherein the SS groups include one of a common search space (CSS) or a UE-specific search space (USS).

18. A processor for a base station, the processor being configured to perform operations including: Configure a Physical Downlink Control Channel (PDCCH) for User Equipment (UE), the PDCCH including repetition of PDCCH candidates including first PDCCH data, wherein the PDCCH candidates are repeated for multiple durations across a DL resource grid, wherein the UE will use a repetition detection scheme to detect each of the PDCCH candidates and combine soft bits from each of the PDCCH candidates, wherein the combined soft bits are jointly decoded to determine the first PDCCH data; as well as A scaling factor is generated for the signaling to the UE to calculate the number of blind decodings (BDs) for the duration of the DL resource grid carrying the PDCCH candidate, wherein the UE scales at least one BD value of the PDCCH candidate according to the scaling factor to calculate the number of BDs, wherein the duration is a span, and a first BD value of the PDCCH candidate from an earlier duration N-1 of the duration is scaled by a first scaling factor, and a second BD value of the PDCCH candidate from the last duration N is scaled by a second scaling factor different from the first scaling factor.

19. The processor of claim 18, wherein the operation further comprises: Receive at least one potential scaling factor from the UE, the at least one potential scaling factor being based on the UE's capabilities; as well as A scaling factor is selected from the at least one potential scaling factor for the UE to use in the calculation.

20. The processor of claim 18, wherein the operation further comprises: The UE is signaled with the priority of each of the multiple search spaces (SS), wherein when one or more durations of the configured PDCCH include the number of BDs exceeding the maximum BD limit, the UE discards the lowest priority SS until the number of BDs is within the maximum BD limit.

Citation Information

Patent Citations

  • Physical downlink control channel (PDCCH) blind decoding in fifth generation (5G) new radio (NR) systems

    US20190223164A1