Techniques for downlink control information processing

Abstract

Methods, systems, and apparatus for wireless communication at a user equipment (UE) are described. A first network node may receive downlink control information from a second network node based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected for a physical downlink control channel. In some examples, the second physical downlink control channel candidate may end later than the first physical downlink control channel candidate. The first network node may identify a physical downlink shared channel that is not scheduled based on the downlink control information. Then, the first network node may send a feedback message to the base station in response to the downlink control information at least a threshold time unit after the second physical downlink control channel candidate.

Description

[Technical Field]

[0001] Cross-reference to related applications

[0002] This patent application claims priority to the following applications: U.S. Patent Application No. 17 / 686,243, filed March 3, 2022, entitled "TECHNIQUES FOR CALCULATING DOWNLINK CONTROL INFORMATION PROCESSING TIME" by Khoshnevisan et al.; and U.S. Provisional Patent Application No. 63 / 160,646, filed March 12, 2021, entitled "TECHNIQUES FOR CALCULATING DOWNLINK CONTROL INFORMATION PROCESSING TIME", each of which is assigned to the assignee of this application, and the entire contents of each of which is expressly incorporated herein by reference.

[0003] The following text relates to wireless communication UE, including techniques for downlink control information processing. [Previous Technology]

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiplexing access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiple Access (DFT-S-OFDM). A wireless multiplexing access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices (which may also be referred to as user equipment (UE)).

[0005] In some NR systems, two search space sets associated with the same control resource set (CORESET) may overlap, meaning they may have overlapping resource blocks, use the same scrambling, and have the same Transmission Configuration Indicator (TCI) state. Some wireless communication systems can support physical downlink control channel repetition, where each repetition is a physical downlink control channel candidate, and repetitions of two physical downlink control channel candidates for shared control information are linked together. As the demand for communication efficiency increases, improvements to such communication systems may be desired. [Summary of the Invention]

[0006] The described techniques relate to improved methods, systems, nodes, devices, and apparatuses that support techniques for resolving ambiguity in downlink control information transmitted using two or more entity downlink control channel candidates. In some examples, the techniques described herein provide a network node (e.g., a user equipment (UE)) to receive downlink control information using a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly linked for entity downlink control channels. In some examples, the second entity downlink control channel candidate may end later than the first entity downlink control channel candidate. In some examples, the network node may decide to send a feedback message at least a threshold time unit after the second entity downlink control channel candidate. Alternatively or additionally, the network node may decide to overwrite uplink control resources indicated by previous downlink control information based on the determination that the uplink control resources are at least a threshold time unit after the second entity downlink control channel candidate.

Implementation Method

[0020] The described technology relates to methods, systems, devices, and apparatuses that support improvements in techniques for processing downlink control information. In some wireless communication systems, two search space sets may be associated with the same control resource set (CORESET). Some wireless communication systems may support physical downlink control channel repetition, where each repetition is a physical downlink control channel candidate, and repetitions of two physical downlink control channel candidates for the same downlink control information are linked together. For example, physical downlink control channel repetition can be used to improve reliability or add redundancy. For example, wireless communication in a network may be interfered with. Depending on the amount of interference, user equipment (UE) may potentially no longer decode individual physical downlink control channel candidates. Two physical downlink control channel candidates may be linked together for repetition to increase reliability. The UE may perform soft combination of the corresponding signals to decode downlink control information.

[0021] In another example, the network can use two different beams to transmit duplicate physical downlink control channels for redundancy. If one beam is blocked or the aggregation level is too low, a network node (e.g., a UE) may potentially be able to decode downlink control information from the other beam. The downlink control information payloads transmitted using the two physical downlink control channel candidates can be identical.

[0022] Network nodes can perform soft combination of signals associated with physical downlink control channel candidates to decode downlink control information, or use one of the linked physical downlink control channel candidates to decode downlink control information. In some cases, isochrones can be defined for subsequent physical downlink shared channel processing via downlink control information (e.g., in the case of downlink control information scheduling (subsequent) physical downlink shared channel transmission).

[0023] However, there may be other situations where downlink control information is not scheduled for entity downlink shared channels, and the isochrones for downlink control information processing may be ambiguous. For example, an isochrone for responding to downlink control information using feedback transmissions may not be defined, for instance, when downlink control information is received using multiple entity downlink control channel candidates, and it is ambiguous which of the multiple entity downlink control channel candidates can be used as the sole reference point for the isochrone. In another example, the isochrone for overriding (multiplexing) feedback messages in entity uplink control channel resources associated with downlink control information may be ambiguous.

[0024] One or more embodiments of this invention provide techniques for determining the isochrones used for processing downlink control information. In a first example, a network node may use two entity downlink control channel candidates to receive downlink control information. For example, a network node may receive downlink control information based on at least one first entity downlink control channel candidate or a second entity downlink control channel candidate linked for repeated entity downlink control channels. In some examples, the second entity downlink control channel candidate may end later than the first entity downlink control channel candidate. When a network node uses two entity downlink control channel candidates to detect a particular downlink control information format and identifies that the downlink control information does not have a scheduled entity downlink shared channel, the network node may then send a feedback message for at least a threshold number of time units after the second entity downlink control channel candidate. That is, the network node may expect to send a feedback message no earlier than a threshold number of symbols (e.g., N symbols) after the second entity downlink control channel candidate (e.g., the entity downlink control channel candidate that ends later in time).

[0025] In the second example, the network node can receive multiple downlink control messages directed to the same time slot used for feedback transmission. For example, the network node can receive the first downlink control message and the second downlink control message at a later time than the first downlink control message. Specifically, the network node can receive the second downlink control message based on repeatedly monitoring at least one of the first physical downlink control channel candidate or the second physical downlink control channel candidate for the physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate.

[0026] The network node may overwrite the feedback message to be sent in the first entity uplink control channel resource based on the time unit associated with the first entity uplink control channel resource at least a threshold number of time units after the second entity downlink control channel candidate.

[0027] Specific forms of the subject matter described in this application can be implemented to achieve one or more potential improvements, as well as other improvements. The technology employed by the network node can provide benefits and enhancements to the operation of the network node. For example, when operating in a wireless communication system, the operations performed by the network node can provide improvements to communication. In some examples, configuring the network node in a wireless communication system to support technologies for downlink control information processing, and other examples, can support improvements in power consumption, resource utilization, coverage enhancement, spectral efficiency, higher data rates, and other benefits.

[0028] First, the various forms of the present invention are described in the context of a wireless communication system. The various forms of the present invention are shown and described with reference to block diagrams and program flow diagrams. The various forms of the present invention are further illustrated with device diagrams, system diagrams, and flowcharts relating to techniques for downlink control information processing, and the various forms of the present invention are described with reference to these diagrams.

[0029] Figure 1 illustrates examples of a wireless communication system 100 supporting technologies for downlink control information processing according to various embodiments of the present invention. The wireless communication system 100 may include multiple network nodes, such as one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices, or any combination thereof.

[0030] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. Coverage area 110 can be an example of such a geographical area where base stations 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0031] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Some example UE 115s are illustrated in Figure 1. The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backload (IAB) nodes, or other network devices), as shown in Figure 1.

[0032] Base station 105 can communicate with core network 130, or communicate with each other, or perform both of the above operations. For example, base station 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both of the above operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0033] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station transceiver, radio base station, access point, radio transceiver, node B, evolved node B (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), home node B, home evolved node B, or some other suitable term.

[0034] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or user equipment, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless area loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, and other examples, which may be implemented in various articles such as electrical appliances, or vehicles, meters, and other examples.

[0035] The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s that can sometimes act as repeaters, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations and other examples, as shown in Figure 1.

[0036] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can represent a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signal transmissions (e.g., synchronization signals, system information), control signal transmissions coordinating operation for the carrier, user data, or other signal transmissions. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0037] In some examples (e.g., in a carrier aggregation configuration), carriers may also have acquisition signal passing or control signal passing that coordinates operation against other carriers. Carriers may be associated with frequency channels (e.g., Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Channel Number (EARFCN)) and may be positioned according to a channel grid for exploration by UE 115. Carriers may operate in standalone mode, where UE 115 performs initial acquisition and connection via a carrier, or carriers may operate in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0038] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0039] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the "system bandwidth" of the wireless communication system 100. For example, the carrier bandwidth may be one of a number of bandwidths of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have hardware settings supporting communication on a specific carrier bandwidth, or may be configurable to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0040] The signal waveform transmitted on the carrier can be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread spectrum OFDM (DFT-S-OFDM). In a system employing MCM, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate for UE 115 can be. Radio communication resources can represent a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with UE 115.

[0041] One or more numbering schemes for a carrier can be supported, wherein the numbering scheme may include a subcarrier spacing (∆f) and a cyclic prefix. A carrier can be divided into one or more BWPs having the same or different numbering schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0042] The time interval for base station 105 or UE 115 can be represented by a sampling period of a basic time unit (which may be, for example, 1 second), where the maximum supported subcarrier spacing can be represented, and the maximum supported Discrete Fourier Transform (DFT) size can be represented. The time interval of communication resources can be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0043] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier interval. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple microtime slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., ) sampling periods. The duration of a symbol period may depend on the subcarrier interval or the operating frequency band.

[0044] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in the form of a short pulse of a shortened TTI (sTTI)).

[0045] Entity channels can be multiplexed on a carrier using various techniques. For example, one or more of time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex entity control channels and entity data channels on a downlink carrier. A control region (e.g., CORESET) for an entity control channel can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a group of UEs 115. For example, one or more of the UEs 115 can monitor or search for control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. The aggregation level for control channel candidates can represent the number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a downlink control information format having a given payload size. The search space set may include a shared search space set configured to send control information to multiple UEs 115 and a UE-specific search space set configured to send control information to a particular UE 115.

[0046] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may represent a logical communication entity used (e.g., on a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier). In some examples, a cell may also represent a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of base station 105, the range of such cells can be from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, or external spaces between or overlapping geographic coverage areas 110, and other examples.

[0047] Macrocells generally cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 having a service subscription with a network provider supporting the macrocell. Compared to macrocells, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macrocells. Small cells can provide unrestricted access to UE 115 having a service subscription with a network provider, or can provide restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0048] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0049] In some examples, base station 105 may be mobile, and therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0050] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timings, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, base stations 105 can have different frame timings, and in some examples, transmissions from different base stations 105 may not be aligned in time. The techniques described herein can be used for both synchronous and asynchronous operation.

[0051] Some UEs 115 (e.g., MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated machine-to-machine communication (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can represent data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0052] Some UEs 115 can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communication, when operating on limited bandwidth (e.g., according to narrowband communication), or when a combination of these techniques is used. For example, some UEs 115 can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs) within a carrier, within a carrier's guard band, or outside a carrier.

[0053] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 may be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communication and may be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData)). Support for mission-critical functions may include service prioritization, and mission-critical services may be used for public safety or general business applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0054] In some examples, UE 115 can communicate directly with other UE 115 on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UE 115s utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UE 115s communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE 115s without involving base station 105.

[0055] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicle may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. The vehicle may signal information relating to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relating to the V2X system. In some examples, the vehicle in the V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0056] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which can include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function unit (AMF)) managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function unit (UPF)) routing packets to or interconnecting with external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted via user plane entities, which can provide IP address allocation and other functions. The user plane entity can connect to IP services 150 for one or more network service providers. IP services 150 may include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0057] Some network devices (e.g., base station 105) may include sub-elements such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 via one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0058] The wireless communication system 100 can operate using one or more frequency bands (e.g., in the range of 300 MHz to 300 GHz). Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently permeable to penetrate structures for macrocells to provide service to the UE 115 located indoors. Compared to the transmission of smaller frequencies and longer waves using the lower frequencies (HF) or ultra-high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0059] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding device can be even smaller and more closely spaced compared to UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may suffer even greater atmospheric attenuation and shorter distances. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory authority.

[0060] Wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) may employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands may be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0061] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at antenna elements, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with a number of rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Alternatively or additionally, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0062] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals through different spatial layers. This technique can be referred to as spatial multiplexing. For example, a transmitting device can transmit multiple signals through different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals through different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same coded characters) or different data streams (e.g., different coded characters). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0063] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to form or guide an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a specific orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried by the transmitting or receiving device via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0064] As part of beamforming operations, base station 105 or UE 115 may use beam scanning technology. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device (such as base station 105) or by a receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions performed by base station 105.

[0065] Base station 105 may transmit signals (e.g., data signals associated with a specific receiving device, such as UE 115) in a single beam direction (e.g., a direction associated with a particular receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0066] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., base station 105 or UE 115), and the device can use a combination of digital precoding or radio frequency beamforming to generate a combined beam for (e.g., from base station 105 to UE 115) transmissions. UE 115 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured number of beams spanning the system bandwidth or one or more sub-bands. Base station 105 can transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0067] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, the receiving device (e.g., UE 115) may attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device may attempt multiple receiving directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receiving beamforming weights applied to the signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing the received signals according to different sets of receiving beamforming weights applied to the signals received at multiple antenna elements of the antenna array (any of the above operations may be referred to as "listening" according to different receiving configurations or receiving directions). In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiver configuration can be aligned to a beam direction determined based on listening in different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0068] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly for transmission over logical channels. The media access control (MAC) layer may perform prioritization and multiplexing from logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0069] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of data being correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0070] According to one or more embodiments of the present invention, a network node such as UE 115 can receive downlink control information from another network node such as base station 105 based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is connected repeatedly for physical downlink control channels. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. UE 115 can identify that the downlink control information is not scheduled for transmission on the physical downlink shared channel. Alternatively, UE 115 can determine that the second physical downlink control channel candidate spans a time period ending in the second time unit. Then, UE 115 can send a feedback message to base station 105 in response to the downlink control information for a time unit period at least a threshold number of time units after the second physical downlink control channel candidate. In the example where the second physical downlink control channel candidate spans a time period ending in the second time unit, UE 115 can send the feedback message for a time unit period at least a threshold number of time units after the second time unit.

[0071] According to one or more embodiments of the present invention, UE 115 may determine the first physical uplink control channel resource for sending feedback messages. In some examples, UE 115 may receive first downlink control information and may determine the first physical uplink control channel resource indicated by the first downlink control information. In some examples, UE 115 may receive second downlink control information from base station 105 based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected for the physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. Then, UE 115 may determine to overlay the feedback message to be sent in the first physical uplink control channel resource based on determining that the time unit associated with the first physical uplink control channel resource is at least a threshold time unit after the second physical downlink control channel candidate.

[0072] Figure 2 illustrates examples of wireless communication system 200 supporting technologies for downlink control information processing according to various embodiments of the present invention. In some embodiments, wireless communication system 200 may implement various embodiments of wireless communication system 100. For example, wireless communication system 200 may include network nodes, such as base station 205, which may be an example of the corresponding device described with reference to Figure 1 (e.g., base station 105). Wireless communication system 200 may also include network nodes, such as UE 215, which may be an example of the corresponding device described with reference to Figure 1 (e.g., UE 115). For example, wireless communication system 200 may support technologies for processing downlink control information when receiving downlink control information using multiple entity downlink control channel candidates.

[0073] Base station 205 can serve one or more UEs 115, including UE 215, within coverage area 250. Base station 205 can send messages to UE 215 on downlink communication link 225-a. UE 215 can receive messages from base station 205 (e.g., control signal transmission 210 including downlink control information). UE 215 can communicate with base station 205 by sending messages on uplink communication link 225-b. Depending on one or more configurations, wireless communication system 200 can support techniques for determining the timing of feedback transmissions based on the timing of the reception of control signal transmission 210.

[0074] UE 215 can be configured for two or more search space sets. In some examples, base station 205 can configure UE 215 for a search space set. In other examples, UE 215 configures itself for a search space set according to the specification. When configuring the physical downlink control channel, UE 215 can have up to three or five CORESETs in a given BWP for the component carriers of the serving cell. CORESETs can be used to configure the physical downlink control channel. Each CORESET can be associated with an active TCI state. In some examples, the attributes of a CORESET can include the TCI state of the physical downlink control channel, the resource blocks in the frequency domain, and the number of symbols of the CORESET in the time domain. As part of the CORESET configuration, the resource blocks of the CORESET in the frequency domain and the number of symbols of the CORESET (e.g., 1 / 2 / 3 OFDM symbols) can be configured by control signals (e.g., RRC signals).

[0075] Other attributes of CORESET may include the CCE Resource Element Group (REG) appended mapping type, precoding nuances, and scrambling identifier (ID). These parameters can be used for the encoded bits of the demodulation reference signal for the entity's downlink control channel or the downlink control information content. In some examples, the CCE-REG appended mapping type may be the same as the REG appended type used for narrowband channel estimation or wideband precoding throughout the CORESET.

[0076] Once a CORESET is configured, one or more search space sets can also be configured to monitor the physical downlink control channel. In some examples, each search space set may be associated with one CORESET. In some examples, the UE 215 may be configured with up to ten search space sets in a given BWP of component carriers. As part of the configuration of the search space sets, each search space set may be associated with a given identifiable CORESET. The number of symbols may be a time-domain behavior in the CORESET, but which time slots and symbols can be used for the physical downlink control channel may be part of the configuration of the search space sets.

[0077] The search space set can be configured for the timing, period (e.g., number of time slots), and offset of the monitoring of the time domain, entity downlink control channel, to determine which time slots are monitored. The period (represented as ks time slots) and offset (represented as os time slots) can be configured using the parameter monitoringSlotPeriodicityAndOffset, in units of time slots. For example, if the period is five time slots (ks = 5 time slots), then there may be one search space in each period (e.g., at least one time slot in the five time slots in which the search space exists).

[0078] The search space set can also be configured with a parameter duration (denoted as Ts), which can indicate how many time slots the search space set exists in (e.g., Ts < ks). If the parameter duration is two, then in each cycle of five time slots, the search space set exists in two time slots.

[0079] In each slot where the search space set exists, the entity downlink control channel monitoring mode within the slot can be indicated by the parameter MonitoringSymbolsWithinSlot. The entity downlink control channel monitoring mode can be a 14-symbol bitmap, and each 1 in the bitmap (e.g., 010000100000, etc.) can indicate the first symbol of the CORESET used for that monitoring time. If there are three 1s in the bitmap, then there are three monitoring times in the slot, and the position of the 1 indicates the first symbol of the CORESET used for that monitoring time. For example, if we assume that the search space set has three symbols, then for each slot in which the entity downlink control channel of the search space set is monitored, there are three monitoring times.

[0080] The search space set type can be UE-specific or a common search space set type. The search space set configuration can also configure which downlink control information formats the UE 215 should monitor. In some examples, physical downlink control channel candidates can also be configured as part of the search space set configuration. For example, a certain number of physical downlink control channel candidates can be configured for each aggregation level.

[0081] Depending on one or more patterns, UE 215 can identify at least a first monitoring opportunity for a first entity downlink control channel candidate to be monitored in the first search space set and a second monitoring opportunity for a second entity downlink control channel candidate to be monitored in the second search space set, based on the repetition of downlink control information in a first search space set and a second search space set. As illustrated herein, entity downlink control channel candidates can also be configured as part of a search space set configuration. For example, a certain number of entity downlink control channel candidates can be configured for each aggregation level.

[0082] For entity downlink control channel repetitions, each repetition can be an entity downlink control channel candidate. Two entity downlink control channel candidates can be concatenated for possible repetitions of the same downlink control information. The two entity downlink control channel candidates can have the same aggregation level (e.g., the same number of CCEs), and the downlink control information payloads sent by the two entity downlink control channel candidates can be the same. Therefore, UE 215 can use two entity downlink control channel candidates (e.g., two entity downlink control channel repetitions) to perform soft combination to decode downlink control information. In some examples, two entity downlink control channel candidates from different search space sets (e.g., associated with different CORESETs) can be concatenated for entity downlink control channel repetitions.

[0083] For example, UE 215 can use different search space sets configured to be linked together for repetition. For example, a search space set with index 2 can be linked with a search space set with index 4. Each search space set can have different monitoring times (e.g., within a time slot or across time slots). For physical downlink control channel repetition and monitoring times, the monitoring times of the first search space set can be associated with or linked with the monitoring times of the second search space set. To link two physical downlink control channel candidates (which may occur within a first monitoring time of the first search space set and a second monitoring time of the second search space set), one or more of several linking methods can be used. For example, two physical downlink control channel candidates with the same candidate index can be linked across two search space sets. In another example, two physical downlink control channel candidates with the same starting CCE can be linked. In other examples, the link can be explicitly provided as an RRC configuration. The RRC configuration can identify which candidate in the first search space set is linked with which candidate in the second search space set, which can be configured for UE 215. For example, a candidate index in a search space set can be linked to another candidate index in a second search space set. In another example, the link can be configured with RRC between the two search space sets, provided the UE is indicated to have a link. Furthermore, UE 215 can infer the link between two control channel candidates based on the same initial CCE.

[0084] Based on one or more patterns, UE 215 can identify a link between a first search space set and a second search space set for physical downlink control channel repetition. This link can associate one or more monitoring events of each search space set together. As shown herein, UE 215 can know the link before decoding downlink control information. To provide the link, the monitoring events of the search space sets of the two links can be mapped one-to-one. Physical downlink control channel candidates with the same aggregation level and the same candidate index in the search space sets of the two links can be linked. Alternatively, the search space sets of the two links can be configured with the same number of candidates for each aggregation level. UE 215 and base station 205 can support at least one of in-slot physical downlink control channel repetition or inter-slot physical downlink control channel repetition.

[0085] In some examples, isochrones can be defined for uplink and downlink control information (e.g., downlink control information format 0_0, 0_1, or 0_2 for a scheduled entity uplink shared channel). An entity uplink shared channel preparation isochrone (e.g., N2 symbols) can be defined, where N2 is a function of the subcarrier spacing and the UE capability (based on whether the UE supports capability 1 or capability 2). In some cases, the isochrone can begin after the end of reception of the last symbol of the entity downlink control channel carrying the downlink control information for the scheduled entity uplink shared channel. In some examples, when receiving downlink control information for a scheduled entity uplink shared channel or triggering aperiodic channel state information using two entity downlink control channel candidates that are repeatedly linked for the entity downlink control channel, the isochrone can begin from the last symbol of the entity downlink control channel candidate that ends later in time.

[0086] In some wireless communication systems, a reference physical downlink control channel candidate can be defined as the candidate that ends later in time among two linked physical downlink control channel candidates in the time domain. UE 215 can determine the scheduling offset to identify whether UE 215 uses a preset beam for physical downlink shared channel or CSI-RS reception. In some examples, UE 215 can identify the order definition of physical downlink control channel - physical downlink shared channel and physical downlink control channel - physical uplink shared channel. That is, in some examples, the end symbol of the physical downlink control channel can be the last symbol of the reference physical downlink control channel candidate. For any two HARQ procedure IDs in a given scheduling cell, if the UE is scheduled to start receiving a first physical downlink shared channel starting at symbol "j" via a physical downlink control channel ending at symbol "i", it may not be expected to schedule the UE to receive a physical downlink shared channel starting earlier than the end of the first physical downlink shared channel via a physical downlink control channel ending later than symbol "i". Alternatively, for any two HARQ procedure IDs in a given scheduling cell, if the UE is scheduled to begin receiving a first physical uplink shared channel transmission that begins in symbol "j" via a physical downlink control channel that ends in symbol "i", it may not be expected that the UE will be scheduled to send a physical uplink shared channel transmission that begins earlier than the end of the first physical uplink shared channel via a physical downlink control channel that ends later than symbol "i".

[0087] For the entity uplink shared channel preparation time (N2) and channel status information calculation time (Z): the last symbol of the entity downlink control channel can be based on the last symbol of the reference entity downlink control channel candidate. If the entity downlink control channel is repeated between support slots, then for the slot offset used to schedule the same entity downlink shared channel or entity uplink shared channel or CSI-RS or probe reference signal (SRS): the slot of the reference entity downlink control channel candidate can be used as the reference slot. For example, the slot offset of the entity downlink shared channel, entity uplink shared channel, CSI-RS or SRS used for scheduling can be applied to a reference, which can be the slot in which the scheduled downlink control information is detected.

[0088] In some wireless communication systems, isochrones can be defined for the processing of downlink shared channels for downlink control information. However, there may be instances where downlink control information is not scheduled for the processing of downlink shared channels, in which case isochrones for downlink control information processing may not be defined. Specifically, when multiple candidate downlink control channels are used to receive downlink control information, isochrones for downlink control information processing may not be defined.

[0089] In some examples, UE 215 may provide HARQ acknowledgment (HARQ-ACK) feedback information in response to a semi-persistent schedule released from the physical downlink shared channel N symbols after the last symbol of the physical downlink control channel that provides the semi-persistent schedule. If the processingType2Enabled of PDSCH-ServingCellConfig is set to enabled for a serving cell that provides a semi-persistent schedule for the release of the physical downlink shared channel, then for u=0, N=5, for u=1, N=5.5, and for u=2, N=11; otherwise, for u=0, N=10, for u=1, N=12, for u=2, N=22, and for u=3, N=25, where u corresponds to the minimum subcarrier spacing configuration between the subcarrier spacing configuration of the physical downlink control channel that provides the semi-persistent schedule for the release of the physical downlink shared channel and the subcarrier spacing configuration of the physical uplink control channel that carries HARQ-ACK information in response to the semi-persistent schedule for the release of the physical downlink shared channel.

[0090] In some examples, UE 215 may provide HARQ-ACK information in response to the detection of downlink control information format 1_1, which indicates a cocell hibernation after N symbols from the last symbol of the downlink control channel of the entity providing downlink control information format 1_1. If the processingType2Enabled of PDSCH-ServingCellConfig is set to enabled for a serving cell that provides downlink control information format 1_1 for an entity downlink control channel, then for u=0, N=7, for u=1, N=7.5, and for u=2, N=15; otherwise, for u=0, N=14, for u=1, N=16, for u=2, N=27, and for u=3, N=31, where u is the minimum subcarrier spacing configuration between the subcarrier spacing configuration of the entity downlink control channel that provides downlink control information format 1_0, 1_1, or 1_2 and the subcarrier spacing configuration of the entity uplink control channel that responds to the detection of HARQ-ACK information of downlink control information format 1_0, 1_1, or 1_2.

[0091] In some examples, the downlink control information format may provide a request for a type 3 HARQ-ACK codebook report and does not schedule the reception of the entity downlink shared channel. It is expected that UE 215 will provide HARQ-ACK information in response to a request for a type 3 HARQ-ACK codebook N symbols after the last symbol of the entity downlink control channel providing the downlink control information format, where for u=0, 1, 2, the value of N may be the same value defined for releasing the semi-persistent scheduling of the entity downlink shared channel.

[0092] According to one or more of the states described herein, UE 215 may receive downlink control information via control signal transmission 210. UE 215 may use two physical downlink control channel candidates to receive downlink control information. For example, UE 215 may receive downlink control information based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected for a physical downlink control channel. In some examples, the second physical downlink control channel candidate may end later than the first physical downlink control channel candidate. When UE 215 uses two physical downlink control channel candidates to detect the downlink control information format, the downlink control information has a specific format, and no physical downlink shared channel is scheduled, then UE 215 may send feedback 220 in response to the detection of the downlink control information format no earlier than a threshold number of symbols (N symbols) after the physical downlink control channel candidate that ends later in time (e.g., the second physical downlink control channel candidate). For example, UE 215 can identify entities with missing downlink shared channels based on downlink control information. UE 215 can also determine that the downlink control information has a specific format. Then, UE 215 can send feedback 220 in response to the downlink control information for at least a threshold number of time units after being a second entity downlink control channel candidate (or a reference entity downlink control channel candidate or an entity downlink control channel candidate that ends later in time).

[0093] In some wireless communication systems, multiple downlink control messages can point to the same time slot used for feedback transmission. The UE and base station can provide physical uplink control channel resource coverage if the most recent downlink control message is received at least a threshold time period prior to the physical uplink control channel resource indicated by the previous downlink control message. That is, UE 215 can receive both the first and second downlink control messages. In some examples, the second downlink control message can cover the physical uplink control channel resource indicated by the first downlink control message. If the second downlink control message is received at least a threshold time period prior to the physical uplink control channel resource indicated by the first downlink control message, UE 215 can allow coverage. An isochrone can be defined for physical uplink control channel resource coverage to ensure that canceling the current physical uplink control channel resource and using the new physical uplink control channel resource is not too late relative to the current physical uplink control channel resource (i.e., UE 215 has sufficient time to cancel the first physical uplink control channel resource). The pattern described in this paper defines the isochrones for entity uplink control channel coverage when multiple entity downlink control channel candidates are used to receive second downlink control information.

[0094] Depending on one or more of the states described herein, UE 215 may determine the first physical uplink control channel resource to send a feedback message (e.g., in response to the first downlink control information). As shown in FIG2, the first downlink control information may be included in control signaling 210. Alternatively, the first downlink control information may be sent separately from control signaling 210. UE 215 may then receive the second downlink control information based on monitoring at least one of the first physical downlink control channel candidate or the second physical downlink control channel candidate that is repeatedly connected for the physical downlink control channel. In some examples, the second physical downlink control channel candidate may end later than the first physical downlink control channel candidate. Therefore, UE 215 may receive the first downlink control information and may then use both physical downlink control channel candidates to receive the second downlink control information. If two entity downlink control channel candidates that are repeatedly linked for the entity downlink control channel are used to detect the second downlink control information, then if the last symbol of the entity downlink control channel candidate that ends later in time (the second entity downlink control channel candidate) is not earlier than N3 symbols before the first entity uplink control channel resource, then UE 215 may not expect to multiplex HARQ-ACK information corresponding to the second downlink control information format with HARQ-ACK information corresponding to the first downlink control information format in the entity uplink control channel resource in the time slot. That is, UE 215 can cover the first entity uplink control channel resource based on the time unit associated with the first entity uplink control channel resource being at least a threshold number of time units after the second entity downlink control channel candidate.

[0095] Figure 3 illustrates an example of a block diagram 300 supporting technologies for downlink control information processing according to various states of the present invention. Block diagram 300 may implement various states of the wireless communication system 100, or may be implemented by various states of the wireless communication system 100, and other examples. Block diagram 300 illustrates a time slot 305. Although five symbols are shown in the example of Figure 3, it is understood that time slot 305 may include 14 symbols.

[0096] The time slot 305 can be configured to include a first monitoring timing 310 of a first search space set and a second monitoring timing 315 of a second search space set. In the example of FIG3, the first monitoring timing 310 and the second monitoring timing 315 do not overlap. However, it is understood that the first monitoring timing 310 may overlap with the second monitoring timing 315.

[0097] If two search space sets are associated with the same CORESET (e.g., the same resource block, the same scrambling, and the same TCI state), then the first monitoring timing 310 of the first search space set may overlap with the second monitoring timing 315 of the second search space set. In such cases, a first entity downlink control channel candidate may be mapped to the first search space set, and a second entity downlink control channel candidate may be mapped to the second search space set. As illustrated in the example of Figure 3, a network node such as a UE may receive downlink control information based on monitoring at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate that repeats for an entity downlink control channel. The UE may monitor the first entity downlink control channel candidate mapped to the first monitoring timing 310 and the second entity downlink control channel candidate mapped to the second monitoring timing 315. As described herein, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate.

[0098] As illustrated in the example of Figure 3, the first monitoring timing 310 may include downlink control information, and the second monitoring timing 315 may include repetition of downlink control information. The UE may decode at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate, wherein receiving downlink control information is based on this decoding. Alternatively, the UE may soft-combine the signal associated with the first entity downlink control channel candidate and the signal associated with the second entity downlink control channel candidate. The UE may then decode the soft-combined signal, wherein receiving downlink control information is based on this decoding.

[0099] Based on one or more patterns, the UE can identify that the received downlink control information is not scheduled for downlink shared channel transmission by an entity. For example, there may be at least three cases where downlink control information is not scheduled for downlink shared channel transmission by an entity. In such cases, the UE can calculate a time threshold for processing the downlink control information (to define the earliest time when a HARQ-ACK in response to the downlink control information can be sent) starting from the last symbol of the downlink control information.

[0100] When using two entity downlink control channel candidates that are repeatedly linked for an entity downlink control channel to detect the downlink control information format, and the downlink control information format can be 1_0, 1_1, or 1_2 and no entity downlink shared channel is scheduled, the UE may send a HARQ-ACK (e.g., feedback 320) in response to the detection of the downlink control information format no earlier than N symbols after the last symbol of the entity downlink control channel candidate that ends later in time (which can be defined as a reference entity downlink control channel candidate). That is, the UE may send feedback 320 (e.g., feedback message) in response to the downlink control information for at least a threshold number of time units after the second entity downlink control channel candidate.

[0101] In the example of Figure 3, the first entity downlink control channel candidate is mapped to the first monitoring timing 310, and the second entity downlink control channel candidate is mapped to the second monitoring timing 315. The UE can determine that the last symbol of the second entity downlink control channel candidate is symbol 5. In this type of example, the UE can determine to send feedback 320 at least N symbols after symbol 5.

[0102] In some examples, downlink control information sent using a first entity downlink control channel candidate mapped to a first monitoring time 310 and a second entity downlink control channel candidate mapped to a second monitoring time 315 can be associated with: releasing a semi-persistent schedule for an entity downlink shared channel or indicating a cocell dormancy for an unscheduled entity downlink shared channel, or requesting a type 3 or one-time feedback for an unscheduled entity downlink shared channel. For example, the UE can decide to associate downlink control information with releasing a semi-persistent schedule for an entity downlink shared channel. The UE can then calculate the threshold time unit number based on the decision to associate downlink control information with releasing a semi-persistent schedule for an entity downlink shared channel and with an entity downlink shared channel that does not have a schedule. Alternatively, the UE can decide to associate downlink control information with an cocell dormancy for an unscheduled entity downlink shared channel. The UE can then calculate the threshold time unit number based on the decision to associate downlink control information with an cocell dormancy for an unscheduled entity downlink shared channel. In some examples, the UE can determine that downlink control information is associated with a one-time feedback requesting a non-scheduled entity to share the downlink channel. The UE can then calculate the threshold time unit number based on the association between the downlink control information and the one-time feedback requesting a non-scheduled entity to share the downlink channel.

[0103] As shown in the example in Figure 3, the values ​​of the N symbols can be the same values ​​defined for semi-persistent scheduling of releasing the physical downlink shared channel and for one-time feedback requesting an unscheduled physical downlink shared channel. For cocell hibernation of an unscheduled physical downlink shared channel, the values ​​of the N symbols may differ. Alternatively, the values ​​of the N symbols (or the number of threshold time units) can be based on the subcarrier spacing configuration and UE processing capabilities (e.g., whether the UE supports or enables fast isochronism or processing type 2). The isochronism of the N symbols can define the earliest time the UE can send a HARQ-ACK (e.g., feedback 320). It is understood that the HARQ-ACK can be scheduled to be sent after the N symbols. If the HARQ-ACK is scheduled earlier, the UE can consider it an error condition (unexpected by the UE). In some examples, rules for calculating the number of threshold symbols can be applied regardless of whether the UE is detecting downlink control information in one connected physical downlink control channel candidate or in two connected physical downlink control channel candidates (e.g., when the UE performs soft combination of signals).

[0104] Figure 4 illustrates an example of a block diagram 400 supporting various forms of technology for downlink control information processing according to the present invention. Block diagram 400 can implement various forms of the wireless communication system 100, or can be implemented by various forms of the wireless communication system 100, and other examples. Block diagram 400 illustrates time slots 405 and 455. Although in the example of Figure 4, two symbols are illustrated in time slot 455 and five symbols are illustrated in time slot 405, it is understood that each of time slots 405 and 455 may include 14 symbols.

[0105] Time slot 455 may include first downlink control information. The first downlink control information may indicate uplink control channel resources for a first entity. Time slot 405 may include second downlink control information. Although the first and second downlink control information are illustrated to be received in separate time slots, it is understood that the first and second downlink control information may also be received in the same time slot. Specifically, the first downlink control information may be received in a time slot, and the second downlink control information may be received later.

[0106] Time slot 405 may be configured with a first monitoring timing 410 of a first search space set and a second monitoring timing 415 of a second search space set. In the example of FIG4, the first monitoring timing 410 and the second monitoring timing 415 do not overlap. However, it is understood that the first monitoring timing 410 may overlap with the second monitoring timing 415. In some examples, a first entity downlink control channel candidate may be mapped to the first search space set, and a second entity downlink control channel candidate may be mapped to the second search space set. As shown in the example of FIG4, a network node such as a UE may receive second downlink control information based on monitoring at least one first entity downlink control channel candidate or a second entity downlink control channel candidate that repeats for an entity downlink control channel. The UE may monitor the first entity downlink control channel candidate mapped to the first monitoring timing 410 and the second entity downlink control channel candidate mapped to the second monitoring timing 415. As illustrated herein, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate.

[0107] As illustrated in the example of Figure 4, the first monitoring timing 410 may include second downlink control information, and the second monitoring timing 415 may include repetition of the second downlink control information. The UE may decode at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate, wherein receiving downlink control information is based on this decoding. Alternatively, the UE may soft-combine the signal associated with the first physical downlink control channel candidate and the signal associated with the second physical downlink control channel candidate. The UE may then decode the soft-combined signal, wherein receiving downlink control information is based on this decoding.

[0108] In some examples, the UE may decide to overwrite the feedback message to be sent in the first physical uplink control channel resource based on the time unit associated with the first physical uplink control channel resource being at least a threshold time unit number after the second physical downlink control channel candidate. The UE may decide to overwrite the feedback message to be sent in the first physical uplink control channel resource in response to the first and second downlink control information, wherein the feedback (e.g., another feedback message) is multiplexed with the feedback information. In the example of FIG4, the UE may determine that the last symbol of the second physical downlink control channel candidate is symbol 5 of time slot 405. In such examples, the UE may decide to overwrite the feedback message to be sent in the first physical uplink control channel resource 420 based on the time unit associated with the first physical uplink control channel resource 420 being at least a threshold time unit number (e.g., N3 symbols) after the second physical downlink control channel candidate. That is, if the first physical uplink control channel resource 420 is at least N3 symbols after symbol 5, the UE may decide to overwrite the first physical uplink control channel resource 420. Therefore, the isochronous line (or time threshold) defined for physical uplink control channel resource coverage ensures that canceling the current physical uplink control channel resource transmission and replacing it with a new physical uplink control channel resource transmission (based on feedback from the second downlink control information) is not too late compared to the feedback information responding to the first downlink control information. Thus, the UE can utilize the multiplexed feedback information corresponding to the first and second downlink control information to cover the first physical uplink control channel resource.

[0109] As illustrated in the example of Figure 4, if two entity downlink control channel candidates that are repeatedly linked for the entity downlink control channel are used to detect the second downlink control information, then if the last symbol of the entity downlink control channel candidate that ends later in time (e.g., the reference entity downlink control channel candidate) is not earlier than N3 symbols before the first entity uplink control channel resource, the UE may not expect to multiplex HARQ-ACK information corresponding to the second downlink control information format with HARQ-ACK information corresponding to the first downlink control information format in the first entity uplink control channel resource in the time slot. In some examples, the value of N3 symbols (or the number of threshold time units) can be based on the subcarrier spacing configuration and the UE's processing capabilities. For example, the value of N3 symbols (or the number of threshold time units) can be based on whether the UE supports or enables fast isochronous or processing type 2. In some examples, rules for calculating the number of threshold symbols can be applied regardless of whether the UE is in a single entity downlink control channel candidate or in two entities downlink control channel candidates to detect the second entity downlink control information format (e.g., when the UE performs soft combination of signals).

[0110] Figure 5 illustrates an example of a procedure flow 500 supporting downlink control information processing technology according to various forms of the present invention. In some examples, procedure flow 500 may implement various forms of wireless communication system 100 and wireless communication system 200. A first network node such as UE 515 may be an example of UE 115 described with reference to Figures 1 and 2, and a second network node such as base station 505 may be an example of base station 105 described with reference to Figures 1 and 2.

[0111] In the following description of the procedure flow 500, operations between the base station 505 and the UE 515 may be transmitted in an order different from the exemplary order shown. Operations performed by the base station 505 or the UE 515 may be performed in an order different from the exemplary order shown or at different times. Some operations may be omitted from the procedure flow 500, or other operations may be added to the procedure flow 500. Furthermore, the base station 505 and the UE 515 are not limiting, as the described features can be associated with any number of different devices.

[0112] At 520, UE 515 may receive search space set configurations. For example, base station 505 may send configurations for a first search space set and a second search space set. UE 515 may be configured for two or more search space sets. In some examples, base station 505 may configure UE 515 for a search space set. In other examples, UE 515 configures itself for a search space set according to the specification.

[0113] At 525, UE 515 can identify the link between the first search space and the second search space. For example, UE 515 can identify that the first search space set includes downlink control information and the second search space set includes duplicates of downlink control information.

[0114] To link two entity downlink control channel candidates (which may occur during a first monitoring time in a first search space set and a second monitoring time in a second search space set), one or more of several linking methods can be used. For example, two entity downlink control channel candidates with the same candidate index across two search space sets can be linked. In another example, two entity downlink control channels with the same starting CCE can be linked. In other examples, the link can be explicitly provided as an RRC configuration. The RRC configuration can identify which candidate in the first search space set is linked to which candidate in the second search space set, which can be configured for UE 115. For example, a candidate index in the search space set can be linked to another candidate index in the second search space set.

[0115] At 530, UE 515 can identify at least a first monitoring opportunity for a first entity downlink control channel candidate to be monitored in the first search space set and a second monitoring opportunity for a second entity downlink control channel candidate to be monitored in the second search space set, based on the repetition of downlink control information in the first search space set and the second search space set. Then, UE 515 can monitor one or more of the identified monitoring opportunities in at least the first search space set or the second search space set.

[0116] At 535, UE 515 may receive downlink control information based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly linked for a physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. In some examples, UE 515 may receive downlink control information based on one or more monitoring moments identified in at least a first search space set or a second search space set.

[0117] At 540, UE 515 can identify physical downlink shared channels without scheduling based on downlink control information. At 545, UE 515 can calculate the threshold time unit number. In some examples, UE 515 can determine that downlink control information is associated with a semi-persistent schedule for releasing physical downlink shared channels. Then, UE 515 can calculate the threshold time unit number based on the determination that downlink control information is associated with a semi-persistent schedule for releasing physical downlink shared channels and physical downlink shared channels without scheduling.

[0118] Alternatively or concurrently, UE 515 may determine that downlink control information is associated with a secondary cell hibernation of the non-scheduled entity downlink shared channel. In such cases, UE 515 may calculate the threshold time unit number based on the association of downlink control information with the secondary cell hibernation of the non-scheduled entity downlink shared channel. Alternatively or concurrently, UE 515 may determine that downlink control information is associated with a one-time feedback requesting the non-scheduled entity downlink shared channel. In such cases, UE 515 may calculate the threshold time unit number based on the association of downlink control information with the one-time feedback requesting the non-scheduled entity downlink shared channel.

[0119] At 550, UE 515 may send a feedback message to base station 505 in response to downlink control information for at least a threshold number of time units after the second entity downlink control channel candidate. Although not shown in the example of Figure 5, it can be understood that base station 505 may identify the set of resources for feedback transmission for at least a threshold number of time units after the second entity downlink control channel candidate without scheduling an entity downlink shared channel based on the downlink control information.

[0120] Figure 6 illustrates an example of a procedure flow 600 supporting downlink control information processing technology according to various embodiments of the present invention. In some embodiments, procedure flow 600 may implement various embodiments of wireless communication system 100 and wireless communication system 200. A first network node such as UE 615 may be an example of UE 115 described with reference to Figures 1 and 2, and a second network node such as base station 605 may be an example of base station 105 described with reference to Figures 1 and 2.

[0121] In the following description of the procedure flow 600, operations between base station 605 and UE 615 may be transmitted in an order different from the exemplary order shown. Operations performed by base station 605 or UE 615 may be performed in an order different from the exemplary order shown or at different times. Some operations may be omitted from procedure flow 600, or other operations may be added to procedure flow 600. Furthermore, base station 605 and UE 615 are not limiting, as the described features can be associated with any number of different devices.

[0122] At 620, UE 615 can receive search space set configurations. For example, base station 605 can send configurations for a first search space set and a second search space set. UE 615 can be configured for two or more search space sets. In some examples, base station 605 can configure UE 615 for a search space set. In other examples, UE 615 configures itself for a search space set according to the specification.

[0123] At 625, UE 615 can identify the link between the first search space and the second search space. For example, UE 615 can identify that the first search space set includes downlink control information and the second search space set includes duplicates of downlink control information.

[0124] At 630, UE 615 can identify at least a first monitoring opportunity for a first entity downlink control channel candidate to be monitored in the first search space set and a second monitoring opportunity for a second entity downlink control channel candidate to be monitored in the second search space set, based on the repetition of downlink control information in the first search space set and the second search space set. Then, UE 615 can monitor one or more of the identified monitoring opportunities in at least the first search space set or the second search space set.

[0125] At 635, UE 615 may optionally receive first downlink control information. UE 615 may identify a first entity uplink control channel resource for sending feedback messages based on the first downlink control information. In some examples, the first entity uplink control channel resource may be associated with the release of a semi-persistent scheduling entity downlink shared channel.

[0126] At 640, UE 615 may receive second downlink control information based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly linked for a physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. In some examples, UE 615 may receive downlink control information based on one or more monitoring moments identified in at least a first search space set or a second search space set. In some examples, UE 615 may determine that the second physical downlink control channel candidate spans a time period ending in the second time unit.

[0127] At 645, UE 615 may override the feedback message to be sent in the first entity uplink control channel resource based on the determination that the time unit associated with the first entity uplink control channel resource is at least a threshold time unit number after the second entity downlink control channel candidate. In some examples, UE 615 may override the feedback message to be sent in the first entity uplink control channel resource based on the determination that the time unit associated with the first entity uplink control channel resource is scheduled at least a threshold time unit number after the second time unit.

[0128] Figure 7 illustrates a block diagram 700 of a device 705 supporting downlink control information processing technology according to various forms of the present invention. Device 705 may be an example of a UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 may also include a processor. Each of these elements may communicate with each other (e.g., via one or more buses).

[0129] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for downlink control information processing). Information may be transmitted to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0130] Transmitter 715 may provide components for transmitting signals generated by other elements of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with technologies used for downlink control information processing). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0131] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof or various elements thereof may be examples of components for performing various forms of the technology for downlink control information processing described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof or elements thereof may support methods for performing one or more of the functions described herein.

[0132] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, individual gate or transistor logic, individual hardware elements, or any combination thereof, configured to or otherwise support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0133] Alternatively or in some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be implemented using code executed by a processor (e.g., as communication management software or firmware). If implemented using code executed by a processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be performed by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supporting the performance of the functions described herein).

[0134] In some examples, the communication manager 720 may be configured to use the receiver 710, the transmitter 715, or both, or otherwise coordinate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receiving, monitoring, sending). For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to receive information, send information, or perform various other operations as described herein.

[0135] According to the examples disclosed herein, the communication manager 720 may be associated with a first network node and may support wireless communication at the UE. For example, the communication manager 720 may be configured or otherwise supported to receive downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 720 may be configured or otherwise supported to identify physical downlink shared channels that are not scheduled based on downlink control information. The communication manager 720 may be configured or otherwise supported to send a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0136] Alternatively or additionally, according to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured or otherwise supported to support components for determining a first physical uplink control channel resource for sending a feedback message. The communication manager 720 may be configured or otherwise supported to support components for receiving downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to the physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 720 may be configured or otherwise supported to support components for covering the first feedback message to be sent in the first physical uplink control channel resource based on determining that the first physical uplink control channel resource is at least a threshold time unit number after the second physical downlink control channel candidate.

[0137] By including or configuring the communication manager 720 according to the examples described herein, the device 705 (e.g., a processor that controls or otherwise couples to the receiver 710, transmitter 715, communication manager 720, or a combination thereof) can support techniques for reducing processing, lowering power consumption, and utilizing communication resources more efficiently.

[0138] Figure 8 illustrates a block diagram 800 of a device 805 supporting downlink control information processing technology according to various embodiments of the present invention. Device 805 may be an example of a device 705, UE 115, or a first network node as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 may also include a processor. Each of these elements may communicate with each other (e.g., via one or more buses).

[0139] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for downlink control information processing). Information may be transmitted to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0140] Transmitter 815 may provide components for transmitting signals generated by other elements of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with technologies used for downlink control information processing). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0141] Device 805 or its various components may be examples of various types of components used to perform the techniques for downlink control information processing as described herein. For example, communication manager 820 may include control information element 825, entity downlink shared channel identification element 830, feedback element 835, uplink control resource element 840, overlay element 845, or any combination thereof. Communication manager 820 may be examples of various types of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise coordinate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 820 may receive information from receiver 810, send information to transmitter 815, or be integrated with receiver 810, transmitter 815, or both to receive information, send information, or perform various other operations as described herein.

[0142] According to the example disclosed herein, the communication manager 820 may be associated with a first network node and may support wireless communication at the UE. The control information element 825 may be configured or otherwise supported to receive downlink control information from the second network node based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The physical downlink shared channel identification element 830 may be configured or otherwise supported to identify a physical downlink shared channel that is not scheduled based on downlink control information. The feedback element 835 may be configured or otherwise supported to send a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0143] Alternatively or additionally, according to the example disclosed herein, the communication manager 820 may be associated with a first network node and may support wireless communication at the UE. The uplink control resource element 840 may be configured or otherwise supported to support components for determining a first physical uplink control channel resource for sending a feedback message. The control information element 825 may be configured or otherwise supported to support components for receiving downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The overlay element 845 may be configured or otherwise supported to overlay a first feedback message to be sent in the first physical uplink control channel resource based on the first physical uplink control channel resource being at least a threshold time unit number after the second physical downlink control channel candidate.

[0144] Figure 9 illustrates a block diagram 900 of a communication manager 920 supporting technologies for downlink control information processing according to various forms of the present invention. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various forms of technologies for downlink control information processing as described herein. For example, the communication manager 920 may include a control information element 925, an entity downlink shared channel identification element 930, a feedback element 935, an uplink control resource element 940, an overlay element 945, a search space element 950, a threshold element 955, a decoding element 960, a monitoring timing element 965, or any combination thereof. Each of these elements may communicate directly or indirectly with each other (e.g., via one or more buses).

[0145] According to the example disclosed herein, the communication manager 920 can support wireless communication at the UE. The control information element 925 can be configured or otherwise support a component for receiving downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate.

[0146] The physical downlink shared channel identification element 930 may be configured or otherwise supported to support components for identifying physical downlink shared channels that do not have a schedule based on downlink control information. The feedback element 935 may be configured or otherwise supported to send a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0147] In some examples, the feedback element 935 may be configured or otherwise supported for determining the time period spanning the end of the first time unit for the candidate of the second entity downlink control channel, wherein sending the feedback message includes sending the feedback message at least a threshold number of time units after the first time unit.

[0148] In some examples, the search space element 950 may be configured or otherwise supported to support components for receiving a first search space set and a second search space set. In some examples, the search space element 950 may be configured or otherwise supported to support components for identifying duplicates of downlink control information in the first search space set and the second search space set. In some examples, receiving downlink control information is based on the first search space set including downlink control information and the second search space set including duplicates of downlink control information.

[0149] In some examples, the monitoring timing element 965 may be configured or otherwise supported to identify at least a first monitoring timing to be monitored in the first search space set and a second monitoring timing to be monitored in the second search space set for a first entity downlink control channel candidate, based on the repetition of downlink control information in a first search space set and a second search space set including downlink control information. In some examples, the monitoring timing element 965 may be configured or otherwise supported to monitor at least one of the first monitoring timing or the second monitoring timing, wherein receiving downlink control information is based on the monitoring.

[0150] In some examples, the control information element 925 may be configured or otherwise supported to support components for determining the association of downlink control information with a semi-persistent schedule for releasing an entity's downlink shared channel. In some examples, the threshold element 955 may be configured or otherwise supported to support components for calculating a threshold time unit number based on the association of determining the association of downlink control information with a semi-persistent schedule for releasing an entity's downlink shared channel, wherein sending feedback messages includes sending feedback messages for at least the calculated threshold time unit number after the second entity downlink control channel candidate.

[0151] In some examples, the control information element 925 may be configured or otherwise supported to support components for determining the association of downlink control information with the cocell dormancy of the non-scheduled entity downlink shared channel. In some examples, the threshold element 955 may be configured or otherwise supported to support components for calculating a threshold time unit number based on determining the association of downlink control information with the cocell dormancy of the non-scheduled entity downlink shared channel, wherein sending feedback messages includes sending feedback messages at least for the calculated threshold time unit number after the second entity downlink control channel candidate.

[0152] In some examples, the control information element 925 may be configured or otherwise supported to include means for determining the association between downlink control information and a one-time feedback requesting a non-scheduled entity downlink shared channel. In some examples, the threshold element 955 may be configured or otherwise supported to include means for calculating a threshold time unit number based on the association between the determination of downlink control information and a one-time feedback requesting a non-scheduled entity downlink shared channel, wherein sending the feedback message includes sending the feedback message at least for the threshold time unit number calculated after the second entity downlink control channel candidate.

[0153] In some examples, the decoding element 960 may be configured or otherwise support a component for decoding at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate, wherein receiving downlink control information is based on the decoding. In some examples, the time and frequency resource set is at least a threshold time unit number following the second entity downlink control channel candidate.

[0154] In some examples, the decoding element 960 may be configured or otherwise supported to support means for soft combining signals associated with a first entity downlink control channel candidate and signals associated with a second entity downlink control channel candidate. In some examples, the decoding element 960 may be configured or otherwise supported to support means for decoding the softly combined signals, wherein receiving downlink control information is based on the decoding.

[0155] In some examples, the decoding element 960 may be configured or otherwise supported to support means for decoding at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate. In some examples, the feedback element 935 may be configured or otherwise supported to support means for identifying a set of time and frequency resources for transmitting a feedback message based on the decoding, wherein the time and frequency resource sets are scheduled at least a threshold time unit number after the second entity downlink control channel candidate.

[0156] In some examples, sending feedback messages includes sending feedback messages during the identified set of time and frequency resources. In some examples, the threshold time unit number is based on the subcarrier spacing configuration and processing capacity.

[0157] Alternatively or additionally, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The uplink control resource element 940 may be configured or otherwise supported to support components for determining a first physical uplink control channel resource for sending feedback messages. In some examples, the control information element 925 may be configured or otherwise supported to support components for receiving downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate.

[0158] The overlay element 945 may be configured or otherwise supported to overlay the first feedback message to be sent in the first entity uplink control channel resource based on the determination that the first entity uplink control channel resource is at least a threshold time unit number after the second entity downlink control channel candidate.

[0159] In some examples, the overlay element 945 may be configured or otherwise support a component for determining the time period that the candidate for the second entity downlink control channel spans the end of the first time unit, wherein the overlay of the feedback message to be sent in the first entity uplink control channel resource includes: overlaying the first feedback message to be sent in the first entity uplink control channel resource based on the determination that the time unit associated with the first entity uplink control channel resource is scheduled at least a threshold number of time units after the first time unit.

[0160] In some examples, the control information element 925 may be configured or otherwise supported to determine a second physical uplink control channel resource for transmission of a physical uplink control channel with a second feedback message. In some examples, the feedback element 935 may be configured or otherwise supported to use the second physical uplink control channel resource to send a first feedback message and a second feedback message based on at least a threshold time unit number after the first physical uplink control channel resource is a candidate for the second physical downlink control channel.

[0161] In some examples, the search space element 950 may be configured or otherwise supported to include components for receiving a configuration of a first search space set and a second search space set. In some examples, the search space element 950 may be configured or otherwise supported to include components for identifying duplicates of downlink control information in the first search space set and the second search space set, wherein receiving the downlink control information is based on the first search space set including downlink control information and the second search space set including duplicates of downlink control information.

[0162] In some examples, the monitoring timing element 965 may be configured or otherwise supported to identify at least a first monitoring timing to be monitored in the first search space set and a second monitoring timing to be monitored in the second search space set for a first entity downlink control channel candidate, based on the repetition of downlink control information in a first search space set and a second search space set including downlink control information. In some examples, the monitoring timing element 965 may be configured or otherwise supported to monitor at least one of the first monitoring timing or the second monitoring timing, wherein receiving downlink control information is based on the monitoring.

[0163] In some examples, the decoding element 960 may be configured or otherwise support a component for decoding at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate, wherein receiving downlink control information is based on the decoding.

[0164] In some examples, the decoding element 960 may be configured or otherwise supported to support means for soft combining signals associated with a first entity downlink control channel candidate and signals associated with a second entity downlink control channel candidate. In some examples, the decoding element 960 may be configured or otherwise supported to support means for decoding the softly combined signals, wherein receiving downlink control information is based on the decoding.

[0165] In some examples, the control information element 925 may be configured or otherwise support a component for receiving second downlink control information from the base station that indicates uplink control channel resources of the first entity, wherein the downlink control information is received after the second downlink control information is received.

[0166] In some examples, the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of the semi-persistent scheduling entity. In some examples, the threshold time unit number is based on the subcarrier spacing configuration and processing capacity.

[0167] Figure 10 illustrates a system 1000 including a device 1005 supporting technology for downlink control information processing, according to various embodiments of the present invention. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include elements thereof. Device 1005 may wirelessly communicate with one or more base stations 105, UE 105, or any combination thereof. Device 1005 may include elements for bidirectional voice and data communication, including elements for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These elements may be electronically communicated or otherwise coupled via one or more buses (e.g., bus 1045) or otherwise (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0168] The I / O controller 1010 can manage input and output signals for the device 1005. The I / O controller 1010 can also manage peripheral devices not integrated into the device 1005. In some cases, the I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1010 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Alternatively or concurrently, the I / O controller 1010 can represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 can be implemented as part of a processor (such as processor 1040). In some cases, a user can interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0169] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which are capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired or wireless links as described herein. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1025 for transmission, and demodulating packets received from one or more antennas 1025. Transceiver 1015 or transceiver 1015 and one or more antennas 1025 may be examples of transmitter 715, transmitter 815, receiver 710, receiver 810 or any combination thereof or elements thereof as described herein.

[0170] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035, which includes instructions that, when executed by processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium (such as system memory or other types of memory). In some cases, code 1035 may not be directly executable by processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition, memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0171] Processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, individual gate or transistor logic elements, individual hardware elements, or any combination thereof). In some cases, processor 1040 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting techniques for downlink control information processing). For example, device 1005 or elements thereof may include processor 1040 and memory 1030 coupled to processor 1040, processor 1040 and memory 1030 being configured to perform the various functions described herein.

[0172] According to the example disclosed herein, the communication manager 1020 may be associated with a first network node and may support wireless communication at the UE. For example, the communication manager 1020 may be configured or otherwise supported to receive downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1020 may be configured or otherwise supported to identify physical downlink shared channels that are not scheduled based on downlink control information. The communication manager 1020 may be configured or otherwise supported to send a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0173] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. For example, the communication manager 1020 may be configured or otherwise supported to support components for determining a first physical uplink control channel resource for sending a feedback message. The communication manager 1020 may be configured or otherwise supported to support components for receiving downlink control information from the base station based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to the physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1020 may be configured or otherwise supported to support components for covering the first feedback message to be sent in the first physical uplink control channel resource based on determining that the first physical uplink control channel resource is at least a threshold time unit number after the second physical downlink control channel candidate.

[0174] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 can support technologies for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, longer battery life, and improving the utilization of processing power.

[0175] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or in coordination with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is shown as a separate element, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by the processor 1040 to cause the device 1005 to perform various forms of techniques for downlink control information processing as described herein, or the processor 1040 and memory 1030 may be otherwise configured to perform or support such operations.

[0176] Figure 11 illustrates a block diagram 1100 of a device 1105 supporting downlink control information processing technology according to various embodiments of the present invention. Device 1105 may be an example of a base station 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0177] Receiver 1110 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for downlink control information processing). Information may be transmitted to other components of device 1105. Receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0178] Transmitter 1115 may provide components for transmitting signals generated by other elements of device 1105. For example, transmitter 1115 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with technologies used for downlink control information processing). In some examples, transmitter 1115 may be co-located with receiver 1110 in a transceiver module. Transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0179] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof or various elements thereof may be examples of components for performing various forms of the techniques for downlink control information processing described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof or elements thereof may support methods for performing one or more of the functions described herein.

[0180] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, ASICs, FPGAs, or other programmable logic devices, individual gate or transistor logic, individual hardware elements, or any combination thereof configured to or otherwise support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0181] Alternatively or in some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be implemented using code executed by a processor (e.g., as communication management software or firmware). If implemented using code executed by a processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functions described herein).

[0182] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or integrate with the receiver 1110, transmitter 1115, or both to receive information, send information, or perform various other operations as described herein.

[0183] According to the example disclosed herein, the communication manager 1120 may be associated with a first network node and may support wireless communication at a base station. For example, the communication manager 1120 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1120 may be configured or otherwise support components for identifying a set of resources for feedback transmission during a time unit period of at least a threshold time unit number after the second physical downlink control channel candidate, without scheduling a physical downlink shared channel based on downlink control information. The communication manager 1120 may be configured or otherwise support components for receiving feedback messages from the UE in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0184] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at the base station. For example, the communication manager 1120 may be configured or otherwise support components for scheduling a first physical uplink control channel resource for the UE to send a first feedback message. The communication manager 1120 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1120 may be configured or otherwise support components for determining whether the first physical uplink control channel resource is within a time unit period of at least a threshold time unit number after the second physical downlink control channel candidate. The communication manager 1120 may be configured or otherwise support components for determining which feedback message to cover based on the determination time unit of at least a threshold time unit number after the second physical downlink control channel candidate.

[0185] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor that controls or is otherwise coupled to the receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and utilizing communication resources more efficiently.

[0186] Figure 12 illustrates a block diagram 1200 of a device 1205 supporting downlink control information processing technology according to various embodiments of the present invention. Device 1205 may be an example of a device 1105 or a base station 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] Receiver 1210 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for downlink control information processing). Information may be transmitted to other components of device 1205. Receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0188] Transmitter 1215 may provide components for transmitting signals generated by other elements of device 1205. For example, transmitter 1215 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with technologies used for downlink control information processing). In some examples, transmitter 1215 may be co-located with receiver 1210 in a transceiver module. Transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0189] Device 1205 or its various components may be examples of various types of components used to perform the techniques for downlink control information processing as described herein. For example, communication manager 1220 may include control information element 1225, resource scheduling element 1230, feedback element 1235, uplink control resource element 1240, coverage determination element 1245, or any combination thereof. Communication manager 1220 may be examples of various types of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use receiver 1210, transmitter 1215, or both, or otherwise coordinate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 1220 may receive information from receiver 1210, send information to transmitter 1215, or be combined and integrated with receiver 1210, transmitter 1215, or both to receive information, send information, or perform various other operations as described herein.

[0190] According to the example disclosed herein, the communication manager 1220 may be associated with a first network node and may support wireless communication at a base station. The control information element 1225 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate.

[0191] Resource scheduling element 1230 may be configured or otherwise supported for identifying a set of resources for feedback transmission during a time period of at least a threshold time unit after the second entity downlink control channel candidate, without scheduling an entity downlink shared channel based on downlink control information. Feedback element 1235 may be configured or otherwise supported for receiving feedback messages from the UE in response to downlink control information, at least a threshold time unit after the second entity downlink control channel candidate.

[0192] Alternatively or additionally, according to the example disclosed herein, the communication manager 1220 may support wireless communication at the base station. The uplink control resource element 1240 may be configured or otherwise support components for scheduling a first physical uplink control channel resource for the UE to send a first feedback message. The control information element 1225 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate.

[0193] Resource scheduling element 1230 may be configured or otherwise supported for determining whether the first entity uplink control channel resource is available for at least a threshold number of time units after the second entity downlink control channel candidate. Coverage determination element 1245 may be configured or otherwise supported for determining the components to cover feedback messages based on the determination time units at least a threshold number of time units after the second entity downlink control channel candidate.

[0194] Figure 13 illustrates a block diagram 1300 of a communication manager 1320 supporting various forms of downlink control information processing according to the present invention. The communication manager 1320 may be an example of a communication manager 1120, communication manager 1220, or both as described herein. The communication manager 1320 or its various elements may be examples of components for performing various forms of downlink control information processing as described herein. For example, the communication manager 1320 may include a control information element 1325, a resource scheduling element 1330, a feedback element 1335, an uplink control resource element 1340, a coverage determination element 1345, a search space element 1350, a threshold element 1355, a monitoring timing element 1360, or any combination thereof. Each of these elements may communicate directly or indirectly with each other (e.g., via one or more buses).

[0195] According to the example disclosed herein, the communication manager 1320 may be associated with a first network node and may support wireless communication at a base station. The control information element 1325 may be configured or otherwise supported to send downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The resource scheduling element 1330 may be configured or otherwise supported to identify a set of resources for feedback transmission during a time period of at least a threshold time unit after the second physical downlink control channel candidate, without scheduling a physical downlink shared channel based on the downlink control information. The feedback element 1335 may be configured or otherwise supported to receive a feedback message from the UE in response to downlink control information at least a threshold time unit after the second physical downlink control channel candidate.

[0196] In some examples, resource scheduling element 1330 may be configured or otherwise supported for determining the time period spanning the end of the first time unit for candidates of the second entity downlink control channel, wherein receiving feedback messages includes receiving feedback messages at least a threshold number of time units after the first time unit.

[0197] In some examples, the search space element 1350 may be configured or otherwise supported to support components for transmitting a first search space set and a second search space set. In some examples, the search space element 1350 may be configured or otherwise supported to support components for identifying duplicates of downlink control information in the first search space set and the second search space set, wherein transmitting the downlink control information is based on the first search space set including downlink control information and the second search space set including duplicates of downlink control information.

[0198] In some examples, the monitoring timing element 1360 may be configured or otherwise supported to identify at least a first monitoring timing for monitoring a first entity downlink control channel candidate in the first search space set and a second monitoring timing for monitoring a second entity downlink control channel candidate in the second search space set, based on the repetition of a first search space set including downlink control information and a second search space set including downlink control information.

[0199] In some examples, the control information element 1325 may be configured or otherwise supported to include means for determining the association of downlink control information with a semi-persistent schedule for releasing an entity downlink shared channel. In some examples, the threshold element 1355 may be configured or otherwise supported to include means for calculating a threshold time unit number based on the association of determining the association of downlink control information with a semi-persistent schedule for releasing an entity downlink shared channel, wherein receiving feedback messages includes receiving feedback messages for at least a threshold time unit number calculated after the second entity downlink control channel candidate.

[0200] In some examples, the control information element 1325 may be configured or otherwise supported to support components for determining the association of downlink control information with the cocell dormancy of a non-scheduled entity downlink shared channel. In some examples, the threshold element 1355 may be configured or otherwise supported to support components for calculating a threshold time unit number based on determining the association of downlink control information with the cocell dormancy of a non-scheduled entity downlink shared channel, wherein receiving feedback messages includes receiving feedback messages for at least the threshold time unit number calculated after the second entity downlink control channel candidate.

[0201] In some examples, control information element 1325 may be configured or otherwise supported to include components for determining the association between downlink control information and a one-time feedback requesting a non-scheduled entity's downlink shared channel. In some examples, threshold element 1355 may be configured or otherwise supported to include components for calculating the number of threshold time units based on the association between the determination of downlink control information and a one-time feedback requesting a non-scheduled entity's downlink shared channel.

[0202] In some examples, receiving feedback messages includes receiving feedback messages for at least a calculated number of threshold time units after the second entity downlink control channel candidate. In some examples, the number of threshold time units is based on the subcarrier spacing configuration and processing capacity.

[0203] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1320 may support wireless communication at the base station. The uplink control resource element 1340 may be configured or otherwise supported to support components for scheduling a first physical uplink control channel resource for the UE to send a first feedback message. In some examples, the control information element 1325 may be configured or otherwise supported to support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. In some examples, the resource scheduling element 1330 may be configured or otherwise supported to support components for determining whether the first physical uplink control channel resource is available for at least a threshold time unit period after the second physical downlink control channel candidate. The coverage determination element 1345 may be configured or otherwise supported to support components for determining which feedback message to cover based on the determination time unit at least a threshold time unit period after the second physical downlink control channel candidate.

[0204] In some examples, the coverage determination element 1345 may be configured or otherwise support a component for determining the time period that the candidate downlink control channel for the second entity spans across the end of the first time unit, wherein determining that the first entity uplink control channel resource is covered includes: determining that the first entity uplink control channel resource is covered based on the time unit associated with the first entity uplink control channel resource being scheduled at least a threshold number of time units after the first time unit.

[0205] In some examples, the control information element 1325 may be configured or otherwise supported to include means for determining downlink control information indications for a second physical uplink control channel resource for transmission of a physical uplink control channel with a second feedback message. In some examples, the feedback element 1335 may be configured or otherwise supported to include means for using the second physical uplink control channel resource to receive the feedback message and the second feedback message based on the time unit associated with the first physical uplink control channel resource being at least a threshold time unit number after the second physical downlink control channel candidate.

[0206] In some examples, the search space element 1350 may be configured or otherwise support components for transmitting a first search space set and a second search space set. In some examples, the search space element 1350 may be configured or otherwise support components for identifying duplicates of downlink control information in the first search space set and the second search space set, wherein transmitting the downlink control information is based on the first search space set including downlink control information and the second search space set including duplicates of downlink control information.

[0207] In some examples, the monitoring timing element 1360 may be configured or otherwise supported to identify at least a first monitoring timing for monitoring a first entity downlink control channel candidate in the first search space set and a second monitoring timing for monitoring a second entity downlink control channel candidate in the second search space set, based on the repetition of a first search space set including downlink control information and a second search space set including downlink control information.

[0208] In some examples, the control information element 1325 may be configured or otherwise support a component for sending second downlink control information to the UE, indicating uplink control channel resources of a first entity, wherein the downlink control information is sent after the second downlink control information is sent.

[0209] In some examples, the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of the semi-persistent scheduling entity. In some examples, the threshold time unit number is based on the subcarrier spacing configuration and processing capacity.

[0210] Figure 14 illustrates a system 1400 including a device 1405 supporting technology for downlink control information processing, according to various embodiments of the present invention. Device 1405 may be an example of device 1105, device 1205, or base station 105 as described herein, or may include elements thereof. Device 1405 may wirelessly communicate with one or more base stations 105, UE 145, or any combination thereof. Device 1405 may include elements for bidirectional voice and data communication, including elements for transmitting and receiving communications, such as a communication manager 1420, a network communication manager 1410, a transceiver 1415, an antenna 1425, a memory 1430, a code 1435, a processor 1440, and an inter-station communication manager 1445. These elements may be electronically communicated via one or more buses (e.g., bus 1450) or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0211] The network communication manager 1410 can manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1410 can manage the transmission of data communications to client devices (e.g., one or more UEs 115).

[0212] In some cases, device 1405 may include a single antenna 1425. However, in other cases, device 1405 may have more than one antenna 1425, which are capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1415 may communicate bidirectionally via one or more antennas 1425, wired or wireless links as described herein. For example, transceiver 1415 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1415 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1425 for transmission, and demodulating packets received from one or more antennas 1425. Transceiver 1415, or transceiver 1415 and one or more antennas 1425, may be an example of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or elements thereof as described herein.

[0213] Memory 1430 may include RAM and ROM. Memory 1430 may store computer-readable, computer-executable code 1435, which includes instructions that, when executed by processor 1440, cause device 1405 to perform the various functions described herein. Code 1435 may be stored in a non-transitory computer-readable medium (such as system memory or other types of memory). In some cases, code 1435 may not be directly executable by processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition, memory 1430 may also include a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0214] Processor 1440 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, individual gate or transistor logic elements, individual hardware elements, or any combination thereof). In some cases, processor 1440 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks supporting techniques for downlink control information processing). For example, device 1405 or elements thereof may include processor 1440 and memory 1430 coupled to processor 1440, processor 1440 and memory 1430 being configured to perform the various functions described herein.

[0215] The inter-site communication manager 1445 can manage communication with other base stations 105 and may include a controller or scheduler for coordinating communication with the UE 115 with other base stations 105. For example, the inter-site communication manager 1445 can coordinate the scheduling of transmissions to the UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1445 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0216] According to the example disclosed herein, the communication manager 1420 may be associated with a first network node and may support wireless communication at a base station. For example, the communication manager 1420 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1420 may be configured or otherwise support components for identifying a set of resources for feedback transmission during a time unit period of at least a threshold time unit number after the second physical downlink control channel candidate, without scheduling a physical downlink shared channel based on downlink control information. The communication manager 1420 may be configured or otherwise support components for receiving feedback messages from the UE in response to downlink control information at least a threshold time unit number after the second physical downlink control channel candidate.

[0217] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1420 may support wireless communication at the base station. For example, the communication manager 1420 may be configured or otherwise support components for scheduling a first physical uplink control channel resource for the UE to send a first feedback message. The communication manager 1420 may be configured or otherwise support components for sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The communication manager 1420 may be configured or otherwise support components for determining whether the first physical uplink control channel resource is available for at least a threshold number of time units after the second physical downlink control channel candidate. The communication manager 1420 may be configured or otherwise support components for determining which feedback message to cover based on the determination time unit being at least a threshold number of time units after the second physical downlink control channel candidate.

[0218] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, longer battery life, and improving the utilization of processing power.

[0219] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, monitor, transmit) using or in coordination with the transceiver 1415, one or more antennas 1425, or any combination thereof. Although the communication manager 1420 is shown as a separate element, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1440, memory 1430, code 1435, or any combination thereof. For example, code 1435 may include instructions that can be executed by the processor 1440 to cause the device 1405 to perform various forms of techniques for downlink control information processing as described herein, or the processor 1440 and memory 1430 may be otherwise configured to perform or support such operations.

[0220] Figure 15 illustrates a flowchart of a method 1500 supporting downlink control information processing techniques according to various forms of the present invention. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by a UE 115 as described with reference to Figures 1 to 10. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively, the UE can use dedicated hardware to perform various forms of the described functions.

[0221] At 1505, the method may include receiving downlink control information from the second network node based on monitoring at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly connected for the entity downlink control channel. In some examples, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 1505 may be performed by the control information element 925 as described with reference to 9.

[0222] At 1510, the method may include: identifying an entity downlink shared channel that is not scheduled based on downlink control information. The operation at 1510 may be performed according to examples disclosed herein. In some examples, various forms of the operation at 1510 may be performed by an entity downlink shared channel identification element 930 as described with reference to 9.

[0223] At 1515, the method may include: sending a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second entity downlink control channel candidate. The operation of 1515 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1515 may be performed by a feedback element 935 as described with reference to 9.

[0224] Figure 16 illustrates a flowchart of a method 1600 supporting downlink control information processing techniques according to various forms of the present invention. The operation of method 1600 can be implemented by a UE or its components as described herein; for example, the operation of method 1600 can be performed by a UE 115 as described with reference to Figures 1 to 10. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively, the UE can use dedicated hardware to perform various forms of the described functions.

[0225] At 1605, the method may include receiving a configuration of a first search space set and a second search space set. The operation of 1605 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1605 may be performed by a search space element 950 as described with reference to 9.

[0226] At 1610, the method may include: identifying a first search space set including downlink control information and a second search space set including repetitions of downlink control information. The operation of 1610 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1610 may be performed by a search space element 950 as described with reference to 9.

[0227] At 1615, the method may include: identifying at least a first monitoring opportunity for monitoring downlink control channel candidates of a first entity in a first search space set and a second monitoring opportunity for monitoring downlink control channel candidates of a second entity in a second search space set. In some examples, the first and second monitoring opportunities may be identified based on the repetition of downlink control information in the first search space set and the second search space set. The operation of 1615 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1615 may be performed by a monitoring opportunity element 965 as described with reference to 9.

[0228] At 1620, the method may include: monitoring at least one of a first monitoring timing or a second monitoring timing. Operation 1620 may be performed according to examples disclosed herein. In some examples, various forms of operation of 1620 may be performed by a monitoring timing element 965 as described with reference to 9.

[0229] At 1625, the method may include: receiving downlink control information from the second network node based on monitoring at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly connected for entity downlink control channels. In some examples, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate.

[0230] In some examples, receiving downlink control information is based on a first search space set including downlink control information and a second search space set including repetitions of downlink control information. In some examples, receiving downlink control information is based on monitoring at least one of a first monitoring timing or a second monitoring timing. The operation of 1625 can be performed according to the examples disclosed herein. In some examples, various forms of operation of 1625 can be performed by control information element 925 as described with reference to 9.

[0231] At 1630, the method may include: identifying an entity downlink shared channel that is not scheduled based on downlink control information. The operation at 1630 may be performed according to examples disclosed herein. In some examples, various forms of the operation at 1630 may be performed by an entity downlink shared channel identification element 930 as described with reference to 9.

[0232] At 1635, the method may include: sending a feedback message to the base station in response to downlink control information at least a threshold time unit number after the second entity downlink control channel candidate. The operation of 1635 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1635 may be performed by a feedback element 935 as described with reference to 9.

[0233] Figure 17 illustrates a flowchart of a method 1700 supporting downlink control information processing technology according to various forms of the present invention. The operation of method 1700 can be implemented by a UE or its components as described herein; for example, the operation of method 1700 can be performed by a UE 115 as described with reference to Figures 1 to 10. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively or concurrently, the UE can use dedicated hardware to perform various forms of the described functions.

[0234] At 1705, the method may include: determining a first entity uplink control channel resource for sending a feedback message. The operation at 1705 may be performed according to examples disclosed herein. In some examples, the operation at 1705 may be performed by an uplink control resource element 940 as described with reference to 9.

[0235] At 1710, the method may include receiving downlink control information from the second network node based on monitoring at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly connected for entity downlink control channels. In some examples, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, various forms of the operation of 1710 may be performed by control information element 925 as described with reference to 9.

[0236] At 1715, the method may include: overriding a first feedback message to be sent in the first entity uplink control channel resource based on the determination that the first entity uplink control channel resource is at least a threshold time unit number after the second entity downlink control channel candidate. The operation of 1715 can be performed according to examples as disclosed herein. In some examples, various forms of the operation of 1715 may be performed by an overriding element 945 as described with reference to 9.

[0237] Figure 18 illustrates a flowchart of a method 1800 supporting downlink control information processing techniques according to various forms of the present invention. Operation of method 1800 can be implemented by a UE or its components as described herein; for example, operation of method 1800 can be performed by a UE 115 as described with reference to Figures 1 to 10. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described functions. Alternatively, the UE can use dedicated hardware to perform various forms of the described functions.

[0238] At 1805, the method may include: determining a first entity uplink control channel resource for sending a feedback message. The operation at 1805 may be performed according to examples disclosed herein. In some examples, the operation at 1805 may be performed by an uplink control resource element 940 as described with reference to 9.

[0239] At 1810, the method may include receiving downlink control information from the second network node based on monitoring at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly connected for the entity downlink control channel. In some examples, the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate. The operation of 1810 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 1810 may be performed by the control information element 925 as described with reference to 9.

[0240] At 1815, the method may include: determining downlink control information indicating a second physical uplink control channel resource for transmission of physical uplink control channel with a second feedback message. The operation of 1815 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1815 may be performed by control information element 925 as described with reference to 9.

[0241] At 1820, the method may include: overriding a first feedback message to be sent in the first entity uplink control channel resource based on the determination that the first entity uplink control channel resource is at least a threshold time unit number after the second entity downlink control channel candidate. The operation at 1820 may be performed according to examples disclosed herein. In some examples, various forms of the operation at 1820 may be performed by an overriding element 945 as described with reference to 9.

[0242] At 1825, the method may include: based on the determination that the time unit associated with the first entity uplink control channel resource is at least a threshold time unit number after the second entity downlink control channel candidate, using the second entity uplink control channel resource to send a first feedback message and a second feedback message. The operation at 1825 may be performed according to examples as disclosed herein. In some examples, various forms of the operation at 1825 may be performed by a feedback element 935 as described with reference to 9.

[0243] Figure 19 illustrates a flowchart of a method 1900 supporting downlink control information processing techniques according to various aspects of the present invention. Operation of method 1900 can be implemented by a base station or its components as described herein; for example, operation of method 1900 can be performed by a base station 105 as described with reference to Figures 1 to 6 and 11 to 14. In some examples, the base station can execute an instruction set to control the functional units of the base station to perform the described functions. Alternatively or concurrently, the base station can use dedicated hardware to perform various aspects of the described functions.

[0244] At 1905, the method may include: sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The operation at 1905 may be performed according to examples as disclosed herein. In some examples, various forms of the operation at 1905 may be performed by control information element 1325 as described with reference to 13.

[0245] At 1910, the method may include: identifying a set of resources for feedback transmission during a time unit period of at least a threshold time unit number following the candidate of the second entity downlink control channel, without scheduling an entity downlink shared channel based on downlink control information. The operation at 1910 may be performed according to examples as disclosed herein. In some examples, various forms of the operation at 1910 may be performed by resource scheduling element 1330 as described with reference to 13.

[0246] At 1915, the method may include: receiving a feedback message from the UE in response to downlink control information using the identified set of resources. The operation of 1915 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 1915 may be performed by a feedback element 1335 as described with reference to 13.

[0247] Figure 20 illustrates a flowchart of a method 2000 supporting downlink control information processing techniques according to various aspects of the present invention. Operation of method 2000 can be implemented by a base station or its components as described herein; for example, operation of method 2000 can be performed by a base station 105 as described with reference to Figures 1 to 6 and 11 to 14. In some examples, the base station can execute an instruction set to control the functional units of the base station to perform the described functions. Alternatively or concurrently, the base station can use dedicated hardware to perform various aspects of the described functions.

[0248] At 2005, the method may include: sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The operation of 2005 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 2005 may be performed by control information element 1325 as described with reference to 13.

[0249] At 2010, the method may include: determining the time period during which the candidate downlink control channel for the second entity ends in the first time unit. The operation at 2010 may be performed according to examples as disclosed herein. In some examples, the various forms of the operation at 2010 may be performed by resource scheduling element 1330 as described with reference to 13.

[0250] At 2015, the method may include: identifying a set of resources for feedback transmission during a time unit period of at least a threshold time unit number following the candidate of the second entity downlink control channel, without scheduling an entity downlink shared channel based on downlink control information. Operation 2015 may be performed according to examples disclosed herein. In some examples, various forms of operation 2015 may be performed by resource scheduling element 1330 as described with reference to 13.

[0251] At 2020, the method may include: using the identified set of resources, in response to downlink control information, to receive a feedback message from the UE. In some examples, receiving the feedback message includes: receiving the feedback message at least a threshold time unit number after a first time unit. The operation of 2020 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 2020 may be performed by a feedback element 1335 as described with reference to 13.

[0252] Figure 21 illustrates a flowchart of a method 2100 supporting downlink control information processing technology according to various aspects of the present invention. Operation of method 2100 can be implemented by a base station or its components as described herein; for example, operation of method 2100 can be performed by a base station 105 as described with reference to Figures 1 to 6 and 11 to 14. In some examples, the base station can execute an instruction set to control the functional units of the base station to perform the described functions. Alternatively or concurrently, the base station can use dedicated hardware to perform various aspects of the described functions.

[0253] At 2105, the method may include: determining a first entity uplink control channel resource for sending a feedback message. The operation of 2105 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2105 may be performed by an uplink control resource element 1340 as described with reference to 13.

[0254] At 2110, the method may include: sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. The operation of 2110 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 2110 may be performed by the control information element 1325 as described with reference to 13.

[0255] At 2115, the method may include: determining whether the first entity uplink control channel resource is available for at least a threshold number of time units after the second entity downlink control channel candidate. The operation of 2115 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2115 may be performed by resource scheduling element 1330 as described with reference to 13.

[0256] At 2120, the method may include: determining to cover the feedback message based on the number of time units at least a threshold time unit after the second entity downlink control channel candidate. The operation of 2120 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2120 may be performed by the coverage determination element 1345 as described with reference to 13.

[0257] Figure 22 illustrates a flowchart of a method 2200 supporting downlink control information processing technology according to various aspects of the present invention. Operation of method 2200 can be implemented by a base station or its components as described herein; for example, operation of method 2200 can be performed by a base station 105 as described with reference to Figures 1 to 6 and 11 to 14. In some examples, the base station can execute an instruction set to control the functional units of the base station to perform the described functions. Alternatively or concurrently, the base station can use dedicated hardware to perform various aspects of the described functions.

[0258] At 2205, the method may include: sending second downlink control information to the UE indicating uplink control channel resources of the first entity. The operation of 2205 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2205 may be performed by control information element 1325 as described with reference to 13.

[0259] At 2210, the method may include: determining a first entity uplink control channel resource for sending a feedback message. The operation of 2210 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2210 may be performed by an uplink control resource element 1340 as described with reference to 13.

[0260] At 2215, the method may include: sending downlink control information to the UE using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel. In some examples, the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate. In some examples, the downlink control information is sent later than the second downlink control information. The operation of 2215 may be performed according to the examples disclosed herein. In some examples, various forms of the operation of 2215 may be performed by the control information element 1325 as described with reference to 13.

[0261] At 2220, the method may include: determining whether the first entity uplink control channel resource is available for at least a threshold number of time units after the second entity downlink control channel candidate. The operation of 2220 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2220 may be performed by resource scheduling element 1330 as described with reference to 13.

[0262] At 2225, the method may include: determining to cover the feedback message based on the number of time units at least a threshold time unit after the second entity downlink control channel candidate. The operation of 2225 may be performed according to examples disclosed herein. In some examples, various forms of the operation of 2225 may be performed by the coverage determination element 1345 as described with reference to 13.

[0263] The following provides a summary of the various aspects of the content of this case:

[0264] State 1: A method for wireless communication at a first network node, comprising: receiving downlink control information from a second network node based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; and sending a feedback message to the second network node in response to the downlink control information at least a threshold time unit after the second physical downlink control channel candidate.

[0265] State 2: The method according to State 1 further includes: identifying the downlink control information non-scheduled entity downlink shared channel transmission.

[0266] State 3: The method according to States 1 to 2 further includes: determining the time period that the candidate downlink control channel of the second entity will span in the first time unit, wherein sending the feedback message includes: sending the feedback message at least the threshold time unit number after the first time unit.

[0267] State 4: The method according to any one of States 1 to 3 further includes: receiving a configuration of a first search space set and a second search space set; and identifying a repetition of the downlink control information in the first search space set and the downlink control information in the second search space set, wherein receiving the downlink control information is based on the repetition of the downlink control information in the first search space set and the downlink control information in the second search space set.

[0268] State 5: The method according to State 4 further includes: identifying at least a first monitoring opportunity for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set based on the repetition of the downlink control information included in the first search space set and the second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set; and monitoring at least one of the first monitoring opportunity or the second monitoring opportunity, wherein receiving the downlink control information is based on the monitoring.

[0269] State 6: The method according to any one of states 1 to 5 further includes: determining that the downlink control information is associated with a semi-persistent schedule for releasing the entity downlink shared channel; and calculating the threshold time unit number based on determining that the downlink control information is associated with a semi-persistent schedule for releasing the entity downlink shared channel, wherein sending the feedback message includes sending the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

[0270] State 7: The method according to any one of states 1 to 6 further includes: determining that the downlink control information is associated with the cocell dormancy of the unscheduled entity downlink shared channel; and calculating the threshold time unit number based on determining that the downlink control information is associated with the cocell dormancy of the unscheduled entity downlink shared channel, wherein sending the feedback message includes sending the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

[0271] State 8: The method according to any one of states 1 to 7 further includes: determining that the downlink control information is associated with a one-time feedback requesting non-scheduled entity downlink shared channel; and calculating the threshold time unit number based on determining that the downlink control information is associated with a one-time feedback requesting non-scheduled entity downlink shared channel, wherein sending the feedback message includes sending the feedback message for at least the threshold time unit number calculated after the second entity downlink control channel candidate.

[0272] State 9: The method according to any one of states 1 to 8 further includes: decoding at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate, wherein receiving the downlink control information is based on the decoding, wherein the time and frequency resource set is at least the threshold time unit number after the second entity downlink control channel candidate.

[0273] State 10: The method according to any one of states 1 to 9 further includes: soft combining the signal associated with the first entity downlink control channel candidate and the signal associated with the second entity downlink control channel candidate; and decoding the softly combined signal, wherein receiving the downlink control information is based on the decoding.

[0274] State 11: The method according to any one of states 1 to 10 further includes: decoding at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate; and identifying a set of time and frequency resources for sending the feedback message based on the decoding, wherein the set of time and frequency resources is scheduled at least the threshold time unit number after the second entity downlink control channel candidate, wherein sending the feedback message includes: sending the feedback message during the identified set of time and frequency resources.

[0275] State 12: The method according to any one of states 1 to 11, wherein the number of threshold time units is based on the subcarrier spacing configuration and processing capability.

[0276] Sample 13: A method for wireless communication at a first network node, comprising: determining a first physical uplink control channel resource for transmitting a feedback message; receiving downlink control information from a second network node based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; and covering the first feedback message to be transmitted in the first physical uplink control channel resource at least a threshold time unit after the second physical downlink control channel candidate, based on determining that the first physical uplink control channel resource is at least a threshold time unit after the second physical downlink control channel candidate.

[0277] State 14: The method according to State 13 further includes: determining the time period that the candidate downlink control channel of the second entity ends in the first time unit, wherein covering the feedback message to be sent in the uplink control channel resource of the first entity includes: covering the first feedback message to be sent in the uplink control channel resource of the first entity based on the fact that the uplink control channel resource of the first entity is at least the threshold time unit number after the first time unit.

[0278] State 15: The method according to any one of states 13 to 14 further includes: determining the downlink control information indicating a second physical uplink control channel resource for transmission of a physical uplink control channel with a second feedback message; and using the second physical uplink control channel resource to send the first feedback message and the second feedback message based on the first physical uplink control channel resource being at least the threshold time unit number after the second physical downlink control channel candidate.

[0279] State 16: The method according to any one of states 13 to 15 further includes: receiving a configuration of a first search space set and a second search space set; and identifying a repetition of the downlink control information in the first search space set and the downlink control information in the second search space set, wherein receiving the downlink control information is based on the repetition of the downlink control information in the first search space set and the downlink control information in the second search space set.

[0280] State 17: The method according to State 16 further includes: identifying at least a first monitoring opportunity for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set based on the repetition of the downlink control information included in the first search space set and the second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set; and monitoring at least one of the first monitoring opportunity or the second monitoring opportunity, wherein receiving the downlink control information is based on the monitoring.

[0281] State 18: The method according to any one of states 13 to 17 further includes: decoding at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate, wherein receiving the downlink control information is based on the decoding.

[0282] State 19: The method according to any one of states 13 to 18 further includes: soft combining the signal associated with the first entity downlink control channel candidate and the signal associated with the second entity downlink control channel candidate; and decoding the softly combined signal, wherein receiving the downlink control information is based on the decoding.

[0283] State 20: The method according to any one of states 13 to 19 further includes: receiving from the second network node second downlink control information indicating uplink control channel resources of the first entity, wherein the downlink control information is received later than the second downlink control information.

[0284] State 21: The method according to any one of states 13 to 20, wherein the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of the semi-persistent scheduling entity.

[0285] State 22: The method according to any one of states 13 to 21, wherein the number of threshold time units is based on the subcarrier spacing configuration and processing capability.

[0286] Sample 23: A method for wireless communication at a first network node, comprising: sending downlink control information to a second network node using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; and receiving a feedback message from the second network node in response to the downlink control information at least a threshold time unit after the second physical downlink control channel candidate.

[0287] State 24: The method according to State 23 further includes: identifying a set of resources for feedback transmission during at least the number of time units of the threshold time unit after the candidate of the second entity downlink control channel, without scheduling the entity downlink shared channel based on the downlink control information.

[0288] State 25: The method according to States 23 to 24 further includes: determining the time period that the candidate downlink control channel of the second entity spans to end in the first time unit, wherein receiving the feedback message includes: receiving the feedback message at least the threshold number of time units after the first time unit.

[0289] Format 26: The method according to any one of Formats 23 to 25 further includes: transmitting a configuration of a first search space set and a second search space set; and identifying a repetition of the downlink control information in the first search space set and the downlink control information in the second search space set, wherein transmitting the downlink control information is based on the repetition of the downlink control information in the first search space set and the downlink control information in the second search space set.

[0290] State 27: The method according to State 26 further includes: based on the repetition of the downlink control information included in the first search space set and the downlink control information included in the second search space set, to at least identify a first monitoring time for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring time for monitoring the downlink control channel candidate of the second entity in the second search space set.

[0291] State 28: The method according to any one of states 23 to 27 further includes: determining that the downlink control information is associated with a semi-persistent schedule for releasing the entity downlink shared channel; and calculating the threshold time unit number based on determining that the downlink control information is associated with a semi-persistent schedule for releasing the entity downlink shared channel, wherein receiving the feedback message includes receiving the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

[0292] State 29: The method according to any one of states 23 to 28 further includes: determining that the downlink control information is associated with the cocell dormancy of the non-scheduled downlink shared channel of the entity; and calculating the threshold time unit number based on determining that the downlink control information is associated with the cocell dormancy of the non-scheduled downlink shared channel of the entity, wherein receiving the feedback message includes receiving the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

[0293] State 30: The method according to any one of states 23 to 29 further includes: determining that the downlink control information is associated with a one-time feedback requesting that the entity's downlink shared channel not be scheduled; and calculating the threshold time unit number based on determining that the downlink control information is associated with a one-time feedback requesting that the entity's downlink shared channel not be scheduled, wherein receiving the feedback message includes receiving the feedback message for at least the threshold time unit number calculated after the second entity downlink control channel candidate.

[0294] State 31: The method according to any one of states 23 to 30, wherein the number of threshold time units is based on the subcarrier spacing configuration and processing capability.

[0295] Sample 32: A method for wireless communication at a first network node, comprising: scheduling a first physical uplink control channel resource for a second network node to send a first feedback message; sending downlink control information to the second network node using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly connected for a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; determining whether the first physical uplink control channel resource is available for at least a threshold time unit period after the second physical downlink control channel candidate; and determining whether to cover the feedback message based on the determination of the time unit period after the second physical downlink control channel candidate.

[0296] State 33: The method according to State 32 further includes: determining the time period at which the candidate span of the second entity downlink control channel ends in the first time unit, wherein determining that the first entity uplink control channel resource is covered includes: determining that the first entity uplink control channel resource is covered based on the time unit associated with the first entity uplink control channel resource being scheduled at least the threshold number of time units after the first time unit.

[0297] State 34: The method according to any one of states 32 to 33 further includes: determining that the downlink control information indicates a second physical uplink control channel resource for transmission of a physical uplink control channel with a second feedback message; and using the second physical uplink control channel resource to receive the feedback message and the second feedback message based on the time unit associated with the first physical uplink control channel resource being at least the threshold time unit number after the second physical downlink control channel candidate.

[0298] Format 35: The method according to any one of Formats 32 to 34 further includes: transmitting the configuration of a first search space set and a second search space set; and identifying a repetition of the downlink control information in the first search space set and the downlink control information in the second search space set, wherein transmitting the downlink control information is based on the repetition of the downlink control information in the first search space set and the downlink control information in the second search space set.

[0299] State 36: The method according to State 35 further includes: based on the repetition of the downlink control information included in the first search space set and the downlink control information included in the second search space set, to at least identify a first monitoring time for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring time for monitoring the downlink control channel candidate of the second entity in the second search space set.

[0300] State 37: The method according to any one of states 32 to 36 further includes: sending to the second network node second downlink control information indicating the uplink control channel resources of the first entity, wherein the downlink control information is sent later than the second downlink control information.

[0301] State 38: The method according to any one of states 32 to 37, wherein the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of the semi-persistent scheduling entity.

[0302] State 39: The method according to any one of states 32 to 38, wherein the number of threshold time units is based on the subcarrier spacing configuration and processing capability.

[0303] Style 40: An apparatus for wireless communication at a first network node, comprising: at least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to perform the method according to any one of styles 1 to 12.

[0304] Format 41: An apparatus for wireless communication at a first network node, comprising at least one component for performing the method according to any one of Formats 1 to 12.

[0305] Format 42: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code including instructions executable by a processor to perform the method according to any one of Formats 1 to 12.

[0306] Sample 43: An apparatus for wireless communication at a first network node, comprising: at least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to perform the method according to any one of Samples 13 to 22.

[0307] Sample 44: An apparatus for wireless communication at a first network node, comprising at least one component for performing the method according to any one of Samples 13 to 22.

[0308] Sample 45: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code including instructions executable by a processor to perform the method according to any one of Samples 13 to 22.

[0309] Sample 46: An apparatus for wireless communication at a first network node, comprising: at least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to perform the method according to any one of Samples 23 to 31.

[0310] Sample 47: An apparatus for wireless communication at a first network node, comprising at least one component for performing the method according to any one of Samples 23 to 31.

[0311] Sample 48: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code including instructions executable by a processor to perform the method according to any one of Samples 23 to 31.

[0312] Sample 49: An apparatus for wireless communication at a first network node, comprising: at least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to perform the method according to any one of Samples 32 to 39.

[0313] Sample 50: An apparatus for wireless communication at a first network node, comprising at least one component for performing the method according to any one of Samples 32 to 39.

[0314] Format 51: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code including instructions executable by a processor to perform the method according to any one of formats 32 to 39.

[0315] It should be noted that the methods described herein describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, variants from two or more methods can be combined.

[0316] While various forms of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the technologies described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described technologies can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0317] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles or any combination thereof.

[0318] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) can be a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more elements, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, a network node can be a UE. As another example, a network node can be a base station. As another example, a first network node can be configured to communicate with a second or third network node. In one embodiment of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another embodiment of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In yet another embodiment of this example, the first, second, and third network nodes may differ from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures that the UE, base station, device, equipment, computing system, etc., are network nodes. For example, disclosures that the UE is configured to receive information from a base station also disclose that the first network node is configured to receive information from a second network node. Consistent with the content of this application, once a specific example is broadened according to the content of this application (e.g., disclosures that the UE is configured to receive information from a base station also disclose that the first network node is configured to receive information from a second network node), a broader example of a narrower example can be interpreted in reverse, but in a broad, open-ended manner. In the example above, the UE is configured to receive information from the base station, and it is also revealed that the first network node is configured to receive information from the second network node. The first network node may refer to the first UE, the first base station, the first device, the first computing system, the first one or more components, the first processing entity, etc., configured to receive information; and the second network node may refer to the second UE, the second base station, the second device, the second computing system, the first one or more components, the first processing entity, etc.

[0319] As described herein, communication of information (e.g., any information, signal, etc.) can be described in various forms using different terms. The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node can be described as being configured to send information to a second network node. In this example and consistent with the present invention, the disclosure that a first network node is configured to send information to a second network node includes the disclosure that the first network node is configured to provide, send, output, transmit, or transmit information to the second network node. Similarly, in this example and consistent with the present invention, the disclosure that a first network node is configured to send information to a second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or transmitted by the first network node.

[0320] The various illustrative blocks and elements described in connection with the disclosure herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, individual gate or transistor logic, individual hardware element or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration).

[0321] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, such functions can be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and implementations are within the scope of this document and the claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be located at various physical locations, including being distributed such that different parts of the functionality are implemented at different physical locations.

[0322] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media including any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available media that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory, CD-ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures, and any other non-transitory media that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, magnetic disks and optical disks include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically reproduce data magnetically, while optical discs utilize lasers to optically reproduce data. Combinations of the above are also included within the scope of computer-readable media.

[0323] As used herein (including in a request item), the word "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "at least partially based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

[0324] The term "determine" or "determining" encompasses a wide variety of actions, and therefore, "determining" can include calculation, operation, processing, deduction, research, examination (e.g., examining in a table, database, or other data structure), ascertainment, etc. Furthermore, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determining" can include parsing, selecting, choosing, creating, and other similar actions.

[0325] In the accompanying drawings, similar elements or features may have the same element symbol. Furthermore, various elements of the same type can be distinguished by a dash and a second mark following the element symbol, which is used to differentiate between similar elements. If only the first element symbol is used in the specification, the description applies to any one of the similar elements having the same first element symbol, without regard to the second element symbol or other subsequent element symbols.

[0326] This document describes example configurations in conjunction with the accompanying drawings, and does not represent all examples that can be implemented or are within the scope of the requested item. The term "example" as used herein means "used as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The term "style" as used herein means "used as an example, instance, or illustration," and not "preferred" or "advantageous over other styles." For the purpose of providing an understanding of the described techniques, detailed descriptions include specific details. However, these techniques can be implemented without these specific details.

[0327] The description herein enables those skilled in the art to implement or use the content of this application. Various modifications to the content of this application will be readily apparent to those skilled in the art, and the overall principles defined herein can be applied to other variations without departing from the scope of the content of this application. Therefore, the content of this application is not limited to the examples and designs of the various forms described herein, but is given the broadest scope consistent with the principles and novel features disclosed herein. [Simplified Explanation of the Diagram]

[0007] Figure 1 illustrates an example of a wireless communication system that supports downlink control information processing technology according to various aspects of the present invention.

[0008] Figure 2 illustrates an example of a wireless communication system that supports downlink control information processing technology according to various aspects of the present invention.

[0009] Figure 3 illustrates an example of a block diagram showing various forms of support for downlink control information processing technologies according to the content of this case.

[0010] Figure 4 illustrates an example of a block diagram showing various forms of support for downlink control information processing according to the contents of this case.

[0011] Figure 5 illustrates an example of a program flow supporting downlink control information processing technology according to various aspects of the present invention.

[0012] Figure 6 illustrates an example of a program flow that supports various technologies for downlink control information processing according to the contents of this case.

[0013] Figures 7 and 8 are block diagrams of devices supporting downlink control information processing technologies according to various aspects of the present invention.

[0014] Figure 9 is a block diagram illustrating a communication manager that supports downlink control information processing technology according to various forms of the present invention.

[0015] Figure 10 is a diagram of a system including a device supporting technology for downlink control information processing, according to various forms of the present invention.

[0016] Figures 11 and 12 illustrate block diagrams of devices supporting downlink control information processing technologies according to various aspects of the present invention.

[0017] Figure 13 is a block diagram illustrating a communication manager that supports downlink control information processing technology according to various forms of the present invention.

[0018] Figure 14 is a diagram of a system including a device supporting technology for downlink control information processing, according to various forms of the present invention.

[0019] Figures 15 to 22 illustrate flowcharts of various methods for supporting downlink control information processing technologies according to the contents of this case. [Biomaterial Storage]

[0329] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.

Claims

1. A first network node for wireless communication, comprising: At least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to: receive downlink control information from a second network node based on monitoring at least one of a first physical downlink control channel candidate or a second physical downlink control channel candidate that is repeatedly connected to a physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; and respond to the downlink control information by sending a feedback message to the second network node in response to the downlink control information at least a threshold time unit after the second physical downlink control channel candidate; wherein the downlink control information is not configured to schedule a physical downlink shared channel transmission.

2. The first network node according to claim 1, wherein the second entity downlink control channel candidate spans a time period ending in a first time unit, and wherein, in order to send the feedback message, the at least one processor is configured to send the feedback message after the first time unit for at least the threshold number of time units.

3. The first network node according to claim 1, wherein the at least one processor is configured to: receive a configuration of a first search space set and a second search space set, wherein the first search space set includes the downlink control information and the second search space set includes a duplicate of the downlink control information, and wherein the at least one processor is configured to: receive the downlink control information based on the duplicate of the downlink control information in the first search space set and the second search space set.

4. The first network node according to claim 3, wherein the at least one processor is configured to: identify at least a first monitoring opportunity for monitoring a first entity downlink control channel candidate in the first search space set and a second monitoring opportunity for monitoring a second entity downlink control channel candidate in the second search space set, based on the repetition of the downlink control information in the first search space set and the second search space set including the downlink control information; and wherein, in order to receive the downlink control information, the at least one processor is configured to: monitor at least one of the first monitoring opportunity or the second monitoring opportunity.

5. The first network node according to claim 1, wherein the downlink control information is associated with a semi-persistent schedule for releasing an entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on the association between the downlink control information and the semi-persistent schedule for releasing the entity downlink shared channel, wherein in order to send the feedback message, the at least one processor is configured to: send the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

6. The first network node according to claim 1, wherein the downlink control information is associated with a secondary cell sleep of an unscheduled entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on the association of the downlink control information with the secondary cell sleep of the unscheduled entity downlink shared channel, wherein in order to send the feedback message, the at least one processor is configured to: send the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

7. The first network node according to claim 1, wherein the downlink control information is associated with a request for a one-time feedback for an unscheduled entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on the downlink control information associated with the request for a one-time feedback for an unscheduled entity downlink shared channel, wherein in order to send the feedback message, the at least one processor is configured to: send the feedback message after at least the calculated threshold time unit number following the candidate for the second entity downlink control channel.

8. The first network node according to claim 1, wherein the at least one processor is configured to: decode at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate, wherein the at least one processor is configured to: receive the downlink control information based on the decoding.

9. The first network node according to claim 1, wherein the at least one processor is configured to: softly combine a signal associated with the first entity downlink control channel candidate and a signal associated with the second entity downlink control channel candidate; and decode the softly combined signal, wherein the at least one processor is configured to: receive the downlink control information based on the decoding.

10. The first network node according to claim 1, wherein the at least one processor is configured to: decode at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate, wherein in order to send the feedback message, the at least one processor is configured to: send the feedback message using a set of time and frequency resources based on the decoding, wherein the set of time and frequency resources is at least the threshold time unit number after the second entity downlink control channel candidate.

11. The first network node according to claim 1, wherein the threshold time unit number is based on a carrier interval configuration and a processing capacity.

12. A first network node for wireless communication, comprising: At least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to: determine a first entity uplink control channel resource for sending a first feedback message; receive downlink control information from a second network node based on monitoring at least one of a first entity downlink control channel candidate or a second entity downlink control channel candidate that is repeatedly connected to the entity downlink control channel, wherein the second entity downlink control channel candidate ends later than the first entity downlink control channel candidate; and cover the first feedback message to be sent in the first entity uplink control channel resource based on determining that the first entity uplink control channel resource is at least one threshold time unit after the second entity downlink control channel candidate; wherein the downlink control information is not configured to be scheduled for transmission on an entity downlink shared channel.

13. The first network node according to claim 12, wherein the second entity downlink control channel candidate spans a time period ending in a first time unit, and wherein the at least one processor is configured to: cover the first feedback message to be sent in the first entity uplink control channel resource based on the fact that the first entity uplink control channel resource is at least the threshold number of time units after the first time unit.

14. The first network node according to claim 12, wherein the downlink control information indicates a second physical uplink control channel resource for transmission of a physical uplink control channel having a second feedback message, and wherein the at least one processor is configured to: use the second physical uplink control channel resource to send the first feedback message and the second feedback message based on the first physical uplink control channel resource being at least the threshold time unit number after the second physical downlink control channel candidate.

15. The first network node according to claim 12, wherein the at least one processor is configured to: receive a configuration of a first search space set and a second search space set, wherein the first search space set includes the downlink control information and the second search space set includes a duplicate of the downlink control information, and wherein the at least one processor is configured to: receive the downlink control information based on the duplicate of the downlink control information in the first search space set and the second search space set.

16. The first network node according to claim 15, wherein the at least one processor is configured to: identify at least a first monitoring opportunity for monitoring a first entity downlink control channel candidate in the first search space set and a second monitoring opportunity for monitoring a second entity downlink control channel candidate in the second search space set, based on the duplication of the downlink control information in the first search space set and the second search space set including the downlink control information; and monitor at least one of the first monitoring opportunity or the second monitoring opportunity, wherein the at least one processor is configured to: receive the downlink control information based on the monitoring.

17. The first network node according to claim 12, wherein the at least one processor is configured to: decode at least one of the first entity downlink control channel candidate or the second entity downlink control channel candidate, wherein the at least one processor is configured to: receive the downlink control information based on the decoding.

18. The first network node according to claim 12, wherein the at least one processor is configured to: softly combine a signal associated with the first entity downlink control channel candidate and a signal associated with the second entity downlink control channel candidate; and decode the softly combined signal, wherein the at least one processor is configured to: receive the downlink control information based on the decoding.

19. The first network node according to claim 12, wherein the at least one processor is configured to: receive second downlink control information indicating uplink control channel resources of the first entity from the second network node, wherein the at least one processor is configured to: receive the downlink control information later than the second downlink control information.

20. The first network node as described in claim 12, wherein the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of a half-persistent scheduling entity.

21. The first network node according to claim 12, wherein the number of threshold time units is based on a carrier interval configuration and a processing capacity.

22. A first network node for wireless communication, comprising: At least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to: send downlink control information to a second network node using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for physical downlink control channels, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; and, in response to the downlink control information, receive a feedback message from the second network node after the second physical downlink control channel candidate by at least a threshold time unit; wherein the downlink control information is not configured to schedule a physical downlink shared channel transmission.

23. The first network node according to claim 22, wherein the at least one processor is configured to: identify a set of resources for feedback transmission during a time unit period of at least the threshold time unit number after the second physical downlink control channel candidate, without scheduling a physical downlink shared channel based on the downlink control information.

24. The first network node according to claim 22, wherein the second entity downlink control channel candidate spans a time period ending in a first time unit, and wherein, in order to receive the feedback message, the at least one processor is configured to receive the feedback message after the first time unit for at least the threshold number of time units.

25. The first network node according to claim 22, wherein the at least one processor is configured to: send a configuration of a first search space set and a second search space set, wherein the first search space set includes the downlink control information and the second search space set includes a duplicate of the downlink control information, and wherein the at least one processor is configured to: send the downlink control information based on the duplicate of the downlink control information in the first search space set and the second search space set.

26. The first network node according to claim 25, wherein the at least one processor is configured to: identify at least a first monitoring opportunity for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set, based on the repetition of the downlink control information in the first search space set including the downlink control information and the second search space set including the downlink control information.

27. The first network node according to claim 22, wherein the downlink control information is associated with a semi-persistent schedule for releasing an entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on the determination that the downlink control information is associated with the semi-persistent schedule for releasing the entity downlink shared channel, wherein in order to receive the feedback message, the at least one processor is configured to: receive the feedback message for at least the calculated threshold time unit number after the second entity downlink control channel candidate.

28. The first network node according to claim 22, wherein the downlink control information is associated with a secondary cell dormancy of an unscheduled entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on the determination that the downlink control information is associated with a secondary cell dormancy of an unscheduled entity downlink shared channel, wherein in order to receive the feedback message, the at least one processor is configured to: receive the feedback message after at least the calculated threshold time unit number following the second entity downlink control channel candidate.

29. The first network node according to claim 22, wherein the downlink control information is associated with a request for a one-time feedback for an unscheduled entity downlink shared channel, and wherein the at least one processor is configured to: calculate the threshold time unit number based on determining that the downlink control information is associated with the request for a one-time feedback for an unscheduled entity downlink shared channel, wherein in order to receive the feedback message, the at least one processor is configured to: receive the feedback message for at least the calculated threshold time unit number after the second entity downlink control channel candidate.

30. The first network node according to claim 22, wherein the threshold time unit number is based on a carrier interval configuration and a processing capacity.

31. A first network node for wireless communication, comprising: At least one processor; and memory coupled to the at least one processor, wherein the at least one processor is configured to: schedule a first physical uplink control channel resource for a second network node to send a feedback message; send downlink control information to the second network node using a first physical downlink control channel candidate and a second physical downlink control channel candidate that are repeatedly linked for the physical downlink control channel, wherein the second physical downlink control channel candidate ends later than the first physical downlink control channel candidate; determine whether the first physical uplink control channel resource is available during a time unit period at least a threshold time unit number after the second physical downlink control channel candidate; and determine whether to cover the feedback message based on the determination of the time unit at least the threshold time unit number after the second physical downlink control channel candidate; wherein the downlink control information is not configured to be scheduled for transmission on a physical downlink shared channel.

32. The first network node according to claim 31, wherein the second entity downlink control channel candidate spans a time period ending in a first time unit, and wherein the at least one processor is configured to determine that the first entity uplink control channel resource is covered based on the time unit associated with the first entity uplink control channel resource being scheduled at least the threshold number of time units after the first time unit.

33. The first network node according to claim 31, wherein the downlink control information indicates a second physical uplink control channel resource for transmission of a physical uplink control channel having a second feedback message; and the second physical uplink control channel resource is used to receive the feedback message and the second feedback message based on the time unit associated with the first physical uplink control channel resource being at least the threshold time unit number after the second physical downlink control channel candidate.

34. The first network node according to claim 31, wherein the at least one processor is configured to: send a configuration of a first search space set and a second search space set, wherein the first search space set includes the downlink control information and the second search space set includes a duplicate of the downlink control information, and wherein the at least one processor is configured to: send the downlink control information based on the duplicate of the downlink control information in the first search space set and the second search space set.

35. The first network node according to claim 34, wherein the at least one processor is configured to: identify at least a first monitoring opportunity for monitoring the downlink control channel candidate of the first entity in the first search space set and a second monitoring opportunity for monitoring the downlink control channel candidate of the second entity in the second search space set, based on the repetition of the downlink control information in the first search space set including the downlink control information and the second search space set including the downlink control information.

36. The first network node according to claim 31, wherein the at least one processor is configured to: send to the second network node a second downlink control information indicating uplink control channel resources of the first entity, wherein the downlink control information is sent later than the second downlink control information.

37. The first network node as described in claim 31, wherein the uplink control channel resources of the first entity are associated with the release of the downlink shared channel of a half-persistent scheduling entity.

38. The first network node according to claim 31, wherein the threshold time unit number is based on a carrier interval configuration and a processing capacity.

Images