Improved reliability in physical uplink shared channel transmission

Abstract

The present invention provides a system, apparatus, and method for performing physical uplink shared channel transmission with improved reliability in a wireless communication system. [Solution] In a method for providing physical uplink shared channel transmission, a wireless device establishes a wireless link with a cellular base station and receives uplink data transmission configuration information from the cellular base station. The uplink data transmission configuration information constitutes uplink data transmission to multiple transmission / reception points. The wireless device further performs uplink data transmission to the multiple transmission / reception points.

Description

Technical Field

[0001] This application relates to wireless communication, and more specifically, to a system, apparatus, and method for performing physical uplink shared channel transmission with improved reliability in a wireless communication system.

Background Art

[0002] The use of wireless communication systems has been increasing rapidly. In recent years, wireless devices such as smartphones and tablet computers have become increasingly more powerful. Currently, many mobile devices (i.e., user equipment devices, or UEs) not only support telephone calls, but also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate high-performance applications that utilize these functions. In addition, there are numerous different wireless communication technologies and standards. Some examples of wireless communication standards include GSM, UMTS (associated with, for example, the WCDMA (registered trademark) or TD-SCDMA air interface), LTE, LTE Advanced (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE802.11 (WLAN or Wi-Fi), BLUETOOTH (registered trademark), and the like.

[0003] As the features and functions introduced into wireless communication devices constantly increase, a continuous need arises to improve both wireless communication and wireless communication devices. In particular, it is crucial to ensure the accuracy of transmitted and received signals via user equipment (UE) devices, such as cellular phones, base stations, and relay stations used in wireless cellular communications. In addition, increasing the functionality of UE devices can place a significant burden on their battery life. Therefore, it is also very important to reduce the power requirements of UE devices while ensuring they maintain good transmission and reception capabilities to improve communication. Thus, improvements in this area are desirable. [Overview of the project]

[0004] This specification presents embodiments of apparatus, systems, and methods for performing physically uplink shared channel transmission with improved reliability in wireless communication systems.

[0005] According to the technology described herein, a wireless device can receive uplink data transmission configuration information that constitutes uplink data transmission to multiple transmission / reception points, and can perform uplink data transmission to multiple transmission / reception points. The uplink data transmission may be any of various types of uplink data transmission, 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] According to at least some embodiments, performing uplink data transmission in such a manner may help improve the reliability of uplink data communications by taking advantage of the potential for beam diversity that may be possible when uplink data may be provided to multiple transmission and reception points.

[0007] It should be noted that the technologies described herein may be implemented in and / or used in 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 powered vehicles, and various other computing devices.

[0008] This summary of the invention is intended to provide a brief overview of some of the subject matter described herein. Therefore, it should be understood that the features described above are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein. 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 this subject can be obtained when the following detailed descriptions of various embodiments are considered together with the following drawings.

[0010] [Figure 1] Several exemplary (and simplified) wireless communication systems according to certain embodiments are shown.

[0011] [Figure 2] An exemplary base station communicating with an exemplary wireless user equipment (UE) device is shown according to several embodiments.

[0012] [Figure 3] An exemplary block diagram of a UE according to several embodiments is shown.

[0013] [Figure 4] An exemplary block diagram of a base station according to several embodiments is shown.

[0014] [Figure 5]This flowchart illustrates exemplary methods for providing improved reliability of physical uplink shared channel transmission in a wireless communication system, according to several embodiments.

[0015] [Figure 6] The following are exemplary embodiments of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmission according to several embodiments. [Figure 7] The following are exemplary embodiments of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmission according to several embodiments. [Figure 8] The following are exemplary embodiments of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmission according to several embodiments.

[0016] [Figure 9] The following illustrates various possible exemplary approaches for mapping TRP to iterations for dynamic grant physical uplink shared channel transmissions, according to several embodiments.

[0017] [Figure 10] This figure shows exemplary embodiments of possible non-codebook-based physical uplink shared channel operation according to several embodiments.

[0018] While various modifications and alternative forms are possible for the features described herein, specific embodiments are shown in the drawings as examples and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit the invention to any particular form, but rather to encompass all modifications, equivalents, and alternatives within the spirit and scope of the subject matter as defined by the appended claims. [Modes for carrying out the invention]

[0019] acronym Various acronyms are generally used throughout the present disclosure. The definitions of the most prominently used acronyms that may appear throughout the present disclosure are as follows. ● UE: User Equipment ● RF: Radio Frequency ● BS: Base Station ● GSM: Global System for Mobile Communications ● UMTS: Universal Mobile Telecommunications System ● LTE: Long Term Evolution ● NR: New Radio ● TX: Transmit / Transmitting ● RX: Receive / Receiving ● RAT: Radio Access Technology ● TRP: Transmission and Reception Point ● DCI: Downlink Control Information ● CORESET: Control Resource Set ● CSI: Channel State Information ● CSI-RS: Channel State Information Reference Signal term The following is an explanation of terms that may appear in the present disclosure.

[0020] Memory medium – any of the various types of non-temporary memory devices or storage devices. The term “memory medium” is intended to include, for example, installation media such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM; non-volatile memory such as flash, magnetic media such as hard drives, or optical storage, registers, or other similar types of memory elements. Storage medium may include other types of non-temporary memory, or combinations thereof. In addition, the memory medium may be located in a first computer system on which a program is executed, or in a second different 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 the first computer system with program instructions to be executed. The term “memory medium” may include two or more memory mediums that may exist in different locations, for example, in different computer systems connected via a network. The memory medium may store program instructions (embodied, for example, as computer programs) that can be executed by one or more processors.

[0021] Carrier medium - memory media as described above, as well as physical transmission media such as buses and networks, and / or other physical transmission media that transmit signals such as electrical signals, electromagnetic signals, or digital signals.

[0022] Computer system (or computer) – any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network equipment, 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 include any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0023] User equipment (UE) (or "UE device") - any computer system or device of any kind that is mobile or portable and performs wireless communication. 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 powered vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), and unmanned aerial controllers (UACs). Generally, the terms "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communication.

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

[0025] A communication device is 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) or fixed or permanently installed in a specific location. A wireless device is an example of a communication device. A UE is another example of a communication device.

[0026] Base station (BS) - The term "base station" has all of its ordinary meanings and includes at least a radio communication station that is installed in a fixed location and used for communication as part of a radiotelephone system or a radio system.

[0027] Processing element (or processor) refers to various elements or combinations of elements that can perform functions within a device, for example, within a user equipment device or within a cellular network device. Processing elements may include, for example, processors and associated memory, parts or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as Application Specific Integrated Circuits (ASICs), programmable hardware elements such as field-programmable gate arrays (FPGAs), and any of the various combinations of the above.

[0028] The term "Wi-Fi" encompasses the full scope of its ordinary meaning and includes, at a minimum, wireless communication networks or RATs (Radio-Aided Networks) that are serviced by wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. 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 distinct from cellular networks.

[0029] Automatically – This refers to the execution of user input by a computer system (e.g., software run by the computer system) or device (e.g., circuit mechanisms, programmable hardware elements, ASICs, etc.) without the user directly specifying or performing the action or operation. Therefore, the term “automatically” is in contrast to operations performed or specified manually by the user, where the user provides input and directly executes the operation. An automated procedure may be initiated by user-provided input, but the subsequent actions performed “automatically” are not specified by the user; that is, each action performed is not “manually” specified by the user. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, selecting radio selections, etc.) is considered manually filling out the form, although the computer system must update the form in response to the user action. A form may also be automatically filled out by a computer system, where the computer system (e.g., software run by the computer system) analyzes the fields of the form and fills it out without user input specifying answers to the fields. As described above, users can invoke form autofill but do not participate in the actual form completion (for example, the user does not manually specify answers in the fields; rather, the answers are completed automatically). This specification provides various examples of actions that are performed automatically in response to actions taken by the user.

[0030] "Configured to" - Various components can be described as "configured to" perform a task. In such contexts, "configured to" is a broad description that generally means "having a structure" that performs a task or a set of tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing that task (for example, a set of conductors may be configured to electrically connect two modules to another module even when the two modules are not connected). In some contexts, "configured to" may be a broad description of a structure that generally means "having a circuit" that performs a task or a set of tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently turned on. Generally, the circuit that forms a structure corresponding to "configured to" may include hardware circuits.

[0031] For convenience, various components may be described in this specification as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to perform.” Descriptions of components configured to perform one or more tasks are expressly intended to be exempt from the interpretation of those components under 112, paragraph 6 of the U.S. Patent Act. Figures 1 and 2 - Exemplary Communication System

[0032] Figure 1 shows an exemplary (and simplified) wireless communication system that can implement aspects of the present disclosure according to several embodiments. Note that the system in Figure 1 is merely one example of a possible system, and embodiments can be implemented in various systems as desired.

[0033] As illustrated, an exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number) user devices 106A, 106B, etc. ~ 106N via a transmission medium. In this specification, each user device may be referred to as a “user equipment” (UE) or UE device. Thus, user device 106 is referred to as a UE or UE device.

[0034] 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 UE106A~106N. When base station 102 is implemented in the context of LTE, it may be referred to as "eNodeB" or "eNB" instead. When base station 102 is implemented in the context of 5G NR, it may be referred to as "gNodeB" or "gNB" instead. Base station 102 may also be equipped to communicate with network 100 (e.g., among various possibilities, the core network of a cellular service provider, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet). Thus, base station 102 can facilitate communication between user devices and / or communication between user devices and network 100. The communication area (or coverage area) of a base station may be referred to as a "cell". Furthermore, as used herein, from the perspective of a UE, a base station may be considered representative of the network insofar as it relates to the UE's uplink and downlink communications. Therefore, a UE communicating with one or more base stations in the network may be interpreted as a UE communicating with the network.

[0035] The base station 102 and user devices may be configured to communicate over a transmission medium using various radio access technologies (RATs), also known as wireless communication technologies, or telecommunications standards such as GSM, UMTS (WCDMA®), LTE, LTE-Advanced (LTE-A), LAA / LTE-U, 5G NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and Wi-Fi.

[0036] Therefore, other similar base stations operating according to the same or different cellular communication standards as base station 102 may be provided as one or more networks of cells, capable of providing continuous or nearly continuous overlapping services over a geographical area to UE 106 and similar devices via one or more cellular communication standards.

[0037] It should be noted that UE106 may be capable of communicating using multiple wireless communication standards. For example, UE106 may be configured to communicate using either or both of the 3GPP® cellular communication standard or the 3GPP2 cellular communication standard. In some embodiments, UE106 may be configured to perform robust uplink data transmission techniques, such as by following the various methods described herein. UE106 may also be further or alternatively configured to communicate using WLAN, BLUETOOTH®, one or more global navigation satellite systems (GNSS, e.g., GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including three or more wireless communication standards) are also possible.

[0038] Figure 2 shows an exemplary user device 106 (e.g., one of devices 106A to 106N) communicating with a base station 102 according to several embodiments. UE106 may be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device, computer or tablet, unmanned aerial vehicle (UAV), unmanned aerial vehicle controller (UAC), or substantially any type of wireless device. UE106 may include a processor (processing element) configured to execute program instructions stored in memory. By executing such stored instructions, UE106 can perform any of the embodiments of the method described herein. Alternatively or in addition, UE106 may include programmable hardware elements such as a field programmable gate array (FPGA), an integrated circuit, and / or any of the embodiments of the method described herein, or any part of any of the embodiments of the method described herein (e.g., individually or in combination). UE106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, the UE106 may be configured to communicate using two or more of the following: CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0039] The UE106 may include one or more antennas for communication using one or more radio communication protocols conforming to one or more RAT standards. In some embodiments, the UE106 may share one or more portions of the receive chain and / or transmit chain among multiple radio communication standards. The shared radio may include a single antenna or multiple antennas (e.g., for MIMO) for performing radio communication. Generally, the radio may include any combination of a baseband processor, analog RF signal processing circuits (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuits (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the hardware described above.

[0040] In some embodiments, UE106 may include separate transmit and / or receive chains (e.g., separate antennas and other radio components) for each of the radio communication protocols to which UE106 is configured to communicate. Further possibilities include UE106 including one or more radios shared among multiple radio communication protocols and one or more radios used exclusively by a single radio communication protocol. For example, UE106 may include a shared radio for communication using either LTE or CDMA2000 1xRTT (or LTE or NR or LTE or GSM) and separate radios for communication using Wi-Fi and BLUETOOTH®, respectively. Other configurations are also possible. Figure 3 - Block diagram of an exemplary UE device

[0041] Figure 3 shows a block diagram of an exemplary UE106 according to several embodiments. As shown, the UE106 may include a system-on-chip (SOC) 300, which may include parts for various purposes. For example, as shown in the figure, the SOC 300 may include (one or more) processors 302 that can execute program instructions for the UE106, and a display circuit 304 that can perform graphics processing and supply display signals to a display 360. The SOC 300 may also include a sensor circuit 370 which may include components for sensing or measuring any of the various possible characteristics or parameters of the UE106. For example, the sensor circuit 370 may include a motion sensing circuit configured to detect the movement of the UE106 using, for example, a gyroscope, an accelerometer, and / or various other motion sensing components. Alternatively, the sensor circuit 370 may include, for example, one or more temperature sensing components for measuring the temperature of one or more antenna panels and / or each of the other components of the UE106. Any of the various other possible types of sensor circuits may be included additionally or alternatively in the UE106 as needed. One or more processors 302 may be coupled to a memory management unit (MMU) 340, which receives addresses from the one or more processors 302 and translates those addresses to locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310), and / or the one or more processors 302 may be configured to be coupled to other circuits or devices such as a display circuit 304, a radio 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 one or more processors 302.

[0042] As shown in the figure, the SOC 300 may be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (including, for example, NAND flash 310), a connector interface 320 (for coupling to, for example, computer systems, docks, charging stations, etc.), a display 360, and a wireless communication circuit 330 (for, for example, LTE, LTE-A, NR, CDMA2000, BLUETOOTH®, Wi-Fi, GPS, etc.). The UE device 106 may include at least one antenna (e.g., 335a) and optionally multiple antennas (e.g., illustrated by antennas 335a and 335b) for performing wireless communication with base stations and / or other devices. Antennas 335a and 335b are shown as examples, and the UE device 106 may include fewer or more antennas. In general, one or more of these antennas are collectively referred to as antenna 335. For example, the UE device 106 may use the antenna 335 and the wireless circuit 330 to perform wireless communication. As described above, in some embodiments, the UE may be configured to communicate wirelessly using multiple wireless communication standards.

[0043] UE106 may include hardware and software components for implementing methods of performing improved reliability uplink data transmission techniques, such as those described later in this specification. One or more processors 302 of the UE device 106 may be configured to perform part or all of the methods described herein by executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium). In other embodiments, one or more processors 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, one or more processors 302 may be coupled with and / or interoperable with other components shown in Figure 3 to perform improved reliability uplink data transmission techniques according to the various embodiments disclosed herein. One or more processors 302 may also implement various other applications and / or end-user applications running on UE106.

[0044] In some embodiments, the radio 330 may include separate controllers dedicated to communication control for various respective RAT standards. For example, as shown in Figure 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 separate integrated circuits (abbreviated as ICs or chips) that communicate with each other and with the SOC 300 (more specifically with (one or more) processors 302). For example, the Wi-Fi controller 352 may communicate with the cellular controller 354 via a cell-ISM link or WCI interface, and / or the Bluetooth® controller 356 may communicate with the cellular controller 354 via a cell-ISM link, etc. Although three separate controllers are shown within the radio 330, other embodiments may have fewer or more similar controllers for various different RATs that may be implemented in the UE device 106.

[0045] Furthermore, embodiments are conceivable in which the controller can perform functions related to multiple 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 Wi-Fi-related activities, 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. Figure 4 - Exemplary base station block diagram

[0046] Figure 4 shows a block diagram of an exemplary base station 102 according to several embodiments. Note that the base station in Figure 4 is only one example of a possible base station. As shown in the figure, the base station 102 may include (one or more) processors 404 that can execute program instructions for the base station 102. The (one or more) processors 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the (one or more) processors 404 and translate those addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or other circuits or devices.

[0047] The base station 102 may include at least one network port 470. The network port 470 may be configured to connect to a telephone network and provide access to the telephone network to multiple devices, such as UE devices 106, as described in Figures 1 and 2 above. The network port 470 (or additional network ports) may also, or alternatively, be configured to connect to a cellular network, such as the core network of a cellular service provider. The core network can provide mobility-related services and / or other services to multiple devices, such as UE devices 106. In some cases, the network port 470 may connect to a telephone network via 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).

[0048] The base station 102 may include at least one antenna 434, and possibly more antennas. One or more antennas 434 may be configured to operate as a radio transceiver and may be further configured by a radio 430 to communicate with the UE device 106. One or more antennas 434 communicate with the radio 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio 430 may be designed to communicate via a variety of radio telecommunications 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, for example, executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as a field-programmable gate array (FPGA), as an application-specific integrated circuit (ASIC), or a combination thereof. In the case of a given RAT, for example 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 (one or more) wide area networks and / or local area networks, and may include, for example, at least one Ethernet port, and the radio 430 may be designed to communicate in accordance with the Wi-Fi standard. Figure 5 shows an uplink data transmission technique with improved reliability.

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

[0050] One such area may include uplink data communications and / or other communications that can be performed over 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 multi-beam diversity.

[0051] Therefore, Figure 5 is a flowchart illustrating a method for performing uplink data communication with improved reliability in a wireless communication system, according to at least some embodiments.

[0052] Embodiments of the method shown in Figure 5 may be implemented by a wireless device, or more generally, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the above-mentioned figures, in other devices as desired, in conjunction with one or more cellular base stations such as UE106 and BS102, which are illustrated in various figures herein and described in relation to those figures. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to execute any combination of the method elements shown in the figure and / or other method elements.

[0053] While at least some elements of the method in Figure 5 are described in relation to the use of communication techniques and / or features associated with 3GPP standards and / or NR standards documents, such descriptions are not intended to limit the disclosure, and it should be noted that embodiments of the method in Figure 5 may be used in any suitable wireless communication system as needed. In various embodiments, some of the elements of the method shown in the figure may be performed simultaneously, in an order different from that shown in the figure, replaced by other method elements, or omitted. Additional method elements may be performed as needed. As illustrated, the method in Figure 5 may operate as follows:

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

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

[0056] According to at least some embodiments, a wireless device can establish multiple wireless links with multiple TRPs in a cellular network, for example, according to a multi-TRP configuration. In such a scenario, the wireless device may be configured with one or more transmission control indicators (TCIs) that can correspond to various beams that may be used to communicate with the TRPs (for example, via RRC signaling). Furthermore, one or more configured TCI states may be activated by the media access control (MAC) control element (CE) of the wireless device at a particular time.

[0057] In at least some instances, establishing a wireless link (one or more) may involve a wireless device providing functional information about the wireless device. Such functional information may include information related to any of the various types of wireless device functions.

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

[0059] An uplink data transmission can be any of several types of uplink data transmissions. One possibility is that the uplink data transmission may be a configured grant (CG) push transmission, such as a 3GPP Type 1 CG-PUSCH transmission (which may be composed of, for example, the RRCConfiguredGrantConfig information element) or a 3GPP Type 2 CG-PUSCH transmission (which may be activated or deactivated by DCI format 0_0, 0_1, or 0_2 using cyclic redundancy codes (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI)). Another possibility is that the uplink data transmission may be a dynamic grant (DG) push transmission, such as a 3GPP Type A push iteration or a 3GPP Type B push iteration. A further possibility is that the uplink data transmission may be a 3GPP non-codebook-based (NCB) push transmission.

[0060] According to some embodiments, uplink data transmission configuration information may constitute a transmission pattern for repeating uplink data transmissions to multiple TRPs. One such possible pattern may include sending individual repetitions alternately to multiple TRPs. Another such possible pattern may include sending a sequence of repetitions (e.g., of a specified length) alternately to multiple TRPs. Yet another possible pattern may include alternation in which TRP transmissions are performed in alternating slots.

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

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

[0063] As another example, in the case of 3GPP Type B DG Push iterations, various parameters may be independently configured by the DCI for each TRP. For example, any or all of the following may be indicated by the DCI in such scenarios: P0 parameter (target received power), alpha parameter (path loss compensation coefficient), 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 layer number.

[0064] As previously stated herein, in some instances, uplink data transmission configuration information may constitute a 3GPP non-codebook-based (NCB) push transmission. In such scenarios, the uplink data transmission configuration information may constitute multiple SRS resource sets, each SRS resource set configured using a non-zero-power channel state information reference signal (NZP-CSI-RS). For example, an NZP-CSI-RS may be configured for each TRP on which an NCB push transmission is scheduled, and the NZP-CSI-RS may effectively configure an SRS resource set that logically maps to that TRP.

[0065] In some instances, when two SRS resource sets are configured, each mapping to one TRP, two SRS resource indicator fields may be configured in DCI formats 0_1 and 0_2 for NCB-based PUSCH operation. In such scenarios, each SRS resource indicator field may map to one SRS resource set when the NCB is configured.

[0066] Alternatively, uplink data transmission configuration information may constitute an SRS resource set, and an SRS resource set may be associated with multiple NZP-CSI-RS resources. For example, the first portion of the SRS resources in an SRS resource set may be associated with a first TRP, and the second portion of the SRS resources in an SRS resource set may be associated with a second TRP. In relation to such a scenario, it should be noted that, as one possibility, the number of SRS resources that can be configured per SRS resource set may increase, for example, from 4 to 8 (to support the possibility of including sufficient SRS resources for push transmissions to multiple TRPs). In at least some instances, the mapping of each SRS resource to its associated NZP-CSI-RS resource may be configured by RRC control signaling.

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

[0068] It should be noted that, according to at least some embodiments, nominally scheduled PUSCH iterations may be terminated if duplex contention exists (e.g., if downlink communication is scheduled during a PUSCH iteration for a wireless device configured for half-duplex operation), and / or if PUSCH iterations are scheduled across slot boundaries. In such scenarios, there may be a mechanism for determining, for example, which TRP each actual iteration is transmitted to, according to a configured transmission pattern. For example, one possibility is that the wireless device may be configured to determine, based on the nominal iterations of uplink data transmissions, which TRP each actual uplink data transmission should be performed to, according to a configured transmission pattern. Another possibility is that the wireless device may be configured to determine, based on the actual iterations of uplink data transmissions, which TRP each actual uplink data transmission should be performed to, according to a configured transmission pattern. A further possibility is that the wireless device may be configured to determine, based on the slot in which the uplink data transmission takes place, which TRP each actual uplink data transmission should be performed to, according to a configured transmission pattern.

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

[0070] Therefore, the method shown in Figure 5 can be used to provide a framework for more reliably configuring and performing uplink data transmission in a cellular communication system. Such a framework may be particularly useful, according to at least some embodiments, in supporting enhanced PUSCH reliability by taking advantage of the potential availability of multiple TRPs and multiple radio device antenna panels to provide increased beam diversity for uplink data communication, among other possible benefits. Figures 6-10 and additional information

[0071] Figures 6 to 10 illustrate further embodiments which may be used in conjunction with the method of Figure 5 as needed. However, it should be noted that the exemplary details shown in Figures 6 to 10 and described with respect to Figures 6 to 11 are not intended to limit the disclosure as a whole, and numerous variations and substitutions are possible for the details provided below herein and should be considered within the scope of the disclosure.

[0072] 3GPP Release 16 supports multi-TRP designs for improved physical downlink shared channel (PDSCH) performance. This support may include the use of multiple DCIs across up to five control resource sets (CORESETs) to schedule up to two PDSCHs. It may also be 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 transport block (TB), FDM mode with two TBs, in-slot time division multiplexing (TDM) mode, and inter-slot TDM mode.

[0073] 3GPP Release 16 may also support Type B Physical Uplink Shared Channel (PUSCH) repetitions for improved reliability. For example, in control signaling (e.g., in PUSCH-Allocation-r16 in PUSCH-TimeDomainResourceAllocationListPUSCH-r16), a parameter (e.g., numberOfRepetitions-r16) may be added to allow dynamic changes to the number of PUSCH repetitions via DCI. Nominal repetitions may be executed sequentially if configured. Nominal PUSCH transmissions may be terminated when nominal repetitions would cross slot boundaries or conflict with duplexing duplexing directions.

[0074] For example, further improvements to push reliability may be possible by providing support for push transmissions to multiple TRPs. For instance, techniques for configuring and executing configured grants (CG), dynamic grants (DG), and / or non-codebook-based (NCB) push transmissions to multiple TRPs are described herein, which may help improve push reliability in at least some instances.

[0075] According to some embodiments, there may be two types of CG PUSCH supported in 3GPP communications. In a 3GPP Type I CG-PUSCH, the CG-PUSCH may be configured by an RRCConfiguredGrantConfig information element (IE). In a 3GPP Type II CG-PUSCH, the CG-PUSCH may be activated or deactivated by DCI format 0_0, 0_1, or 0_2 using a cyclic redundancy code (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI).

[0076] For 3GPP Type I CG PUSCH, modifications to how the RRC configuration is performed may be introduced to provide support for multi-TRP PUSCH operation. These modifications may include providing a mechanism for signaling different precoding, beam, 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 grants and may include the rrc-ConfiguredUplinkGrant field. Such a field may include the precodingAndNumberOfLayers parameter, the srs ResourceIndicator parameter, and the pathlossReferenceIndex parameter, which may be used to indicate the precoding, beam, and path loss reference signals for CG-PUSCH operation.

[0077] As one possibility to provide support for indicating 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, thus potentially enabling two different precoding configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of precodingAndNumberOfLayers code points, where each precodingAndNumberOfLayers code point may contain one or two entries of the uplink rank and the transmit precoding matrix indicator (TPMI), and the precodingAndNumberOfLayers parameter may be used to indicate the precodingAndNumberOfLayers code point.

[0078] As one possibility to provide support for indicating different beams for different TRPs in such an IE, an additional field (e.g., "additional-srs-ResourceIndicator") may be introduced to configure a beam for a second TRP, thus potentially enabling 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 SRS resource code point may contain one or two sets of SRS resources, and the srs-ResourceIndicator parameter may be used to indicate an SRS resource code point.

[0079] As one possibility to provide support for indicating different path loss reference signals for different TRPs in such an IE, an additional field (e.g., "additional pathlossReferenceIndex") may be introduced to configure a path loss reference signal for a second TRP, thus potentially enabling 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, where each pathlossReferenceIndex may contain one or two path loss reference signal configurations, and the pathlossReferenceIndex parameter may be used to indicate a pathlossReferenceIndex code point.

[0080] In the case of 3GPP Type I CG-PUSCH, when different beams, precodings, and / or path loss reference signals are configured for each TRP, there can be multiple possible mappings to the actual PUSCH transmission. Figures 6-8 show some such possible transmission patterns according to several embodiments.

[0081] Figure 6 shows an exemplary possible transmission pattern in which the TRPs in which PUSCH transmissions are performed alternately in a cyclical pattern for each repetition opportunity, such that the TRPs in which PUSCH transmissions are performed alternate with each transmission opportunity.

[0082] Figure 7 shows an exemplary possible transmission pattern in which TRPs on which PUSCH transmissions are performed alternately in a continuous 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 has been performed. In the illustrated example, the sequence length may include two PUSCH transmissions.

[0083] Figure 8 shows an exemplary possible transmission pattern in which the TRPs on which PUSCH transmissions are performed alternate in a sequential pattern for each slot, for example, so that the TRPs on which PUSCH transmissions are performed alternate in each slot.

[0084] Furthermore, it should be noted that, according to at least some embodiments, for Type I CG-PUSCH, it may be possible, either as an addition or alternative, to configure the powerControlLoopToUse and / or p0-PUSCH-Alpha parameters related to open-loop power control (OLPC) independently for each TRP.

[0085] According to some embodiments, for example, it may be possible to use techniques similar to those described herein with respect to the 3GPP Type I CG PUSCH operation for the 3GPP Type A DG PUSCH operation to send PUSCH repetitions to multiple TRPs.

[0086] In the case of Type B DG Push iterations, various parameters may be independently configured / indicated by the DCI for each TRP. Such parameters may include any or all of the following: P0 (e.g., target received power), alpha (e.g., path loss compensation coefficient), 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 layer number.

[0087] In the case of such type B DG push iterations, when one or more parameters are configured independently for each of multiple TRPs, there may be multiple possibilities for mapping nominal push iterations to actual push iterations, taking into account possible truncation of nominal push iterations due to duplex direction conflicts or slot boundary intersections caused by nominal push iterations. Figure 9 shows some such possible options that may be used to map nominal push iterations to actual push iterations, according to at least some embodiments.

[0088] As shown in the figure, in the first option 910, the mapping of which TRP an actual PUSCH transmission is sent to may be based on nominal repetitions. Thus, in this method, the first actual PUSCH repetition may be sent to TRP1, the second and third actual PUSCH repetitions may be sent to TRP2, the fourth and fifth actual PUSCH repetitions may be sent to TRP1, and the sixth actual PUSCH repetition may be sent to TRP2.

[0089] In the second illustrated option 920, the mapping of which TRP an actual PUSCH transmission is sent to may be based on the actual iterations. Thus, in this technique, the first actual PUSCH iteration may be sent to TRP1, the second actual PUSCH iteration may be sent to TRP2, the third actual PUSCH iteration may be sent to TRP1, the fourth actual PUSCH iteration may be sent to TRP2, the fifth actual PUSCH iteration may be sent to TRP1, and the sixth actual PUSCH iteration may be sent to TRP2.

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

[0091] In the case of NCB push operation, according to at least some embodiments, it may be possible to support multi-TRP push operation by configuring two or more SRS-ResourceSets. Figure 10 shows some examples of such possible techniques according to some embodiments. As shown, in the illustrated examples, each SRS-ResourceSet is logically mapped to one TRP. Each SRS-ResourceSet may consist of different non-zero power channel state information reference signal resource identifiers (NZP-CSI-RS-ResourceId), each of which may be transmitted from a different TRP.

[0092] In some instances, under NCB PUSCH operation, when two SRS-ResourceSets are configured, each mapped to one TRP, it may be possible to configure two SRS resource indicator fields in 3GPP DCI formats 0_1 and 0_2. In such scenarios, each SRS resource indicator field may be mapped to one SRS-ResourceSet with the use of "nonCodebook".

[0093] As a further possibility, in the case of NCB PUSCH operation, a single SRS-ResourceSet may be configured to include two or more associated NZP-CSI-RS-ResourceIds. In such a 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 within the SRS-ResourceSet to its associated NZP-CSI-RS-ResourceId may be configured by RRC control signaling. Thus, it may also be possible to support multi-TRP NCB PUSCH operation using such a configuration.

[0094] Further exemplary embodiments are provided below.

[0095] A set of embodiments may include a baseband processor configured to perform operations including establishing a radio link with a cellular base station, receiving uplink data transmission configuration information which constitutes uplink data transmission to a plurality of transmission / reception points (TRPs), and performing uplink data transmission to the plurality of TRPs.

[0096] According to some embodiments, uplink data transmission configuration information constitutes 3GPP configured grant physical uplink shared channel (PUSCH) transmission.

[0097] According to some embodiments, uplink data transmission configuration information constitutes 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission.

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

[0099] According to some embodiments, the uplink data transmission configuration information constitutes a transmission pattern for repeating uplink data transmission to multiple TRPs.

[0100] According to some embodiments, the uplink data transmission configuration information includes, for each TRP associated with uplink transmission, information indicating one or more of the following: beam information, precoding information, path loss reference signal information, target received power information, or path loss compensation coefficient.

[0101] Another set of embodiments may include a radio device comprising an antenna, a radio operably coupled to the antenna, and a processor operably coupled to the radio, wherein the radio device is configured to establish a radio link with a cellular base station, receive uplink data transmission configuration information, wherein the uplink data transmission configuration information constitutes uplink data transmission to a plurality of transmission / reception points (TRPs), and perform uplink data transmission to the plurality of TRPs.

[0102] According to some embodiments, the uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, and the beam information for each TRP is indicated using either a separate beam configuration field for each TRP, or a single beam configuration field that includes beam configuration index values ​​associated with a plurality of beam configurations.

[0103] According to some embodiments, the uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, and the precoding information for each TRP is indicated using one of a separate precoding configuration field for each TRP, or a single precoding configuration field that includes precoding configuration index values ​​associated with multiple precoding configurations.

[0104] According to some embodiments, the uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, and the path loss reference signal information for each TRP is indicated using either a separate path loss reference signal configuration field for each TRP, or a single path loss reference signal configuration field that includes path loss reference signal configuration index values ​​associated with a plurality of path loss reference signal configurations.

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

[0106] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern for performing repeated uplink data transmissions to multiple TRPs, and according to the transmission pattern, individual repetitions are transmitted alternately to the multiple TRPs.

[0107] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern for performing repeated uplink data transmissions to multiple TRPs, and according to the transmission pattern, a sequence of repetitions is transmitted alternately to the multiple TRPs.

[0108] According to some embodiments, the uplink data transmission configuration information sets a transmission pattern for repeating uplink data transmission to multiple TRPs, and transmissions are made to alternating TRPs in alternating slots according to the transmission pattern.

[0109] A further set of embodiments may include a method comprising establishing a wireless link with a cellular base station, receiving uplink data transmission configuration information, wherein the uplink data transmission configuration information constitutes uplink data transmission to a plurality of transmission / reception points (TRPs), and performing uplink data transmission to the plurality of TRPs.

[0110] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines which of a plurality of TRPs each iteration of uplink data transmission should be directed to, and when a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method further includes determining, based on the nominal iterations of uplink data transmission, which of a plurality of TRPs each actual uplink data transmission should be directed to according to the transmission pattern.

[0111] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines which of a plurality of TRPs each iteration of uplink data transmission should be directed to, and when a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method further includes determining, based on the actual iterations of uplink data transmission, which of the plurality of TRPs each actual uplink data transmission should be directed to according to the transmission pattern.

[0112] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines which of a plurality of TRPs each iteration of uplink data transmission should be directed to, and when a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method further includes determining, based on the slot in which the uplink data transmission is performed, which of the plurality of TRPs each actual uplink data transmission should be directed to according to the transmission pattern.

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

[0114] According to some embodiments, uplink data transmission configuration information constitutes a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission, 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, the first portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a first TRP, and the second portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a second TRP.

[0115] A further set of embodiments may include a device that includes a processor configured to cause a cellular base station to establish a wireless link with a wireless device, to provide the wireless device with uplink data transmission configuration information, the uplink data transmission configuration information constitutes uplink data transmission to a plurality of transmission / reception points (TRPs), and to receive at least a portion of the uplink data transmission to the plurality of TRPs.

[0116] According to some embodiments, uplink data transmission configuration information constitutes 3GPP configured grant physical uplink shared channel (PUSCH) transmission.

[0117] According to some embodiments, uplink data transmission configuration information constitutes 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission.

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

[0119] According to some embodiments, the uplink data transmission configuration information constitutes a transmission pattern for repeating uplink data transmission to multiple TRPs.

[0120] According to some embodiments, the uplink data transmission configuration information independently comprises one or more of the following for each TRP associated with uplink transmission: beam information, precoding information, path loss reference signal information, target received power information, or path loss compensation coefficient.

[0121] A further set of embodiments may include a cellular base station comprising an antenna, a radio operably coupled to the antenna, and a processor operably coupled to the radio, wherein the cellular base station establishes a radio link with a radio device and provides the radio device with uplink data transmission configuration information, the uplink data transmission configuration information comprising uplink data transmission to a plurality of transmission / reception points (TRPs), and is configured to receive at least a portion of the uplink data transmission to the plurality of TRPs.

[0122] According to some embodiments, the uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, and the beam information for each TRP is indicated using either a separate beam configuration field for each TRP, or a single beam configuration field that includes beam configuration index values ​​associated with a plurality of beam configurations.

[0123] According to some embodiments, the uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, and the precoding information for each TRP is indicated using one of a separate precoding configuration field for each TRP, or a single precoding configuration field that includes precoding configuration index values ​​associated with multiple precoding configurations.

[0124] According to some embodiments, the uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, and the path loss reference signal information for each TRP is indicated using either a separate path loss reference signal configuration field for each TRP, or a single path loss reference signal configuration field that includes path loss reference signal configuration index values ​​associated with a plurality of path loss reference signal configurations.

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

[0126] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern for performing repeated uplink data transmissions to multiple TRPs, and according to the transmission pattern, individual repetitions are transmitted alternately to the multiple TRPs.

[0127] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern for performing repeated uplink data transmissions to multiple TRPs, and according to the transmission pattern, a sequence of repetitions is transmitted alternately to the multiple TRPs.

[0128] According to some embodiments, the uplink data transmission configuration information sets a transmission pattern for repeating uplink data transmission to multiple TRPs, and transmissions are made to alternating TRPs in alternating slots according to the transmission pattern.

[0129] A further set of embodiments may include a method comprising: establishing a radio link with a radio device by a cellular base station; providing the radio device with uplink data transmission configuration information, the uplink data transmission configuration information constitutes uplink data transmission to a plurality of transmission / reception points (TRPs); and receiving at least a portion of the uplink data transmission to the plurality of TRPs.

[0130] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines to which of a plurality of TRPs each iteration of uplink data transmission is directed, and according to the transmission pattern, when a nominal uplink data transmission is terminated due to duplexing conflict or scheduling across slot boundaries, to which of the plurality of TRPs each actual uplink data transmission is directed is determined based on the nominal iteration of the uplink data transmission.

[0131] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines to which of a plurality of TRPs each iteration of uplink data transmission is directed, and when a nominal uplink data transmission is terminated due to duplexing conflict or scheduling across slot boundaries, to which of the plurality of TRPs each actual uplink data transmission is directed is determined based on the actual iteration of the uplink data transmission.

[0132] According to some embodiments, uplink data transmission configuration information constitutes a transmission pattern that determines to which of a plurality of TRPs each iteration of uplink data transmission is directed, and when a nominal uplink data transmission is terminated due to duplexing conflict or scheduling across slot boundaries, to which of the plurality of TRPs each actual uplink data transmission is directed is determined based on the slot in which the uplink data transmission is performed.

[0133] 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, which constitutes a non-zero power channel state information reference signal associated with an additional sounding reference signal resource set, and additional non-zero power channel state information reference signals associated with an additional sounding reference signal resource set.

[0134] 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, 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, the first portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a first TRP, and the second portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a second TRP.

[0135] Further exemplary embodiments may include methods, which involve performing any or all of the above-described embodiments by a device.

[0136] Another exemplary embodiment may include a device comprising an antenna, a radio coupled to the antenna, and a processing element operably coupled to the radio, the device being configured to implement any or all parts of the above-described embodiments.

[0137] A further exemplary set of embodiments may include a non-temporary computer-accessible memory medium containing program instructions that, when executed on the device, cause the device to implement any or all of the above embodiments.

[0138] A further exemplary set of embodiments may include computer programs that include instructions for performing any or all parts of any of the embodiments described above.

[0139] Another exemplary set of embodiments may include an apparatus that includes means for performing any or all of the elements of any of the embodiments described above.

[0140] A further set of exemplary embodiments may include a device comprising a processing element configured to perform any or all of the elements of the aforementioned embodiments.

[0141] Another exemplary set of embodiments may include a baseband processor configured to perform operations that include any or all of the elements of any of the embodiments described above.

[0142] It is well understood that the use of personal information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personal data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

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

[0144] Embodiments of this disclosure may be implemented in any variety of forms. For example, in some embodiments, the subject matter may be implemented as a method executed on a computer, a computer-readable storage medium, or a computer system. In other embodiments, the subject matter may be implemented using one or more custom-designed hardware devices, such as ASICs. In other embodiments, the subject matter may be implemented using one or more programmable hardware elements, such as FPGAs.

[0145] In some embodiments, a non-temporary computer-readable memory medium (e.g., a non-temporary memory element) stores program instructions and / or data, and the program instructions may be configured to cause a computer system, when executed by that computer system, to execute, for example, any embodiment of the method described herein, a combination of embodiments of the method described herein, a subset of embodiments of the method described herein, or a combination of such subsets.

[0146] In some embodiments, the device (e.g., UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory elements), the memory medium storing program instructions, and the processor being configured to read and execute program instructions from the memory medium, the program instructions being 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 implemented in any of the various forms.

[0147] Although the embodiments described above are described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art if the above disclosure is fully understood. The following claims are intended to be construed as encompassing all such variations and modifications.

Claims

1. A baseband processor configured to perform an operation, wherein the operation is Establishing a wireless link with a cellular base station, Uplink data transmission configuration information, wherein the uplink data transmission configuration information constitutes uplink data transmission to multiple transmission / reception points (TRPs), and the reception of uplink data transmission configuration information. The process involves performing the transmission of the uplink data to the aforementioned multiple TRPs, A baseband processor, including a baseband processor.

2. The aforementioned uplink data transmission configuration information constitutes a 3GPP configuration grant physical uplink shared channel (PUSCH) transmission. The baseband processor according to claim 1.

3. The aforementioned uplink data transmission configuration information constitutes a 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission. The baseband processor according to claim 1.

4. The aforementioned uplink data transmission configuration information constitutes a 3GPP non-codebook-based physical uplink shared channel (PUSCH) transmission. The baseband processor according to claim 1.

5. The uplink data transmission configuration information constitutes a transmission pattern for repeating the uplink data transmission for the plurality of TRPs. The baseband processor according to claim 1.

6. The aforementioned uplink data transmission configuration information applies to each TRP related to the uplink transmission, Beam information, Precoding information, Path loss reference signal information, Target received power information, or Information including one or more of the path loss compensation coefficients, The baseband processor according to claim 1.

7. A wireless device, Antenna and, A radio unit operably coupled to the aforementioned antenna, The wireless device comprises a processor operably coupled to the aforementioned wireless device, The aforementioned wireless device, Establish a wireless link with a cellular base station, Uplink data transmission configuration information, wherein the uplink data transmission configuration information constitutes uplink data transmission to multiple transmission / reception points (TRPs), and the uplink data transmission configuration information is received. A wireless device configured to perform the uplink data transmission to the plurality of TRPs.

8. The uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, and the beam information for each TRP is A separate beam configuration field for each TRP, or It is shown using one of a single beam configuration field that contains beam configuration index values ​​associated with multiple beam configurations, The wireless device according to claim 7.

9. The uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, and the precoding information for each TRP is A separate pre-coding configuration field for each TRP, or This is indicated using one of a single precoding configuration field that contains precoding configuration index values ​​associated with multiple precoding configurations. The wireless device according to claim 7.

10. The uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, and the path loss reference signal information for each TRP is A separate path loss reference signal configuration field for each TRP, or This is represented using one of a single path loss reference signal configuration fields that contains path loss reference signal configuration index values ​​associated with multiple path loss reference signal configurations. The wireless device according to claim 7.

11. For each TRP associated with the uplink transmission, the uplink data transmission configuration information is as follows: Target received power information, or One or more of the path loss compensation coefficients are independently constructed. The wireless device according to claim 7.

12. The uplink data transmission configuration information constitutes a transmission pattern for repeating the uplink data transmission to the plurality of TRPs, and according to the transmission pattern, individual repetitions are transmitted alternately to the plurality of TRPs. The wireless device according to claim 7.

13. The uplink data transmission configuration information constitutes a transmission pattern for repeating the uplink data transmission to the plurality of TRPs, and according to the transmission pattern, a sequence of repetitions is transmitted alternately to the plurality of TRPs. The wireless device according to claim 7.

14. The uplink data transmission configuration information constitutes a transmission pattern for repeating the uplink data transmission to the plurality of TRPs, and transmission is performed to alternating TRPs in alternating slots according to the transmission pattern. The wireless device according to claim 7.

15. Establishing a wireless link with a cellular base station, Uplink data transmission configuration information, wherein the uplink data transmission configuration information constitutes uplink data transmission to multiple transmission / reception points (TRPs), and the reception of uplink data transmission configuration information. The process involves performing the transmission of the uplink data to the aforementioned multiple TRPs, Methods that include...

16. The uplink data transmission configuration information constitutes a transmission pattern that determines which of the plurality of TRPs to send each iteration of the uplink data transmission to. When a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method shall The further includes determining, based on the nominal iteration of the uplink data transmission, which of the plurality of TRPs each actual uplink data transmission should be performed to according to the transmission pattern, The method according to claim 15.

17. The uplink data transmission configuration information constitutes a transmission pattern that determines which of the plurality of TRPs to send each iteration of the uplink data transmission to. When a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method shall The further includes determining, based on the actual iterations of the uplink data transmissions, which of the plurality of TRPs each actual uplink data transmission should be performed to according to the transmission pattern, The method according to claim 15.

18. The uplink data transmission configuration information constitutes a transmission pattern that determines which of the plurality of TRPs to send each iteration of the uplink data transmission to. When a nominal uplink data transmission is terminated due to duplexing conflict or because it is scheduled across slot boundaries, the method shall The further includes determining, based on the slot in which the uplink data transmission is performed, to which of the plurality of TRPs each actual uplink data transmission is performed according to the transmission pattern, The method according to claim 15.

19. The aforementioned uplink data transmission configuration information constitutes a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission. The uplink data transmission configuration information comprises a plurality of sounding reference signal resource sets, each sounding reference signal resource set is configured using a non-zero power channel state information reference signal (NZP-CSI-RS). The method according to claim 15.

20. The aforementioned uplink data transmission configuration information constitutes a non-codebook-based (NCB) physical uplink shared channel (PUSCH) transmission. 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 (NZP-CSI-RS), the first portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a first TRP, and the second portion of the sounding reference signal resources of the sounding reference signal resource set is associated with a second TRP. The method according to claim 15.

Images