CN117426075A

CN117426075A - Multi-point communication coordination mechanism and operation method thereof

Info

Publication number: CN117426075A
Application number: CN202280035253.5A
Authority: CN
Inventors: 郭力
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-05-17
Filing date: 2022-05-16
Publication date: 2024-01-19
Also published as: WO2022243847A2; WO2022243847A3

Abstract

Systems and methods for dynamically coordinating power allocation in wireless signals are disclosed. In some embodiments, a communication system dynamically configures power levels of one or more communication signals in a multiple Transmit Receive Point (TRP) environment. The power level may be used to coordinate a single TRP transmission scheme and/or a multi TRP or joint transmission scheme for communication with the mobile/terminal device.

Description

Multi-point communication coordination mechanism and operation method thereof

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No. 63/189,590 filed 5/17 at 2021, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications, and in particular, to a wireless communication method and apparatus.

Background

The rapid development of computing technology has increased the need for data communications. The increasing demand in turn drives further developments in communication technology. One such technological advance corresponds to multi-point joint communication using multiple points/devices to communicate with one device. However, the rapid evolution further increases the demand for higher throughput, which requires additional coordination and corresponding complexity between multiple transmission points.

Drawings

In order to more clearly describe the technical solutions in the embodiments of the present technology, the drawings are briefly described below. The figures illustrate only some aspects or embodiments of the present technology and those of ordinary skill in the art may still derive other figures from these figures without inventive effort.

Fig. 1 illustrates a wireless communication system in accordance with one or more embodiments of the present technology.

Figure 2 illustrates an example multicast scheme in accordance with one or more embodiments of the present technology.

Fig. 3A, 3B, and 3C illustrate example multi-point coordination schemes in accordance with one or more implementations of the present technology.

FIG. 4 illustrates a flow diagram of an example method in accordance with one or more embodiments of the present technology.

Fig. 5 shows a schematic block diagram of a terminal device according to one or more embodiments of the present disclosure.

Fig. 6 shows a schematic block diagram of a system chip in accordance with one or more embodiments of the present disclosure.

Fig. 7 shows a schematic block diagram of a communication device in accordance with one or more embodiments of the present disclosure.

Detailed Description

Technical solutions in one or more embodiments of the present technology are described below. The wireless communication system may coordinate and configure multipoint joint communications to/from the terminal devices. For example, a system may include multiple transmission-reception points (TRPs) connected to each other for coordination by a backhaul link (e.g., of the ideal type or the non-ideal type). However, conventional approaches fail to specify a particular approach for coordinating some aspects of joint communications. For example, when downlink control information (downlink control information, DCI) indicates a physical uplink shared channel (physical uplink shared channel, PUSCH) and/or a physical uplink control channel (physical uplink control channel, PUCCH) transmission to a single TRP or multiple TRPs, the conventional method fails to clarify how to apply the transmit power command (transmit power command, TPC). Thus, the expected response of the terminal device may be unclear, which may lead to the terminal device applying an incorrect configuration and compromising or degrading the uplink transmission performance.

Rather, embodiments of the present technology include one or more mechanisms for separately configuring communications between a terminal device and a plurality of TRPs using target configuration data. The system may use/apply TPC between the terminal device and the TRP to individually control the power used for communication from the terminal device to the different TRP. For example, the terminal device may be provided with two or more TPC command fields in the DCI, two or more sets of sounding reference signals (sounding reference signal, SRS), two or more SRS resource indicator (SRS resource indicator, SRI) fields in the DCI, or a combination thereof to control the power allocated for scheduled PUCCH and/or PUSCH communications. Thus, various embodiments of the present technology may enable a communication system to apply proper or accurate closed loop power control (closed loop power control) to communications using a single TRP and/or multiple TRPs.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the presently described technology. In other embodiments, the techniques described herein may be practiced without these specific details. In other instances, well-known features, such as specific functions or routines, have not been described in detail to avoid unnecessarily obscuring the present technology. Reference in the specification to "an embodiment," "one embodiment," etc., means that a particular feature, structure, material, or characteristic described is included in at least one embodiment of the described technology. Thus, the appearances of such phrases in various places throughout this specification are not necessarily all referring to the same embodiment. On the other hand, such references are not necessarily mutually exclusive. Furthermore, the particular features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that the various embodiments shown in the figures are merely illustrative representations and are not necessarily drawn to scale.

For clarity, several details describing structures or processes that are well known and often associated with communication systems and subsystems, but may unnecessarily obscure some important aspects of the disclosed technology are not set forth in the following description. Furthermore, while the following disclosure sets forth several embodiments of different aspects of the present technology, several other embodiments may have different configurations or components than those described in this section. Thus, the disclosed technology may have other embodiments with additional elements or several elements not described below.

Many of the embodiments or aspects of the technology described below may take the form of computer or processor-executable instructions, including routines executed by a programmable computer or processor. Those skilled in the relevant art will appreciate that the described techniques may be practiced on computer or processor systems other than those shown and described below. The techniques described herein may be implemented in a special purpose computer or data processor that is specially programmed, configured, or constructed to perform one or more of the computer-executable instructions described below. Thus, the terms "computer" and "processor" are generally used herein to refer to any data processor. The information processed by these computers and processors may be presented on any suitable display medium, including a liquid crystal display (liquid crystal display, LCD). Instructions for performing computer or processor-executable tasks may be stored in or on any suitable computer-readable medium, including hardware, firmware, or a combination of hardware and firmware. The instructions may be embodied in any suitable memory device, including for example a flash drive and/or other suitable medium.

The terms "coupled" and "connected," along with their derivatives, may be used herein to describe structural relationships between components. It should be understood that these terms are not intended as synonyms for each other. In contrast, in particular embodiments, "connected" may be used to indicate that two or more elements are in direct contact with each other. Unless otherwise apparent from the context, the term "coupled" may be used to indicate that two or more elements are in direct or indirect (with other intervening elements between the elements) contact with each other and/or that two or more elements cooperate or interact with each other (e.g., as in a causal relationship, e.g., for signaling/receiving or for function calls). The term "and/or" in this specification is merely used to describe the association of associated objects, and indicates that there may be three relationships, for example, a and/or B may indicate the following three cases: a alone, a and B both exist, and B alone. Furthermore, the character "/" in this specification generally indicates an or relationship between associated objects.

Suitable environment

Fig. 1 illustrates a wireless communication system 100 in accordance with one or more embodiments of the present technology. As shown in fig. 1, a wireless communication system 100 may include a network device 110. Network device 110 may include circuitry to provide communication coverage for a particular geographic area. Some examples of network devices 110 may include: base transceiver stations (base transceiver station, BTSs), node bs (nodebs, NB), evolved nodebs (enbs or enodebs), next generation nodebs (next generation nodebs, gNB or gNode bs), wireless fidelity (wireless fidelity, wi-Fi) Access Points (APs). Additional examples of network device 110 may include a relay station, an access point, an in-vehicle device, a wearable device, and so forth. Network device 110 may include other wireless connection devices for a communication network, such as: global system for mobile communications (global system for mobile communication, GSM) networks, code division multiple access (code division multiple access, CDMA) networks, wideband CDMA (WCDMA) networks, long Term Evolution (LTE) networks, cloud radio access networks (cloud radio access network, CRAN), institute of electrical and electronics engineers (institute of electrical and electronics engineer, IEEE) 802.11 based networks (e.g., wiFi networks), internet of things (Internet of things, ioT) networks, device-to-device (D2D) networks, next generation networks (e.g., fifth generation (5G) networks), future evolution public land mobile networks (public land mobile network, PLMNs), and the like. Alternatively, the 5G system or network may also be referred to as a New Radio (NR) system or network. Network device 110 may also include TRP.

Additionally or alternatively, the wireless communication system 100 may include a terminal device 120. The terminal device 120 may be an end user device for facilitating wireless communications. Terminal device 120 may be configured to wirelessly connect to network device 110 (via, for example, a wireless channel) according to one or more corresponding communication protocols/standards. The terminal device 120 may be mobile or stationary. The terminal device 120 may be an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. Some examples of terminal device 120 may include: a cellular phone, a smart phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or another processing device connected to a wireless modem, an in-vehicle device, a wearable device, an IoT device, a terminal device in a future 5G network, a terminal device in a future evolved PLMN, etc.

Communications between network device 110 and terminal device 120 may experience variations as the corresponding signals travel through the medium or channel between the devices. In other words, the received signal (Y) may be different from the transmitted signal (X) due to the effects (e.g., fading, interference, doppler effect, delay, noise, etc.) through the channel (H).

For illustration, fig. 1 shows a wireless communication system 100 via a network device 110 and a terminal device 120. However, it should be understood that the wireless communication system 100 may include additional devices/other devices, such as additional instances of the network device 110 and/or the terminal device 120, network controllers, mobility management entities, and the like.

Multipoint joint communication

Fig. 2 illustrates an example multicast scheme 200 in accordance with one or more embodiments of the present technology. The communication system 100 may use multiple TRPs (e.g., instances of the network device 110 (e.g., the gNB)) to communicate with one terminal device 120. For example, the first TRP 202 and the second TRP 204 may be coupled to a terminal device. The first TRP 202 and the second TRP 204 may be coupled to each other via a backhaul link. Thus, multiple TRPs may communicate with each other to coordinate joint communications with terminal device 120.

For context, the backhaul link may be ideal or non-ideal. When the TRP is connected via an ideal backhaul link, the TRP may exchange dynamic scheduling information (e.g., dynamic scheduling information about physical downlink shared channel (physical downlink shared channel, PDSCH) communications) with short delays. Accordingly, TRP may coordinate downlink transmission of each transmission using an ideal backhaul link. In contrast, when TRPs are connected via non-ideal backhaul links, information exchanged between the TRPs may have a relatively large delay. Thus, TRP may coordinate communications using semi-static or static schemes.

In non-coherent joint transmission, different TRPs may independently use different physical downlink control channels (physical downlink control channel, PDCCH) to schedule PDSCH transmissions. Each TRP may send one DCI to schedule one PDSCH transmission. Thus, different TRPs may schedule the corresponding PDSCH in the same or different slots. Thus, two different PDSCH transmissions from different TRPs may overlap entirely or partially in PDSCH resource allocation. To support multi-TRP based non-coherent joint transmission, communication system 100 may request terminal device 120 to receive PDCCHs from multiple TRPs. For each PDSCH transmission, the terminal device 120 may provide feedback information (e.g., hybrid ARQ acknowledgements (hybrid ARQ acknowledge, HARQ-ACKs)) to the network. In multi-TRP communication, the terminal device 120 may provide feedback for each PDSCH transmission to the corresponding TRP. The terminal device 120 may also receive PDSCH transmissions from one TRP and provide corresponding feedback to another TRP (e.g., a designated TRP).

Fig. 3A and 3B illustrate example multi-point coordination schemes 300a and 300B, respectively, in accordance with one or more embodiments of the present technology. The coordination schemes 300a and 300b may represent different combinations of the above-described feedback.

For the coordination schemes 300a and 300b, the terminal device 120 may receive or establish PDSCH based on non-coherent joint transmissions from the first TRP 202 and the second TRP 204. For example, the first TRP 202 may send a first configuration command (e.g., DCI 1) to schedule transmission of a first communication (PDSCH 1) to the terminal device 120. Further, the second TRP 204 may send a second configuration command (e.g., DCI 2) to schedule transmission of a second communication (PDSCH 2) to the terminal device 120.

Thus, terminal device 102 may receive and decode separate configuration commands (e.g., DCI1 and DCI 2). The terminal device 120 may use separate decoding results of separate configuration commands to receive and decode corresponding communications (e.g., PDSCH1 and PDSCH2, respectively). In other words, the terminal device 102 may (1) receive and decode the PDSCH1 using the decoding result of the DCI1 and (2) receive and decode the PDSCH2 using the decoding result of the DCI 2.

In some implementations, the plurality of TRPs may use different sets of control resources (control resource set, CORESET) and search spaces to send configuration commands (DCI) for scheduling communications (e.g., PDSCH transmissions). In this way, the communication system 100 or network may configure multiple CORESETs and search spaces. Each TRP may be associated with one or more CORESETs and related search spaces, which may be used to send corresponding configuration commands to terminal device 120. The terminal device 120 may be requested to decode a configuration command in CORESET associated with one or more (e.g., any, or all) TRPs to obtain scheduling information.

The terminal device 102 may provide feedback information back to one or more TRPs, e.g., using HARQ-ACK/NACK. The feedback information may describe the quality of the received information (e.g., PDSCH communications), the corresponding channel, and/or the processing success/failure associated with the received information. For the example scheme 300a, the terminal device 120 may report separate feedback information to each TRP. In other words, the terminal device 120 may report (1) the first feedback (ACK/NACK 1) to the first TRP 202 and (2) the second feedback (ACK/NACK 2) to the second TRP 204. For the example scheme 300b, the terminal device 120 reports common feedback information for two or all communications (e.g., PDSCH1 and PDSCH 2) to one/specified TRP. The example scheme 300b may correspond to an ideal backhaul link between the first TRP 202 and the second TRP 204.

In some embodiments, the communication system 100 may use higher layer parameters (e.g., cosetoolindex) to indicate whether multi-TRP transmission is supported in the serving cell. In one serving cell, if multi-TRP transmission is supported, CORESET in the serving cell may be configured with one of two different values of the higher layer parameter coresetpoolndex. For example, when the terminal device 120 is (1) provided with a high-layer parameter corespoolindex of 0, or (2) not provided with a high-layer parameter for some corefets and provided with a high-layer parameter corespoolindex of 1 for other corefets, multi-TRP transmission of the terminal device 120 may be supported in one bandwidth part (BWP) of the serving cell.

In an active BWP of the serving cell, the communication system 100 may configure the terminal device 120 with one of a plurality of feedback modes. For example, the terminal device 120 may be configured with a joint HARQ-ACK feedback mode and a separate HARQ-ACK feedback mode. In the joint HARQ-ACK feedback mode, HARQ-ACK bits from PDSCH of all TRPs may be multiplexed in the HARQ codebook. The terminal device 120 may report the HARQ-ACK codebook to the network in one PUCCH or PUSCH. In the separate HARQ-ACK feedback mode, the terminal device 120 may separately generate a HARQ-ACK codebook for the PDSCH of each TRP. The terminal device 120 may report each HARQ-ACK codebook separately in different PUCCH or PUSCH transmissions. In the separate HARQ-ACK transmission mode, the terminal device 120 may assume that PUCCHs carrying HARQ-ACK bits for different TRPs are separated in the time domain and do not overlap.

The communication system 100 may support a variety of methods for repeated transmissions (e.g., for slot-based repetition and minislot repetition). For slot-based repetition (e.g., type a repetition), the number K of repetitions of PUSCH transmission may be provided to terminal device 120, and the same symbol allocation may be applied over K consecutive slots. PUSCH may be limited to a single transmission layer. Thus, the terminal device 120 may apply the same symbol allocation in each slot to repeat the TB (transport block) over K consecutive slots.

For minislot repetition (e.g., type B repetition), the number K of repetitions of PUSCH transmission may be provided to terminal device 120. Accordingly, the terminal device 120 may transmit K PUSCH repetitions in consecutive symbols. At the position ofThe start symbol or first symbol relative to the start (e.g. start) of the slot can be described as +.>The end/end time slot of the nominal repetition can be described as +.>And the corresponding end symbol may be described asItem K _s The time slot at which PUSCH transmission starts can be described, while the term +.>The number of symbols per slot may be described.

For minislot repetition, the terminal device 120 may first determine an invalid symbol according to one or more predefined conditions. After determining invalid symbols for repeated transmissions for each of the K nominal repetitions, the remaining symbols may be considered potentially valid symbols. When the number of potential valid symbols of the nominal repetition is greater than zero, the nominal repetition may include one or more actual repetitions having a contiguous set of potential valid symbols that may be used within the slot. The actual repetition may be omitted according to the conditions defined by the slot format determination. In addition, the terminal device 120 may determine a redundancy version for the nth actual repetition according to the following table.

Communication power control

In conventional schemes, the system may coordinate communications using one or more aspects of joint transmission. For example, legacy systems may indicate DCI via which PUSCH transmissions and PUCCH transmissions to a single TRP or multiple TRPs are indicated. Thus, the legacy scheme may use DCI to dynamically identify whether a transmission is to a single TRP or multiple TRPs. However, the conventional scheme fails to specify details about the application of TPC. Therefore, the expected behavior of the legacy UE is undefined and unclear, and the legacy UE may transmit PUCCH and PUSCH in an erroneous setting, thereby compromising uplink transmission performance.

In contrast, the communication system 100 (via, for example, the multi-point communication scheme 200) may use one or more messages to individually configure communications between the terminal device 120 and one or more TRPs 202/204 using the target configuration data. Referring back to fig. 2, the communication system 100 may use/apply separate configurations (e.g., the first communication configuration 212 and the second communication configuration 214) to separately control the power (e.g., UL power) for communicating from the terminal device 120 to different TRPs. For example, the terminal device 120 may control the first UL power using a first communication configuration 212 (e.g., TPC, DCI, or a combination thereof) to the first TRP 202, e.g., when transmitting information from the terminal device 120 to the first TRP 202. Further, for example, when transmitting information from the terminal device 120 to the second TRP 204, the terminal device 120 may control the second UL power using a second communication configuration 214 (e.g., TPC, DCI, or a combination thereof) to the second TRP 204.

Fig. 3C illustrates an example embodiment of a communication configuration. The first communication configuration 212 and/or the second communication configuration 214 may include a command field 302 for controlling the power allocated for scheduled PUCCH and/or PUSCH communications.

In some implementations, a configuration command 312 may be provided to the terminal device 120, the configuration command 312 having at least a first command 314 and a second command 316 (e.g., examples of the command field 302) of DCI format 1_1 or DCI format 1_2. The first command 314 and/or the second command 316 may correspond to a TCP command for a scheduled PUCCH. In other words, the terminal device 120 may apply the first command 314 and/or the second command 316 on the scheduled PUCCH transmission according to a communication scheme (e.g., whether the communication scheme is single point communication using a single TRP or joint communication using multiple TRPs).

As an example application of TPC commands, if a PUCCH transmission scheduled by DCI format 1_1 or DCI format 1_2 is sent to a single TRP, terminal device 120 may be requested to apply a first command 314 (e.g., a first TPC command) and/or a second command 316 (e.g., a second TPC command) on the PUCCH transmission. The communication system 100 may transmit one DCI format 1_1 or 1_2 to the terminal device 120 (via, for example, TRP (e.g., gNB)). DCI format 1_1 or 1_2 may indicate two TCP command fields: a first TPC command for the scheduled PUCCH and a second TPC command for the scheduled PUCCH. DCI format 1_1 or 1_2 may indicate a first PUCCH resource. If the first PUCCH resource is transmitted to one TRP, the terminal device 120 may apply the first TPC command and/or the second TPC command for the scheduled PUCCH on the PUCCH transmission on the scheduled first PUCCH resource. The first PUCCH resource may be configured or indicated by one PUCCH spatial relationship information to indicate that the first PUCCH resource is to be transmitted to a single TRP. Additionally or alternatively, the first PUCCH resource may be configured, linked, or indicated by one power control parameter set to indicate a single TRP.

In other example embodiments, the terminal device 120 may be requested to apply the first command 314 on the PUCCH sent to the first TRP 202 and the second command 316 on the PUCCH sent to the second TRP 204. In other words, if a PUCCH transmission scheduled by DCI format 1_1 or DCI format 1_2 is sent to the first TRP 202, the terminal device 120 may be requested to apply the first command 314 (e.g., TPC command) on the PUCCH transmission. If a PUCCH transmission scheduled by DCI format 1_1 or DCI format 1_2 is sent to the second TRP 204, the terminal device 120 may be requested to apply a second command 316 (e.g., TPC command) on the PUCCH transmission. In other example embodiments, if a PUCCH transmission scheduled by DCI format 1_1 or DCI format 1_2 is transmitted to two TRPs, terminal device 120 may be requested to (1) apply first command 314 on all PUCCH transmission occasions transmitted to first TRP 202 and/or (2) apply second TPC command on all PUCCH transmission occasions transmitted to second TRP 204.

For PUSCH coordination, the terminal device 120 may be provided with a configuration command 312 having a first command 314 and a second command 316 of DCI format 0_1 or DCI format 0_2. The first command 314 and/or the second command 316 may correspond to a TCP command for a scheduled PUSCH. In other words, the terminal device 120 may apply the first command 314 and/or the second command 316 on the scheduled PUSCH transmission.

As an example application of TPC commands, if a PUSCH transmission scheduled by DCI format 0_1 or DCI format 0_2 is sent to a single TRP, the terminal device 120 may be requested to apply a first command 314 (e.g., a first TPC command) and/or a second command 316 (e.g., a second TPC command) on the PUSCH transmission. The communication system 100 (via, for example, TRP (e.g., gNB)) may schedule the terminal device 120 for PUSCH transmission in DCI format 0_1 or 0_2. The terminal device may be configured with a reference set 322 (e.g., SRS set), the reference set 322 comprising a first set 324 and a second set 326 for PUSCH transmission. The PUSCH transmission may be a codebook-based transmission or a non-codebook-based transmission. DCI format 0_1 or 0_2 may indicate two TCP command fields: a first TPC command for a scheduled PUSCH and a second TPC command for a scheduled PUSCH. DCI format 0_1 or 0_2 may schedule PUSCH transmission corresponding to first set 324 or second set 326. In other words, DCI format 0_1 or 0_2 may schedule PUSCH transmission corresponding to a single TRP.

The terminal device 120 may determine TPC commands for the scheduled PUSCH transmission in various ways. In one example, when DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to one SRS resource set, terminal device 120 may apply the first TPC command and/or the second TPC command to the scheduled PUSCH. In another example, when DCI format 0_1 or 0_2 corresponds to first set 324, terminal device 120 may apply first command 314. In other words, if DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to the first SRS resource set, the terminal device 120 may apply the first TPC command to the scheduled PUSCH. Further, when DCI format 0_1 or 0_2 corresponds to second set 326, terminal device 120 may apply second command 316. In other words, if DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to the second SRS resource set, terminal device 120 may apply the second TPC command to the scheduled PUSCH.

In some embodiments, communication system 100 may use an SRS Resource Indicator (SRI) field to coordinate/schedule PUSCH. For example, the terminal device 120 may be provided with a configuration command 312 of DCI format 0_1 or 0_2, the configuration command 312 having a first field 334 (e.g., a first SRI field) and a second field 336 (e.g., a second SRI field) and a first command 314 and a second command 316 for a scheduled PUSCH. The communication system 100 may use the configuration command 312 to schedule PUSCH transmissions corresponding to the first field 334 or the second field 336. In other words, DCI format 0_1 or 0_2 may schedule PUSCH transmission corresponding to a single TRP.

The terminal device 120 may determine TPC commands for the scheduled PUSCH transmission in various ways. In one example, when DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to one SRI field, terminal device 120 may apply the first TPC command and/or the second TPC command to the scheduled PUSCH. In another example, when DCI format 0_1 or 0_2 corresponds to first field 334, terminal device 120 may apply first command 314. In other words, if DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to the first SRI field, the terminal device 120 may apply the first TPC command to the scheduled PUSCH. Further, when DCI format 0_1 or 0_2 corresponds to the second field 336, the terminal device 120 may apply the second command 316. In other words, if DCI format 0_1 or 0_2 indicates PUSCH transmission corresponding to the second SRI field, the terminal device 120 may apply the second TPC command to the scheduled PUSCH.

Example operation flow

FIG. 4 is a flow diagram of an example method 400 in accordance with one or more implementations of the present technology. The method 400 may be implemented by a system, such as the communication system 100 of fig. 1 and/or one or more devices therein, such as the terminal device 120 of fig. 1 and/or the network device 110 of fig. 1. Method 400 is used to dynamically control communication (e.g., UL) power. The method 400 may correspond to one or more aspects of the control scheme described above.

The method 400 may include: at block 402, one or more communications (e.g., UL communications, such as PUSCH and/or PUCCH) are coordinated. At block 404, the communication system 100 may determine a power level designated for communication with a plurality of TRPs. For example, the communication system 100 may determine a power level of UL transmissions from one or more UEs using a single TRP communication scheme based on the UE location. Communication system 100 may determine a power level that may reduce interference caused by UL transmissions. Further, the communication system 100 may determine a power level of UL transmissions from one/each UE using the multi-TRP communication scheme. Communication system 100 may determine a power level and/or other signal characteristics (e.g., SRS set selection, SRI selection, etc.) applicable to UL transmissions to first TRP 202 and/or second TRP 204.

At block 406, the communication system 100 may transmit the determined power level and/or other signal characteristics to a TRP communicatively coupled to the target UE. The communication system 100 may use the backhaul link to transmit the determined coordination information to different TRPs (e.g., the first TRP 202 and/or the second TRP 204). At block 408, the communication system 100 may generate commands, such as the first command 314 of fig. 3C and/or the second command 316 of fig. 3C (e.g., TPC commands), based on the determined power level. At block 410, the communication system 100 may determine communication settings (e.g., SRS/SRI settings) based on other signal characteristics.

At block 412, the communication system 100 may transmit a configuration command (e.g., the first communication configuration 212 of fig. 2 and/or the second communication configuration 214 of fig. 2). The communication system 100 may transmit a configuration command from one or more TRPs (e.g., the first TRP 202 and/or the second TRP 204). The communication system 100 may transmit a configuration command to coordinate a single TRP communication scheme or a multi TRP communication scheme for communication with the target UE.

Communication system 100 may include configuration commands and/or fields corresponding to the determined power level and/or SRS/SRI settings. For example, as shown in block 414, communication system 100 may transmit TCP commands to and receive TCP commands at a target UE. The communication system 100 may include the first command 314 and/or the second command 316 in the transmitted configuration command. The TCP command may be transmitted via a DCI format (e.g., DCI format 1_1 or 1_2 for PUCCH, DCI format 0_1 or 0_2 for PUSCH, etc.). In some implementations, the first command 314 can be associated with a first TRP 202 and the second command 316 can be associated with a second TRP 204. Thus, communication system 100 may use (1) first command 314 to control/coordinate the power level of PUCCH/PUSCH to first TRP 202 and (2) second command 316 to control/coordinate the power level of PUCCH/PUSCH to second TRP 204.

As indicated by block 416, communication system 100 may also transmit other settings (e.g., SRS/SRI settings). For example, the communication system 100 may use the first field 334 of fig. 3C, the second field 336 of fig. 3C, etc. to indicate the SRI to the UE for use during UL communication. Further, communication system 100 can include SRS set indications for first set 324 of fig. 3C, second set 326 of fig. 3C, and so forth. The communication system 100 may transmit other settings to coordinate PUSCH communications, for example, for a single TRP communication scheme.

At block 422, the communication system 100 (at, for example, the terminal device 120 (e.g., target UE)) may apply the command/setting to the scheduled UL communication. For example, the UE may apply TCP commands as described above. Upon application of the command/setting, the UE may process the received configuration command to determine the communication parameters. For example, the UE may process TCP commands and/or other parameters to determine PUCCH scheduling and/or PUSCH scheduling. Further, the UE may process the TCP command and/or other parameters to determine whether the scheduled UL communication corresponds to a single TRP communication scheme or a multi TRP communication scheme. As a result of the processing, the UE may effectively determine a power level for coordinated UL transmissions, as indicated by block 424. Thus, the UE may control the power for the scheduled PUCCH/PUSCH transmission according to the first TPC command, the second TPC command, the SRS set indication, the SRI indication, or a combination thereof as described above.

At block 432, the communication system 100 may communicate in accordance with the determined power level. For example, the terminal device 120 may transmit at least one scheduled message (e.g., UL message, such as PUCCH and/or PUSCH) to one or more TRPs (e.g., the first TRP 202 and/or the second TRP 204) according to the configuration command and the processing result described above. The power level of the transmission may correspond to the first TPC and/or the second TPC, SRS set indication, SRI field, etc.

Example devices and systems

Fig. 5-7 illustrate example devices and systems that include or incorporate the dynamic power control mechanisms described above. Fig. 5 is a schematic block diagram of a terminal device 500 (e.g., an example of terminal device 120 of fig. 1) in accordance with one or more embodiments of the present technique. As shown in fig. 5, the terminal device 500 includes a processing unit 510 (e.g., DSP, CPU, GPU, etc.) and a memory 520. The processing unit 510 may be used to implement instructions corresponding to the method 400 of fig. 4 and/or other aspects of the embodiments described above.

Fig. 6 is a schematic block diagram of a system chip 600 (e.g., components within terminal device 120 of fig. 1 and/or network device 110 of fig. 1) in accordance with one or more embodiments of the present technology. The system chip 600 in fig. 6 includes an input interface 601, an output interface 602, a processor 603, and a memory 604 (e.g., a non-transitory computer readable medium) that may be connected by internal communication connection lines, wherein the processor 603 is configured to execute code in the memory 604. Memory 604 may include code corresponding to method 400 of fig. 4 and/or other aspects of the embodiments described above. Thus, the processor 603 may implement the method 400 and/or other aspects of the above-described embodiments.

Fig. 7 is a schematic block diagram of a communication device 700 (e.g., an example of terminal device 120 of fig. 1 and/or network device 110 of fig. 1) in accordance with one or more embodiments of the present technology. The communication device 700 may include a processor 710 and a memory 720. The memory 720 may store program codes, and the processor 710 may execute the program codes stored in the memory 720. Memory 720 may include code corresponding to method 400 of fig. 4 and/or other aspects of the above-described embodiments. Accordingly, processor 710 may implement method 400 and/or other aspects of the above-described embodiments.

It should be appreciated that the processor in embodiments of the present technology may be an integrated circuit chip and have signal processing capabilities. During implementation, the steps in the foregoing methods may be implemented by integrated logic circuits using hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a discrete gate or transistor logic device, and discrete hardware components. Methods, steps, and logic blocks disclosed in embodiments of the present technology may be implemented or performed. A general purpose processor may be a microprocessor, or the processor may alternatively be any conventional processor or the like. The steps in the methods disclosed with reference to embodiments of the present technology may be performed or accomplished directly by a decoding processor implemented as hardware, or by using a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, or another well-known storage medium in the art. The storage medium is located in memory and the processor reads the information in the memory and, in combination with its hardware, performs the steps in the method described above.

It will be appreciated that the memory in embodiments of the present technology may be or include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), or flash memory. The volatile memory may be random-access memory (RAM) and used as an external cache. For purposes of illustration and not limitation, many forms of RAM may be used, and RAM is, for example, static random-access memory (SRAM), dynamic random-access memory (DRAM), synchronous dynamic random-access memory (synchronous dynamic random-access memory, SDRAM), double data rate synchronous dynamic random-access memory (doubledata rate synchronous dynamic random-access memory, DDR SDRAM), enhanced synchronous dynamic random-access memory (enhanced synchronous dynamic random-access memory, ESDRAM), synchronous link dynamic random-access memory (synchronous link dynamic random-access memory, SLDRAM), and direct Rambus random-access memory (direct Rambus random-access memory, DR). It should be noted that the memories in the systems and methods described herein are intended to comprise, without being limited to, these memories and any other suitable types of memories.

Example

1. A method for operating a communication device, the method comprising:

transmitting configuration commands for coordinating a single Transmit Receive Point (TRP) communication scheme or a multi-TRP communication scheme, wherein the configuration commands include at least a first command (e.g., a first TPC command) and a second command (e.g., a second TPC command);

at least one scheduled message is transmitted between a User Equipment (UE) and one or more TRPs according to the configuration command, wherein power in the at least one scheduled message is processed according to the first command and/or the second command.

2. The method of example 1, or a combination of parts thereof, wherein:

transmitting the configuration command includes receiving the configuration command at the UE, wherein the first command and the second command correspond to according to a Downlink Control Information (DCI) format; and

transmitting the at least one scheduled message includes transmitting an Uplink (UL) message from the UE to the first TRP and/or the second TRP.

3. The method of any one of examples 1 or 2, or a combination thereof, wherein:

the configuration command includes the first TPC command and the second TPC command of DCI format 1_1 or DCI format 1_2; and

The UL message includes a scheduled Physical Uplink Control Channel (PUCCH) transmission configured by the UE based on applying the first TPC command and/or the second TPC command on the scheduled PUCCH transmission.

4. The method of any one of examples 1 to 3, or a combination thereof, further comprising:

determining that the configuration command corresponds to the single TRP communication scheme; and

based on the determination, controlling power for the scheduled PUCCH transmission according to the first TPC command and/or the second TPC command;

wherein transmitting the at least one scheduled message comprises: the scheduled PUCCH transmission is transmitted to the first TRP according to the controlled power and without communicating with the second TRP.

5. The method of any one of examples 1 to 4, or a combination thereof, wherein:

the configuration commands include (1) the first TPC command associated with the first TRP and (2) the second TPC command associated with the second TRP, wherein the first TPC command and the second TPC command represent the multi-TRP communication scheme coordinated between the first TRP and the second TRP using a backhaul channel; and

Transmitting the at least one scheduled message includes: (1) Transmitting a first PUCCH transmission to the first TRP at a first power level corresponding to the first TPC, and (2) transmitting a second PUCCH transmission to the second TRP at a first power level corresponding to the first TPC.

6. The method of any one of examples 1 to 5, or a combination thereof, wherein:

the UE is configured to: communicating with the first TRP and/or the second TRP using at least one of a first set of Sounding Reference Signals (SRS) and a second set of SRS;

the configuration command includes the first TPC command and the second TPC command of DCI format 0_1 or DCI format 0_2; and

the UL message includes a scheduled Physical Uplink Shared Channel (PUSCH) transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUSCH transmission and according to the SRS set used.

7. The method of any one of examples 1 to 6, or a combination thereof, further comprising:

determining that the configuration command indicates a selected SRS set, wherein the selected SRS set includes the SRS set used; and

based on the determination, controlling power for the scheduled PUSCH transmission in accordance with the first TPC command and/or the second TPC command;

Wherein transmitting the at least one scheduled message comprises: the scheduled PUSCH transmission is sent to the first TRP according to the controlled power and without communicating with the second TRP.

8. The method of any one of examples 1 to 7, or a combination thereof, wherein:

the SRS sets used include one of (1) the first SRS set corresponding to the first TPC and (2) the second SRS set corresponding to the second TPC indicated by the communication command; and

the scheduled PUSCH transmission is configured by applying the first TPC command or the second TPC command corresponding to the SRS set used.

9. The method of any one of examples 1 to 8, or a combination thereof, wherein:

the configuration commands include (1) the first and second TPC commands of DCI format 0_1 or DCI format 0_2 and (2) at least first and second Sounding Reference Signal (SRS) indicator (SRI) fields; and

the UL message includes a scheduled Physical Uplink Shared Channel (PUSCH) transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUSCH transmission and according to the first SRI field and/or the second SRI field in the configuration command.

10. The method of any one of examples 1 to 9, or a combination thereof, further comprising:

determining that the configuration command indicates at least one of the first SRI field and the second SRI field; and

11. The method of any one of examples 1 to 10, or a combination thereof, wherein:

the configuration command specifies one of (1) the first SRI field corresponding to the first TPC and (2) the second SRI field corresponding to the second TPC; and

the scheduled PUSCH transmission is configured by applying the first TPC command or the second TPC command corresponding to the specified SRI field.

12. The method of any one of examples 1 to 11, or a combination thereof, wherein:

transmitting the configuration command includes sending the communication command to the UE; and

transmitting the at least one scheduled message includes receiving an Uplink (UL) message from the UE at the first TRP and/or the second TRP.

13. The method of any one of examples 1 to 12, or a combination thereof, further comprising:

coordinating the single TRP communication scheme or the multi TRP communication scheme for communication with the UE using a backhaul link; and

wherein transmitting the configuration command comprises generating the first TPC command and/or the second TPC command in accordance with the coordination.

13. The method of any one of examples 1 to 12, or a combination thereof, wherein transmitting the communication command comprises transmitting the first TPC command and the second TPC command in DCI format 1_1 or DCI format 1_2 for coordinating a Physical Uplink Control Channel (PUCCH), or transmitting the first TPC command and the second TPC command in DCI format 0_1 or DCI format 0_2 for coordinating a Physical Uplink Shared Channel (PUSCH).

14. A wireless communication device (e.g., a network-side device, such as a gNB, node device/function, TRP, etc.), comprising:

an antenna for wireless transmission of one or more information or signals as described above;

processing circuitry coupled to the antenna and to perform the method according to any of examples 1-13, any complementary process according to examples 1-13, any portion according to examples 1-13, or a combination thereof.

15. A wireless communication device (e.g., a terminal/mobile device, such as a UE), comprising:

Conclusion(s)

The above detailed description of various examples of the disclosed technology is not intended to be exhaustive or to limit the disclosed technology to the precise form disclosed above. Although specific examples of the disclosed technology are described above for illustrative purposes, various equivalent modifications are possible within the scope of the described technology, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps in a different order, or employ systems having such blocks, and may delete, move, add, subdivide, combine, and/or modify some processes or blocks to provide alternatives or sub-combinations. Each of these processes or blocks may be implemented in a variety of different ways. Further, although processes or blocks are sometimes shown as being performed in series, these processes or blocks may alternatively be performed or implemented in parallel, or may be performed at different times. Furthermore, any specific numbers mentioned herein are merely examples; alternative embodiments may employ different values or ranges.

These and other changes can be made to the techniques disclosed in accordance with the above detailed description. While the above detailed description describes certain examples of the disclosed technology, as well as the best mode contemplated, the disclosed technology can be practiced in many ways, regardless of the degree of detail presented in the foregoing description. The details of the system may vary significantly in its specific embodiments while still being encompassed by the technology disclosed herein. As noted above, particular terminology used in describing certain features or aspects of the disclosed technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosed technology with which that terminology is associated. The invention, therefore, is not to be restricted except in the spirit of the appended claims. In general, the terms used in the following claims should not be construed to limit the disclosed technology to the specific examples disclosed in the specification, unless the above detailed description section explicitly defines such terms.

Those of ordinary skill in the art will appreciate that the examples, elements, and algorithm steps described in connection with the embodiments disclosed herein may be implemented by electronic hardware or combinations of computer software and electronic hardware. Whether a function is performed by hardware or software depends upon the particular application and design constraints imposed on the technical solution. Those skilled in the art may use different methods to implement the described functionality for each particular application, but such implementation is not to be considered as beyond the scope of the present application.

While certain aspects of the invention are presented above in certain claim forms, the applicant contemplates various aspects of the invention in any number of claim forms. Accordingly, the applicants reserve the right to append additional claims after filing the application to append such additional claims form in the application or in a continuation-in-progress application.

Claims

1. A method for operating a communication device, the method comprising:

transmitting a configuration command for coordinating a single-transmission-reception-point (TRP) communication scheme or a multi-TRP communication scheme, wherein the configuration command at least comprises a first TPC command and a second TPC command according to a Downlink Control Information (DCI) format;

at least one scheduled message is transmitted between the user equipment UE and one or more TRPs according to the configuration command, wherein power in the at least one scheduled message is processed according to the first TPC command and/or the second TPC command.

2. The method according to claim 1, wherein:

transmitting the configuration command includes receiving the configuration command at the UE; and

transmitting the at least one scheduled message includes transmitting an uplink UL message from the UE to the first TRP and/or the second TRP.

3. The method according to claim 2, wherein:

the UL message includes a scheduled physical uplink control channel, PUCCH, transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUCCH transmission.

4. A method according to claim 3, further comprising:

5. A method according to claim 3, wherein:

6. The method according to claim 2, wherein:

the UE is configured to: communicating with the first TRP and/or the second TRP using at least one of a first set of sounding reference signals, SRSs, and a second set of SRSs;

the UL message includes a scheduled physical uplink shared channel, PUSCH, transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUSCH transmission and according to the SRS set used.

7. The method of claim 6, further comprising:

8. The method according to claim 6, wherein:

9. The method according to claim 2, wherein:

the configuration commands include (1) the first and second TPC commands of DCI format 0_1 or DCI format 0_2 and (2) at least first and second sounding reference signal, SRS, indicator, SRI, fields; and

the UL message includes a scheduled physical uplink shared channel, PUSCH, transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUSCH transmission and in accordance with the first SRI field and/or the second SRI field in the configuration command.

10. The method of claim 9, further comprising:

11. The method according to claim 9, wherein:

12. The method according to claim 1, wherein:

transmitting the at least one scheduled message includes receiving an uplink UL message from the UE at the first TRP and/or the second TRP.

13. The method of claim 12, further comprising:

14. The method of claim 13, wherein transmitting the communication command comprises transmitting the first TPC command and the second TPC command in DCI format 1_1 or DCI format 1_2 for coordinating a physical uplink control channel, PUCCH, or DCI format 0_1 or DCI format 0_2 for coordinating a physical uplink shared channel, PUSCH.

15. A wireless communication network device, comprising:

an antenna for wirelessly transmitting information with a user equipment UE, wherein the transmitted information comprises:

a configuration command sent to the UE, where the configuration command is used to coordinate a single-transmit-receive point TRP communication scheme or a multi-TRP communication scheme, where the configuration command at least includes a first TPC command and a second TPC command according to a downlink control information DCI format;

an uplink, UL, communication received from the UE, wherein the UL communication has a power level corresponding to the first TPC command and/or the second TPC command;

A backhaul interface for transmitting information with another network device to coordinate the single TRP communication scheme or the multi TRP communication scheme for communication with the UE;

processing circuitry coupled to the antenna and the backhaul interface and configured to generate the first TPC command and/or the second TPC command according to the coordinated single TRP scheme or multi TRP scheme to control application of the first TPC command and/or the second TPC command at the UE.

16. The wireless communication network device of claim 15, wherein the first TPC command and the second TPC command correspond to (1) DCI format 1_1 or DCI format 1_2 for coordinating a physical uplink control channel, PUCCH, or (2) DCI format 0_1 or DCI format 0_2 for coordinating a physical uplink shared channel, PUSCH.

17. A wireless communication user device, comprising:

an antenna for wirelessly transmitting information with a wireless communication network, wherein the transmitted information comprises:

a configuration command received from at least a first transmission reception point TRP and/or a second TRP, the configuration command being used for coordinating a single transmission reception point TRP communication scheme or a multi-TRP communication scheme, wherein the configuration command comprises at least a first TPC command and a second TPC command according to a downlink control information DCI format, an

At least one scheduled uplink UL message transmitted to the first TRP and/or the second TRP; and

processing circuitry coupled to the antenna and configured to control a power level of the at least one scheduled UL message in accordance with the first TRP and/or the second TRP.

18. The wireless communication user equipment of claim 17, wherein:

the at least one scheduled UL message includes a scheduled physical uplink control channel, PUCCH, transmission configured by the UE based on the application of the first TPC command and/or the second TPC command on the scheduled PUCCH transmission.

19. The wireless communication user equipment of claim 18, wherein:

the communication commands include at least one of (1) the first TPC command associated with the first TRP and (2) the second TPC command associated with the second TRP; and

transmitting the at least one scheduled message includes transmitting at least one of the scheduled PUCCH transmissions to one or more TRPs corresponding to the at least one of the first TPC command or the second TPC command.

20. The wireless communication user equipment of claim 17, wherein:

the wireless communication user equipment is configured to: communicating with the first TRP and/or the second TRP using at least one of a first set of sounding reference signals, SRSs, and a second set of SRSs;

the configuration command specifies a selected SRS set that identifies the first SRS set and/or the second SRS set, an

The configuration commands include at least one of (1) the first TPC command associated with the first TRP and (2) the second TPC command associated with the second TRP, wherein the first TPC command and the second TPC command are in DCI format 0_1 or DCI format 0_2;

the at least one scheduled UL message comprises a scheduled physical uplink shared channel, PUSCH, transmission configured based on the application of the first TPC command and/or the second TPC command on the scheduled PUSCH transmission and according to the selected SRS set; and