Performing physical uplink shared channel transmissions with improved reliability
By configuring uplink data transmissions to multiple transceiver points with independent parameters, the reliability and efficiency of wireless communication systems are improved, addressing the challenges of increasing device functionality and power consumption.
Patent Information
- Application Number
- JP2024141179
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-22
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing wireless communication systems face challenges in ensuring reliable uplink data transmission due to increasing device functionality and power consumption demands, particularly in cellular communication systems where robustness and reliability are crucial for various use cases.
Implementing uplink data transmission techniques that utilize multiple transceiver points (TRPs) with independent configuration parameters, such as beam diversity and patterned transmission, to enhance reliability and efficiency.
Enhances the reliability and robustness of uplink data communications by leveraging beam diversity and multi-TRP configurations, improving the overall performance of wireless devices.
Smart Images

Figure 2024167273000001_ABST
Abstract
Description
[Technical field]
[0001] FIELD This application relates to wireless communications, and more particularly to systems, apparatus and methods for performing physical uplink shared channel transmissions with improved reliability in wireless communications systems. [Background technology]
[0002] The use of wireless communication systems is growing 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 not only support telephony, but also provide access to the Internet, e-mail, text messaging, and navigation using the Global Positioning System (GPS), and are capable of running sophisticated applications that utilize these features. In addition, there are many different wireless communication technologies and standards. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE Advanced (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH, etc.
[0003] The ever-increasing number of features and functions introduced into wireless communication devices creates a continuing need to improve both wireless communication and wireless communication devices. In particular, it is important to ensure the accuracy of transmitted and received signals through user equipment (UE) devices, e.g., wireless devices such as cellular telephones, base stations, and relay stations used in wireless cellular communication. In addition, increasing the functionality of UE devices can place a heavy burden on the battery life of UE devices. Therefore, it is also very important to reduce the power requirements of UE devices while allowing the UE devices to maintain good transmission and reception capabilities to improve communication. Therefore, improvements in this area are desirable. Summary of the Invention
[0004] Presented herein are embodiments of apparatus, systems, and methods for performing physical uplink shared channel transmissions with improved reliability in wireless communication systems.
[0005] In accordance with the techniques described herein, a wireless device can receive uplink data transmission configuration information that configures uplink data transmission to multiple transmission / reception points and can perform uplink data transmission to the multiple transmission / reception points. The uplink data transmission can be any of a variety of types of uplink data transmission, and some or all of the parameters used when transmitting to each of the configured transmission / reception points can be independently configured 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 beam diversity possibilities that may be possible when uplink data may be provided to multiple transmitting and receiving points.
[0007] It should be noted that the techniques described herein may be implemented in and / or used in conjunction with many different types of devices, including, but not limited to, base stations, access points, cellular telephones, portable media players, tablet computers, wearable devices, unmanned aerial vehicles, unmanned aerial controllers, automobiles and / or motor vehicles, and a variety of other computing devices.
[0008] This Summary is intended to provide a brief overview of some of the subject matter described in this document. It should therefore be understood that the above features 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 description of the drawings]
[0009] A better understanding of the present subject matter may be obtained from the following detailed description of various embodiments when considered in conjunction with the following drawings.
[0010] [Figure 1] 1 illustrates an exemplary (and simplified) wireless communication system according to some embodiments.
[0011] [Diagram 2] 1 illustrates an exemplary base station in communication with an exemplary wireless user equipment (UE) device, according to some embodiments.
[0012] [Diagram 3] 1 illustrates an example block diagram of a UE according to some embodiments.
[0013] [Figure 4] 1 illustrates an example block diagram of a base station according to some embodiments.
[0014] [Diagram 5]1 is a flow chart diagram illustrating aspects of an example possible method for providing physical uplink shared channel transmission with improved reliability in a wireless communication system according to some embodiments.
[0015] [Figure 6] 1 illustrates example aspects of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmissions according to some embodiments. [Figure 7] 1 illustrates example aspects of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmissions according to some embodiments. [Figure 8] 1 illustrates example aspects of various possible transmission patterns that may be used for configuration grant physical uplink shared channel transmissions according to some embodiments.
[0016] [Figure 9] 1 illustrates various possible example approaches for mapping TRPs to repetitions for dynamic grant physical uplink shared channel transmissions according to some embodiments.
[0017] [Figure 10] 1 illustrates an example aspect of a possible non-codebook based physical uplink shared channel operation according to some embodiments.
[0018] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives within the spirit and scope of the present subject matter as defined by the appended claims. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0019] acronym Various acronyms are used throughout this disclosure. Definitions of the most prominently used acronyms that may appear throughout this disclosure are provided below: ●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: Send / Transmit ● RX: Receive / Receive RAT: Radio Access Technology ●TRP: Transmitting / receiving point ●DCI: Downlink control information ● CORESET: Control resource set ●CSI: Channel State Information ●CSI-RS: Channel State Information Reference Signal term Below is a description of terms that may appear in this disclosure.
[0020] Memory medium - any of various types of non-transitory memory or storage devices. The term "memory medium" is intended to include, for example, installation media such as CD-ROM, floppy disk, 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, and the like. Storage media may include other types of non-transitory memory, or combinations thereof. In addition, the memory medium may be located in a first computer system where the program is executed, or in a second, different computer system that connects to the first computer system via a network such as the Internet. In the latter case, the second computer system can provide the first computer system with program instructions to execute. The term "memory medium" may include two or more memory media that can exist in different locations, for example, in different computer systems connected via a network. The memory medium may store program instructions (e.g., embodied as a computer program) 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 a bus, network, and / or other physical transmission medium that carries signals, such as electrical, electromagnetic, or digital signals.
[0022] Computer System (or Computer) - Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network device, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or any other device or combination of devices. In general, 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.
[0023] User Equipment (UE) (or "UE device") - any of 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., smart watches, smart glasses), laptops, PDAs, portable Internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), unmanned aerial controllers (UACs), and the like. In general, the term "UE" or "UE device" may be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communications.
[0024] Wireless Device - any of various types of computer systems or devices that perform wireless communications. A wireless device can be portable (or mobile) or may be stationary or fixed to a location. A UE is an example of a wireless device.
[0025] Communications Device - Any of various types of computer systems or devices that perform communications, which may be wired or wireless. A communications device may be portable (or mobile) or may be stationary or fixed to a particular location. A wireless device is one example of a communications device. A UE is another example of a communications device.
[0026] Base Station (BS) - The term "base station" has all of its ordinary meanings and includes at least a wireless communication station that is installed at a fixed location and used for communication as part of a wireless telephone or wireless system.
[0027] Processing Element (or Processor) - refers to various elements or combinations of elements capable of performing functions within a device, e.g., within a user equipment device or within a cellular network device. A processing element may include, for example, a processor and associated memory, a portion or circuitry of an individual processor core, an entire processor core, a processor array, a circuit such as an Application Specific Integrated Circuit (ASIC), a programmable hardware element such as a Field Programmable Gate Array (FPGA), and any of the various combinations of the above.
[0028] Wi-Fi - The term "Wi-Fi" has the full scope of its ordinary meaning and includes at least a wireless communication network or RAT that is served by wireless LAN (WLAN) access points and provides 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 - refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or device (e.g., circuit mechanisms, programmable hardware elements, ASICs, etc.) without user input directly specifying or executing the action or operation. Thus, the term "automatically" is in contrast to an operation that is manually performed or specified by a user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by a user, but the subsequent actions that are performed "automatically" are not specified by the user; that is, they are not performed "manually" with the user specifying each action to be performed. 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 to be manually filling out the form, even though the computer system must update the form in response to the user actions. A form may be filled out automatically by a computer system, where the computer system (e.g., software executed by the computer system) analyzes the fields of the form and fills out the form without user input specifying answers to the fields. As noted above, a user can invoke automatic filling of a form, but is not involved in the actual filling of the form (e.g., the user does not manually specify answers in fields, but rather the answers are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.
[0030] Configured to - Various components may be described as "configured to" perform a task. In such contexts, "configured to" is a broad description that generally means "having a structure" to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a set of conductors may be configured to electrically connect a module 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 circuitry" to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.
[0031] In the description herein, for convenience, various components may be described as performing a task or tasks. Such descriptions should be construed to include the phrase "configured to." It is expressly intended that the description of a component as being configured to perform one or more tasks does not apply to the interpretation of that component under 35 U.S.C. § 112, sixth paragraph. FIG. 1 and FIG. 2—An exemplary communication system
[0032] 1 illustrates an exemplary (and simplified) wireless communication system in which aspects of the present disclosure may be implemented, according to some embodiments. It should be noted that the system of FIG. 1 is merely one example of a possible system, and that embodiments may be implemented in a variety of systems, as desired.
[0033] As shown, the exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number of) user devices 106A, 106B, etc. through 106N over a transmission medium. Each of the user devices may be referred to herein as a "user equipment" (UE) or a UE device. Accordingly, the user devices 106 are referred to as UEs or UE devices.
[0034] The base station 102 may be a base transceiver station (BTS) or cell site and may include hardware and / or software to enable wireless communication with the UEs 106A-106N. If the base station 102 is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". If the base station 102 is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB". The base station 102 may also be equipped to communicate with the network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, the base station 102 may facilitate communication between and / or between user devices and the network 100. The communication area (or coverage area) of a base station may be referred to as a "cell". Also, as used herein, from the perspective of a UE, a base station may be considered to represent a network as far as the UE's uplink and downlink communications are concerned. Thus, a UE that communicates with one or more base stations in a network may be interpreted as a UE that communicates with the network.
[0035] The base stations 102 and user devices may be configured to communicate over a transmission medium using any of a variety of Radio Access Technologies (RATs), also referred to 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), Wi-Fi, etc.
[0036] Thus, 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 that may provide continuous or near-continuous overlapping service to UE 106 and similar devices over a geographic area via one or more cellular communication standards.
[0037] It should be noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using either or both of the 3GPP® or 3GPP2 cellular communication standards. In some embodiments, the UE 106 may be configured to perform robust uplink data transmission techniques, such as in accordance with various methods described herein. The UE 106 may also or alternatively be 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 broadcast standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including three or more wireless communication standards) are also possible.
[0038] FIG. 2 illustrates an exemplary user equipment 106 (e.g., one of devices 106A-106N) communicating with a base station 102, according to some embodiments. The UE 106 may be a device with 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 aircraft controller (UAC), or virtually any type of wireless device. The UE 106 may include a processor (processing element) configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a Field Programmable Gate Array (FPGA), an integrated circuit, and / or any of a variety of other possible hardware components configured to perform (e.g., individually or in combination) any of the method embodiments described herein, or any portion of any of the method embodiments described herein. 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 possible.
[0039] 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 portions of a receive chain and / or transmit chain between multiple wireless communication standards. A shared radio may include a single antenna or multiple antennas (e.g., for MIMO) for performing wireless communication. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, a radio may implement one or more receive and transmit chains using the hardware described above.
[0040] In some embodiments, the UE 106 may include a separate transmit and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol over which the UE 106 is configured to communicate. As a further possibility, the UE 106 may include one or more radios shared among multiple wireless communication protocols and one or more radios used exclusively by a single wireless communication protocol. For example, the UE 106 may include a shared radio for communicating using either LTE or CDMA2000 1xRTT (or LTE or NR or LTE or GSM) and a separate radio for communicating using each of Wi-Fi and BLUETOOTH. Other configurations are possible. Figure 3 - Block diagram of an exemplary UE device
[0041] 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, which may include portions for a variety of purposes. For example, as illustrated, the SOC 300 may include a processor(s) 302, which may execute program instructions for the UE 106, and a display circuit 304, which may perform graphics processing and provide 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 a variety of possible characteristics or parameters of the UE 106. For example, the sensor circuit 370 may include a motion sensing circuit configured to detect movement of the UE 106, for example, using a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. As another possibility, the sensor circuit 370 may include one or more temperature sensing components, for example, for measuring the temperature of one or more antenna panels and / or each of the other components of the UE 106. Any of a variety of other possible types of sensor circuitry may additionally or alternatively be included in the UE 106, as desired. The processor(s) 302 may be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from the processor(s) 302 and translate those addresses into locations in memory (e.g., memory 306, read only memory (ROM) 350, NAND flash memory 310) and / or to couple the processor(s) 302 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 the processor(s) 302.
[0042] As shown, 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 example, for coupling to a computer system, a dock, a charging station, etc.), a display 360, and wireless communication circuitry 330 (for example, for LTE, LTE-A, NR, CDMA2000, BLUETOOTH, Wi-Fi, GPS, etc.). The UE device 106 may include at least one antenna (e.g., 335a) and possibly multiple antennas (e.g., as illustrated by antennas 335a and 335b) for performing wireless communication with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and the UE device 106 may include fewer or more antennas. In general, the one or more antennas are collectively referred to as antennas 335. For example, the UE device 106 may use the antenna 335 and perform wireless communications using the radio circuitry 330. As mentioned above, in some embodiments, the UE may be configured to communicate wirelessly using multiple wireless communication standards.
[0043] The UE 106 may include hardware and software components for implementing methods for the UE 106 to perform uplink data transmission techniques with improved reliability, such as described further below in this specification. The processor(s) 302 of the UE device 106 may be configured to perform some or all of the methods described herein, for example, by executing program instructions stored in a memory medium (e.g., a non-transitory 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 combined with and / or interoperate with other components shown in FIG. 3 to perform uplink data transmission techniques with improved reliability according to various embodiments disclosed herein. The processor(s) 302 may also implement various other applications and / or end user applications running on the UE 106.
[0044] In some embodiments, the radio 330 may include separate controllers dedicated to controlling communications for each of the various RAT standards. For example, as shown 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, where in at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (ICs or chips for short) 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 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 in the radio 330, other embodiments have fewer or more similar controllers for the various different RATs that may be implemented in the UE device 106.
[0045] Further, embodiments are contemplated in which the controller is capable of performing functions related to multiple radio 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 related to Wi-Fi, such as Wi-Fi preamble detection and / or Wi-Fi physical layer preamble signal generation and transmission, in addition to hardware and / or software components for performing cellular communications. FIG. 4 - Block diagram of an exemplary base station
[0046] FIG. 4 illustrates a block diagram of an exemplary base station 102, according to some embodiments. It should be noted that the base station of FIG. 4 is merely one example of a possible base station. As shown, the base station 102 may include a 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, which may be configured to receive addresses from the processor(s) 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 couple to a telephone network and provide a plurality of devices, such as the UE device 106, with access to the telephone network as described above in FIGS. 1 and 2. The network port 470 (or additional network ports) may also or alternatively be configured to couple to a cellular network, such as, 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 the UE device 106. In some cases, the network port 470 may couple to the telephone network via the core network and / or the core network may provide the telephone network (e.g., among other UE devices serviced by the cellular service provider).
[0048] 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 the UE device 106 via a radio 430. The antenna(s) 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 various wireless telecommunication 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 the implementation of some or all of the methods described herein, for example, by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC), or as a combination thereof. For a given RAT, 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 (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 according to the Wi-Fi standard. FIG. 5 illustrates an uplink data transmission technique with improved reliability.
[0049] Wireless communications are being used for an increasingly broad set of use cases. For at least some such types of communications, robustness and reliability of the communications may be particularly important. It may therefore be useful to extend the range of types of communications 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 may be performed on a Physical Uplink Shared Channel (PUSCH) of a cellular communications 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] Accordingly, FIG. 5 is a flow chart diagram illustrating a method for performing uplink data communications with improved reliability in a wireless communication system, according to at least some embodiments.
[0052] 5 may be implemented by a wireless device in conjunction with one or more cellular base stations, such as UE 106 and BS 102, illustrated in and described with respect to the various figures herein, or, more generally, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the above figures, among other devices, as desired. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the method elements shown in the figures and / or other method elements.
[0053] It should be noted that, although at least some elements of the method of FIG. 5 are described as relating to the use of communication techniques and / or features associated with 3GPP and / or NR standard documents, such description is not intended to limit the disclosure, and aspects of the method of FIG. 5 may be used in any suitable wireless communication system, as appropriate. In various embodiments, some of the method elements shown in the figures may be performed simultaneously, may be performed in a different order than shown in the figures, may be replaced by other method elements, or may be omitted, as appropriate. Additional method elements may be performed, as illustrated. As illustrated, the method of FIG. 5 may operate as follows.
[0054] At 502, the 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 via 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 via an eNB that provides wireless access to the cellular network. Other types of cellular links are possible, and the cellular network may additionally or alternatively operate according to another cellular communication technology (e.g., UMTS, CDMA2000, GSM, etc.) according to various embodiments.
[0055] Establishing the radio link may include establishing an RRC connection with a serving cellular base station according to at least some embodiments. Establishing a first RRC connection may include configuring various parameters for communication between the wireless device and the cellular base station, establishing context information of the wireless device, and / or any of various other possible features related to, for example, establishing 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 connected state. In some instances, the RRC connection may also be released (e.g., after a certain inactive period with respect to data communication), in which case the wireless device may operate in an RRC idle state or an RRC inactive state. In some instances, the wireless device may perform a handover (e.g., while in an RRC connected mode) or perform a cell reselection to a new serving cell (e.g., in an RRC idle or RRC inactive mode) due to wireless device mobility changing wireless medium conditions and / or any of various other possible reasons.
[0056] According to at least some embodiments, a wireless device may establish multiple radio links with, for example, multiple TRPs of a cellular network according to a multi-TRP configuration. In such a scenario, the wireless device may be configured (e.g., via RRC signaling) with one or more transmission control indicators (TCIs), which may correspond to, for example, different beams that may be used to communicate with the TRPs. Furthermore, one or more configured TCI states may be activated by a media access control (MAC) control element (CE) of the wireless device at a particular time.
[0057] In at least some instances, establishing the wireless link(s) may include the wireless device providing wireless device capability information. Such capability information may include information related to any of various types of wireless device capabilities.
[0058] At 504, the cellular base station may provide uplink data transmission configuration information to the wireless device. 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, among other possibilities. The uplink data transmission configuration information may configure uplink data transmission to multiple TRPs.
[0059] The uplink data transmission may be any of various types of uplink data transmission. As one possibility, the uplink data transmission may be a configured grant (CG) PUSCH transmission, such as a 3GPP type 1 CG-PUSCH transmission (which may be configured, for example, by an 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, for example, with a cyclic redundancy code (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI). As another possibility, the uplink data transmission may be a dynamic grant (DG) PUSCH transmission, such as a 3GPP type A PUSCH repetition or a 3GPP type B PUSCH repetition. As a further possibility, the uplink data transmission may be a 3GPP non-codebook based (NCB) PUSCH transmission.
[0060] According to some embodiments, the uplink data transmission configuration information may configure a transmission pattern for repetitions of uplink data transmissions to multiple TRPs. One such possible pattern may include alternating transmission of individual repetitions to multiple TRPs. Another such possible pattern may include alternating transmission of a sequence of repetitions (e.g., of a specified length) 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 indicative of one or more parameters for each TRP associated with the 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 factor for each TRP associated with the uplink transmission.
[0062] Such configuration information may be provided in any of a variety of possible ways. For example, in the case of a 3GPP type 1 CG-PUSCH transmission, some or all of such parameters may be configured using various fields of the RRC information element that configures the CG-PUSCH transmission. Thus, to potentially indicate beam information for each TRP associated with an uplink transmission, it may be possible to provide a separate beam configuration field for each TRP, or to provide a single beam configuration field that includes beam configuration index values associated with multiple beam configurations, among other possibilities. Similarly, to potentially indicate precoding information for each TRP associated with an uplink transmission, it may be possible to provide a separate precoding configuration field for each TRP, or to provide a single precoding configuration field that includes precoding configuration index values associated with multiple precoding configurations, among other possibilities. Similarly, to potentially indicate pathloss reference signal information for each TRP associated with an uplink transmission, it may be possible to provide a separate pathloss reference signal configuration field for each TRP, or to provide a single pathloss reference signal configuration field that includes pathloss reference signal configuration index values associated with multiple pathloss reference signal configurations, among other possibilities.
[0063] As another example, for 3GPP Type-B DG PUSCH repetition, it may be the case that various parameters can be configured by DCI for each TRP independently, such as the P0 parameter (target received power), the alpha parameter (path loss compensation factor), the path loss reference signal, the beam (e.g., in the form of TCI or Sounding Reference Signal (SRS) Resource Indicator (SRI)), and / or the transmit precoding matrix indicator (TPMI) and number of layers, may be indicated by DCI in such a scenario.
[0064] As previously described herein, in some instances, the uplink data transmission configuration information may configure a 3GPP non-codebook-based (NCB) PUSCH transmission. In such a scenario, the uplink data transmission configuration information may configure 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 for which an NCB PUSCH 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, it may be the case that two SRS resource indicator fields may be configured in DCI formats 0_1 and 0_2 for NCB-based PUSCH operation. In such a scenario, each SRS resource indicator field may map to one SRS resource set when NCB is configured.
[0066] As another possibility, the uplink data transmission configuration information may configure an SRS resource set, which is associated with multiple NZP-CSI-RS resources. For example, a first portion of the SRS resources of the SRS resource set may be associated with a first TRP, and a second portion of the SRS resources of the SRS resource set may be associated with a second TRP. In relation to such a scenario, it should be noted that one possibility may be that the number of SRS resources that may be configured per SRS resource set (e.g., to support the possibility of including sufficient SRS resources for PUSCH transmission to multiple TRPs) may be increased, e.g., from 4 to 8. In at least some instances, the mapping of each SRS resource to an associated NZP-CSI-RS resource may be configured by RRC control signaling.
[0067] At 506, the wireless device can perform uplink data transmission to the multiple TRPs. The uplink data transmission can 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. The uplink data transmission can be performed using a configured transmission pattern, for example, if applicable.
[0068] It should be noted that, according to at least some embodiments, there may be cases where a nominally scheduled PUSCH repetition may be truncated if a duplex conflict exists (e.g., if downlink communication is scheduled during a PUSCH repetition for a wireless device configured for half-duplex operation) and / or if a PUSCH repetition is scheduled across a slot boundary. In such scenarios, there may be a mechanism for determining, for example, which TRP each actual repetition is transmitted to according to a configured transmission pattern. For example, as one possibility, the wireless device may be configured to determine, based on the nominal repetition of the uplink data transmission, for which TRP each actual uplink data transmission should be performed according to the configured transmission pattern. As another possibility, the wireless device may be configured to determine, based on the actual repetition of the uplink data transmission, for which TRP each actual uplink data transmission should be performed according to the configured transmission pattern. As a further possibility, the wireless device may be configured to determine, based on the slot in which the uplink data transmission is performed, for which TRP each actual uplink data transmission should be performed according to the configured transmission pattern.
[0069] The uplink data transmission may be received by the cellular network. For example, each TRP scheduled to perform an uplink data transmission may receive at least a portion (e.g., one or more repetitions) of the uplink data transmission from the wireless device.
[0070] 5 may be used to provide a framework for more reliably configuring and executing uplink data transmissions in a cellular communication system. Such a framework, according to at least some embodiments, may be particularly useful in supporting enhanced PUSCH reliability by leveraging the potential availability of multiple TRPs and multiple wireless device antenna panels to provide increased beam diversity for uplink data communications, among other possible benefits. Figures 6 to 10 and additional information
[0071] Figures 6-10 show further embodiments that may be used, if desired, in conjunction with the method of Figure 5. It should be noted, however, that the exemplary details shown in Figures 6-10 and described with respect to Figures 6-11 are not intended to limit the disclosure as a whole, and numerous variations and alternatives to the details provided herein below are possible and should be considered within the scope of the disclosure.
[0072] 3GPP Release 16 supports multi-TRP design 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 overlapped PDSCHs, frequency division multiplexing (FDM) mode with a single transport block (TB), FDM mode with two TBs, intra-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. The nominal repetitions may be performed consecutively if configured. When the nominal repetitions would be performed across a slot boundary or in conflict with a duplexing duplex direction, the nominal PUSCH transmission may be aborted.
[0074] For example, further improvements to PUSCH reliability may be possible by providing support for PUSCH transmission to multiple TRPs. For example, techniques for configuring and performing configured grant (CG), dynamic grant (DG), and / or non-codebook based (NCB) PUSCH transmission to multiple TRPs are described herein, which may help improve PUSCH reliability, at least in some instances.
[0075] 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 the RRCConfiguredGrantConfig information element (IE); In 3GPP Type II CG-PUSCH, the CG-PUSCH may be activated or deactivated by DCI format 0_0, 0_1, or 0_2, with 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 the way RRC configuration is performed may be introduced to provide support for multi-TRP PUSCH operation. These modifications may include providing mechanisms 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, it may be the case that the ConfiguredGrantConfig information element may be used to configure uplink transmissions without dynamic grants and may include the rrc-ConfiguredUplinkGrant field. Such fields may include the precodingAndNumberOfLayers, srs ResourceIndicator, and pathlossReferenceIndex parameters, 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 precoding for different TRPs in such an IE, an additional field (e.g., "additional precodingAndNumberOfLayers") may be introduced to configure a precoder for the second TRP, thus potentially allowing two different precoding configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of precodingAndNumberOfLayers codepoints, where each precodingAndNumberOfLayers codepoint may include one or two entries of uplink rank and transmit precoding matrix indicator (TPMI), and the precodingAndNumberOfLayers parameter may be used to indicate the precodingAndNumberOfLayers codepoint.
[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 allowing two different beam configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of SRS resource codepoints, each of which may contain one or two sets of SRS resources, and the srs-ResourceIndicator parameter may be used to indicate the SRS resource codepoint.
[0079] As one possibility to provide support for indicating different pathloss reference signals for different TRPs in such an IE, an additional field (e.g., "Additional pathlossReferenceIndex") may be introduced to configure a pathloss reference signal for the second TRP, thus potentially allowing two different pathloss reference signal configurations for two different TRPs. As another such possibility, the RRC configuration may provide a list of pathlossReferenceIndex codepoints, where each pathlossReferenceIndex may contain one or two pathloss reference signal configurations, and the pathlossReferenceIndex parameter may be used to indicate the pathlossReferenceIndex codepoint.
[0080] For 3GPP Type I CG-PUSCH, when different beams, precoding, and / or path loss reference signals are configured per TRP, there may be multiple possible mappings to the actual PUSCH transmission. Figures 6-8 show some such possible transmission patterns according to some embodiments.
[0081] FIG. 6 illustrates an exemplary possible transmission pattern in which the TRPs at which PUSCH transmissions are performed alternate in a cyclic pattern at each repetitive opportunity, e.g., such that the TRPs at which PUSCH transmissions are performed alternate at each transmission opportunity.
[0082] 7 illustrates an example possible transmission pattern in which the TRPs at which PUSCH transmissions are performed alternate in a consecutive pattern for each repetition opportunity, e.g., such that the TRPs at which PUSCH transmissions are performed alternate after a sequence of PUSCH transmissions of a specified length is performed. In the illustrated example, the sequence length may include two PUSCH transmissions.
[0083] FIG. 8 illustrates an exemplary possible transmission pattern in which the TRPs on which PUSCH transmissions are performed alternate in a slot-by-slot sequential pattern, such 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, the open loop power control (OLPC) related powerControlLoopToUse and / or p0-PUSCH-Alpha parameters may additionally or alternatively be configured independently for each TRP.
[0085] According to some embodiments, it may be possible to use techniques similar to those described herein for 3GPP Type I CG PUSCH operation for 3GPP Type A DG PUSCH operation, for example, to transmit PUSCH repetitions on multiple TRPs.
[0086] For Type-B DG PUSCH repetitions, various parameters may be allowed to be configured / indicated by DCI for each TRP independently. Such parameters may include any 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 transmission configuration indicator (TCI) or sounding reference signal (SRI) resource indicator), and / or TPMI and number of layers.
[0087] For such Type-B DG PUSCH repetitions, when one or more parameters are configured independently for each of multiple TRPs, there may be multiple possibilities for mapping the nominal PUSCH repetitions to actual PUSCH transmissions, e.g., taking into account possible truncation of the nominal PUSCH transmissions due to duplex direction contention or crossing of slot boundaries with the nominal PUSCH transmissions. Figure 9 illustrates some such possible options that may be used to map the nominal PUSCH repetitions to actual PUSCH transmissions, according to at least some embodiments.
[0088] As shown, in the first option 910, the mapping of which TRP an actual PUSCH transmission is transmitted to may be based on the nominal repetition. Thus, in this approach, the first actual PUSCH repetition may be transmitted to TRP1, the second and third actual PUSCH repetitions may be transmitted to TRP2, the fourth and fifth actual PUSCH repetitions may be transmitted to TRP1, and the sixth actual PUSCH repetition may be transmitted to TRP2.
[0089] In a second illustrated option 920, the mapping of which TRP the actual PUSCH transmission is transmitted to may be based on the actual repetition. Thus, in this approach, the first actual PUSCH repetition may be transmitted to TRP1, the second actual PUSCH repetition may be transmitted to TRP2, the third actual PUSCH repetition may be transmitted to TRP1, the fourth actual PUSCH repetition may be transmitted to TRP2, the fifth actual PUSCH repetition may be transmitted to TRP1, and the sixth actual PUSCH repetition may be transmitted to TRP2.
[0090] In a third illustrated option 930, the mapping of which TRP the actual PUSCH transmission is transmitted on may be based on the slot the PUSCH transmission is performed in. Thus, in this approach, the first, second, and third actual PUSCH repetitions may be transmitted on TRP1, and the fourth, fifth, and sixth actual PUSCH repetitions may be transmitted on TRP2.
[0091] For 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. Figure 10 illustrates some examples of such possible approaches, according to some embodiments. As shown, in the illustrated example, each SRS-ResourceSet logically maps to one TRP. Each SRS-ResourceSet may be configured with different non-zero power channel state information reference signal resource identifiers (NZP-CSI-RS-ResourceIds), each of which may be transmitted from a different TRP.
[0092] In some instances, for NCB PUSCH operation, it may be possible to configure two SRS resource indicator fields in 3GPP DCI formats 0_1 and 0_2 when two SRS-ResourceSets are configured, each mapped to one TRP. In such a scenario, each SRS resource indicator field may map to one SRS-ResourceSet with the use of "nonCodebook".
[0093] As a further possibility, it may be the case that for NCB PUSCH operation, a single SRS-ResourceSet may be configured to include more than one associated NZP-CSI-RS-ResourceId. In such a scenario, it may be the case that the number of SRS resources that may be configured per SRS-ResourceSet may be increased, for example, from 4 to 8. The mapping of each SRS-resource in the SRS-ResourceSet to the 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 wireless link with a cellular base station, receiving uplink data transmission configuration information, where the uplink data transmission configuration information configures 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, the uplink data transmission configuration information configures a 3GPP configuration grant Physical Uplink Shared Channel (PUSCH) transmission.
[0097] According to some embodiments, the uplink data transmission configuration information configures a 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission.
[0098] According to some embodiments, the uplink data transmission configuration information configures a 3GPP non-codebook based Physical Uplink Shared Channel (PUSCH) transmission.
[0099] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission for multiple TRPs.
[0100] In some embodiments, the uplink data transmission configuration information includes, for each TRP associated with the uplink transmission, information indicative of one or more of beam information, precoding information, path loss reference signal information, target received power information, or path loss compensation factor.
[0101] Another set of embodiments may include a wireless device comprising an antenna, a radio operably coupled to the antenna, and a processor operably coupled to the radio, the wireless device configured to establish a wireless link with a cellular base station, receive uplink data transmission configuration information, where the uplink data transmission configuration information configures 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 one of a separate beam configuration field for each TRP or a single beam configuration field that includes beam configuration index values associated with multiple 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, a single precoding configuration field including precoding configuration index values associated with multiple precoding configurations.
[0104] According to some embodiments, the uplink data transmission configuration information includes pathloss reference signal information for each TRP associated with the uplink transmission, and the pathloss reference signal information for each TRP is indicated using one of a separate pathloss reference signal configuration field for each TRP or a single pathloss reference signal configuration field that includes pathloss reference signal configuration index values associated with multiple pathloss reference signal configurations.
[0105] According to some embodiments, for each TRP associated with an uplink transmission, the uplink data transmission configuration information independently configures one or more of the target received power information or the path loss compensation factor.
[0106] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission to multiple TRPs, whereby individual repetitions are transmitted alternately to the multiple TRPs according to the transmission pattern.
[0107] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission to multiple TRPs, whereby a sequence of repetitions is transmitted alternately to the multiple TRPs according to the transmission pattern.
[0108] According to some embodiments, the uplink data transmission configuration information sets a transmission pattern for repeating uplink data transmission for multiple TRPs, whereby transmissions are made to alternate TRPs in alternate slots according to the transmission pattern.
[0109] Yet another set of embodiments may include a method including establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information, where the uplink data transmission configuration information configures 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, the uplink data transmission configuration information configures a transmission pattern that determines on which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be performed, and when a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method further includes determining on which TRP of the plurality of TRPs each actual uplink data transmission should be performed according to the transmission pattern based on the nominal repetition of the uplink data transmission.
[0111] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern that determines on which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be performed, and when a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method further includes determining on which TRP of the plurality of TRPs each actual uplink data transmission should be performed according to the transmission pattern based on the actual repetition of the uplink data transmission.
[0112] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern that determines on which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be performed, and when a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method further includes determining on which TRP of the plurality of TRPs each actual uplink data transmission should be performed according to the transmission pattern based on the slot in which the uplink data transmission is performed.
[0113] According to some embodiments, the 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, each sounding reference signal resource set configured using a non-zero power channel state information reference signal.
[0114] According to some embodiments, the uplink data transmission configuration information configures a non-codebook based (NCB) physical uplink shared channel (PUSCH) transmission, the uplink data transmission configuration information configures a sounding reference signal resource set, the sounding reference signal resource set being 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 being associated with a first TRP, and a second portion of the sounding reference signal resources of the sounding reference signal resource set being associated with a second TRP.
[0115] A further set of embodiments may include an apparatus including a processor configured to cause a cellular base station to establish a wireless link with a wireless device, provide uplink data transmission configuration information to the wireless device, where the uplink data transmission configuration information configures uplink data transmissions to a plurality of transmission / reception points (TRPs), and receive at least a portion of the uplink data transmissions to the plurality of TRPs.
[0116] According to some embodiments, the uplink data transmission configuration information configures a 3GPP configuration grant Physical Uplink Shared Channel (PUSCH) transmission.
[0117] According to some embodiments, the uplink data transmission configuration information configures a 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission.
[0118] According to some embodiments, the uplink data transmission configuration information configures a 3GPP non-codebook based Physical Uplink Shared Channel (PUSCH) transmission.
[0119] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission for multiple TRPs.
[0120] In some embodiments, the uplink data transmission configuration information independently configures one or more of beam information, precoding information, path loss reference signal information, target received power information, or path loss compensation factor for each TRP associated with the uplink transmission.
[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, the cellular base station configured to establish a wireless link with a wireless device, provide uplink data transmission configuration information to the wireless device, the uplink data transmission configuration information configuring uplink data transmissions to a plurality of transmission / reception points (TRPs), and receive at least a portion of the uplink data transmissions 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 one of a separate beam configuration field for each TRP or a single beam configuration field that includes beam configuration index values associated with multiple 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, a single precoding configuration field including precoding configuration index values associated with multiple precoding configurations.
[0124] According to some embodiments, the uplink data transmission configuration information includes pathloss reference signal information for each TRP associated with the uplink transmission, and the pathloss reference signal information for each TRP is indicated using one of a separate pathloss reference signal configuration field for each TRP or a single pathloss reference signal configuration field that includes pathloss reference signal configuration index values associated with multiple pathloss reference signal configurations.
[0125] According to some embodiments, for each TRP associated with an uplink transmission, the uplink data transmission configuration information independently configures one or more of the target received power information or the path loss compensation factor.
[0126] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission to multiple TRPs, whereby individual repetitions are transmitted alternately to the multiple TRPs according to the transmission pattern.
[0127] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern for repetition of uplink data transmission to multiple TRPs, whereby a sequence of repetitions is transmitted alternately to the multiple TRPs according to the transmission pattern.
[0128] According to some embodiments, the uplink data transmission configuration information sets a transmission pattern for repeating uplink data transmission for multiple TRPs, whereby transmissions are made to alternate TRPs in alternate slots according to the transmission pattern.
[0129] A further set of embodiments may include a method including: establishing, by a cellular base station, a wireless link with a wireless device; providing uplink data transmission configuration information to the wireless device, the uplink data transmission configuration information configuring 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, the uplink data transmission configuration information configures a transmission pattern that determines for which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be made, and according to the transmission pattern, when a nominal uplink data transmission is aborted due to duplex contention or being scheduled across a slot boundary, for which TRP of the plurality of TRPs each actual uplink data transmission is to be made is determined based on the nominal repetition of the uplink data transmission.
[0131] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern that determines for which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be made, and according to the transmission pattern, when a nominal uplink data transmission is aborted due to duplex contention or being scheduled across a slot boundary, for which TRP of the plurality of TRPs each actual uplink data transmission is to be made is determined based on the actual repetition of the uplink data transmission.
[0132] According to some embodiments, the uplink data transmission configuration information configures a transmission pattern that determines for which TRP of the plurality of TRPs each repetition of the uplink data transmission is to be made, and according to the transmission pattern, when a nominal uplink data transmission is aborted due to duplex contention or being scheduled across a slot boundary, for which TRP of the plurality of TRPs each actual uplink data transmission is to be made is determined based on the slot in which the uplink data transmission is made.
[0133] According to some embodiments, the uplink data transmission configuration information configures at least a portion of a non-codebook based (NCB) physical uplink shared channel (PUSCH) transmission, the uplink data transmission configuration information configures a non-zero power channel state information reference signal associated with a sounding reference signal resource set, and additional uplink data transmission configuration information configuring additional non-zero power channel state information reference signals associated with additional sounding reference signal resource sets is also provided to the wireless device.
[0134] According to some embodiments, the uplink data transmission configuration information configures at least a portion of a non-codebook based (NCB) physical uplink shared channel (PUSCH) transmission, the uplink data transmission configuration information configures a sounding reference signal resource set, the sounding reference signal resource set being 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 being associated with a first TRP, and a second portion of the sounding reference signal resources of the sounding reference signal resource set being associated with a second TRP.
[0135] Further exemplary embodiments may include a method, the method including performing, by a device, any or all parts of the above examples.
[0136] Another example 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 configured to implement any or all portions of the aforementioned examples.
[0137] A further exemplary set of embodiments can include a non-transitory computer-accessible memory medium that includes program instructions that, when executed on a device, cause the device to perform any or all portions of any of the foregoing examples.
[0138] A still further exemplary set of embodiments may include a computer program including instructions for carrying out any or all portions of any of the foregoing examples.
[0139] Yet another exemplary set of embodiments may include an apparatus comprising means for performing any or all of the elements of any of the preceding examples.
[0140] Yet another example set of embodiments may include an apparatus comprising a processing element configured to cause a device to perform any or all of the elements of any of the preceding examples.
[0141] Yet another example set of embodiments may include a baseband processor configured to perform operations including any or all of the elements of any of the preceding examples.
[0142] It is well understood that use of personal information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personal information 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 uses should be clearly indicated to users.
[0143] Any of the methods described herein for operating a user equipment (UE) may be 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] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, in some embodiments, the subject matter may be implemented as a computer-implemented method, 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 an ASIC. In other embodiments, the subject matter may be implemented using one or more programmable hardware elements, such as an FPGA.
[0145] In some embodiments, a non-transitory computer-readable memory medium (e.g., a non-transitory memory element) may store program instructions and / or data that, when executed by a computer system, may be configured to cause the computer system to perform a method, such as any of the method embodiments described herein, or a combination of the method embodiments described herein, or a subset of the method embodiments described herein, or a combination of such subsets.
[0146] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or set of processors) and a memory medium (or memory element), where the memory medium stores program instructions and the processor is configured to read and execute the program instructions from the memory medium, where 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 a variety of forms.
[0147] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.
Claims
1. 1. A baseband processor configured to perform operations, the operations comprising: Establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information, the uplink data transmission configuration information configuring uplink data transmission to a plurality of transmission / reception points (TRPs); performing the uplink data transmission to the plurality of TRPs; a baseband processor including:
2. The uplink data transmission configuration information configures a 3GPP configuration grant Physical Uplink Shared Channel (PUSCH) transmission. The baseband processor of claim 1 .
3. The uplink data transmission configuration information configures a 3GPP dynamic grant physical uplink shared channel (PUSCH) transmission. The baseband processor of claim 1 .
4. The uplink data transmission configuration information configures a 3GPP non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission. The baseband processor of claim 1 .
5. The uplink data transmission configuration information configures a transmission pattern for performing repetition of the uplink data transmission for the plurality of TRPs. The baseband processor of claim 1 .
6. The uplink data transmission configuration information comprises, for each TRP associated with the uplink transmission: Beam information, Precoding information, Path loss reference signal information; Target received power information, or a path loss compensation factor; The baseband processor of claim 1 .
7. 1. A wireless device, comprising: The antenna, a radio operably coupled to the antenna; a processor operably coupled to the radio; The wireless device comprises: Establishing a radio link with a cellular base station; receiving uplink data transmission configuration information, the uplink data transmission configuration information configuring uplink data transmission to a plurality of transmission / reception points (TRPs); A wireless device configured to perform the uplink data transmission to the multiple TRPs.
8. The uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, the beam information for each TRP comprising: A separate beam configuration field for each TRP, or Indicated using one of the single beam configuration fields that includes beam configuration index values associated with multiple beam configurations; 8. The wireless device of claim 7.
9. The uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, the precoding information for each TRP being: A separate precoding configuration field for each TRP, or indicated using one of a single precoding configuration field that includes a precoding configuration index value associated with a plurality of precoding configurations; 8. The wireless device of 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 includes: A separate path loss reference signal configuration field for each TRP, or indicated using one of a single pathloss reference signal configuration field that includes a pathloss reference signal configuration index value associated with a plurality of pathloss reference signal configurations; 8. The wireless device of claim 7.
11. For each TRP associated with the uplink transmission, the uplink data transmission configuration information comprises: Target received power information, or [0036] independently configuring one or more of:
8. The wireless device of claim 7.
12. The uplink data transmission configuration information configures a transmission pattern for performing repetitions of 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.
8. The wireless device of claim 7.
13. the uplink data transmission configuration information configures a transmission pattern for performing repetitions of the uplink data transmissions to the plurality of TRPs, and a sequence of repetitions is transmitted alternately to the plurality of TRPs according to the transmission pattern; 8. The wireless device of claim 7.
14. The uplink data transmission configuration information configures a transmission pattern for repeating the uplink data transmission for the plurality of TRPs, and transmissions are performed on alternate TRPs in alternate slots according to the transmission pattern.
8. The wireless device of claim 7.
15. Establishing a wireless link with a cellular base station; receiving uplink data transmission configuration information, the uplink data transmission configuration information configuring uplink data transmission to a plurality of transmission / reception points (TRPs); performing the uplink data transmission to the plurality of TRPs; A method comprising:
16. The uplink data transmission configuration information configures a transmission pattern that determines on which of the plurality of TRPs each repetition of the uplink data transmission is to be performed; When a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method includes: determining, based on a nominal repetition of the uplink data transmission, on which of the plurality of TRPs each actual uplink data transmission should be performed according to the transmission pattern; The method of claim 15.
17. The uplink data transmission configuration information configures a transmission pattern that determines on which of the plurality of TRPs each repetition of the uplink data transmission is to be performed; When a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method includes: Further comprising: determining, based on an actual repetition of the uplink data transmission, for which TRP of the plurality of TRPs each actual uplink data transmission is to be performed according to the transmission pattern. The method of claim 15.
18. The uplink data transmission configuration information configures a transmission pattern that determines on which of the plurality of TRPs each repetition of the uplink data transmission is to be performed; When a nominal uplink data transmission is aborted due to a duplex contention or due to being scheduled across a slot boundary, the method includes: Further comprising: determining for which TRP among the plurality of TRPs each actual uplink data transmission is to be performed according to the transmission pattern based on a slot in which the uplink data transmission is performed; The method of claim 15.
19. The uplink data transmission configuration information configures a non-codebook based (NCB) physical uplink shared channel (PUSCH) transmission; The uplink data transmission configuration information configures a plurality of sounding reference signal resource sets, each sounding reference signal resource set being configured using a non-zero power channel state information reference signal (NZP-CSI-RS). The method of claim 15.
20. The uplink data transmission configuration information configures a non-codebook based (NCB) physical uplink shared channel (PUSCH) transmission; The uplink data transmission configuration information configures a sounding reference signal resource set, the sounding reference signal resource set being associated with a plurality of non-zero power channel state information reference signals (NZP-CSI-RSs), a first portion of the sounding reference signal resources of the sounding reference signal resource set being associated with a first TRP, and a second portion of the sounding reference signal resources of the sounding reference signal resource set being associated with a second TRP. The method of claim 15.
Citation Information
Patent Citations
Method and apparatus for beam indication for uplink transmission in a wireless communication system
US20190349964A1
Method and apparatus for communicating user data via a physical shared channel
US20200107353A1
User equipment and radio communication method
WO2020044409A1
