CN117897919A - Downlink feedback information with physical downlink control channel repetition - Google Patents

Downlink feedback information with physical downlink control channel repetition Download PDF

Info

Publication number
CN117897919A
CN117897919A CN202280058644.9A CN202280058644A CN117897919A CN 117897919 A CN117897919 A CN 117897919A CN 202280058644 A CN202280058644 A CN 202280058644A CN 117897919 A CN117897919 A CN 117897919A
Authority
CN
China
Prior art keywords
pdcch
pdcch candidates
candidates
dfi
dci
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202280058644.9A
Other languages
Chinese (zh)
Inventor
M·霍什内维桑
张晓霞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/813,507 external-priority patent/US20230114685A1/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority claimed from PCT/US2022/075733 external-priority patent/WO2023064650A1/en
Publication of CN117897919A publication Critical patent/CN117897919A/en
Pending legal-status Critical Current

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a mobile station may receive a set of Physical Downlink Control Channel (PDCCH) candidates, wherein the set of PDCCH candidates are linked for PDCCH repetition. The mobile station may detect Downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more PDCCH candidates. The mobile station may identify the PDCCH candidate as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria. The mobile station may determine whether the DFI is valid for a Physical Uplink Shared Channel (PUSCH) transmission based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols before a first symbol of the reference PDCCH candidate. Various other aspects are described.

Description

Downlink feedback information with physical downlink control channel repetition
Cross Reference to Related Applications
This patent application claims priority to the following applications: U.S. provisional patent application Ser. No.63/262,486, filed on month 10, 2021, entitled "DOWNLINK FEEDBACK INFORMATION WITH PHYSICAL DOWNLINK CONTROL CHANNEL REPETITION (with physical downlink control channel repeated downlink feedback information)", and U.S. non-provisional patent application Ser. No.17/813,507, filed on month 7, 2022, and entitled "DOWNLINK FEEDBACK INFORMATION WITH PHYSICAL DOWNLINK CONTROL CHANNEL REPETITION (with physical downlink control channel repeated downlink feedback information)", are expressly incorporated herein by reference.
Technical Field
Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for Downlink Feedback Information (DFI) with Physical Downlink Control Channel (PDCCH) repetition.
Background
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the third generation partnership project (3 GPP).
A wireless network may include one or more base stations that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink and uplink communications. "downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.
The multiple access techniques described above have been employed in various telecommunications standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and/or global level. The New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3 GPP. NR is designed as: mobile broadband internet access is better supported by improving spectral efficiency, reducing costs, improving services, using new spectrum and other open standards with Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), and supporting beamforming, multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.
Disclosure of Invention
Some aspects described herein relate to a mobile station for wireless communications. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: a set of Physical Downlink Control Channel (PDCCH) candidates is received, wherein the set of PDCCH candidates are linked for PDCCH repetition. The one or more processors may be configured to: downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more PDCCH candidates in the set of PDCCH candidates is detected. The one or more processors may be configured to: the PDCCH candidates in the set of PDCCH candidates are identified as reference PDCCH candidates based at least in part on the PDCCH candidates meeting one or more criteria. The one or more processors may be configured to: determining whether feedback information for transport blocks of a corresponding hybrid automatic repeat request (HARQ) process number in the DFI is valid for a Physical Uplink Shared Channel (PUSCH) transmission based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols before a first symbol of the reference PDCCH candidate.
Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include: a set of PDCCH candidates is received by the mobile station, wherein the set of PDCCH candidates is linked for PDCCH repetition. The method may include: detecting, by the mobile station, DCI carrying a DFI among one or more PDCCH candidates in the set of PDCCH candidates. The method may include: identifying, by the mobile station, the PDCCH candidate in the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria. The method may include: determining, by the mobile station, whether feedback information for transport blocks of a corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols preceding a first symbol of the reference PDCCH candidate.
Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a mobile station. The set of instructions, when executed by the one or more processors of the mobile station, may cause the mobile station to: a set of PDCCH candidates is received, wherein the set of PDCCH candidates is linked for PDCCH repetition. The set of instructions, when executed by the one or more processors of the mobile station, may cause the mobile station to: and detecting DCI carrying DFI in one or more PDCCH candidates in the PDCCH candidate set. The set of instructions, when executed by the one or more processors of the mobile station, may cause the mobile station to: the PDCCH candidates in the set of PDCCH candidates are identified as reference PDCCH candidates based at least in part on the PDCCH candidates meeting one or more criteria. The set of instructions, when executed by the one or more processors of the mobile station, may cause the mobile station to: determining whether feedback information for transport blocks of a corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols preceding a first symbol of the reference PDCCH candidate.
Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: and means for receiving a set of PDCCH candidates, wherein the set of PDCCH candidates is linked for PDCCH repetition. The apparatus may include: and means for detecting DCI carrying a DFI among one or more PDCCH candidates in the set of PDCCH candidates. The apparatus may include: and identifying the PDCCH candidate in the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidate satisfying one or more criteria. The apparatus may include: determining whether feedback information for transport blocks of the corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols preceding a first symbol of the reference PDCCH candidate.
Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user device, base station, wireless communication device, and/or processing system as generally described herein with reference to and as illustrated in the accompanying drawings and description.
The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein (their organization and method of operation) and associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.
While various aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that: these aspects may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial devices, retail/procurement devices, medical devices, and/or artificial intelligence devices). The various aspects may be implemented in a chip-level component, a modular component, a non-chip-level component, a device-level component, and/or a system-level component. Devices including the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) for analog and digital purposes.
Drawings
So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to some aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description herein may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
Fig. 2 is a diagram illustrating an example of a base station communicating with a User Equipment (UE) in a wireless network in accordance with the present disclosure.
Fig. 3A-3E are diagrams illustrating example resource structures for wireless communications according to this disclosure.
Fig. 4A-4D are diagrams illustrating examples associated with Downlink Feedback Information (DFI) with Physical Downlink Control Channel (PDCCH) repetition according to the present disclosure.
Fig. 5 is a diagram illustrating an example process associated with a DFI with PDCCH repetition in accordance with the present disclosure.
Fig. 6 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure.
Detailed Description
Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art will appreciate that: the scope of the present disclosure is intended to encompass any aspect of the disclosure herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Furthermore, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to or other than the aspects of the disclosure presented herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
Several aspects of the telecommunications system will now be presented with reference to various apparatus and techniques. These devices and techniques are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
While aspects may be described using terms commonly associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).
Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, and so on. Wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120, or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Base station 110 is the entity in communication with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or transmit-receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a base station 110 and/or a base station subsystem serving the coverage area, depending on the context in which the term is used.
Base station 110 may provide communication coverage for macro cells, pico cells, femto cells, and/or other types of cells. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow limited access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, BS110a may be a macro base station for macro cell 102 a; BS110b may be a pico base station for pico cell 102 b; and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells.
In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the moving base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected to each other and/or one or more other base stations 110 or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces (e.g., direct physical connections or virtual networks) using any suitable transmission network.
The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., base station 110 or UE 120) and send data transmissions to a downstream station (e.g., UE 120 or base station 110). The relay station may be UE 120 that may relay transmissions for other UEs. In the example shown in fig. 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE 120d in order to facilitate communication between BS110a and UE 120 d. The base station 110 relaying communications may be referred to as a relay station, a relay base station, a repeater, etc.
The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, and so on. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different effects on interference in the wireless network 100. For example, macro base stations may have a higher transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).
The network controller 130 may be coupled to or in communication with a set of base stations 110 and provide coordination and control for these base stations 110. The network controller 130 may 110 communicate with the base stations 110 via backhaul communication links. Base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.
UEs 120 may be dispersed throughout wireless network 100 and each UE 110 may be fixed or mobile. UE 120 may include, for example, an access terminal, a mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, a super-book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring, a smartband)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicle component or sensor, a smartmeter/sensor, an industrial manufacturing device, a global positioning system device, and/or any other suitable device configured to communicate via a wireless medium.
Some UEs 120 may be considered Machine Type Communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and/or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses components (e.g., processor components and/or memory components) of UE 120. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequencies may be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120 e) may communicate directly (e.g., without using base station 110 as an intermediary device) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-all (V2X) protocols (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein that are performed by base station 110.
Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been determined as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as the (interchangeable) "below 6 GHz" frequency band in various documents and articles. Similar naming problems sometimes occur for FR2, which in documents and articles is commonly (interchangeably) referred to as the "millimeter wave" band, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.
The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have determined the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and may therefore effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands belongs to the EHF frequency band.
In view of the above examples, unless explicitly stated otherwise, it should be understood that the term "below 6GHz" and the like, if used herein, may broadly mean frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless explicitly stated otherwise, it is to be understood that: the term "millimeter wave" or the like, if used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4-a, FR4-1, and/or FR 5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.
In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may perform one or more operations associated with Downlink Feedback Information (DFI) with Physical Downlink Control Channel (PDCCH) repetition. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.
As described above, fig. 1 is provided as an example. Other examples may differ from the example described with respect to fig. 1.
Fig. 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234T, e.g., T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, e.g., R antennas (r≡1).
At base station 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on the one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) as indicated by modems 232a through 232T. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232T may transmit a set of downlink signals (e.g., T downlink signals) via corresponding antenna groups 234 (e.g., T antennas), shown as antennas 234a through 234T.
At UE 120, antenna group 252 (shown as antennas 252a through 252R) may receive the downlink signals from base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254R. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator assembly to condition (e.g., filter, amplify, downconvert, and/or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to controller/processor 280. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter, among others. In some examples, one or more components of UE 120 may be included in housing 284.
The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may comprise, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via a communication unit 294.
One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and/or one or more antenna arrays, etc. The antenna panel, antenna group, group of antenna elements, and/or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmit and/or receive components, such as one or more components of fig. 2.
On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 as well as control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ and/or CQI). Transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., with reference to fig. 4A-4D, fig. 5, and fig. 6).
At base station 110, uplink signals from UE 120 and/or other UEs may be received by antennas 234, processed by a modem 232 (e.g., a demodulator component of modem 232, shown as DEMOD), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., with reference to fig. 4A-4D, fig. 5, and fig. 6).
As described in more detail elsewhere herein, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform one or more techniques associated with DFI with PDCCH repetition. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations of process 500 of fig. 5 and/or other processes as described herein, for example. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and/or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly or after compiling, converting, and/or interpreting), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 500 of fig. 5 and/or other processes as described herein. In some examples, the execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions, among others.
In some aspects, a mobile station (e.g., UE 120) includes: means for receiving, by a mobile station, a set of PDCCH candidates, wherein the set of PDCCH candidates is linked for PDCCH repetition; means for detecting, by a mobile station, downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more PDCCH candidates in a set of PDCCH candidates; identifying, by the mobile station, a PDCCH candidate of the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidates meeting one or more criteria; and/or determining, by the mobile station, whether feedback information for transport blocks of the corresponding HARQ process number in the DFI is valid for a Physical Uplink Shared Channel (PUSCH) transmission based at least in part on whether a last symbol of the PUSCH transmission is at least some number of symbols prior to a first symbol of the reference PDCCH candidate. In some aspects, means for causing a mobile station to perform operations described herein may comprise, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
Although the blocks in fig. 2 are shown as distinct components, the functionality described above for the blocks may be implemented in a single hardware, software, or combined component or various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by or under the control of controller/processor 280.
As described above, fig. 2 is provided as an example. Other examples may differ from the example described with respect to fig. 2.
Fig. 3A-3E are diagrams illustrating an example resource structure 300 for wireless communications according to this disclosure. Resource structure 300 illustrates an example of various resource groups described herein. As shown, the resource structure 300 may include a subframe 305. The subframe 305 may include a plurality of slots 310. Although resource structure 300 is shown as including 2 slots per subframe, a different number of slots (e.g., 4 slots, 8 slots, 16 slots, 32 slots, or other number of slots) may be included in a subframe. In some aspects, different types of Transmission Time Intervals (TTIs) may be used instead of subframes and/or slots. The slot 310 may include a plurality of symbols 315, for example 7 symbols per slot.
The potential control region of the slot 310 may be referred to as a control resource set (CORESET) 320 and may be structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources of the CORESET 320 for one or more PDCCHs and/or one or more Physical Downlink Shared Channels (PDSCH). In some aspects, CORESET 320 may occupy a first symbol 315 of slot 310, the first two symbols 315 of slot 310, or the first three symbols 315 of slot 310. Accordingly, CORESET 320 may include a plurality of Resource Blocks (RBs) in the frequency domain, as well as one, two, or three symbols 315 in the time domain. In 5G, the number of resources included in CORESET 320 may be flexibly configured, for example, by using Radio Resource Control (RRC) signaling to indicate a frequency domain region (e.g., the number of resource blocks) and/or a time domain region (e.g., the number of symbols) for CORESET 320.
As shown, symbols 315 comprising CORESET 320 may include one or more Control Channel Elements (CCEs) 325, shown as two CCEs 325 as an example, that span a portion of the system bandwidth. CCE 325 may include Downlink Control Information (DCI) for providing control information for wireless communications. The base station may transmit DCI during a plurality of CCEs 325 (as shown), where the number of CCEs 325 used to transmit the DCI represents an Aggregation Level (AL) used by the base station to transmit the DCI. In fig. 3, an aggregation level of 2 is shown as an example, corresponding to two CCEs 325 in a slot 310. In some aspects, different aggregation levels may be used, such as 1, 2, 4, 8, 16, or other aggregation levels.
Each CCE 325 may include a fixed number of Resource Element Groups (REGs) 330, shown as 6 REGs 330, or may include a variable number of REGs 330. In some aspects, the number of REGs 330 included in CCE 325 may be specified by the REG bundle size. REG 330 may include one resource block, which may include 12 Resource Elements (REs) 335 within symbol 315. The resource unit 335 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.
The search space may include all possible locations (e.g., in time and/or frequency) where the PDCCH may be located. CORESET 320 may include one or more search spaces, such as a UE-specific search space, a group public search space, and/or a public search space. The search space may indicate a set of CCE locations where the UE may find a PDCCH that may potentially be used to send control information to the UE. The possible locations of the PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group-common PDCCH (e.g., for multiple UEs) and/or the aggregation level being used. The possible locations (e.g., in time and/or frequency) of the PDCCH may be referred to as PDCCH candidates, and the set of all possible PDCCH locations at the aggregation level may be referred to as a search space. For example, the set of all possible PDCCH locations for a particular UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations across all UEs may be referred to as a common search space. The set of all possible PDCCH locations for a particular UE group may be referred to as a group common group search space. One or more search spaces across aggregation levels may be referred to as a Set of Search Spaces (SSs).
In some cases, the UE may receive DCI via PDCCH candidates. In some cases, the DCI may include a DFI indicating feedback information associated with one or more previous PUSCH transmissions. For example, the DCI may include a specific format (e.g., DCI format 0_1) in which a Cyclic Redundancy Check (CRC) is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI). The DCI may include a DFI flag field. The UE may determine that the DCI includes the DFI when the DFI flag field is set to a first value (e.g., 1) and may determine that the DCI does not include the DFI when the DFI flag field is set to a second value (e.g., 0).
When the DFI flag field is set to a first value, the DFI included in the DCI may include a 16-bit bitmap indicating feedback information (e.g., hybrid automatic repeat request (HARQ) feedback information) for each identifier (e.g., for each HARQ identifier) of a previous PUSCH transmission. In some cases, the UE may determine the validity of the DFI for each PUSCH transmission based at least in part on when the PUSCH transmission is received (e.g., the DCI is sent by the base station 110 to the UE) with respect to a first symbol of the DCI including the DFI.
In some cases, PUSCH transmissions may not be sent repeatedly. PUSCH transmissions may be associated with semi-static configurations (e.g., configured by configured grants) or may be dynamically scheduled. The UE may determine that the DFI is valid for each PUSCH transmission with a last symbol transmitted at least a certain number of symbols before the first symbol of the DCI was received by the UE. In some cases, a particular number of symbols may be configured by the network (e.g., base station 110 transmitting DCI to the UE). For example, as shown in fig. 3B, a particular number of symbols may correspond to a configured grant minimum DFI Delay (cg-minDFI-Delay) parameter 340.
The UE may determine that the DFI is not valid for PUSCH transmissions associated with HARQ identifiers 3 and 4 based at least in part on the last symbol of the PUSCH transmission not being transmitted at a number of symbols indicated at least by cg-minDFI-Delay parameter 340 prior to the first symbol of the DCI including the DFI received by the UE. The UE may determine that the DFI is valid for PUSCH transmissions associated with HARQ identifiers 0, 1, and 8 based at least in part on the last symbol of each PUSCH transmission being transmitted at least the number of symbols indicated by cg-minDFI-Delay parameter 340 prior to the first symbol of the DCI including the DFI received by the UE.
In some cases, as shown in fig. 3C, a PUSCH transmission (e.g., a PUSCH transmission associated with HARQ identifier 1, as shown) may be configured by the configured grant and may be repeatedly transmitted. In these cases, the UE may determine that the DFI is valid for the PUSCH transmission when the last symbol of any repetition of the PUSCH transmission is transmitted at least a certain number of symbols before the first symbol of the DCI carrying the DFI received by the UE.
In some cases, as shown in fig. 3D, PUSCH transmissions (e.g., PUSCH transmissions associated with HARQ identifier 1, as shown) may be scheduled by dynamic grants and may be repeatedly transmitted. In these cases, the UE may determine that the DFI is valid for the PUSCH transmission when the DFI indicates an Acknowledgement (ACK) associated with the PUSCH transmission, and the last symbol of the first repetition of the PUSCH transmission is transmitted at least a certain number of symbols before the first symbol of the DCI carrying the DFI received by the UE.
In some cases, the DFI may indicate a Negative Acknowledgement (NACK) associated with PUSCH transmissions. In these cases, the UE may determine that the DFI is valid for PUSCH transmission when the last symbol of the last repetition of PUSCH transmission is transmitted at least a certain number of symbols before the first symbol of the DCI carrying the DFI received by the UE. As shown in fig. 3E, the UE may determine that the DFI is not valid for a PUSCH transmission associated with a HARQ Identifier (ID) 1 based at least in part on the last symbol of the last repetition of the PUSCH transmission (e.g., repetition 4, as shown) not being at least a certain number of symbols before the first symbol of the DCI carrying the DFI received by the UE.
In some cases, each PDCCH candidate may be repeatedly configured. For example, the two SS sets may be linked by RRC configuration. The PDCCH candidates of the two linked SS sets may be one-to-one mapped (e.g., a first PDCCH candidate of a first SS set may be mapped to a first PDCCH candidate of a second SS set). The two PDCCH candidates mapped together may have the same aggregation level and may carry the same DCI payload.
The UE may receive the two PDCCH candidates and may decode DCI of the first PDCCH candidate received by the UE or the second PDCCH candidate received by the UE, or may perform soft combining to decode the DCI. Accordingly, the UE may decode DCI included in the first PDCCH candidate received by the UE, DCI included in the second PDCCH candidate received by the UE, or both DCI included in the first PDCCH candidate received by the UE and DCI included in the second PDCCH candidate received by the UE.
In some cases, the DCI may include a DFI indicating feedback information associated with one or more previous PUSCH transmissions. For example, the DCI may include a particular format (e.g., DCI format 0_1) where the CRC is scrambled by the CS-RNTI. The DCI may include a DFI flag field set to a first value (e.g., 1) indicating that the DCI includes a DFI associated with a previous PUSCH transmission. The UE may determine whether the DFI is valid for PUSCH transmission in a manner similar to that described above. However, because the UE may decode DCI included in the first PDCCH candidate, the second PDCCH candidate, or both the first PDCCH candidate and the second PDCCH candidate, the first symbol of the DCI carrying the DFI may be different based at least in part on the DCI decoded by the UE. Thus, the UE may determine different results regarding whether the DFI is valid for PUSCH transmission based at least in part on the DCI decoded by the UE.
Some techniques and apparatuses described herein enable a UE to identify a reference that will be used to determine whether a DFI is valid for PUSCH transmission when the UE receives linked PDCCH candidates. In some aspects, the UE may determine the reference to correspond to DCI received via PDCCH candidates meeting one or more criteria. By utilizing a reference to determine whether the DFI included in the DCI is valid for PUSCH transmission, the UE may prevent different results determined based at least in part on the DCI decoded by the UE.
As described above, fig. 3A-3E are provided as examples. Other examples may be different from the examples described with respect to fig. 3A-3E.
Fig. 4A-4D are diagrams illustrating examples 400, 415, 430, 445 associated with DFI with PDCCH repetition according to the present disclosure. As shown in fig. 4A, in some aspects, a UE (e.g., UE 120) may receive a set of PDCCH candidates (e.g., PDCCH candidate 405 and PDCCH candidate 410, as shown). As described elsewhere herein, PDCCH candidates may be linked for PDCCH repetition.
In some aspects, the UE may detect DCI carrying the DFI in one or more of the PDCCH candidates 405, 410. In some aspects, the UE may decode the PDCCH candidate 405 and may detect that the DCI includes a DFI. In some aspects, the UE may decode the PDCCH candidate 410 and may detect that the DCI includes a DFI. In some aspects, the UE may perform soft combining to decode PDCCH candidate 405 and PDCCH candidate 410, and may detect that the DCI includes a DFI based at least in part on performing soft combining to decode PDCCH candidate 405 and PDCCH candidate 410.
In some aspects, the UE may detect that the DCI carries the DFI based at least in part on the DCI including a particular format (e.g., DCI format 0_1) having a CRC scrambled by the CS-RNTI and the DCI including a DFI flag field set to a particular value (e.g., 1). The DFI may include a 16-bit bitmap indicating feedback information (e.g., HARQ feedback information) for each identifier (e.g., each HARQ identifier) of a previous PUSCH transmission.
In some aspects, the UE may determine one or more reference criteria for determining a reference to be used to determine the validity of the DFI for each PUSCH transmission. In some aspects, the one or more reference criteria may indicate: the PDCCH candidate that starts earliest in time with respect to the other PDCCH candidates will be selected as a reference, the PDCCH candidate that ends earliest in time with respect to the other PDCCH candidates will be selected as a reference, the PDCCH candidate that starts latest in time with respect to the other PDCCH candidates will be selected as a reference, or the PDCCH candidate that ends latest in time with respect to the other PDCCH candidates will be selected as a reference, and so on.
In some aspects, the UE may determine that the PDCCH candidate 405 meets one or more reference criteria and may select the PDCCH candidate 405 as a reference. In some aspects, the UE may determine that PDCCH candidate 410 meets one or more reference criteria and may select PDCCH candidate 410 as a reference.
In some aspects, as shown in fig. 4A, the previous PUSCH transmission may not be repeatedly transmitted. The UE may determine validity of the DFI for the previous PUSCH transmission based at least in part on the previous PUSCH transmission being transmitted without repetition. For example, the UE may determine the validity of the DFI for the previous PUSCH transmission based at least in part on whether the last symbol of the previous PUSCH transmission was transmitted at least a particular number of symbols before the first symbol of the reference in a similar manner as described elsewhere herein. As shown in fig. 4A, the UE may determine that the DFI is valid for the previous PUSCH transmission associated with HARQ IDs 8, 0, and 1 based at least in part on the last symbol of the previous PUSCH transmission being transmitted at least a certain number of symbols before the first symbol of the reference. As also shown in fig. 4A, the UE may determine that the DFI is not valid for the previous PUSCH transmission associated with HARQ ID 3 based at least in part on the last symbol of the previous PUSCH transmission not being transmitted at least a particular number of symbols before the first symbol of the reference.
In some aspects, as shown in fig. 4B, the previous PUSCH transmission may be configured by a configured grant and may be repeatedly transmitted. The UE may determine validity of the DFI for the previous PUSCH transmission based at least in part on the previous PUSCH transmission being configured by the configured grant and based at least in part on the previous PUSCH transmission being repeatedly transmitted. For example, the UE may determine the validity of the DFI for the previous PUSCH transmission based at least in part on whether the last symbol of any repetition of the previous PUSCH transmission was transmitted at least a particular number of symbols before the first symbol of the reference in a similar manner as described elsewhere herein. As shown in fig. 4B, the UE may determine that the DFI is valid for the previous PUSCH transmission based at least in part on the last symbol of the at least first repetition of the previous PUSCH transmission being transmitted at least a particular number of symbols before the first symbol of the reference.
In some aspects, as shown in fig. 4C, the previous PUSCH transmission may be scheduled by a dynamic grant and may be repeatedly transmitted. In some aspects, as also shown in fig. 4C, the DFI may indicate an ACK. The UE may determine validity of the DFI for the previous PUSCH transmission based at least in part on the previous PUSCH transmission being scheduled by the dynamic grant and based at least in part on the DFI indication ACK. For example, the UE may determine the validity of the DFI for the previous PUSCH transmission based at least in part on whether the last symbol of the first repetition of the previous PUSCH transmission was transmitted at least a particular number of symbols before the first symbol of the reference in a similar manner as described elsewhere herein. As shown in fig. 4C, the UE may determine that the DFI is valid for the previous PUSCH transmission based at least in part on the last symbol of the first repetition of the previous PUSCH transmission being transmitted at least a particular number of symbols before the first symbol of the reference.
In some aspects, as shown in fig. 4D, the DFI may indicate a NACK. The UE may determine validity of the DFI for the previous PUSCH transmission based at least in part on the previous PUSCH transmission being scheduled by the dynamic grant and based at least in part on the DFI indication NACK. For example, the UE may determine the validity of the DFI for the previous PUSCH transmission based at least in part on whether the last symbol of the last repetition of the previous PUSCH transmission was transmitted at least a particular number of symbols before the first symbol of the reference in a similar manner as described elsewhere herein. As shown in fig. 4D, the UE may determine that the DFI is not valid for the previous PUSCH transmission based at least in part on the last symbol of the last repetition of the previous PUSCH transmission not being transmitted at least a particular number of symbols before the first symbol of the reference.
As described above, fig. 4A-4D are provided as examples. Other examples may differ from the examples described with respect to fig. 4A-4D.
Fig. 5 is a diagram illustrating an example process 500 performed, for example, by a mobile station in accordance with the present disclosure. Example process 500 is an example of a mobile station (e.g., UE 120) performing operations associated with a DFI with PDCCH repetition.
As shown in fig. 5, in some aspects, process 500 may include receiving a set of PDCCH candidates, wherein the set of PDCCH candidates are linked for PDCCH repetition (block 510). For example, a mobile station (e.g., using communication manager 140 and/or receiving component 602 depicted in fig. 6) can receive a set of PDCCH candidates, wherein the set of PDCCH candidates are linked for PDCCH repetition, as described above.
As further shown in fig. 5, in some aspects, process 500 may include detecting DCI carrying a DFI among one or more PDCCH candidates in a set of PDCCH candidates (block 520). For example, a mobile station (e.g., using communication manager 140 and/or detection component 608 depicted in fig. 6) may detect DCI carrying a DFI among one or more PDCCH candidates in a set of PDCCH candidates, as described above.
As further shown in fig. 5, in some aspects, process 500 may include: the PDCCH candidates in the set of PDCCH candidates are identified as reference PDCCH candidates based at least in part on the PDCCH candidates meeting one or more criteria (block 530). For example, the mobile station (e.g., using communication manager 140 and/or identification component 610 depicted in fig. 6) can identify a PDCCH candidate in the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidates meeting one or more criteria, as described above.
As further shown in fig. 5, in some aspects, process 500 may include: based at least in part on whether the last symbol of the PUSCH transmission is at least some number of symbols before the first symbol of the reference PDCCH candidate, it is determined whether feedback information for a transport block of the corresponding HARQ process number in the DFI is valid for the PUSCH transmission (block 540). For example, the mobile station (e.g., using the communication manager 140 and/or the determining component 612 depicted in fig. 6) can determine whether feedback information for a transport block of a corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of PUSCH transmission is at least some number of symbols before a first symbol of a reference PDCCH candidate, as described above.
Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
In a first aspect, the DCI is associated with a DCI format 0_1 and a CRC scrambled by a CS-RNTI, and a DFI flag of the DCI is set to a first value indicating that the DCI includes the DFI.
In a second aspect, alone or in combination with the first aspect, the PDCCH candidates meet the one or more criteria based at least in part on the earliest in time of the PDCCH candidates relative to other PDCCH candidates in the set of PDCCH candidates.
In a third aspect, alone or in combination with one or more of the first and second aspects, the PDCCH candidates meet the one or more criteria based at least in part on the PDCCH candidates starting latest in time relative to other PDCCH candidates in the set of PDCCH candidates.
In a fourth aspect, alone or in combination with one or more aspects of the first to third aspects, the PDCCH candidates meet the one or more criteria based at least in part on the earliest ending in time of the PDCCH candidates relative to other PDCCH candidates in the set of PDCCH candidates.
In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the PDCCH candidates meet the one or more criteria based at least in part on the PDCCH candidates ending last in time relative to other PDCCH candidates in the set of PDCCH candidates.
While fig. 5 shows example blocks of process 500, in some aspects process 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those shown in fig. 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.
Fig. 6 is a diagram of an example apparatus 600 for wireless communications. The apparatus 600 may be a mobile station or the mobile station may include the apparatus 600. In some aspects, the apparatus 600 includes a receiving component 602 and a transmitting component 604 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 600 may communicate with another apparatus 606 (e.g., a UE, a base station, or another wireless communication device) using a receiving component 602 and a transmitting component 604. As further shown, the apparatus 600 may include a communication manager 140. The communications manager 140 can include one or more of a detection component 608, an identification component 610, or a determination component 612, among others.
In some aspects, the apparatus 600 may be configured to perform one or more operations described herein in connection with fig. 4A-4D. Additionally or alternatively, the apparatus 600 may be configured to perform one or more processes described herein, such as the process 500 of fig. 5. In some aspects, the apparatus 600 and/or one or more components illustrated in fig. 6 may comprise one or more components in a mobile station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 6 may be implemented within one or more of the components described in connection with fig. 2. Additionally, or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.
The receiving component 602 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 606. The receiving component 602 may provide the received communication to one or more other components of the apparatus 600. In some aspects, the receiving component 602 can perform signal processing (e.g., filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 600. In some aspects, the receive component 602 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a mobile station described in connection with fig. 2.
The transmitting component 604 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 606. In some aspects, one or more other components of apparatus 600 may generate a communication and may provide the generated communication to sending component 604 for transmission to apparatus 606. In some aspects, the transmitting component 604 can perform signal processing (e.g., filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 606. In some aspects, the transmit component 604 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the mobile station described in connection with fig. 2. In some aspects, the transmitting component 604 can be co-located with the receiving component 602 in the transceiver.
The receiving component 602 can receive a set of PDCCH candidates, wherein the set of PDCCH candidates is linked for PDCCH repetition. The detection component 608 can detect DCI carrying a DFI among one or more PDCCH candidates in a set of PDCCH candidates. The identifying component 610 can identify a PDCCH candidate in the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidates meeting one or more criteria. The determining component 612 can determine whether feedback information for transport blocks of the corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of PUSCH transmission is at least some number of symbols before a first symbol of a reference PDCCH candidate.
The number and arrangement of components shown in fig. 6 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than the components shown in FIG. 6. Further, two or more of the components shown in FIG. 6 may be implemented within a single component, or a single component shown in FIG. 6 may be implemented as multiple, distributed components. Additionally or alternatively, one set (one or more) of components shown in fig. 6 may perform one or more functions described as being performed by another set of components shown in fig. 6.
The following provides an overview of some aspects of the disclosure:
aspect 1: a method of wireless communication performed by a mobile station, comprising: receiving, by the mobile station, a set of PDCCH candidates, wherein the set of PDCCH candidates is linked for PDCCH repetition; detecting, by the mobile station, DCI carrying a DFI among one or more PDCCH candidates in the set of PDCCH candidates; identifying, by the mobile station, the PDCCH candidate in the set of PDCCH candidates as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria; and determining, by the mobile station, whether feedback information for transport blocks of the corresponding HARQ process number in the DFI is valid for PUSCH transmission based at least in part on whether a last symbol of the PUSCH transmission is at least some number of symbols before a first symbol of the reference PDCCH candidate.
Aspect 2: the method of aspect 1, wherein the DCI is associated with a DCI format 0_1 and a CRC scrambled by a CS-RNTI, and wherein a DFI flag of the DCI is set to a first value indicating that the DCI includes the DFI.
Aspect 3: the method of aspects 1 and 2, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate starting earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
Aspect 4: the method of any of aspects 1-3, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate starting latest in time relative to other PDCCH candidates in the set of PDCCH candidates.
Aspect 5: the method of any of aspects 1-4, wherein the PDCCH candidate meets the one or more criteria based at least in part on the earliest ending in time of the PDCCH candidate relative to other PDCCH candidates in the set of PDCCH candidates.
Aspect 6: the method of any of aspects 1-5, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate ending last in time relative to other PDCCH candidates in the set of PDCCH candidates.
Aspect 7: an apparatus for wireless communication at a device, comprising a processor; a memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1-6.
Aspect 8: an apparatus for wireless communication, comprising a memory, and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-6.
Aspect 9: an apparatus for wireless communication, comprising at least one unit for performing the method of one or more of aspects 1-6.
Aspect 10: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-6.
Aspect 11: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-6.
The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the aspects.
As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, should be broadly interpreted to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures and/or functions, and the like. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It is apparent that the systems and/or methods described herein may be implemented in different forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of these aspects. Because those skilled in the art will appreciate that software and hardware may be designed to implement systems and/or methods based at least in part on the description herein, the operation and behavior of the systems and/or methods are described herein without reference to the specific software code.
As used herein, meeting a threshold may refer to the following values depending on the context: greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc.
Although specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim of the claim sets. As used herein, a phrase referring to "at least one" in a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to cover: a. b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with a plurality of the same elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items associated with the article "the" and may be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more. Where only one item is meant, the phrase "only one" or similar language is used. Also, as used herein, the terms "have", "possess", or the like are intended to be open-ended terms that do not limit the elements they modify (e.g., elements having a may also have B). Furthermore, unless explicitly stated otherwise, the phrase "based on" is intended to mean "based, at least in part, on". Furthermore, as used herein, the term "or" is intended to be used in a series unless explicitly stated otherwise (e.g., if "or" only one ") is intended to be inclusive and used interchangeably with" and/or ".

Claims (30)

1. A mobile station for wireless communication, comprising:
a memory; and
one or more processors coupled to the memory configured to: based at least in part on the information stored in the memory, performing the following:
transmitting a Physical Uplink Shared Channel (PUSCH); and
receiving Downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more Physical Downlink Control Channel (PDCCH) candidates in a set of PDCCH candidates,
wherein the set of PDCCH candidates is linked for PDCCH repetition; and is also provided with
Wherein the mobile station determines whether feedback information for transport blocks of a respective hybrid automatic repeat request (HARQ) process number in the DFI is valid for transmission of the PUSCH based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols preceding a first symbol of a PDCCH candidate in the set of PDCCH candidates.
2. The mobile station of claim 1, wherein the DCI is associated with a DCI format 0_1 and a Cyclic Redundancy Check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), and wherein a DFI flag field of the DCI is set to a first value indicating that the DCI includes the DFI.
3. The mobile station of claim 1, wherein the PDCCH candidate starts earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
4. The mobile station of claim 1, wherein the PDCCH candidate starts latest in time relative to other PDCCH candidates in the set of PDCCH candidates.
5. The mobile station of claim 1, wherein the PDCCH candidate ends earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
6. The mobile station of claim 1, wherein the PDCCH candidate ends last in time relative to other PDCCH candidates in the set of PDCCH candidates.
7. The mobile station of claim 1, wherein the one or more processors are further configured to: based at least in part on the information stored in the memory, performing the following:
the PDCCH candidate is identified as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria.
8. The mobile station of claim 7, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate beginning earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
9. A method of wireless communication performed by a mobile station, comprising:
transmitting a Physical Uplink Shared Channel (PUSCH); and
receiving, by the mobile station, downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more Physical Downlink Control Channel (PDCCH) candidates in a set of PDCCH candidates,
wherein the set of PDCCH candidates is linked for PDCCH repetition; and is also provided with
Wherein the mobile station determines whether feedback information for transport blocks of a respective hybrid automatic repeat request (HARQ) process number in the DFI is valid for transmission of the PUSCH based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols before a first symbol of a PDCCH candidate in the set of PDCCH candidates.
10. The method of claim 9, wherein the DCI is associated with a DCI format 0_1 and a Cyclic Redundancy Check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), and wherein a DFI flag of the DCI is set to a first value indicating that the DCI includes the DFI.
11. The method of claim 9, wherein the PDCCH candidate starts earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
12. The method of claim 9, wherein the PDCCH candidate starts latest in time relative to other PDCCH candidates in the set of PDCCH candidates.
13. The method of claim 9, wherein the PDCCH candidate ends earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
14. The method of claim 9, wherein the PDCCH candidate ends last in time relative to other PDCCH candidates in the set of PDCCH candidates.
15. The method of claim 9, further comprising:
the PDCCH candidate is identified as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria.
16. The method of claim 15, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate beginning earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
17. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a mobile station, cause the mobile station to:
Transmitting a Physical Uplink Shared Channel (PUSCH); and
receiving Downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more Physical Downlink Control Channel (PDCCH) candidates in a set of PDCCH candidates,
wherein the set of PDCCH candidates is linked for PDCCH repetition; and is also provided with
Wherein the mobile station determines whether feedback information for transport blocks of a respective hybrid automatic repeat request (HARQ) process number in the DFI is valid for transmission of the PUSCH based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols before a first symbol of a PDCCH candidate in the set of PDCCH candidates.
18. The non-transitory computer-readable medium of claim 17, wherein the DCI is associated with a DCI format 0_1 and a Cyclic Redundancy Check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), and wherein a DFI flag of the DCI is set to a first value indicating that the DCI includes the DFI.
19. The non-transitory computer-readable medium of claim 17, wherein the PDCCH candidate starts earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
20. The non-transitory computer-readable medium of claim 17, wherein the PDCCH candidate starts last in time relative to other PDCCH candidates in the set of PDCCH candidates.
21. The non-transitory computer-readable medium of claim 17, wherein the PDCCH candidate ends earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
22. The non-transitory computer-readable medium of claim 17, wherein the PDCCH candidate ends last in time relative to other PDCCH candidates in the set of PDCCH candidates.
23. The non-transitory computer-readable medium of claim 17, wherein the one or more instructions, when executed by one or more processors of a mobile station, further cause the mobile station to:
the PDCCH candidate is identified as a reference PDCCH candidate based at least in part on the PDCCH candidate meeting one or more criteria.
24. The non-transitory computer-readable medium of claim 17, wherein the PDCCH candidate meets the one or more criteria based at least in part on the PDCCH candidate beginning earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
25. An apparatus for wireless communication, comprising:
a unit for transmitting a Physical Uplink Shared Channel (PUSCH); and
means for receiving Downlink Control Information (DCI) carrying Downlink Feedback Information (DFI) among one or more Physical Downlink Control Channel (PDCCH) candidates in a set of PDCCH candidates,
wherein the set of PDCCH candidates is linked for PDCCH repetition; and is also provided with
Wherein the apparatus determines whether feedback information for transport blocks of a respective hybrid automatic repeat request (HARQ) process number in the DFI is valid for transmission of the PUSCH based at least in part on whether a last symbol of the PUSCH transmission is at least a particular number of symbols before a first symbol of a PDCCH candidate in the set of PDCCH candidates.
26. The apparatus of claim 25, wherein the DCI is associated with a DCI format 0_1 and a Cyclic Redundancy Check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), and wherein a DFI flag of the DCI is set to a first value indicating that the DCI includes the DFI.
27. The apparatus of claim 25, wherein the PDCCH candidate starts earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
28. The apparatus of claim 25, wherein the PDCCH candidate starts latest in time relative to other PDCCH candidates in the set of PDCCH candidates.
29. The apparatus of claim 25, wherein the PDCCH candidate ends earliest in time relative to other PDCCH candidates in the set of PDCCH candidates.
30. The apparatus of claim 25, wherein the PDCCH candidate ends last in time relative to other PDCCH candidates in the set of PDCCH candidates.
CN202280058644.9A 2021-10-13 2022-08-31 Downlink feedback information with physical downlink control channel repetition Pending CN117897919A (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US63/262,486 2021-10-13
US17/813,507 US20230114685A1 (en) 2021-10-13 2022-07-19 Downlink feedback information with physical downlink control channel repetition
US17/813,507 2022-07-19
PCT/US2022/075733 WO2023064650A1 (en) 2021-10-13 2022-08-31 Downlink feedback information with physical downlink control channel repetition

Publications (1)

Publication Number Publication Date
CN117897919A true CN117897919A (en) 2024-04-16

Family

ID=90641709

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202280058644.9A Pending CN117897919A (en) 2021-10-13 2022-08-31 Downlink feedback information with physical downlink control channel repetition

Country Status (1)

Country Link
CN (1) CN117897919A (en)

Similar Documents

Publication Publication Date Title
US20220039141A1 (en) Downlink control information size configuration for multiple carrier scheduling scenarios
CN116134916A (en) Transmitting resource conflict indication on side-uplink feedback channel
CN116137965A (en) Downlink control information size configuration in a cross-carrier scheduling scenario
CN116195219A (en) Multicast downlink control information configuration
US11882577B2 (en) Physical downlink control channel candidates aggregated over different numbers of monitoring occasions
CN115152171B (en) Parameter determination for user equipment
CN117716647A (en) Request for cancelled hybrid automatic repeat request codebook
CN118104340A (en) Capability compatibility for paging subgroups
CN117837248A (en) Bandwidth portion specific downlink-uplink mode
CN117280824A (en) HARQ acknowledgement for semi-persistent scheduling release of downlink control information
CN117652184A (en) Relative power setting between different cells in dual connectivity or carrier aggregation
CN116391340A (en) Uplink control information reporting
CN115606128A (en) Physical uplink control channel transmission for low latency communication deployments
US20230114685A1 (en) Downlink feedback information with physical downlink control channel repetition
CN117897919A (en) Downlink feedback information with physical downlink control channel repetition
US20230045695A1 (en) Transmission of a hybrid automatic repeat request acknowledgment codebook
US20230061324A1 (en) Dynamic guard band signaling for full-duplex communications
US20220312454A1 (en) User equipment processing time for physical downlink shared channel scheduled using downlink control information repetition
US20220394747A1 (en) Search space sharing for cross-carrier scheduling
WO2023064650A1 (en) Downlink feedback information with physical downlink control channel repetition
CN117730499A (en) Transmission of hybrid automatic repeat request acknowledgement codebook
WO2023015140A1 (en) Transmission of a hybrid automatic repeat request acknowledgment codebook
EP4381650A1 (en) Transmission of a hybrid automatic repeat request acknowledgment codebook
CN117813791A (en) Feedback transmission on uplink resources of bandwidth part
CN117882482A (en) Resource conflict indication for side link resources

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination