Sounding reference signal resource indicators associated with configured grant physical uplink shared channel repetition
Patent Information
- Application Number
- TW111143162
- Authority / Receiving Office
- TW · TW
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-11-10
- Filing Date
- 2022-11-11
- Publication Date
- 2026-09-01
- Estimated Expiration
- 2042-11-10
AI Technical Summary
User equipment (UE) lacks the ability to decide which sounding reference signal (SRS) resources to associate with physical uplink shared channel (PUSCH) repetition sets, leading to incorrect transmission parameters and negatively impacting network performance.
The UE receives a configured grant (CG) PUSCH configuration that includes an SRS resource indicator associated with a PUSCH repetition set, allowing it to determine the appropriate SRS resources and transmission parameters for each repetition set, thereby enabling accurate PUSCH transmissions.
This approach facilitates effective PUSCH repetition sets using transmission parameters associated with SRS resources, improving network performance, particularly in multi-TRP scenarios.
Smart Images

Figure TWG2TB001908322_001 
Figure TWG2TB001908322_002 
Figure TWG2TB001908322_003
Abstract
Description
[Technical Field]
[0001] In general, the various aspects of this disclosure relate to wireless communication, and more specifically, to techniques and apparatus for use in repeatedly associating a probe reference signal indicator with a configured permitted entity uplink shared channel. [Previous Technology]
[0002] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiplexing access technologies that support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile service standard issued by the 3rd Generation Partnership Project (3GPP).
[0003] The multiplexing access technology described above has been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, or global level. New Radio (NR) (which may be referred to as 5G) is a collection of enhancements to the LTE mobile service standard released by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving service, utilizing new spectrum, and integrating with other open standards such as Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful.
[0004] In some cases, one or more entity uplink shared channel (PUSCH) repeat sets may be associated with one or more sounding reference signal (SRS) resource sets, but the UE may not be able to determine which SRS resource sets will be associated with which PUSCH repeat sets. Therefore, the UE may not be able to determine the transmission parameters for the two PUSCH repeat sets, and may therefore be unable to transmit one or more of the PUSCH repeat sets, or may transmit one or more of the PUSCH repeat sets in an invalid manner, thereby negatively impacting network performance. [Summary of the Invention]
[0005] Some of the methods described herein relate to methods for wireless communication performed by a user equipment (UE). The method may include: receiving a permitted (CG) PUSCH configuration including a configuration of at least one probe reference signal (SRS) resource indicator associated with at least one entity uplink shared channel (PUSCH) repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The method may include: determining at least one set of PUSCH transmission parameters for the at least one PUSCH repetition set based at least in part on the determination of the at least one SRS resource set. The method may include: transmitting the at least one PUSCH repetition set based at least in part on the at least one set of PUSCH transmission parameters.
[0006] Some of the methods described herein relate to wireless communication performed by a base station. The method may include: transmitting a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The method may include: receiving at least one PUSCH repetition set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0007] Some of the states described herein relate to a UE for wireless communication. The user equipment may include at least one processor and at least one memory coupled communicatively to the at least one processor to store processor-readable code. When executed by the at least one processor, the processor-readable code may be configured to cause the user equipment to: receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. When executed by the at least one processor, the processor-readable code may be configured to cause the user equipment to: determine at least one set of PUSCH transmission parameters for the at least one PUSCH repetition set, at least in part based on a determination of the at least one SRS resource set. When executed by at least one processor, the processor-readable code can be configured to cause the user equipment to perform the following operation: send at least one set of PUSCH repetitions based at least in part on at least one set of PUSCH transmission parameters.
[0008] Some of the states described herein relate to a base station for wireless communication. The base station may include at least one processor and at least one memory coupled communicatively to the at least one processor to store processor-readable code. When executed by the at least one processor, the processor-readable code may be configured to cause the base station to: transmit a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. When executed by the at least one processor, the processor-readable code may be configured to cause the base station to: receive at least one PUSCH repetition set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0009] Some of the states described herein relate to non-transitory computer-readable media storing instruction sets for wireless communications performed by a UE. When executed by one or more processors of the UE, the instruction sets cause the UE to: receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. When executed by one or more processors of the UE, the instruction sets cause the UE to: determine at least one set of PUSCH transmission parameters for at least one PUSCH repetition set, at least in part based on the determination of at least one SRS resource set. When executed by one or more processors of the UE, the instruction sets cause the UE to: transmit at least one PUSCH repetition set, at least in part based on at least one set of PUSCH transmission parameters.
[0010] Some of the states described herein relate to non-transitory computer-readable media storing instruction sets for wireless communication performed by a base station. When executed by one or more processors of the base station, the instruction set causes the base station to: transmit a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. When executed by one or more processors of the base station, the instruction set causes the base station to: receive at least one PUSCH repetition set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0011] Some of the forms described herein relate to apparatus for wireless communication. The apparatus may include: means for receiving a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The apparatus may include: means for determining at least one set of PUSCH transmission parameters for at least one PUSCH repetition set, at least in part based on a determination of at least one SRS resource set. The apparatus may include: means for transmitting at least one PUSCH repetition set, at least in part based on at least one set of PUSCH transmission parameters.
[0012] Some of the forms described herein relate to apparatus for wireless communication. The apparatus may include: means for transmitting a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The apparatus may include: means for receiving at least one PUSCH repetition set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0013] Various types generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices or processing systems as fully described with reference to the accompanying drawings and description, and as shown by the accompanying drawings and description.
[0014] The features and technical advantages of the examples according to this disclosure have been summarized quite broadly above in order to provide a better understanding of the subsequent embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for performing the same purposes of this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and operation) and the associated advantages will be better understood when considered in conjunction with the accompanying drawings, based on the following description. Each drawing in the accompanying drawings is provided for illustrative and descriptive purposes and is not intended to define a limitation on the scope of the claims.
Implementation Method
[0023] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function provided throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, an apparatus or method may be implemented using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functions, or structures and functions other than those set forth herein or different from those set forth herein. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0024] Several embodiments of a telecommunications system will now be provided with reference to various devices and techniques. These devices and techniques will be described in the following embodiments and illustrated in the accompanying drawings by means of various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether such an element is implemented as hardware or as software depends on the specific application and the design constraints imposed on the overall system.
[0025] Various states generally pertain to the interpretation of the Sounding Reference Signal (SRS) resource indicator in the Radio Resource Control (RRC) configuration to determine the PUSCH transmission parameters for Permissive (CG) Entity Uplink Shared Channel (PUSCH) repetitions for Type 1 configuration. Some states are more specifically about: receiving a CG PUSCH configuration that includes at least one SRS resource indicator associated with at least one PUSCH repetition set, and determining at least one set of PUSCH transmission parameters based at least in part on at least one SRS resource indicator. In some states, the UE may determine at least one set of SRS resources associated with at least one set of PUSCH repetitions. In some states, the UE may determine which SRS resources in the determined at least one set of SRS resources to use. In some states, the UE may determine at least one set of PUSCH transmission parameters based at least in part on the determined SRS resources to be used.
[0026] Specific configurations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some instances, the described techniques can be used to facilitate the transmission of at least one set of PUSCH repetitions using transmission parameters associated with one or more SRS resource sets. In some instances, the described techniques can be used to facilitate multiple transmit / receive point (mTRP) type 1 CG PUSCH repetitions, thereby positively impacting network performance.
[0027] Figure 1 is a diagram illustrating an example of a wireless network according to this disclosure. Wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, etc., or may include elements of a 5G (e.g., NR) network or a 4G network, etc. Wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. Base station 110 is the entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) may include, for example, NR base stations, LTE base stations, Node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, or Transmit / Receive Points (TRPs). Each base station 110 may provide communication coverage for a specific geographic area. In the 3GPP, depending on the context in which the term "cell" is used, the term "cell" may represent the coverage area of base station 110 or the base station subsystem serving that coverage area.
[0028] Base station 110 can provide communication coverage for macrocells, picocells, femtocells, or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. Picocells can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Base station 110 for macrocells can be referred to as a macro base station. Base station 110 for picocells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femto base station or a home base station.
[0029] Wireless network 100 can be a heterogeneous network comprising different types of base stations 110 (such as macro base stations, pico base stations, femto base stations, or repeater base stations). These different types of base stations 110 can have different transmit power levels, different coverage areas, or different effects on interference in wireless network 100. For example, macro base stations can have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and repeater base stations can have lower transmit power levels (e.g., 0.1 to 2 watts). In the example shown in Figure 1, BS 110a can be a macro base station for macro cell 102a, BS 110b can be a pico base station for pico cell 102b, and BS 110c can be a femto base station for femto cell 102c. Base stations can support one or more (e.g., three) cells. Network controller 130 can be coupled to or communicate with a group of base stations 110, and provide coordination and control for such base stations 110. Network controller 130 can communicate with base stations 110 via a backhaul communication link. Base stations 110 can communicate with each other directly or indirectly via wireless or wired backhaul communication links.
[0030] In some instances, the cell may not be stationary, and the geographical area of the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some instances, the base stations 110 may use any suitable transport network to interconnect with each other or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0031] Wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., base station 110 or UE 120) and sending data transmissions to a downstream station (e.g., UE 120 or base station 110). A relay station may be a UE 120 capable of relaying transmissions to other UE 120s. In the example shown in FIG1, BS 110d (e.g., a relay base station) may communicate with BS 110a (e.g., a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. The base station 110 relaying the communication may be referred to as a relay station, relay base station, or repeater.
[0032] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a user unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a wireless phone, a wireless loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smart computer, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio unit), a vehicle component or sensor, a smart instrument / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless media.
[0033] Some UEs 120 may be considered Machine Type Communication (MTC) or Evolved or Enhanced Machine Type Communication (eMTC) UEs. For example, an MTC UE or eMTC UE may include a robot, drone, remote device, sensor, meter, monitor, or location tag capable of communicating with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included in a housing that houses the components of UE 120, such as processor components or memory components. In some instances, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electrically coupled, or electronically coupled.
[0034] Typically, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology or air interface. A frequency can be referred to as a carrier or frequency channel. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0035] In some instances, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more lateral link channels (e.g., without using base station 110 as an intermediary for communication). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such instances, UE 120 may perform scheduling operations, resource selection operations, or other operations that are described elsewhere herein as being performed by base station 110.
[0036] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and files. A similar naming issue sometimes arises with FR2; although different from the Very High Frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the "millimeter wave" band in documents and files.
[0037] Frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands used for these IF bands as the frequency range name FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 or FR2 characteristics, and thus can effectively extend the features of FR1 or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range names FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.
[0038] Considering the above examples, unless otherwise explicitly stated, it should be understood that the term "sub-6 GHz" (if used herein) can broadly refer to frequencies that can be less than 6 GHz, frequencies that can be within FR1, or frequencies that can include intermediate frequency bands. Furthermore, unless otherwise explicitly stated, it should be understood that the term "millimeter wave" (if used herein) can broadly refer to frequencies that can include intermediate frequency bands, frequencies that can be within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies that can be within the EHF band. It is desirable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein can be applied to such modified frequency ranges.
[0039] In some configurations, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repetition set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; determine at least one set of PUSCH transmission parameters for the at least one PUSCH repetition set based at least in part on the determination of the at least one SRS resource set; and transmit the at least one PUSCH repetition set based at least in part on the at least one set of PUSCH transmission parameters. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0040] In some embodiments, base station 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; and receive at least one PUSCH repeat set at least in part based on at least one PUSCH transmission parameter set, wherein at least one PUSCH transmission parameter set is at least in part based on a decision regarding at least one resource set. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.
[0041] Figure 2 is a diagram illustrating communication between an example base station and a UE in a wireless network according to this disclosure. The base station may correspond to base station 110 of Figure 1. Similarly, the UE may correspond to UE 120 of Figure 1. Base station 110 may be equipped with a set of antennas 234a to 234t (such as T antennas (T ≥ 1)). UE 120 may be equipped with a set of antennas 252a to 252r (such as R antennas (R ≥ 1)).
[0042] At base station 110, transmit processor 220 can receive data intended for UE 120 (or a group of UE 120) from data source 212. Transmit processor 220 can select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120, and provide data symbols for UE 120. Transmit processor 220 can process system information (e.g., for Semi-Static Resource Partitioning (SRPI)) and control information (e.g., CQI requests, permission, or upper-layer signaling), and provide management burden symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulated reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, administrative burden symbols, or reference symbols, and provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of data machines 232 (e.g., T data machines) (shown as data machines 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of data machine 232. Each data machine 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or upconvert) the output sampled stream to obtain a downlink signal. Modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0043] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 or other base station 110, and can provide a set of received signals (e.g., R received signals) to a set of data terminals 254 (e.g., R data terminals) (shown as data terminals 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of data terminal 254. Each data terminal 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each data terminal 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain the received symbols from data terminal 254, can perform MIMO detection on the received symbols (if applicable), and can provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data slot 260, and provide decoded control and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), or CQI, etc. In some instances, one or more components of the UE 120 may be included in a housing.
[0044] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. For example, the network controller 130 may include one or more devices in the core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0045] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more antenna element sets, or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more antenna element sets, or one or more antenna arrays, etc. Antenna panels, antenna groups, antenna element sets, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more components of FIG2.
[0046] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, or CQI). Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some instances, modem 254 of UE 120 may include modulator and demodulator. In some instances, UE 120 includes transceiver. Transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The processor (e.g., controller / processor 280) and memory 282 may use a transceiver to perform various forms of any of the methods described herein.
[0047] At base station 110, uplink signals from UE 120 or other UEs can be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data slot 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some instances, modem 232 of base station 110 may include modulator and demodulator. In some instances, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. Processors (e.g., controller / processor 240) and memory 242 may be used with the transceiver to perform various forms of any of the methods described herein.
[0048] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, or any other component of FIG. 2 may perform one or more techniques associated with the SRS indicator associated with the CG PUSCH repetition, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, or any other component of FIG. 2 may perform or direct the operation of, for example, process 500 of FIG. 5, process 600 of FIG. 6, or other processes as described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some instances, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors of base station 110 or UE 120 (e.g., directly, or after compilation, translation, or interpretation), they may cause one or more processors, UE 120, or base station 110 to perform or direct operations such as process 500 of FIG. 5, process 600 of FIG. 6, or other processes as described herein. In some instances, the execution instructions may include run instructions, translation instructions, compilation instructions, or interpretation instructions, etc.
[0049] In some embodiments, the UE includes: a component for receiving a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; a component for determining at least one set of PUSCH transmission parameters for at least one PUSCH repeat set based at least in part on the determination of at least one SRS resource set; or a component for transmitting at least one PUSCH repeat set based at least in part on at least one set of PUSCH transmission parameters. Components for enabling the UE to perform the operations described herein may include one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receiver processor 258, transmitter processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.
[0050] In some embodiments, the base station includes: a component for transmitting a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; or a component for receiving at least one PUSCH repeat set at least in part based on at least one PUSCH transmission parameter set, wherein at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set. The components that enable the base station to perform the operations described herein may include one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.
[0051] Base station 110 may configure UE 120 to have one or more SRS resource sets to allocate resources for SRS transmissions performed by UE 120. For example, the configuration for the SRS resource sets may be indicated in Radio Resource Control (RRC) messages (e.g., RRC configuration messages or RRC reconfiguration messages). An SRS resource set may include one or more SRS resources, which may include time resources or frequency resources (e.g., time slots, symbols, resource blocks, or periods of time resources). The SRS resource indicator (SRI) field in the downlink control information (DCI) transmission may be used to indicate the SRS resources to be used for uplink transmissions. The SRI may indicate the uplink transmission rank and precoder set available for uplink transmissions by the UE.
[0052] An SRS resource may include one or more antenna ports on which SRS is to be transmitted (e.g., in time-frequency resources). Therefore, the configuration for an SRS resource set may indicate one or more time-frequency resources on which SRS is to be transmitted, and may indicate one or more antenna ports on which SRS is to be transmitted within such time-frequency resources. In some cases, the configuration for an SRS resource set may indicate use cases for the SRS resource set (e.g., indicated in the SRS-ResourceSet information element). For example, the SRS resource set may have use cases for antenna switching, codebooks, non-codebooks, or beam management.
[0053] The antenna switching SRS resource set can be used to indicate the downlink CSI that is reciprocal between the uplink and downlink channels. For example, when there is reciprocity between the uplink and downlink channels, base station 110 can use the antenna switching SRS (e.g., the SRS transmitted using resources of the antenna switching SRS resource set) to obtain the downlink CSI (e.g., to determine the downlink precoder to be used for communication with UE 120).
[0054] When base station 110 indicates an uplink precoder to UE 120, the codebook SRS resource set can be used to indicate the uplink CSI. For example, when base station 110 is configured to indicate an uplink precoder to UE 120 (e.g., using a precoder codebook), base station 110 can use the codebook SRS (e.g., an SRS transmitted using resources from the codebook SRS resource set) to obtain the uplink CSI (e.g., determining the uplink precoder to indicate to UE 120 and used by UE 120 to communicate with base station 110). In some configurations, at least for the codebook SRS, virtual ports with maximum transmit power (e.g., a combination of two or more antenna ports) can be supported.
[0055] The codebook SRS resource set can also be used to facilitate codebook-based Physical Uplink Shared Channel (PUSCH) transmission. In codebook-based PUSCH transmission, the UE can be configured to have a unique SRS resource set with a "Use" indicator set to "Codebook". In codebook-based PUSCH transmission, a maximum of four SRS resources within the set can be configured for the UE. Each SRS resource RRC can be configured to have multiple ports (e.g., using the parameter nrofSRS-Ports). The SRI field in the DCI of the scheduled PUSCH can indicate an SRS resource. The number of ports configured for the indicated SRS resource determines the number of antenna ports used for PUSCH transmission. In codebook-based PUSCH transmission, the PUSCH transmission is transmitted using the same spatial domain filter (e.g., uplink beam) as the indicated SRS resource. The number of transport layers (rank) for the scheduled PUSCH and the transmitted precoding matrix indicator (TPMI) are determined based on individual DCI fields.
[0056] When UE 120 selects an uplink precoder, it can use a non-codebook SRS resource set to indicate the uplink CSI (e.g., instead of the uplink precoder indicated by base station 110 to be used by UE 120). For example, when UE 120 is configured to select an uplink precoder, base station 110 can use a non-codebook SRS (e.g., an SRS transmitted using resources from a non-codebook SRS resource set) to obtain the uplink CSI. In this case, the non-codebook SRS can be precoded using the precoder selected by UE 120 (e.g., which may be indicated to base station 110).
[0057] Non-codebook SRS resource sets can also be used to facilitate non-codebook-based PUSCH transmissions. In non-codebook-based PUSCH transmissions, the UE can be configured to have a unique SRS resource set with a "Use" indicator set to "Non-codebook". In non-codebook PUSCH transmissions, a maximum of four SRS resources within the set can be configured for the UE. Each SRS resource has one port. The SRI field in the DCI of the scheduled PUSCH transmission can indicate one or more SRS resources. The number of indicated SRS resources determines the rank of the scheduled PUSCH transmission, and the PUSCH transmission is transmitted using the same precoder and the same spatial domain filter (e.g., beam) as the indicated SRS resources.
[0058] In some cases, wireless communication standards may specify one or more SRI indicator tables to facilitate SRI signal transmission. The SRI indicator table can be used to identify SRS resources based on the number of SRS resources indicated by the SRI, and to indicate the number of bits used to transmit the SRI. For example, according to a wireless communication standard, the number of bits used to transmit the SRI can be calculated as [log 2(N SRS)] bits based on the SRI table, where the indicator is set to the codebook, and N SRS is the number of SRS resources configured in the SRS resource set configured by the SRS resource set list (e.g., represented by the higher-level parameter srs-ResourceSetToAddModList). Table 1 depicts an example of an SRI table for codebook-based PUSCH transmission, where N SRS = 4. Bit fields mapped to the index SRI(s),N SRS =4 0 0 1 1 2 2 3 3 Table 1
[0059] In some cases, according to wireless communication standards, based on the SRI table, the number of bits used to transmit the SRI can be calculated as individual bits, where an indicator is used to indicate the non-coding book, Lmax indicates the maximum number of transport layers, and NSRS is the number of SRS resources configured in the SRS resource set configured by the SRS resource set list (e.g., represented by the higher-layer parameter srs-ResourceSetToAddModList). Table 2 depicts an example of an SRI table for PUSCH transmission based on the non-coding book, where Lmax = 4. Bit fields mapped to the index SRI(s), N SRS =2 Bit fields mapped to the index SRI(s), N SRS =3 Bit fields mapped to the index SRI(s), N SRS =4 0 0 0 0 0 0 1 1 1 1 1 1 2 0,1 2 2 2 2 3 reserve 3 0,1 3 3 4 0,2 4 0,1 5 1,2 5 0,2 6 0,1,2 6 0,3 7 reserve 7 1,2 8 1,3 9 2,3 10 0,1,2 11 0,1,3 12 0,2,3 13 1,2,3 14 0,1,2,3 15 reserve Table 2
[0060] As indicated above, when the PUSCH is scheduled via DCI (e.g., in the case of dynamically permitted PUSCH (DG-PUSCH)) or initiated via DCI (e.g., in the case of Type 2 CG PUSCH), DCI transmissions can be used to send SRIs for codebook-based or non-codebook-based PUSCHs. However, for Type 1 CG PUSCH, all parameters are configured by RRC (e.g., not indicated in DCI). In such cases, the SRS resource indicator can be the RRC parameter "srs-ResourceIndicator," which can be configured as part of the CG configuration in the CG configuration parameter ("rrc-ConfiguredUplinkGrant"). The SRS resource indicator determines one or more SRS resources associated with the PUSCH transmission, which in turn determine the number of beams, precoding, and PUSCH ports for the PUSCH transmission of Type 1 CG PUSCH. The RRC parameter "srs-ResourceIndicator" can be interpreted based on the specified SRI table (e.g., Table 1 or Table 2 above). The interpretation may depend on the comparison between codebook-based PUSCH and non-codebook-based PUSCH, and the number of SRS resources in the SRS resource set (similar to the case of DG-PUSCH).
[0061] Some wireless communication standards specify DCI format 0_2 for scheduling PUSCH. The purpose of DCI format 0_2 is to reduce the DCI size by reducing the number of bits required for each DCI field through RRC-based configuration. SRS resource sets (for both codebook and non-codebook PUSCHs) can be configured individually for PUSCHs scheduled using DCI format 0_2. The SRS resource set list represented by the RRC parameter srs-ResourceSetToAddModListDCI-0-2 can be used for DCI format 0_2 (similar to srs-ResourceSetToAddModList for DCI format 0_1). For codebook PUSCHs, a single SRS resource set set to be used and set as "codebook" can be configured within srs-ResourceSetToAddModListDCI-0-2. For non-codebook PUSCHs, a single SRS resource set set to be used and set as "non-codebook" can be configured within srs-ResourceSetToAddModListDCI-0-2.
[0062] A smaller number of SRS resources in the SRS resource set can be configured for srs-ResourceSetToAddModListDCI-0-2, which can result in a smaller SRI bit width. Each SRS resource in the SRS resource set for DCI format 0_2 can be the first SRS resource in the SRS resource set for DCI format 0_1. This prevents an increase in UE complexity because for DCI format 0_2, a subset of the SRS resources in the SRS resource set configured for DCI format 0_1 can be configured.
[0063] Figure 3 is a diagram illustrating an example 300 of multi-TRP (mTRP) communication (sometimes referred to as multi-panel communication) according to this disclosure. As shown in Figure 3, UE 305 can communicate with multiple TRPs 310. In some cases, TRP 310 can be, include, or be included in base station 110 as described above in conjunction with Figures 1 and 2. For example, different TRPs 310 can be included in different base stations 110. In some cases, multiple TRPs 310 can be included in a single base station 110. In some cases, base station 110 can include a control unit (CU) (e.g., a CU integrating access and backhaul (IAB) networks) or one or more distributed units (DUs) (e.g., one or more TRPs 310). In some cases, TRP 310 can be referred to as a cell, panel, antenna array, or array. UE 305 may be, include, or be included in UE 120 as described above in conjunction with Figures 1 and 2.
[0064] In some configurations, multiple TRPs 310 may transmit communications (e.g., the same communication or different communications) using different quasi-co-address (QCL) relationships (e.g., different spatial parameters, different Transmission Configuration Indicator (TCI) states, different precoding parameters, or different beamforming parameters) in the same Transmission Time Interval (TTI) (e.g., time slot, micro-time slot, subframe, or symbol) or in different TTIs. In some configurations, the TCI state may be used to indicate one or more QCL relationships. TRPs 310 may be configured to provide transmissions to UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 310).
[0065] Multiple TRPs 310 (shown as TRP A and TRP B) can communicate with the same UE 305 in a coordinated manner (e.g., using coordinated multicast) to improve reliability or increase throughput. Different TRPs 310 may communicate with the UE 305 using different QCL relationships (e.g., different TCI states), different DMRS ports, or different layers (e.g., different layers of multi-layer communication).
[0066] In a multi-TRP transmission mode, one or more entity downlink control channels (PDCCHs) can be used to schedule downlink data communication for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH), or for uplink data communication for multiple corresponding entity uplink shared channels (PUSCHs). In this case, for example, PDCCH 315 sent by the first TRP 310 (TRP A) can be scheduled as a first PUSCH (PUSCH 1) 320 for sending uplink data to TRP A 310 and a second PUSCH (PUSCH 2) 325 for sending uplink data to the second TRP 310 (TRP B).
[0067] In some wireless communication standards, PUSCH transmissions can be configured as PUSCH repetitions. As used herein, the term "repetition" is used to refer to the initial transmission and also to repeated transmissions of the initial transmission. For example, if UE 305 is configured to send four repetitions, UE 305 can send the initial transmission and can send three repeated transmissions of that initial transmission. Therefore, each transmission (whether it is the initial transmission or a retransmission) is considered a repetition. Repetitions can be sent at transmission times (sometimes referred to as transmission instances).
[0068] PUSCH repeats can be configured by PDCCH 315 to be transmitted using Time Division Multiplexing (TDM), where PUSCH repeats correspond to different transmission parameters (beam / spatial relationship, power control, precoding). In some cases, PUSCH repeats scheduled by a single DCI (e.g., PDCCH 315) can belong to two sets, each with its own transmission parameters. The two PUSCH repeat sets can be associated with two SRS resource sets. For example, as shown in Figure 3, PUSCH 1 320 can represent a first PUSCH repeat set, and PUSCH 2 325 can represent a second PUSCH repeat set. UE 305 can transmit PUSCH 1 repeat to TRP A 310 using the first PUSCH transmission parameter set (e.g., a first beam or a first power control parameter set). UE 305 can transmit PUSCH 2 repeat to TRP B 310 using the second PUSCH transmission parameter set (e.g., a second beam or a second power control parameter set). A first PUSCH repeat set (PUSCH 1) can be associated with a first SRS resource set, and a second PUSCH repeat set (PUSCH 2) can be associated with a second SRS resource set. For example, a DCI transmission can use two corresponding SRI fields to indicate two beams and two sets of power control parameters.
[0069] As shown in Figure 3, UE 305 determines, based on the SRS resource set list, which SRS resource sets are associated with the corresponding sets of PUSCH repeats PUSCH 1 320 and PUSCH 2 325. As indicated above, a first SRS resource set list (e.g., srs-ResourceSetToAddModList) 330 may list one or more SRS resource sets, and a second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2) 335 may list one or more SRS resource sets. For example, as shown, the first SRS resource set list 330 may list SRS resource set A 340 and SRS resource set B 345, and the second SRS resource set list 335 may list SRS resource set C 350 and SRS resource set D 355. SRS resource set A 340 may include, for example, SRS resource 0 (represented as "SRS R0"), SRS resource 1 (represented as "SRS R0"), and SRS resource 2 (represented as "SRS R2"). SRS resource set B 345 may include, for example, SRS resource 3 (represented as "SRS R3"), SRS resource 4 (represented as "SRS R4"), and SRS resource 5 (represented as "SRS R5"). As indicated above, the SRS resource sets listed in the second SRS resource set list 335 may be subsets of the SRS resource sets listed in the first SRS resource set list 330. For example, as shown, SRS resource set C 350 may be a subset of SRS resource set A 340 (where SRS resource set C includes SRS R0 and SRS R1), and SRS resource set D 355 may be a subset of SRS resource set B 345 (where SRS resource set D 355 includes SRS R3 and SRS R4).
[0070] To determine which SRS resource set listed in the SRS resource set list is associated with each PUSCH repeating set, the SRS resource set with the lower SRS resource set identifier (ID) value is the first SRS resource set (e.g., the SRS resource set associated with PUSCH 1 320), and the SRS resource set with the higher SRS resource set ID is the second SRS resource set (e.g., the SRS resource set associated with PUSCH 2 325). In some cases, two SRS resource sets may have the same number of SRS resources. The SRS resources to be used can be determined based on the SRS resource indicator. For the case of Type 1 CG PUSCH (e.g., where there is no transmitted DCI or no SRI field in the transmitted DCI), the wireless communication standard specifies two RRC parameters to be used as the SRS resource indicator. The first SRS resource indicator srs-ResourceIndicator may be associated with a first SRS resource set (e.g., the SRS resource set associated with PUSCH 1 320), and the second SRS resource indicator srs-ResourceIndicator2 may be associated with a second SRS resource set (e.g., the SRS resource set associated with PUSCH 2 325).
[0071] Two (first and second) SRS resource sets for mTRP PUSCH can be defined for DCI format 0_1 and DCI format 0_2 respectively, and both resource sets can be used with CG PUSCH configured by RRC. Three alternative scenarios are possible.
[0072] In the first case (which may be referred to as "Case 1"), two SRS resource sets are configured in each of the first SRS resource set list (e.g., srs-ResourceSetToAddModList) and the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2). Both DCI formats 0_1 and 0_2 can schedule mTRP PUSCH (repeated PUSCH associated with different SRS resource sets, different beams, different precoders, or different power controls, etc.). Both DCI formats 0_1 and 0_2 have two SRI fields. The first SRS resource set for DCI format 0_2 consists of the first N SRS,0_2 SRS resources of the first SRS resource set for DCI format 0_1. The second SRS resource set for DCI format 0_2 consists of the first N SRS,0_2 SRS resources of the second SRS resource set for DCI format 0_1.
[0073] In the second case (which may be referred to as "Case 2"), one SRS resource set is configured in the first SRS resource set list (e.g., srs-ResourceSetToAddModList), but two SRS resource sets are configured in the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2). Only DCI format 0_2 can schedule mTRP PUSCH. DCI format 0_1 can only schedule PUSCH duplicates associated with one SRS resource set. DCI format 0_2 has two SRI fields, and DCI format 0_1 has one SRI field. The first SRS resource set for DCI format 0_2 consists of the first N SRS,0_2 SRS resources of the SRS resource set for DCI format 0_1.
[0074] In the third case (which may be referred to as "Case 3"), two SRS resource sets are configured in the first SRS resource set list (e.g., srs-ResourceSetToAddModList), but only one SRS resource set is configured in the second SRS resource set list (srs-ResourceSetToAddModListDCI-0-2). Only DCI format 0_1 can schedule mTRP PUSCH. DCI format 0_2 can only schedule PUSCH duplicates associated with one SRS resource set. DCI format 0_1 has two SRI fields, and DCI format 0_2 has one SRI field. The SRS resource set used for DCI format 0_2 consists of the first N SRS,0_2 SRS resources of the first SRS resource set used for DCI format 0_1.
[0075] For Type 1 CG PUSCH, UE 305 can identify PUSCH transmission parameters based on the interpretation of SRS resource indicator RRC parameters (e.g., srs-ResourceIndicator and srs-ResourceIndicator2 (if configured)) based on the number of SRS resources in the first SRS resource set and the second SRS resource set, respectively. However, for identifying PUSCH transmission parameters, it is unclear whether the SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList configured for DCI format 0_1) or the SRS resource set in the second SRS resource set (e.g., srs-ResourceSetToAddModListDCI-0-2 configured for DCI format 0_2) should be used. Furthermore, even if the number of SRS resources in the first SRS resource set and the second SRS resource set is the same, the number of SRS resources in the SRS resource set used for DCI format 0_2 may be less than the number of SRS resources in the SRS resource set used for DCI format 0_1. This may affect the interpretation of the first SRS resource indicator (e.g., srs-ResourceIndicator) and (if configured) the second SRS resource indicator (e.g., srs-ResourceIndicator2) used for type 1 CG PUSCH.
[0076] For example, for Type 1 CG PUSCH, the UE may not be able to determine which SRS resource sets will be associated with the first PUSCH repeat set or the second PUSCH repeat set. In some instances, only the first SRS resource indicator (e.g., srs-ResourceIndicator) can be configured for Type 1 CG PUSCH (e.g., no second SRS resource indicator is configured). In such cases, all PUSCH repeats are associated with the first SRS resource set, but there is no ability for the UE to determine which SRS resource set will be considered the first SRS resource set (e.g., the SRS resource set associated with the first PUSCH repeat set). The UE may not be able to determine the transmission parameters for the PUSCH repeats, and therefore may be unable to send PUSCH repeats or may send PUSCH repeats in an invalid manner, thus negatively impacting network performance.
[0077] In other instances, both the first SRS resource indicator (e.g., srs-ResourceIndicator) and the second SRS resource indicator (e.g., srs-ResourceIndicator2) are configured for Type 1 CG PUSCH. In such cases, two PUSCH repeat sets are associated with two SRS resource sets respectively, but there is no ability for the UE to determine which SRS resource sets will be considered as the first SRS resource set (e.g., the SRS resource set associated with the first PUSCH repeat set) and the second SRS resource set (e.g., the SRS resource set associated with the second PUSCH repeat set). The UE may not be able to determine the transmission parameters for the two PUSCH repeat sets, and therefore may be unable to transmit one or more of these PUSCH repeat sets, or may transmit one or more of these PUSCH repeat sets in an invalid manner, thereby negatively impacting network performance.
[0078] Various states generally concern the interpretation of SRS resource indicators in the RRC configuration to determine the PUSCH transmission parameters used for Type 1 CG PUSCH repeats. Some states are more specifically concerned with: receiving a CG PUSCH configuration that includes at least one SRS resource indicator associated with at least one PUSCH repeat set, and determining at least one set of PUSCH transmission parameters based at least in part on at least one SRS resource indicator. In some states, the UE may determine at least one set of SRS resources associated with at least one PUSCH repeat set. In some states, the UE may determine which SRS resources in the determined at least one set of SRS resources to use. In some states, the UE may determine at least one set of PUSCH transmission parameters based at least in part on the determined SRS resources to be used.
[0079] Specific forms of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some instances, the described techniques can be used to facilitate the transmission of at least one set of PUSCH repetitions using transmission parameters associated with one or more SRS resource sets. In some instances, the described techniques can be used to facilitate mTRP type 1 CG PUSCH repetitions, thereby positively impacting network performance.
[0080] Figure 4 is a diagram illustrating an instance 400 associated with an SRS resource indicator that is repeatedly associated with the same CG PUSCH according to this disclosure. As shown in Figure 4, UE 405 and base station 410 can communicate with each other. For example, UE 405 can be or is similar to UE 120 depicted in Figures 1 and 2. Base station 410 can be or is similar to base station 110 depicted in Figures 1 and 2.
[0081] In the first operation 415, base station 410 can send an SRS configuration, and UE 405 can receive an SRS configuration. In some configurations, base station 410 can send the SRS configuration by sending an RRC message containing the SRS configuration. The SRS configuration can configure one or more SRS resources, which can be organized into SRS resource sets, as explained above. In some configurations, as shown, the SRS configuration can include an indication 420 corresponding to a list of SRS resource sets. For example, indication 420 can include an indication of several SRS resource sets listed in a first SRS resource set list 425 or several SRS resources listed in a second SRS resource set list 430. In the illustrated example, indication 420 can indicate that the first SRS resource set list 425 lists SRS resource set A 435 and SRS resource set B 440, and the second SRS resource set list 430 lists SRS resource set C 445 and SRS resource set D 450. The SRS configuration may also include a configuration 455 of at least one set of transmission parameters corresponding to each SRS resource (e.g., SRS R0, SRS R1, SRS R2, SRS R3, SRS R4, and SRS R5) included in the listed SRS resource sets. In some cases, at least one SRS resource set listed in the second SRS resource set list 430 may be a subset of the corresponding SRS resource set listed in the first SRS resource set list 425.
[0082] In the second operation 460, base station 410 can send a CG PUSCH configuration, and UE 405 can receive a CG PUSCH configuration. The CG PUSCH configuration can be a type 1 CG PUSCH configuration (where all PUSCH repeat parameters are configured by an RRC message). In some states, base station 410 can send the CG PUSCH configuration by sending an RRC message containing an SRS configuration. In some states, the CG PUSCH configuration can include a configuration 465 for a first PUSCH repeat set. In some states, configuration 465 can indicate that the first PUSCH repeat set is associated with a first SRS resource set. The CG PUSCH configuration can also include a configuration 470 for a second PUSCH repeat set. Configuration 470 can indicate that the second PUSCH repeat set is associated with a second SRS resource set.
[0083] The CG PUSCH configuration may also include at least one SRS resource indicator 475. The at least one SRS resource indicator may be associated with at least one PUSCH repeat set and may indicate at least one SRS resource corresponding to the at least one SRS resource set. The at least one SRS resource set may be listed in at least one of a first SRS resource set list 425 or a second SRS resource set list 430. For example, the at least one SRS resource indicator 475 may include a first SRS resource indicator (e.g., srs-ResourceIndicator) indicating which SRS resources in the first SRS resource set (the SRS resource set associated with the first PUSCH repeat set) should be used. The at least one SRS resource indicator 475 may include a second SRS resource indicator (e.g., srs-ResourceIndicator2) indicating which SRS resources in the second SRS resource set (the SRS resource set associated with the second PUSCH repeat set) should be used.
[0084] In the third operation 480, UE 405 may determine at least one set of PUSCH transmission parameters for at least one PUSCH repetition set. UE 405 may determine at least one set of PUSCH transmission parameters based at least in part on a determination of at least one SRS resource set. In some cases, for example, UE 405 may determine at least one set of PUSCH transmission parameters based at least in part on a determination of at least one SRS resource set. UE 405 may determine at least one SRS resource set based at least in part on a determination of which configured SRS resource sets correspond to a first SRS resource set or a second SRS resource set, respectively. In the illustrated example, UE 405 may determine that the first SRS resource set (e.g., the SRS resource set associated with the first PUSCH repetition set) is resource set A, and the second SRS resource set (e.g., the SRS resource set associated with the second PUSCH repetition set) is resource set B.
[0085] According to the various configurations described herein, UE 405 may determine at least one SRS resource set based on one or more rules specified in the radio communication standard. For example, one or more rules may be classified according to a first case or a second case, in which only a first SRS resource indicator (e.g., srs-ResourceIndicator) is configured for type 1 CG PUSCH, and in a second case, a first SRS resource indicator (e.g., srs-ResourceIndicator) and a second SRS resource indicator (e.g., srs-ResourceIndicator2) are configured for type 1 CG PUSCH. In the first case, all PUSCH repetitions are associated with one SRS resource set, and in the second case, the first PUSCH repetition set is associated with the first SRS resource set, and the second PUSCH repetition set is associated with the second SRS resource set.
[0086] In a first case, at least one SRS resource indicator 475 may include a unique SRS resource indicator, and at least one SRS resource set may include a unique SRS resource set. In some states, according to one or more rules, UE 405 may determine at least one SRS resource set as the first SRS resource set listed in the first SRS resource set list 425 that has a usage indicator set to either a codebook or a non-codebook (e.g., SRS resource set A 435), based at least in part on the inclusion of a unique SRS resource set in the first SRS resource set list 425. In some states, the first SRS resource set may be the unique SRS resource set listed in the first SRS resource set list 425. In some other states, the first SRS resource set listed in the first SRS resource set list 425 may include an SRS resource set with a lower SRS resource set ID value compared to any other SRS resource set identifier (ID) value associated with any other SRS resource set listed in the first SRS resource set list 425. For example, the SRS resource set ID associated with SRS resource set A 435 can have a lower value than the SRS resource set ID associated with SRS resource set B 440.
[0087] In some configurations, UE 405 may, at least in part, determine at least one SRS resource set as the first SRS resource set listed in the second SRS resource set list 430 that has a usage indicator set to either a codebook or a non-codebook, based on one or more rules. This determination is made based on the unique inclusion of one SRS resource set in the first SRS resource set listed in the second SRS resource set list 430. In some configurations, the first SRS resource set listed in the second SRS resource set list 430 may be the only SRS resource set listed in the second SRS resource set list 430. In some other configurations, the first SRS resource set listed in the second SRS resource set list 430 may include an SRS resource set with a lower SRS resource set ID value compared to any other SRS resource set ID value associated with any other SRS resource set listed in the second SRS resource set list 430.
[0088] In some configurations, the CG PUSCH configuration may include indicator bits according to one or more rules, and the UE 405 may determine, at least in part, that at least one SRS resource set is a unique SRS resource set (wherein the unique SRS resource set includes the first SRS resource set listed in the first SRS resource set list 425) based at least partially on the indicator bits having a first value, or at least in part on the indicator bits having a second value, that at least one SRS resource set is the first SRS resource set listed in the second SRS resource set list 430. In some configurations, the UE 405 may determine, at least in part, that at least one SRS resource set is an SRS resource set associated with the SRS resource set ID associated with the unique SRS resource set based at least in part on an explicit indicator associated with the uplink allowance parameter of the CG PUSCH configuration that indicates the SRS resource set ID.
[0089] In the second case described above for classifying one or more rules, at least one SRS resource indicator 475 may include a first SRS resource identifier and a second SRS resource indicator. At least one PUSCH repeat set may include a first PUSCH repeat set associated with a first SRS resource set and a second PUSCH repeat set associated with a second SRS resource set, and the first SRS resource set and the second SRS resource set may be listed in at least one of the first SRS resource set list 425 or the second SRS resource set list 430.
[0090] In some configurations, UE 405 may determine at least one SRS resource set based at least in part on a decision that the first SRS resource set is included in the first SRS resource set list 425 and has a first usage indicator set to either a codebook or a non-codebook (e.g., SRS resource set A 435), and a decision that the second SRS resource set is included in the first SRS resource set list 425 and has a second usage indicator set to either a codebook or a non-codebook (SRS resource set B 440). In some configurations, UE 405 may determine at least one SRS resource set based at least in part on the first SRS resource set list 425 that lists the second SRS resource set. In some other configurations, UE 405 may determine at least one SRS resource set based at least in part on the first SRS resource set list 425 that lists only the first SRS resource set. For example, a first SRS resource indicator (e.g., srs-ResourceIndicator) may be associated with a first SRS resource set in the first SRS resource set list 425, and if the first SRS resource set list 425 lists a second SRS resource set, then a second SRS resource indicator (e.g., srs-ResourceIndicator2) may be associated with the second SRS resource set in the first SRS resource set list 425. If the first SRS resource set list 425 lists only one SRS resource set, then the second SRS resource indicator may be associated with the second SRS resource set in the second SRS resource set list 430.
[0091] In some configurations, the first SRS resource set and the second SRS resource set may both originate from the first SRS resource set list 425 or both originate from the second SRS resource set list 430, according to one or more rules. For example, UE 405 may determine at least one SRS resource set based at least in part on the determination that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list 430 and has a first usage indicator set to either a codebook or a non-codebook, and the determination that the second SRS resource set is included in the second SRS resource set list 430 and has a second usage indicator set to either a codebook or a non-codebook. In some other configurations, UE 405 may determine at least one SRS resource set based at least in part on both the first SRS resource set and the second SRS resource set listed in the second SRS resource set list 430.
[0092] In some other configurations, the CG PUSCH configuration may include indicator bits, and the UE 405 may determine at least one SRS resource set based at least in part on the following: determining the first SRS resource set as the first SRS resource set listed in the first SRS resource set list 425 based at least in part on the indicator bits having a first value, or determining the first SRS resource set as the first SRS resource set listed in the second SRS resource set list 430 based at least in part on the indicator bits having a second value. In some configurations, the CG PUSCH configuration may include indicator bits, and the UE 405 may determine at least one SRS resource set based at least in part on the following: determining the second SRS resource set as the second SRS resource set listed in the first SRS resource set list 425 based at least in part on the indicator bits having a first value, or determining the second SRS resource set as the second SRS resource set listed in the second SRS resource set list 430 based at least in part on the indicator bits having a second value.
[0093] In some configurations, a first SRS resource set ID may correspond to a first SRS resource set, and a second SRS resource set ID may correspond to a second SRS resource set. In some configurations, based on one or more rules, UE 405 may determine at least one SRS resource set to include a first SRS resource set associated with a first SRS resource set ID and a second SRS resource set associated with a second SRS resource set ID. In some configurations, UE 405 may determine at least one SRS resource set based at least in part on an explicit indicator associated with the uplink allowance parameters configured in the CG PUSCH that indicates the first SRS resource set ID and the second SRS resource set ID.
[0094] The third operation 480 may also include: determining at least one SRS resource indicator 475 to indicate to the UE 405 which SRS resources in at least one resource set will be used to determine the PUSCH transmission parameters. In some cases, the UE 405 may determine the SRS resources to be used based at least in part on one or more SRI tables specified by a radio communication standard (e.g., Table 1 or Table 2 above). The third operation 480 may also include: determining at least one PUSCH transmission parameter based at least in part on the SRS configuration of the determined SRS resources.
[0095] In the fourth operation 485, UE 405 may transmit at least one PUSCH repetition set, and base station 410 may receive at least one PUSCH repetition set. UE 405 may transmit at least one PUSCH repetition set using at least one determined PUSCH transmission parameter set, as described above. For example, in some cases, UE 405 may transmit a first PUSCH repetition set using a first PUSCH transmission parameter set and a second PUSCH repetition set using a second PUSCH transmission parameter set.
[0096] Figure 5 is a flowchart illustrating an example procedure 500 performed by a UE, for example, according to this disclosure. Example procedure 500 is an instance of a UE (e.g., UE 405) performing an operation associated with an SRS resource indicator that is repeatedly associated with CG PUSCH.
[0097] As shown in FIG5, in some states, process 500 may include: receiving a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list (block 510). For example, a UE (such as by using a communication manager 140 or a receiving unit 702 depicted in FIG. 7) may receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, wherein the at least one SRS resource indicator indicates at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list, as described above.
[0098] As further shown in FIG5, in some cases, process 500 may include: determining at least one set of PUSCH transmission parameters for at least one PUSCH repetition set based at least in part on a decision of at least one SRS resource set (block 520). For example, a UE (such as by using communication manager 140 or decision unit 708 depicted in FIG7) may determine at least one set of PUSCH transmission parameters for at least one PUSCH repetition set based at least in part on a decision of at least one SRS resource set, as described above.
[0099] As further shown in FIG5, in some cases, process 500 may include: transmitting at least one set of PUSCH repetitions based at least partially on at least one set of PUSCH transmission parameters (block 530). For example, a UE (such as by using communication manager 140 or transmission component 704 depicted in FIG7) may transmit at least one set of PUSCH repetitions based at least partially on at least one set of PUSCH transmission parameters, as described above.
[0100] Process 500 may include additional patterns, such as any single pattern or any combination of patterns described below or in conjunction with one or more other processes described elsewhere herein.
[0101] In the first additional state, at least one SRS resource indicator includes a unique SRS resource indicator, and at least one SRS resource set includes a unique SRS resource set.
[0102] In the second additional state sample, either alone or in combination with the first state sample, the process 500 includes: determining, at least in part, that at least one SRS resource set is a first SRS resource set listed in the first SRS resource set list and has a usage indicator set to codebook or non-codebook, based on at least one unique SRS resource set included in the first SRS resource set list.
[0103] In the third additional state sample, either alone or in combination with the second state sample, the first SRS resource set is the only SRS resource set listed in the first SRS resource set list.
[0104] In the fourth additional state sample, either alone or in combination with one or more states from the second to the third state sample, the first SRS resource set listed in the first SRS resource set list includes: an SRS resource set that has a lower SRS resource set ID value compared to any other resource set ID value associated with any other SRS resource set listed in the first SRS resource set list.
[0105] In the fifth additional state sample, either alone or in combination with one or more of the first to fourth state samples, the process 500 includes: determining, at least in part, that at least one SRS resource set is a first SRS resource set listed in the second SRS resource set list that has a usage indicator set to codebook or non-codebook, based on at least one unique SRS resource set included in the first SRS resource set listed in the second SRS resource set list.
[0106] In the sixth additional state sample, either alone or in combination with the fifth state sample, the first SRS resource set listed in the second SRS resource set list is the only SRS resource set listed in the second SRS resource set list.
[0107] In the seventh additional state sample, either alone or in combination with one or more states sample from the fifth to the sixth state sample, the first SRS resource set listed in the second SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set ID value associated with any other SRS resource set listed in the second SRS resource set list.
[0108] In the eighth additional state, either alone or in combination with the first state, the CG PUSCH configuration includes an indicator bit, and the process 500 includes: determining that at least one SRS resource set is a unique SRS resource set, wherein a unique SRS resource set includes: a first SRS resource set listed in a first SRS resource set list based at least in part on the indicator bit having a first value; or a first SRS resource set listed in a second SRS resource set list based at least in part on the indicator bit having a second value.
[0109] In the ninth additional state sample, either alone or in combination with the first state sample, process 500 includes: determining, at least in part, that at least one SRS resource set is an SRS resource set associated with an SRS resource set ID associated with the same unique SRS resource set, based on an explicit indicator associated with an uplink allowance parameter configured in the CG PUSCH that indicates the SRS resource set ID.
[0110] In the tenth additional state sample, at least one SRS resource indicator includes a first SRS resource indicator and a second SRS resource indicator, wherein at least one PUSCH repeat set includes a first PUSCH repeat set associated with the first SRS resource set and a second PUSCH repeat set associated with the second SRS resource set, and wherein the first SRS resource set and the second SRS resource set are listed in at least one of the first SRS resource set list or the second SRS resource set list.
[0111] In the eleventh additional state sample, alone or in combination with the tenth state sample, process 500 includes: determining at least one SRS resource set, wherein determining at least one SRS resource set includes: determining a first SRS resource set including a first SRS resource set listed in a first SRS resource set list and having a first use indicator set to codebook or non-codebook; and determining a second SRS resource set including a second SRS resource set listed in the first SRS resource set list and having a second use indicator set to codebook or non-codebook.
[0112] In the twelfth additional state sample, determining at least one SRS resource set, either alone or in combination with the eleventh state sample, includes: determining at least one SRS resource set by listing a second SRS resource set based at least in part on a first SRS resource set list.
[0113] In the thirteenth additional state sample, determining at least one SRS resource set, either alone or in combination with the eleventh state sample, includes: determining at least one SRS resource set based at least in part on the first SRS resource set list, which only lists the first SRS resource set.
[0114] In the fourteenth additional state sample, either alone or in combination with the tenth state sample, process 500 includes: determining at least one SRS resource set, wherein determining at least one SRS resource set includes: determining that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list and has a first usage indicator set to codebook or non-codebook; and determining that the second SRS resource set is included in the second SRS resource set list and has a second usage indicator set to codebook or non-codebook.
[0115] In the fifteenth additional state sample, determining at least one SRS resource set, either alone or in combination with the tenth state sample, includes: determining at least one SRS resource set by listing the first SRS resource set and the second SRS resource set at least in part based on the second SRS resource set list.
[0116] In the sixteenth additional state sample, either alone or in combination with the tenth state sample, the CG PUSCH configuration includes an indicator bit, and the process 500 includes: determining, at least in part based on the indicator bit having a first value, that the first SRS resource set is a first SRS resource set listed in the first SRS resource set list, or at least in part based on the indicator bit having a second value, that the first SRS resource set is a first SRS resource set listed in the second SRS resource set list.
[0117] In the seventeenth additional state, either alone or in combination with one or more states in the tenth or sixteenth state, the CG PUSCH configuration includes an indicator bit, and the process 500 includes: determining, at least in part based on the indicator bit having a first value, that the second SRS resource set is a second SRS resource set listed in the first SRS resource set list, or at least in part based on the indicator bit having a second value, that the second SRS resource set is a second SRS resource set listed in the second SRS resource set list.
[0118] In the eighteenth additional state sample, either alone or in combination with the tenth state sample, the first SRS resource set ID corresponds to the first SRS resource set, and the second SRS resource set ID corresponds to the second SRS resource set, and the process 500 includes: determining at least one SRS resource set to include the first SRS resource set associated with the first SRS resource set ID and the second SRS resource set associated with the second SRS resource set ID, wherein determining at least one SRS resource set includes: determining at least one SRS resource set based at least in part on an explicit indicator associated with the uplink allowance parameter configured in the CG PUSCH that indicates the first SRS resource set ID and the second SRS resource set ID.
[0119] Although Figure 5 illustrates an example block of process 500, in some versions, process 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 5. Alternatively or concurrently, two or more blocks of process 500 may be executed in parallel.
[0120] Figure 6 is a diagram illustrating an example process 600 performed by a base station, for example, according to this disclosure. Example process 600 is an instance of a base station (e.g., base station 410) performing an operation associated with an SRS resource indicator that is repeatedly associated with CG PUSCH.
[0121] As shown in FIG6, in some cases, process 600 may include: sending a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list (block 610). For example, a base station (such as by using a communication manager 150 or a transmission component 804 depicted in FIG8) can send a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, wherein the at least one SRS resource indicator indicates at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list, as described above.
[0122] As further shown in FIG6, in some embodiments, process 600 may include: receiving at least one set of PUSCH repetitions based at least in part on at least one set of PUSCH transmission parameters, wherein the at least one set of PUSCH transmission parameters is based at least in part on a determination of at least one set of resources (block 620). For example, a base station (such as by using communication manager 150 or receiving unit 802 depicted in FIG8) may receive at least one set of PUSCH repetitions based at least in part on at least one set of PUSCH transmission parameters, wherein the at least one set of PUSCH transmission parameters is based at least in part on a determination of at least one set of resources, as described above.
[0123] Process 600 may include additional patterns, such as any single pattern or any combination of patterns described below or in conjunction with one or more other processes described elsewhere herein.
[0124] In the first additional state, at least one SRS resource indicator includes a unique SRS resource indicator, and at least one SRS resource set includes a unique SRS resource set.
[0125] In the second additional state, either alone or in combination with the first state, at least in part, based on a unique SRS resource set, the first SRS resource set listed in the first SRS resource set list is included, at least one SRS resource set being a first SRS resource set listed in the first SRS resource set list that has a usage indicator set to codebook or non-codebook.
[0126] In the third additional state sample, either alone or in combination with the second state sample, the first SRS resource set is the only SRS resource set listed in the first SRS resource set list.
[0127] In the fourth additional state sample, either alone or in combination with one or more states from the second to the third state samples, the first SRS resource set listed in the first SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set ID value associated with any other SRS resource set listed in the first SRS resource set list.
[0128] In the fifth additional state sample, either alone or in combination with the first state sample, at least in part, based on a unique SRS resource set, the first SRS resource set listed in the second SRS resource set list is included, at least one SRS resource set being the first SRS resource set listed in the second SRS resource set list that has a usage indicator set to codebook or non-codebook.
[0129] In the sixth additional state sample, either alone or in combination with the fifth state sample, the first SRS resource set listed in the second SRS resource set list is the only SRS resource set listed in the second SRS resource set list.
[0130] In the seventh additional state sample, either alone or in combination with one or more states sample from the fifth to the sixth state sample, the first SRS resource set listed in the first SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set ID value associated with any other SRS resource set listed in the second SRS resource set list.
[0131] In the eighth additional state, either alone or in combination with the first state, the CG PUSCH configuration includes an indicator bit, wherein at least one SRS resource set is a unique SRS resource set, and the unique SRS resource set includes: a first SRS resource set listed in the second SRS resource set list based at least in part on the indicator bit having a first value; or a first SRS resource set listed in the second SRS resource set list based at least in part on the indicator bit having a second value.
[0132] In the ninth additional state sample, either alone or in combination with the first state sample, at least one SRS resource set is an SRS resource set associated with an SRS resource set ID associated with the uplink allowance parameter configured in the CG PUSCH, based at least in part on an explicit indicator that indicates the SRS resource set ID.
[0133] In the tenth additional state sample, at least one SRS resource indicator includes a first SRS resource indicator and a second SRS resource indicator, wherein at least one PUSCH repeat set includes a first PUSCH repeat set associated with the first SRS resource set and a second PUSCH repeat set associated with the second SRS resource set, and wherein the first SRS resource set and the second SRS resource set are listed in at least one of the first SRS resource set list or the second SRS resource set list.
[0134] In the eleventh additional state sample, the determination of at least one SRS resource set, either alone or in combination with the tenth state sample, includes: determining that the first SRS resource set includes the first SRS resource set listed in the first SRS resource set list and having a first use indicator set to either a codebook or a non-codebook; and the second SRS resource set includes the second SRS resource set listed in the first SRS resource set list and having a second use indicator set to either a codebook or a non-codebook.
[0135] In the twelfth additional state sample, the decision on at least one SRS resource set is made, either alone or in combination with the eleventh state sample, based at least in part on the listing of the second SRS resource set in the first SRS resource set list.
[0136] In the thirteenth additional state sample, the decision on at least one SRS resource set is based, either alone or in combination with the eleventh state sample, on the fact that the first SRS resource set list only lists the first SRS resource set.
[0137] In the fourteenth additional state sample, the determination of at least one SRS resource set, either alone or in combination with the tenth state sample, includes: determining that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list and having a first use indicator set to either a codebook or a non-codebook; and determining that the second SRS resource set is included in the second SRS resource set listed in the second SRS resource set list and having a second use indicator set to either a codebook or a non-codebook.
[0138] In the fifteenth additional state sample, the decision on at least one SRS resource set is made, either alone or in combination with the eleventh state sample, based at least in part on the second SRS resource set list which lists the first SRS resource set and the second SRS resource set.
[0139] In the sixteenth additional state, either alone or in combination with the eleventh state, the CG PUSCH configuration includes an indicator bit, and the determination of at least one SRS resource set includes: determining, at least in part based on the indicator bit having a first value, that the first SRS resource set is a first SRS resource set listed in the first SRS resource set list, or determining, at least in part based on the indicator bit having a second value, that the first SRS resource set is a first SRS resource set listed in the second SRS resource set list.
[0140] In the seventeenth additional state, either alone or in combination with the eleventh state, the CG PUSCH configuration includes an indicator bit, and the determination of at least one SRS resource set includes: determining, at least in part based on the indicator bit having a first value, that the second SRS resource set is a second SRS resource set listed in the first SRS resource set list, or determining, at least in part based on the indicator bit having a second value, that the second SRS resource set is a second SRS resource set listed in the second SRS resource set list.
[0141] In the eighteenth additional state sample, either alone or in combination with the eleventh state sample, the first SRS resource set ID corresponds to the first SRS resource set, and the second SRS resource set ID corresponds to the second SRS resource set, wherein the determination of at least one SRS resource set includes: determining that at least one SRS resource set includes the first SRS resource set associated with the first SRS resource set ID and the second SRS resource set associated with the second SRS resource set ID, wherein the determination of at least one SRS resource set is based at least in part on an explicit indicator associated with the uplink allowance parameter configured in the CG PUSCH that indicates the first SRS resource set ID and the second SRS resource set ID.
[0142] Although FIG6 illustrates an example block of process 600, in some versions, process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in FIG6. Alternatively or concurrently, two or more blocks of process 600 may be executed in parallel.
[0143] FIG7 is a diagram of an example device 700 for wireless communication according to the present disclosure. Device 700 may be a UE, or a UE may include device 700. In some embodiments, device 700 includes a receiving component 702, a transmitting component 704, and a communication manager 140, which can communicate with each other (e.g., via one or more buses). As shown, device 700 may use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device).
[0144] In some embodiments, device 700 may be configured to perform one or more operations described herein in conjunction with FIG. 4. Alternatively or additionally, device 700 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5. In some embodiments, device 700 may include one or more components of the UE described above in conjunction with FIG. 2.
[0145] The receiving unit 702 may receive communications from the device 706, such as reference signals, control information, data communications, or combinations thereof. The receiving unit 702 may provide the received communications to one or more other components of the device 700 (such as the communication manager 140). In some embodiments, the receiving unit 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components. In some embodiments, the receiving unit 702 may include one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the UE described above in conjunction with FIG. 2.
[0146] The transmission component 704 can send communications, such as reference signals, control information, data communications, or combinations thereof, to the device 706. In some embodiments, the communication manager 140 can generate communications and send the generated communications to the transmission component 704 for transmission to the device 706. In some embodiments, the transmission component 704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communications and send the processed signals to the device 706. In some embodiments, the transmission component 704 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof, as described above in conjunction with FIG. 2. In some embodiments, the transmission component 704 may be co-located with the receiving component 702 in a transceiver.
[0147] Communication manager 140 may receive or cause receiving unit 702 to receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. Communication manager 140 may determine at least one set of PUSCH transmission parameters for at least one PUSCH repeat set based at least in part on the determination of at least one SRS resource set. Communication manager 140 may send or cause transmission unit 704 to send at least one PUSCH repeat set based at least in part on at least one set of PUSCH transmission parameters. In some cases, communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of communication manager 140.
[0148] The communication manager 140 may include the controller / processor, memory, or a combination thereof of the UE described above in conjunction with FIG. 2. In some embodiments, the communication manager 140 includes a set of components, such as decision component 708. Alternatively, the set of components may be separate from and different from the communication manager 140. In some embodiments, one or more components in the set of components may include, or be implemented within, the controller / processor, memory, or a combination thereof of the UE described above in conjunction with FIG. 2. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of that component.
[0149] The receiving unit 702 can receive a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The determining unit 708 can determine at least one set of PUSCH transmission parameters for at least one PUSCH repeat set based at least in part on the determination of the at least one SRS resource set. The transmitting unit 704 can transmit at least one PUSCH repeat set based at least in part on the at least one set of PUSCH transmission parameters.
[0150] The determining component 708 may determine, at least in part, that at least one SRS resource set is a first SRS resource set listed in the first SRS resource set list that has a usage indicator set to codebook or non-codebook, based on a unique SRS resource set included in the first SRS resource set list.
[0151] The determining component 708 may determine, at least in part, that at least one SRS resource set is a first SRS resource set listed in the second SRS resource set list that has a usage indicator set to codebook or non-codebook, based on a unique SRS resource set included in the first SRS resource set listed in the second SRS resource set list.
[0152] The determining component 708 may determine, at least in part, that at least one SRS resource set is an SRS resource set associated with an SRS resource set ID associated with the same unique SRS resource set, based on an explicit indicator associated with the uplink allowance parameter configured in the CG PUSCH that indicates the SRS resource set ID.
[0153] The determining component 708 can determine at least one SRS resource set, wherein determining at least one SRS resource set includes: determining a first SRS resource set including a first SRS resource set listed in a first SRS resource set list and having a first usage indicator set to codebook or non-codebook; and determining a second SRS resource set including a second SRS resource set listed in the first SRS resource set list and having a second usage indicator set to codebook or non-codebook.
[0154] The determining component 708 can determine at least one SRS resource set, wherein determining at least one SRS resource set includes: determining that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list and has a first usage indicator set to codebook or non-codebook; and determining that the second SRS resource set is included in the second SRS resource set list and has a second usage indicator set to codebook or non-codebook.
[0155] The number and arrangement of components shown in Figure 7 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 7. Furthermore, two or more components shown in Figure 7 may be implemented in a single component, or a single component shown in Figure 7 may be implemented as multiple distributed components. Additionally or alternatively, the set of components shown in Figure 7 (e.g., one or more components) may perform one or more functions described as being performed by another set of components shown in Figure 7.
[0156] FIG8 is a block diagram of an example device 800 for wireless communication according to the present disclosure. Device 800 may be a base station, or a base station may include device 800. In some embodiments, device 800 includes a receiving component 802, a transmitting component 804, and a communication manager 150, which can communicate with each other (e.g., via one or more buses). As shown, device 800 can use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (such as a UE, a base station, or another wireless communication device).
[0157] In some embodiments, device 800 may be configured to perform one or more operations described herein in conjunction with FIG4. Alternatively or additionally, device 800 may be configured to perform one or more processes described herein, such as process 600 of FIG6. In some embodiments, device 800 may include one or more components of a base station described above in conjunction with FIG2.
[0158] The receiving unit 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving unit 802 may provide the received communications to one or more other components of the device 800 (such as the communication manager 150). In some embodiments, the receiving unit 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components. In some embodiments, the receiving unit 802 may include one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the base station described above in conjunction with FIG2.
[0159] The transmission unit 804 can send communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some embodiments, the communication manager 150 can generate communications and send the generated communications to the transmission unit 804 for transmission to the device 806. In some embodiments, the transmission unit 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communications and send the processed signals to the device 806. In some embodiments, the transmission unit 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, memory, or combinations thereof, as described above in conjunction with FIG2. In some embodiments, the transmission unit 804 may be co-located with the receiving unit 802 in a transceiver.
[0160] The communication manager 150 may send or cause the transmission unit 804 to send a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The communication manager 150 may receive or cause the receiving unit 802 to receive at least one PUSCH repeat set based at least in part on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is based at least in part on a determination of at least one resource set. In some cases, the communication manager 150 may perform one or more operations that are otherwise described herein as being performed by one or more components of the communication manager 150.
[0161] The communication manager 150 may include the base station controller / processor, memory, scheduler, communication unit, or a combination thereof as described above in conjunction with FIG2. In some embodiments, one or more components of the component set of the communication manager 150 may include, or may be implemented in, the base station controller / processor, memory, scheduler, communication unit, or a combination thereof as described above in conjunction with FIG2. Alternatively or additionally, one or more components of the component set may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0162] The transmission unit 804 can transmit a CG PUSCH configuration including at least one SRS resource indicator associated with at least one PUSCH repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list. The receiving unit 802 can receive at least one PUSCH repeat set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0163] The number and arrangement of components shown in Figure 8 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 8. Furthermore, two or more components shown in Figure 8 may be implemented in a single component, or a single component shown in Figure 8 may be implemented as multiple distributed components. Additionally or alternatively, the set of components shown in Figure 8 (e.g., one or more components) may perform one or more functions described as being performed by another set of components shown in Figure 8.
[0164] The following provides an overview of some aspects of the contents of this disclosure.
[0165] Sample 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving an allowable (CG) PUSCH configuration including a configuration of at least one probe reference signal (SRS) resource indicator associated with at least one entity uplink shared channel (PUSCH) repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; determining at least one set of PUSCH transmission parameters for at least one PUSCH repeat set based at least in part on the determination of at least one SRS resource set; and transmitting at least one PUSCH repeat set based at least in part on the at least one set of PUSCH transmission parameters.
[0166] State 2: The method as described in State 1, wherein at least one SRS resource indicator includes a unique SRS resource indicator, and wherein at least one SRS resource set includes a unique SRS resource set.
[0167] State 3: The method as described in State 2 further includes: determining at least one SRS resource set as a first SRS resource set listed in the first SRS resource set list, having a usage indicator set as either a codebook or a non-codebook, based at least in part on a unique SRS resource set included in the first SRS resource set list.
[0168] State 4: The method is as described in State 3, wherein the first SRS resource set is the only SRS resource set listed in the first SRS resource set list.
[0169] State 5: The method as described in any of the states 3 or 4, wherein the first SRS resource set listed in the first SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set identifier (ID) value associated with any other SRS resource set listed in the first SRS resource set list.
[0170] State 6: The method as described in any of States 2 to 5, further comprising: determining at least one SRS resource set as the first SRS resource set listed in the second SRS resource set list, having a usage indicator set to a codebook or non-codebook, based at least in part on a unique SRS resource set included in the first SRS resource set listed in the second SRS resource set list.
[0171] State 7: The method is as described in State 6, wherein the first SRS resource set listed in the second SRS resource set list is the only SRS resource set listed in the second SRS resource set list.
[0172] State 8: The method as described in any of the states 6 or 7, wherein the first SRS resource set listed in the second SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set identifier (ID) value associated with any other SRS resource set listed in the second SRS resource set list.
[0173] State 9: The method as described in State 2, wherein the CG PUSCH configuration includes indicator bits, and the method further includes determining at least one SRS resource set as a unique SRS resource set, wherein the unique SRS resource set includes: a first SRS resource set listed in a first SRS resource set list based at least in part on the indicator bits having a first value, or a first SRS resource set listed in a second SRS resource set list based at least in part on the indicator bits having a second value.
[0174] State 10: The method as described in State 2 further includes: determining at least one SRS resource set as an SRS resource set associated with an SRS resource set identifier (ID) associated with the same unique SRS resource set, based at least in part on an explicit indicator associated with an uplink allowance parameter configured in the CG PUSCH indicating the SRS resource set ID.
[0175] State 11: The method as described in State 1, wherein at least one SRS resource indicator includes a first SRS resource indicator and a second SRS resource indicator, wherein at least one PUSCH repeat set includes a first PUSCH repeat set associated with a first SRS resource set and a second PUSCH repeat set associated with a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set are listed in at least one of a first SRS resource set list or a second SRS resource set list.
[0176] State 12: The method of State 11 further includes determining at least one SRS resource set, wherein determining at least one SRS resource set includes: determining that a first SRS resource set includes a first SRS resource set listed in a first SRS resource set list and having a first usage indicator set to a codebook or non-codebook; and determining that a second SRS resource set includes a second SRS resource set listed in a first SRS resource set list and having a second usage indicator set to a codebook or non-codebook.
[0177] State 13: The method as described in State 12, wherein determining at least one SRS resource set comprises: determining at least one SRS resource set by listing a second SRS resource set at least in part based on a first SRS resource set list.
[0178] State 14: The method as described in State 12, wherein determining at least one SRS resource set comprises: determining at least one SRS resource set based at least in part on a first SRS resource set list that only lists the first SRS resource set.
[0179] State 15: The method of State 11 further includes determining at least one SRS resource set, wherein determining at least one SRS resource set includes: determining that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list and has a first usage indicator set to codebook or non-codebook; and determining that the second SRS resource set is included in the second SRS resource set list and has a second usage indicator set to codebook or non-codebook.
[0180] State 16: The method as described in State 11, wherein determining at least one SRS resource set comprises: determining at least one SRS resource set by listing the first SRS resource set and the second SRS resource set at least in part based on a second SRS resource set list.
[0181] State 17: The method as described in State 11, wherein the CG PUSCH configuration includes indicator bits, the method further comprising: determining, at least in part based on the indicator bits having a first value, that the first SRS resource set is a first SRS resource set listed in a first SRS resource set list, or at least in part based on the indicator bits having a second value, that the first SRS resource set is a first SRS resource set listed in a second SRS resource set list.
[0182] State 18: The method as described in any of the states 11 or 17, wherein the CG PUSCH configuration includes indicator bits, the method further comprising: determining the second SRS resource set as the second SRS resource set listed in the first SRS resource set list based at least in part on the indicator bits having a first value, or determining the second SRS resource set as the second SRS resource set listed in the second SRS resource set list based at least in part on the indicator bits having a second value.
[0183] State 19: The method as described in State 11, wherein the first SRS resource set identifier (ID) corresponds to the first SRS resource set and the second SRS resource set ID corresponds to the second SRS resource set, further comprising: determining at least one SRS resource set as including the first SRS resource set associated with the first SRS resource set ID and the second SRS resource set associated with the second SRS resource set ID, wherein determining at least one SRS resource set comprises: determining at least one SRS resource set based at least in part on an explicit indicator associated with the uplink allowance parameter configured in the CG PUSCH that indicates the first SRS resource set ID and the second SRS resource set ID.
[0184] Sample 20: A method of wireless communication performed by a base station, comprising: transmitting a permitted (CG) PUSCH configuration including a configuration of at least one probe reference signal (SRS) resource indicator associated with at least one entity uplink shared channel (PUSCH) repeat set, the at least one SRS resource indicator indicating at least one SRS resource corresponding to at least one SRS resource set, wherein the at least one SRS resource set is listed in at least one of a first SRS resource set list or a second SRS resource set list, wherein the at least one SRS resource set listed in the second SRS resource set list is a subset of the corresponding SRS resource set listed in the first SRS resource set list; and receiving at least one PUSCH repeat set at least in part based on at least one PUSCH transmission parameter set, wherein the at least one PUSCH transmission parameter set is at least in part based on a determination of at least one resource set.
[0185] State 21: The method as described in State 20, wherein at least one SRS resource indicator includes a unique SRS resource indicator, and wherein at least one SRS resource set includes a unique SRS resource set.
[0186] State 22: The method as described in State 21, wherein at least in part, based on a unique SRS resource set included in a first SRS resource set listed in a first SRS resource set list, at least one SRS resource set being a first SRS resource set listed in a first SRS resource set list having a usage indicator set to a codebook or non-codebook.
[0187] State 23: The method is as described in State 22, wherein the first SRS resource set is a unique SRS resource set listed in the first SRS resource set list.
[0188] State 24: The method as described in any of the states 22 or 23, wherein the first SRS resource set listed in the first SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set identifier (ID) value associated with any other SRS resource set listed in the first SRS resource set list.
[0189] State 25: The method as described in State 21, wherein at least in part, based on a unique SRS resource set included in a first SRS resource set listed in a second SRS resource set list, at least one SRS resource set being a first SRS resource set listed in a second SRS resource set list having a usage indicator set to a codebook or non-codebook.
[0190] State 26: The method as described in State 25, wherein the first SRS resource set listed in the second SRS resource set list is the only SRS resource set listed in the second SRS resource set list.
[0191] State 27: The method as described in any of the states 25 or 26, wherein the first SRS resource set listed in the second SRS resource set list includes: an SRS resource set having a lower SRS resource set ID value compared to any other SRS resource set identifier (ID) value associated with any other SRS resource set listed in the second SRS resource set list.
[0192] State 28: The method as described in State 21, wherein the CG PUSCH configuration includes indicator bits, wherein at least one SRS resource set is a unique SRS resource set, and wherein the unique SRS resource set includes: a first SRS resource set listed in a first SRS resource set list at least in part based on the indicator bits having a first value; or a first SRS resource set listed in a second SRS resource set list at least in part based on the indicator bits having a second value.
[0193] State 29: The method as described in State 21, wherein at least in part, based on an explicit indicator associated with an uplink allowance parameter configured in the CG PUSCH indicating an SRS resource set ID, at least one SRS resource set is an SRS resource set associated with an SRS resource set identifier (ID) associated with the same unique SRS resource set.
[0194] State 30: The method as described in State 20, wherein at least one SRS resource indicator includes a first SRS resource indicator and a second SRS resource indicator, wherein at least one PUSCH repeat set includes a first PUSCH repeat set associated with a first SRS resource set and a second PUSCH repeat set associated with a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set are listed in at least one of a first SRS resource set list or a second SRS resource set list.
[0195] State 31: The method as described in State 30, wherein the determination of at least one SRS resource set includes: determining that the first SRS resource set includes a first SRS resource set listed in the first SRS resource set list and having a first use indicator set to codebook or non-codebook; and determining that the second SRS resource set includes a second SRS resource set listed in the first SRS resource set list and having a second use indicator set to codebook or non-codebook.
[0196] State 32: The method as described in State 31, wherein the decision on at least one SRS resource set is based at least in part on listing a second SRS resource set in a first SRS resource set list.
[0197] State 33: The method as described in State 31, wherein the decision on at least one SRS resource set is based at least in part on a first SRS resource set list that only lists the first SRS resource set.
[0198] State 34: The method as described in State 30, wherein the determination of at least one SRS resource set includes: determining that the first SRS resource set is included in the first SRS resource set listed in the second SRS resource set list and having a first use indicator set to codebook or non-codebook; and determining that the second SRS resource set is included in the second SRS resource set list and having a second use indicator set to codebook or non-codebook.
[0199] State 35: The method as described in State 30, wherein the decision on at least one SRS resource set is based at least in part on a second SRS resource set list listing the first SRS resource set and the second SRS resource set.
[0200] State 36: The method as described in State 30, wherein the CG PUSCH configuration includes indicator bits, and wherein the determination of at least one SRS resource set includes: determining, at least in part based on the indicator bits having a first value, that the first SRS resource set is a first SRS resource set listed in a first SRS resource set list, or determining, at least in part based on the indicator bits having a second value, that the first SRS resource set is a first SRS resource set listed in a second SRS resource set list.
[0201] State 37: The method as described in State 30, wherein the CG PUSCH configuration includes indicator bits, and wherein the determination of at least one SRS resource set includes: determining, at least in part based on the indicator bits having a first value, that the second SRS resource set is a second SRS resource set listed in the first SRS resource set list, or determining, at least in part based on the indicator bits having a second value, that the second SRS resource set is a second SRS resource set listed in the second SRS resource set list.
[0202] State 38: The method as described in State 30, wherein a first SRS resource set identifier (ID) corresponds to a first SRS resource set and a second SRS resource set ID corresponds to a second SRS resource set, wherein the determination of at least one SRS resource set includes: determining that at least one SRS resource set includes a first SRS resource set associated with a first SRS resource set ID and a second SRS resource set associated with a second SRS resource set ID, wherein the determination of at least one SRS resource set is based at least in part on an explicit indicator associated with an uplink tolerance parameter configured in the CG PUSCH that indicates the first SRS resource set ID and the second SRS resource set ID.
[0203] Style 39: An apparatus for wireless communication at a device, comprising: a processor; memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in one or more of the styles 1 to 19.
[0204] State 40: A device for wireless communication, including a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method as described in one or more of the states 1-19.
[0205] State 41: An apparatus for wireless communication, comprising at least one component for performing the method as described in one or more of the states 1 to 19.
[0206] State 42: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of the states 1 to 19.
[0207] Style 43: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions, which, when executed by one or more processors of the device, cause the device to perform the method described in one or more of the styles 1 to 19.
[0208] State 44: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform the method as described in one or more of states 20 to 38.
[0209] State 45: A device for wireless communication, including a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method as described in one or more of the states 20 to 38.
[0210] State 46: An apparatus for wireless communication, comprising at least one component for performing the method as described in one or more of the states 20 to 38.
[0211] Format 47: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of formats 20 to 38.
[0212] Session 48: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions, which, when executed by one or more processors of the device, cause the device to perform the method described in one or more of the states 20 to 38.
[0213] The foregoing disclosure provides explanation and description, but is not intended to be exhaustive or to limit the various forms to the precise forms disclosed. Modifications and variations can be made as disclosed above, or modifications and variations can be derived from practice with the various forms.
[0214] As used herein, the term "component" is intended to be interpreted broadly as hardware, or a combination of hardware and software. Whether referred to as software, firmware, intermediary software, microcode, hardware description language, or other terms, "software" should be interpreted broadly as instructions, instruction sets, code, code fragments, code, programs, subprograms, software modules, applications, software applications, software packages, conventions, sub-conventions, objects, executable files, executable threads, programs or functions, etc. As used herein, a "processor" is implemented using hardware, or a combination of hardware and software. It will be apparent that the systems or methods described herein can be implemented using different forms of hardware, or combinations of hardware and software. The actual dedicated control hardware or software code used to implement such systems or methods is not limited to this type. Therefore, the operation and behavior of such systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that software and hardware for implementing such systems or methods can be designed, at least in part, based on the description herein.
[0215] As used herein, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, etc.
[0216] Although a specific combination of features is described in the claims or disclosed in the specification, such combinations are not intended to limit the disclosure of each variant. Many features may be combined in a manner not described in the claims or disclosed in the specification. The disclosure of each variant includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase representing "at least one of" in a list of items represents any combination of those items (including a single member). For example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, and any combination having multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).
[0217] Elements, actions, or instructions used herein should not be construed as critical or fundamental unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced by the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “have,” “contain,” “have,” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term "or" is intended to be inclusive when used in sequence and may be used interchangeably with "and / or" unless otherwise explicitly stated (e.g., when used in conjunction with "any" or "only one of"). [Simplified Explanation of the Diagram]
[0015] To gain a more detailed understanding of the features described above, a more specific description of the content briefly outlined above can be obtained by referring to various embodiments, some of which are shown in the accompanying drawings. However, it should be noted that the drawings only show some typical embodiments of the present disclosure and are therefore not intended to limit its scope, as the specification may acknowledge other equivalent embodiments. The same element symbols in different drawings may identify the same or similar elements.
[0016] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0017] Figure 2 is a diagram illustrating communication between an example base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0018] Figure 3 is a diagram illustrating an example of multi-transmitter / receiver (multi-TRP or mTRP) communication according to the present disclosure.
[0019] Figure 4 is a diagram illustrating an example of a probe reference signal (SRS) resource indicator associated with a repeating uplink shared channel (PUSCH) of a permitted (CG) entity according to this disclosure.
[0020] Figure 5 is a flowchart illustrating an example process performed by a UE that supports an SRS resource indicator associated with CG PUSCH repetition, according to this disclosure.
[0021] Figure 6 is a flowchart illustrating an example process performed, for example, by a base station supporting an SRS resource indicator associated with repeated CG PUSCH, according to this disclosure.
[0022] Figures 7 and 8 are diagrams of an example device for wireless communication that supports an SRS resource indicator associated with CG PUSCH repetition according to the present disclosure. [Biomaterial Storage]
[0219] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.
Claims
1. A method of wireless communication performed by an apparatus, comprising the steps of: receiving a probe reference signal (SRS) configuration, the configuration including an indication of at least one SRS resource set listed in a first SRS resource set list and at least one SRS resource set listed in a second SRS resource list, each SRS resource set having at least one SRS resource, wherein the SRS configuration further includes a configuration of at least one set of transmission parameters corresponding to each SRS resource; receiving a Type including a single probe reference signal (SRS) resource indicator associated with at least one entity uplink shared channel (PUSCH) repetition set.
1. A configured allowable (CG) PUSCH configuration, wherein the SRS resource indicator indicates an SRS resource included in an SRS resource set, wherein the SRS resource set is determined according to a predetermined rule to be an SRS resource set having a lower SRS resource set identifier (ID) compared to any other SRS resource set included in either the first SRS resource set list or the second SRS resource set list; and the at least one PUSCH repeat set is transmitted at least in part based on at least one PUSCH transmission parameter set, the at least one PUSCH transmission parameter set corresponding to the SRS resource indicated by the SRS resource indicator in the determined SRS resource set.
2. The method as described in claim 1, wherein each of the SRS configuration and the Type 1 CG PUSCH configuration is included in a Radio Resource Control (RRC) message.
3. The method of claim 1, wherein the predetermined rule indicates that the SRS resource set is to be determined as an SRS resource set having a lower SRS resource set ID compared to any other SRS resource set included in the first SRS resource set list.
4. The method of claim 1, wherein the predetermined rule indicates that the SRS resource set is to be determined as an SRS resource set having a lower SRS resource set ID compared to any other SRS resource set included in the second SRS resource set list.
5. The method as described in request item 1, further comprising determining whether the Type 1 CG PUSCH configuration contains an SRS resource set indicator, wherein, If the Type 1 CG PUSCH configuration includes the SRS resource set indicator, then the at least one PUSCH transport parameter set corresponds to the SRS resource indicated by the SRS resource indicator in an SRS resource set, which is indicated by the SRS resource set indicator.
6. The method as described in claim 5, wherein the SRS resource set indicator is an indicator bit indicating whether the SRS resource set is a first SRS resource set of the first resource set list or a first SRS resource set of the second resource set list.
7. A method of wireless communication performed by an apparatus, comprising the steps of: receiving a probe reference signal (SRS) configuration, the configuration including an indication of at least one SRS resource set listed in a first SRS resource set list and at least one SRS resource set listed in a second SRS resource list, each SRS resource set having at least one SRS resource, wherein the SRS configuration further includes a configuration of at least one set of transmission parameters corresponding to each SRS resource; receiving a Type 1 configuration of a permitted (CG) entity uplink shared channel (PUSCH) configuration including a first SRS resource indicator associated with a first PUSCH repeat set and a second SRS resource indicator associated with a second PUSCH repeat set, wherein the first PUSCH repeat set and the second PUSCH repeat set are respectively associated with a first SRS resource set and a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set are listed in at least one of the first SRS resource set list or the second SRS resource set list, wherein, If the first SRS resource set list includes two SRS resource sets, the first SRS resource set and the second SRS resource set are respectively determined as the two SRS resource sets listed in the first SRS resource set list; and the first PUSCH repeat set is transmitted at least partially based on a first PUSCH transmission parameter set, the first PUSCH transmission parameter set corresponding to the SRS resource indicated by the first SRS resource indicator in the first SRS resource set; and the second PUSCH repeat set is transmitted at least partially based on a second PUSCH transmission parameter set, the second PUSCH transmission parameter set corresponding to the SRS resource indicated by the second SRS resource indicator in the second SRS resource set.
8. The method as described in claim 7, wherein each of the SRS configuration and the Type 1 CG PUSCH configuration is included in a Radio Resource Control (RRC) message.
9. The method as described in claim 7, wherein, If the first SRS resource set list includes a single SRS resource set and the second SRS resource set includes two SRS resource sets, the first SRS resource set and the second SRS resource set are respectively identified as the two SRS resource sets listed in the second SRS resource set list.
10. The method as described in claim 7, wherein, If the first SRS resource set list includes a single SRS resource set and the second SRS resource set includes a single SRS resource set, the first SRS resource set and the second SRS resource set are respectively determined to be the SRS resource sets listed in the first and second SRS resource set lists.
11. The method as described in claim 7, wherein, If the Type 1 CG PUSCH configuration contains first and second SRS resource set IDs, the first SRS resource set and the second SRS resource set are determined to be indicated by the first and second SRS resource set IDs, respectively.
12. An apparatus for wireless communication, comprising at least one component for performing the method as described in any one of claims 1 to 11.
Citation Information
Patent Citations
Methods and apparatuses for physical uplink shared channel for multi transmit-receive-point communications in a wireless communications network
EP3879738A1
Method and device for determining the number of retransmissions, method and device for indicating the number of retransmissions, communication node, and medium
TW202118340A
Cross-link interference detection and mitigation
US20190274155A1
Power control method and terminal device
US20200336990A1
User terminal and wireless communication method
WO2020090091A1