Performing physical uplink shared channel transmissions with improved reliability

Abstract

The present disclosure relates to techniques for performing physical uplink shared channel transmissions with improved reliability in a wireless communication system. A wireless device can establish a wireless link with a cellular base station. The wireless device can receive uplink data transmission configuration information from the cellular base station. The uplink data transmission configuration information can configure uplink data transmission to multiple transmission-reception-points. The wireless device can perform uplink data transmission to multiple transmission-reception-points.

Description

Technology Field

[0001] The present application relates to wireless communications, and more specifically to systems, devices, and methods for performing physical uplink shared channel transmissions with improved reliability in wireless communication systems. Background Technology

[0002] The use of wireless communication systems is increasing rapidly. In recent years, wireless devices such as smartphones and tablet computers have become increasingly sophisticated. Many mobile devices (i.e., User Equipment Devices or UEs) now provide access to the Internet, email, text messaging, and navigation using GPS (Global Positioning System), in addition to supporting phone calls, and can run sophisticated applications that utilize these capabilities. Furthermore, numerous different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (LTE Advanced), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and Bluetooth. TM Includes the back.

[0003] The ever-increasing number of features and functions introduced into wireless communication devices creates a continuous need for improvement in both wireless communications and wireless communication devices. In particular, it is important to ensure the accuracy of transmitted and received signals through User Equipment (UE) devices—such as wireless devices like cellular phones used in wireless cellular communication, for example—as well as through base stations and relay stations. Additionally, increasing the functionality of UE devices can place a significant burden on their battery life. Therefore, it is crucial to reduce power requirements in UE device designs while allowing UE devices to maintain good transmit and receive capabilities for enhanced communications. Consequently, improvements in this area are desired.

[0004] Embodiments of devices, systems, and methods for performing physical uplink shared channel transmissions with improved reliability in wireless communication systems are presented herein.

[0005] According to the techniques described herein, a wireless device may receive uplink data transmission configuration information that constitutes uplink data transmission to multiple transmission-reception-points and may perform uplink data transmission to multiple transmission-reception-points. The uplink data transmission may be any of various types of uplink data transmissions, and some or all of the parameters used when transmitting to each of the configured transmission-reception-points may be configured independently for each transmission-reception-point.

[0006] Performing uplink data transmission in this manner can help improve the reliability of uplink data communications by utilizing the potential for beam diversity that may be possible when uplink data can be provided to multiple transmission and reception points, at least according to some embodiments.

[0007] It should be noted that the technologies described herein may be implemented and / or used with a number of different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablet computers, wearable devices, unmanned aerial vehicles, unmanned aerial vehicle controllers, automobiles and / or motorized vehicles and various other computing devices.

[0008] The content of the present invention is intended to provide a brief overview of some of the subject matter described herein. Accordingly, it will be understood that the features described above are merely illustrative and should not be interpreted to limit the scope or concept of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Brief explanation of the drawing

[0009] A better understanding of the subject of the invention can be obtained when the following detailed description of various embodiments is considered together with the accompanying drawings. FIG. 1 illustrates an exemplary (and simplified) wireless communication system according to some embodiments. FIG. 2 illustrates an exemplary base station communicating with an exemplary wireless user equipment (UE) device according to some embodiments. FIG. 3 illustrates an exemplary block diagram of a UE according to some embodiments. FIG. 4 illustrates an exemplary block diagram of a base station according to some embodiments. FIG. 5 is a flowchart illustrating exemplary possible methods for providing physical uplink shared channel transmissions with improved reliability in a wireless communication system according to some embodiments. FIGS. 6 through 8 illustrate exemplary aspects of various possible transmission patterns that can be used in configured acknowledgment physical uplink shared channel transmissions according to some embodiments. FIG. 9 illustrates various possible exemplary approaches for mapping TRPs to iterations for dynamic acknowledgment physical uplink shared channel transmissions according to some embodiments. FIG. 10 illustrates exemplary aspects of possible non-codebook based physical uplink sharing channel operations according to some embodiments. While various modifications and alternative forms are possible for the features described herein, specific embodiments thereof are illustrated by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and the detailed description therein are not intended to limit the specific forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives within the spirit and scope of the subject matter as defined by the appended claims. Specific details for implementing the invention

[0010] Abbreviations

[0011] Various acronyms are used throughout this disclosure. Definitions of the most predominantly used acronyms that may appear throughout this disclosure are provided as follows:

[0012] UE User Equipment

[0013] RF Radio Frequency

[0014] BS : Base Station

[0015] GSM Global System for Mobile Communication

[0016] UMTS Universal Mobile Telecommunication System

[0017] LTE Long Term Evolution

[0018] NR New Radio

[0019] TX : Transmission / Transmit

[0020] RX : Reception (Reception / Receive)

[0021] RAT: Radio Access Technology

[0022] TRP Transmission-Reception Point

[0023] DCI: Downlink Control Information

[0024] CORESET: Control Resource Set

[0025] CSI: Channel State Information

[0026] CSI-RS : Channel status information reference signal

[0027] Terms

[0028] The following is an explanation of terms that may appear in this disclosure:

[0029] memory media - Any of various types of non-transient memory devices or storage devices. The term “memory medium” is intended to include installation media, e.g., CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash, magnetic media, e.g., hard drives, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may also include other types of non-transient memory or combinations thereof. Additionally, the memory medium may be located in a first computer system where programs are executed, or in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer system for execution. The term “memory medium” may include two or more memory media residing in different locations, e.g., different computer systems connected via a network. A memory medium can store program instructions that can be executed by one or more processors (e.g., implemented as computer programs).

[0030] Carrier media - In addition to memory media as described above, physical transmission media such as buses and networks, and / or other physical transmission media that transmit signals such as electrical, electromagnetic, or digital signals.

[0031] computer system (or computer)Any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, Internet appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. Generally, the term "computer system" may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0032] User Equipment (UE) (or "UE Device") - Any of the various types of computer systems or devices that are mobile or portable and perform wireless communications. Examples of UE Devices include mobile phones or smartphones (e.g., iPhone™, Android™-based phones), tablet computers (e.g., iPad™, Samsung Galaxy™), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motorized vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally, the terms "UE" or "UE device" may be broadly defined to encompass any electronic, computing, and / or communication device (or combination of devices) that is easily movable by a user and capable of wireless communication.

[0033] wireless devices - Any of the various types of computer systems or devices that perform wireless communication. A wireless device may be portable (or mobile) or may be stationary or fixed in a specific location. A UE is an example of a wireless device.

[0034] communication device - Any of the various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), stationary, or fixed in a specific location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0035] Base Station (BS) - The term "base station" encompasses the full scope of its general meaning and includes, at a minimum, a radio station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0036] processing element (or processor) - Refers to various elements or combinations of elements capable of performing functions in a device, for example, in a user equipment device or in a cellular network device. Processing elements may include, for example, processors and associated memory, parts of individual processor cores or their circuits, entire processor cores, processor arrays, circuits such as ASICs (Application-Specific Integrated Circuits), programmable hardware elements such as Field Programmable Gate Arrays (FPGAs), as well as any of the various combinations of the above.

[0037] Wi-Fi -The term "Wi-Fi" encompasses the full range of its general meaning and includes, at a minimum, wireless communication networks or RATs that are serviced by wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are different from cellular networks.

[0038] automatically- Refers to an action or operation being performed by a computer system (e.g., software executed by the computer system) or a device (e.g., circuits, programmable hardware elements, ASICs, etc.) without user input directly specifying or performing the action or operation. Therefore, the term "automatically" is contrasted with an operation that is performed or specified manually by the user, where the user provides input that directly performs the operation. While an automatic procedure may be initiated by input provided by the user, subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually" by the user specifying each action to be performed. For example, filling out an electronic form by a user selecting each field and providing input that specifies information (e.g., typing information, selecting checkboxes, selecting wireless communication devices, etc.) constitutes filling out the form manually, even if the computer system is required to update the form in response to user actions. A form may be automatically filled out by a computer system, wherein the computer system (e.g., software running on the computer system) analyzes the fields of the form and fills them out without any user input specifying responses to the fields. As indicated above, the user may invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify responses to the fields, but rather they are completed automatically). This specification provides various examples of actions that are automatically performed in response to actions taken by the user.

[0039] configured to ~- Various components may be described as having a task or being "configured to perform tasks." In such a context, "configured to perform" is a broad description generally meaning "having a structure that performs a task or tasks during operation." As such, a component may be configured to perform a task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect two modules even when one module is not connected to the other). In some contexts, "configured to perform" may be a broad description of a structure generally meaning "having a circuit part that performs a task or tasks during operation." As such, a component may be configured to perform a task even when the component is not currently in an "on" state. Generally, the circuit part forming the structure corresponding to "configured to perform" may include hardware circuits.

[0040] Various components may be described as performing tasks or tasks for the convenience of description. Such descriptions should be interpreted as containing the phrase “configured to perform.” Referring to a component configured to perform one or more tasks is clearly intended not to apply the interpretation of 35 USC § 112, 6 to that component.

[0041] FIGS. 1 and FIGS. 2 - Exemplary communication system

[0042] FIG. 1 illustrates an exemplary (and simplified) wireless communication system in which aspects of the present invention may be implemented according to some embodiments. It should be noted that the system of FIG. 1 is merely an example of a possible system and that the embodiments may be implemented in any of the various systems as desired.

[0043] As described, an exemplary wireless communication system includes a base station (102) that communicates via a transmission medium with one or more (e.g., any number) user devices (106A, 106B, etc. to 106N). Each of the user devices may be referred to herein as "user equipment (UE)" or a UE device. Accordingly, the user devices (106) are referred to as UEs or UE devices.

[0044] The base station (102) may be a base transceiver station (BTS) or a cell site and may include hardware and / or software that enables wireless communication with UEs (106A to 106N). If the base station (102) is implemented in the context of LTE, the base station may alternatively be referred to as an 'eNodeB' or 'eNB'. If the base station (102) is implemented in the context of 5G NR, the base station may alternatively be referred to as a 'gNodeB' or 'gNB'. The base station (102) may also be equipped to communicate with a network (100) (e.g., among various possibilities, a core network of a cellular service provider, a communication network such as a public switched telephone network (PSTN), and / or the Internet). Thus, the base station (102) can facilitate communication between user devices and / or between user devices and the network (100). The communication area (or coverage area) of the base station may be referred to as a "cell". As also used herein, from the perspective of UEs, a base station may sometimes be considered to represent a network, insofar as UE's uplink and downlink communications are involved. Accordingly, a UE communicating with one or more base stations within a network may also be interpreted as the UE communicating with the network.

[0045] Base stations (102) and user devices may be configured to communicate through a transmission medium using any of the various radio access technologies (RATs) also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (WCDMA), LTE, LTE-A (LTE-Advanced), LAA / LTE-U, 5G NR, 3GPP2 CDMA2000 (e.g. 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.

[0046] Accordingly, a base station (102) and other similar base stations operating according to the same or different cellular communication standards may be provided as one or more networks of cells, and these may provide continuous or nearly continuous overlapping services to UEs (106) and similar devices across a geographical area through one or more cellular communication standards.

[0047] Note that the UE (106) may communicate using a number of wireless communication standards. For example, the UE (106) may be configured to communicate using either or both of the 3GPP cellular communication standards or the 3GPP2 cellular communication standards. In some embodiments, the UE (106) may be configured to perform robust uplink data transmission techniques, for example, according to the various methods described herein. The UE (106) may also, or alternatively, WLAN, Bluetooth TM It may be configured to communicate using one or more GNSS (global navigational satellite systems) (e.g., GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H), etc. Other combinations of radio communication standards (including more than two radio communication standards) are also possible.

[0048] FIG. 2 illustrates an exemplary user device (106) (e.g., one of devices (106A to 106N)) communicating with a base station (102) according to some embodiments. The UE (106) may be a device having wireless network connectivity, such as a mobile phone, a handheld device, a wearable device, a computer or tablet, an unmanned aerial vehicle (UAV), an unmanned air controller (UAC), a vehicle, or virtually any type of wireless device. The UE (106) may include a processor (processing element) configured to execute program instructions stored in memory. The UE (106) may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, the UE (106) may include programmable hardware elements, such as a Field Programmable Gate Array (FPGA), an integrated circuit, and / or any of various other possible hardware components, configured to perform any of the method embodiments described herein, or any part of any of the method embodiments described herein (e.g., individually or in combination). The UE (106) may be configured to communicate using any of a number of wireless communication protocols. For example, the UE (106) may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0049] The UE (106) may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, the UE (106) may share one or more parts of the receive chain and / or transmit chain among a number of wireless communication standards. To perform wireless communication, the shared wireless device may include a single antenna or a number of antennas (e.g., for MIMO). Generally, the wireless device may include any combination of a baseband processor, an analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the wireless device may implement one or more receive and transmit chains using the hardware described above.

[0050] In some embodiments, for each wireless communication protocol configured to communicate using the UE (106), the UE may include separate transmit and / or receive chains (e.g., including separate antennas and other wireless components). As an additional possibility, the UE (106) may include one or more wireless communication devices shared among a number of wireless communication protocols, and one or more wireless communication devices used exclusively by a single wireless communication protocol. For example, the UE (106) may include a shared wireless communication device for communicating using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and Wi-Fi and Bluetooth. TM It may include separate wireless communication devices for communicating using each. Other configurations are also possible.

[0051] Fig. 3 - Block diagram of an exemplary UE device

[0052] FIG. 3 illustrates a block diagram of an exemplary UE (106) according to some embodiments. As illustrated, the UE (106) may include a system on chip (SOC) (300) that may include parts for various purposes. For example, as illustrated, the SOC (300) may include a processor(s) (302) capable of executing program instructions for the UE (106), and a display circuit (304) capable of performing graphics processing and providing display signals to a display (360). The SOC (300) may also include a sensor circuit (370) that may include components for detecting or measuring any of the various possible characteristics or parameters of the UE (106). For example, the sensor circuit (370) may include a motion detection circuit configured to detect motion of the UE (106) using, for example, a gyroscope, an accelerometer, and / or any of various other motion detection components. As another possibility, the sensor circuit (370) may include one or more temperature sensing components for measuring the temperature of each of one or more antenna panels and / or other components of the UE (106), for example. Any of the various other possible types of sensor circuits may also or alternatively be included in the UE (106). The processor(s) (302) may also be coupled to a memory management unit (MMU) (340) which may be configured to receive addresses from the processor(s) (302) and convert these addresses into locations within memory (e.g., memory (306), read-only memory (ROM) (350), NAND flash memory (310)), and / or other circuits or devices such as a display circuit (304), a wireless communication device (330), a connector I / F (320), and / or a display (360).The MMU (340) may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU (340) may be included as part of the processor(s) (302).

[0053] As illustrated, the SOC (300) can be coupled to various other circuits of the UE (106). For example, the UE (106) may include various types of memory (e.g., NAND flash (310)), a connector interface (320) (for coupling, e.g., to a computer system, dock, charging station, etc.), a display (360), and (e.g., LTE, LTE-A, NR, CDMA2000, Bluetooth). TM It may include a wireless communication circuit (330) for Wi-Fi, GPS, etc. The UE device (106) may include at least one antenna (e.g., 335a) and possibly a plurality of antennas (e.g., illustrated as antennas (335a and 335b)) to perform wireless communication with base stations and / or other devices. The antennas (335a and 335b) are illustrated as examples, and the UE device (106) may include fewer or more antennas. Overall, one or more antennas are collectively referred to as antenna (335). For example, the UE device (106) may use antenna (335) to perform wireless communication with the help of the wireless circuit (330). As mentioned above, the UE may be configured to communicate wirelessly using a plurality of wireless communication standards in some embodiments.

[0054] The UE (106) may include hardware and software components for implementing methods for performing uplink data transmission technologies with improved reliability, as further subsequently described herein. The processor(s) (302) of the UE device (106) may be configured to implement some or all of the methods described herein by executing program instructions stored, for example, on a memory medium (e.g., a non-transient computer-readable memory medium). In other embodiments, the processor(s) (302) may be configured as a programmable hardware element, such as a Field Programmable Gate Array (FPGA), or as an Application-Specific Integrated Circuit (ASIC). Furthermore, the processor(s) (302) may be coupled to and / or interact with other components, such as those shown in FIG. 3, to perform uplink data transmission technologies with improved reliability, according to various embodiments disclosed herein. The processor(s) (302) can also implement various other applications and / or end-user applications running on the UE (106).

[0055] In some embodiments, the wireless communication device (330) may include separate controllers dedicated to controlling communications for various individual RAT standards. For example, as illustrated in FIG. 3, the radio (330) may include a Wi-Fi controller (352), a cellular controller (e.g., an LTE and / or LTE-A controller) (354), and a Bluetooth™ controller (356), and in at least some embodiments, one or more or all of these controllers may be implemented as their respective integrated circuits (briefly, ICs or chips) that communicate with each other and with the SOC (300) (and more specifically with the processor(s) (302). For example, the Wi-Fi controller (352) may and may communicate with the cellular controller (354) via a cell-ISM link or a WCI interface, or the Bluetooth™ controller (356) may communicate with the cellular controller (354) via a cell-ISM link, and so on. Although three distinct controllers are shown in the radio (330), other embodiments have fewer or more similar controllers for various different RATs that can be implemented in the UE device (106).

[0056] Additionally, embodiments are also considered in which controllers can implement functions associated with a number of wireless access technologies. For example, according to some embodiments, the cellular controller (354) may include hardware and / or software components for performing one or more activities associated with Wi-Fi, such as Wi-Fi preamble detection and / or generation and transmission of Wi-Fi physical layer preamble signals, in addition to hardware and / or software components for performing cellular communication.

[0057] Fig. 4 - Block diagram of an exemplary base station

[0058] FIG. 4 illustrates a block diagram of an exemplary base station (102) according to some embodiments. Note that the base station of FIG. 4 is merely an example of a possible base station. As illustrated, the base station (102) may include processor(s) (404) capable of executing program instructions for the base station (102). The processor(s) (404) may also be coupled to a memory management unit (MMU) (440) or other circuits or devices that may be configured to receive addresses from the processor(s) (404) and convert these addresses into locations within memory (e.g., memory (460) and read-only memory (ROM) (450)).

[0059] The base station (102) may include at least one network port (470). The network port (470) may be configured to be coupled to a telephone network and to provide access to the telephone network as described in FIGS. 1 and FIGS. 2 above to a plurality of devices, such as UE devices (106). The network port (470) (or additional network port) may additionally or alternatively be configured to be coupled to a cellular network, for example, a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices, such as UE devices (106). In some cases, the network port (470) may be coupled to a telephone network through the core network, and / or the core network may provide a telephone network (for example, between other UE devices serviced by a cellular service provider).

[0060] The base station (102) may include at least one antenna (434) and possibly multiple antennas. The antenna(s) (434) may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices (106) via a wireless communication device (430). The antenna(s) (434) communicate with the wireless communication device (430) via a communication chain (432). The communication chain (432) may be a receiving chain, a transmitting chain, or both. The wireless communication device (430) may be designed to communicate via various wireless communication standards, including but not limited to NR, LTE, LTE-A WCDMA, CDMA2000, etc. The processor (404) of the base station (102) may be configured to implement and / or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively, the processor (404) may be configured as a programmable hardware element such as an FPGA (Field Programmable Gate Array), as an ASIC (Application-Specific Integrated Circuit), or as a combination thereof. For certain RATs, e.g. Wi-Fi, the base station (102) may be designed as an access point (AP), in which case the network port (470) may be implemented to provide access to a wide area network and / or local area network(s), e.g., it may include at least one Ethernet port, and the wireless communication device (430) may be designed to communicate according to Wi-Fi standards.

[0061] Fig. 5 - Uplink data transmission technologies with improved reliability

[0062] Wireless communication is being used for an increasingly wide range of use cases. For at least some of these types of communications, robustness and reliability can be particularly important. Therefore, it may be useful to expand the range of communication types that can be performed in a very robust and reliable manner.

[0063] One such area may include uplink data communications and / or other communications that can be performed on the physical uplink shared channel (PUSCH) of a cellular communication system. In particular, it may be useful to provide techniques for performing uplink data communications that can benefit from multiple input multiple output (MIMO) capabilities and multiple beam diversity.

[0064] Accordingly, FIG. 5 is a flowchart illustrating a method for performing uplink data communications with improved reliability in a wireless communication system according to at least some embodiments.

[0065] Aspects of the method of FIG. 5 may be implemented by a wireless device, for example, with one or more cellular base stations such as UE (106) and BS (102) illustrated and described in the various drawings of this specification, or more generally, as desired, with any computer circuits, systems, devices, elements, or components illustrated in the drawings among others. For example, the processor (and / or other hardware) of such a device may be configured to enable the device to perform any combination of the illustrated method elements and / or other method elements.

[0066] Although at least some elements of the method of FIG. 5 are described in a manner relating to the use of communication techniques and / or features associated with 3GPP and / or NR specification documents, it should be noted that such description is not intended to limit the scope of the disclosure and that embodiments of the method of FIG. 5 may be used as desired in any suitable wireless communication system. In various embodiments, some of the elements of the illustrated methods may be performed simultaneously, in a different order than illustrated, replaced by other method elements, or omitted. Additional method elements may also be performed as desired. As illustrated, the method of FIG. 5 may operate as follows.

[0067] In 502, a wireless device may establish a wireless link with a cellular base station. According to some embodiments, the wireless link may include a cellular link according to 5G NR. For example, the wireless device may establish a session with an AMF entity of the cellular network by one or more gNBs that provide wireless access to the cellular network. As another possibility, the wireless link may include a cellular link according to LTE. For example, the wireless device may establish a session with a mobility management entity of the cellular network by an eNB that provides wireless access to the cellular network. According to various embodiments, other types of cellular links are also possible, and the cellular network may also or alternatively operate according to other cellular communication technologies (e.g., UMTS, CDMA2000, GSM, etc.).

[0068] Establishing a wireless link may include, according to at least some embodiments, establishing an RRC connection with a serving cellular base station. Establishing the first RRC connection may include any of various other possible features related to configuring various parameters for communication between the wireless device and the cellular base station, configuring context information for the wireless device, and / or, for example, configuring an air interface for the wireless device to perform cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device may operate in an RRC connection state. In some cases, the RRC connection may also be released (for example, after a certain period of inactivity regarding data communication), in which case the wireless device may operate in an RRC idle state or an RRC inactive state. In some cases, the wireless device may perform a handover to a new serving cell (e.g., while in RRC connection mode) or cell reselection (e.g., while in RRC idle or RRC inactive mode) due to, for example, wireless device mobility, changing wireless medium conditions, and / or any of various other possible reasons.

[0069] According to at least some embodiments, a wireless device may establish multiple wireless links with multiple TRPs of a cellular network, for example, according to a multi-TRP configuration. In such a scenario, the wireless device may be configured using one or more Transmit Control Indicators (TCIs) that correspond to various beams that may be used to communicate with the TRPs, for example (e.g., via RRC signaling). Additionally, there may be cases where one or more configured TCI states can be activated by a Media Access Control (MAC) control element (CE) for the wireless device at a specific time.

[0070] In at least some cases, establishing wireless link(s) may involve the wireless device providing capability information about the wireless device. Such capability information may include information regarding any of the various types of wireless device capabilities.

[0071] In 504, the cellular base station may provide uplink data transmission configuration information to the wireless device. Among various possibilities, the uplink data transmission configuration information may be provided using RRC control signaling, MAC signaling (e.g., MAC CE), downlink control information (DCI), or a combination thereof. The uplink data transmission configuration information may configure uplink data transmission to multiple TRPs.

[0072] The uplink data transmission may be any of the various types of uplink data transmissions. As one possibility, the uplink data transmission may be a configured acknowledgment (CG) PUSCH transmission, such as a 3GPP Type 1 CG-PUSCH transmission (e.g., which may be configured by the RRC ConfiguredGrantConfig information element) or a 3GPP Type 2 CG-PUSCH transmission (e.g., which may be enabled or disabled by DCI format 0_0, 0_1, or 0_2 having a Cyclic Redundant Code (CRC) scheduled by the configured Scheduled Radio Network Temporary Identifier (CS-RNTI). As another possibility, the uplink data transmission may be a dynamic acknowledgment (DG) PUSCH transmission, such as a 3GPP Type A PUSCH repeat or a 3GPP Type B PUSCH repeat. As yet another possibility, the uplink data transmission may be a 3GPP non-codebook-based (NCB) PUSCH transmission.

[0073] According to some embodiments, uplink data transmission configuration information may configure a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs. One such possible pattern may include transmitting individual repetitions to multiple TRPs in an alternating manner. Another such possible pattern may include transmitting sequences of repetitions (e.g., of a specific length) to multiple TRPs in an alternating manner. Yet another possible pattern may include alternating TRP transmissions being performed in alternating slots.

[0074] According to some embodiments, uplink data transmission configuration information includes information representing one or more parameters for each TRP associated with uplink transmission. For example, such information may include any or all of beam information, precoding information, path loss reference signal information, target received power information, and / or path loss compensation factors for each TRP associated with uplink transmission.

[0075] Such configuration information may be provided in any of the various possible ways. For example, in the case of 3GPP Type 1 CG-PUSCH transmission, some or all of these parameters may be configured using various fields of the RRC information elements that constitute the CG-PUSCH transmission. Thus, to potentially represent beam information for each TRP associated with the uplink transmission, among the various possibilities, it may be possible to provide separate beam configuration fields for each TRP or to provide a single beam configuration field containing a beam configuration index value associated with multiple beam configurations. Similarly, to potentially represent precoding information for each TRP associated with the uplink transmission, among the various possibilities, it may be possible to provide separate precoding configuration fields for each TRP or to provide a single precoding configuration field containing a precoding configuration index value associated with multiple precoding configurations. Likewise, to potentially represent path loss reference signal information for each TRP associated with uplink transmission, among various possibilities, it may be possible to provide separate path loss reference signal configuration fields for each TRP, or to provide a single path loss reference signal configuration field containing a path loss reference signal configuration index value associated with multiple path loss reference signal configurations.

[0076] As another example, in the case of 3GPP Type B DG PUSCH iterations, various parameters may be configured independently by the DCI for each TRP. For example, any of all P0 parameters (target received power), alpha parameters (path loss compensation factor), path loss reference signal, beam (e.g., in the form of TCI or Sounding Reference Signal (SRS) Resource Indicator (SRI)), and / or transmit precoding matrix indicator (TPMI) and the number of layers may be indicated by the DCI in this scenario.

[0077] As previously mentioned in this specification, in some cases, uplink data transmission configuration information may configure 3GPP non-codebook-based (NCB) PUSCH transmissions. In such scenarios, the uplink data transmission configuration information may configure multiple sets of SRS resources, each set of SRS resources configured using a non-zero power channel state information reference signal (NZP-CSI-RS). For example, NZP-CSI-RS may be configured for each TRP to which an NCB PUSCH transmission is scheduled, and NZP-CSI-RS may effectively configure a set of SRS resources that is logically mapped to that TRP.

[0078] In some cases, when two sets of SRS resources are configured and each is mapped to a single TRP, two SRS resource indicator fields may be set in DCI formats 0_1 and 0_2 for NCB-based PUSCH operations. In this scenario, each SRS resource indicator field may be mapped to one set of SRS resources when the NCB is configured.

[0079] As another possibility, the uplink data transmission configuration information may configure an SRS resource set, and the SRS resource set is associated with multiple NZP-CSI-RS resources. For example, a first portion of the SRS resources in the SRS resource set may be associated with a first TRP, and a second portion of the SRS resources in the SRS resource set may be associated with a second TRP. Along with this scenario, note that as a possibility, the number of SRS resources that can be configured per SRS resource set may be increased, for example, from 4 to 8 (e.g., to support the possibility of including sufficient SRS resources for PUSCH transmission to multiple TRPs). In at least some cases, mapping each SRS resource to an associated NZP-CSI-RS resource may be configured by RRC control signaling.

[0080] In 506, the wireless device may perform uplink data transmission to multiple TRPs. Uplink data transmission may be performed according to uplink data transmission configuration information, for example, potentially including using different configuration parameters when transmitting to each of the configured TRPs. Uplink data transmission may be performed, for example, using a configured transmission pattern where applicable.

[0081] Note that, according to at least some embodiments, there may be cases where a duplexing conflict exists (e.g., when downlink communication is scheduled during a PUSCH iteration for a wireless device configured for half-duplex operation), and / or when a PUSCH iteration is scheduled across slot boundaries, a nominally scheduled PUSCH iteration may be truncateable. In such scenarios, there may be a mechanism for determining which TRP each actual iteration is transmitted to, for example, according to a configured transmission pattern. For example, as one possibility, the wireless device may be configured to determine which TRP each actual uplink data transmission is performed to, according to a configured transmission pattern, based on nominal iterations of uplink data transmission. As another possibility, the wireless device may be configured to determine which TRP each actual uplink data transmission is performed to, according to a configured transmission pattern, based on actual iterations of uplink data transmission. As another possibility, the wireless device may be configured to determine which TRP to perform each actual uplink data transmission according to the configured transmission pattern, based on the slot where the uplink data transmission is performed.

[0082] Uplink data transmission can be received by a cellular network. For example, each TRP scheduled to perform uplink data transmission can receive at least a portion (e.g., one or more iterations) of the uplink data transmission from a wireless device.

[0083] Accordingly, the method of FIG. 5 can be used to provide a framework for more reliably configuring and performing uplink data transmissions in a cellular communication system. Such a framework may be particularly useful, depending on at least some embodiments, for supporting improved PUSCH reliability by utilizing the potential availability of multiple TRPs and multiple wireless device antenna panels to provide increased beam variety for uplink data communications, among other possible advantages.

[0084] FIGS. 6 to 10 and additional information

[0085] FIGS. 6 through 10 illustrate additional embodiments that may be used in conjunction with the method of FIG. 5, if desired. However, it should be noted that the exemplary details illustrated and described with respect to FIGS. 6 through 10 are not intended to limit the entirety of the disclosure: numerous variations and alternatives to the details provided below are possible and should be considered within the scope of the disclosure.

[0086] 3GPP Release 16 supports multi-TRP designs for improved Physical Downlink Shared Channel (PDSCH) performance. This support may involve the use of multiple DCIs across up to five sets of control resources (CORESETs) to schedule up to two PDSCHs. It is also possible for a single DCI to schedule multiple PDSCHs in several possible modes, including Spatial Division Multiplexing (SDM) mode with fully overlapping PDSCHs, Frequency Division Multiplexing (FDM) mode with a single transmit block (TB), FDM mode with two TBs, In-Slot Time Division Multiplexing (TDM) mode, and Inter-Slot TDM mode.

[0087] 3GPP Release 16 may also support type B physical uplink shared channel (PUSCH) repeats for improved reliability. For example, in control signaling (e.g., in PUSCH-Allocator-r16 of PUSCH-TimeDomainResourceAllocationListPUSCH-r16), a parameter (e.g., numberOfRepertions-r16) may be added to allow dynamic variations in the number of PUSCH repeats through the DCI. Nominal repeats may be performed back-to-back if configured. When nominal repeats are performed across slot boundaries or conflict with the duplexing direction, the nominal PUSCH transmission may be cut off.

[0088] For example, additional improvements to PUSCH reliability may be possible by providing support for PUSCH transmissions to multiple TRPs. For example, techniques for configuring and performing configured acknowledgments (CG), dynamic acknowledgments (DG), and / or non-codebook-based (NCB) PUSCH transmissions to multiple TRPs are described herein, which can help improve PUSCH reliability in at least some cases.

[0089] According to some embodiments, there may be two types of CG PUSCH supported in 3GPP communications. In 3GPP Type I CG-PUSCH, the CG-PUSCH may be configured by an RRC ConfiguredGrantConfig information element (IE). In 3GPP Type II CG-PUSCH, the CG-PUSCH may be enabled or disabled by DCI format 0_0, 0_1, or 0_2, having a Cyclic Redundant Code (CRC) scrambled by a configured Scheduling Radio Network Temporary Identifier (CS-RNTI).

[0090] For 3GPP Type I CG PUSCH, modifications may be introduced to the way RRC configuration is performed to provide support for multi-TRP PUSCH operations. These modifications may include providing a mechanism for signaling different precoding, beaming, and / or path loss reference signals for different TRPs. According to 3GPP TS 38.331, v.16.1.0, section (6.3.2), the ConfiguredGrantConfig information element may be used to configure uplink transmission without dynamic acknowledgment and may include an rrc-ConfiguredUplinkGrant field. This field may include the precodingAndNumberOfLayers parameter, the srs-ResourceIndicator parameter, and the pathlossReferenceIndex parameter, which may be used to indicate the precoding, beaming, and path loss reference signals for CG-PUSCH operations.

[0091] As one possibility for providing support for representing different precodings for different TRPs in such an IE, an additional field (e.g., 'additional-precodingAndNumberOfLayers') may be introduced to configure a precoder for a second TRP, potentially allowing two different precoding configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of precodingAndNumberOfLayers code points, each precodingAndNumberOfLayers code point may include one or two entries of the uplink rank and transmit precoding matrix indicator (TPMI), and the precodingAndNumberOfLayers parameter may be used to represent the precodingAndNumberOfLayers code point.

[0092] As one possibility for providing support for representing different beams for different TRPs in such IE, an additional field (e.g., 'additional-srs-ResourceIndicator') may be introduced to configure a beam for a second TRP, potentially allowing two different beam configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of SRS resource code points, each of which may contain one or two sets of SRS resources, and the srs-ResourceIndicator parameter may be used to represent the SRS resource code point.

[0093] As one possibility for providing support for representing different path loss reference signals for different TRPs in such an IE, an additional field (e.g., 'additional-pathlossReferenceIndex') may be introduced to configure the path loss reference signal for the second TRP, potentially allowing two different path loss reference signal configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of pathlossReferenceIndex code points, each pathlossReferenceIndex may contain one or two path loss reference signal configurations, and the pathlossReferenceIndex parameter may be used to represent the pathlossReferenceIndex code point.

[0094] In the case of 3GPP Type I CG-PUSCH, when different beams, precodings, and / or path loss reference signals are configured per TRP, there may be multiple possible mappings for actual PUSCH transmissions. FIGS. 6 through 8 illustrate some of these possible transmission patterns according to some embodiments.

[0095] FIG. 6 illustrates an exemplary possible transmission pattern in which TRPs in which PUSCH transmissions are performed alternate in a cyclic pattern for each repetition opportunity, for example, so that TRPs in which PUSCH transmissions are performed alternate for each transmission opportunity.

[0096] FIG. 7 illustrates an exemplary possible transmission pattern in which TRPs on which PUSCH transmissions are performed alternate in a sequential pattern per repetition opportunity, for example, such that the TRP on which a PUSCH transmission is performed alternates after a sequence of PUSCH transmissions of a specified length is performed. In the illustrated example, the sequence length may include two PUSCH transmissions.

[0097] FIG. 8 illustrates an exemplary possible transmission pattern in which TRPs performing PUSCH transmissions alternate in a slot-by-slot cyclic pattern, for example, so that TRPs performing PUSCH transmissions alternate in each slot.

[0098] Additionally, in the case of type I CG-PUSCH, according to at least some embodiments, powerControlLoopToUse and / or p0-PUSCH-Alpha parameters related to open-loop power control (OLPC) may additionally or alternatively be configured independently for each TRP.

[0099] According to some embodiments, for example, to transmit PUSCH iterations to multiple TRPs, it may be possible to use techniques similar to those described herein in relation to 3GPP Type I CG PUSCH operations for 3GPP Type A DG PUSCH operations.

[0100] For Type B DG PUSCH iterations, various parameters for each TRP may be independently configured / indicated by the DCI. These parameters may include some or all of P0 (e.g., target received power), alpha (e.g., path loss compensation factor), path loss reference signal, beam used for transmission (e.g., in the form of a transmit configuration indicator (TCI) or sounding reference signal (SRI) resource indicator), and / or TPMI and the number of layers.

[0101] In the case of such Type B DG PUSCH iterations, when one or more parameters are configured independently for each of the multiple TRPs, there may be multiple possibilities for mapping nominal PUSCH iterations to actual PUSCH transmissions, for example, by considering possible truncation of the nominal PUSCH transmission due to dual-directional conflict or the intersection of slot boundaries by the nominal PUSCH transmission. FIG. 9 illustrates some of these possible options that can be used to map nominal PUSCH iterations to actual PUSCH transmissions according to at least some embodiments.

[0102] As described, in the first option (910), the mapping of which TRP the actual PUSCH transmission is transmitted to may be based on nominal iterations. Thus, in this approach, the first actual PUSCH iteration may be transmitted to TRP1, the second and third actual PUSCH iterations may be transmitted to TRP2, the fourth and fifth actual PUSCH iterations may be transmitted to TRP1, and the sixth actual PUSCH iteration may be transmitted to TRP2.

[0103] In the second option (920) illustrated, the mapping of which TRP the actual PUSCH transmission is transmitted to may be based on the actual iteration. Thus, in this approach, the first actual PUSCH iteration may be transmitted to TRP1, the second actual PUSCH iteration may be transmitted to TRP2, the third actual PUSCH iteration may be transmitted to TRP1, the fourth actual PUSCH iteration may be transmitted to TRP2, the fifth actual PUSCH iteration may be transmitted to TRP1, and the sixth actual PUSCH iteration may be transmitted to TRP2.

[0104] In the illustrated third option (930), the mapping of which TRP the actual PUSCH transmission is transmitted to may be based on the slot in which the PUSCH transmission is performed. Thus, in this approach, the first, second, and third actual PUSCH iterations may be transmitted to TRP1, and the fourth, fifth, and sixth actual PUSCH iterations may be transmitted to TRP2.

[0105] In the case of NCB PUSCH operation, according to at least some embodiments, it may be possible to support multi-TRP PUSCH operation by configuring more than one SRS-ResourceSet. FIG. 10 illustrates aspects of this approach according to some embodiments. As illustrated, in the illustrated example, each SRS-ResourceSet is logically mapped to one TRP. Each SRS-ResourceSet may be composed of different non-zero-power channel state information reference signal resource identifiers (NZP-CSI-RS-ResourceId), each of which may be transmitted from different TRPs.

[0106] In some cases, for NCB PUSCH operations, when two SRS-ResourceSets are configured, each mapped to a single TRP, it may be possible to configure two SRS resource indicator fields in 3GPP DCI formats 0_1 and 0_2. In this scenario, each SRS resource indicator field can be mapped to a single SRS-ResourceSet using "nonCodebook".

[0107] As an additional possibility, for NCB PUSCH operations, a single SRS-ResourceSet may be configured, which may include more than one associated NZP-CSI-RS-ResourceId. In this scenario, the number of SRS resources that can be configured per SRS-ResourceSet may increase, for example, from 4 to 8. The mapping of each SRS resource of the SRS-ResourceSet to an associated NZP-CSI-RS-ResourceId can be configured by RRC control signaling. Therefore, it may also be possible to support multi-TRP NCB PUSCH operations using this configuration.

[0108] Additional exemplary embodiments are provided below.

[0109] A set of embodiments may include a baseband processor configured to perform operations, the operations including: establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information, wherein the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs); and performing uplink data transmission to multiple TRPs.

[0110] According to some embodiments, uplink data transmission configuration information configures a 3GPP-configured authorized physical uplink shared channel (PUSCH) transmission.

[0111] According to some embodiments, uplink data transmission configuration information configures 3GPP dynamically acknowledged physical uplink shared channel (PUSCH) transmission.

[0112] According to some embodiments, uplink data transmission configuration information configures 3GPP non-codebook based physical uplink shared channel (PUSCH) transmission.

[0113] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs.

[0114] According to some embodiments, the uplink data transmission configuration information includes, for each TRP associated with the uplink transmission, information representing one or more of beam information; precoding information; path loss reference signal information; target received power information; or path loss compensation factors.

[0115] Other sets of embodiments may include a wireless device, the wireless device comprising: an antenna; a wireless communication device operably coupled to the antenna; and a processor operably coupled to the wireless communication device, the wireless device comprising: establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information—the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs)—; and performing uplink data transmission to multiple TRPs.

[0116] According to some embodiments, uplink data transmission configuration information includes beam information for each TRP associated with uplink transmission, and the beam information for each TRP is represented using one of separate beam configuration fields for each TRP; or a single beam configuration field including a beam configuration index value associated with a plurality of beam configurations.

[0117] According to some embodiments, uplink data transmission configuration information includes precoding information for each TRP associated with uplink transmission, and the precoding information for each TRP is represented using one of separate precoding configuration fields for each TRP; or a single precoding configuration field including a precoding configuration index value associated with a plurality of precoding configurations.

[0118] According to some embodiments, uplink data transmission configuration information includes path loss reference signal information for each TRP associated with uplink transmission, and the path loss reference signal information for each TRP is represented using one of separate path loss reference signal configuration fields for each TRP; or a single path loss reference signal configuration field including a path loss reference signal configuration index value associated with a plurality of path loss reference signal configurations.

[0119] According to some embodiments, for each TRP associated with uplink transmission, the uplink data transmission configuration information independently comprises one or more of target reception power information or path loss compensation factors.

[0120] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, individual repetitions are transmitted to multiple TRPs in an alternating manner.

[0121] According to some embodiments, uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, sequences of repetitions are transmitted to multiple TRPs in an alternating manner.

[0122] According to some embodiments, uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, transmissions are performed to alternating TRPs in alternating slots.

[0123] Another set of embodiments may include a method, the method comprising: establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information, wherein the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs); and performing uplink data transmission to multiple TRPs.

[0124] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern to determine which of the multiple TRPs each iteration of uplink data transmission will be performed, and when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, the method further includes the step of determining which of the multiple TRPs each actual uplink data transmission will be performed according to the transmission pattern based on the nominal iterations of uplink data transmission.

[0125] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern to determine which of the multiple TRPs each iteration of uplink data transmission will be performed, and when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, the method further includes the step of determining which of the multiple TRPs each actual uplink data transmission will be performed according to the transmission pattern based on the actual iterations of uplink data transmission.

[0126] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern to determine which of the multiple TRPs each iteration of uplink data transmission will be performed, and when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, the method further includes the step of determining which of the multiple TRPs uplink data transmission will be performed according to the transmission pattern based on the slot in which the uplink data transmission will be performed.

[0127] According to some embodiments, uplink data transmission configuration information configures a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission, and the uplink data transmission configuration information configures a plurality of sounding reference signal resource sets, and each sounding reference signal resource set is configured using a non-zero power channel state information reference signal.

[0128] According to some embodiments, uplink data transmission configuration information configures a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission, and uplink data transmission configuration information configures a sounding reference signal resource set, and the sounding reference signal resource set is associated with a plurality of non-zero power channel state information reference signals, and a first portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a first TRP, and a second portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a second TRP.

[0129] Embodiments of an additional set may include a device comprising a processor, wherein the processor enables a cellular base station to establish a wireless link with a wireless device; provides uplink data transmission configuration information to the wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs); and is configured to receive at least a portion of the uplink data transmission to multiple TRPs.

[0130] According to some embodiments, uplink data transmission configuration information configures a 3GPP-configured authorized physical uplink shared channel (PUSCH) transmission.

[0131] According to some embodiments, uplink data transmission configuration information configures 3GPP dynamically acknowledged physical uplink shared channel (PUSCH) transmission.

[0132] According to some embodiments, uplink data transmission configuration information configures 3GPP non-codebook based physical uplink shared channel (PUSCH) transmission.

[0133] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs.

[0134] According to some embodiments, the uplink data transmission configuration information includes, for each TRP associated with the uplink transmission, information including one or more of beam information; precoding information; path loss reference signal information; target received power information; and path loss compensation factors.

[0135] Embodiments of another additional set may include a cellular base station, the cellular base station comprising: an antenna; a radio communication device operably coupled to the antenna; and a processor operably coupled to the radio communication device, the cellular base station comprising: establishing a radio link with a radio device; providing uplink data transmission configuration information to the radio device, wherein the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs); and being configured to receive at least a portion of uplink data transmission to multiple TRPs.

[0136] According to some embodiments, uplink data transmission configuration information includes beam information for each TRP associated with uplink transmission, and the beam information for each TRP is represented using one of separate beam configuration fields for each TRP; or a single beam configuration field including a beam configuration index value associated with a plurality of beam configurations.

[0137] According to some embodiments, uplink data transmission configuration information includes precoding information for each TRP associated with uplink transmission, and the precoding information for each TRP is represented using one of separate precoding configuration fields for each TRP; or a single precoding configuration field including a precoding configuration index value associated with a plurality of precoding configurations.

[0138] According to some embodiments, uplink data transmission configuration information includes path loss reference signal information for each TRP associated with uplink transmission, and the path loss reference signal information for each TRP is represented using one of separate path loss reference signal configuration fields for each TRP; or a single path loss reference signal configuration field including a path loss reference signal configuration index value associated with a plurality of path loss reference signal configurations.

[0139] According to some embodiments, for each TRP associated with uplink transmission, the uplink data transmission configuration information independently comprises one or more of target reception power information or path loss compensation factors.

[0140] According to some embodiments, uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, individual repetitions are transmitted to the multiple TRPs in an alternating manner.

[0141] According to some embodiments, uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, sequences of repetitions are transmitted to multiple TRPs in an alternating manner.

[0142] According to some embodiments, uplink data transmission configuration information configures a transmission pattern for performing repetitions of uplink data transmission to multiple TRPs, and according to the transmission pattern, transmissions are performed to alternating TRPs in alternating slots.

[0143] Other additional sets of embodiments may include a method, the method comprising: establishing a wireless link with a wireless device by a cellular base station; providing uplink data transmission configuration information to the wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to multiple transmission and reception points (TRPs); and receiving at least a portion of the uplink data transmission to multiple TRPs.

[0144] According to some embodiments, uplink data transmission configuration information configures a transmission pattern to determine which of multiple TRPs each iteration of uplink data transmission will be performed to, and according to the transmission pattern, when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, which of multiple TRPs each actual uplink data transmission will be performed to is determined based on the nominal iteration of uplink data transmission.

[0145] According to some embodiments, uplink data transmission configuration information configures a transmission pattern to determine which of the multiple TRPs each iteration of uplink data transmission will be performed to, and according to the transmission pattern, when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, which of the multiple TRPs each actual uplink data transmission will be performed to is determined based on the actual iteration of uplink data transmission.

[0146] According to some embodiments, uplink data transmission configuration information configures a transmission pattern to determine which of the multiple TRPs each iteration of uplink data transmission will be performed to, and according to the transmission pattern, when the nominal uplink data transmission is cut off due to double conflict or scheduling across slot boundaries, which of the multiple TRPs each actual uplink data transmission will be performed to is determined based on the slot in which the uplink data transmission is performed.

[0147] According to some embodiments, uplink data transmission configuration information constitutes at least a portion of a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission, and additional uplink data transmission configuration information is also provided to the wireless device, wherein the uplink data transmission configuration information constitutes a non-zero power channel state information reference signal associated with a sounding reference signal resource set and additional non-zero power channel state information reference signal associated with an additional sounding reference signal resource set.

[0148] According to some embodiments, uplink data transmission configuration information constitutes at least a portion of a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission, and the uplink data transmission configuration information constitutes a sounding reference signal resource set, the sounding reference signal resource set is associated with a plurality of non-zero power channel state information reference signals, a first portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a first TRP, and a second portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a second TRP.

[0149] Further exemplary embodiments may include a method comprising the step of performing any or all of the preceding examples by a device.

[0150] Another exemplary embodiment may include a device, the device may include an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, and the device is configured to implement any or all of the prior examples.

[0151] An additional set of exemplary embodiments may include a non-transient computer-accessible memory medium comprising program instructions that, when executed on a device, cause the device to implement any or all parts of any of the preceding examples.

[0152] Other additional exemplary sets of embodiments may include computer programs containing instructions for performing any or all parts of any of the prior examples.

[0153] Another set of exemplary embodiments may include a device comprising means for performing any or all of the elements of any of the preceding examples.

[0154] Another set of exemplary embodiments may include a device comprising a processing element configured to cause the device to perform any or all elements of any of the preceding examples.

[0155] Other exemplary sets of embodiments may include a baseband processor configured to perform operations including any or all of the elements of any of the preceding examples.

[0156] It is well understood that the use of personally identifiable information must follow privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining users' privacy. In particular, personally identifiable information data must be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of authorized use must be clearly indicated to users.

[0157] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station by interpreting each message / signal X received by the UE in the downlink as a message / signal X transmitted by the base station and each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station.

[0158] Embodiments of the present disclosure may be realized in any of various forms. For example, in some embodiments, the subject matter of the present invention may be realized as a computer-implemented method, a computer-readable memory medium, or a computer system. In other embodiments, the subject matter may be realized using one or more custom-designed hardware devices, such as ASICs. In other embodiments, the subject matter may be realized using one or more programmable hardware elements, such as FPGAs.

[0159] In some embodiments, a non-transient computer-readable memory medium (e.g., a non-transient memory element) may be configured to store program instructions and / or data, wherein the program instructions, when executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets.

[0160] In some embodiments, a device (e.g., UE) may be configured to include a processor (or set of processors) and a memory medium (or, memory element), wherein the memory medium stores program instructions, the processor is configured to read and execute program instructions from the memory medium, and the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be realized in any of the various forms.

[0161] Although the above embodiments have been described in considerable detail, once the above disclosure is sufficiently recognized, many variations and modifications will be obvious to those skilled in the art. The following claims are intended to be interpreted to encompass all such variations and modifications.

Claims

Claim 1 A method comprising: receiving a configuration including multiple sounding reference signal (SRS) resource sets for use in a non-codebook based physical uplink shared channel (PUSCH) multiple transmission and reception point (TRP) operation; performing uplink data transmission based on a downlink control information (DCI) format 0_1 ​​or 0_2 including multiple SRS resource indicators (SRIs) corresponding to each of the multiple SRS resource sets; and performing Type 1 configured uplink acknowledgment uplink data transmission, wherein the step of performing Type 1 configured uplink acknowledgment uplink data transmission includes transmitting each of the multiple uplink transmission repetitions through multiple slots according to different SRIs of the multiple SRIs, wherein only one of the multiple SRIs is applied in each of the multiple slots. Claim 2 A method according to claim 1, wherein the configuration comprises mapping each of the plurality of SRS resource sets to different non-zero-power channel state information reference signal resource identifiers (NZP-CSI-RS-ResourceId). Claim 3 A method according to claim 1, wherein each of the plurality of SRS resource sets is logically mapped to each of the plurality of TRPs. Claim 4 A method according to claim 1, wherein a type A repetition is applied to the uplink acknowledgment uplink data transmission configured as Type 1. Claim 5 A method according to claim 1, wherein a type B repetition is applied to the uplink acknowledgment uplink data transmission configured as Type 1. Claim 6 In claim 1, each of the plurality of SRS resource sets is logically mapped to each of the plurality of TRPs, independent parameters are configured for each of the plurality of TRPs, and a target received power; a path loss compensation factor; a path loss reference signal - each of the plurality of SRIs is mapped to one TRP, and each path loss reference signal is indicated for each of the plurality of TRPs through the plurality of SRIs -; or at least one of a transmit precoding matrix indicator and a number of layers. Claim 7 A processor comprising a memory storing instructions, wherein, when the instructions are executed, the processor transmits to a wireless device a configuration comprising multiple sets of sounding reference signals (SRS) resources for use in non-codebook-based physical uplink shared channel (PUSCH) multiple transmit / receive points (TRP) operations; receives an uplink data transmission as one of multiple TRPs based on a DCI (downlink control information) format 0_1 ​​or 0_2 comprising multiple SRS resource indicators (SRIs) corresponding to each of the multiple SRS resource sets; and receives a Type 1 configured uplink acknowledgment uplink data transmission as one of the multiple TRPs, comprising each of the multiple uplink transmission repetitions of the multiple uplink transmissions through multiple slots according to different SRIs of the multiple SRIs, wherein only one of the multiple SRIs is applied in each of the multiple slots. Claim 8 In claim 7, the configuration comprises a processor comprising mapping each of the plurality of SRS resource sets to different non-zero power channel state information reference signal resource identifiers (NZP-CSI-RS-ResourceId). Claim 9 In paragraph 7, each of the plurality of SRS resource sets is a processor that is logically mapped to each of the plurality of TRPs. Claim 10 In paragraph 7, the Type 1 configured uplink acknowledgment uplink data transmission is associated with a Type A iteration, a processor. Claim 11 In paragraph 7, the Type 1 configured uplink acknowledgment uplink data transmission is associated with a Type B repetition, a processor. Claim 12 In claim 7, each of the plurality of SRS resource sets is logically mapped to each of the plurality of TRPs, independent parameters are configured for each of the plurality of TRPs, and a target received power; a path loss compensation factor; a path loss reference signal - each of the plurality of SRIs is mapped to one TRP, and each path loss reference signal is indicated for each of the plurality of TRPs through the plurality of SRIs -; or a processor comprising at least one of a transmit precoding matrix indicator and a number of layers. Claim 13 A method comprising: receiving a configuration including a plurality of sounding reference signal (SRS) resource indicators for use in non-codebook-based physical uplink shared channel (PUSCH) multiple transmit / receive points (TRP) operation; performing uplink data transmission based on a downlink control information (DCI) format 0_1 ​​or 0_2 including a plurality of SRS resource indicators (SRIs) corresponding to each of the respective SRS resource sets of the plurality of SRS resource sets; and performing Type 1 configured uplink acknowledgment uplink data transmission, wherein the step of performing Type 1 configured uplink acknowledgment uplink data transmission includes transmitting each of the plurality of uplink transmission repetitions through a plurality of slots according to different SRIs of the plurality of SRIs, wherein only one of the plurality of SRIs is applied in each of the respective slots of the plurality of slots. Claim 14 In claim 13, the method wherein the Type 1 configured uplink approval configuration comprises a plurality of precodingAndNumberOfLayers values ​​corresponding to the plurality of TRPs. Claim 15 In paragraph 13, the method wherein the Type 1 configured uplink approval configuration comprises a plurality of pathlossReferenceIndex values ​​corresponding to the plurality of TRPs. Claim 16 In paragraph 13, the method wherein the Type 1 configured uplink approval configuration comprises a plurality of powerControlLoopToUse and a plurality of p0-PUSCH-Alpha values ​​corresponding to the plurality of TRPs. Claim 17 In paragraph 13, a method wherein each of the multiple SRS resource sets is logically mapped to each of the multiple TRPs. Claim 18 In paragraph 13, the transmission of uplink acknowledgment uplink data configured as Type 1 is associated with a Type A repetition, a method. Claim 19 In paragraph 13, the method wherein the Type 1 configured uplink acknowledgment uplink data transmission is associated with a Type B repetition. Claim 20 In claim 13, each of the plurality of SRS resource sets is logically mapped to each of the plurality of TRPs, independent parameters are configured for each of the plurality of TRPs, and a target received power; a path loss compensation factor; a path loss reference signal - each of the plurality of SRIs is mapped to one TRP, and each path loss reference signal is indicated for each of the plurality of TRPs through the plurality of SRIs -; or at least one of a transmit precoding matrix indicator and a number of layers.

Images