Configure physical uplink shared channel transmission with improved reliability
By providing personalized uplink data transmission configurations to wireless devices through cellular base stations and utilizing beam diversity technology with multiple transmission and reception points, the reliability problem of signal transmission in wireless communication systems is solved, and the accuracy of signal reception and the battery life of devices are improved.
Patent Information
- Application Number
- CN202080105768.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-10-02
- Publication Date
- 2025-12-02
- Estimated Expiration
- 2040-10-02
AI Technical Summary
In wireless communication systems, existing technologies struggle to effectively improve the reliability of physical uplink shared channels, especially in beam diversity environments with multiple transmission and reception points. This results in insufficient accuracy and reliability of signal transmission, impacting device battery life and communication quality.
Cellular base stations provide uplink data transmission configuration information to wireless devices, allowing wireless devices to transmit data to multiple transmission and receiving points and configure transmission parameters individually according to the characteristics of each transmission and receiving point, thereby improving the reliability of signal reception by leveraging the potential of beam diversity.
By coordinating transmission through multiple transmission and receiving points, the reliability of uplink data communication is improved, power requirements are reduced, device battery life is extended, and good communication quality is maintained.
Smart Images

Figure CN116325595B_ABST
Abstract
Description
Technical Field
[0001] This application relates to wireless communication, and more specifically to systems, apparatus, and methods for configuring physical uplink shared channel transmission in wireless communication systems with improved reliability.
[0002] Related technical descriptions
[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (LTE-Advanced), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and BLUETOOTH. TM wait.
[0004] The increasing number of features and functions introduced into wireless communication devices necessitates continuous improvement of both wireless communication and the devices themselves. Specifically, it is crucial to ensure the accuracy of signals transmitted and received by user equipment (UE) devices (e.g., wireless devices such as cellular phones, base stations, and relay stations used in wireless cellular communications). Furthermore, increasing the functionality of UE devices can significantly strain their battery life. Therefore, it is equally important to reduce the power requirements in UE device design while allowing them to maintain good transmit and receive capabilities for improved communication. Thus, improvements are expected in this area. Summary of the Invention
[0005] This paper provides implementation schemes for apparatus, systems, and methods for configuring physical uplink shared channel transmission in wireless communication systems with improved reliability.
[0006] According to the technology described herein, a cellular base station can provide uplink data transmission configuration information to a wireless device configured to transmit uplink data to multiple transmission receiving points. The cellular base station can also receive at least a portion of the uplink data transmission from the wireless device. The uplink data transmission can be any of various types of uplink data transmission, and some or all of the parameters used to transmit to each of the configured transmission receiving points can be configured individually for each transmission receiving point.
[0007] According to at least some implementation schemes, configuring uplink data transmission in this manner can help improve the reliability of uplink data communication, specifically by taking advantage of the potential for beam diversity when uplink data can be received by multiple transmission receiving points.
[0008] It should be noted that the technologies described herein can be implemented in and / or used in several different types of devices, including but not limited to base stations, access points, mobile phones, portable media players, tablets, wearable devices, unmanned aerial vehicles, unmanned flight controllers, automobiles and / or motor vehicles, and various other computing devices.
[0009] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description
[0010] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:
[0011] Figure 1 Exemplary (and simplified) wireless communication systems according to some implementation schemes are shown;
[0012] Figure 2 An exemplary base station communicating with an exemplary wireless user equipment (UE) device according to some embodiments is shown;
[0013] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown;
[0014] Figure 4 An exemplary block diagram of a base station according to some implementation schemes is shown;
[0015] Figure 5This is a flowchart illustrating various aspects of exemplary possible methods for providing physical uplink shared channel transmission with improved reliability in a wireless communication system, according to some implementation schemes;
[0016] Figures 6 to 8 Exemplary aspects of various possible transport modes that can be used to configure authorized physical uplink shared channel transport according to some implementation schemes are shown;
[0017] Figure 9 Various possible exemplary methods for mapping TRP to repetitions for dynamically licensed physical uplink shared channel transmissions, according to some implementation schemes, are shown; and
[0018] Figure 10 Exemplary aspects of possible non-codebook-based physical uplink shared channel operation according to some implementation schemes are shown.
[0019] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation
[0020] acronym
[0021] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:
[0022] UE: User Equipment
[0023] RF: Radio Frequency
[0024] ·BS: Base Station
[0025] GSM: Global System for Mobile Communications
[0026] UMTS: Universal Mobile Telecommunications System
[0027] LTE: Long Term Evolution
[0028] NR: New Radio
[0029] TX: Transmission
[0030] RX: Receiver
[0031] • RAT: Radio Access Technology
[0032] • TRP: Transmitter / Receiver Point
[0033] • DCI: Downlink Control Information
[0034] • CORESET: Control Resource Set
[0035] • CSI: Channel State Information
[0036] • CSI-RS: Channel State Information Reference Signal
[0037] the term
[0038] The following is a glossary of terms that will appear in this disclosure:
[0039] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In a later example, the second computer system may provide program instructions to the first computer system for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.
[0040] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).
[0041] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. Generally, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.
[0042] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), tablet computers (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM This includes wearable devices (e.g., smartwatches, 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), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.
[0043] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.
[0044] A communication device is any of 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 it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.
[0045] Base station (BS) — The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.
[0046] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (such as a user equipment device or a cellular network device). A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.
[0047] Wi-Fi—The term “Wi-Fi” encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.
[0048] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.
[0049] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.
[0050] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.
[0051] Figure 1 and Figure 2 -Exemplary communication system
[0052] Figure 1 Exemplary (and simplified) wireless communication systems that can implement various aspects of this disclosure according to some embodiments are shown. It should be noted that... Figure 1 The system described is merely one example of a possible system, and this implementation can be carried out in any of a variety of systems as needed.
[0053] As shown in the figure, this exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number) user equipments 106A, 106B, etc., up to 106N, via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE) or UE device. Therefore, user equipment 106 is referred to as a UE or UE device.
[0054] Base station 102 may be a transceiver base station (BTS) or a cell site, and may include hardware and / or software for implementing wireless communication with UEs 106A to 106N. If base station 102 is implemented in the context of LTE, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possible networks). Therefore, base station 102 facilitates communication between user equipments and / or between user equipments and network 100. The communication area (or coverage area) of a base station may be referred to as a "cell". Also as used herein, in relation to a UE, a base station may sometimes be considered to represent the network, taking into account both uplink and downlink communication of the UE. Therefore, a UE communicating with one or more base stations in the network may also be understood as a UE communicating with the network.
[0055] Base station 102 and user equipment can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-A Advanced, LAA / LTE-U, 5G NR, 3GPP2, CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.
[0056] Base station 102 and other similar base stations operating according to the same or different cellular communication standards may thus provide, as one or more cell networks, continuous or near-continuous overlapping services to UE 106 and similar devices over a geographic area via one or more cellular communication standards.
[0057] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, UE 106 can be configured to communicate using either or both of the 3GPP cellular communication standards or the 3GPP2 cellular communication standards. In some implementations, UE 106 can be configured to perform robust uplink data transmission techniques, such as those described herein. UE 106 can also be configured, or alternatively configured, to use WLAN, BLUETOOTH, etc. TM It can communicate with one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.
[0058] Figure 2An exemplary user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 according to some embodiments is illustrated. UE 106 can be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device, computer or tablet, unmanned aerial vehicle (UAV), unmanned flight controller (UAC), automobile, or virtually any type of wireless device. UE 106 may include a processor (processing element) configured to execute program instructions stored in memory. UE 106 can perform any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as any of an FPGA (Field Programmable Gate Array), integrated circuit, and / or various other possible hardware components configured to perform (e.g., individually or in combination) any of or any portion of any of the method embodiments described herein. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 can be configured to communicate using two or more of CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.
[0059] UE 106 may include one or more antennas communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication standards. The shared radio components may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Typically, the radio components may include any combination of baseband processors, analog radio frequency (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, the radio components may use the aforementioned hardware to implement one or more receive chains and transmit chains.
[0060] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and shared radio components for communication using Wi-Fi and BLUETOOTH.TM Each component communicates via a separate radio. Other configurations are also possible.
[0061] Figure 3 - Block diagram of an exemplary UE device
[0062] Figure 3 A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, UE 106 may include a System-on-Chip (SOC) 300, which may include parts for various purposes. For example, as shown, SOC 300 may include a processor 302 capable of executing program instructions for UE 106, and display circuitry 304 capable of performing graphics processing and providing display signals to a display 360. SOC 300 may also include sensor circuitry 370, which may include components for sensing or measuring any of a variety of possible characteristics or parameters of UE 106. For example, sensor circuitry 370 may include motion sensing circuitry configured to detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of a variety of other motion sensing components. As another possibility, sensor circuitry 370 may include one or more temperature sensing components, for example, for measuring the temperature of each of one or more antenna panels and / or other components of UE 106. Any of a variety of other possible types of sensor circuitry may also or alternatively be included in UE 106 as needed. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, connector I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.
[0063] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH). TM(e.g., Wi-Fi, GPS, etc.). UE device 106 may include at least one antenna (e.g., 335a) and may include multiple antennas (e.g., shown 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 UE device 106 may include fewer or more antennas. In general, one or more antennas are collectively referred to as antenna 335. For example, UE device 106 may use antenna 335 to perform wireless communication via radio circuitry 330. As described above, in some embodiments, the UE may be configured to use multiple wireless communication standards for wireless communication.
[0064] UE 106 may include hardware and software components for implementing methods of performing uplink data transmission techniques with improved reliability, such as those described further herein. The processor 302 of UE device 106 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, processor 302 may be coupled to, for example,... Figure 3 Other components shown and / or interoperable with these other components can be used to perform uplink data transmission techniques with improved reliability according to the various embodiments disclosed herein. Processor 302 can also implement various other applications and / or end-user applications running on UE 106.
[0065] In some implementations, radio component 330 may include a separate controller dedicated to controlling communications for various corresponding RAT standards. For example, such as Figure 3 As shown, the radio component 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. TM Controller 356, and in at least some embodiments, one or more of these controllers may be implemented as corresponding integrated circuits (referred to as ICs or chips), which communicate with each other and with the SOC 300 (more specifically with the processor 302). For example, Wi-Fi controller 352 may communicate with cellular controller 354 via a cell-ISM link or WCI interface, and / or BLUETOOTH TMController 356 can communicate with cellular controller 354 via a cell-ISM link or the like. Although three separate controllers are shown within radio component 330, other implementations with fewer or more similar controllers for various different RATs can be implemented in UE device 106.
[0066] Furthermore, implementation schemes in which the controller can perform functions associated with various radio access technologies are envisioned. For example, according to some implementation schemes, in addition to hardware and / or software components for performing cellular communications, the cellular controller 354 may also include hardware and / or software components for performing one or more activities associated with Wi-Fi, such as Wi-Fi preamble detection, and / or the generation and transmission of Wi-Fi physical layer preamble signals.
[0067] Figure 4 - Block diagram of an exemplary base station
[0068] Figure 4 A block diagram of an exemplary base station 102 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).
[0069] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106. Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices such as UE device 106. In some cases, network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).
[0070] Base station 102 may include at least one antenna 434 and possibly multiple antennas. One or more antennas 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to NR, LTE, LTE-A WCDMA, CDMA2000, etc. Processor 404 of base station 102 may be configured to implement and / or support implementation of some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), base station 102 can be designed as an access point (AP), in which case network port 470 can be implemented to provide access to a wide area network and / or one or more local area networks, for example it may include at least one Ethernet port, and radio component 430 can be designed to communicate according to the Wi-Fi standard.
[0071] Figure 5 - Uplink data transmission technology with improved reliability
[0072] Wireless communication is being used in an increasingly wide range of use cases. For at least some of these types of communication, robustness and reliability may 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.
[0073] Such an area may include uplink data communications and / or other communications that can be performed on the Physical Uplink Shared Channel (PUSCH) of a cellular communication system. Specifically, 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.
[0074] therefore, Figure 5 This is a flowchart illustrating, according to at least some embodiments, a method for performing uplink data communication in a wireless communication system with improved reliability.
[0075] Figure 5The aspects of the method can be implemented by a wireless device, for example, in conjunction with one or more cellular base stations (such as UE 106 and BS 102 shown and described with respect to the various figures herein), or more generally, in conjunction as needed with any of the computer circuits, systems, devices, elements, or components shown in the aforementioned figures. For example, the processor (and / or other hardware) of such a device can be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements.
[0076] It should be noted that, although the description uses methods involving the use of communication technologies and / or features associated with 3GPP and / or NR specification documents, Figure 5 This method describes at least some elements, but this description is not intended to limit this disclosure and can be used in any suitable wireless communication system as needed. Figure 5 The method encompasses various aspects. In various implementation schemes, some elements of the method shown may be performed simultaneously in a different order than those shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown in the figure, Figure 5 The method can be operated as follows.
[0077] In section 502, a wireless device can establish a radio link with a cellular base station. According to some implementations, the radio link may include a 5G NR-based cellular link. For example, the wireless 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 an LTE-based cellular link. For example, the wireless 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 according to various implementations, and the cellular network may also, or alternatively, operate according to another cellular communication technology (e.g., UMTS, CDMA2000, GSM, etc.).
[0078] Establishing a radio link may include, according to at least some implementations, 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 environmental information for the radio device, and / or any of various other possible characteristics, such as establishing an air interface for the radio device to communicate with a cellular network associated with the cellular base station. After establishing an RRC connection, the radio device may operate in an RRC connected state. In some instances, the RRC connection may also be released (e.g., after a period of inactivity relative to data communication), in which case the radio device may operate in an RRC idle state or an RRC inactive state. In some instances, for example due to radio device mobility, changes in radio medium conditions, and / or any other possible reasons, the radio device may perform a handover (e.g., when in RRC connected mode) or cell reselection (e.g., when in RRC idle mode or RRC inactive mode) to a new serving cell.
[0079] According to at least some implementations, a wireless device can establish multiple wireless links, for example, with multiple TRPs in a cellular network, based on a multi-TRP configuration. In such scenarios, the wireless device may be configured (e.g., via RRC signaling) to have one or more Transmission Control Indicators (TCIs), which may correspond to various beams available for communication with the TRPs. Furthermore, there may be situations where one or more configured TCI states can be activated at a specific time by the wireless device's Media Access Control (MAC) control element (CE).
[0080] In at least some instances, establishing a wireless link may include the wireless device providing information about its capabilities. This capability information may include information related to any one of several types of wireless device capabilities.
[0081] In 504, the cellular base station can provide uplink data transmission configuration information to the radio device. This uplink data transmission configuration information can be provided using RRC control signaling, MAC signaling (e.g., MAC CE), downlink control information (DCI), or combinations thereof, and various other possible methods. The uplink data transmission configuration information can be configured for uplink data transmission across multiple TRPs.
[0082] Uplink data transmission can be any of the various types of uplink data transmission. As one possibility, uplink data transmission can be a configuration-granted (CG) PUSCH transmission, such as a 3GPP type 1 CG-PUSCH transmission (e.g., which can be configured by the RRC ConfiguredGrantConfig information element), or a 3GPP type 2 CG-PUSCH transmission (e.g., which can be activated or deactivated via DCI formats 0_0, 0_1, or 0_2, where the Cyclic Redundancy Code (CRC) is scrambled by the Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI)). As another possibility, uplink data transmission can be a dynamic-granted (DG) PUSCH transmission, such as a 3GPP type A PUSCH repeat or a 3GPP type B PUSCH repeat. As yet another possibility, uplink data transmission can be a 3GPP non-codebook (NCB) based PUSCH transmission.
[0083] According to some implementations, uplink data transmission configuration information can configure a repetitive transmission mode for performing uplink data transmissions to the plurality of TRPs. One such possible mode may include transmitting individual repetitions to the plurality of TRPs in an alternating manner. Another such possible mode may include transmitting a repetitive sequence (e.g., a sequence of specified length) to the plurality of TRPs in an alternating manner. Yet another possible mode may include performing TRP transmissions alternately in alternating time slots.
[0084] According to some implementations, 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 any or all of the following: 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.
[0085] This configuration information can be provided in any of a variety of possible ways. For example, for a 3GPP Type 1 CG-PUSCH transmission, some or all of these parameters can be configured using various fields of the RRC information element that configures the CG-PUSCH transmission. Therefore, to make it possible to indicate beam information for each TRP associated with an uplink transmission, a separate beam configuration field can be provided for each TRP, or a single beam configuration field including beam configuration index values associated with multiple beam configurations, or various other possible methods. Similarly, to make it possible to indicate precoding information for each TRP associated with an uplink transmission, a separate precoding configuration field can be provided for each TRP, or a single precoding configuration field including precoding configuration index values associated with multiple precoding configurations, or various other possible methods. Likewise, to make it possible to indicate path loss reference signal information for each TRP associated with an uplink transmission, a separate path loss reference signal configuration field can be provided for each TRP, or a single path loss reference signal configuration field including path loss reference signal configuration index values associated with multiple path loss reference signal configurations, or various other possible methods.
[0086] For example, for 3GPP type B DG PUSCH repetition, it is possible that various parameters can be configured individually for each TRP via DCI. For instance, in this case, any of the following parameters can be indicated by DCI: P0 parameter (target received power), Alpha parameter (path loss compensation factor), path loss reference signal, beam (e.g., in the form of TCI or SNR resource indicator (SRI)) and / or transport precoding matrix indicator (TPMI) and layer number.
[0087] As previously described, in some instances, uplink data transmission configuration information can configure 3GPP non-codebook (NCB) based PUSCH transmissions. In this case, it's possible that the uplink data transmission configuration information configures multiple SRS resource sets, with each SRS resource set configured using a non-zero power channel state information reference signal (NZP-CSI-RS). For example, NZP-CSI-RS can be configured for each TRP that schedules NCB PUSCH transmissions, and NZP-CSI-RS can effectively configure the SRS resource sets logically mapped to that TRP.
[0088] In some instances, when configuring two SRS resource sets and each resource set is mapped to a TRP, for NCB-based PUSCH operations, the two SRS resource indicator fields can be configured using DCI formats 0_1 and 0_2. In this case, when configuring NCB, each SRS resource indicator field can be mapped to one SRS resource set.
[0089] As another possibility, uplink data transmission configuration information can configure SRS resource sets, where each SRS resource set is associated with multiple NZP-CSI-RS resources. For example, a first portion of the SRS resources in an SRS resource set may be associated with a first TRP, and a second portion of the SRS resources in the SRS resource set may be associated with a second TRP. It should be noted that, in this context, it is possible to increase the number of configurable SRS resources per SRS resource set (e.g., to support the possibility of including sufficient SRS resources for PUSCH transmissions to multiple TRPs), for example, increasing from four to eight. At least in some instances, it is possible to configure the mapping of each SRS resource to its associated NZP-CSI-RS resource via RRC control signaling.
[0090] In 506, the wireless device can perform the uplink data transmission to the plurality of TRPs. The uplink data transmission can be performed based on uplink data transmission configuration information; for example, it may include using different configuration parameters when transmitting to each of the configured TRPs. For example, if applicable, a configured transmission mode can be used to perform the uplink data transmission.
[0091] It should be noted that, at least according to some implementations, it is possible that nominally scheduled PUSCH repetitions may be truncated if duplex conflicts exist (e.g., if downlink communication is scheduled during a PUSCH repetition of a wireless device configured for half-duplex operation), and / or if PUSCH repetitions are scheduled across time slot boundaries. In this case, a mechanism may exist for determining which TRP each actual repetition is transmitted to (e.g., based on a configured transmission mode). For example, as one possibility, the wireless device may be configured to determine, based on the nominal repetition of uplink data transmission, which determines which TRP each actual uplink data transmission should be performed for, according to the configured transmission mode. As another possibility, the wireless device may be configured to determine, based on the actual repetition of uplink data transmission, which determines which TRP each actual uplink data transmission should be performed for, according to the configured transmission mode. As yet another possibility, the wireless device may be configured to determine, based on the time slot in which uplink data transmission is performed, which determines which TRP each actual uplink data transmission should be performed for, according to the configured transmission mode.
[0092] Uplink data transmission can be received via a cellular network. For example, each TRP scheduled to perform uplink data transmission can receive at least a portion (e.g., one or more repetitions) of uplink data transmission from a wireless device.
[0093] therefore, Figure 5 The approach can be used to provide a framework for configuring and more reliably performing uplink data transmission in cellular communication systems. At least according to some implementations, such a framework may be particularly useful in supporting enhanced PUSCH reliability, specifically by leveraging the potential availability of multiple TRPs and multiple wireless device antenna panels to provide greater beam diversity for uplink data communication, among other potential benefits.
[0094] Figures 6 to 10 and additional information
[0095] Figures 6 to 10 It shows that it can be combined if needed. Figure 5 Another aspect of the method used. However, it should be noted that in Figures 6 to 10 Shown and about Figures 6 to 10 The exemplary details described are not intended to limit this disclosure as a whole: many variations and alternatives to the details provided below are possible and should be considered within the scope of this disclosure.
[0096] 3GPP Release 16 supports multi-TRP designs for improving the performance of Physical Downlink Shared Channel (PDSCH). This support can include scheduling up to two PDSCHs using multiple DCIs across up to five Control Resource Sets (CORESETs). It is also possible for a single DCI to schedule multiple PDSCHs in several possible modes, including Spatial Division Multiplexing (SDM) mode with fully overlapping PDSCHs, Frequency Division Multiplexing (FDM) mode with a single Transport Block (TB), FDM mode with two TBs, Intra-Slot Time Division Multiplexing (TDM) mode, and Inter-Slot TDM mode.
[0097] 3GPP Release 16 also supports Type B Physical Uplink Shared Channel (PUSCH) repetition for improved reliability. For example, parameters (e.g., numberOfRepetitions-r16) can be added to control signaling (e.g., in PUSCH-TimeDomainResourceAllocationListPUSCH-r16 within PUSCH-TimeDomainResourceAllocationListPUSCH-r16) to allow the number of PUSCH repetitions to be dynamically changed via DCI. Nominal repetitions (if configured) can be performed continuously. Nominal PUSCH transmissions can be truncated when nominal repetitions are performed across time slot boundaries or conflict with duplex direction.
[0098] For example, PUSCH reliability can be further improved by providing support for PUSCH transports to multiple TRPs. This paper describes techniques for configuring and performing Configuration Grant (CG), Dynamic Grant (DG), and / or Non-Codebook (NCB) based PUSCH transports to multiple TRPs, which can help improve PUSCH reliability in at least some instances.
[0099] According to some implementation schemes, it is possible that two types of supported CGPUSCH exist in 3GPP communications. In 3GPP Type I CG-PUSCH, the CG-PUSCH can be configured via the RRC ConfiguredGrantConfig information element (IE). In 3GPP Type II CG-PUSCH, the CG-PUSCH can be activated or deactivated via DCI format 0_0, 0_1, or 0_2, where the Cyclic Redundancy Code (CRC) is scrambled by the Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI).
[0100] For 3GPP Type I CG PUSCH, modifications to the method of performing RRC configuration may be introduced to provide support for multiple TRPPUSCH operations. These modifications may include providing a mechanism for signaling different precoding, beam, and / or path loss reference signals for different TRPs. According to Section 6.3.2 of 3GPP TS 38.331, v.16.1.0, it is possible that the ConfiguredGrantConfig information element can be used to configure uplink transports without dynamic grants and may include the rrc-ConfiguredUplinkGrant field. This field may include the precodingAndNumberOfLayers parameter, the srs-ResourceIndicator parameter, and the pathlossReferenceIndex parameter, which can be used to indicate the precoding, beam, and path loss reference signals used for CG-PUSCH operations.
[0101] As one possibility, to support different precoding for different TRPs in this IE, an additional field (e.g., "additional-precodingAndNumberOfLayers") can be introduced to configure the precoder for the second TRP, thus enabling two different precoding configurations for two different TRPs. Alternatively, the RRC configuration can provide a list of precodingAndNumberOfLayers codepoints, where each codepoint can contain one or two entries for the uplink rank and Transport Precoding Matrix Indicator (TPMI), and the precodingAndNumberOfLayers parameter can be used to indicate the codepoints.
[0102] As one possibility, to support indicating different beams for different TRPs in this IE, an additional field (e.g., "additional-srs-ResourceIndicator") can be introduced to configure the beam for the second TRP, thus enabling two different beam configurations for two different TRPs. Alternatively, the RRC configuration can provide a list of SRS resource code points, where each SRS resource code point can contain one or two SRS resource sets, and the srs-ResourceIndicator parameter can be used to indicate the SRS resource code point.
[0103] As one possibility, to support indicating different path loss reference signals for different TRPs in this IE, an additional field (e.g., "additional-pathlossReferenceIndex") can be introduced to configure the path loss reference signal for the second TRP, thus making it possible to implement two different path loss reference signal configurations for two different TRPs. As another possibility, the RRC configuration can provide a list of pathlossReferenceIndex code points, where each pathlossReferenceIndex can contain one or two path loss reference signal configurations, and the pathlossReferenceIndex parameter can be used to indicate the pathlossReferenceIndex code point.
[0104] For 3GPP Type I CG-PUSCH, when different beams, precoding and / or path loss reference signals are configured for each TRP, there may be multiple possible mappings to the actual PUSCH transmission. Figures 6 to 8 Several such possible transmission modes according to some implementation schemes are shown.
[0105] Figure 6 An exemplary possible transmission mode is shown, wherein the TRP that performs the PUSCH transmission to it alternates in a per-repetition-time cyclic mode, for example, such that the TRP that performs the PUSCH transmission to it alternates at each transmission time.
[0106] Figure 7 Exemplary possible transmission modes are shown, in which the TRP performing the PUSCH transmission performs alternation in a per-repetition sequence pattern, for example, such that the TRP performing the PUSCH transmission performs alternation after a PUSCH transmission sequence of a specified length. In the illustrated example, the sequence length may include 2 PUSCH transmissions.
[0107] Figure 8 An exemplary possible transmission mode is shown, in which the TRP performing the PUSCH transmission performs alternation in a per-slot sequence mode, for example, such that the TRP performing the PUSCH transmission performs alternation in each slot.
[0108] It should also be noted that, for type I CG-PUSCH, at least according to some implementations, the powerControlLoopToUse and / or p0-PUSCH-Alpha parameters related to open-loop power control (OLPC) can be configured separately for each TRP, either additionally or alternatively.
[0109] According to some implementation schemes, techniques similar to those described herein for 3GPP Type I CG PUSCH operations can be used for 3GPP Type A DDG PUSCH operations, for example, to transmit PUSCH duplicates to multiple TRPs.
[0110] For Type B DG PUSCH repetition, various parameters can be configured / indicated individually for each TRP via DCI. Such parameters may include 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 Transmission Configuration Indicator (TCI) or Sounding Reference Signal (SRI) resource indicator) and / or any or all of TPMI and layer number.
[0111] For this type of B DG PUSCH repetition, when one or more parameters are configured individually for each of the multiple TRPs, there may be multiple possibilities for mapping nominal PUSCH repetition to actual PUSCH transmissions, for example, considering that nominal PUSCH transmissions may be truncated due to duplex direction conflicts or nominal PUSCH transmissions crossing time slot boundaries. Figure 9Several such possible options for repeatedly mapping nominal PUSCH to actual PUSCH transports are shown, according to at least some implementation schemes.
[0112] As shown in the figure, in the first option 910, the mapping of which TRP the actual PUSCH transfer is transmitted to can be based on the nominal repeat. Therefore, in this method, the first actual PUSCH repeat can be transmitted to TRP1, the second and third actual PUSCH repeats can be transmitted to TRP2, the fourth and fifth actual PUSCH repeats can be transmitted to TRP1, and the sixth actual PUSCH repeat can be transmitted to TRP2.
[0113] In option 920 of the second example, the mapping of which TRP the actual PUSCH transfer is transmitted to can be based on the actual repeat. Therefore, in this method, the first actual PUSCH repeat can be transmitted to TRP1, the second actual PUSCH repeat can be transmitted to TRP2, the third actual PUSCH repeat can be transmitted to TRP1, the fourth actual PUSCH repeat can be transmitted to TRP2, the fifth actual PUSCH repeat can be transmitted to TRP1, and the sixth actual PUSCH repeat can be transmitted to TRP2.
[0114] In option 930 of the third example, the mapping of which TRP the actual PUSCH transmission is transmitted to can be based on the time slot in which the PUSCH transmission is performed. Therefore, in this method, the first actual PUSCH repeat, the second actual PUSCH repeat, and the third actual PUSCH repeat can be transmitted to TRP1, and the fourth actual PUSCH repeat, the fifth actual PUSCH repeat, and the sixth actual PUSCH repeat can be transmitted to TRP2.
[0115] For NCB PUSCH operations, at least according to some implementation schemes, multiple TRP PUSCH operations can be supported by configuring more than one SRS-ResourceSet. Figure 10 Aspects of this method according to some implementation schemes are illustrated. As shown in the figure, in the illustrated example, each SRS-ResourceSet is logically mapped to a TRP. Each SRS-ResourceSet can be configured with a different Non-Zero Power Channel State Information Reference Signal Resource Identifier (NZP-CSI-RS-ResourceId), each of which can be transmitted through a different TRP.
[0116] In some instances, for NCB PUSCH operations, when two SRS-ResourceSets are configured (each SRS-ResourceSet mapped to a TRP), two SRS resource indicator fields can be configured using 3GPP DCI formats 0_1 and 0_2. In this case, each SRS resource indicator field can be mapped to an SRS-ResourceSet using "nonCodebook".
[0117] As another possibility, for NCB PUSCH operations, it's possible to configure a single SRS-ResourceSet such that it contains more than one associated NZP-CSI-RS-ResourceId. In this case, it's possible to increase the number of configurable SRS resources per SRS-ResourceSet, for example, from four to eight. The mapping from each SRS-resource in the SRS-ResourceSet to its associated NZP-CSI-RS-ResourceId can be configured via RRC control signaling. Therefore, this configuration can also be used to support multi-TRP NCB PUSCH operations.
[0118] Further exemplary implementations are provided below.
[0119] One set of implementations 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, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and performing the uplink data transmission to the plurality of TRPs.
[0120] According to some implementation schemes, uplink data transmission configuration information configures 3GPP configuration to authorize Physical Uplink Shared Channel (PUSCH) transmission.
[0121] According to some implementation schemes, uplink data transmission configuration information configures 3GPP dynamically licensed Physical Uplink Shared Channel (PUSCH) transmission.
[0122] According to some implementation schemes, uplink data transmission configuration information configures 3GPP non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission.
[0123] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the multiple TRPs.
[0124] According to some implementation schemes, uplink data transmission configuration information includes information indicating 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 factor.
[0125] Another set of embodiments may include a wireless device comprising: an antenna; a radio component operatively coupled to the antenna; and a processor operatively coupled to the radio component; wherein the wireless device is configured to: establish a wireless link with a cellular base station; receive uplink data transmission configuration information, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and perform the uplink data transmission to the plurality of TRPs.
[0126] According to some implementation schemes, the uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, wherein the beam information for each TRP is indicated using one of the following: a separate beam configuration field for each TRP; or a single beam configuration field that includes a beam configuration index value associated with multiple beam configurations.
[0127] According to some implementation schemes, the uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, wherein the precoding information for each TRP is indicated by one of the following: a separate precoding configuration field for each TRP; or a single precoding configuration field that includes a precoding configuration index value associated with multiple precoding configurations.
[0128] According to some implementation schemes, the uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, wherein the path loss reference signal information for each TRP is indicated by one of the following: a separate path loss reference signal configuration field for each TRP; or a single path loss reference signal configuration field that includes a path loss reference signal configuration index value associated with multiple path loss reference signal configurations.
[0129] According to some implementation schemes, for each TRP associated with uplink transmission, the uplink data transmission configuration information is configured individually with one or more of the following: target received power information; or path loss compensation factor.
[0130] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, individual repeats are transmitted to the plurality of TRPs in an alternating manner.
[0131] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, repeating sequences are transmitted to the plurality of TRPs in an alternating manner.
[0132] According to some implementation schemes, uplink data transmission configuration information configures a recurring transmission mode for performing uplink data transmission to multiple TRPs, wherein, according to the transmission mode, transmission is performed for alternating TRPs in alternating time slots.
[0133] Another set of implementations 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 configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and performing the uplink data transmission to the plurality of TRPs.
[0134] According to some implementation schemes, uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeat of the transmission mode for uplink data transmission, wherein when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the method further includes: determining which of the plurality of TRPs to perform each actual uplink data transmission based on the nominal repetition of uplink data transmission and the transmission mode.
[0135] According to some implementation schemes, uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repetition of uplink data transmission in a transmission mode, wherein when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the method further includes: determining which of the plurality of TRPs to perform each actual uplink data transmission based on the transmission mode, according to the actual repetition of uplink data transmission.
[0136] According to some implementation schemes, uplink data transmission configuration information is configured to determine each repeated transmission mode for which of the plurality of TRPs to perform uplink data transmission, wherein when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the method further includes: determining, based on the time slot in which uplink data transmission is performed, which of the plurality of TRPs to perform each actual uplink data transmission according to the transmission mode.
[0137] According to some implementation schemes, uplink data transmission configuration information configures physical uplink shared channel (PUSCH) transmission based on non-codebook (NCB), wherein the uplink data transmission configuration information configures multiple sounding reference signal resource sets, wherein a non-zero power channel state information reference signal is used to configure each sounding reference signal resource set.
[0138] According to some implementation schemes, uplink data transmission configuration information configures physical uplink shared channel (PUSCH) transmission based on non-codebook (NCB), wherein the uplink data transmission configuration information configures a set of probe reference signal resources, wherein the set of probe reference signal resources is associated with a plurality of non-zero power channel state information reference signals, wherein a first portion of the probe reference signal resources of the set of probe reference signal resources is associated with a first TRP, and wherein a second portion of the probe reference signal resources of the set of probe reference signal resources is associated with a second TRP.
[0139] Another set of embodiments may include an apparatus comprising: 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, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and receive at least a portion of the uplink data transmission from the plurality of TRPs.
[0140] According to some implementation schemes, uplink data transmission configuration information configures 3GPP configuration to authorize Physical Uplink Shared Channel (PUSCH) transmission.
[0141] According to some implementation schemes, uplink data transmission configuration information configures 3GPP dynamically licensed Physical Uplink Shared Channel (PUSCH) transmission.
[0142] According to some implementation schemes, uplink data transmission configuration information configures 3GPP non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission.
[0143] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the multiple TRPs.
[0144] According to some implementation schemes, uplink data transmission configuration information includes information indicating 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 factor.
[0145] Another embodiment may include a cellular base station comprising: an antenna; a radio component operatively coupled to the antenna; and a processor operatively coupled to the radio component; wherein the cellular base station is configured to: establish a wireless link with a wireless device; provide uplink data transmission configuration information to the wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and receive at least a portion of the uplink data transmission from the plurality of TRPs.
[0146] According to some implementation schemes, the uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, wherein the beam information for each TRP is indicated using one of the following: a separate beam configuration field for each TRP; or a single beam configuration field that includes a beam configuration index value associated with multiple beam configurations.
[0147] According to some implementation schemes, the uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, wherein the precoding information for each TRP is indicated by one of the following: a separate precoding configuration field for each TRP; or a single precoding configuration field that includes a precoding configuration index value associated with multiple precoding configurations.
[0148] According to some implementation schemes, the uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, wherein the path loss reference signal information for each TRP is indicated by one of the following: a separate path loss reference signal configuration field for each TRP; or a single path loss reference signal configuration field that includes a path loss reference signal configuration index value associated with multiple path loss reference signal configurations.
[0149] According to some implementation schemes, for each TRP associated with uplink transmission, the uplink data transmission configuration information is configured individually with one or more of the following: target received power information; or path loss compensation factor.
[0150] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, individual repeats are transmitted to the plurality of TRPs in an alternating manner.
[0151] According to some implementation schemes, uplink data transmission configuration information configures a repeating transmission mode for performing uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, repeating sequences are transmitted to the plurality of TRPs in an alternating manner.
[0152] According to some implementation schemes, uplink data transmission configuration information configures a recurring transmission mode for performing uplink data transmission to multiple TRPs, wherein, according to the transmission mode, transmission is performed for alternating TRPs in alternating time slots.
[0153] Another set of embodiments may include a method comprising: a cellular base station: establishing a wireless link with a wireless device; providing uplink data transmission configuration information to the wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receivers (TRPs); and receiving at least a portion of the uplink data transmission from the plurality of TRPs.
[0154] According to some implementation schemes, uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeat of the transmission mode for uplink data transmission, wherein, according to the transmission mode, when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the nominal repetition of uplink data transmission determines which of the plurality of TRPs to perform each actual uplink data transmission for.
[0155] According to some implementation schemes, uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repetition of uplink data transmission in a transmission mode, wherein, according to the transmission mode, when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the actual repetition of uplink data transmission is used to determine which of the plurality of TRPs to perform each actual uplink data transmission in a transmission mode.
[0156] According to some implementation schemes, uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeated transmission mode of uplink data transmission, wherein, according to the transmission mode, when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the determination of which of the plurality of TRPs to perform each actual uplink data transmission is based on the time slot in which uplink data transmission is performed.
[0157] According to some implementation schemes, uplink data transmission configuration information configures at least a portion of the Physical Uplink Shared Channel (PUSCH) transmission based on non-codebook (NCB), wherein the uplink data transmission configuration information configures a non-zero power channel state information reference signal associated with a sounding reference signal resource set, wherein additional uplink data transmission configuration information is also provided to the wireless device, which configures an additional non-zero power channel state information reference signal associated with an additional sounding reference signal resource set.
[0158] According to some implementation schemes, uplink data transmission configuration information configures at least a portion of a Physical Uplink Shared Channel (PUSCH) transmission based on non-codebook (NCB), wherein the uplink data transmission configuration information configures a set of probe reference signal resources, wherein the set of probe reference signal resources is associated with a plurality of non-zero power channel state information reference signals, wherein a first portion of the probe reference signal resources of the set of probe reference signal resources is associated with a first TRP, and wherein a second portion of the probe reference signal resources of the set of probe reference signal resources is associated with a second TRP.
[0159] Another exemplary implementation may include a method comprising: having the device perform any or all of the foregoing examples.
[0160] Another exemplary embodiment may include a device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.
[0161] Another set of exemplary embodiments may include a non-transitory computer-accessible memory medium comprising program instructions that, when executed at the device, cause the device to implement any or all of the portions of any of the foregoing examples.
[0162] Another exemplary set of implementations may include a computer program comprising instructions for performing any or all portions of any of the examples described above.
[0163] Another exemplary set of embodiments may include an apparatus that includes means for performing any or all elements of any of the examples described above.
[0164] Another set of exemplary embodiments may include an apparatus that includes a processing element configured to cause the apparatus to perform any or all of the elements described in any of the foregoing examples.
[0165] Another set of exemplary embodiments may include a baseband processor configured to perform operations including any or all of the elements of any of the foregoing examples.
[0166] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
[0167] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.
[0168] Embodiments of this 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 ASICs. In still other embodiments, the subject matter may be implemented using one or more programmable hardware elements such as FPGAs.
[0169] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any method embodiments described herein, or any combination of such subsets.
[0170] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory elements), wherein the memory medium stores program instructions, and wherein the processor is configured to read from and execute the program instructions, wherein 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 or any combination of such subsets of any method embodiments described herein). The device may be implemented in any of a variety of forms.
[0171] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.
Claims
1. An apparatus for uplink data communication, comprising: A processor configured to perform operations when executing instructions stored in memory, the operations including: Uplink data transmission configuration information is provided to a wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receiver Points (TRPs), wherein the uplink data transmission configuration information configures a repetitive transmission mode for performing the uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, the plurality of TRPs performing uplink data transmission are alternately executed in a per-slot sequence mode, such that each time slot includes only one uplink data transmission opportunity for a corresponding TRP; and Receive at least a portion of the uplink data transmissions from the plurality of TRPs, The uplink data transmission mentioned above is the Physical Uplink Shared Channel (PUSCH) transmission.
2. The apparatus according to claim 1, The uplink data transmission configuration information configures 3GPP configuration authorization for PUSCH transmission.
3. The apparatus according to claim 1, The uplink data transmission configuration information configures 3GPP dynamic licensed PUSCH transmission.
4. The apparatus according to claim 1, The uplink data transmission configuration information configures 3GPP non-codebook-based PUSCH transmission.
5. A method for wireless communication, comprising: Receive uplink data transmission configuration information, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmission Receiving Points (TRPs), wherein the uplink data transmission configuration information configures a repetitive transmission mode for performing the uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, the plurality of TRPs performing uplink data transmission to them are alternately executed in a per-slot sequence mode, such that each time slot includes only a plurality of uplink data transmission opportunities for a corresponding TRP; as well as The uplink data transmission to the plurality of TRPs is performed. The uplink data transmission mentioned above is the Physical Uplink Shared Channel (PUSCH) transmission.
6. The method according to claim 5, The uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, wherein a single beam configuration field is used to indicate the beam information for each TRP, the single beam configuration field including a beam configuration index value associated with multiple beam configurations.
7. The method according to claim 5, The uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, wherein a single precoding configuration field is used to indicate the precoding information for each TRP, the single precoding configuration field including a precoding configuration index value associated with multiple precoding configurations.
8. The method according to claim 5, The uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, wherein a single path loss reference signal configuration field is used to indicate the path loss reference signal information for each TRP, the single path loss reference signal configuration field including a path loss reference signal configuration index value associated with multiple path loss reference signal configurations.
9. The method according to claim 5, The uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeated transmission pattern of the uplink data transmission for. When nominal uplink data transmission is truncated due to duplex conflicts or scheduling across time slot boundaries, the method further includes: Based on the actual repetition of the uplink data transmission, the transmission mode determines which of the plurality of TRPs each actual uplink data transmission should be performed for.
10. The method according to claim 5, The uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeated transmission pattern of the uplink data transmission for. When nominal uplink data transmission is truncated due to duplex conflicts or scheduling across time slot boundaries, the method further includes: Based on the time slot in which the uplink data transmission is performed, the transmission mode determines which of the plurality of TRPs each actual uplink data transmission should be performed for.
11. The method according to claim 5, The uplink data transmission configuration information configured is based on non-codebook (NCB) PUSCH transmission. The uplink data transmission configuration information configures a probe reference signal resource set, wherein the probe reference signal resource set is associated with multiple non-zero power channel state information reference signals (NZP-CSI-RS), wherein a first portion of the probe reference signal resources of the probe reference signal resource set is associated with a first TRP, and wherein a second portion of the probe reference signal resources of the probe reference signal resource set is associated with a second TRP.
12. A method performed by a cellular base station, comprising: Uplink data transmission configuration information is provided to a wireless device, wherein the uplink data transmission configuration information configures uplink data transmission to a plurality of Transmitter Receiver Points (TRPs), wherein the uplink data transmission configuration information configures a repetitive transmission mode for performing the uplink data transmission to the plurality of TRPs, wherein, according to the transmission mode, the plurality of TRPs performing uplink data transmission to them are alternately executed in a per-slot sequence mode, such that each time slot includes only a plurality of uplink data transmission opportunities for a corresponding TRP; as well as Receive at least a portion of the uplink data transmissions from the plurality of TRPs, The uplink data transmission mentioned above is the Physical Uplink Shared Channel (PUSCH) transmission.
13. The method according to claim 12, The uplink data transmission configuration information includes beam information for each TRP associated with the uplink transmission, wherein a single beam configuration field, including a beam configuration index value associated with multiple beam configurations, is used to indicate the beam information for each TRP.
14. The method according to claim 12, The uplink data transmission configuration information includes precoding information for each TRP associated with the uplink transmission, wherein a single precoding configuration field, including a precoding configuration index value associated with multiple precoding configurations, is used to indicate the precoding information for each TRP.
15. The method according to claim 12, The uplink data transmission configuration information includes path loss reference signal information for each TRP associated with the uplink transmission, wherein a single path loss reference signal configuration field, including a path loss reference signal configuration index value associated with multiple path loss reference signal configurations, is used to indicate the path loss reference signal information for each TRP.
16. The method according to claim 13, The uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeated transmission pattern of the uplink data transmission for. According to the transmission mode, when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the actual uplink data transmission is used to determine which of the plurality of TRPs should perform each actual uplink data transmission.
17. The method according to claim 13, The uplink data transmission configuration information is configured to determine which of the plurality of TRPs to perform each repeated transmission pattern of the uplink data transmission for. According to the transmission mode, when nominal uplink data transmission is truncated due to duplex conflict or scheduling across time slot boundaries, the determination of which TRP should perform each actual uplink data transmission for the plurality of TRPs is based on the time slot in which the uplink data transmission is performed.
18. The method according to claim 13, The uplink data transmission configuration information configured includes at least a portion of the non-codebook (NCB) PUSCH transmission. The uplink data transmission configuration information configures a probe reference signal resource set, the probe reference signal resource set is associated with multiple non-zero power channel state information reference signals, a first part of the probe reference signal resources of the probe reference signal resource set is associated with a first TRP, and a second part of the probe reference signal resources of the probe reference signal resource set is associated with a second TRP.
19. An apparatus for wireless communication, comprising: A processor configured to perform the method according to any one of claims 5-11 when executing instructions stored in memory.
20. The apparatus of claim 19, further comprising: A radio device operatively coupled to the processor.
Citation Information
Patent Citations
Method and apparatus for triggering power headroom reports
US20200100193A1
User terminal and wireless communication method
WO2019244207A1
Uplink transmission adaptation based on transmission configuration state
WO2019245689A1
SRS configuration for non-codebook based pusch transmission
WO2020093362A1