Power determination method for uplink transmission in mtrp wireless communications

Abstract

In traditional macrocell deployments, User Equipment (UE) communicates with a single Transmission Receiver Point (TRP) on the same cell for both downlink (DL) and uplink (UL) transmissions. However, to minimize both cost and interference (and improve UL transmission performance), dense deployment of UL Transmission Receiver Points (TRPs) is considered. Therefore, enhanced UL transmissions for multiple-input / multiple-output wireless communication are desired, especially in “asymmetric” scenarios, such as DL single-TRP (sTRP) / UL multiple-TRP (mTRP) wireless communication. To support UL-only TRPs, several issues need to be addressed, such as how the UE should perform UL power control for UL-only TRPs and how to account for scenarios where DL and UL transmissions from a given UE are associated with different TRPs. Solutions to these issues are disclosed, along with more efficient sounding reference signal (SRS) power control methods (especially when transmitting different sets of SRS resources to different TRPs).

Description

Technical Field

[0001] This application relates to wireless devices and wireless networks, including power control devices, circuits, and methods for multiple transmit receiver point (mTRP) transmission in wireless communication systems. Background Technology

[0002] 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 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 functionalities. 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-Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and Bluetooth. TM etc.

[0003] The increasing number of features and functionalities introduced into wireless communication devices has also generated a continuous demand for improvements in wireless communication and devices themselves. In addition to the aforementioned communication standards, there are wireless communication technologies under development to increase coverage and better serve the intended uses of wireless communication, including fifth-generation (5G) standards and new radio (NR) communication technologies. Therefore, there is a need to improve the areas supporting this development and design.

[0004] As an example, in a traditional macrocell deployment, user equipment (UE) devices (e.g., mobile phones) communicate with the same cell for both downlink (DL) and uplink (UL) transmissions. However, for UEs located at the cell edge, UL performance can be poor, for example, due to greater path loss and UE transmission power limitations. In contrast, small cell deployments can improve UE UL and DL performance by providing lower path loss, but such cell configurations may also have their own disadvantages, such as requiring a larger number of gNodeBs (gNBs) for network implementation and needing to manage more severe DL interference.

[0005] To minimize both cost and interference (and improve UL transmission performance), dense deployment of UL Transmitter Receiver Points (TRPs) can also be considered. In fact, one objective of 3GPP Release 19 is to further enhance UL transmissions for multiple-input / multiple-output (MIMO) wireless communications, particularly in the context of “asymmetric” wireless communication scenarios, such as DL single TRP (sTRP) / UL mTRP scenarios, and especially in-band and in-cell, non-co-located mTRP scenarios. Preferably, such enhancements can be implemented without changing existing cell definitions or defining new cell types (e.g., with “UL-only” cells), and the existing unified TCI framework can be reused for mTRPs, targeting both frequency ranges FR1 and FR2.

[0006] To support the concept of UL-only TRPs, several issues may need to be addressed, such as how the UE should perform UL power control for UL-only TRPs, and how to account for scenarios where DL and UL transmissions from a given UE are associated with different TRPs. Such scenarios may also require transmitting probe reference signals (SRS) to different TRPs for different purposes (e.g., codebook vs. non-codebook). Therefore, solutions to these various problems and more efficient SRS power control methods are needed, especially in scenarios where different sets of SRS resources are transmitted to different TRPs. Summary of the Invention

[0007] According to one or more aspects, a method for enhancing power control for transmission in a multiple transmit receiver point (mTRP) user equipment (UE) is disclosed, the method comprising: receiving a first configuration at the UE, the first configuration including at least a first power control parameter for a first transmit receiver point (TRP), wherein the first TRP is configured for uplink and downlink communication with the UE; receiving a second configuration at the UE, the second configuration including at least a second power control parameter for a second TRP, wherein the second TRP is configured for uplink communication only from the UE; and transmitting from the UE to at least the second TRP according to the at least second power control parameter.

[0008] According to some aspects, the at least second power control parameter includes a common power offset value to be applied during transmission over at least each of the following: the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Sound Reference Signal (SRS) channel.

[0009] According to other aspects, the at least second power control parameter includes: a first power offset value to be applied during transmission on the PUSCH; a second power offset value to be applied during transmission on the PUCCH; and a third power offset value to be applied during transmission on the SRS channel.

[0010] According to some aspects, including the second configuration of the at least second power control parameter, it is received via Radio Resource Control (RRC) signaling. According to some of these aspects, the at least second power control parameter includes a power offset parameter having an extended range (e.g., the range {-16-Δ, …,15}) relative to {-16, …,15} as defined in 3GPP Release 18, and wherein the value of Δ is predefined.

[0011] According to some aspects, the power control enhancement method may further include: receiving a first Transmission Configuration Indicator (TCI) state configuration at the UE, wherein the first TCI state is configured for uplink and downlink communication with the UE and is associated with first TCI state uplink power control parameters. According to some such aspects, the power control enhancement method may further include: receiving a second TCI state configuration at the UE, wherein the second TCI state is configured for uplink communication only with the UE and is associated with second TCI state uplink power control parameters. For example, the second TCI state uplink power control parameters include a common power offset value to be applied during transmissions on at least each of the following when the UE is configured to be in the second TCI state: PUSCH, PUCCH, and SRS channels.

[0012] According to other aspects, the at least second power control parameter includes a first plurality of power offset values ​​(e.g., received via RRC). According to some of these aspects, the power control enhancement method may further include updating at least a first power offset value among the first plurality of power offset values ​​via a media access control (MAC) control element (CE). For example, the MACCE may also include one or more of the following: an indication of an index to the updated power offset value; an indication of a new value for the updated power offset value.

[0013] According to some aspects, the power control enhancement method may further include: receiving, at the UE, an association at DCI format 2_3 of a first Transmission Power Control (TPC) command field with a first SRS resource set associated with the first TRP via RRC signaling. According to some such aspects, the power control enhancement method may further include: receiving, at the UE, an association at DCI format 2_3 of a second TPC command field with a second SRS resource set associated with the second TRP via RRC signaling.

[0014] According to some aspects, the method for enhancing power control may further include: receiving at the UE a DCI format 2_3 including a flag field indicating whether the TPC command in the DCI format 2_3 is to be applied to an uplink transmission associated with a first SRS resource set used by the first TRP or an uplink transmission associated with a second SRS resource set used by the second TRP.

[0015] According to other aspects, the power control enhancement method may further include: receiving, at the UE, via RRC signaling, an association between a first TPC command field in DCI format 2_3 and a first SRS resource set used by the first TRP, wherein the association between the first TPC command field and the first SRS resource set also includes an implicit association between a second TPC command field in DCI format 2_3 and a second SRS resource set used by the second TRP. For example, according to some of these aspects, if the first TPC command field has an index value k, then the second TPC command field has an index value k+1 (i.e., the second TPC command field uses the next available consecutive index value).

[0016] According to some aspects, the power control enhancement method may further include: receiving, at the UE, a first TPC command field in DCI format 2_3 via RRC signaling to an uplink transmission associated with each of the following: a first SRS resource set used by the first TRP; and a second SRS resource set used by the second TRP, wherein the determination of whether to apply the received TPC command to the uplink transmission associated with the first SRS resource set or the uplink transmission associated with the second SRS resource set is based at least in part on the index number of the time slot in which the TPC command in DCI format 2_3 is received.

[0017] According to other aspects, the power control enhancement method may further include: receiving, at the UE, via RRC signaling, an association between a first control resource set (CORESET) (or a first search space set) and a first SRS resource set used by the first TRP; and receiving, at the UE, via RRC signaling, an association between a second CORESET (or a second search space set) and a second SRS resource set used by the second TRP, wherein the determination of whether to apply the received TPC command to an uplink transmission associated with the first SRS resource set or an uplink transmission associated with the second SRS resource set is based at least in part on the index of the first CORESET (or the index of the first search space) in which a TPC command in the DCI format 2_3 is received.

[0018] The various methods and techniques outlined in this section can also be executed by a device, including: a receiver; a transmitter; and a processor configured to execute any of the various methods and techniques outlined herein. The various methods and techniques outlined in this section can also be stored as instructions on a non-transitory computer-readable medium, wherein these instructions, when executed, for example, by a baseband processor, cause the various methods and techniques outlined herein to be executed, for example, by a UE device.

[0019] 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

[0020] A better understanding of this subject matter can be obtained by considering the following detailed description of the various aspects in conjunction with the accompanying drawings:

[0021] Figure 1 An example wireless communication system is illustrated based on some aspects.

[0022] Figure 2 Another example of a wireless communication system based on some aspects is shown.

[0023] Figure 3 Example block diagrams of a UE based on some aspects are shown.

[0024] Figure 4 Example block diagrams of base stations (BS) based on some aspects are shown.

[0025] Figure 5A An exemplary macro cell deployment is illustrated according to some aspects, in which the UE communicates with a single TRP on the same cell for both uplink and downlink transmissions.

[0026] Figure 5B An exemplary dense UL cell deployment is illustrated according to some aspects, in which each UE can communicate with different cells for uplink and downlink transmissions.

[0027] Figure 6 An exemplary multi-TCI state open-loop power control (OLPC) parameter configuration process is illustrated based on some aspects.

[0028] Figure 7 Various mechanisms for updating power control parameters are illustrated based on several aspects.

[0029] Figure 8It is a flowchart that details a method for enhancing power control of mTRP transmission in a wireless communication system according to some aspects.

[0030] Although the features described herein may be subject to various modifications and alternatives, their specific aspects are shown 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 one to the specific forms disclosed, but rather 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

[0031] As mentioned above, one objective of 3GPP Release 19 is to further enhance UL MIMO transmissions, particularly in the context of “asymmetric” wireless communication scenarios, such as DL single TRP (sTRP) / UL mTRP scenarios, and especially in-band and intra-cell, non-co-located mTRP scenarios. To support the concept of UL-only TRPs, several issues may need to be addressed, such as how the UE should perform UL power control for UL-only TRPs, and how to account for scenarios where DL and UL transmissions from a given UE are associated with different TRPs. According to certain aspects of this disclosure, various methods can be considered for configuring (and updating) open-loop power control (OLPC) parameters for UL transmissions, particularly those toward UL-only TRPs.

[0032] In version 17 of the 3GPP NR specification, for SRS power control, a set of power control parameters can be configured for the SRS resource set, including several parameters such as: α parameter (i.e., a parameter used for partial or complete path loss compensation); P0 parameter (i.e., the target received power at the base station receiver); and pathlossReferenceRS parameter (i.e., a reference signal used for path loss estimation). Furthermore, special Transmission Power Control (TPC) commands for Closed-Loop Power Control (CLPC) can be indicated, for example, by DCI format 2_3.

[0033] Therefore, UL TRP scenarios (such as those mentioned above) may also require the transmission of probe reference signals (SRS) to different TRPs for different purposes (e.g., codebook and non-codebook). Consequently, more efficient SRS power control (and configuration) methods are needed, especially in scenarios where different sets of SRS resources are transmitted to different TRPs.

[0034] The following is an additional glossary that may be used in this disclosure.

[0035] Memory media – any device of any type of nontransitory memory device or storage device. The term “memory media” is intended to include mounting media (e.g., CD-ROM, floppy disk, or magnetic 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 (e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements). 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 the latter example, the second computer system may provide program instructions to the first computer for execution. The term “memory media” may include two or more memory media that may reside in different locations (e.g., in different computer systems connected via a network). Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0036] Carrier medium – such as memory media as described above, and physical transmission media, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0037] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can range from fine-grained (combinational logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "reconfigurable logic units."

[0038] User equipment (UE) (also known as “user equipment,” “UE device,” or “terminal”) – 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). ™ Based on Android ™ Telephones), portable gaming devices (e.g., Nintendo Switch) ™ Nintendo DS ™ PlayStation Vita ™ PlayStation Portable ™ Gameboy Advance™ iPhone ™ This includes laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument clusters, head-up displays (HUD) devices, on-board diagnostics (OBD) devices, dashboard moving equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or "smart" appliances, machine-type communication (MTC) devices, machine-to-machine (M2M) and Internet of Things (IoT) devices, etc. Generally speaking, the terms "UE," "UE device," "terminal," or "user equipment" can be broadly defined to encompass any electronic, computing, and / or telecommunications equipment (or combination of devices) that is easily transportable by a user (or vehicle) and capable of wireless communication.

[0039] 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 one location. A UE is an example of a wireless device.

[0040] Communication device – 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 one location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0041] Base station – The terms “base station,” “wireless base station,” or “wireless station” have the full range of their common meaning and include at least a wireless communication station installed in a fixed location and used for communication as part of a wireless telephone system or radio system. For example, if a base station is implemented in the context of LTE, it may alternatively be referred to as an “eNodeB” or “eNB.” If a base station is implemented in the context of 5G NR, it may alternatively be referred to as a “gNodeB” or “gNB.” Although certain aspects are described in the context of LTE or 5G NR, references to “eNB,” “gNB,” “nodeB,” “base station,” and “NB,” etc., may also refer to one or more wireless nodes serving a cell to provide wireless connectivity between user equipment and a generally wider network, and the concepts discussed are not limited to any particular wireless technology. Although certain aspects are described in the context of LTE or 5G NR, references to “eNB,” “gNB,” “nodeB,” “base station,” and “NB,” etc., are not intended to limit the concepts discussed herein to any particular wireless technology, and the concepts discussed can be applied to any wireless system.

[0042] Node – As used herein, the term “node” or “wireless node” can refer to one or more devices associated with a cell that provides a wireless connection between a user equipment and a typically wired network.

[0043] A processing element (or processor) – refers to a variety of elements or combinations of elements capable of performing the functions of a device, such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry (such as application-specific integrated circuits (ASICs)), programmable hardware elements (such as field-programmable gate arrays (FPGAs)), and any combination thereof.

[0044] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on the wireless protocol, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities and frequency band conditions). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels (e.g., different channels for uplink or downlink and / or different channels for different purposes, such as data and control information).

[0045] Frequency band - The term "frequency band" has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0046] "Configured as" – Various components can be described as being "configured as" to perform one or more tasks. In this context, "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 be a broad expression generally meaning "having 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.

[0047] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0048] Example wireless communication system

[0049] Now go to Figure 1 This illustrates a simplified example of a wireless communication system based on some aspects. It should be noted that... Figure 1 The system described herein is a non-limiting example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0050] As shown in the figure, the example wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0051] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (e.g., a “cellular base station”), and may include hardware that enables wireless communication with UEs 106A to 106N.

[0052] The communication area (or coverage area) of a base station may be referred to as a "cell". Base station 102A and UE 106 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 (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A, 5G NR, HSPA, and 3GPP2 CDMA2000. Note that if base station 102A is implemented in an LTE context, it may alternatively be referred to as an 'eNodeB' or 'eNB'. Note that if base station 102A is implemented in a 5G NR context, it may alternatively be referred to as a "gNodeB" or "gNB".

[0053] In some aspects, UE 106 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connectivity. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity Service (ProSe), or Device-to-Device (D2D) communication, sensor network, or IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connectivity. As an example, vehicle-to-everything (V2X) communication may utilize ProSe features using an SL interface to communicate directly between devices. The IoT UE may also perform background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0054] As shown in the figure, UE 106 (such as UE 106A and UE 106B) can directly exchange communication data via SL interface 108. SL interface 108 can be a PC5 interface, which includes one or more physical channels, including but not limited to the Physical Side Link Shared Channel (PSSCH), Physical Side Link Control Channel (PSCCH), Physical Side Link Broadcast Channel (PSBCH), and Physical Side Link Feedback Channel (PSFCH).

[0055] In a V2X scenario, one or more base stations in base station 102 may be roadside units (RSUs) or act as roadside units (RSUs). The term RSU can refer to any transport infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable radio node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Intelligent Transportation Systems (ITS) band to provide extremely low-latency communications required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the radio frequency circuitry in the computing device and the RSU may be encapsulated in a weather enclosure suitable for outdoor installation, and may include a network interface controller to provide wired connections (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0056] As shown in the figure, base station 102A can also be configured 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 possibilities). Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various telecommunications capabilities such as voice, SMS, and / or data services.

[0057] Base station 102A and other similar base stations (such as base stations 102B to 102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UEs 106A to 106N and similar devices over a geographical area via one or more cellular communication standards.

[0058] Therefore, although base station 102A can act as such Figure 1 The illustrated UEs 106A to 106N are "serving cells," but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B to 102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in Figure 1 Base stations 102A and 102B illustrated can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0059] In some respects, base station 102A may be a next-generation base station (e.g., a 5G New Radio (5G NR) base station or "gNB"). In some respects, the gNB may connect to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) / 5G core (5GC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. For example, base station 102A and one or more other base stations 102 may support joint transmission, enabling UE 106 to receive transmissions from multiple base stations (and / or multiple TRPs provided by the same base station). For example, as... Figure 1 As illustrated, both base station 102A and base station 102C are shown as serving UE 106A.

[0060] It should be noted that UE 106 may be able to communicate using multiple wireless communication standards. For example, in addition to at least one of the cellular communication protocols discussed in the above definition, UE 106 may also be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth and Wi-Fi pairs, etc.). If desired, UE 106 may also be configured, or alternatively, to communicate using one or more Global Navigation Satellite Systems (GNSS) (e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0061] like Figure 2As illustrated, in one or more embodiments, UE 106 can be a cellular communication-enabled device, such as a mobile phone, handheld device, computer, laptop, tablet, smartwatch or other wearable device or virtually any type of wireless device.

[0062] UE 106 may include a processor (processing element) configured to execute program instructions stored in memory. UE 106 may execute any aspect of the method described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include programmable hardware elements, such as any hardware component of an FPGA (Field Programmable Gate Array), integrated circuit, and / or various other possible hardware components configured to perform (e.g., independently or in combination) any aspect of the method described herein or any part of any aspect of the method described herein.

[0063] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some aspects, UE 106 may be configured to communicate using, for example, NR or LTE using at least some shared radio components. As an additional possibility, UE 106 may be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio component may be coupled to a single antenna or may be coupled to multiple antennas (e.g., for a multiple-input multiple-output (MIMO) configuration) for performing wireless communication. Generally, the radio component may include any combination of baseband processors, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, and amplifiers) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication technologies (such as those discussed above).

[0064] In some aspects, UE 106 may include separate transmission and / or reception chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therein. 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 used uniquely by a single wireless communication protocol. For example, UE 106 may include shared radio components for communicating using either LTE or 5G NR (or either LTE or 1xRTT, or either LTE or GSM, and various other possibilities), and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0065] In some respects, the downlink resource grid can be used for downlink transmissions from any of the base stations in base station 102 to UE 106, while uplink transmissions can utilize similar techniques. This grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. Such a time-frequency plane representation is standard practice for Orthogonal Frequency Division Multiplexing (OFDM) systems, making radio resource selection intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid may include multiple resource blocks, which describe the mapping from a specific physical channel to resource elements. Each resource block includes a set of resource elements. Such resource blocks are used to transport several different physical downlink channels.

[0066] The Physical Downlink Shared Channel (PDSCH) carries user data and higher-layer signaling to UE 106. The Physical Downlink Control Channel (PDCCH) carries information such as transmission format and resource allocation related to the PDSCH channel. It also informs UE 106 of transmission format, resource allocation, and HARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UE 102 within the cell) can be performed at any base station in base station 102 based on channel quality information fed back from any UE in UE 106. Downlink resource assignment information can be transmitted on the PDCCH used for (e.g., assigned to) each UE in the UE.

[0067] The PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH are first organized into quadruplets, which are then arranged using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE corresponds to a set of four physical resource elements (REGs) of nine. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the Downlink Control Information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8) can exist.

[0068] Example communication device

[0069] Figure 3 A simplified block diagram illustrating a communication device 106 according to some aspects is shown. Note that... Figure 3 The block diagram of the communication device is merely one example of possible communication devices. Depending on the aspects, among other devices, communication device 106 may be a UE device or terminal, mobile device or mobile station, wireless device or wireless station, desktop computer or computing device, mobile computing device (e.g., laptop, notebook, or portable computing device), tablet computer, and / or a combination of devices. As shown, communication device 106 may include a set of components configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, this set of components may be implemented as individual components or groups of components for various purposes. This set of components 200 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of communication device 106.

[0070] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some aspects, communication device 106 may include wired communication circuitry (not shown), such as a network interface card (e.g., for Ethernet connectivity).

[0071] Wireless communication circuitry 330 may be (e.g., communicatively grounded; directly or indirectly) coupled to one or more antennas, such as antenna 335 as shown in the figure (each of which may include an antenna panel). Wireless communication circuitry 230 may include cellular communication circuitry and / or short-to-medium range wireless communication circuitry, and may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a MIMO configuration.

[0072] In some aspects, as further described below, the cellular communication circuit 330 may include one or more receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for various radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some aspects, the cellular communication circuit 330 may include a single transmission chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT (e.g., LTE) and can communicate with a dedicated receive chain and a transmission chain shared with a second radio component. A second radio component may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmission chain. In some aspects, the second RAT is capable of operating at millimeter-wave frequencies. Because millimeter-wave systems operate at frequencies higher than those typically found in LTE systems, signals in the millimeter-wave frequency range are significantly attenuated due to environmental factors. To help address this attenuation problem, millimeter-wave systems typically utilize beamforming and include more antennas compared to LTE systems. These antennas can be organized into antenna arrays or panels consisting of individual antenna elements. These antenna arrays can be coupled to a radio link.

[0073] The communication device 106 may also include one or more user interface elements and / or be configured for use with one or more user interface elements.

[0074] The communication device 106 may also include one or more smart cards 345 (such as one or more Universal Integrated Circuit Cards (UICCs) 345), which include subscriber identity module (SIM) functionality.

[0075] As shown in the figure, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions of the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from the processor 302 and translate these addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310); and / or coupled to other circuitry or devices, such as the display circuit 304, wireless communication circuitry 330, connector I / F 320, and / or display 360. The MMU 340 may be configured to perform memory protection and page table translation or setup. In some aspects, the MMU 340 may be included as part of the processor 302.

[0076] As noted above, communication device 106 may be configured to communicate using wireless and / or wired communication circuitry. As described herein, communication device 106 may include hardware and software components for implementing any of the various features and techniques described herein. Processor 302 of communication device 106 may be configured to implement some or all of the features described herein (e.g., by executing program instructions stored on a memory medium). Alternatively (or additionally), processor 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). Alternatively (or additionally), in conjunction with one or more of other components 300, 304, 306, 310, 320, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0077] Furthermore, as described herein, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit and a second circuit, etc.) configured to perform the functions of processor 302.

[0078] Furthermore, as described herein, the wireless communication circuit 330 may include one or more processing elements. In other words, one or more processing elements may be included in the wireless communication circuit 330. Therefore, the wireless communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the wireless communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit and a second circuit, etc.) configured to perform the functions of the wireless communication circuit 330.

[0079] Example base station

[0080] Figure 4 An example block diagram of base station 102 is shown, illustrating some aspects. It should be noted that... Figure 4 The base station shown is a non-limiting example of a possible base station. As shown, base station 102 may include processor 304, which can execute program instructions for base station 102. Processor 404 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from processor 404 and translate these addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450); or coupled to other circuitry or devices.

[0081] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access rights as described above. Figure 1 Multiple devices (such as UE device 106) of the telephone network described herein.

[0082] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to couple 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 a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in addition to other UE devices served by the cellular service provider).

[0083] In some respects, base station 102 may be a next-generation base station (e.g., a 5G New Radio (5G NR) base station or a “gNB”). In such respects, base station 102 may connect to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) / 5G core (5GC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0084] Base station 102 may include at least one antenna 434 and possibly multiple antennas or antenna panels. At least one antenna 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 configured to communicate via various wireless communication standards, including 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, and Wi-Fi.

[0085] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. When base station 102 supports millimeter wave, the 5G NR radio component may be coupled to one or more millimeter wave antenna arrays or panels. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies, such as 5G NR and LTE, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.

[0086] Furthermore, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured to implement or support specific implementations of some or all of the methods described herein (e.g., by executing program instructions stored on a memory medium). Alternatively, 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 a combination thereof. Alternatively (or further), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of BS 102 may be configured to implement or support the implementation of some or all of the features described herein.

[0087] Furthermore, as described herein, processor 404 may include one or more processing elements. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit and a second circuit, etc.) configured to perform the functions of processor 404.

[0088] Furthermore, as described herein, radio component 430 may include one or more processing elements. Therefore, radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 430. Additionally, each integrated circuit may include circuitry (e.g., a first circuit and a second circuit, etc.) configured to perform the functions of radio component 430.

[0089] Enhanced power control for multi-TRP wireless communication

[0090] Now go to Figure 5A Based on several aspects, an exemplary macro cell deployment 500A is illustrated, in which a UE communicates with a single TRP on the same cell for both uplink and downlink transmissions. UEs 505A and 505B represent exemplary UEs that may be located near cell edge 508A. In deployment 500A, each of UEs 505A and 505B communicates with a single TRP (i.e., TRP 502A) on the same cell for both UL and DL transmissions. For example, UE 505A may communicate with UL / DL TRP 502A via UL beam 504A, and it may also receive DL transmissions from UL / DL TRP 502A via DL beam 506A. Similarly, UE 505B may communicate with UL / DL TRP 502A via UL beam 504B, and it may also receive DL transmissions from UL / DL TRP 502A via DL beam 506B.

[0091] As mentioned above, UL performance may be poor for UEs located at or near the cell edge of macro cell deployments (such as the 500A), for example, due to greater path loss and UE transmission power limitations. In contrast, small cell deployments can improve UL and DL performance of UEs by providing lower path loss, but such cell configurations may also have their own disadvantages, such as requiring a larger number of gNodeBs (gNBs) for network implementation and needing to manage more severe DL interference.

[0092] Therefore, to minimize both cost and interference (as well as improve UL transmission performance), dense deployment of UL Transmitter Receiver Points (TRPs) can also be considered. In fact, one of the goals of 3GPP Release 19 is to further enhance UL transmissions for multiple-input / multiple-output (MIMO) wireless communications, especially in the context of “asymmetric” wireless communication scenarios, such as DL single TRP (sTRP) / UL mTRP scenarios, and particularly in-band and intra-cell, non-co-located mTRP scenarios.

[0093] Next, turn to Figure 5B Based on several aspects, an exemplary dense UL cell deployment 500B is illustrated, in which each UE can communicate with different cells for uplink and downlink transmissions. UEs 505C and 505D represent exemplary UEs that may be located near cell edge 508B. In deployment 500B, each of UEs 505C and 505D communicates with a single TRP (i.e., TRP 502B) on the same cell for DL ​​transmissions, but communicates with different UL-only TRPs in the cell (e.g., TRP 502C for UE 505C and TRP 502D for UE 505D) for UL transmissions. For example, UE 505C may communicate for UL transmissions with UL-only TRP 502C via UL beam 504C, but it may receive DL transmissions from DL TRP 502B via DL beam 506C. Similarly, UE 505D can communicate via UL beam 504D with UL-only TRP 502D, but it can receive DL transmissions from DL TRP 502B via DL beam 506D. Each of the UL-only TRPs 504C / 504D can also have a data connection 510C / 510D back to TRP 502B.

[0094] As mentioned above, successfully supporting the use of UL-only TRPs (such as 504C / 504D) may require addressing several issues, such as how UE 505 should perform UL power control for UL-only TRPs (e.g., using a power offset different from the power offset the UE will use for DL / UL TRPs), and how to account for scenarios where DL and UL transmissions from a given UE are associated with different TRPs. Such scenarios may also require probe reference signals (SRS) to be transmitted toward different TRPs for different purposes (e.g., codebook transmissions versus non-codebook transmissions for UL, and antenna switching for DL).

[0095] Open-loop power control (OLPC) for UL TRP only

[0096] In traditional OLPC, there is no feedback from the UE to the base station or from the base station to the UE. For example, the base station may transmit the target received power (i.e., P0) at the gNB to the UE. The UE receives the target power and adjusts its transmission power accordingly based on this parameter and other path loss measurements and / or channel conditions.

[0097] According to certain aspects of this disclosure, various methods may be considered for configuring OLPC parameters for UL transmissions toward UL-only TRPs. For example, in some embodiments, separate CLPC parameters may be configured for UL transmissions of the UE toward a first DL / UL TRP (TRP#1) and a second UL-only TRP (TRP#2). In particular, according to some specific implementations, one or more new information elements (IEs) (e.g., P0_offset IE) may be added to the legacy version 17 OLPC configuration to indicate power offset values.

[0098] According to the first option, a common offset IE (e.g., "P0_offset") can be introduced and applied to all uplink channels toward any UL-only TRP, i.e., including the PUSCH / PUCCH and SRS channels. According to the second option, separate power offset IEs can be introduced for one or more uplink channels. For example, in one implementation, three offset IEs can be introduced: "P0_offset_PUSCH", "P0_offset_PUCCH", and "P0_offset_SRS", and applied to UL transmissions toward the PUSCH, PUCCH, and SRS channels, respectively.

[0099] In some specific implementations of this kind, the UE can P 0,PUSCH / PUCCH / SRS,b,f,c The value is determined as the sum of the value indicated by the traditional "p0_r17" IE value and the newly introduced power offset value (e.g., "p0_offset-r19") (if a power offset value has already been configured), where P 0,PUSCH / PUCCH / SRS,b,f,c These are parameters used for uplink power control and essentially represent the target received power of PUSCH / PUCCH / SRS, where parameter "b" is the index for activating the UL BWP, parameter "c" is the cell index, and parameter "f" is the carrier index of cell "c".

[0100] In other specific implementations, the range of available “P0” values ​​for UE-specific PUSCH / PUCCH / SRS UL transmissions can be extended from the {-16, …, 15} range as defined in Release 18. For example, it can be alternatively extended to the range {-16-Δ, …, 15}, where the value of Δ can be predefined and hard-coded in the specification.

[0101] In other specific implementations, the UE can be configured with separate DL / UL TCI state modes. For example, if two TRPs operate for a given cell, one TRP can be designated as TRP#1 and the other as TRP#2 for this example. In such an example, the UE can be configured with a joint TCI state mode for TRP#1, while the UE can be configured with a separate TCI state mode for communicating with TRP#2. The difference between the "joint" and "separate" TCI state modes in this example lies in the number of TCI states applied to communication with the TRP. In the case of the "joint" TCI state mode, a single TCI state is applied to both DL and UL communication. However, in the case of the "separate" TCI state mode, two TCI states are applied, i.e., one for DL ​​communication and another for UL communication. Furthermore, RRC signaling can be used to associate the UL TCI state with a specific uplink power control ID (e.g., "ul-powercontrolId"). In such a specific implementation, the UE can then expect a UL TCI state toward UL TRP only to be associated with an “ul-powercontrol” IE consisting of at least the aforementioned newly defined “p0_offset-r19” IE value, wherein the “ul-powercontrol” IE is identified by the value of “ul-powercontrolId” associated with the UL TCI state.

[0102] In another specific implementation, a new common offset IE (e.g., 'P0_offset') may be added to the UL TCI state configuration (e.g., TCI-UL-State-r18) via RRC signaling, for example.

[0103] Uplink TCI status configuration

[0104] Depending on the TCI state configured for the UE, the UE can use different SSBs for path loss measurement and / or channel condition awareness. Therefore, power control enhancement techniques are needed for multi-TCI state / mTRP UL transmission. Depending on several aspects, each TCI state can be independently configured with a different set of power control parameters, including at least one of the following: an α parameter (for partial or full path loss compensation); a P0 parameter (i.e., the target received power at the base station receiver); a pathlossReferenceRS parameter (a reference signal for path loss estimation); and a new P0_offset parameter (i.e., the amount by which the UE adjusts the UL transmission power).

[0105] Now go to Figure 6Based on several aspects, an exemplary multi-TCI state open-loop power control (OLPC) parameter configuration procedure 600 is illustrated. In the exemplary procedure 600, it is assumed that a UE 605 located near a cell edge 608 including both UL / DL TRP 602A and UL TRP 602B only is configured for separate DL / UL unified TCI state operation.

[0106] Specifically, as shown in Table 612, the UE 605 in this example has been configured with four different possible UL TCI states: TCI state #0 (610A), TCI state #1 (610B), TCI state #2 (610C), and TCI state #3 (610D). As shown in Example 600, TCI state #1 (610B) is intended for UL transmissions toward TRP 602A (604A) (and DL transmissions from TRP 602A (606A)). As shown in more detail in Table 614B, because UL TCI state #1 is intended to use the same TRP for both DL and UL links, it is not necessary to configure a separate “P0_offset” IE value in the OLPC power control set.

[0107] However, as shown in Example 600, TCI state #2 (610C) is intended for use only with UL transmissions (604B) toward TRP 602B. Therefore, as shown in more detail in Table 614C, because UL TCI state #2 is intended for use with UL-only TRPs, the “P0_offset” IE value 616 is configured in the OLPC power control set. In this example, the “P0_offset” IE is configured to compensate for the PL difference between the measurement taken on SSB #6 from TRP 602A and the UL transmission toward TRP 602B. Referring again to the settings for TCI state #2 in Table 614C, the P0_new of the assumed PUSCH transmission in this example will be calculated as: P0 + P0_offset = -60 - 30 = -90 dB, and the UL transmission power will be adjusted accordingly. As can be understood, using such a power offset can have the beneficial effect of minimizing interference to neighboring cells, because the UE will apply a power offset (e.g., -30dB) to at least the UL TRP, instead of transmitting at full power to both TRPs.

[0108] Mechanism for rapidly updating power control parameters

[0109] According to certain aspects of this disclosure, various methods may be considered to perform rapid updates to the values ​​of the aforementioned new P0_offset power configuration parameters. For example, in one implementation, the UE may be configured, for instance, via RRC signaling, to have a list including multiple “P0_offset” values ​​(e.g., 16, 32, or 64 candidate power offset values). In some such implementations, the “P0_offset” list may be created at least in part based on measurements taken on SRS resources in an SRS resource set where its “use” is set to “beam management”.

[0110] In other specific implementations, for example, to avoid additional RRC signaling overhead, new forms of Media Access Control (MAC) control elements (CEs) can be introduced to allow for rapid updates of the value used for power offset, for example, when one (or both) of the ULTCI states of two TRPs are updated. Such a MAC CE can be identified by an identifier (e.g., a logical channel ID) in its MAC subheader. Such a MAC CE can have a fixed size and can have at least the following fields, defined as follows: P0_offset Identity (i.e., a field indicating the P0_offset ID of the addressed P0_offset); P0_offset value (i.e., a field indicating the value of the updated P0_offset).

[0111] As mentioned above, depending on some specific implementation, there may be a fixed number of P0_offsets available, such as 64. This means that 8 bits will be needed to address and identify which of the 64 candidate values ​​(e.g., 64 candidate active beam pairs) is updated in a given fast update operation.

[0112] Closed-loop power control (CLPC) for enhanced SRS transmission power control

[0113] Closed-loop power control is a mechanism that allows a UE to control the power of its PUSCH (or PUCCH or SRS) channel while communicating with a base station (i.e., connecting). For example, by using TPC commands (e.g., transmitted in DCI format 2_3), the base station can instruct the UE how much its transmission power should decrease or increase. For instance, a "cumulative" TPC mode can be used, where the UE uses memory to track its previous power state and then increases (or decreases) its power state based on the latest value received in the TPC command. As another example, an "absolute" TPC mode can be used, where the UE is provided with the total power value to be used (and there is no need to recall or modify previously stored power states).

[0114] Based on some aspects disclosed herein, TPC commands can also be applied in scenarios where the UE uses multiple SRS resource sets, for example, when the UE is configured for mTRP wireless communication. Now turn to... Figure 7 Various mechanisms for updating power control parameters are illustrated, based on several aspects.

[0115] For option 700A, RRC signals can be used to associate two TPC command fields in DCI format 2_3 with two SRS resource sets associated with two TRPs. For example, as shown in option 700A, a first SRS resource set 7041 used by a first DL / UL TRP can be associated with a first TPC command field 7021 in DCI format 2_3 via RRC signaling, and a second SRS resource set 7042 used by a second UL-only TRP can be associated with a second TPC command field 7024 in DCI format 2_3 via RRC signaling. It should be understood that this pairing of TRPs and their corresponding association with specific TPC command fields is merely illustrative, and other TPC command fields (e.g., 7022 or 7023) can also be associated with specific SRS sets if needed.

[0116] As a second option 700B, a new block field 710 is illustrated for TPC command 706, which can be applied to a UL carrier having both DL / UL TRPs and UL TRPs only. This also includes a new flag field 708, such as a 1-bit flag field, which can be appended to the existing (2-bit?) TPC command field. Flag field 708 can be used to indicate which TRP a given TPC command is applied to. In the illustrated example, a simple scheme can be adopted where a value of "0" in flag field 708 indicates that TPC command 706 is applied to a first SRS resource set 7041 used by the DL / UL TRP, and a value of "1" in flag field 708 indicates that TPC command 706 is applied to a second SRS resource set 7042 used by the UL TRP only.

[0117] As another example, option 700C illustrates a scenario where a first TPC command field (e.g., 7021) (e.g., a field with index value k) can be configured using RRC signals to work with a first SRS resource set 7041 used by the DL / UL TRP. According to option 700C, a second TPC command field with index value k+1 can be implicitly assigned using the first TPC command field with index value k to work with a second SRS resource set 7042 used only by the UL TRP. In this way, only a single TPC command field association needs to be notified via RRC signaling, while other associations can be implicitly derived according to a predetermined scheme (such as the scheme described above).

[0118] As yet another example, option 700D illustrates a scenario where a first TPC command field (e.g., a TPC field with index "k") is configured (e.g., via RRC signaling) and shared by both the DL / UL TRP and the UL-only TRP. Subsequently, according to some specific implementations, the application of the received TPC command to an uplink transmission associated with the first SRS resource set used by the DL / UL TRP or to an uplink transmission associated with the second SRS resource set used by the UL-only TRP is determined, at least in part, based on the index number of the time slot in which the TPC command in DCI format 2_3 is received. For example, if DCI format 2_3 is detected in a time slot with an even index number (e.g., DCI format 2_37141 received in time slot index #6 7121), the TPC field in DCI 2_3 is applied to the first SRS resource set used by the DL / UL TRP. Otherwise, if DCI format 2_3 is detected in a slot with an odd index number (e.g., DCI format 2_3 7142 received in slot index #9 7124), then that DCI format is applied to a second SRS resource set used only by the UL TRP. It should be understood that this pairing of TRP with even / odd slot index numbers is merely exemplary, and other schemes (e.g., involving slot index ranges, specific slot indices, etc.) can also be used to associate specific slots with specific SRS resource sets if needed.

[0119] As a final example, option 700E illustrates a scenario where a control resource set (CORESET) (or the search space associated with a CORESET) is configured for DCI format 2_3 monitoring. For example, the UE may receive, for instance, via RRC signaling, an association between a first CORESET (or first search space set) 7201) and a first SRS resource set used by a first DL / UL TRP, and another association between a second CORESET (or second search space set) 7202 and a second SRS resource set used by a second UL-only TRP, wherein the determination of whether to apply the received TPC command to an uplink transmission associated with the first SRS resource set or an uplink transmission associated with the second SRS resource set is based at least in part on the index of the first CORESET index or the index of the first search space index in which a TPC command in DCI format 2_3 is received. In another example, instead of receiving the association between the CORESET / search space and the TRP via RRC signaling, implicit rules can be defined in the 3GPP specification, such as CORESET / search spaces with “even” IDs for DL / UL TRPs and CORESET / search spaces with “odd” IDs for UL-only TRPs, etc.

[0120] An exemplary method for implementing enhanced power control for uplink mTRP transmission

[0121] Now go to Figure 8 The flowchart details a method 800 for enhanced power control of mTRP transmission in a wireless communication system according to several aspects. First, at block 802, method 800 may receive a first configuration at a user equipment (UE) including at least a first power control parameter for a first transmit receive point (TRP), wherein the first TRP is configured for uplink and downlink communication with the UE.

[0122] Next, in block 804, method 800 may receive a second configuration at the UE (e.g., via RRC signaling), the second configuration including at least a second power control parameter for a second TRP, wherein the second TRP is configured to be used only for uplink communication from the UE.

[0123] In block 806, method 800 may transmit from the UE to at least a second TRP according to at least a second power control parameter. For example, in block 808, the at least second power control parameter may include a common power offset value to be applied during transmission over at least each of the following: the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Sounding Reference Signal (SRS) channel. Alternatively, in block 810, the at least second power control parameter may include: a first power offset value to be applied during transmission over the PUSCH; a second power offset value to be applied during transmission over the PUCCH; and a third power offset value to be applied during transmission over the SRS channel.

[0124] Additional notes

[0125] The use of the connective term "and / or" is intended to represent all possible alternative forms of the connective "and" and the connective "or". For example, the statement "configuration of A and / or B" includes the meanings of the statements "configuration of A and B" and "configuration of A or B".

[0126] 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.

[0127] Various aspects of this disclosure can be implemented in any of a variety of forms. For example, some aspects may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. Other aspects may be implemented using one or more custom-designed hardware devices such as ASICs. Other aspects may be implemented using one or more programmable hardware elements such as FPGAs.

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

[0129] In some aspects, the apparatus (e.g., UE 106, BS 102) may be configured to include a processor (or a set of processors) and a memory medium storing program instructions, wherein the processor is configured to read from and execute the program instructions, wherein the program instructions are executable to implement any one of the various method aspects described herein (or any combination of the method aspects described herein, or any subset of any method aspects described herein, or any combination of such subsets). The apparatus may be implemented in any of the various forms.

[0130] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the foregoing disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for enhancing power control in multi-transmitter-receiver point (mTRP) user equipment (UE) transmission, the method comprising: A first configuration is received at the UE, the first configuration including at least a first power control parameter for a first transmit receive point (TRP), wherein the first TRP is configured for uplink and downlink communication with the UE; A second configuration is received at the UE, the second configuration including at least a second power control parameter for a second TRP, wherein the second TRP is configured to be used only for uplink communication from the UE; as well as Transmission is made from the UE to at least the second TRP according to the at least second power control parameters.

2. The method of claim 1, wherein the at least second power control parameter includes a common power offset value to be applied during transmission on at least each of the following: the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Sound Reference Signal (SRS) channel.

3. The method of claim 1, wherein the at least second power control parameter comprises: The first power offset value to be applied during transmission on the PUSCH; The second power offset value to be applied during transmission on the PUCCH; as well as A third power offset value to be applied during transmission on the SRS channel.

4. The method of claim 1, wherein the second configuration of the at least second power control parameter is received via radio resource control (RRC) signaling.

5. The method of claim 4, wherein the at least second power control parameter includes a power offset parameter having an extended range relative to {-16, …,15} as defined in 3GPP Release 18.

6. The method of claim 5, wherein the extended range includes the range {-16-Δ, …,15}, and wherein the value of Δ is predefined.

7. The method according to claim 1, further comprising: The UE receives a first Transmission Configuration Indicator (TCI) state configuration, wherein the first TCI state is configured for uplink and downlink communication with the UE and is associated with the first TCI state uplink power control parameters.

8. The method according to claim 7, further comprising: The UE receives a second TCI state configuration, wherein the second TCI state is configured to be used only for uplink communication with the UE and is associated with the second TCI state uplink power control parameters.

9. The method of claim 8, wherein the second TCI state uplink power control parameters include a common power offset value to be applied during transmission on at least each of the following when the UE is configured to be in the second TCI state: the PUSCH, the PUCCH, and the SRS channel.

10. The method of claim 4, wherein the at least second power control parameter includes a first plurality of power offset values.

11. The method according to claim 10, further comprising: At least the first power offset value among the plurality of power offset values ​​is updated via a media access control (MAC) control element (CE).

12. The method of claim 11, wherein the MAC CE further comprises one or more of the following: An indication of the index of the updated power offset value; or Indication of the new value for the updated power offset value.

13. The method according to claim 1, further comprising: At the UE, the association between the first Transmission Power Control (TPC) command field in DCI format 2_3 and the first SRS resource set associated with the first TRP is received via RRC signaling.

14. The method according to claim 13, further comprising: At the UE, the association between the second TPC command field in the DCI format 2_3 and the second SRS resource set associated with the second TRP is received via RRC signaling.

15. The method according to claim 1, further comprising: The UE receives DCI format 2_3 including a flag field, the flag field indicating whether the TPC command in DCI format 2_3 is to be applied to an uplink transmission associated with a first SRS resource set used by the first TRP or an uplink transmission associated with a second SRS resource set used by the second TRP.

16. The method according to claim 1, further comprising: At the UE, the association between the first TPC command field in DCI format 2_3 and the first SRS resource set used by the first TRP is received via RRC signaling. The association between the first TPC command field and the first SRS resource set also includes the implicit association between the second TPC command field in the DCI format 2_3 and the second SRS resource set used by the second TRP.

17. The method of claim 16, wherein the first TPC command field has an index value k, and wherein the second TPC command field has an index value k+1.

18. The method according to claim 1, further comprising: At the UE, the first TPC command field in DCI format 2_3 is received via RRC signaling to the association of uplink transmissions associated with each of the following: a first SRS resource set used by the first TRP; and a second SRS resource set used by the second TRP. The determination of whether to apply the received TPC command to an uplink transmission associated with a first SRS resource set or an uplink transmission associated with a second SRS resource set is based at least in part on the index number of the time slot in which the TPC command in the DCI format 2_3 is received.

19. The method according to claim 1, further comprising: At the UE, the association between the first control resource set (CORESET) or the first search space set and the first SRS resource set used by the first TRP is received via RRC signaling. as well as At the UE, the association between the second CORESET or the second search space set and the second SRS resource set used by the second TRP is received via RRC signaling. The determination of whether to apply the received TPC command to an uplink transmission associated with a first SRS resource set or an uplink transmission associated with a second SRS resource set is based at least in part on the index of the first CORESET in which the TPC command in the DCI format 2_3 is received.

20. A user equipment, the user equipment comprising: Receiver; Transmitter; And a processor configured to perform any of the methods according to claims 1 to 19.

21. A baseband processor configured to cause a user equipment to perform any one of the methods according to claims 1 to 19.

Images