WO2024197779A1 - Indication de multiples occasions d'octroi configuré inutilisées - Google Patents

Indication de multiples occasions d'octroi configuré inutilisées Download PDF

Info

Publication number
WO2024197779A1
WO2024197779A1 PCT/CN2023/085367 CN2023085367W WO2024197779A1 WO 2024197779 A1 WO2024197779 A1 WO 2024197779A1 CN 2023085367 W CN2023085367 W CN 2023085367W WO 2024197779 A1 WO2024197779 A1 WO 2024197779A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
occasions
unused
period
aspects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/085367
Other languages
English (en)
Inventor
Fang Yuan
Iyab Issam SAKHNINI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2023/085367 priority Critical patent/WO2024197779A1/fr
Publication of WO2024197779A1 publication Critical patent/WO2024197779A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for indicating multiple unused configured grant occasions.
  • 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 network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs.
  • a UE may communicate with a network node via downlink communications and uplink communications.
  • Downlink (or “DL” ) refers to a communication link from the network node to the UE
  • uplink (or “UL” ) refers to a communication link from the UE to the network node.
  • Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL) , a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples) .
  • SL sidelink
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • 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 generating an indication of multiple unused configured grant (CG) occasions.
  • the method may include transmitting the indication less frequently than the multiple unused CG occasions occur.
  • CG configured grant
  • the method may include receiving an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur.
  • the method may include adjusting communications based at least in part on the indication.
  • the UE may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to generate an indication of multiple unused CG occasions.
  • the one or more processors may be configured to transmit the indication less frequently than the multiple unused CG occasions occur.
  • 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 receive an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur.
  • the one or more processors may be configured to adjust communications based at least in part on the indication.
  • the apparatus may include means for generating an indication of multiple unused CG occasions.
  • the apparatus may include means for transmitting the indication less frequently than the multiple unused CG occasions occur.
  • 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. 4 is a diagram illustrating an example of uplink configured grant (CG) communication, in accordance with the present disclosure.
  • Fig. 5 is a diagram illustrating examples of CG skipping indications, in accordance with the present disclosure.
  • Fig. 9 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.
  • Fig. 12 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.
  • CG communications may include periodic uplink communications that are configured for a UE, such that a network entity does not need to send separate downlink control information (DCI) to schedule each uplink communication, thereby conserving signaling overhead.
  • DCI downlink control information
  • resource allocation may be large, resource utilization may be high, interference in the uplink may increase, and power consumption may be higher.
  • the UE may skip CGs to conserve power. If one or more CGs are skipped, the UE may indicate, in uplink control information (UCI) , the CGs that are skipped.
  • UCI uplink control information
  • CG physical uplink shared channel (PUSCH) occasions also referred to herein as just “CG occasions”
  • PUSCH physical uplink shared channel
  • the skipping indication is carried in each CG occasion. If the skipping indication for extended reality (XR) is carried in every CG occasion, the overhead may be large.
  • the UE may transmit a skipping indication, or an indication of unused CG occasions, less frequently than the multiple unused CG occasions occur, in order to reduce overhead and conserve signaling resources. This may include less frequent indications or an indication for multiple CG occasions.
  • the multiple CG occasions may be in a subset of CG occasions of a CG period. The subset may be the first few CG occasions and/or the last few CG occasions in the CG period. By transmitting indications in the subset of CG occasions, there may be fewer indications of unused resources, and signaling resources are conserved.
  • 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 network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d) , a 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 entities.
  • a network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit) .
  • RAN radio access network
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .
  • CUs central units
  • DUs distributed units
  • RUs radio units
  • a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU.
  • a network node 110 may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs.
  • a network node 110 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, a transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof.
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
  • a network node 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used.
  • a network node 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 subscriptions.
  • 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) ) .
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig.
  • the network node 110a may be a macro network node for a macro cell 102a
  • the network node 110b may be a pico network node for a pico cell 102b
  • the network node 110c may be a femto network node for a femto cell 102c.
  • a network node 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 network node 110 that is mobile (e.g., a mobile network node) .
  • base station or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof.
  • base station or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, or a combination thereof.
  • the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110.
  • the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity 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 terms “base station” or “network node” may refer to any one or more of those different devices.
  • the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device.
  • the terms “base station” or “network node” 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 a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110) .
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the network node 110d e.g., a relay network node
  • the network node 110a may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d.
  • a network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • macro network nodes may have a high transmit power level (e.g., 5 to 40 watts)
  • pico network nodes, femto network nodes, and relay network nodes 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 network nodes 110 and may provide coordination and control for these network nodes 110.
  • the network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link.
  • the network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.
  • 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 node, 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.
  • 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 network node 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 network node 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.
  • a may include a communication manager 140.
  • the communication manager 140 may generate an indication of multiple unused configured grant (CG) occasions.
  • the communication manager 140 may transmit the indication less frequently than the multiple unused CG occasions occur. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • CG configured grant
  • a network entity may include a communication manager 150.
  • the communication manager 150 may receive an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur.
  • the communication manager 150 may adjust communications based at least in part on the indication. 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 network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the network node 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) .
  • the network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232.
  • a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node.
  • Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.
  • 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 modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • MCSs modulation and coding schemes
  • CQIs channel quality indicators
  • the network node 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 network node 110 and/or other network nodes 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 network node 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 network node 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. 2-12) .
  • 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 network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the network node 110 may include a modulator and a demodulator.
  • the network node 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. 2-12) .
  • the controller/processor 240 of the network node 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 indicating unused CG occasions, as described in more detail elsewhere herein.
  • the controller/processor 240 of the network node 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 900 of Fig. 9, process 1000 of Fig. 10, and/or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the network node 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 network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 900 of Fig. 9, process 1000 of Fig. 10, 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.
  • a UE (e.g., a UE 120) includes means for generating an indication of multiple unused CG occasions; and/or means for transmitting the indication less frequently than the multiple unused CG occasions occur.
  • the means for the UE 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., a network node 110) includes means for receiving an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur; and/or means for adjusting communications based at least in part on the indication.
  • 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.
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • NB Node B
  • eNB evolved NB
  • AP access point
  • TRP TRP
  • a cell a cell
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • AP access point
  • TRP TRP
  • a cell a cell, among other examples
  • Network entity or “network node”
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit) .
  • a disaggregated base station e.g., a disaggregated network node
  • a CU may be implemented within a network 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 network 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, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.
  • 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) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed.
  • a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
  • Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure.
  • the disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) .
  • a CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links.
  • RF radio frequency
  • Each of the units may include one or more interfaces or be coupled with 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 one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium.
  • each of 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, and 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 310 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples.
  • RRC radio resource control
  • 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 310.
  • the CU 310 may be configured to handle user plane functionality (for example, Central Unit –User Plane (CU-UP) functionality) , control plane functionality (for example, Central Unit –Control Plane (CU-CP) functionality) , or a combination thereof.
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
  • Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 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 depending, at least in part, on a functional split, such as a functional split defined by the 3GPP.
  • the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples.
  • FEC forward error correction
  • the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel
  • Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower-layer functionality.
  • an RU 340, controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split.
  • each RU 340 can be operated 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) 340 can be controlled by the corresponding DU 330.
  • this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 305 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 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) 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) platform 390
  • 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 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface.
  • the SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the Non-RT RIC 315 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 325.
  • the Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325.
  • the Near-RT RIC 325 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 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
  • the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .
  • 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 an example 400 of uplink CG communication, in accordance with the present disclosure.
  • PRBs physical resource blocks for uplink communications may be granted dynamically, such as with a scheduling request (SR) or a buffer status report (BSR) .
  • a UE may first transmit an SR on a physical uplink control channel (PUCCH) , requesting radio resources in the uplink when the UE has pending data in its buffer. With periodic BSR reporting, the network entity knows the available buffer at the UE. The network entity then transmits an uplink grant DCI. The allocated resources are specified in the DCI for the UE to transmit a communication on the PUSCH.
  • SR scheduling request
  • BSR buffer status report
  • PRBs for uplink communications may be granted according to a configuration.
  • CG communications may include periodic uplink communications that are configured for a UE, such that the network entity does not need to send separate DCI to schedule each uplink communication, thereby conserving signaling overhead.
  • a UE may be configured with a CG configuration for CG communications.
  • the UE may receive the CG configuration via an RRC message transmitted by a network entity (e.g., a network node 110) .
  • the CG configuration may indicate a resource allocation associated with CG uplink communications (e.g., in a time domain, frequency domain, spatial domain, and/or code domain) and a periodicity at which the resource allocation is repeated, resulting in periodically reoccurring scheduled CG occasions 405 for the UE.
  • the CG configuration may identify a resource pool or multiple resource pools that are available to the UE for an uplink transmission.
  • the CG configuration may configure contention-free CG communications (e.g., where resources are dedicated for the UE to transmit uplink communications) or contention-based CG communications (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure) .
  • contention-free CG communications e.g., where resources are dedicated for the UE to transmit uplink communications
  • contention-based CG communications e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure
  • the network entity may additionally transmit CG activation DCI to the UE to activate the CG configuration for the UE (e.g., for a Type 2 CG configuration) .
  • the network entity may indicate, in the CG activation DCI, communication parameters, such as an MCS, a resource block (RB) allocation, and/or antenna ports, for the CG-PUSCH communications to be transmitted in the scheduled CG occasions 405.
  • the UE may begin transmitting in the CG occasions 405 based at least in part on receiving the CG activation DCI. For example, beginning with a next scheduled CG occasion 405 subsequent to receiving the CG activation DCI, the UE may transmit a PUSCH communication in the scheduled CG occasions 405 using the communication parameters indicated in the CG activation DCI. The UE may refrain from transmitting in configured CG occasions 405 prior to receiving the CG activation DCI.
  • the network entity may transmit CG reactivation DCI to the UE to change the communication parameters for the CG-PUSCH communications.
  • the UE may begin transmitting in the scheduled CG occasions 405 using the communication parameters indicated in the CG reactivation DCI. For example, beginning with a next scheduled CG occasion 405 subsequent to receiving the CG reactivation DCI, the UE may transmit PUSCH communications in the scheduled CG occasions 405 based at least in part on the communication parameters indicated in the CG reactivation DCI.
  • the network entity may transmit CG cancellation DCI to the UE to temporarily cancel or deactivate one or more subsequent CG occasions 405 for the UE.
  • the CG cancellation DCI may deactivate only a subsequent one CG occasion 405 or a subsequent N CG occasions 405 (where N is an integer) .
  • CG occasions 405 after the one or more (e.g., N) CG occasions 405 subsequent to the CG cancellation DCI may remain activated.
  • the UE may refrain from transmitting in the one or more (e.g., N) CG occasions 405 subsequent to receiving the CG cancellation DCI.
  • the CG cancellation DCI cancels one subsequent CG occasion 405 for the UE.
  • the UE may automatically resume transmission in the scheduled CG occasions 405.
  • the network entity may transmit CG release DCI to the UE to deactivate the CG configuration for the UE.
  • the UE may stop transmitting in the scheduled CG occasions 405 based at least in part on receiving the CG release DCI. For example, the UE may refrain from transmitting in any scheduled CG occasions 405 until another CG activation DCI is received from the base station.
  • the CG cancellation DCI may deactivate only a subsequent one CG occasion 405 or a subsequent N CG occasions 405
  • the CG release DCI deactivates all subsequent CG occasions 405 for a given CG configuration for the UE until the given CG configuration is activated again by a new CG activation DCI.
  • RB allocation in the uplink may match the information bits of a communication and thus use less power.
  • transmitting an SR and waiting for an uplink grant increases latency.
  • RB allocation might be more than what is needed for the UE information bits and more power may be consumed than necessary.
  • the UE will have to pad the information bits such that all of the allocated resources to the UE are used. If the UE has fewer information bits, the UE may still be required to transmit over the allocation resources.
  • CG scheduling resource allocation may be large, resource utilization may be high, interference in the uplink may increase, and power consumption may be higher.
  • the higher power consumption may increase the thermal properties of the UE, which may be an important issue for XR devices or augmented reality (AR) devices.
  • AR augmented reality
  • a UE may skip or refrain from transmitting or receiving a communication associated with a grant, whether a dynamic grant or a CG. Otherwise, the UE transmits padded bits over the allocated resources (e.g., RBs) , even though the information bits may not require the allocated number of RBs for transmission.
  • the allocated number of RBs may be an overallocation.
  • the UE may receive a configuration (e.g., via RRC) that configures the UE to be able to skip a communication associated with a grant.
  • the UE may receive the grant for an uplink communication.
  • the UE may transmit the uplink communication (e.g., MAC protocol data unit (PDU) ) if data is available. Power consumption may increase if the grant is larger. If no data is available, the UE may not transmit the uplink communication.
  • PDU MAC protocol data unit
  • the UE may indicate, in UCI, the one or more CG-PUSCH occasions that are skipped.
  • CG-PUSCH occasions also referred to herein as just “CG occasions”
  • CG occasions that are not skipped and can be used are considered to be “not unused. ”
  • the CG occasions cannot be considered to be definitely “used” and thus such CG occasions that are not skipped may be considered to be “not unused. ” That is, CG occasions that are “not unused” may or may not be used.
  • UCI may indicate which CG occasions are used and which CG occasions are not unused.
  • UCI may explicitly indicate CG occasions that are not unused and the CG occasions that are unused can be derived.
  • UCI may explicitly indicate CG occasions that are unused and the CG occasions that are not unused can be derived.
  • HARQ hybrid automatic repeat request
  • the UE may multiplex hybrid automatic repeat request (HARQ) feedback in a PUSCH transmission that includes UCI (e.g., CG-UCI) .
  • HARQ hybrid automatic repeat request
  • a “not unused” CG occasion may also be called a “used” CG occasion.
  • the UE is allowed to not transmit a PUSCH if there is no uplink data.
  • the indication of “used” CG occasion may help the network entity to reduce blind detection efforts for overlapping CG occasions.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
  • Fig. 5 is a diagram illustrating examples 500 and 502 of CG skipping indications, in accordance with the present disclosure.
  • Example 500 shows a transmission in a CG occasion and a skipping indication for a skipped CG occasion.
  • the skipping indication is carried in each CG occasion. If the skipping indication for XR is carried in every CG occasion, the overhead may be large.
  • the UE may transmit a skipping indication, or an indication of unused CG occasions, less frequently than the multiple unused CG occasions occur, in order to reduce overhead and conserve signaling resources. This may include less frequent indications or an indication for multiple CG occasions.
  • the multiple CG occasions may be in a subset of CG occasions of a CG period. The subset may be the first few CG occasions and/or the last few CG occasions in the CG period.
  • the UE may transmit an indication of unused CG occasions only in the subset of CG occasions.
  • Example 502 shows CG occasions with PUSCH transmissions and CG occasions that may include an indication 504 of unused CG occasions.
  • the indication 504 may be in a subset of CG occasions 506 (e.g., first 6 CG occasions) within a CG period 508.
  • a predetermined occasion such as a first configured or a first transmitted PUSCH transmission occasion in a CG period may be used for the transmission of the indication.
  • Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
  • Fig. 6 is a diagram illustrating an example 600 associated with indicating unused CG occasions, in accordance with the present disclosure.
  • a network entity 610 e.g., a network node 110
  • a UE 620 e.g., a UE 120
  • a wireless network e.g., wireless network 100
  • the UE 620 may generate an indication of multiple unused CG occasions.
  • the multiple unused CG occasions may be in a subset of CG occasions of a CG period.
  • the indication may indicate multiple CG periods that respectively include the multiple unused CG occasions.
  • the UE 620 may transmit the indication.
  • the UE 620 may transmit indications less frequently than the multiple unused CG occasions occur. That is, the UE 620 may not transmit an indication in each CG occasion.
  • the UE 620 may transmit fewer indications than the quantity of unused CG occasions.
  • the network entity 610 may adjust communications based at least in part on the indication. For example, the network entity 610 may use the unused CG occasions to schedule other UEs. The network entity 610 may reduce power or activity during the unused CG occasions.
  • Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.
  • Fig. 7 is a diagram illustrating examples 700 and 702 of skipping indications, in accordance with the present disclosure.
  • an indication of unused CG occasions may apply to a skipping indication period.
  • the indication may indicate the skipping indication period.
  • the skipping indication period may include multiple CG periods.
  • a predetermined occasion such as a first configured or a first transmitted PUSCH transmission occasion in a multiple of CG periods may be used for the transmission of the indication.
  • an indication of unused CG occasions may apply to multiple CG periods.
  • An indication may be in one or more CG occasions out of multiple CG periods of a CG configuration.
  • a periodicity of the skipping indication periods may be independent of a periodicity of the CG periods.
  • a time offset for an indication within the skipping indication period may be independent of a time offset for an indication within a CG period.
  • Example 702 shows skipping indication periods that are different than CG periods. An indication may be found at an end of each skipping indication period but in different locations within each CG period.
  • 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 an example 800 of CG skipping indications, in accordance with the present disclosure.
  • a UE may transmit UCI that includes an indication of unused CG occasions for multiple CG configurations.
  • the UE may indicate one or more target CG configurations (e.g., one or more target CG configuration indices) with a HARQ identifier (ID) that is configured for joint CG deactivation of the target CG configurations.
  • Each target CG configuration may be indicated with unused CG occasions.
  • the UE may be configured with a HARQ ID for multiple CG occasions in deactivation DCI.
  • the HARQ ID may be reused in UCI for indications of unused CG occasions in XR.
  • the UE may deactivate the multiple CG occasions that are associated with the HARQ ID.
  • the UE may indicate the unused CG occasions for the multiple CG occasions that are associated with the HARQ ID.
  • the HARQ ID may apply for a configured time duration after a configured time.
  • Example 800 shows two CG configurations (e.g., CG ID1, CG ID2) for a component carrier (CC) , where each CG configuration has a different CG period and a different time offset.
  • CG ID1 may carry a skipping indication of unused CG occasions (shown by boxes) .
  • the indication may specify a time duration for the unused CG occasions.
  • the time duration may span multiple CG periods.
  • the HARQ ID may have a value of 1 (one) to indicate CG ID1.
  • a HARQ ID value of 1 may also be used to indicate both CG ID1 and CG ID2, such that a skipping indication applies to CG periods of both CG ID1 and CG ID2.
  • Fig. 8 is provided as an example. Other examples may differ from what is described with regard to Fig. 8.
  • Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 900 is an example where the UE (e.g., UE 120, UE 620) performs operations associated with indicating multiple unused CG occasions.
  • the UE e.g., UE 120, UE 620
  • process 900 may include generating an indication of multiple unused CG occasions (block 910) .
  • the UE e.g., using communication manager 1106, depicted in Fig. 11
  • process 900 may include transmitting the indication less frequently than the multiple unused CG occasions occur (block 920) .
  • the UE e.g., using transmission component 1104 and/or communication manager 1106, depicted in Fig. 11
  • Process 900 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 multiple unused CG occasions are a subset of CG occasions of a CG period.
  • the indication indicates multiple CG periods that respectively include the multiple unused CG occasions.
  • the multiple CG periods are included in a skipping indication period.
  • a periodicity of the skipping indication period is independent of a periodicity of the multiple CG periods.
  • a slot offset for the indication within the skipping indication period is independent of a slot offset for the indication within a CG period.
  • the indication indicates the skipping indication period.
  • the indication includes a HARQ ID that indicates one or more target CG configurations that indicate the multiple unused CG occasions.
  • the HARQ ID for the multiple unused CG occasions is associated with a deactivation downlink control information.
  • the indication is for a time duration that overlaps one or more CG periods.
  • process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.
  • Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a network entity, in accordance with the present disclosure.
  • Example process 1000 is an example where the network entity (e.g., network node 110, network entity 610) performs operations associated with indication of multiple unused CG occasions.
  • the network entity e.g., network node 110, network entity 610 performs operations associated with indication of multiple unused CG occasions.
  • process 1000 may include receiving an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur (block 1010) .
  • the network entity e.g., using reception component 1202 and/or communication manager 1206, depicted in Fig. 12
  • process 1000 may include adjusting communications based at least in part on the indication (block 1020) .
  • the network entity e.g., using communication manager 1206, depicted in Fig. 12
  • Process 1000 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 multiple unused CG occasions are a subset of CG occasions of a CG period.
  • the indication indicates multiple CG periods that respectively include the multiple unused CG occasions.
  • the multiple CG periods are included in a skipping indication period.
  • a periodicity of the skipping indication period is independent of a periodicity of the multiple CG periods.
  • a slot offset for the indication within the skipping indication period is independent of a slot offset for the indication within a CG period.
  • the indication is for the skipping indication period.
  • the indication includes a HARQ ID that indicates one or more target CG configurations that include the multiple unused CG occasions.
  • the HARQ ID for the multiple unused CG occasions is associated with a deactivation DCI.
  • the indication is for a time duration that overlaps one or more CG periods.
  • process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
  • Fig. 11 is a diagram of an example apparatus 1100 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1100 may be a UE (e.g., UE 120, UE 620) , or a UE may include the apparatus 1100.
  • the apparatus 1100 includes a reception component 1102, a transmission component 1104, and/or a communication manager 1106, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the communication manager 1106 is the communication manager 140 described in connection with Fig. 1.
  • the apparatus 1100 may communicate with another apparatus 1108, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1102 and the transmission component 1104.
  • another apparatus 1108 such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1102
  • the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figs. 1-8. Additionally, or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of Fig. 9.
  • the apparatus 1100 and/or one or more components shown in Fig. 11 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. 11 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 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1108.
  • the reception component 1102 may provide received communications to one or more other components of the apparatus 1100.
  • the reception component 1102 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 1100.
  • the reception component 1102 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 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1108.
  • one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmission component 1104 for transmission to the apparatus 1108.
  • the transmission component 1104 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 1108.
  • the transmission component 1104 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 1104 may be co-located with the reception component 1102 in a transceiver.
  • the communication manager 1106 may support operations of the reception component 1102 and/or the transmission component 1104. For example, the communication manager 1106 may receive information associated with configuring reception of communications by the reception component 1102 and/or transmission of communications by the transmission component 1104. Additionally, or alternatively, the communication manager 1106 may generate and/or provide control information to the reception component 1102 and/or the transmission component 1104 to control reception and/or transmission of communications.
  • the communication manager 1106 may generate an indication of multiple unused CG occasions.
  • the transmission component 1104 may transmit the indication less frequently than the multiple unused CG occasions occur.
  • Fig. 11 The number and arrangement of components shown in Fig. 11 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. 11. Furthermore, two or more components shown in Fig. 11 may be implemented within a single component, or a single component shown in Fig. 11 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 11 may perform one or more functions described as being performed by another set of components shown in Fig. 11.
  • Fig. 12 is a diagram of an example apparatus 1200 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1200 may be a network entity (e.g., network node 110, network entity 610) , or a network entity may include the apparatus 1200.
  • the apparatus 1200 includes a reception component 1202, a transmission component 1204, and/or a communication manager 1206, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the communication manager 1206 is the communication manager 150 described in connection with Fig. 1.
  • the apparatus 1200 may communicate with another apparatus 1208, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1202 and the transmission component 1204.
  • the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figs. 1-8. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 1000 of Fig. 10.
  • the apparatus 1200 and/or one or more components shown in Fig. 12 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. 12 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 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1208.
  • the reception component 1202 may provide received communications to one or more other components of the apparatus 1200.
  • the reception component 1202 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 1200.
  • the reception component 1202 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 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1208.
  • one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmission component 1204 for transmission to the apparatus 1208.
  • the transmission component 1204 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 1208.
  • the transmission component 1204 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 1204 may be co-located with the reception component 1202 in a transceiver.
  • the communication manager 1206 may support operations of the reception component 1202 and/or the transmission component 1204. For example, the communication manager 1206 may receive information associated with configuring reception of communications by the reception component 1202 and/or transmission of communications by the transmission component 1204. Additionally, or alternatively, the communication manager 1206 may generate and/or provide control information to the reception component 1202 and/or the transmission component 1204 to control reception and/or transmission of communications.
  • the reception component 1202 may receive an indication of multiple unused CG occasions less frequently than the multiple unused CG occasions occur.
  • the communication manager 1206 may adjust communications based at least in part on the indication.
  • Fig. 12 The number and arrangement of components shown in Fig. 12 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. 12. Furthermore, two or more components shown in Fig. 12 may be implemented within a single component, or a single component shown in Fig. 12 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 12 may perform one or more functions described as being performed by another set of components shown in Fig. 12.
  • a method of wireless communication performed by a user equipment (UE) comprising: generating an indication of multiple unused configured grant (CG) occasions; and transmitting the indication less frequently than the multiple unused CG occasions occur.
  • UE user equipment
  • Aspect 2 The method of Aspect 1, wherein the multiple unused CG occasions are a subset of CG occasions of a CG period.
  • Aspect 3 The method of any of Aspects 1-2, wherein the indication indicates multiple CG periods that respectively include the multiple unused CG occasions.
  • Aspect 4 The method of Aspect 3, wherein the multiple CG periods are included in a skipping indication period.
  • Aspect 5 The method of Aspect 4, wherein a periodicity of the skipping indication period is independent of a periodicity of the multiple CG periods.
  • Aspect 6 The method of Aspect 4 or 5, wherein a slot offset for the indication within the skipping indication period is independent of a slot offset for the indication within a CG period.
  • Aspect 7 The method of any of Aspects 4-6, wherein the indication indicates the skipping indication period.
  • Aspect 8 The method of any of Aspects 1-7, wherein the indication includes a hybrid automatic repeat request (HARQ) identifier (ID) that indicates one or more target CG configurations that indicate the multiple unused CG occasions.
  • HARQ hybrid automatic repeat request
  • Aspect 9 The method of Aspect 8, wherein the HARQ ID for the multiple unused CG occasions is associated with a deactivation downlink control information.
  • Aspect 10 The method of any of Aspects 1-9, wherein the indication is for a time duration that overlaps one or more CG periods.
  • a method of wireless communication performed by a network entity comprising: receiving an indication of multiple unused configured grant (CG) occasions less frequently than the multiple unused CG occasions occur; and adjusting communications based at least in part on the indication.
  • CG configured grant
  • Aspect 12 The method of Aspect 11, wherein the multiple unused CG occasions are a subset of CG occasions of a CG period.
  • Aspect 13 The method of any of Aspects 11-12, wherein the indication indicates multiple CG periods that respectively include the multiple unused CG occasions.
  • Aspect 14 The method of Aspect 13, wherein the multiple CG periods are included in a skipping indication period.
  • Aspect 15 The method of Aspect 14, wherein a periodicity of the skipping indication period is independent of a periodicity of the multiple CG periods.
  • Aspect 16 The method of Aspect 14 or 15, wherein a slot offset for the indication within the skipping indication period is independent of a slot offset for the indication within a CG period.
  • Aspect 17 The method of any of Aspects 14-16, wherein the indication is for the skipping indication period.
  • Aspect 18 The method of any of Aspects 11-17, wherein the indication includes a hybrid automatic repeat request (HARQ) identifier (ID) that indicates one or more target CG configurations that include the multiple unused CG occasions.
  • HARQ hybrid automatic repeat request
  • Aspect 19 The method of Aspect 18, wherein the HARQ ID for the multiple unused CG occasions is associated with a deactivation downlink control information.
  • Aspect 20 The method of any of Aspects 11-19, wherein the indication is for a time duration that overlaps one or more CG periods.
  • Aspect 21 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-20.
  • Aspect 22 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-20.
  • Aspect 23 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-20.
  • Aspect 24 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-20.
  • Aspect 25 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-20.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation portent en général sur le domaine des communications sans fil. Selon certains aspects, un équipement utilisateur (UE) peut générer une indication de multiples occasions d'octroi configuré (CG) inutilisées. L'UE peut transmettre l'indication moins fréquemment que le nombre de fois où les multiples occasions de CG inutilisées se produisent. De nombreux autres aspects sont décrits.
PCT/CN2023/085367 2023-03-31 2023-03-31 Indication de multiples occasions d'octroi configuré inutilisées Ceased WO2024197779A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/085367 WO2024197779A1 (fr) 2023-03-31 2023-03-31 Indication de multiples occasions d'octroi configuré inutilisées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/085367 WO2024197779A1 (fr) 2023-03-31 2023-03-31 Indication de multiples occasions d'octroi configuré inutilisées

Publications (1)

Publication Number Publication Date
WO2024197779A1 true WO2024197779A1 (fr) 2024-10-03

Family

ID=92903021

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/085367 Ceased WO2024197779A1 (fr) 2023-03-31 2023-03-31 Indication de multiples occasions d'octroi configuré inutilisées

Country Status (1)

Country Link
WO (1) WO2024197779A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210314999A1 (en) * 2018-12-25 2021-10-07 Vivo Mobile Communication Co., Ltd. Method for Configured Grant Configuration, Terminal, and Network-Side Device
WO2022104614A1 (fr) * 2020-11-18 2022-05-27 Lenovo (Beijing) Limited Procédé et appareil de transmission de données
US20220248446A1 (en) * 2021-02-02 2022-08-04 Qualcomm Incorporated Skipping semi persistent scheduling (sps) or configured grant physical uplink shared channel (cg pusch) occasions
WO2023021471A1 (fr) * 2021-08-18 2023-02-23 Lenovo (Singapore) Pte. Ltd. Transmissions sans autorisations correspondantes pour un service de réalité étendue
WO2023044912A1 (fr) * 2021-09-27 2023-03-30 Nec Corporation Procédé, dispositif et support de stockage informatique pour la communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210314999A1 (en) * 2018-12-25 2021-10-07 Vivo Mobile Communication Co., Ltd. Method for Configured Grant Configuration, Terminal, and Network-Side Device
WO2022104614A1 (fr) * 2020-11-18 2022-05-27 Lenovo (Beijing) Limited Procédé et appareil de transmission de données
US20220248446A1 (en) * 2021-02-02 2022-08-04 Qualcomm Incorporated Skipping semi persistent scheduling (sps) or configured grant physical uplink shared channel (cg pusch) occasions
WO2023021471A1 (fr) * 2021-08-18 2023-02-23 Lenovo (Singapore) Pte. Ltd. Transmissions sans autorisations correspondantes pour un service de réalité étendue
WO2023044912A1 (fr) * 2021-09-27 2023-03-30 Nec Corporation Procédé, dispositif et support de stockage informatique pour la communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Designs to Improve Reliability and Latency of UL Configured Grant", 3GPP DRAFT; R1-1906107 DESIGNS TO IMPROVE RELIABILITY AND LATENCY OF UL CONFIGURED GRANT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada, US; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051727564 *
INTEL CORPORATION: "Enhancements to configured grants for NR-unlicensed", 3GPP DRAFT; R1-1910643 - INTEL - CONFIGURED GRANT FOR NR-U, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 8 October 2019 (2019-10-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051789435 *

Similar Documents

Publication Publication Date Title
US12563463B2 (en) Event-based layer 1 measurement reporting
US12438658B2 (en) Skipped resources of a grant
US20240267924A1 (en) Reclaiming unused uplink occasions
US20240323951A1 (en) Preventing collisions between cell-specific reference signals and demodulation reference signals
US20250380294A1 (en) Prioritization for reducing semi-persistent scheduling or configured grant blind decoding
US12261800B2 (en) Non-overlapped cross-link interference reference signal transmission and reception windows
US12389415B2 (en) Resource skipping for multiple grants
US20240032046A1 (en) Repurposing skipping in uplink configured grant to improve uplink coverage
US20240349297A1 (en) Sounding reference signal resource set configuration
US20240314764A1 (en) Resource selection for configured grant
US12598049B2 (en) Full-duplex partial uplink transmissions
US20240334178A1 (en) User equipment sub-band full duplex
US20230300756A1 (en) Prioritizations for transmission power reductions in carrier aggregation for simultaneous transmissions
US20240314596A1 (en) Inter-user-equipment cross-link interference measurement
WO2024197779A1 (fr) Indication de multiples occasions d'octroi configuré inutilisées
US20240334427A1 (en) Configured grant (cg) occasion identifiers for overlapping cg occasions
US12418923B2 (en) Status indications for uplink configured grant instances
WO2024207409A1 (fr) Informations de commande de liaison descendante pour autorisation configurée de multiples canaux physiques partagés montants
US12484053B2 (en) Indication of whether configured grant physical uplink shared channel is to be transmitted
US12439389B2 (en) Resource skipping for partial uplink transmissions
WO2023184379A1 (fr) Indication de fin de données d'autorisation configurée
US20240155602A1 (en) Indication of uplink transmission precoding parameter change
WO2024234329A1 (fr) Attribution de puissance pour transmissions de canal de rétroaction de liaison latérale physique
WO2025050240A1 (fr) Réservation d'occasion de transmission de liaison montante
WO2024212154A1 (fr) Signal de référence de sondage précoce avant connexion de commande de ressources radio

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: 23929371

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23929371

Country of ref document: EP

Kind code of ref document: A1