WO2024011437A1 - Répétitions de canal physique de liaison descendante dans des sous-bandes - Google Patents

Répétitions de canal physique de liaison descendante dans des sous-bandes Download PDF

Info

Publication number
WO2024011437A1
WO2024011437A1 PCT/CN2022/105342 CN2022105342W WO2024011437A1 WO 2024011437 A1 WO2024011437 A1 WO 2024011437A1 CN 2022105342 W CN2022105342 W CN 2022105342W WO 2024011437 A1 WO2024011437 A1 WO 2024011437A1
Authority
WO
WIPO (PCT)
Prior art keywords
physical downlink
frequency hopping
downlink channel
repetitions
configuration
Prior art date
Application number
PCT/CN2022/105342
Other languages
English (en)
Inventor
Hung Dinh LY
Yongjun Kwak
Kexin XIAO
Original Assignee
Qualcomm Incorporated
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
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2022/105342 priority Critical patent/WO2024011437A1/fr
Publication of WO2024011437A1 publication Critical patent/WO2024011437A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/0012—Hopping in multicarrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for physical uplink channel repetitions in subbands.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) .
  • multiple-access technologies 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 (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs.
  • a UE may communicate with a base station via downlink communications and uplink communications.
  • Downlink (or “DL” ) refers to a communication link from the base station to the UE
  • uplink (or “UL” ) refers to a communication link from the UE to the base station.
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP- OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple-input multiple-output
  • the method may include receiving a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the method may include receiving the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the method may include transmitting a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the method may include transmitting physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the UE may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to receive a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the one or more processors may be configured to receive the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the network entity may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to transmit a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the one or more processors may be configured to transmit physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity.
  • the set of instructions when executed by one or more processors of the network entity, may cause the network entity to transmit a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the set of instructions when executed by one or more processors of the network entity, may cause the network entity to transmit physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the apparatus may include means for receiving a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the apparatus may include means for receiving the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the apparatus may include means for transmitting a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the apparatus may include means for transmitting physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • 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 equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices) .
  • Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
  • Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) .
  • RF radio frequency
  • aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
  • Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
  • Fig. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • Fig. 3 is a diagram illustrating an example of a single downlink control information (DCI) scheduling multiple physical uplink channel communications, in accordance with the present disclosure.
  • DCI downlink control information
  • Fig. 4 is a diagram illustrating examples of frequency hopping for physical channel repetition, in accordance with the present disclosure.
  • Fig. 5 is a diagram illustrating examples of frequency hopping for physical channel repetition, in accordance with the present disclosure.
  • Fig. 6 is a diagram illustrating examples of frequency domain resource allocations, in accordance with the present disclosure.
  • Fig. 7 is a diagram illustrating an example of frequency hopping with subbands of a bandwidth part, in accordance with the present disclosure.
  • Fig. 8 is a diagram illustrating examples of switching time gaps, in accordance with the present disclosure.
  • Fig. 9 is a diagram illustrating an example of intra-slot frequency hopping, in accordance with the present disclosure.
  • Fig. 10 is a diagram illustrating an example of paired repetitions, in accordance with the present disclosure.
  • Fig. 11 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.
  • Fig. 12 is a diagram illustrating an example process performed, for example, by a network entity, in accordance with the present disclosure.
  • Figs. 13-14 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.
  • Fig. 15 is a diagram illustrating an example of a disaggregated base station, in accordance with the present disclosure.
  • NR New Radio
  • RAT radio access technology
  • Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples.
  • the wireless network 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110b, a BS 110c, and a BS 110d) , a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and/or other network entities.
  • UE user equipment
  • a base station 110 is an entity that communicates with UEs 120.
  • a base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G) , a gNB (e.g., in 5G) , an access point, and/or a transmission reception point (TRP) .
  • Each base station 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a base station 110 and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.
  • a base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a 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 restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) .
  • CSG closed subscriber group
  • a base station 110 for a macro cell may be referred to as a macro base station.
  • a base station 110 for a pico cell may be referred to as a pico base station.
  • a base station 110 for a femto cell may be referred to as a femto base station or an in-home base station.
  • the BS 110a may be a macro base station for a macro cell 102a
  • the BS 110b may be a pico base station for a pico cell 102b
  • the BS 110c may be a femto base station for a femto cell 102c.
  • a base station may support one or multiple (e.g., three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station) .
  • the base stations 110 may be interconnected to one another and/or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
  • base station e.g., the base station 110 or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof.
  • base station or “network entity” may refer to a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, or a combination thereof.
  • the term “base station” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110.
  • the term “base station” or “network entity” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station” or “network entity” may refer to any one or more of those different devices.
  • base station or “network entity” may refer to one or more virtual base stations and/or one or more virtual base station functions.
  • two or more base station functions may be instantiated on a single device.
  • base station or “network entity” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110) .
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the BS 110d e.g., a relay base station
  • the BS 110a e.g., a macro base station
  • a base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100.
  • macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • a network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110.
  • the network controller 130 may communicate with the base stations 110 via a backhaul communication link.
  • the base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (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, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet) ) , an entertainment device (e.g., a music device, a video device, and/or a satellite radio)
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network entity (e.g., base station 110) , 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 a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
  • UEs may be of different categories for different capabilities.
  • a network entity may serve a first category of UEs that have a less advanced capability (e.g., a lower capability and/or a reduced capability) and a second category of UEs that have a more advanced capability (e.g., a higher capability) .
  • a UE of the first category may have a reduced feature set compared to UEs of the second category, and may be referred to as a reduced capability (RedCap) UE, a low tier UE, NR-Light UE, and/or an NR-Lite UE, among other examples.
  • RedCap reduced capability
  • a UE of the first category may be, for example, industrial wireless sensors, low-end smartphones, health monitors, video surveillance, high-end wearables, MTC devices, and/or high-end logistic trackers.
  • UEs of the first category may be associated with 3GPP Release 17.
  • a UE of the second category may have an advanced feature set compared to UEs of the first category, and may be referred to as a baseline UE, a high tier UE, an NR UE, and/or a premium UE, among other examples.
  • a UE of the second category may include enhanced mobile broadband (eMBB) devices, ultra-reliable low latency communication (URLLC) devices, extended reality (XR) devices, laptops, robots, industrial machines, and/or high-end smartphones.
  • UEs of the second category may be associated with 3GPP Release 15 and onwards.
  • a UE of the first category has capabilities that satisfy requirements of a first (earlier) wireless communication standard but not a second (later) wireless communication standard
  • a UE of the second category has capabilities that satisfy requirements of the second (later) wireless communication standard (and also the first wireless communication standard, in some cases) .
  • UEs of the first category may support a lower maximum modulation and coding scheme (MCS) than UEs of the second category (e.g., quadrature phase shift keying (QPSK) or the like as compared to 256-quadrature amplitude modulation (QAM) or the like) , may support a lower maximum transmit power than UEs of the second category, may have a less advanced beamforming capability than UEs of the second category (e.g., may not be capable of forming as many beams as UEs of the second category) , may require a longer processing time than UEs of the second category, may include less hardware than UEs of the second category (e.g., fewer antennas, fewer transmit antennas, and/or fewer receive antennas) , and/or may not be capable of communicating on as wide of a maximum bandwidth part as UEs of the second category, among other examples.
  • MCS modulation and coding scheme
  • QPSK quadrature phase shift keying
  • QAM quadrat
  • UEs of the second category may be capable of communicating using a shortened transmission time interval (TTI) (e.g., a slot length of 1 ms or less, 0.5 ms, 0.25 ms, 0.125 ms, 0.0625 ms, or the like, depending on a sub-carrier spacing) , and UEs of the first category may not be capable of communicating using the shortened TTI.
  • TTI transmission time interval
  • eRedCap enhanced RedCap
  • NR-Superlight devices may include eMTC devices, and/or NB-IoT devices in associated with 3GPP Release 18 and/or massive IoT.
  • UEs of the third category may include, for example, low-end industrial sensors, parking sensors, agricultural sensors, utility meters, low-end wearables, and/or low-end asset trackers.
  • UE capabilities of the first category differ from UE capabilities of the second category.
  • UE capabilities of the third category may differ from UE capabilities of the first category and the second category.
  • 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.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (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.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz –24.25 GHz
  • FR3 7.125 GHz –24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR4 52.6 GHz –114.25 GHz
  • FR5 114.25 GHz –300 GHz
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may receive a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the communication manager 140 may receive the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • a network entity may include a communication manager 150.
  • the communication manager 150 may transmit a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the communication manager 150 may transmit physical downlink channel repetitions across the multiple subbands based at least in part on the configuration. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ⁇ 1) .
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ⁇ 1) .
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) .
  • the transmit processor 220 may select one or more MCSs for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • the base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120.
  • the 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 reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) .
  • reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals 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) , shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) , shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the 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.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a 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 other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the network controller 130 may include, for example, one or more devices in a core network.
  • the network controller 130 may communicate with the base station 110 via the communication unit 294.
  • One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the base station 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 7-14) .
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the 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.
  • the base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the base station 110 may include a modulator and a demodulator.
  • the base station 110 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 7-14) .
  • the controller/processor 240 of a network entity e.g., base station 110
  • the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with physical uplink channel repetitions in subbands, as described in more detail elsewhere herein.
  • the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 1100 of Fig. 11, process 1200 of Fig. 12, and/or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively.
  • the memory 242 and/or the 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.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the base station 110 to perform or direct operations of, for example, process 1100 of Fig. 11, process 1200 of Fig. 12, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • the UE 120 includes means for receiving a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands; and/or means for receiving the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the means for the UE 120 to perform operations described herein may include, 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.
  • a network entity (e.g., base station 110) includes means for transmitting a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands; and/or means for transmitting physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the means for the network entity to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3 is a diagram illustrating an example 300 of capabilities for different types of UEs, in accordance with the present disclosure.
  • Example 300 shows a comparison of UE communication features for an NB-IOT device, an eMTC device, a Release 16 NR eMBB device, a Release 17 NR RedCap (NR Light) device, and a Release 18 NR Superlight device.
  • Such features include a UE bandwidth (BW) , a duplex capability, a quantity of antennas, MIMO layers, peak data rates, a maximum coupling loss (MCL) , channel coding, a modulation order, and/or other features.
  • an eRedCap UE may operate with a bandwidth limitation, such as 5 MHz with 25 physical resource blocks (PRBs) and a 15 KHz subcarrier spacing (SCS) for FR1. There may be limited reuse of the bandwidth for a synchronization signal block (SSB) . For example, there may be limited reuse of synchronization signals, a physical broadcast channel (PBCH) , and control resource set (CORESET) #0 with a 15 KHz SCS. 24 PRBs with a 15 KHz SCS can be reused for CORESET#0.
  • PRBs physical resource blocks
  • SCS subcarrier spacing
  • SSB synchronization signal block
  • PBCH physical broadcast channel
  • CORESET control resource set
  • Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
  • Fig. 4 is a diagram illustrating examples 400 and 402 of frequency hopping for physical channel repetition, in accordance with the present disclosure.
  • a single downlink control information is able to schedule multiple physical downlink shared channel (PDSCH) communications or multiple physical uplink shared channel (PUSCH) communications with different transport blocks (TBs) , as shown by example 300.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • TBs transport blocks
  • Each PDSCH or PUSCH may have its own TB and duration, confined within a slot.
  • Each TB may have its own hybrid automatic repeat request (HARQ) process identifier (ID) , redundancy version ID (RVID) , new data indicator (NDI) , time domain resource allocation (TDRA) , and/or frequency domain resource allocation (FDRA) .
  • ID hybrid automatic repeat request
  • RVID redundancy version ID
  • NDI new data indicator
  • TDRA time domain resource allocation
  • FDRA frequency domain resource allocation
  • a UE when receiving a PDSCH communication (data) scheduled by DCI, a UE may be configured for slot aggregation, where a TB can be repeated over multiple slots (or mini-slots) .
  • the quantity of allocated symbols, or the start and length indicator (SLIV) for all the consecutive slots may be the same as the first slot.
  • the transmitter may sequentially read the coded bits from the data buffer based on a specified RV order.
  • the PDSCH may be limited to a single layer.
  • a control channel element (CCE) aggregation level (AL) for physical downlink control channel (PDCCH) frequency diversity may be between 1 and 16 for 6 to 96 PRBs in one OFDM symbol if the SCS is 15 kilohertz (kHz) .
  • An NR UE CORESET may be in a maximum of 3 symbols in the time domain and a multiple of 6 resource blocks (RBs) in the frequency domain.
  • a resource element group (REG) may be 1 symbol ⁇ 1 RB, and a control channel element (RE for control information) may be equal to 6 REGs.
  • REG resource element group
  • RE for control information may be equal to 6 REGs.
  • An eRedcap UE CORESET for 5 MHz with a 15 or 30 KHz SCS may have up to 12 or 6 CCEs in a CORESET (with 3 OFDM symbols) .
  • An AL 16 with 15 KHz and an AL 8 for 30 KHz SCS may not be allowed.
  • a PDCCH configuration may include parameters for a CORESET. Such parameters may include frequency domain resources within a bandwidth part (BWP) that are assigned to the UE and a duration (e.g., quantity of symbols) of the CORESET.
  • the PDCCH configuration may also include parameters for a search space. Such parameters may include a CORESET ID, a PDCCH monitoring periodicity and offset, and/or symbols for PDCCH monitoring in slots configured for PDCCH monitoring.
  • Some UEs such as 3GPP Release 15 NR UEs or Release 16 NR UEs, may use multi-slot aggregation (e.g., multiple slot repetition in the time domain with an aggregation factor for PDSCH of 2, 4, or 8 consecutive slots) but not downlink frequency hopping.
  • multi-slot aggregation e.g., multiple slot repetition in the time domain with an aggregation factor for PDSCH of 2, 4, or 8 consecutive slots
  • an eRedcap UE may have a limited maximum bandwidth of 5 MHz, while a RedCap UE or a regular UE may have a much higher maximum bandwidth.
  • the baseband bandwidth for the eRedCap UE may be limited to 5 MHz (for reducing the UE peak data rate and buffer size) .
  • an eRedCap UE may use repetition and frequency hopping for the PDSCH and the PDCCH. This may include inter-slot frequency hopping for PDSCH repetitions, intra-slot frequency hopping for the PDSCH, PDCCH repetition with frequency hopping, and/or PDCCH and PDSCH pair with frequency hopping.
  • the PDSCH repetition includes repetition of a TB on a PDSCH.
  • the PDSCH repetition may be of one type (e.g., Type A) .
  • Two frequency hopping modes include intra-slot frequency hopping (applicable to single slot and multi-slot PDSCH communication) and inter-slot frequency hopping (applicable to multi-slot PDSCH communication) .
  • Example 400 shows an example of intra-slot frequency hopping.
  • the quantity of symbols in the first hop may be given by half of a total length of a PDSCH reception in one slot, and the quantity of symbols in the second hop may be the other half of the total length.
  • the hopping boundary for a PDSCH repetition is within each slot.
  • Example 402 shows an example of inter-slot frequency hopping.
  • the hopping boundary for a PDSCH repetition is at a slot boundary.
  • Fig. 4 provides some examples. Other examples may differ from what is described with regard to Fig. 4.
  • Fig. 5 is a diagram illustrating examples 500 and 502 of frequency hopping for physical downlink channel repetition, in accordance with the present disclosure.
  • PDSCH repetition may be of another type (e.g., Type B) .
  • Frequency hopping modes may include inter-repetition frequency hopping and inter-slot frequency hopping.
  • Example 500 shows an example of inter-repetition frequency hopping.
  • the hopping boundary is between PDSCH repetitions.
  • the hopping boundary may be within a slot.
  • a nominal repetition may span a slot boundary while actual repetitions may be separated by the slot boundary.
  • Example 502 shows an example of inter-slot frequency hopping.
  • the hopping boundary for a PDSCH repetition is at a slot boundary. Actual repetitions may be separated by the slot boundary.
  • the frequency hopping types of Figs. 4 and 5 may also apply to PDCCH repetition, PUSCH repetition, and/or physical uplink control channel (PUCCH) repetition.
  • PDCCH Physical uplink control channel
  • Fig. 5 provides some examples. Other examples may differ from what is described with regard to Fig. 5.
  • Fig. 6 is a diagram illustrating examples 600 and 602 of frequency domain resource allocations, in accordance with the present disclosure.
  • Legacy UEs and eRedCap UEs may coexist in the same BWP.
  • Example 600 shows a legacy BWP bandwidth of 20 MHz for RedCap UEs and Regular UEs.
  • a UE may be configured for PDCCH repetitions or PDSCH repetitions within an active BWP that is divided into multiple subbands. The UE may receive the PDCCH repetitions or PDSCH repetitions across the multiple subbands.
  • Example 602 shows multiple subbands of 5 MHz within an active downlink BWP of 20 MHz to account for the 5 MHz maximum bandwidth limitation for eRedCap UEs.
  • a start location for a first of the subbands may be determined with respect to the PRB 0 of the BWP and based on the SCS of the BWP.
  • Other subbands may start based on an FDRA start offset.
  • the start offset based at least in part on the maximum UE bandwidth.
  • the offset k may be k*N rb , where N rb is the quantity of RBs in a maximum UE bandwidth.
  • a subband may be valid if the subband includes a specified or predefined quantity of RBs (e.g., N rb ) .
  • the start of an FDRA for downlink reception may be the first RB in a valid subband.
  • Fig. 6 is provides some examples. Other examples may differ from what is described with regard to Fig. 6.
  • Fig. 7 is a diagram illustrating an example 700 of frequency hopping with subbands of a BWP, in accordance with the present disclosure.
  • a network entity 710 e.g., base station 110
  • a UE 720 e.g., a UE 120
  • a wireless network e.g., wireless network 100
  • Example 700 shows that the network entity 710 may configure the UE 720 for physical downlink channel (e.g., PDSCH, PDCCH) repetitions in a BWP that is divided into subbands. As shown by reference number 725, the network entity 710 may transmit such a configuration.
  • the configuration may specify a bandwidth size (e.g., 5 MHz) for each subband.
  • a separate indication e.g., radio resource control (RRC) message or DCI
  • RRC radio resource control
  • a specified rule e.g., subbands with highest or lowest indices
  • Example 700 shows a bandwidth divided into 4 subbands, each with a bandwidth of 5 MHz.
  • Example 700 shows PDSCH repetition with an aggregation factor (quantity of repetitions) of 2.
  • the UE 720 may receive a frequency hopping indication that indicates that frequency hopping is to be performed for reception of PDSCH repetitions or PDCCH repetitions.
  • the indication may include a frequency hopping flag, and the indication may be received in an RRC message or in DCI.
  • the indication may indicate intra-slot frequency hopping or inter-slot frequency hopping.
  • Example 700 shows inter-slot frequency hopping.
  • the UE 720 may receive a first PDSCH repetition for a TB on a first frequency hop in subband 0 at slot n.
  • the UE 720 may receive a second PDSCH repetition for the TB on a second frequency hop in subband 3 at slot n + 1.
  • One DCI may schedule multiple consecutive downlink slots for the PDSCH.
  • PDSCH repetition received in different slots may have the same TDRA but different subbands.
  • the UE 720 may maintain the same relative RB location within the subband after hopping.
  • a subband for a repetition may be based at least in part on a slot index. For example, the UE 720 may use the subband with the lowest index for an odd slot and use the subband with the highest index for an even slot. In example 700, the UE 720 does not perform frequency hopping within a subband.
  • Fig. 7 is provided as an example. Other examples may differ from what is described with regard to Fig. 7.
  • Fig. 8 is a diagram illustrating examples 800 and 802 of switching time gaps, in accordance with the present disclosure.
  • the UE 720 may introduce a switching time gap for switching between different subbands when frequency hopping between subbands.
  • a switching time gap 804 is configured as one or more symbols at a beginning of a slot after a frequency hop.
  • a switching time gap 806 is configured as one or more symbols at an end of a slot before a frequency hop.
  • the time switching gap may be specified or configured via a system information block (SIB1) . If the switching time gap overlaps with a PDSCH transmission, those symbols may be punctured in the PDSCH or rate matched to the PDSCH. Puncturing includes not assigning data to the punctured symbols. Rate matching may match data of layers to symbols and may not assign data to the symbols for the time switching gap.
  • SIB1 system information block
  • Fig. 8 is provides some examples. Other examples may differ from what is described with regard to Fig. 8.
  • Fig. 9 is a diagram illustrating an example 900 of intra-slot frequency hopping, in accordance with the present disclosure.
  • the UE 720 may perform intra-slot frequency hopping across different subbands for PDSCH.
  • the network entity 710 may indicate (e.g., via a frequency hopping flag) intra-slot PDSCH frequency hopping across multiple subbands in an RRC message or in DCI.
  • the UE 720 may determine subbands for frequency hops.
  • the first frequency hop may be the first valid subband, or a valid subband configured to the UE 720.
  • the quantity of frequency hops (e.g., 2 hops) may be specified or configured by the network entity 710.
  • a switching time gap may be used between frequency hops.
  • the network entity 710 may use a new field not previously used or reuse a reserved bit in an RRC message or in DCI format 1_0 or DCI format 1_1 to indicate the frequency hopping.
  • the UE 720 may interpret the new field to enable intra-slot frequency hopping when PDSCH aggregation is not configured via RRC signaling.
  • the UE 720 may interpret the new field to enable inter-slot frequency hopping when PDSCH aggregation is configured via RRC signaling. If the new field is not indicated, no frequency hopping is configured. Intra-slot frequency hopping and inter-slot frequency hopping may not be simultaneously supported.
  • the network entity 710 may transmit PDSCH repetitions in one subband that may be predefined (e.g., subband with lowest index or highest index) or correspond to the first or second frequency hop determination or indication via RRC.
  • the network entity 710 may enable the UE 720 to make efficient use of maximum bandwidth limitations for eRedCap UEs or similar types of UEs. While the described examples involve PDSCH, the aspects described herein may also be applicable to PDCCH.
  • Fig. 9 is provided as an example. Other examples may differ from what is described with regard to Fig. 9.
  • Fig. 10 is a diagram illustrating an example 1000 of paired repetitions, in accordance with the present disclosure.
  • PDCCH and PDSCH may be repeated as a pair. If PDCCH frequency hopping is configured, PDSCH frequency hopping may be configured to follow the PDCCH in the same subband.
  • Example 1000 shows a first PDCCH/PDSCH pair and one switching time gap before a second PDCCH/PDSCH pair. In this way, there is one switching time gap rather than 3 switching time gaps.
  • Fig. 10 is provided as an example. Other examples may differ from what is described with regard to Fig. 10.
  • Fig. 11 is a diagram illustrating an example process 1100 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 1100 is an example where the UE (e.g., a UE 120, UE 720) performs operations associated with physical downlink channel (e.g., PDCCH, PDSCH) repetitions in subbands.
  • the UE e.g., a UE 120, UE 720
  • PDCCH Physical downlink channel
  • process 1100 may include receiving a configuration for physical downlink channel repetitions within an active BWP that is divided into multiple subbands (block 1110) .
  • the UE e.g., using communication manager 1308 and/or reception component 1302 depicted in Fig. 13
  • process 1100 may include receiving the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration (block 1120) .
  • the UE e.g., using communication manager 1308 and/or reception component 1302 depicted in Fig. 13
  • Process 1100 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.
  • the configuration specifies a bandwidth size for each subband.
  • the bandwidth size is less than or equal to half of the active BWP (e.g., 5 MHz) .
  • the configuration or an indication in a message specifies the multiple subbands.
  • a subband used for a physical downlink channel repetition is based on a slot index.
  • receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions across subbands and with a same time domain resource allocation.
  • process 1100 includes receiving a frequency hopping indication, and receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • the frequency hopping includes inter-slot frequency hopping.
  • the frequency hopping includes intra-slot frequency hopping.
  • the frequency hopping indication specifies intra-slot frequency hopping across the multiple subbands.
  • the configuration indicates a switching time gap for the frequency hopping.
  • the switching time gap includes one or more symbols at a beginning of a slot after a frequency hop.
  • the one or more symbols are punctured or rate matched based at least in part on the switching time gap overlapping with a physical downlink channel transmission.
  • the switching time gap includes one or more symbols at an end of a slot before a frequency hop.
  • process 1100 includes receiving a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • the frequency hopping indication indicates intra-slot frequency hopping in response to the UE not being configured for downlink channel aggregation.
  • the frequency hopping indication indicates inter-slot frequency hopping in response to the UE being configured for downlink channel aggregation.
  • the configuration or a message indicates no frequency hopping within a subband.
  • the physical downlink channel repetitions include one or more of physical downlink control channel repetitions or physical downlink shared channel repetitions.
  • receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions with frequency hopping of PDSCH repetitions and PDCCH repetitions, and a PDSCH repetition follows a PDCCH repetition in a subband of each slot of multiple slots.
  • process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
  • Fig. 12 is a diagram illustrating an example process 1200 performed, for example, by a network entity, in accordance with the present disclosure.
  • Example process 1200 is an example where the network entity (e.g., base station 110, network entity 710) performs operations associated with physical downlink channel repetitions in subbands.
  • the network entity e.g., base station 110, network entity 710 performs operations associated with physical downlink channel repetitions in subbands.
  • process 1200 may include transmitting a configuration for physical downlink channel repetition with an active BWP that is divided into multiple subbands (block 1210) .
  • the network entity e.g., using communication manager 1408 and/or transmission component 1404 depicted in Fig. 14
  • process 1200 may include transmitting physical downlink channel repetitions across the multiple subbands based at least in part on the configuration (block 1220) .
  • the network entity e.g., using communication manager 1408 and/or transmission component 1404 depicted in Fig. 14
  • Process 1200 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.
  • the configuration specifies a bandwidth size for each subband.
  • process 1200 includes transmitting a frequency hopping indication, and transmitting the physical downlink channel repetitions includes transmitting the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • the configuration indicates a switching time gap for the frequency hopping.
  • process 1200 includes puncturing or rate matching one or more symbols based at least in part on the switching time gap overlapping with a physical downlink channel transmission.
  • process 1200 includes transmitting a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • the frequency hopping indication indicates intra-slot frequency hopping based on a configuration for downlink channel aggregation.
  • the frequency hopping indication indicates inter-slot frequency hopping based on a configuration for downlink channel aggregation.
  • the configuration or a message indicates no frequency hopping within a subband.
  • transmitting the physical downlink channel repetitions includes transmitting the physical downlink channel repetitions with frequency hopping of PDSCH repetitions and PDCCH repetitions, and a PDSCH repetition follows a PDCCH repetition in a subband of each slot of multiple slots.
  • process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
  • Fig. 13 is a diagram of an example apparatus 1300 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1300 may be a UE (e.g., a UE 120, UE 720) , or a UE may include the apparatus 1300.
  • the apparatus 1300 includes a reception component 1302 and a transmission component 1304, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the reception component 1302 and the transmission component 1304.
  • the apparatus 1300 may include the communication manager 1308.
  • the communication manager 1308 may control and/or otherwise manage one or more operations of the reception component 1302 and/or the transmission component 1304.
  • the communication manager 1308 may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the communication manager 1308 may be, or be similar to, the communication manager 140 depicted in Figs. 1 and 2.
  • the communication manager 1308 may be configured to perform one or more of the functions described as being performed by the communication manager 140.
  • the communication manager 1308 may include the reception component 1302 and/or the transmission component 1304.
  • the communication manager 1308 may include a hopping component 1310, among other examples.
  • the apparatus 1300 may be configured to perform one or more operations described herein in connection with Figs. 1-10. Additionally, or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 1100 of Fig. 11.
  • the apparatus 1300 and/or one or more components shown in Fig. 13 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 13 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a 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 a processor to perform the functions or operations of the component.
  • the reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1306.
  • the reception component 1302 may provide received communications to one or more other components of the apparatus 1300.
  • the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1300.
  • the reception component 1302 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1306.
  • one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1306.
  • the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1306.
  • the transmission component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1304 may be co-located with the reception component 1302 in a transceiver.
  • the reception component 1302 may receive a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands.
  • the hopping component 1310 may perform frequency hopping for receiving the physical downlink channel repetitions.
  • the reception component 1302 may receive the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the reception component 1302 may receive a frequency hopping indication, and receive the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • the reception component 1302 may receive a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • Fig. 13 The number and arrangement of components shown in Fig. 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 13. Furthermore, two or more components shown in Fig. 13 may be implemented within a single component, or a single component shown in Fig. 13 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 13 may perform one or more functions described as being performed by another set of components shown in Fig. 13.
  • Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1400 may be a network entity (e.g., base station 110, network entity 710) , or a network entity may include the apparatus 1400.
  • the apparatus 1400 includes a reception component 1402 and a transmission component 1404, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using the reception component 1402 and the transmission component 1404.
  • the apparatus 1400 may include the communication manager 1408.
  • the communication manager 1408 may control and/or otherwise manage one or more operations of the reception component 1402 and/or the transmission component 1404.
  • the communication manager 1408 may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig. 2.
  • the communication manager 1408 may be, or be similar to, the communication manager 150 depicted in Figs. 1 and 2.
  • the communication manager 1408 may be configured to perform one or more of the functions described as being performed by the communication manager 150.
  • the communication manager 1408 may include the reception component 1402 and/or the transmission component 1404.
  • the communication manager 1408 may include a configuration component 1410, among other examples.
  • the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 1-10. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12.
  • the apparatus 1400 and/or one or more components shown in Fig. 14 may include one or more components of the network entity described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a 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 a processor to perform the functions or operations of the component.
  • the reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1406.
  • the reception component 1402 may provide received communications to one or more other components of the apparatus 1400.
  • the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1400.
  • the reception component 1402 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig. 2.
  • the transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1406.
  • one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1406.
  • the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1406.
  • the transmission component 1404 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in a transceiver.
  • the transmission component 1404 may transmit a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands.
  • the configuration component 1410 may generate the configuration based at least in part on a UE capability, traffic conditions, and/or channel conditions.
  • the transmission component 1404 may transmit physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • the transmission component 1404 may transmit a frequency hopping indication and transmit the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • the transmission component 1404 may puncture or rate matching one or more symbols based at least in part on the switching time gap overlapping with a physical downlink channel transmission.
  • the transmission component 1404 may transmit a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • Fig. 14 The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.
  • Fig. 15 is a diagram illustrating an example of a disaggregated base station 1500, in accordance with the present disclosure.
  • a network node such as a Node B, evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a TRP, or a cell, etc.
  • a BS such as a Node B, evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a TRP, or a cell, etc.
  • eNB evolved NB
  • AP access point
  • TRP Transmission Retention Protocol
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs) .
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units (e.g., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) ) .
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) .
  • O-RAN open radio access network
  • vRAN virtualized radio access network
  • C-RAN cloud radio access network
  • Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • the disaggregated base station 1500 architecture may include one or more CUs 1510 that can communicate directly with a core network 1520 via a backhaul link, or indirectly with the core network 1520 through one or more disaggregated base station units (such as a Near-RT RIC 1525 via an E2 link, or a Non-RT RIC 1515 associated with a Service Management and Orchestration (SMO) Framework 1505, or both) .
  • a CU 1510 may communicate with one or more DUs 1530 via respective midhaul links, such as an F1 interface.
  • the DUs 1530 may communicate with one or more RUs 1540 via respective fronthaul links.
  • the fronthaul link, the midhaul link, and the backhaul link may be generally referred to as “communication links.
  • the RUs 1540 may communicate with respective UEs 120 via one or more RF access links. In some aspects, the UE 120 may be simultaneously served by multiple RUs 1540.
  • the DUs 1530 and the RUs 1540 may also be referred to as “O-RAN DUs (O-DUs” ) and “O-RAN RUs (O-RUs) ” , respectively.
  • a network entity may include a CU, a DU, an RU, or any combination of CUs, DUs, and RUs.
  • a network entity may include a disaggregated base station or one or more components of the disaggregated base station, such as a CU, a DU, an RU, or any combination of CUs, DUs, and RUs.
  • a network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS) , or other components that may provide a network interface for or serve a UE, mobile station, sensor/actuator, or other wireless device.
  • TRP Transmission Control Protocol
  • RATS intelligent reflective surface
  • Each of the units may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units.
  • the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 1510 may host one or more higher layer control functions.
  • control functions can include RRC, packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like.
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1510.
  • the CU 1510 may be configured to handle user plane functionality (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof.
  • the CU 1510 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 1510 can be implemented to communicate with the DU 1530, as necessary, for network control and signaling.
  • the DU 1530 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 1540.
  • the DU 1530 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3GPP.
  • the DU 1530 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1530, or with the control functions hosted by the CU 1510.
  • Lower-layer functionality can be implemented by one or more RUs 1540.
  • an RU 1540 controlled by a DU 1530, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split.
  • the RU (s) 1540 can be implemented to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU (s) 1540 can be controlled by the corresponding DU 1530.
  • this configuration can enable the DU (s) 1530 and the CU 1510 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 1505 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 1505 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) .
  • the SMO Framework 1505 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 1590) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) .
  • a cloud computing platform such as an open cloud (O-Cloud) 1590
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs 1510, DUs 1530, RUs 1540 and Near-RT RICs 1525.
  • the SMO Framework 1505 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 1511, via an O1 interface. Additionally, in some implementations, the SMO Framework 1505 can communicate directly with one or more RUs 1540 via an O1 interface.
  • the SMO Framework 1505 also may include a Non-RT RIC 1515 configured to support functionality of the SMO Framework 1505.
  • the Non-RT RIC 1515 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 1525.
  • the Non-RT RIC 1515 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 1525.
  • the Near-RT RIC 1525 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 1510, one or more DUs 1530, or both, as well as an O-eNB, with the Near-RT RIC 1525.
  • the Non-RT RIC 1515 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 1525 and may be received at the SMO Framework 1505 or the Non-RT RIC 1515 from non-network data sources or from network functions. In some examples, the Non-RT RIC 1515 or the Near-RT RIC 1525 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 1515 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 1505 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
  • SMO Framework 1505 such as reconfiguration via O1
  • A1 policies such as A1 policies
  • Fig. 15 is provided as an example. Other examples may differ from what is described with regard to Fig. 15.
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving a configuration for physical downlink channel repetitions within an active bandwidth part that is divided into multiple subbands; and receiving the physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • UE user equipment
  • Aspect 2 The method of Aspect 1, wherein the configuration specifies a bandwidth size for each subband.
  • Aspect 3 The method of Aspect 2, wherein the bandwidth size less than or equal to half of the active bandwidth part.
  • Aspect 4 The method of any of Aspects 1-3, wherein the configuration or an indication in a message specifies the multiple subbands.
  • Aspect 5 The method of any of Aspects 1-4, wherein a subband used for a physical downlink channel repetition is based on a slot index.
  • Aspect 6 The method of any of Aspects 1-5, wherein receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions across subbands and with a same time domain resource allocation.
  • Aspect 7 The method of any of Aspects 1-6, further comprising receiving a frequency hopping indication, and wherein receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • Aspect 8 The method of Aspect 7, wherein the frequency hopping includes inter-slot frequency hopping.
  • Aspect 9 The method of Aspect 7, wherein the frequency hopping includes intra-slot frequency hopping.
  • Aspect 10 The method of Aspect 9, wherein the frequency hopping indication specifies intra-slot frequency hopping across the multiple subbands.
  • Aspect 11 The method of Aspect 7, wherein the configuration indicates a switching time gap for the frequency hopping.
  • Aspect 12 The method of Aspect 11, wherein the switching time gap includes one or more symbols at a beginning of a slot after a frequency hop.
  • Aspect 13 The method of Aspect 12, wherein the one or more symbols are punctured or rate matched based at least in part on the switching time gap overlapping with a physical downlink channel transmission.
  • Aspect 14 The method of Aspect 11, wherein the switching time gap includes one or more symbols at an end of a slot before a frequency hop.
  • Aspect 15 The method of any of Aspects 1-14, further comprising receiving a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • Aspect 16 The method of Aspect 15, wherein the frequency hopping indication indicates intra-slot frequency hopping in response to the UE not being configured for downlink channel aggregation.
  • Aspect 17 The method of Aspect 15, wherein the frequency hopping indication indicates inter-slot frequency hopping in response to the UE being configured for downlink channel aggregation.
  • Aspect 18 The method of Aspect 1, wherein the configuration or a message indicates no frequency hopping within a subband.
  • Aspect 19 The method of any of Aspects 1-18, wherein the physical downlink channel repetitions include one or more of physical downlink control channel repetitions or physical downlink shared channel repetitions.
  • Aspect 20 The method of any of Aspects 1-19, wherein receiving the physical downlink channel repetitions includes receiving the physical downlink channel repetitions with frequency hopping of physical downlink shared channel (PDSCH) repetitions and physical downlink control channel (PDCCH) repetitions, and wherein a PDSCH repetition follows a PDCCH repetition in a subband of each slot of multiple slots.
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • a method of wireless communication performed by a network entity comprising: transmitting a configuration for physical downlink channel repetition with an active bandwidth part that is divided into multiple subbands; and transmitting physical downlink channel repetitions across the multiple subbands based at least in part on the configuration.
  • Aspect 22 The method of Aspect 21, wherein the configuration specifies a bandwidth size for each subband.
  • Aspect 23 The method of Aspect 21 or 22, further comprising transmitting a frequency hopping indication, and wherein transmitting the physical downlink channel repetitions includes transmitting the physical downlink channel repetitions with frequency hopping in one or more slots across the multiple subbands based at least in part on the frequency hopping indication.
  • Aspect 24 The method of Aspect 23, wherein the configuration indicates a switching time gap for the frequency hopping.
  • Aspect 25 The method of Aspect 24, further comprising puncturing or rate matching one or more symbols based at least in part on the switching time gap overlapping with a physical downlink channel transmission.
  • Aspect 26 The method of any of Aspects 21-25, further comprising transmitting a frequency hopping indication in a dedicated field or a reserved bit of a message.
  • Aspect 27 The method of Aspect 26, wherein the frequency hopping indication indicates intra-slot frequency hopping based on a configuration for downlink channel aggregation.
  • Aspect 28 The method of Aspect 26, wherein the frequency hopping indication indicates inter-slot frequency hopping based on a configuration for downlink channel aggregation.
  • Aspect 29 The method of any of Aspects 21-28, wherein the configuration or a message indicates no frequency hopping within a subband.
  • Aspect 30 The method of any of Aspects 21-28, wherein transmitting the physical downlink channel repetitions includes transmitting the physical downlink channel repetitions with frequency hopping of physical downlink shared channel (PDSCH) repetitions and physical downlink control channel (PDCCH) repetitions, and wherein a PDSCH repetition follows a PDCCH repetition in a subband of each slot of multiple slots.
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • Aspect 31 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-30.
  • Aspect 32 A device 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-30.
  • Aspect 33 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-30.
  • Aspect 34 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-30.
  • Aspect 35 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-30.
  • the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
  • “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 multiples of the same element (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) .
  • the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) .
  • the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon divers aspects, la présente divulgation porte, d'une manière générale, sur le domaine de la communication sans fil. Selon certains aspects, un équipement utilisateur (UE) peut recevoir une configuration pour des répétitions de canal physique de liaison descendante dans une partie de bande passante active qui est divisée en de multiples sous-bandes. L'UE peut recevoir les répétitions de canal de liaison descendante physique dans les multiples sous-bandes sur la base, au moins en partie, de la configuration. La divulgation concerne en outre de nombreux autres aspects.
PCT/CN2022/105342 2022-07-13 2022-07-13 Répétitions de canal physique de liaison descendante dans des sous-bandes WO2024011437A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/105342 WO2024011437A1 (fr) 2022-07-13 2022-07-13 Répétitions de canal physique de liaison descendante dans des sous-bandes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/105342 WO2024011437A1 (fr) 2022-07-13 2022-07-13 Répétitions de canal physique de liaison descendante dans des sous-bandes

Publications (1)

Publication Number Publication Date
WO2024011437A1 true WO2024011437A1 (fr) 2024-01-18

Family

ID=89535276

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/105342 WO2024011437A1 (fr) 2022-07-13 2022-07-13 Répétitions de canal physique de liaison descendante dans des sous-bandes

Country Status (1)

Country Link
WO (1) WO2024011437A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536450A (zh) * 2019-09-03 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置、传输接收节点、终端及介质
US20210099991A1 (en) * 2019-09-27 2021-04-01 Qualcomm Incorporated Physical downlink shared channel resources for reduced capability user equipment
CN114424653A (zh) * 2019-09-30 2022-04-29 华为技术有限公司 物理下行共享信道传输方法及通信装置
CN114499784A (zh) * 2020-10-23 2022-05-13 大唐移动通信设备有限公司 传输资源确定方法、装置及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536450A (zh) * 2019-09-03 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置、传输接收节点、终端及介质
US20210099991A1 (en) * 2019-09-27 2021-04-01 Qualcomm Incorporated Physical downlink shared channel resources for reduced capability user equipment
CN114424653A (zh) * 2019-09-30 2022-04-29 华为技术有限公司 物理下行共享信道传输方法及通信装置
CN114499784A (zh) * 2020-10-23 2022-05-13 大唐移动通信设备有限公司 传输资源确定方法、装置及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "On the CSI-RS configurations for NR CSI acquisition", 3GPP TSG-RAN WG1 #90 R1-1714253, 20 August 2017 (2017-08-20), XP051317040 *

Similar Documents

Publication Publication Date Title
US20230345475A1 (en) Scheduling of an uplink transmission of multiple transport blocks
US20230254815A1 (en) Default beam for multi-downlink control information based multi-transmit receive point with unified transmission configuration indicator
US20230275736A1 (en) Full duplex pattern indication
WO2024011437A1 (fr) Répétitions de canal physique de liaison descendante dans des sous-bandes
WO2024087004A1 (fr) Ressources de radiomessagerie séparées pour des capacités réduites
US20230163889A1 (en) Hybrid automatic repeat request (harq) codebook configurations indicating harq process identifiers
US20240163870A1 (en) Resource blocks in uplink band of subband full duplex symbol
US20230300756A1 (en) Prioritizations for transmission power reductions in carrier aggregation for simultaneous transmissions
WO2023168642A1 (fr) Indication d'indisponibilité de panneau d'antenne
WO2024045004A1 (fr) Informations de système à capacité réduite améliorée et ensemble de ressources de commande
WO2023206326A1 (fr) Multiplexage de commandes de liaison montante pour de multiples points de transmission et de réception
US20240063945A1 (en) Indicating sub-band locations for sub-band full duplex communication
US20230254870A1 (en) Default beam for cross-carrier scheduling with unified transmission configuration indicator
US20240137933A1 (en) Uplink transmissions in next available slots
US20240163070A1 (en) Demodulation reference signal precoding in precoding resource block groups associated with subband full duplex configurations
US20240090016A1 (en) Prioritization for reducing semi-persistent scheduling or configured grant blind decoding
US20240073872A1 (en) Indicating an availability of sub-slots in a sub-band full duplex slot
WO2023184379A1 (fr) Indication de fin de données d'autorisation configurée
WO2023201696A1 (fr) Multiplexage par répartition spatiale de transmissions de canal de liaison montante
WO2023159552A1 (fr) Activation d'état d'indicateur de configuration de transmission unifiée
US20240121019A1 (en) Reference resource or capability for cross-link interference measurement
US20240057090A1 (en) Allocating uplink channel resources for negative acknowledgement only based multicast feedback
US20230127928A1 (en) Carrier switching for a physical uplink control channel
WO2024026606A1 (fr) Saut d'opportunité de planification semi-persistante de liaison descendante
US20240195596A1 (en) Full-duplex partial uplink transmissions

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22950567

Country of ref document: EP

Kind code of ref document: A1