[go: up one dir, main page]

WO2025208267A1 - Contrainte sur une ressource utilisée pour des occasions de transmission configurées - Google Patents

Contrainte sur une ressource utilisée pour des occasions de transmission configurées

Info

Publication number
WO2025208267A1
WO2025208267A1 PCT/CN2024/085183 CN2024085183W WO2025208267A1 WO 2025208267 A1 WO2025208267 A1 WO 2025208267A1 CN 2024085183 W CN2024085183 W CN 2024085183W WO 2025208267 A1 WO2025208267 A1 WO 2025208267A1
Authority
WO
WIPO (PCT)
Prior art keywords
tos
constraint
resources
resource
pusch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/085183
Other languages
English (en)
Inventor
Zhichao ZHOU
Huilin Xu
Jing Sun
Diana MAAMARI
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/CN2024/085183 priority Critical patent/WO2025208267A1/fr
Publication of WO2025208267A1 publication Critical patent/WO2025208267A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • 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

Definitions

  • aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for constraining resources used for configured transmission occasions.
  • Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.
  • the method includes transmitting first signaling configuring a user equipment (UE) with transmission occasions (TOs) and at least one constraint on use of the TOs by the UE and at least one constraint on resources available to the UE within the configured TOs; and receiving uplink data from the UE in one or more of the configured TOs, subject to the at least one constraint.
  • UE user equipment
  • TOs transmission occasions
  • an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and/or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and/or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein.
  • an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.
  • FIG. 1 depicts an example wireless communications network.
  • FIG. 2 depicts an example disaggregated base station architecture.
  • FIG. 3 depicts aspects of an example base station and an example user equipment.
  • FIG. 7 depicts an example of unused transmission occasion (UTO) uplink control information (UCI) signaling.
  • UTI uplink control information
  • FIG. 14 depicts a method for wireless communications.
  • FIG. 15 depicts a method for wireless communications.
  • FIG. 16 depicts aspects of an example communications device.
  • aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for constraining resources used for configured transmission occasions.
  • Configured scheduling is a mechanism in which the network can schedule physical uplink shared channel (PUSCH) resources for a user equipment (UE) .
  • Configured scheduling for the uplink may be performed using a configured grant (CG) .
  • Uplink resources are scheduled via CGs that occur periodically (referred to as CG occasions) without the need for control signaling, eliminating expense and delay associated with dynamic signaling.
  • CG parameters are typically configured via radio resource control (RRC) signaling and the activation of the grant may be accomplished via RRC or L1 signaling.
  • RRC radio resource control
  • the periodicity and configured parameters e.g., number of resource blocks (RBs) , modulation and coding scheme (MCS) , number of repetitions
  • RBs resource blocks
  • MCS modulation and coding scheme
  • a UE may transmit uplink control information (UCI) that indicates unused (i.e., not to be used) CG PUSCH TOs to the network. These unused CG PUSCH TOs may be referred to as unused TOs (UTOs) . Because a UE is not allowed to transmit PUSCH in an indicated UTO, based on the UTO information conveyed in the UCI, the network may better utilize the corresponding resources.
  • UCI uplink control information
  • UTOs unused TOs
  • XR UEs may be configured with multiple CG PUSCH TO configurations to support traffic transmission and avoid delay an signaling overhead associated with dynamic grant (DG) based PUSCH transmissions.
  • DG dynamic grant
  • XR traffic at the UE typically varies from time to time.
  • the configured CG PUSCH transmission occasions may not match the UL traffic data volume.
  • the network may configure more uplink resources than what is actually required by the UE, because configuring insufficient resources may introduce more latency and/or result in transmission failure for the XR UE.
  • the UTO-UCI mechanism described above allows the UE to dynamically indicate, to the network, regarding used or unused CG TOs.
  • a network entity e.g., a gNB
  • a constraint on the maximum amount of CG PUSCH resource a UE can use may help achieve a fit between the resources used and uplink data of the UE.
  • a UE may only use partial bandwidth of configured symbols /CG PUSCH TOs and, to account for this, the constraint of maximum amount of resource can be configured in terms of units of REs or RBs.
  • Potential benefits of the resource constraint based CG TO scheme proposed herein is include helping ensure that a high-priority UE is not able to use all configured resources. As a result, the constraint may help ensure resources are available to other low-priority UEs and that they are able to use remaining resources for CG-based uplink transmission. Another potential benefit is that a constraint on the maximum available resource for a specific UE may result in a reduction in size of the bitmap for UTO-UCI to indicate the ‘unused’ TOs.
  • wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.
  • EPC Evolved Packet Core
  • 5GC 5G Core
  • FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA) , satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor/actuator, display, internet of things (IoT) devices, always on (AON) devices, edge processing devices, or other similar devices.
  • IoT internet of things
  • AON always on
  • edge processing devices or other similar devices.
  • UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.
  • the BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120.
  • the communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and/or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104.
  • UL uplink
  • DL downlink
  • the communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity in various aspects.
  • MIMO multiple-input and multiple-output
  • BSs 102 may generally include: a NodeB, enhanced NodeB (eNB) , next generation enhanced NodeB (ng-eNB) , next generation NodeB (gNB or gNodeB) , access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and/or others.
  • Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell) .
  • a BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area) , a pico cell (covering relatively smaller geographic area, such as a sports stadium) , a femto cell (relatively smaller geographic area (e.g., a home) ) , and/or other types of cells.
  • BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations.
  • one or more components of a base station may be disaggregated, including a central unit (CU) , one or more distributed units (DUs) , one or more radio units (RUs) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, to name a few examples.
  • CU central unit
  • DUs distributed units
  • RUs radio units
  • RIC Near-Real Time
  • Non-RT Non-Real Time
  • a base station may be virtualized.
  • a base station e.g., BS 102
  • BS 102 may include components that are located at a single physical location or components located at various physical locations.
  • a base station includes components that are located at various physical locations
  • the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location.
  • a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture.
  • FIG. 2 depicts and describes an example disaggregated base station architecture.
  • Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and/or 5G.
  • BSs 102 configured for 4G LTE may interface with the EPC 160 through first backhaul links 132 (e.g., an S1 interface) .
  • BSs 102 configured for 5G e.g., 5G NR or Next Generation RAN (NG-RAN)
  • 5G e.g., 5G NR or Next Generation RAN (NG-RAN)
  • BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface) , which may be wired or wireless.
  • third backhaul links 134 e.g., X2 interface
  • Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband.
  • frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband.
  • 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz –7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz” .
  • FR2 Frequency Range 2
  • FR2 includes 24, 250 MHz –71, 000 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” ( “mmW” or “mmWave” ) .
  • FR2 may be further defined in terms of sub-ranges, such as a first sub-range FR2-1 including 24,250 MHz –52,600 MHz and a second sub-range FR2-2 including 52,600 MHz –71,000 MHz.
  • a base station configured to communicate using mmWave/near mmWave radio frequency bands e.g., a mmWave base station such as BS 180
  • the communications links 120 between BSs 102 and, for example, UEs 104 may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and/or other MHz) , and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .
  • BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’ .
  • BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104.
  • the transmit and receive directions for BS 180 may or may not be the same.
  • the transmit and receive directions for UE 104 may or may not be the same.
  • Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and/or 5 GHz unlicensed frequency spectrum.
  • STAs Wi-Fi stations
  • D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .
  • PSBCH physical sidelink broadcast channel
  • PSDCH physical sidelink discovery channel
  • PSSCH physical sidelink shared channel
  • PSCCH physical sidelink control channel
  • FCH physical sidelink feedback channel
  • EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and/or a Packet Data Network (PDN) Gateway 172, such as in the depicted example.
  • MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • MME 162 provides bearer and connection management.
  • IP Internet protocol
  • Serving Gateway 166 which itself is connected to PDN Gateway 172.
  • PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switched (PS) streaming service, and/or other IP services.
  • IMS IP Multimedia Subsystem
  • PS Packet Switched
  • BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and/or may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and/or may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • 5GC 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • AMF 192 may be in communication with Unified Data Management (UDM) 196.
  • UDM Unified Data Management
  • AMF 192 is a control node that processes signaling between UEs 104 and 5GC 190.
  • AMF 192 provides, for example, quality of service (QoS) flow and session management.
  • QoS quality of service
  • IP Internet protocol
  • UPF 195 which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190.
  • IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and/or other IP services.
  • a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
  • IAB integrated access and backhaul
  • FIG. 2 depicts an example disaggregated base station 200 architecture.
  • the disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both) .
  • a CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface.
  • DUs distributed units
  • the DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links.
  • the RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links.
  • RF radio frequency
  • the UE 104 may be simultaneously served by multiple RUs 240.
  • 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 communications 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 a radio frequency (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 a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • RF radio frequency
  • the CU 210 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like.
  • 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 210.
  • the CU 210 may be configured to handle user plane functionality (e.g., Central Unit –User Plane (CU-UP) ) , control plane functionality (e.g., Central Unit –Control Plane (CU-CP) ) , or a combination thereof.
  • the CU 210 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 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.
  • the DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240.
  • the DU 230 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 3 rd Generation Partnership Project (3GPP) .
  • the DU 230 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 230, or with the control functions hosted by the CU 210.
  • Lower-layer functionality can be implemented by one or more RUs 240.
  • an RU 240 controlled by a DU 230, 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) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communications with the RU (s) 240 can be controlled by the corresponding DU 230.
  • this configuration can enable the DU (s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 205 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 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) 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) 290
  • 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 210, DUs 230, RUs 240 and Near-RT RICs 225.
  • the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an O1 interface.
  • the SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.
  • the Non-RT RIC 215 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 225.
  • the Non-RT RIC 215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 225.
  • the Near-RT RIC 225 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 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.
  • the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
  • SMO Framework 205 such as reconfiguration via O1
  • A1 policies such as A1 policies
  • FIG. 3 depicts aspects of an example BS 102 and a UE 104.
  • BS 102 includes various processors (e.g., 320, 330, 338, and 340) , antennas 334a-t (collectively 334) , transceivers 332a-t (collectively 332) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339) .
  • BS 102 may send and receive data between BS 102 and UE 104.
  • BS 102 includes controller/processor 340, which may be configured to implement various functions described herein related to wireless communications.
  • UE 104 includes various processors (e.g., 358, 364, 366, and 380) , antennas 352a-r (collectively 352) , transceivers 354a-r (collectively 354) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360) .
  • UE 104 includes controller/processor 380, which may be configured to implement various functions described herein related to wireless communications.
  • BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller/processor 340.
  • the control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical HARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , and/or others.
  • the data may be for the physical downlink shared channel (PDSCH) , in some examples.
  • Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • DMRS PBCH demodulation reference signal
  • CSI-RS channel state information reference signal
  • Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t.
  • Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream.
  • Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.
  • UE 104 In order to receive the downlink transmission, UE 104 includes antennas 352a-352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively.
  • Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator may further process the input samples to obtain received symbols.
  • MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller/processor 380.
  • UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH) ) from the controller/processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) . The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM) , and transmitted to BS 102.
  • data e.g., for the PUSCH
  • control information e.g., for the physical uplink control channel (PUCCH)
  • Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) .
  • the symbols from the transmit processor 364 may
  • the uplink signals from UE 104 may be received by antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104.
  • Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller/processor 340.
  • Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.
  • Scheduler 344 may schedule UEs for data transmission on the downlink and/or uplink.
  • BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein.
  • “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller/processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and/or other aspects described herein.
  • “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller/processor 340, receive processor 338, scheduler 344, memory 342, and/or other aspects described herein.
  • UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein.
  • transmitting may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller/processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and/or other aspects described herein.
  • receiving may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller/processor 380, receive processor 358, memory 382, and/or other aspects described herein.
  • one or more processors may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.
  • FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.
  • FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure
  • FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe
  • FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure
  • FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.
  • Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD) .
  • OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and/or in the time domain with SC-FDM.
  • a wireless communications frame structure may be frequency division duplex (FDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL.
  • Wireless communications frame structures may also be time division duplex (TDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.
  • FDD frequency division duplex
  • TDD time division duplex
  • the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL/UL.
  • UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) .
  • SFI received slot format indicator
  • DCI DL control information
  • RRC radio resource control
  • a 10 ms frame is divided into 10 equally sized 1 ms subframes.
  • Each subframe may include one or more time slots.
  • each slot may include 7 or 14 symbols, depending on the slot format.
  • Subframes may also include mini-slots, which generally have fewer symbols than an entire slot.
  • Other wireless communications technologies may have a different frame structure and/or different channels.
  • the number of slots within a subframe is based on a slot configuration and a numerology.
  • different numerologies ( ⁇ ) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe.
  • different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe.
  • the subcarrier spacing and symbol length/duration are a function of the numerology.
  • the subcarrier spacing may be equal to 2 ⁇ ⁇ 15 kHz, where ⁇ is the numerology 0 to 6.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the slot duration is 0.25 ms
  • the subcarrier spacing is 60 kHz
  • the symbol duration is approximately 16.67 ⁇ s.
  • a resource grid may be used to represent the frame structure.
  • Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends, for example, 12 consecutive subcarriers.
  • RB resource block
  • PRBs physical RBs
  • the resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3) .
  • the RS may include demodulation RS (DMRS) and/or channel state information reference signals (CSI-RS) for channel estimation at the UE.
  • DMRS demodulation RS
  • CSI-RS channel state information reference signals
  • the RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and/or phase tracking RS (PT-RS) .
  • BRS beam measurement RS
  • BRRS beam refinement RS
  • PT-RS phase tracking RS
  • FIG. 4B illustrates an example of various DL channels within a subframe of a frame.
  • the physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including, for example, nine RE groups (REGs) , each REG including, for example, four consecutive REs in an OFDM symbol.
  • CCEs control channel elements
  • REGs RE groups
  • a primary synchronization signal may be within symbol 2 of particular subframes of a frame.
  • the PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe/symbol timing and a physical layer identity.
  • a secondary synchronization signal may be within symbol 4 of particular subframes of a frame.
  • the SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
  • the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block.
  • the MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and/or paging messages.
  • SIBs system information blocks
  • some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station.
  • the UE may transmit DMRS for the PUCCH and DMRS for the PUSCH.
  • the PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH.
  • the PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
  • UE 104 may transmit sounding reference signals (SRS) .
  • the SRS may be transmitted, for example, in the last symbol of a subframe.
  • the SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 4D illustrates an example of various UL channels within a subframe of a frame.
  • the PUCCH may be located as indicated in one configuration.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK/NACK feedback.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • radio resources can be allocated to a UE by configured scheduling, dynamic scheduling, or a combination of configured and dynamic scheduling.
  • Configured scheduling is a mechanism in which the network can schedule PUSCH resources for the UE without using DCI to schedule each PUSCH transmission. Configured scheduling is done by configuring the UE with the scheduling parameters semi-statically in RRC signaling. Configured scheduling helps reduce the scheduling overhead.
  • Configured scheduling for the uplink may be performed using a configured grant (CG) .
  • FIG. 5 illustrates an example timeline 500 for CG scheduling, where uplink resources are scheduled via CGs that occur periodically (referred to as CG occasions 502) without the need for control signaling, eliminating expense and delay associated with dynamic signaling.
  • CG parameters are typically configured via RRC signaling and the activation of the grant may be through RRC or L1 signaling.
  • the periodicity and configured parameters e.g., number of resource blocks (RBs) , modulation and coding scheme (MCS) , number of repetitions
  • RBs resource blocks
  • MCS modulation and coding scheme
  • Type 1 CGs Two different types of configured grants include Type 1 CGs and Type 2 CGs.
  • the network send higher layer RRC signaling (e.g., an RRCSetup or RRCReconfiguration message according to 3GPP TS 38.331) configuring all the parameters for PUSCH scheduling including a resource allocation.
  • the UE may transmit PUSCH according to configured scheduling, without receiving any lower layer trigger (e.g., DCI) .
  • Type 2 CG after the RRC configuration, the network sends a DCI (e.g., masked with a configured scheduling radio network temporary identifier (CS-RNTI) ) to activate the configured grant.
  • CS-RNTI radio network temporary identifier
  • the network may send MAC CE signaling to downselect the RRC configured resources and/or DCI overwriting the configured scheduling. Because the configured scheduling is semi-static, the UE may be overallocated with resources for uplink transmission, for example, due to changed channel conditions.
  • the network may send DCI to schedule each uplink transmission for the UE.
  • the network schedules uplink resources for the UE based on buffer status reports (BSRs) received from the UE.
  • BSRs buffer status reports
  • the network may still overallocate resources for the UE.
  • a BSR codepoint can correspond to a large range (e.g., 7-8 MB) .
  • a UE may first send a scheduling request (SR) , as indicated at 602, for resources to send the BSR (at 606) .
  • SR scheduling request
  • SR and BSR transmission, and waiting for an uplink grant may increase uplink latency at the UE, as the UE may wait for an uplink grant for the BSR (604) after sending the SR and may also wait for an uplink grant (608) for the data transmission (610) .
  • the UE may transmit uplink control information (UCI) that indicates unused (i.e., not to be used) CG PUSCH TOs to the network.
  • UCI uplink control information
  • these unused CG PUSCH TOs may be referred to as unused TOs (UTOs) .
  • the UTO-UCI mechanism may be useful to address scenarios of high data rate traffic with large and random packet size, as well as stringent latency requirements.
  • a network may configure multiple CG PUSCH TOs within each data generation cycle of UL traffic based on the maximum packet size generated in each data cycle.
  • UTO-UCI signaling is indicated in diagram 650 of FIG. 6B.
  • a UE may immediately begin transmitting PUSCHs 652 on the CG PUSCH TOs when data arrives in the UL data buffer.
  • the UE may indicate unused CG PUSCH TOs (e.g., UTOs 660 and 662) that are not used for UL data transmission via a UTO-UCI (654, 656, and 658) so that network can reallocate these resources to other UEs, this enhances the overall system throughput.
  • This UTO-UCI procedure may help avoid latency loss caused by scheduling request (SR) and buffer status report (BSR) based resource request, described above with reference to FIG. 6A, while avoiding wasted UL resources that are over-allocated to the UE.
  • the network may configure a UE to send UTO-UCI for a given CG configuration, in every transmitted PUSCH of the CG.
  • each UTO-UCI may convey a bitmap with certain bit values indicating one or more upcoming CG PUSCH TOs that will be skipped (UTOs) .
  • an RRC parameter may indicate the size of bit-map (e.g., with a value range from 3 to 8) .
  • each PUSCH transmission (in a used UTO 704) may convey UTO-UCI that is applicable to Nu consecutive and valid CG PUSCH TOs, starting with UTO_offset from the end of the transmitted CG PUSCH.
  • a bit value of “0” may indicate a used TO 704, while a bit value of “1” may indicate a UTO 706.
  • XR UEs may be configured with multiple CG PUSCH TO configurations to support traffic transmission and avoid delay an signaling overhead associated with dynamic grant (DG) based PUSCH transmissions.
  • DG dynamic grant
  • XR traffic at the UE typically varies from time to time.
  • the configured CG PUSCH transmission occasions may not match the UL traffic data volume.
  • the network may configure more uplink resources than what is actually required by the UE, because configuring insufficient resources may introduce more latency and/or result in transmission failure for the XR UE.
  • a high duty-cycle UE that is configured with CG-based PUSCH may take all the remaining resources so that other lower priority UEs cannot be scheduled.
  • the risk is that low-priority UEs may be starved if there is no resource remaining. If high-priority UEs are able to freely select any amount of CG-based resource, a principle of fairness is violated.
  • a maximum constraint for usable CG PUSCH occasions proposed herein may be designed to (e.g., at least almost) cover a maximum uplink data size for delay-sensitive service (e.g., XR video) . Otherwise, the XR video might have to be segmented into two parts, in which case, the latter part may have to wait for a long time for available resource, which is less than ideal.
  • delay-sensitive service e.g., XR video
  • a constraint on the maximum amount of CG PUSCH resource a UE can use may help achieve a fit between the resources used and uplink data of the UE.
  • a UE may only use partial bandwidth of configured symbols /CG PUSCH TOs and, to account for this, the constraint of maximum amount of resource can be configured in terms of units of REs or RBs.
  • Potential benefits of the resource constraint based CG TO scheme proposed herein is include helping ensure that a high-priority UE is not able to use all configured resources. As a result, the constraint may help ensure resources are available to other low- priority UEs and that they are able to use remaining resources for CG-based uplink transmission.
  • a constraint on the maximum available resource for a specific UE may result in a reduction in size of the bitmap for UTO-UCI to indicate the ‘unused’ TOs. This may be understood by considering an example that assumes that a UE is to indicate it does not intend to use the next X CG-PUSCH occasions with UTO-UCI in each PUSCH TO. Absent a constraint on a maximum number of CG TO resources, the bit field for the UTO-UCI may need to be log2 (M-1) , where M is the number of occasions. On the other hand, if the constraint is that the UE may only use N of the M occasions (N ⁇ M) , the bit field only needs to be log2 (N-1) .
  • the network entity may configure the UE with one or more CG configurations that configure the UE with PUSCH TOs. While PUSCH TOs are used as an illustrative example, the techniques proposed herein could also be used in other types of configured TOs.
  • the network entity may also configure the UE with at least one constraint.
  • the constraint may indicate a maximum number/amount of resources of the configured PUSCH TOs (e.g., or symbol thereof) the UE can use.
  • the at least one constraint specifies a maximum amount of resource that can be used by the UE in units of resource elements (REs) , RE groups (REGs) .
  • the at least one constraint comprises at least two different constraints that apply to different TOs or to different symbols of configured TOs.
  • the network entity may activate (e.g., or reactivate) one or more CG configurations.
  • CG configurations may be jointly activated via a same RRC message (e.g., for type 1 CG) or via DCI (e.g., for type 2 CG) .
  • the network may send a single DCI indicating the CG configuration indices (e.g., individual indices) or indicating group ID of the group.
  • the UE may select resources for transmission on the configured TOs, subject to the at least one constraint.
  • the constraint may help ensure at least some resources are available for other UEs.
  • the UE may transmit signaling (e.g., via a UTO-UCI in a transmitted CG PUSCH) indicating at least one UTO.
  • the indication may be via a UTO-UCI with a bitmap, as described with reference to FIG. 7.
  • the constraint on resources used by the UE may help reduce the size of such a bitmap.
  • a gNB can pre-allocate CG PUSCH occasions to a UE, and the network can place a constraint on a maximum number of CG PUSCH occasions the UE can use (e.g., or a maximum amount of resource in terms of the number of REs /RBs per symbol or per CG PUSCH TO for the UE) .
  • the criteria for the maximum amount of resource may be based on data volume and/or certain metrics of traffic. This approach may allow the UE to select its preferred resources and may help resolve certain concerns from the network (gNB) scheduling perspective. For example, a constraint on resources used by one (e.g., high priority) UE may mean at least some resources are available for the network to assign to other (e.g., lower priority) UEs.
  • the example timelines 900, 910, and 920 shown in FIG. 9 assume 8 non-overlapping CG PUSCH TOs, with the constraint dictating that a UE can use at most 4 of the 8.
  • the second, fourth, and fifth TOs are used TOs 904, while the remaining TOs are unused TOs 906.
  • the example timeline 910 only the second and fourth TOs are used.
  • the first-fourth TOs are used.
  • the example timelines 1000, 1010, and 1020 shown in FIG. 10 assume 8 CG PUSCH TOs including some overlapping TOs, again with the constraint dictating that a UE can use at most 4 of the 8.
  • an overlapping occasion generally means there is at least another occasion overlapping with it, but not that all pre-allocated occasions overlap with each other.
  • the second TO is used, as well as two subsequent overlapping TOs.
  • the example timeline 1010 only the second TO and one subsequent overlapping TO are used.
  • the first and second TOs are used, as well as two subsequent overlapping TOs.
  • Timing diagram 1100 of FIG. 11 illustrates an example where the constraint indicates a certain amount of resource 1106 that can be used by the UE, while a remaining amount 1104 may be used by other UEs. As illustrated, the maximum amount of resources indicated may differ in different TOs.
  • the resource unit indicated by the constraint may be a resource element group (REG) , which may contain 12 REs.
  • the maximum amount of resource may be configured from the point of view N REGs /RBs per symbol or per CG PUSCH TO.
  • a specific resource unit may defined for the maximum amount of available resource for the UE.
  • One or multiple specific units may be configured as the maximum amount of resource for the UE to use.
  • the network may configure the maximum number of CG PUSCH occasions that can be used by the UE from the point of view of the number of CG-based PUSCH TOs. In some cases, the network configures multiple CG PUSCH TOs in a cluster /pool to transmit the UL data. In such cases, the periodicity of the cluster may be aligned with UE application data generation cycle (e.g., the 60 frames per second video) .
  • Resources of CG PUSCH TOs may be more than what is needed by the UE to transmit the UL data packet. As proposed herein, there may be a constraint about the maximum number of CG PUSCH TOs that can be used by the UE. Thus, the UE should not indicate more CG PUSCH TOs than this threshold are used in the UCI indicating unused CG PUSCH occasions (e.g., via UTO-UCI) .
  • the maximum number of CG PUSCH TOs may be designed in an effort to provide enough resources for UE to transmit maximum size UL data.
  • the network configures the UE to use at most 4 of the 8 configured CG PUSCH occasions.
  • a summation of the resources of the 4 largest PUSCH occasions may cover the maximum expected uplink video frame size. Thus, these may be the four PUSCH occasions used by the UE.
  • the maximum total amount of resources that can be used by the UE in terms of CG PUSCH TOs can be higher if the UE selects smaller (in terms of resources) CG PUSCH occasions to use (e.g., according to the waiting XR data volume) .
  • UTO-UCI may be used to indicate the extra unused CG resource, within the context of the configured maximum number of CG PUSCH TOs.
  • the UE is configured to use a maximum of 4 CG PUSCH TOs, as indicated at 1302.
  • the UE only uses the first 3 CG PUSCH TOs, as indicated at 1304. Therefore, the UE may indicate this unused CG PUSCH TO (e.g., via a 4-bit bitmap) .
  • the maximum number of CG PUSCH occasions can be used by the UE determines the maximum number of not unused CG PUSCH occasions or the minimum number of unused CG PUSCH occasions indicated by the UCI /UTO-UCI among the configured CG PUSCH TOs.
  • the maximum number of used CG PUSCH occasions may be configured via a parameter in a CG configuration with multiple PUSCH occasions.
  • the maximum number of used CG PUSCH occasions may be configured jointly, for example, by parameters in multiple CG configurations. These CG configurations may be associated and, in such cases, their CG PUSCH occasions may be indicated by the same UCI. For example, a summation of the parameters may provide the maximum number of CG PUSCH occasions the UE can use.
  • the maximum number of used CG PUSCH occasions may be configured via a parameter (e.g., in the UCI configuration) indicating the maximum number of bits in the bitmap or codepoints in the UCI that is used to indicate used/unused PUSCH occasions.
  • the maximum number of used CG PUSCH occasions may be configured via a parameter (e.g., in the UCI configuration) indicating the minimum number of bits in the bitmap or codepoints in the UCI that is used to indicate unused PUSCH occasions.
  • Various factors may be taken into consideration when configuring a UE with CG PUSCH TOs and/or a constraint on the corresponding resources the UE may use. For example, for XR traffic with stringent packet delay budget (PDB) requirements, it may be reasonable to configure the maximum amount of available resource at the beginning of the configured resource pool. In such cases, the network may indicate the beginning Y CG PUSCH TOs as the maximum available resource for the UE.
  • PDB packet delay budget
  • the network may only configure the maximum available resource in the preconfigured resource pool for the UE, but without indicating the specific TOs. In such cases, it may be up to the UE’s judgement. For example, selection for the actually used TOs may be based on the data volume and required metrics of the data (e.g., PDB and/or reliability) .
  • the network may configure the maximum available resources in a configured resource pool for the UE via radio resource control (RRC) and/or a medium access control (MAC) control element (CE) .
  • RRC radio resource control
  • CE medium access control control element
  • the network may update the maximum value dynamically via downlink control information (DCI) .
  • DCI downlink control information
  • FIG. 14 shows an example of a method 1400 of wireless communications at a user equipment (UE) , such as a UE 104 of FIGS. 1 and 3.
  • UE user equipment
  • Method 1400 begins at step 1405 with receiving first signaling configuring the UE with transmission occasions (TOs) and at least one constraint on use of the TOs by the UE.
  • TOs transmission occasions
  • the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 16.
  • Method 1400 then proceeds to step 1410 with selecting resources for transmission on the configured TOs, subject to at least one constraint.
  • the operations of this step refer to, or may be performed by, circuitry for selecting and/or code for selecting as described with reference to FIG. 16.
  • Method 1400 then proceeds to step 1415 with transmitting uplink data on the selected resources.
  • the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 16.
  • the TOs comprise physical uplink shared channel (PUSCH) TOs; and the transmitting comprises transmitting at least one PUSCH on the selected resources.
  • PUSCH physical uplink shared channel
  • the at least one constraint comprises at least two different constraints that apply to different TOs or to different symbols of configured TOs.
  • the at least one constraint specifies a maximum amount of resources that can be used by the UE in a configured TO or within a symbol of a configured TO.
  • the at least one constraint specifies a maximum amount of resource that can be used by the UE in units of resource element groups (REGs) .
  • REGs resource element groups
  • the at least one constraint specifies a maximum amount of resource that can be used by the UE in terms of a number of resource elements (REs) .
  • REs resource elements
  • the at least one constraint specifies a maximum number of the TOs that can be used by the UE.
  • the at least one constraint specifies a maximum amount of resources that can be used by the UE in the configured TOs.
  • the method 1400 further includes transmitting second signaling indicating unused resources within the configured TOs, wherein the specified maximum amount of resources that can be used by the UE determines at least one of a maximum number of not unused TOs or a minimum number of unused TOs indicated by the second signaling.
  • the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 16.
  • the at least one constraint is configured by at least one of: a parameter in a configured grant (CG) configuration with multiple configured TOs; or jointly by parameters in multiple CG configurations.
  • CG configured grant
  • the at least one constraint is configured by at least one of: a parameter in an uplink control information (UCI) configuration that indicates a maximum number of bits in a bitmap or codepoints used to indicate used TOs or unused TOs.
  • UCI uplink control information
  • the configured TOs are based on a configured resource pool; and the constraint indicates a maximum amount of available resource in the configured resource pool.
  • the constraint indicates a maximum amount of available resource at a beginning of the configured resource pool without indicating specific TOs.
  • a value for the maximum amount of resources available in the configured resource pool is configured via at least one of radio resource control (RRC) or medium access control (MAC) control element (CE) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CE control element
  • the method 1400 further includes receiving downlink control information (DCI) updating the value for the maximum amount of resources available in the configured resource pool.
  • DCI downlink control information
  • the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 16.
  • method 1400 may be performed by an apparatus, such as communications device 1600 of FIG. 16, which includes various components operable, configured, or adapted to perform the method 1400.
  • Communications device 1600 is described below in further detail.
  • FIG. 14 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
  • FIG. 15 shows an example of a method 1500 of wireless communications at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
  • a network entity such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
  • Method 1500 begins at step 1505 with transmitting first signaling configuring a user equipment (UE) with transmission occasions (TOs) and at least one constraint on use of the TOs by the UE and at least one constraint on resources available to the UE within the configured TOs.
  • UE user equipment
  • TOs transmission occasions
  • the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference to FIG. 16.
  • Method 1500 then proceeds to step 1510 with receiving uplink data from the UE in one or more of the configured TOs, subject to the at least one constraint.
  • the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 16.
  • the TOs comprise physical uplink shared channel (PUSCH) TOs; and the transmitting comprises transmitting at least one PUSCH on selected resources.
  • PUSCH physical uplink shared channel
  • the at least one constraint comprises at least two different constraints that apply to different TOs or to different symbols of configured TOs.
  • the at least one constraint specifies a maximum amount of resources that can be used by the UE in a configured TO or within a symbol of a configured TO.
  • the at least one constraint specifies a maximum amount of resource that can be used by the UE in units of resource element groups (REGs) .
  • REGs resource element groups
  • the at least one constraint specifies a maximum amount of resource that can be used by the UE in terms of a number of resource elements (REs) .
  • REs resource elements
  • the at least one constraint specifies a maximum number of the TOs that can be used by the UE.
  • the at least one constraint specifies a maximum amount of resources that can be used by the UE in the configured TOs.
  • the method 1500 further includes outputting second signaling indicating unused resources within the configured TOs, wherein the specified maximum amount of resources that can be used by the UE determines at least one of a maximum number of not unused TOs or a minimum number of unused TOs indicated by the second signaling.
  • the operations of this step refer to, or may be performed by, circuitry for outputting and/or code for outputting as described with reference to FIG. 16.
  • the at least one constraint is configured by at least one of: a parameter in a configured grant (CG) configuration with multiple configured TOs; or jointly by parameters in multiple CG configurations.
  • CG configured grant
  • the at least one constraint is configured by at least one of: a parameter in an uplink control information (UCI) configuration that indicates a maximum number of bits in a bitmap or codepoints used to indicate used TOs or unused TOs.
  • UCI uplink control information
  • the configured TOs are based on a configured resource pool; and the at least one constraint indicates a maximum amount of available resource in the configured resource pool.
  • the at least one constraint indicates a maximum amount of available resource at a beginning of the configured resource pool without indicating specific TOs.
  • a value for the maximum amount of resources available in the configured resource pool is configured via at least one of radio resource control (RRC) or medium access control (MAC) control element (CE) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CE control element
  • the method 1500 further includes receiving downlink control information (DCI) updating the value for the maximum amount of resources available in the configured resource pool.
  • DCI downlink control information
  • the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference to FIG. 16.
  • the maximum amount of resources that can be used by the UE is based on at least one of data volume or one or more traffic metrics.
  • method 1500 may be performed by an apparatus, such as communications device 1600 of FIG. 16, which includes various components operable, configured, or adapted to perform the method 1500.
  • Communications device 1600 is described below in further detail.
  • FIG. 15 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
  • FIG. 16 depicts aspects of an example communications device 1600.
  • communications device 1600 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3.
  • communications device 1600 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
  • the communications device 1600 includes a processing system 1605 coupled to the transceiver 1665 (e.g., a transmitter and/or a receiver) .
  • processing system 1605 may be coupled to a network interface 1675 that is configured to obtain and send signals for the communications device 1600 via communication link (s) , such as a backhaul link, midhaul link, and/or fronthaul link as described herein, such as with respect to FIG. 2.
  • the transceiver 1665 is configured to transmit and receive signals for the communications device 1600 via the antenna 1670, such as the various signals as described herein.
  • the processing system 1605 may be configured to perform processing functions for the communications device 1600, including processing signals received and/or to be transmitted by the communications device 1600.
  • the processing system 1605 includes one or more processors 1610.
  • the one or more processors 1610 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and/or controller/processor 380, as described with respect to FIG. 3.
  • one or more processors 1610 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and/or controller/processor 340, as described with respect to FIG. 3.
  • the one or more processors 1610 are coupled to a computer-readable medium/memory 1635 via a bus 1660.
  • the computer-readable medium/memory 1635 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1610, cause the one or more processors 1610 to perform the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it.
  • instructions e.g., computer-executable code
  • reference to a processor performing a function of communications device 1600 may include one or more processors 1610 performing that function of communications device 1600.
  • computer-readable medium/memory 1635 stores code (e.g., executable instructions) , such as code for receiving 1640, code for selecting 1645, code for transmitting 1650, and code for outputting 1655. Processing of the code for receiving 1640, code for selecting 1645, code for transmitting 1650, and code for outputting 1655 may cause the communications device 1600 to perform the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it.
  • code e.g., executable instructions
  • Various components of the communications device 1600 may provide means for performing the method 1400 described with respect to FIG. 14, or any aspect related to it; and the method 1500 described with respect to FIG. 15, or any aspect related to it.
  • means for transmitting, sending or outputting for transmission may include transceivers 354 and/or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and/or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and/or the transceiver 1665 and the antenna 1670 of the communications device 1600 in FIG. 16.
  • Means for receiving or obtaining may include transceivers 354 and/or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and/or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and/or the transceiver 1665 and the antenna 1670 of the communications device 1600 in FIG. 16.
  • a method for wireless communications at a user equipment comprising: receiving first signaling configuring the UE with transmission occasions (TOs) and at least one constraint on use of the TOs by the UE; selecting resources for transmission on the configured TOs, subject to at least one constraint; and transmitting uplink data on the selected resources.
  • TOs transmission occasions
  • Clause 2 The method of Clause 1, wherein: the TOs comprise physical uplink shared channel (PUSCH) TOs; and the transmitting comprises transmitting at least one PUSCH on the selected resources.
  • the TOs comprise physical uplink shared channel (PUSCH) TOs; and the transmitting comprises transmitting at least one PUSCH on the selected resources.
  • PUSCH physical uplink shared channel
  • Clause 3 The method of any one of Clauses 1-2, wherein the at least one constraint comprises at least two different constraints that apply to different TOs or to different symbols of configured TOs.
  • Clause 4 The method of any one of Clauses 1-3, wherein the at least one constraint specifies a maximum amount of resources that can be used by the UE in a configured TO or within a symbol of a configured TO.
  • Clause 5 The method of Clause 4, wherein the at least one constraint specifies a maximum amount of resource that can be used by the UE in units of resource element groups (REGs) .
  • REGs resource element groups
  • Clause 6 The method of Clause 4, wherein the at least one constraint specifies a maximum amount of resource that can be used by the UE in terms of a number of resource elements (REs) .
  • REs resource elements
  • Clause 7 The method of Clause 4, wherein the at least one constraint specifies a maximum number of the TOs that can be used by the UE.
  • Clause 8 The method of Clause 4, wherein the at least one constraint specifies a maximum amount of resources that can be used by the UE in the configured TOs.
  • Clause 9 The method of Clause 4, further comprising: transmitting second signaling indicating unused resources within the configured TOs, wherein the specified maximum amount of resources that can be used by the UE determines at least one of a maximum number of not unused TOs or a minimum number of unused TOs indicated by the second signaling.
  • Clause 10 The method of Clause 4, wherein the at least one constraint is configured by at least one of: a parameter in a configured grant (CG) configuration with multiple configured TOs; or jointly by parameters in multiple CG configurations.
  • CG configured grant
  • Clause 11 The method of Clause 4, wherein the at least one constraint is configured by at least one of: a parameter in an uplink control information (UCI) configuration that indicates a maximum number of bits in a bitmap or codepoints used to indicate used TOs or unused TOs.
  • UCI uplink control information
  • Clause 12 The method of Clause 4, wherein: the configured TOs are based on a configured resource pool; and the constraint indicates a maximum amount of available resource in the configured resource pool.
  • Clause 13 The method of Clause 12, wherein the constraint indicates a maximum amount of available resource at a beginning of the configured resource pool without indicating specific TOs.
  • Clause 14 The method of Clause 12, wherein a value for the maximum amount of resources available in the configured resource pool is configured via at least one of radio resource control (RRC) or medium access control (MAC) control element (CE) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CE control element
  • Clause 15 The method of Clause 14, further comprising receiving downlink control information (DCI) updating the value for the maximum amount of resources available in the configured resource pool.
  • DCI downlink control information
  • Clause 16 A method for wireless communications at a network entity, comprising: transmitting first signaling configuring a user equipment (UE) with transmission occasions (TOs) and at least one constraint on use of the TOs by the UE and at least one constraint on resources available to the UE within the configured TOs; and receiving uplink data from the UE in one or more of the configured TOs, subject to the at least one constraint.
  • UE user equipment
  • TOs transmission occasions
  • Clause 17 The method of Clause 16, wherein: the TOs comprise physical uplink shared channel (PUSCH) TOs; and the transmitting comprises transmitting at least one PUSCH on selected resources.
  • PUSCH physical uplink shared channel
  • Clause 18 The method of any one of Clauses 16-17, wherein the at least one constraint comprises at least two different constraints that apply to different TOs or to different symbols of configured TOs.
  • Clause 19 The method of any one of Clauses 16-18, wherein the at least one constraint specifies a maximum amount of resources that can be used by the UE in a configured TO or within a symbol of a configured TO.
  • Clause 20 The method of Clause 19, wherein the at least one constraint specifies a maximum amount of resource that can be used by the UE in units of resource element groups (REGs) .
  • REGs resource element groups
  • Clause 21 The method of Clause 19, wherein the at least one constraint specifies a maximum amount of resource that can be used by the UE in terms of a number of resource elements (REs) .
  • REs resource elements
  • Clause 22 The method of Clause 19, wherein the at least one constraint specifies a maximum number of the TOs that can be used by the UE.
  • Clause 23 The method of Clause 19, wherein the at least one constraint specifies a maximum amount of resources that can be used by the UE in the configured TOs.
  • Clause 24 The method of Clause 19, further comprising: outputting second signaling indicating unused resources within the configured TOs, wherein the specified maximum amount of resources that can be used by the UE determines at least one of a maximum number of not unused TOs or a minimum number of unused TOs indicated by the second signaling.
  • Clause 25 The method of Clause 19, wherein the at least one constraint is configured by at least one of: a parameter in a configured grant (CG) configuration with multiple configured TOs; or jointly by parameters in multiple CG configurations.
  • CG configured grant
  • Clause 26 The method of Clause 19, wherein the at least one constraint is configured by at least one of: a parameter in an uplink control information (UCI) configuration that indicates a maximum number of bits in a bitmap or codepoints used to indicate used TOs or unused TOs.
  • UCI uplink control information
  • Clause 27 The method of Clause 19, wherein: the configured TOs are based on a configured resource pool; and the at least one constraint indicates a maximum amount of available resource in the configured resource pool.
  • Clause 28 The method of Clause 27, wherein the at least one constraint indicates a maximum amount of available resource at a beginning of the configured resource pool without indicating specific TOs.
  • Clause 29 The method of Clause 27, wherein a value for the maximum amount of resources available in the configured resource pool is configured via at least one of radio resource control (RRC) or medium access control (MAC) control element (CE) signaling.
  • RRC radio resource control
  • MAC medium access control
  • CE control element
  • Clause 30 The method of Clause 29, further comprising receiving downlink control information (DCI) updating the value for the maximum amount of resources available in the configured resource pool.
  • DCI downlink control information
  • Clause 31 The method of Clause 19, wherein the maximum amount of resources that can be used by the UE is based on at least one of data volume or one or more traffic metrics.
  • Clause 32 An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any combination of Clauses 1-31.
  • Clause 33 An apparatus, comprising means for performing a method in accordance with any combination of Clauses 1-31.
  • Clause 34 A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any combination of Clauses 1-31.
  • Clause 35 A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any combination of Clauses 1-31.
  • an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein.
  • the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC) , or any other such configuration.
  • SoC system on a chip
  • processor at least one processor or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation.
  • memory at least one memory or “one or more memories” generally refers to a single memory configured to store data and/or instructions, multiple memories configured to collectively store data and/or instructions.
  • Means for receiving, means for selecting, means for transmitting, and means for outputting may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 16.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “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) .
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the methods disclosed herein comprise one or more actions for achieving the methods.
  • the method actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific actions may be modified without departing from the scope of the claims.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • 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, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Landscapes

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

Abstract

Certains aspects de la présente divulgation concernent des techniques d'établissement de communication sans fil au niveau d'un équipement utilisateur (UE), comprenant de manière générale la réception d'une première signalisation configurant l'UE avec des occasions de transmission (TO) et au moins une contrainte en matière d'utilisation des TO par l'UE, la sélection de ressources pour une transmission sur les TO configurées, en tenant compte d'au moins une contrainte, et la transmission de données de liaison montante sur les ressources sélectionnées.
PCT/CN2024/085183 2024-04-01 2024-04-01 Contrainte sur une ressource utilisée pour des occasions de transmission configurées Pending WO2025208267A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085183 WO2025208267A1 (fr) 2024-04-01 2024-04-01 Contrainte sur une ressource utilisée pour des occasions de transmission configurées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085183 WO2025208267A1 (fr) 2024-04-01 2024-04-01 Contrainte sur une ressource utilisée pour des occasions de transmission configurées

Publications (1)

Publication Number Publication Date
WO2025208267A1 true WO2025208267A1 (fr) 2025-10-09

Family

ID=97265843

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/085183 Pending WO2025208267A1 (fr) 2024-04-01 2024-04-01 Contrainte sur une ressource utilisée pour des occasions de transmission configurées

Country Status (1)

Country Link
WO (1) WO2025208267A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045736A1 (en) * 2018-08-02 2020-02-06 Qualcomm Incorporated Randomized frequency locations for configured uplink grants
US20220167350A1 (en) * 2019-08-15 2022-05-26 Huawei Technologies Co., Ltd. Uplink transmission time domain resource determining method and apparatus
WO2022152261A1 (fr) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 Procédé et appareil de transmission de signal, et dispositif terminal, dispositif de réseau et support de stockage
US20230144103A1 (en) * 2020-04-10 2023-05-11 Nec Corporation Methods, devices and computer storage media for communication
US20230156798A1 (en) * 2020-04-22 2023-05-18 Samsung Electronics Co., Ltd. Transmission method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045736A1 (en) * 2018-08-02 2020-02-06 Qualcomm Incorporated Randomized frequency locations for configured uplink grants
US20220167350A1 (en) * 2019-08-15 2022-05-26 Huawei Technologies Co., Ltd. Uplink transmission time domain resource determining method and apparatus
US20230144103A1 (en) * 2020-04-10 2023-05-11 Nec Corporation Methods, devices and computer storage media for communication
US20230156798A1 (en) * 2020-04-22 2023-05-18 Samsung Electronics Co., Ltd. Transmission method and device
WO2022152261A1 (fr) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 Procédé et appareil de transmission de signal, et dispositif terminal, dispositif de réseau et support de stockage

Similar Documents

Publication Publication Date Title
US20230379921A1 (en) Uplink extended reality scheduling
US12471079B2 (en) Transmission alignment for mini-slots and mixed numerology component carriers
US12302350B2 (en) Hybrid automatic repeat request (HARQ) acknowledgment (ACK) resource indication for multi physical downlink shared channel (PDSCH) grants
WO2023206413A1 (fr) Gestion de transmissions en liaison montante se chevauchant à travers différents groupes d'avance temporelle
WO2025170697A1 (fr) Multiplexage d'informations de commande de liaison montante (uci) sur un canal physique partagé de liaison montante (pusch) avec informations de commande de liaison descendante de secours (dci)
US20240276486A1 (en) Transmission occasion skipping with overlapping resources
US20240267910A1 (en) Partial uplink transmission for simultaneous transmission across multiple panels
US12477546B2 (en) HARQ-ack feedback and intra-UE multiplexing
US20240215053A1 (en) Configuration based on traffic priority and quality-of-service awareness between user equipment
US20230413173A1 (en) Extended reality power savings enhancements
US20230388966A1 (en) Coordination between idle and inactive discontinuous reception
WO2025208267A1 (fr) Contrainte sur une ressource utilisée pour des occasions de transmission configurées
WO2025160729A1 (fr) Améliorations apportées à des communications en semi-duplex
US20240389092A1 (en) Reduced cancelation indication monitoring
US20250039923A1 (en) Multi-slot uplink transmission occasions during network discontinuous reception cycles
US20250267591A1 (en) Unused transmission occasion (uto) enabled transmission power increase
US20240357601A1 (en) Blind decoding improvements
US12356376B2 (en) Slot preconfiguration for coverage enhancement and power saving
US20240057067A1 (en) Sub-selection for overbooked multi physical downlink shared channel (pdsch)/physical uplink shared channel (pusch) transmission resources
US20230328694A1 (en) Flexible uplink transmission skipping
US20250344148A1 (en) Energy saving time division duplexing (tdd) pattern
US20250261008A1 (en) Enhanced rrm measurements for latency-sensitive traffic
WO2023193219A1 (fr) Rétroaction de communications sans fil
US20250089123A1 (en) User equipment initiated connected discontinuous reception command
WO2025043435A1 (fr) Sélection d'indicateur de configuration de transmission unifiée

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

Country of ref document: EP

Kind code of ref document: A1