Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/0091—Signaling for the administration of the divided path
  • H04L5/0094—Indication of how sub-channels of the path are allocated
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
  • H04L5/0055—Physical resource allocation for ACK/NACK
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/0001—Arrangements for dividing the transmission path
  • H04L5/0014—Three-dimensional division
  • H04L5/0023—Time-frequency-space
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
  • H04L5/0035—Resource allocation in a cooperative multipoint environment

Definitions

• the present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with sounding reference signal (SRS), downlink control information (DCI), and a physical uplink (UL) shared channel (PUSCH).
• SRS sounding reference signal
• DCI downlink control information
• PUSCH physical uplink shared channel
• 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. Examples of such 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, and time division synchronous code division multiple access (TD-SCDMA) systems.
• CDMA code division multiple access
• TDMA time division multiple access
• FDMA frequency division multiple access
• OFDMA orthogonal frequency division multiple access
• SC-FDMA single-carrier frequency division multiple access
• TD-SCDMA time division synchronous code division multiple access
• 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements.
• 3GPP Third Generation Partnership Project
• 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC).
• eMBB enhanced mobile broadband
• mMTC massive machine type communications
• URLLC ultra-reliable low latency communications
• Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
• LTE Long Term Evolution
• Each set of repetitions may include one or more repetitions.
• Such two sets of repetitions may correspond with two SRS resource sets which may include DCI that may indicate two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets.
• DCI may indicate two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets.
• Aspects herein enable association between the two SRS resource sets and the two set of PUSCH repetitions, facilitating more efficient PUSCH transmissions.
• a method, a computer-readable medium, and an apparatus at a user equipment are provided.
• the apparatus may include a memory and at least one processor coupled to the memory.
• the memory and the at least one processor coupled to the memory may be configured to receive a configuration of a first SRS resource set and a second SRS resource set.
• the memory and the at least one processor coupled to the memory may be further configured to receive, from anetwork entity (e.g., abase station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• anetwork entity e.g., abase station or a component of the base station
• the memory and the at least one processor coupled to the memory may be further configured to transmit, to the network entity, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a method, a computer-readable medium, and an apparatus at a network entity are provided.
• the apparatus may include a memory and at least one processor coupled to the memory.
• the memory and the at least one processor coupled to the memory may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set.
• the memory and the at least one processor coupled to the memory may be further configured to transmit, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the memory and the at least one processor coupled to the memory may be further configured to receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information transmitted in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
• the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
• FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
• FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
• FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.
• FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
• FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.
• FIG. 3 is a diagram illustrating an example of abase station and user equipment (UE) in an access network.
• FIG. 4 is a diagram illustrating abase station in communication with a UE.
• FIG. 5 is a diagram illustrating communications between a UE and a network entity.
• FIG. 6 is a diagram illustrating an example mapping pattern for physical uplink shared channel (PUSCH) repetitions.
• PUSCH physical uplink shared channel
• FIG. 7 is a diagram illustrating an example mapping pattern for PUSCH repetitions.
• FIG. 8 is a flowchart of a method of wireless communication.
• FIG. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.
• FIG. 10 is a flowchart of a method of wireless communication.
• FIG. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus.
• FIG. 12 shows a diagram illustrating an example disaggregated base station architecture.
• FIG. 13 is a diagram illustrating an example of a hardware implementation for an example network entity.
• FIG. 14 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION
• processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
• processors in the processing system may execute software.
• Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
• the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
• Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
• such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer- readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
• RAM random-access memory
• ROM read-only memory
• EEPROM electrically erasable programmable ROM
• optical disk storage magnetic disk storage
• magnetic disk storage other magnetic storage devices
• combinations of the types of computer- readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
• Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations.
• devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect.
• transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.).
• innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
• a network node may be implemented in an aggregated or disaggregated architecture.
• a network entity such as a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality
• RAN radio access network
• BS base station
• one or more units or one or more components
• aBS such as a Node B (NB), evolved NB (eNB),NRBS, 5GNB, access point (AP), a transmit receive point (TRP), or a cell, etc.
• NB Node B
• eNB evolved NB
• 5GNB 5GNB
• AP access point
• TRP transmit receive point
• a cell etc.
• a BS may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
• An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
• a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
• CUs central or centralized units
• DUs distributed units
• RUs radio units
• a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
• the DUs may be implemented to communicate with one or more RUs.
• Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
• Base station operation or network design may consider aggregation characteristics of base station functionality.
• disaggregated base stations may be utilized in an integrated access backhaul (LAB) 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)).
• LAB integrated access backhaul
• O- RAN open radio access network
• vRAN also known as a cloud radio access network
• Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
• the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
• the wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)).
• the base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station).
• the macrocells include base stations.
• the small cells include femtocells, picocells, and microcells.
• the base stations 102 configured for 4G LTE may interface with the EPC 160 through first backhaul links 132 (e.g., SI interface).
• the base stations 102 configured for 5G NR may interface with core network 190 through second backhaul links 184.
• UMTS Universal Mobile Telecommunications System
• 5G NR Next Generation RAN
• the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages.
• the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface).
• the first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.
• the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102.
• a network that includes both small cell and macrocells may be known as a heterogeneous network.
• a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).
• eNBs Home Evolved Node Bs
• CSG closed subscriber group
• the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from abase station 102 to aUE 104.
• the communication links 120 may use multiple- in put and multiple -output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
• the communication links may be through one or more carriers.
• the base stations 102 / UEs 104 may use spectrum up to 7MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
• the component carriers may include a primary component carrier and one or more secondary component carriers.
• a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
• D2D communication link 158 may use the DL/UL WWAN spectrum.
• the D2D communication 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), and a physical sidelink control channel (PSCCH).
• sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
• sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
• sidelink channels such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH).
• the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like.
• AP Wi-Fi access point
• STAs Wi-Fi stations
• communication links 154 e.g., in a 5 GHz unlicensed frequency spectrum or the like.
• the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
• CCA clear channel assessment
• the small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
• the small cell 102' employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
• the electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc.
• 5G NR 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).
• FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles.
• FR2 which is often referredto (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
• FR4 71 GHz - 114.25 GHz
• FR5 114.25 GHz - 300 GHz
• sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
• millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
• sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid band frequencies.
• millimeter wave or the like if used herein 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.
• Abase station 102 may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station.
• Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104.
• the gNB 180 may be referred to as a millimeter wave base station.
• the millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range.
• the base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.
• the base station 180 may transmit abeamformed signal to the UE 104 in one or more transmit directions 182'.
• the UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182".
• the UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions.
• the base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions.
• the base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104.
• the transmit and receive directions for the base station 180 may or may not be the same.
• the transmit and receive directions for the UE 104 may or may not be the same.
• the EPC 160 may include 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 a Packet Data Network (PDN) Gateway 172.
• MME Mobility Management Entity
• MBMS Multimedia Broadcast Multicast Service
• BM-SC Broadcast Multicast Service Center
• PDN Packet Data Network
• the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
• HSS Home Subscriber Server
• the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
• the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
• IP Internet protocol
• the PDN Gateway 172 provides UE IP address allocation as well as other functions.
• the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
• the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.
• the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
• the 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 may be used to schedule MBMS transmissions.
• PLMN public land mobile network
• the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
• MMSFN Multicast Broadcast Single Frequency Network
• the core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and aUser Plane Function (UPF) 195.
• the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
• the AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190.
• the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195.
• the UPF 195 provides UEIP address allocation as well as other functions.
• the UPF 195 is connected to the IP Services 197.
• the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.
• IMS IP Multimedia Subsystem
• PS Packet Switch
• PSS Packet
• the base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set(BSS), an extended service set (ESS), atransmit reception point (TRP), or some other suitable terminology.
• the base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104.
• Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, amultimedia device, a video device, adigital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
• SIP session initiation protocol
• PDA personal digital assistant
• Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.).
• the UE 104 may also be referredto as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
• the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
• the UE 104 may include an SRS component 198.
• the SRS component 198 may be configured to receive (e.g., from a network entity such as the base station 102/180) a configuration of a first SRS resource set and a second SRS resource set.
• the SRS component 198 may be further configured to receive, from a network entity (e.g., the base station 102/180), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the SRS component 198 may be further configured to transmit, to the network entity, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the UL transmission may include the PUSCH, including the first set of repetitions of the PUSCH and the second set of repetitions of the PUSCH.
• the first set of repetitions of a PUSCH may be transmitted on the first beam associated with the first SRS resource set and power control for the PUSCH may be based on SRS resource indicator (SRI) associated with the first SRS resource set and the second set of repetitions of the PUSCH may be transmitted on the second beam associated with the second SRS resource set and power control for the PUSCH may be based on SRI associated with the second SRS resource set.
• the network entity may be a network node.
• a network node may be implemented as an aggregated base station, as a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, or the like.
• a network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near- Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non- RT) RIC.
• the base station 180 may include an SRS component 199.
• the SRS component 199 may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set.
• the SRS component 199 may be further configured to transmit, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the SRS component 199 may be further configured to receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information transmitted in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the UL transmission may include the PUSCH, including the first set of repetitions of the PUSCH and the second set of repetitions of the PUSCH
• the first set of repetitions of a PUSCH may be received on the first beam associated with the first SRS resource set and power control for the PUSCH may be based on SRI associated with the first SRS resource set
• the second set of repetitions of the PUSCH may be received on the second beam associated with the second SRS resource set and power control for the PUSCH may be based on SRI associated with the second SRS resource set.
• FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure.
• FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe.
• FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure.
• FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe.
• the 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL.
• FDD frequency division duplexed
• TDD time division duplexed
• the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols.
• UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI).
• DCI DL control information
• RRC radio resource control
• SFI received slot format indicator
• FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels.
• a frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols.
• the symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP -OFDM) symbols.
• OFDM orthogonal frequency division multiplexing
• the symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission).
• DFT discrete Fourier transform
• SC-FDMA single carrier frequency-division multiple access
• the number of slots within a subframe is based on the CP and the numerology.
• the numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS.
• SCS subcarrier spacing
• m 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe.
• the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology m, there are 14 symbols/slot and 2r slots/subframe.
• 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 ps.
• BWPs bandwidth parts
• Each BWP may have a particular numerology and CP (normal or extended).
• 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 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.
• the RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE.
• DM-RS demodulation RS
• CSI-RS channel state information reference signals
• the RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).
• BRS beam measurement RS
• BRRS beam refinement RS
• PT-RS phase tracking RS
• FIG. 2B 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) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB.
• CCEs control channel elements
• a PDCCH within one BWP may be referred to as a control resource set (CORESET).
• a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels.
• a PDCCH search space e.g., common search space, UE-specific search space
• a primary synchronization signal may be within symbol 2 of particular subframes of a frame.
• the PSS is used by a UE 104 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. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS.
• PCI physical cell identifier
• the physical broadcast channel which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)).
• 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 paging messages.
• SIBs system information blocks
• some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station.
• the UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH).
• the PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.
• the PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
• the UE may transmit sounding reference signals (SRS).
• the SRS may be transmitted 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. 2D 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 hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)).
• 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
• IP packets may be provided to a controller/processor 375.
• the controller/processor 375 implements layer 3 and layer 2 functionality.
• Layer 3 includes a radio resource control (RRC) layer
• layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
• RRC radio resource control
• SDAP service data adaptation protocol
• PDCP packet data convergence protocol
• RLC radio link control
• MAC medium access control
• the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction
• the transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions.
• Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/ demodulation of physical channels, and MIMO antenna processing.
• the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BP SK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)).
• BP SK binary phase-shift keying
• QPSK quadrature phase-shift keying
• M-PSK M-phase-shift keying
• M-QAM M-quadrature amplitude modulation
• the coded and modulated symbols may then be split into parallel streams.
• Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
• IFFT Inverse Fast Fourier Transform
• the OFDM stream is spatially precoded to produce multiple spatial streams.
• Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
• the channel estimate maybe derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
• Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx.
• Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
• RF radio frequency
• each receiver 354Rx receives a signal through its respective antenna 352.
• Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
• the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
• the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
• the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT).
• FFT Fast Fourier Transform
• the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
• the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
• the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
• the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
• the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
• the memory 360 may be referred to as a computer-readable medium.
• the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets.
• the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
• the controller/processor 359 provides RRC layer functionality associated with system information (e g., MIB, SIB s) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
• RRC layer functionality associated with system information (e g., MIB, SIB s) acquisition, RRC connections, and measurement reporting
• PDCP layer functionality associated with
• Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
• the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate anRF carrier with a respective spatial stream for transmission.
• the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
• Each receiver 318Rx receives a signal through its respective antenna 320.
• Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
• the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
• the memory 376 may be referred to as a computer-readable medium.
• the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets.
• the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
• At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the SRS component 198 of FIG. 1.
• At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the SRS component 199 of FIG. 1.
• FIG. 4 is a diagram 400 illustrating a base station 402 in communication with a UE 404.
• the base station 402 may transmit a beamformed signal to the UE 404 in one or more of the directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h.
• the UE 404 may receive the beamformed signal from the base station 402 in one or more receive directions 404a, 404b, 404c, 404d.
• the UE 404 may also transmit a beamformed signal to the base station 402 in one or more of the directions 404a- 404d.
• the base station 402 may receive the beamformed signal from the UE 404 in one or more of the receive directions 402a-402h.
• the base station 402 / UE 404 may perform beam training to determine the best receive and transmit directions for each of the base station 402 / UE 404.
• the transmit and receive directions for the base station 402 may or may not be the same.
• the transmit and receive directions for the UE 404 may or may not be the same.
• the UE 404 may determine to switch beams, e.g., between beams 404a-404h.
• the beam at the UE 404 may be used for reception of downlink communication and/or transmission of uplink communication.
• the base station 402 may send a transmission that triggers a beam switch by the UE 404.
• the base station 402 may indicate a transmission configuration indication (TCI) state change, and in response, the UE 404 may switch to a new beam for the new TCI state of the base station 402.
• a UE may receive a signal, from a base station, configured to trigger a transmission configuration indication (TCI) state change via, for example, a MAC control element (CE) command.
• TCI transmission configuration indication
• CE MAC control element
• the TCI state change may cause the UE to find the best UE receive beam corresponding to the TCI state from the base station, and switch to such beam.
• Switching beams may allow for enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver use the same configured set of beams for communication.
• the base station 402 and the UE 404 may each include multiple transmission reception points (TRPs). Each TRP may include different RF modules having a shared hardware and/or software controller. Each TRP may perform separate baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements.
• TRP transmission reception points
• Each TRP may include a different antenna panel or a different set of antenna elements.
• SRS resource set A set of time and frequency resources that may be used for one or more transmissions of SRS may be referred to as an “SRS resource set”.
• the SRS resource set applicability (i.e. what the SRS resource set is used for) for an SRS resource set may be configured by a higher layer parameter, such as “usage” associated with the SRS resource set, such as in the SRS-ResourceSet parameter.
• usage may be configured as one of beam management, codebook (e.g. for codebook-based transmission), non-codebook (e.g. for non-codebook— based transmission), antenna switching, or the like.
• codebook e.g. for codebook-based transmission
• non-codebook e.g. for non-codebook— based transmission
• Each SRS resource set may be configured with one or more (such as up to 16) SRS resources.
• Each SRS resource set may be aperiodic, semi-persistent, or periodic.
• the first type may be referred to as codebook based transmission.
• a UE may be configured with one SRS resource set with “usage” set to “codebook”. For example, a maximum of 4 SRS resources within the set may be configured for the UE.
• Each SRS resource may be radio resource control (RRC) configured with a number of ports, such as one or more ports.
• RRC radio resource control
• SRI SRS resource indicator
• the number of ports configured for the indicated SRS resource may determine number of antenna ports for the PUSCH.
• the PUSCH may be transmitted with the same spatial domain filter (which may be otherwise referred to as a “beam”) as the indicated SRS resources.
• the number of layers (i.e., rank) or transmitted precoding matrix indicator (TP MI) (e.g., for precoder) for the scheduled PUSCH may be determined from a separate DCI field “Precoding information and number of layers”.
• a UE may be configured with one SRS resource set with “usage” set to “non-codebook”. For example, a maximum of 4 SRS resources within the set may be configured for the UE. Each SRS resource may be RRC configured with one port.
• the SRI field in the UL DCI scheduling the PUSCH may indicate one or more SRS resources. A number of indicated SRS resources may determine the rank (i.e., number of layers) for the scheduled PUSCH.
• the PUSCH may be transmitted with the same precoder as well as a same spatial domain filter (i.e., beam) as the indicated SRS resources.
• multi- TRP or multi-panel may be used for enhancing reliability and robustness for PUSCH. For example, if one link using a first TRP is blocked and one repetition of the PUSCH fails to be received, another repetition may be received and decoded by another TRP. Therefore, with multi- TRP, diversity of transmission is increased and the PUSCH transmission may be more reliable. A repetition may be otherwise referred to as a transmission occasion.
• a PUSCH may be transmitted in one or more repetitions using different types of repetition. For different PUSCH repetitions corresponding to the same TB (e.g., which may carry the same data), the repetitions are transmitted in different slots in type A repetition while the repetitions are transmitted in different mini-slots in type B repetition.
• the number of repetitions may be RRC configured or may be indicated dynamically, such as by utilizing a time-domain resource assignment (TDRA) field of DCI.
• TDRA time-domain resource assignment
• all the repetitions may be transmitted with the same beam.
• the SRI field of the DCI may be applied to all the repetitions.
• SRI may be a field in the UL DCI that determines the beam or power control parameters for PUSCH by pointing to one or more SRS resources within an SRS resource set.
• different PUSCH repetitions are intended to be received at different TRPs, panels, or antennas at the network entity (e.g., base station) and the repetitions may use the same beam or different beams.
• the network entity e.g., base station
• Each set of repetitions may include one or more repetitions.
• Such two sets of repetitions may correspond with two SRS resource sets which are associated with DCI that indicates two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets.
• Aspects herein enable association between the two SRS resource sets and the two set of PUSCH repetitions.
• FIG. 5 is a diagram 500 illustrating communications between a UE 502 and a network entity 504 (e.g., a base station).
• the network entity 504 may configure the UE 502 with at least two SRS resource sets 506.
• the network entity 504 may or may not support dynamic order switching.
• the SRS resource sets 506 may each have an SRS resource set identifier (ID), which may be represented by an srs-ResourceSetID field in an SRS-ResourceSet parameter.
• the SRS resource sets 506 may include a parameter that represents an order, such as an SRS-ResourceSetOrder parameter.
• the network entity 504 may be a network node.
• a network node may be implemented as an aggregated base station, as a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or the like.
• a network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near- Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non- RT) RIC.
• the network entity 504 may transmit a DCI 508 to the UE 502.
• dynamic order switching may be supported by the network entity 504.
• the DCI 508 may include one or more bits, such as two bits, to indicate an order for the SRS resource sets in the SRS resource sets 506.
• the UE 502 may transmit one or more repetitions of a PUSCH, such as a first PUSCH repetition 510, a second PUSCH repetition 512, a third PUSCH repetition 514, and a fourth PUSCH repetition 516, to the network entity 504.
• the one or more repetitions of the PUSCH may include repetitions of the same data or TB.
• the SRS resource set with the lowest ID may correspond with the first set of repetitions (first may be the one that appears first in time) and the SRS resource set with the second lowest ID corresponds to the second set of repetitions.
• a first set of PUSCH repetitions may include the first PUSCH repetition 510 and the second PUSCH repetition 512 while the second set of PUSCH repetitions may include the third PUSCH repetition 514 and the fourth PUSCH repetition 516.
• the first set of PUSCH repetitions may correspond with the SRS resource set with the lowest ID.
• the first set of repetitions in time of a PUSCH may be transmitted on the first beam associated with the first SRS resource set and power control for the PUSCH may be based on SRI associated with the first SRS resource set and the second set of repetitions in time of the PUSCH may be transmitted on the second beam associated with the second SRS resource set and power control for the PUSCH may be based on SRI associated with the second SRS resource set.
• the first set of PUSCH repetitions may be transmitted using a same beam (first beam) (which may be otherwise referred to as “spatial domain filter”) as the first SRS resource set.
• the second set of PUSCH repetitions may be transmitted using a same beam (second beam) (which may be otherwise referred to as “spatial domain filter”) as the second SRS resource set.
• the first and second sets of repetitions may be transmitted on beams respectively selected for transmission to first and second TRPs, panels, or antennas of network entity 504. If the link to the first TRP is blocked, the first set of repetitions may fail to be received by network entity 504. However, because the data are also sent in the second set of repetitions to the second TRP, network entity 504 may nonetheless receive the data. Therefore, diversity of transmission is increased and the PUSCH transmission may be more reliable.
• the SRS resource set with the highest ID may correspond with the first set of repetitions and the SRS resource set with the second highest ID corresponds to the second set of repetitions.
• a first set of PUSCH repetitions may include the first PUSCH repetition 510 and the second PUSCH repetition 512 while the second set of PUSCH repetitions may include the third PUSCH repetition 514 and the fourth PUSCH repetition 516.
• the first set of PUSCH repetitions may correspond with the SRS resource set with the highest ID.
• the SRS resource set associated with the first PUSCH repetition 510, the second PUSCH repetition 512, the third PUSCH repetition 514, and the fourth PUSCH repetition 516 may be determined based on the parameter that represents an order.
• the SRS resource set, and SRI (which may be used for power control of PUSCH repetitions) or TRP associated with the SRS resource set may be indicated to the UE 502 so that the UE may be aware of which TRP and power control to use for the PUSCH repetitions.
• the one or more bits may represent a DCI code point that may correspond with an order.
• a DCI code point may be 0, 1, 2, or 3 and may be associated with an order 1, 2, 12, and 21.
• the order 1 may be based on that the SRS resource set with the lowest ID may correspond with a first TRP (e.g., which may be a single TRP mode and the second SRS resource set may be unused).
• the order 2 may be based on that the SRS resource set with the second lowest ID may correspond with a second TRP (e.g., which may be a single TRP mode and the first SRS resource set may be unused).
• the order 12 may be based on that the SRS resource set with the lowest ID may correspond with a first TRP and that the SRS resource set with the second lowest ID may correspond with a second TRP.
• the order 21 may be based on that the SRS resource set with the lowest ID may correspond with a second TRP and that the SRS resource set with the second lowest ID may correspond with a first TRP.
• Each SRS resource set may be associated with a beam and an SRI which may be used for power control in PUSCH repetitions.
• the DCI may include order that associate SRS resource set with PUSCH repetitions, which may in turn associate PUSCH repetitions with the beam or SRS associated with the SRS resource set.
• Table 1 illustrates an example correspondence between a set of DCI codepoints and a corresponding set of relationships that indicate an order for SRS resource sets.
• FIG. 6 is a diagram 600 illustrating an example cyclical mapping pattern for PUSCH repetitions.
• the DCI 602 may schedule four PUSCH repetitions, PUSCH repetition 604, PUSCH repetition 606, PUSCH repetition 608, and PUSCH repetition 610.
• the first PUSCH repetition 604 and the third PUSCH repetition 608 may be associated with a first beam and a first set of power control parameters.
• the second PUSCH repetition 606 and the fourth PUSCH repetition 610 may be associated with a second beam and a second set of power control parameters.
• the cyclical mapping pattern may be applicable for both Type A and Type B repetitions.
• FIG. 7 is a diagram 700 illustrating an example sequential mapping pattern for PUSCH repetitions.
• the DCI 702 may schedule four PUSCH repetitions, a first PUSCH repetition 704, a second PUSCH repetition 706, a third PUSCH repetition 708, and a fourth PUSCH repetition 710.
• the first PUSCH repetition 704 and the second PUSCH repetition 706 may be associated with a first beam and a first set of power control parameters.
• the third PUSCH repetition 708 and the fourth PUSCH repetition 710 may be associated with a second beam and a second set of power control parameters.
• the sequential mapping pattern may be applicable for both Type A and Type B repetitions.
• FIG. 8 is a flowchart 800 of a method of wireless communication.
• the method may be performed by a UE (e.g., the UE 104, the UE 404, the UE 502; the apparatus 902).
• a UE e.g., the UE 104, the UE 404, the UE 502; the apparatus 902).
• the UE may receive a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam.
• the UE 502 may receive a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam in the SRS resource sets 506 from the network entity 504.
• 802 may be performed by SRS configuration component 940 in FIG. 9 or the SRS component 198.
• the configuration includes SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.
• the UE may receive, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• a network entity e.g., a base station or a component of the base station
• the UE 502 may receive, from a network entity 504, DCI 508 for an UL transmission, the DCI 508 indicating the first SRS resource set and the second SRS resource set.
• 804 may be performed by DCI component 942 in FIG. 9 or the SRS component 198.
• the DCI does not indicate a support for dynamic order switching.
• the DCI indicates support for dynamic order switching.
• the information in the DCI may include one or more bits indicating an order rule associated with the first SRS resource set and the second SRS resource set.
• the DCI indicates a first SRI for the first set of repetitions and a second SRI for the second set of repetitions.
• the UE may transmit, to the network entity (e.g., a base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the network entity e.g., a base station or a component of the base station
• the UE 502 may transmit, to the network entity 504, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the first set of repetitions may include one or more of the PUSCH repetitions 510, 512, 514, and 516 and the second set of repetitions may include one or more of the PUSCH repetitions 510, 512, 514, and 516.
• 806 may be performed by PUSCH component 944 in FIG. 9 or the SRS component 198.
• the order is based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set and received in the configuration.
• the first SRS resource set ID is a lower number between the first SRS resource set ID and the second SRS resource set ID.
• the first SRS resource set ID is a higher number between the first SRS resource set ID and the second SRS resource set ID.
• the order rule represents that an SRS resource set with a lower SRS resource set ID is later in time. In some aspects, the order rule represents that an SRS resource set with a higher SRS resource set ID is later in time.
• the UE transmits the first set of repetitions with a first set of power control parameters and the second set of repetitions with a second set of power control parameters.
• the first set of repetitions is associated with a first antenna at the network entity and the second set of repetitions is associated with a second antenna at the network entity.
• FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902.
• the apparatus 902 may be a UE, a component of a UE, or may implement UE functionality.
• the apparatus2304 may include a cellular baseband processor 924 (also referred to as a modem) coupled to one or more transceivers 922 (e.g., cellular RF transceiver).
• the cellular baseband processor 924 may include on-chip memory 924'.
• the apparatus 902 may further include one or more subscriber identity modules (SIM) cards 920 and an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910.
• SIM subscriber identity modules
• SD secure digital
• the application processor 906 may include on-chip memory 906'.
• the apparatus 902 may further include a Bluetooth module 912, a WLAN module 914, an SPS module 916 (e.g., GNSS module), one or more sensor modules 918 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial management unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and/or other technologies used for positioning), additional memory modules 926, a power supply 930, and/or a camera 932.
• a Bluetooth module 912 e.g., a WLAN module 914
• SPS module 916 e.g., GNSS module
• sensor modules 918 e.g., barometric pressure sensor / altimeter; motion sensor such as inertial management unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted
• the Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)).
• TRX on-chip transceiver
• the Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include their own dedicated antennas and/or utilize the antennas 980 for communication.
• the cellular baseband processor 924 communicates through the transceiver(s) 922 via one or more antennas 980 with the UE 104 and/or with an RU associated with a network entity 904.
• the cellular baseband processor 924 and the application processor 906 may each include a computer-readable medium / memory 924', 906', respectively.
• the additional memory modules 926 may also be considered a computer-readable medium / memory.
• Each computer-readable medium / memory 924', 906', 926 may be non- transitory.
• the cellular baseband processor 924 and the application processor 906 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory.
• the software when executed by the cellular baseband processor 924 / application processor 906, causes the cellular baseband processor 924 / application processor 906 to perform the various functions described supra.
• the computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor 924 / application processor 906 when executing software.
• the cellular baseband processor 924 / application processor 906 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
• the apparatus 902 may be a processor chip (modem and/or application) and include just the cellular baseband processor 924 and/or the application processor 906, and in another configuration, the apparatus 902 may be the entire UE (e.g., see 350 of FIG. 3) and include the additional modules of the apparatus 902.
• the SRS component 198 may be configured to receive a configuration of a first SRS resource set and a second SRS resource set.
• the SRS component 198 may be further configured to receive, from a network entity, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the SRS component 198 may be further configured to transmit, to the network entity, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the SRS component 198 may include an SRS configuration component 940 that may be configured to receive a configuration of a first SRS resource set and a second SRS resource set, e.g., as described in connection with 802 in FIG. 8.
• the SRS component 198 may further include a DCI component 942 that may be configured to receive, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam, e.g., as described in connection with 804 in FIG. 8.
• a network entity e.g., a base station or a component of the base station
• the SRS component 198 may further include a PUSCH component 944 that may be configured to transmit, to the network entity (e.g., a base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, e.g., as described in connection with 806 in FIG. 8.
• the network entity e.g., a base station or a component of the base station
• the apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 9. As such, each block in the flowchart of FIG. 9 may be performed by a component and the apparatus may include one or more of those components.
• the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
• the apparatus 902 may include a variety of components configured for various functions.
• the apparatus 902, and in particular the cellular baseband processor 924 may include means for receiving a configuration of a first SRS resource set and a second SRS resource set.
• the cellular baseband processor 924 may further include means for receiving, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• a network entity e.g., a base station or a component of the base station
• the cellular baseband processor 924 may further include means for transmitting, to the network entity (e.g., a base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the means may be one or more of the components of the apparatus 902 configured to perform the functions recited by the means.
• the apparatus 902 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
• the means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the means.
• FIG. 10 is a flowchart 1000 of a method of wireless communication.
• the method may be performed by a network entity, such as abase station (e.g., the base station 102/180, the base station 402, the network entity 504, the network entity 1302, or the network entity 1460; the apparatus 1102).
• a network entity such as abase station (e.g., the base station 102/180, the base station 402, the network entity 504, the network entity 1302, or the network entity 1460; the apparatus 1102).
• the network entity may transmit a configuration of a first SRS resource set and a second SRS resource set.
• the network entity 504 may transmit a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam in the SRS resource sets 506 to the UE 502.
• 1002 may be performed by SRS configuration component 1140 in FIG. 11 or the SRS component 199.
• the configuration includes SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.
• the network entity may transmit, for aUE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the network entity 504 may transmit, for a UE 502, DCI 508 for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• 1004 may be performed by DCI component 1142 in FIG. 11 or the SRS component 199.
• the DCI does not indicate a support for dynamic order switching. In some aspects, the DCI indicates support for dynamic order switching. In some aspects, the information in the DCI may include one or more bits indicating an order rule associated with the first SRS resource set and the second SRS resource set. In some aspects, the DCI indicates a first SRI for the first set of repetitions and a second SRI for the second set of repetitions.
• the network entity may receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the network entity 504 may receive, from the UE 502, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the first set of repetitions may include one or more of the PUSCH repetitions 510, 512, 514, and 516 and the second set of repetitions may include one or more of the PUSCH repetitions 510, 512, 514, and 516.
• 1006 may be performed by PUSCH component 1144 in FIG. 11 or the SRS component 199.
• the order is based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set and received in the configuration.
• the first SRS resource set ID is a lower number between the first SRS resource set ID and the second SRS resource set ID.
• the first SRS resource set ID is a higher number between the first SRS resource set ID and the second SRS resource set ID.
• the order rule represents that an SRS resource set with a lower SRS resource set ID is later in time. In some aspects, the order rule represents that an SRS resource set with a higher SRS resource set ID is later in time.
• the UE transmits the first set of repetitions with a first set of power control parameters and the second set of repetitions with a second set of power control parameters. In some aspects, the first set of repetitions is associated with a first antenna at the base station and the second set of repetitions is associated with a second antenna at the base station.
• FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1102.
• the apparatus 1102 may be abase station, a component of a base station, or may implement base station functionality.
• the apparatus 1102 may include a baseband unit 1104.
• the baseband unit 1104 may communicate through a cellular RF transceiver 1122 with the UE 104.
• the baseband unit 1104 may include a computer-readable medium / memory.
• the baseband unit 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory.
• the software when executed by the baseband unit 1104, causes the baseband unit 1104 to perform the various functions described supra.
• the computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit 1104 when executing software.
• the baseband unit 1104 further includes a reception component 1130, a communication manager 1132, and a transmission component 1134.
• the communication manager 1132 includes the one or more illustrated components.
• the components within the communication manager 1132 may be stored in the computer-readable medium / memory and/or configured as hardware within the baseband unit 1104.
• the baseband unit 1104 may be a component of the base station 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
• the communication manager 1132 may include an SRS configuration component 1140 that may transmit a configuration of a first SRS resource set and a second SRS resource set, e.g., as described in connection with 1002 in FIG. 10.
• the communication manager 1132 further may include a DCI component 1142 that may transmit, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam, e.g., as described in connection with 1004 in FIG. 10.
• the communication manager 1132 further may include a PUSCH component 1144 that may receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, e.g., as described in connection with 1006 in FIG. 10.
• a PUSCH component 1144 may receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, e.g., as described in connection with 1006 in FIG. 10.
• the apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 10. As such, each block in the flowcharts of FIG. 10 may be performed by a component and the apparatus may include one or more of those components.
• the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
• the apparatus 1102 may include a variety of components configured for various functions.
• the apparatus 1102 and in particular the baseband unit 1104, may include means for transmitting a configuration of a first SRS resource set and a second SRS resource set.
• the baseband unit 1104 may further include means for transmitting, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the baseband unit 1104 may further include means for receiving a first set of repetitions of aPUSCHbased on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the means may be one or more of the components of the apparatus 1102 configured to perform the functions recited by the means.
• the apparatus 1102 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
• the means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the means.
• FIG. 12 shows a diagram illustrating an example disaggregated base station 1200 architecture.
• the disaggregated base station 1200 architecture may include one or more central units (CUs) 1210 that can communicate directly with a core network 1220 via a backhaul link, or indirectly with the core network 1220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 1225 via an E2 link, or a Non-Real Time (Non-RT) RIC 1215 associated with a Service Management and Orchestration (SMO) Framework 1205, or both).
• a CU 1210 may communicate with one or more distributed units (DUs) 1230 via respective midhaul links, such as an FI interface.
• DUs distributed units
• the DUs 1230 may communicate with one or more radio units (RUs) 1240 via respective fronthaul links.
• the RUs 1240 may communicate with respective UEs 1222 via one or more radio frequency (RF) access links.
• RF radio frequency
• the UE 1222 may be simultaneously served by multiple RUs 1240.
• the network entity 504 or the base station 102/180 may be implemented based on the disaggregated base station 1200 architecture.
• the UE 1222 may correspond with the UE 104 or the UE 502.
• 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.
• the units may collectively be referred to as a “network entity.”
• Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium.
• the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units.
• the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as 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 1210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1210.
• the CU 1210 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (UU CP)), or a combination thereof.
• the CU 1210 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 El interface when implemented in an O-RAN configuration.
• the CU 1210 can be implemented to communicate with the DU 1230, as necessary, for network control and signaling.
• the DU 1230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 1240.
• the DU 1230 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 1230 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 1230, or with the control functions hosted by the CU 1210.
• Lower-layer functionality can be implemented by one or more RUs 1240.
• an RU 1240 controlled by a DU 1230, 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) 1240 can be implemented to handle over the air (OTA) communication with one or more UEs 1222.
• OTA over the air
• real-time and non-real-time aspects of control and user plane communication with the RU(s) 1240 can be controlled by the corresponding DU 1230.
• this configuration can enable the DU(s) 1230 and the CU 1210 to be implemented in a cloud-based RAN architecture, such as avRAN architecture.
• the SMO Framework 1205 may be configured to support RAN deployment and provisioning of non- virtualized and virtualized network elements.
• the SMO Framework 1205 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 01 interface).
• the SMO Framework 1205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 1290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface).
• a cloud computing platform such as an open cloud (O-Cloud) 1290
• network element life cycle management such as to instantiate virtualized network elements
• cloud computing platform interface such as an 02 interface
• Such virtualized network elements can include, but are not limited to, CUs 1210, DUs 1230, RUs 1240 and Near-RTRICs 1225.
• the SMO Framework 1205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 1211, via an 01 interface. Additionally, in some implementations, the SMO Framework 1205 can communicate directly with one or more RUs 1240 via an 01 interface.
• the SMO Framework 1205 also may include aNon-RT RIC 1215 configured to support functionality of the SMO Framework 1205.
• the Non-RT RIC 1215 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 1225.
• the Non-RT RIC 1215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 1225.
• the Near-RT RIC 1225 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 1210, one or more DUs 1230, or both, as well as an O-eNB, with the Near-RT RIC 1225.
• the Non-RT RIC 1215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 1225 and may be received atthe SMO Framework 1205 or the Non-RT RIC 1215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 1215 or the Near-RT RIC 1225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 1215 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 1205 (such as reconfiguration via 01) or via creation of RAN management policies (such as A1 policies).
• FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for a network entity 1302.
• the network entity 1302 may be a BS, a component of a BS, or may implement BS functionality.
• the network entity 1302 may include at least one of a CU 1310, a DU 1330, or an RU 1340.
• the network entity 1302 may include the CU 1310; both the CU 1310 and the DU 1330; each of the CU 1310, the DU 1330, and the RU 1340; the DU 1330; both the DU 1330 and the RU 1340; or the RU 1340.
• the CU 1310 may include a CU processor 1312.
• the CU processor 1312 may include on-chip memory 1312'.
• the CU 1310 may further include additional memory modules 1314 and a communications interface 1318.
• the CU 1310 communicates with the DU 1330 through a midhaul link, such as an FI interface.
• the DU 1330 may include a DU processor 1332.
• the DU processor 1332 may include on-chip memory 1332'.
• the DU 1330 may further include additional memory modules 1334 and a communications interface 1338.
• the DU 1330 communicates with the RU 1340 through a fronthaul link.
• the RU 1340 may include an RU processor 1342.
• the RU processor 1342 may include on-chip memory 1342'.
• the RU 1340 may further include additional memory modules 1344, one or more transceivers 1346, antennas 1380, and a communications interface 1348.
• the RU 1340 communicates with the UE 104.
• the on-chip memory 1312', 1332', 1342' and the additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium / memory.
• Each computer-readable medium / memory may be non-transitory.
• Each of the processors 1312, 1332, 1342 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory.
• the software when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra.
• the computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.
• the SRS component 199 may be configured to transmit a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam.
• the SRS component 199 may be further configured to transmit, for a UE, DCI for anUL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the SRS component 199 may be further configured to receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the SRS component 199 may be within one or more processors of one or more of the CU 1310, DU 1330, and the RU 1340.
• the SRS component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.
• the network entity 1302 may include a variety of components configured for various functions.
• the network entity 1302 includes means for transmitting a configuration of a first SRS resource set and a second SRS resource set
• the network entity 1302 may further include means for transmitting, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the network entity 1302 may further include means for receiving a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the means may be the SRS component 199 of the network entity 1302 configured to perform the functions recited by the means.
• the network entity 1302 may include the TX processor 316, the RX processor 370, and the controller/processor 375.
• the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.
• FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a network entity 1460.
• the network entity 1460 may be within the core network 120.
• the network entity 1460 may include a network processor 1412.
• the network processor 1412 may include on-chip memory 1412'.
• the network entity 1460 may further include additional memory modules 1414.
• the network entity 1460 communicates via the network interface 1480 directly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU 1402.
• the on-chip memory 1412' and the additional memory modules 1414 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory.
• the processor 1412 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory.
• the software when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra.
• the computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.
• the SRS component 199 may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set.
• the SRS component 199 may be further configured to transmit, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the SRS component 199 may be further configured to receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the SRS component 199 may be within the processor 1412.
• the SRS component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.
• the network entity 1460 may include a variety of components configured for various functions.
• the network entity 1460 includes means for means for transmitting a configuration of a first SRS resource set and a second SRS resource set.
• the network entity 1460 may further include means for transmitting, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.
• the network entity 1460 may further include means for receiving a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• the means may be the SRS component 199 of the network entity 1460 configured to perform the functions recited by the means.
• Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
• combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.
• Aspect 1 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to: receive a configuration of a first SRS resource set and a second SRS resource set; receive, from a network entity (e.g., a base station or a component of the base station) , DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and transmit, to the network entity (e.g., the base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.
• Aspect 2 is the apparatus of aspect 1, wherein the order is based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set and received in the configuration.
• Aspect 3 is the apparatus of any of aspects 1-2, wherein the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID either being a lower or higher number between the first SRS resource set ID and the second SRS resource set ID.
• Aspect 4 is the apparatus of any of aspects 1-2, wherein the first and second beam are selected to transmit to different transmission/reception points, antenna panels, or antennas of the network entity.
• Aspect 5 is the apparatus of any of aspects 1-4, wherein the configuration includes SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.
• Aspect 6 is the apparatus of any of aspects 1-5, wherein the same data or transport block is transmitted on each repetition.
• Aspect 7 is the apparatus of any of aspects 1-5, wherein the DCI indicates support for dynamic order switching.
• Aspect 8 is the apparatus of any of aspects 1-7, wherein the information in the DCI comprises one or more bits indicating an order rule associated with the first SRS resource set and the second SRS resource set.
• Aspect 9 is the apparatus of any of aspects 1-8, wherein the order rule represents that an SRS resource set with a lower SRS resource set ID is later in time.
• Aspect 10 is the apparatus of any of aspects 1-8, wherein the order rule represents that an SRS resource set with a higher SRS resource set ID is later in time.
• Aspect 11 is the apparatus of any of aspects 1-10, wherein the UE transmits the first set of repetitions with a first set of power control parameters and the second set of repetitions with a second set of power control parameters.
• Aspect 12 is the apparatus any of aspects 1-11, wherein the DCI indicates a first SRI for the first set of repetitions and a second SRI for the second set of repetitions.
• Aspect 13 is the apparatus of any of aspects 1-12, wherein the first set of repetitions is associated with a first antenna at the network entity (e.g., the base station or a component of the base station) and the second set of repetitions is associated with a second antenna at the network entity.
• the network entity e.g., the base station or a component of the base station
• Aspect 14 is the apparatus of any of aspects 1-13, further comprising a transceiver or an antenna coupled to the at least one processor.
• Aspect 15 is an apparatus for wireless communication at a network entity (e.g., a base station or a component of the base station), comprising: a memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to cause the apparatus to: transmit a configuration of a first SRS resource set and a second SRS resource set; transmit, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g
• Aspect 16 is the apparatus of aspect 15, wherein the order is based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set and received in the configuration.
• Aspect 17 is the apparatus of any of aspects 15-16, wherein the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID either being a lower or higher number between the first SRS resource set ID and the second SRS resource set ID.
• Aspect 18 is the apparatus of any of aspects 15-16, wherein the first and second beam correspond to different transmission/reception points, antenna panels, or antennas of the network entity.
• Aspect 19 is the apparatus of any of aspects 15-18, wherein the configuration includes SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.
• Aspect 20 is the apparatus of any of aspects 15-19, wherein the same data or transport block is transmitted on each repetition.
• Aspect 21 is the apparatus of any of aspects 15-19, wherein the DCI indicates support for dynamic order switching.
• Aspect 22 is the apparatus of any of aspects 15-21, wherein the information in the DCI comprises one or more bits indicating an order rule associated with the first SRS resource set and the second SRS resource set.
• Aspect 23 is the apparatus of any of aspects 15-22, wherein the order rule represents that an SRS resource set with a lower SRS resource set ID is later in time.
• Aspect 24 is the apparatus of any of aspects 15-22, wherein the order rule represents that an SRS resource set with a higher SRS resource set ID is later in time.
• Aspect 25 is the apparatus of any of aspects 15-24, wherein the network entity (e.g., the base station or a component of the base station) receives the first set of repetitions with a first set of power control parameters and the second set of repetitions with a second set of power control parameters.
• the network entity e.g., the base station or a component of the base station
• Aspect 26 is the apparatus of any of aspects 15-25, wherein the DCI indicates a first
• Aspect 27 is the apparatus of any of aspects 15-26, wherein the first set of repetitions is associated with a first antenna at the network entity (e.g., the base station or a component of the base station) and the second set of repetitions is associated with a second antenna at the network entity (e.g., the base station or a component of the base station).
• the network entity e.g., the base station or a component of the base station
• the second set of repetitions is associated with a second antenna at the network entity (e.g., the base station or a component of the base station).
• Aspect 28 is the apparatus of any of aspects 15-27, further comprising a transceiver coupled to the at least one processor.
• Aspect 29 is a method of wireless communication at a UE, comprising: receiving a configuration of a first SRS resource set and a second SRS resource set; receiving, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and transmitting, to the network entity (e.g., the base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource
• Aspect 30 is the method of aspect 29, further comprising method for implementing any of aspects 1-14.
• Aspect 31 is an apparatus for wireless communication ataUE, comprising: means for receiving a configuration of a first SRS resource set and a second SRS resource set; means for receiving, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and means for transmitting, to the network entity (e.g., the base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g., a base station or a component of the base
• Aspect 32 is the apparatus for wireless communication of aspect 31, further comprising means for implementing any of aspects 1-14.
• Aspect 33 is a computer-readable medium storing computer executable code at a UE, the code when executed by a processor causes the processor to: receive a configuration of a first SRS resource set and a second SRS resource set; receive, from a network entity (e.g., a base station or a component of the base station), DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and transmit, to the network entity (e.g., the base station or a component of the base station), a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g.
• Aspect 34 is the computer-readable medium of aspect 33, wherein the code when executed by the processor causes the processor to implement any of aspects 1-14.
• Aspect 35 is a method of wireless communication at a network entity (e.g., a base station or a component of the base station), comprising: transmitting a configuration of a first SRS resource set and a second SRS resource set; transmitting, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receiving a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g., a base station or a component of the base station
• Aspect 36 is the method of aspect 35, further comprising method for implementing any of aspects 15-28.
• Aspect 37 is an apparatus for wireless communication at a network entity (e.g., a base station or a component of the base station), comprising: means for transmitting a configuration of a first SRS resource set and a second SRS resource set; means for transmitting, for a UE, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and means for receiving a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g., a base station or a component of the base station
• Aspect 38 is the apparatus for wireless communication of aspect 37, further comprising means for implementing any of aspects 15-28.
• Aspect 39 is a computer-readable medium storing computer executable code at a network entity (e.g., the base station or a component of the base station), the code when executed by a processor causes the processor to: transmit a configuration of a first SRS resource set and a second SRS resource set; transmit, for aUE, DCIfor an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receive a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.
• a network entity e.g., the base station or a component of the base station
• Aspect 40 is the computer-readable medium of aspect 39, wherein the code when executed by the processor causes the processor to implement any of aspects 15-28.

Applications Claiming Priority (3)

Publications (1)

Family

ID=81854885

Family Applications (1)

Country Status (6)

• 2022
  • 2022-05-06 TW TW111117148A patent/TW202249522A/zh unknown
  • 2022-05-06 BR BR112023022761A patent/BR112023022761A2/pt unknown
  • 2022-05-06 EP EP22726877.8A patent/EP4335069A1/en active Pending
  • 2022-05-06 KR KR1020237037148A patent/KR20240004388A/ko unknown
  • 2022-05-06 WO PCT/US2022/028200 patent/WO2022236140A1/en active Application Filing
  • 2022-05-06 JP JP2023566839A patent/JP2024517192A/ja active Pending

Also Published As

Similar Documents

Legal Events