Method, device and computer storage medium for multi-TRP communication

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer-readable media for multi-TRP communication. A method includes: determining a first beam for a first physical shared channel scheduled by control information; determining a second beam for a second physical shared channel scheduled by the control information, the second beam being different from the first beam; and performing communication on the first physical shared channel via the first beam and on the second physical shared channel via the second beam.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, devices, and computer storage media for multiple transmission and reception point (TRP) communications. Background Art

[0002] Communication technologies have been developed in various communication standards to provide common protocols that enable different wireless devices to communicate at municipal, national, regional, and even global levels. One example of an emerging communication standard is New Radio (NR), such as 5G radio access. NR is a set of enhancements to the Long Term Evolution (LTE) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0003] In NR, a network device (e.g., a next-generation NodeB (gNB)) can be equipped with multiple TRPs or multiple antenna panels. That is, the network device can communicate with a terminal device (e.g., a user equipment (UE)) via one or more of the multiple TRPs or multiple antenna panels, which is also referred to as "multi-TRP communication." In some multi-TRP communication schemes, a single downlink control information (DCI) can be used to schedule more than one physical downlink shared channel (PDSCH), or different DCIs can be used to schedule more than one physical uplink control channel (PUCCH). Summary of the Invention

[0004] In general, example embodiments of the present disclosure provide methods, devices, and computer storage media for multi-TRP communications.

[0005] In a first aspect, a communication method is provided. The method includes determining a first beam for a first physical shared channel scheduled by control information. The method also includes determining a second beam for a second physical shared channel scheduled by the control information, the second beam being different from the first beam. The method also includes performing communication on the first physical shared channel via the first beam and on the second physical shared channel via the second beam.

[0006] In a second aspect, a communication method is provided. The method includes determining a first reference power for performing communication on a first uplink control channel and a second reference power for performing communication on a second uplink control channel, the first uplink control channel and the second uplink control channel being scheduled by different control information. The method also includes determining a first target power for performing the communication on the first uplink control channel and a second target power for performing the communication on the second uplink control channel based on the first reference power and the second reference power. The method also includes performing the communication on the first uplink control channel at the first target power and performing the communication on the second uplink control channel at the second target power.

[0007] In a third aspect, a device for communication is provided. The device includes a processor and a memory. The memory is coupled to the processor and stores instructions thereon. When executed by the processor, the instructions cause the device to perform actions, the actions comprising: determining a first beam for a first physical shared channel scheduled by control information. The actions further comprise: determining a second beam for a second physical shared channel scheduled by the control information, the second beam being different from the first beam. The actions further comprise: performing communication on the first physical shared channel via the first beam and on the second physical shared channel via the second beam.

[0008] In a fourth aspect, a device for communication is provided. The device includes a processor and a memory. The memory is coupled to the processor and stores instructions thereon. When executed by the processor, the instructions cause the device to perform actions, the actions comprising: determining a first reference power for performing communication on a first uplink control channel and a second reference power for performing communication on a second uplink control channel, the first uplink control channel and the second uplink control channel being scheduled by different control information. The actions further comprise: determining a first target power for performing the communication on the first uplink control channel and a second target power for performing the communication on the second uplink control channel based on the first reference power and the second reference power. The actions further comprise: performing the communication on the first uplink control channel at the first target power and performing the communication on the second uplink control channel at the second target power.

[0009] In a fifth aspect, a computer-readable medium having instructions stored thereon is provided, wherein when the instructions are executed on at least one processor, the at least one processor causes the at least one processor to perform the method according to the first aspect of the present disclosure.

[0010] In a sixth aspect, a computer-readable medium having instructions stored thereon is provided, wherein when the instructions are executed on at least one processor, the at least one processor causes the at least one processor to perform the method according to the second aspect of the present disclosure.

[0011] Other features of the present disclosure will become readily apparent from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0013] Figure 1 shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0014] Figure 2 is a schematic diagram illustrating an example process according to some embodiments of the present disclosure;

[0015] Figure 3 shows a schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure;

[0016] Figure 4 shows a schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure;

[0017] Figure 5 shows a schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure;

[0018] Figure 6 shows a schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure;

[0019] Figure 7 is a schematic diagram illustrating an example process according to some embodiments of the present disclosure;

[0020] Figure 8 shows a schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure;

[0021] Figure 9 shows a schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure;

[0022] Figure 10 shows a schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure;

[0023] Figure 11 An example method according to some embodiments of the present disclosure is shown;

[0024] Figure 12 illustrates example methods according to some embodiments of the present disclosure; and

[0025] Figure 13 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0026] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. DETAILED DESCRIPTION

[0027] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, and do not imply any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways other than those described below.

[0028] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0029] As used herein, the term "network device" or "base station" (BS) refers to a device that can provide or accommodate a cell or coverage area in which terminal devices can communicate. Examples of network devices include, but are not limited to, a Node B (Node B or NB), an evolved Node B (eNodeB or eNB), a next-generation Node B (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), low-power nodes such as femto nodes and pico nodes. For discussion purposes, some embodiments will be described below with reference to a gNB as an example of a network device.

[0030] As used herein, the term "terminal device" refers to any device capable of wireless or wired communication. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs), portable computers, image capture devices such as digital cameras, gaming devices, music storage and playback devices, or internet devices capable of wireless or wired internet access and browsing.

[0031] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations should be understood as open terms meaning "including but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0032] In some instances, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among many functional alternatives for use, and that such selection is not necessarily better, lesser, higher, or more preferred than other selections.

[0033] In one embodiment, a terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node, and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device to the terminal device directly or via the first network device. In one embodiment, information related to a configuration configured by the second network device for the terminal device may be sent from the second network device via the first network device. Information related to a reconfiguration configured by the second network device for the terminal device may be transmitted from the second network device to the terminal device directly or via the first network device.

[0034] Figure 1 An example communication network 100 is shown in which embodiments of some aspects of the present disclosure may be implemented. Network 100 includes a network device 110 coupled to two TRPs / panels 130-1 and 130-2 (collectively referred to as TRPs 130 or individually as TRPs 130). Network 100 also includes terminal devices 120 served by network device 110. The service area of ​​network device 110 is referred to as cell 102. It should be understood that the number of network devices, terminal devices, and TRPs is for illustrative purposes only and is not intended to be limiting. Network 100 may include any suitable number of network devices, terminal devices, and TRPs suitable for implementing embodiments of this aspect of the present disclosure. Although not shown, it should be understood that one or more terminal devices may be located in cell 102 and served by network device 110.

[0035] As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to a network device located in a particular geographic location. For example, a network device may be coupled with multiple TRPs in different geographic locations to achieve better coverage. Alternatively or additionally, multiple TRPs may be incorporated into a network device, or in other words, a network device may include multiple TRPs. It should be understood that a TRP may also be referred to as a "panel," which also refers to an antenna array (having one or more antenna elements) or a group of antennas. It should also be understood that a TRP may refer to a logical concept that may be physically implemented in a variety of ways.

[0036] In the communication network 100, the network device 110 can transmit data and control information to the terminal device 120, and the terminal device 120 can also transmit data and control information to the network device 110. The link from the network device 110 to the terminal device 120 is called the downlink (DL) or forward link, and the link from the terminal device 120 to the network device 110 is called the uplink (UL) or reverse link.

[0037] Depending on the communication technology, network 100 can be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, or any other network. The communications discussed in network 100 can use any suitable standard, including but not limited to new radio access (NR), long term evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), cdma2000, global system for mobile communications (GSM), etc. In addition, communications can be performed according to any generation of communication protocols currently known or developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols. The technology described herein can be used for the above-mentioned wireless networks and radio technologies as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

[0038] like Figure 1As shown, the network device 110 can communicate with the terminal device 120 via the TRP 130-1 and the TRP 130-2. Hereinafter, the TRP 130-1 may also be referred to as the first TRP, and the TRP 130-2 may also be referred to as the second TRP. Each TRP 130 may provide multiple beams for communicating with the terminal device 120. The first TRP 130-1 and the second TRP 130-2 may be included in the same service cell provided by the network device 110 (e.g., Figure 1 102) or in different serving cells.

[0039] Although some example embodiments of the present disclosure are described with reference to a first TRP 130-1 and a second TRP 130-2 within the same serving cell 102 provided by a network device 110, these embodiments are provided for illustrative purposes only and to assist those skilled in the art in understanding and implementing the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. Embodiments of the present disclosure may be implemented in a network in which TRPs 130 are within different serving cells provided by a network device 110. It should be understood that the present disclosure described herein may be implemented in various ways other than those described below.

[0040] As described above, in some multi-TRP communication schemes, a single DCI can be used to schedule more than one PDSCH, or different DCIs can be used to schedule more than one PUCCH. For example, a network device can schedule two PDSCHs via a single DCI, for example, each PDSCH corresponds to one of the two TRPs. The terminal device needs time to decode the DCI to determine information about the two PDSCHs. Before the DCI is decoded, the terminal device may not know the beams indicated by the network device for the two PDSCHs. Therefore, there may be a delay in performing PDSCH transmission. In order to reduce the delay, the terminal device can use a default beam to perform PDSCH transmission before the DCI is decoded. However, if there are two PDSCHs that require different beams, for example, in the case of two TRPs, it is necessary to solve how to select beams for the two PDSCHs.

[0041] As used herein, the term "beam" refers to a resource in the spatial domain and is indicated by a set of parameters. In the 3GPP specifications for NR, a beam can be indicated by quasi-colocation (QCL) type D information, which is included in the Transmission Configuration Indication (TCI) status. The beam used here for PDSCH is for reception.

[0042] The exemplary embodiments of the present disclosure provide a solution for multi-TRP communication. This solution supports beam selection for different PDSCHs or beam selection for different parts of the PDSCH. This can reduce the delay of downlink transmission, thereby achieving high performance.

[0043] Figure 2 is a schematic diagram illustrating an example process 200 according to some embodiments of the present disclosure. Figure 2 As shown, example process 200 may involve network device 110 and terminal device 120. It should be understood that process 200 may include additional actions not shown and / or may omit some of the actions shown, and the scope of the present disclosure is not limited in this respect.

[0044] like Figure 2 As shown, the network device 110 may send 205 control information (e.g., DCI) to the terminal device 120. The control information may schedule more than one physical shared channel, each physical shared channel corresponding to a different TRP. For example, the DCI may schedule a first PDSCH corresponding to the first TRP 130-1 and a second PDSCH corresponding to the first TRP 130-2.

[0045] The terminal device 120 determines 210 a first beam for a first physical shared channel, the first physical shared channel being scheduled by control information received from the network device 110. In some example embodiments, the first beam may be a default beam used before the control information is decoded, and / or the first beam may be a default beam used before being switched to a new beam indicated by the control information. For example, before the DCI is decoded by the terminal device 120, there may not be any beam indicated by any DCI for performing PDSCH reception, and it may take some time for the new beam to be enabled before switching to the new beam indicated by the DCI. In this way, the terminal device 120 may use the default beam to perform PDSCH reception.

[0046] Terminal device 120 determines a second beam for a second physical shared channel, which is scheduled by control information received from network device 110. The second beam is different from the first beam. In some example embodiments, the second beam may be another default beam used before the control information is decoded, and / or the second beam may be another default beam used before being switched to a new beam indicated by the control information. In some example embodiments, the second beam may be a beam indicated by a DCI. Since a single DCI can schedule two PDSCHs corresponding to different TRPs, terminal device 120 needs to use two different beams to perform PDSCH reception via different TRPs.

[0047] In some example embodiments, both the first beam and the second beam may be default beams. Figure 3 , Figure 3 A schematic diagram 300 is shown illustrating multiple PDSCHs according to some embodiments of the present disclosure. Figure 3 As shown, DCI 301 can schedule a first PDSCH 311 corresponding to the first TRP 130-1 and a second PDSCH 312 corresponding to the second TRP 130-2. Time 321 indicates the time when the monitoring of the PDCCH ends, and time 322 indicates the time when the decoding of DCI 301 is completed and / or the new beam indicated by DCI 301 is ready for PDSCH reception.

[0048] Since the DCI 301 has not yet been decoded, the terminal device 120 can use two different default beams for performing communication on the PDSCH (e.g., the first PDSCH 311 and the second PDSCH 312) during the time interval between the time instant 321 and the time instant 322. It should be noted that although the PDSCHs scheduled by a single DCI are referred to as the first PDSCH and the second PDSCH, they may also be referred to as the first part of the PDSCH and the second part of the PDSCH.

[0049] In some example embodiments, a first beam may be determined based on a control resource set (CORESET) configured to monitor control information. A CORESET set or CORESET group may be configured to monitor the PDCCH. A beam associated with a CORESET from the CORESET set may be determined as the first beam. Figure 3 As shown, CORESET 331 and CORESET 332 may be configured for the terminal device 120 for monitoring the PDCCH, and DCI 301 may be monitored within CORESET 331. The beam associated with CORESET 331 may be determined as the first beam. In this case, DCI 301 may be transmitted via the first TRP 130-1 or otherwise correspond to the first TRP 130-1.

[0050] The second beam can be determined based on the available TCI states containing QCL type D information. Multiple TCI states for PDSCH transmission (which can be activated by a media access control element MAC CE received from a network device) may be referred to as available TCI states in this article. The second beam can be determined based on the available TCI states corresponding to the second TRP 130-2. A beam corresponding to a specific TCI state in the available TCI states can be determined as the second beam. For example, a beam corresponding to an activated TCI state (e.g., with the lowest ID) can be determined as the second beam, and the activated TCI state is applicable to PDSCH reception for the second TRP 130-2.

[0051] In some example embodiments, both the first beam and the second beam may be determined based on a CORESET configured to monitor control information. In this case, the CORESET may be configured with at least two TCI states, or with TCI states having at least two QCL type D information, and thus the CORESET may be associated with at least two beams. The first beam and the second beam may be selected from at least two beams. For example, the first beam and the second beam may be selected from at least two beams associated with the CORESET in which the control information is monitored (i.e., Figure 3 Select from CORESET 331 of the example shown.

[0052] As another example, the first beam and the second beam may be determined based on the CORESET with the lowest CORESET ID. Figure 3 As shown, DCI 301 may correspond to the first TRP 130-1, and a CORESET set or CORESET group (e.g., CORESETs 331 and 332) may be configured to correspond to the first TRP 130-1. The first beam and the second beam may be determined based on the CORESET with the lowest CORESET ID from the CORESET set or CORESET group (e.g., CORESETs 331 and 332).

[0053] In some example embodiments, the first beam and the second beam may be determined based on available TCI states. The first set of TCI states may be activated by a MAC CE for a PDSCH corresponding to the first TRP 130-1 (e.g., the first PDSCH 311), while the second set of TCI states may be activated by a MAC CE for a PDSCH corresponding to the second TRP 130-2 (e.g., the second PDSCH 312). A beam corresponding to a specific TCI state selected from the first set of TCI states may be determined as the first beam, and a beam corresponding to a specific TCI state selected from the second set of TCI states may be determined as the second beam. For example, the specific TCI state may be the TCI state with the lowest ID among the sets of TCI states.

[0054] The above exemplary embodiments are described to illustrate determining a first beam and a second beam. It should be understood that aspects of these exemplary embodiments may be combined. For example, the method described for determining a first beam may be used to determine a second beam in some other exemplary embodiments, and vice versa.

[0055] Now back to the reference Figure 2 After determining the first beam and the second beam, the terminal device 120 performs 220 communication on the first physical shared channel via the first beam and on the second physical shared channel via the second beam. For example, the terminal device 120 may receive data on the first PDSCH 311 via the first beam and receive data on the second PDSCH 312 via the second beam.

[0056] In some example embodiments, when performing communication, switching between the first beam and the second beam is performed based on criteria defined in the time domain. Figure 4 , Figure 4 A schematic diagram 400 illustrating multiple PDSCHs according to some embodiments of the present disclosure is shown. Figure 4 As shown, DCI 401 may schedule a first PDSCH 411 corresponding to the first TRP 130-1 and a second PDSCH 412 corresponding to the second TRP 130-2. Time 421 indicates the time when monitoring of the PDCCH ends, and time 422 indicates the time when decoding of DCI 401 is completed and / or the new beam indicated by DCI 401 is ready for PDSCH reception.

[0057] like Figure 4As shown, DCI 401, first PDSCH 411, and second PDSCH 412 are all within the same time slot 410. Since DCI 401 has not been decoded or a new beam is not ready, terminal device 120 may use a default beam to perform communication on the PDSCH during the time interval between time 421 and time 422. For example, the first beam may be used before time 423, and the second beam may be used after time 423. In this way, the switching of the receive beam occurs at time 423. The first beam and the second beam may be determined as described in any of the above exemplary embodiments.

[0058] Time 423 can be considered a TDM switching threshold for the TCI. That is, a first TCI state is used before time 423, and a second TCI state different from the first TCI state is used after time 423. The TDM switching threshold can be configured by network device 110 or can be predefined. For example, time 423 can be determined so that the duration of time in time slot 410 before time 423 is the same as the duration of time in time slot 410 after time 423.

[0059] In some example embodiments, one or more CORESETs having a monitoring search space (SS) may be associated with ultra-reliable low latency communication (URLLC), and for ease of discussion, such a CORESET may be referred to as a URLLC CORESET. Meanwhile, a CORESET not associated with URLLC may be referred to as a non-URLLC CORESET (non-URLLC CORESET). In such example embodiments, a URLLC CORESET may take precedence over a non-URLLC CORESET. The above examples regarding the default beam for PDSCH may be implemented in conjunction with a URLLC CORESET. For example, CORESET 431 for monitoring DCI 401 is a URLLC CORESET, and CORESET 432 is a non-URLLC CORESET. When a URLLC CORESET having an SS for monitoring DCI exists in a slot, the above example with two beams for multiple TRPs may be applied. When there is only a non-URLLC CORESET having an SS for monitoring DCI within a slot, a transmission scheme based on a single TRP may be applied.

[0060] In some example embodiments, when performing communication, switching between the first beam and the second beam is performed based on criteria defined in the frequency domain. Figure 5 , Figure 5 A schematic diagram 500 illustrating multiple PDSCHs according to some embodiments of the present disclosure is shown. Figure 5As shown, DCI 501 can schedule a first PDSCH 511 corresponding to the first TRP 130-1 and a second PDSCH 512 corresponding to the second TRP 130-2. Time 521 indicates the time when the monitoring of the PDCCH ends, and time 522 indicates the time when the decoding of DCI 501 is completed and / or the new beam indicated by DCI 501 is ready for PDSCH reception.

[0061] like Figure 5 As shown, DCI 501, a first PDSCH 511, and a second PDSCH 512 are all within the same time slot 510. Since DCI 501 is not decoded, the terminal device 120 can use a default beam to perform communication on the PDSCH during the time interval between time 521 and time 522. For example, the first beam can be used for resources whose frequencies are higher than a threshold frequency 523, and the second beam can be used for resources whose frequencies are lower than the threshold frequency 523. In this way, the switching of the receive beam occurs at the threshold frequency 523. The first beam and the second beam can be determined as described in connection with any of the above exemplary embodiments.

[0062] Threshold frequency 523 can be considered an FDM switching threshold for TCI. That is, above threshold frequency 523, a first TCI state is used, and below threshold frequency 523, a second TCI state different from the first TCI state is used. The FDM switching threshold can be configured by network device 110 or can be predefined.

[0063] In some example embodiments, similar to the above reference Figure 4 As described, a URLLC CORESET can take precedence over a non-URLLC CORESET. For example, CORESET 531 used to monitor DCI 501 is a URLLC CORESET, while CORESET 532 is a non-URLLC CORESET. When URLLC CORESET 531 and non-URLLC CORESET 532 overlap in the time domain used for DCI monitoring and the beams associated with the two CORESETs are different, DCI monitoring associated with URLLC CORESET 531 can be prioritized, and DCI monitoring associated with CORESET 531 can be ignored.

[0064] Some example embodiments in which both the first beam and the second beam are default receive beams are described above. In some example embodiments, one of the first beam and the second beam may be a beam determined based on control information, rather than the default receive beam. Figure 6 , Figure 6Schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure is shown. Figure 6 As shown, DCI 601 may schedule a first PDSCH 611 corresponding to the first TRP 130-1 and a second PDSCH 612 corresponding to the second TRP 130-2. Time 621 indicates the time when monitoring of the PDCCH ends.

[0065] like Figure 6 As shown, DCI 601 and first PDSCH 611 are in the same time slot 610, and second PDSCH 612 is in a time slot 620 following time slot 610. In this case, terminal device 120 can use the first beam to perform communication on first PDSCH 611. The first beam can be the default beam described in any of the above example embodiments. Since second PDSCH 612 is scheduled in the next time slot 620, DCI 601 may have been decoded before receiving second PDSCH 612. In this way, the second beam can be determined based on DCI 601 without using the default beam.

[0066] The CORESET 601 for monitoring DCI 601 may be a URLLC CORESET. In such an embodiment, the default receive beam may be used in the same time slot 610 as the URLLC CORESET with the monitoring SS. The receive beam indicated by DCI 601 may be used in a time slot after time slot 610 (i.e., time slot 620 in this example).

[0067] In some example embodiments, the first beam and the second beam may be determined based on the time offset between the reception of the control information and the corresponding physical shared channel. For example, if the time offset is less than a threshold, as indicated by the "timeDurationForQCL" field, the default beam may be used. If the time offset is greater than the threshold, the beam indicated by the DCI may be used.

[0068] As an example, when the field "tci-PresentInDCI" is set to "enabled" and tci-PresentInDCI is not configured as radio resource control (RRC) connected mode, if the offset between the reception of the DL DCI and the reception of the first part of the corresponding PDSCH is less than timeDurationForQCL, the terminal device may consider that the demodulation reference signal (DM-RS) ports of the first part of the PDSCH of the serving cell (or, in other words, the first PDSCH) are quasi-co-located relative to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitored search space with the lowest CORESET-ID in the most recent time slot, where one or more CORESETs within the active bandwidth part (BWP) of the serving cell are monitored by the terminal device in the most recent time slot. If the offset between the reception of the DL DCI and the reception of the corresponding second part of the PDSCH is greater than the threshold timeDurationForQCL, the terminal device will use the TCI state to determine the quasi-colocation of the second part antenna ports of the PDSCH, where the TCI state is based on the value of the 'TransmissionConfiguration Indication' field of the detected PDCCH with DCI.

[0069] Several example embodiments have been described above to illustrate how to determine a receive beam for a PDSCH, for example, in a multi-TRP scenario. Using a default receive beam in this manner can reduce the delay caused by decoding control information. Furthermore, the delay caused by beam switching can also be reduced.

[0070] As mentioned above, in some multi-TRP communication schemes, different DCIs may be used to schedule more than one PUCCH that may correspond to different TRPs. Therefore, a power control mechanism between such PUCCHs needs to be addressed.

[0071] The terminal device can determine the PUCCH transmission power P in PUCCH transmission opportunity i based on the following equation (1): PUCCb，f，c (i,q u ,q d , l):

[0072]

[0073] Item P O_PUCCH，b，f，c (q u ) can be represented by the component P O_NOMINAL_PUCCH and component P O_UE_PUCCH (q u ) is composed of the cell-specific parameter P O_NOMINAL_PUCCH Can be called P0_NoMINAL , and can be given in the field "in PUCCH-ConfigCommon". Terminal device-specific parameters P O_UE_PUCCH (q u ) can be called P 0_UE and can be given in the p0-Set contained in PUCCH-PowerControl. b，f，c (q d ) is the RS resource index q used by the terminal device d The calculated downlink path loss estimate in decibels. For the purposes of this discussion, the term PL is used to determine b，f，c (q d )’s RS can be referred to as path loss RS here.

[0074] In the multi-TRP communication scheme, it is necessary to determine the above parameter P 0_NOMINAL 、P 0_UE , path loss RS and closed-loop index 1. The actual power used to perform transmission on the PUCCH corresponding to different TRPs may need to be adjusted.

[0075] Figure 7 FIG. 7 is a diagram illustrating an example process 700 according to some embodiments of the present disclosure. Figure 7 As shown, example process 700 may involve network device 110 and terminal device 120. It should be understood that process 700 may include additional actions not shown and / or may omit some of the actions shown, and the scope of the present disclosure is not limited in this respect.

[0076] like Figure 7 As shown, the network device 110 may send 705 different control information to the terminal device 120. For example, the network device 110 may send different DCI corresponding to different TRPs. Different control information may schedule different uplink control channels.

[0077] Now refer to Figure 8 , Figure 8 A schematic diagram 800 illustrating multiple PUCCHs according to some embodiments of the present disclosure is shown. Figure 8As shown, a first DCI 801 may schedule a first PUCCH 811, and a second DCI 802 may schedule a second PUCCH 812. The first DCI 801 may correspond to a first TRP 130-1. For example, the first DCI 801 may be monitored within a first CORESET group 831, which may be assigned to the first TRP 130-1. Similarly, the second DCI 802 may correspond to a second TRP 130-2. For example, the second DCI 802 may be monitored within a second CORESET group 832, which may be assigned to the second TRP 130-2.

[0078] Now back to the reference Figure 7 The terminal device 120 determines 710 a first reference power P1 for performing communications on the first uplink control channel. initial and a second reference power P2 for performing communication on the second uplink control channel initial The first reference power P1 iniitial and the second reference power P2 initial It can be determined based on the above equation (1). The following are some exemplary embodiments to describe how to determine the above parameter P 0_NOMINAL 、P 0_UE , path loss RS and closed-loop index l.

[0079] In some example embodiments, different TRPs or different CORESET groups may correspond to cell-specific parameters P 0_NOMINAL For example, network device 110 can be different values ​​of parameter P 0_NOMINAL Two values ​​are configured, each of which corresponds to a TRP or a CORESET group. These two values ​​can be included in the radio resource control RRC signaling of the terminal device 120. Example information elements for indicating these values ​​can be as follows:

[0080] PUCCH-ConfigCommon::=SEQUENCE{

[0081] pucch-ResourccCommon INTEGER(0..15)OPTIONAL,

[0082] pucch-GroupHopping ENUMERATED{neither, enable, disable},

[0083] hoppingId INTEGER(0..1023)OPTIONAL,

[0084] p0-nominal_TRP1 INTEGER(-202..24)OPTIONAL,

[0085] p0-nominal_TRP2 INTEGER(-202..24)OPTIONAL,

[0086] }

[0087] It should be understood that the above information elements are provided for illustration purposes only and are not limiting. The values ​​may be indicated to the terminal device 120 in various suitable ways.

[0088] In such an example embodiment, the P for the PUCCH in response to the DCI corresponding to the CORESET group / TRP 0_NOMINAL A value can be associated with this CORESET group / TRP. Figure 8 In the example shown, for the first PUCCH 811, P 0_NOMINAL The value may be determined based on the "p0-nominal_TRP1" in the example information element, while the P value for the second PUCCH 812 may be 0_NOMINAL The value may be determined based on the "p0-nominal_TRP2" in the example information element.

[0089] In some example embodiments, for example, P for different PUCCHs may be configured without specific indication from network device 110. 0_UE The P value may be determined in a default manner. The terminal device 120 may obtain a set of P values ​​configured by the network device 110. 0_UE value, and from this group P 0_UE Select two values ​​from the value to determine the reference power P1 initial and P2 initial For example, the default value to be used by the terminal device 120 may be P 0_UE values, for example, p0-PUCCH-Id having values ​​of 0 and 1.

[0090] As an example, if the terminal device 120 is not provided with PUCCH-SpatialRelationInfo, the terminal device 120 may obtain the first two p0-PUCCH-Value values ​​from a P0-PUCCH having a p0-PUCCH-Id in p0-Set equal to 0 and 1. Each of the first two p0-PUCCH-Value values ​​may correspond to a first TRP 130-1 and a second TRP 130-2, respectively.

[0091] In some example embodiments, the terminal device 120 may use the default path loss RS to determine the reference power P1initial and P2 initial A first path loss RS of the first uplink control channel may be determined based on the first control information, and a second path loss RS may be determined based on the second control information.

[0092] In some example embodiments, terminal device 120 may determine a path loss RS based on a synchronization signal / physical broadcast channel SSB / PBCH block and a CORESET. For example, terminal device 120 may determine an SSB / PBCH block associated with the first control information and determine a first path loss RS based on the SSB / PBCH block. Terminal device 120 may also select a CORESET from a group of CORESETs configured to monitor the second control information and determine a second path loss RS based on the selected CORESET.

[0093] In other words, if the terminal device 120 is not provided with pathlossRefrenceRSs, or before the terminal device 120 is provided with dedicated higher layer parameters, the terminal device 120 may calculate the path loss PL for the first uplink control channel using RS resources obtained from the SS / PBCH block that the terminal device 120 uses to obtain the master information block (MIB) for the first TRP. b，f，c (q d ). The terminal device 120 may calculate the PL for the second uplink control channel using the RS resources corresponding to the QCLRS of the CORESET with the lowest ID associated with the second TRP. b，f，c (q d ).

[0094] for Figure 8 In the example shown, a first path loss RS for the first PUCCH 811 may be determined based on the SS / PBCH block used by the terminal device 120 to obtain the MIB for the first TRP 130-1. A second path loss RS for the second PUCCH 812 may be determined based on a CORESET (e.g., with the lowest ID) in the second CORESET group 832 corresponding to the second TRP 130-2.

[0095] In some example embodiments, terminal device 120 may determine a path loss RS based on a CORESET configured to monitor corresponding control information. For example, terminal device 120 may select a first CORESET from a first group of CORESETs configured to monitor first control information, and determine a first path loss RS based on the first CORESET. Terminal device 120 may also select a second CORESET from a second group of CORESETs configured to monitor second control information, and determine a second path loss RS based on the second CORESET.

[0096] In other words, if the terminal device 120 is not provided with pathlossRefrreceRSs, or before the terminal device 120 is provided with dedicated higher layer parameters, the terminal device 120 may calculate the path loss PL for the first uplink control channel using the RS resources corresponding to the QCL RS of the CORESET with the lowest ID associated with the first TRP. b，f，c (q d The terminal device 120 may calculate the path loss PL for the second uplink control channel using the RS resources corresponding to the QCL RS of the CORESET having the lowest ID associated with the second TRP. b，f，c (q d ).

[0097] for Figure 8 In the example shown, a first path loss RS for the first PUCCH 811 may be determined based on the CORESET with the lowest ID in the first CORESET group 831 corresponding to the first TRP 130-1. A second path loss RS for the second PUCCH 812 may be determined based on the CORESET with the lowest ID in the second CORESET group 832 corresponding to the second TRP 130-2.

[0098] In some example embodiments, the path loss RS may be selected from a set of RSs configured by the network device 110. For example, if the terminal device 120 is provided with pathlossReferenceRSs and is not provided with PUCCH-SpatialReIationInfo, the terminal device 120 may obtain two (e.g., the first two) referencesignal values ​​in the PUCCH-PathlossReferenceRS from the pucch-PathlossRefrrenceRS-Id indexed 0 and 1 in the PUCCH-PathlossReferenceRS, where the RS resources are either on the same serving cell or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking. The two referencesignal values ​​obtained may correspond to the first TRP and the second TRP, respectively.

[0099] In some example embodiments, one or more of the following may be indicated by the MAC CE from network device 110: UE-specific parameter P 0_UE Value, path loss RS, and closed loop index (CLI). Table 1 shows an example structure A of a MAC CE for indicating power control parameters. In this example, the field "CLI or TRPID" can be used to indicate the closed loop index l and / or the corresponding TRP. In this case, the UE-specific parameters P of the first and second PUCCHs are 0_UE The value and the path loss RS may be determined as described in the above exemplary embodiment, or may be determined in other suitable manners.

[0100] Table 1 Example structure of MAC CE

[0101]

[0102] Table 2 shows an example structure B of a MAC CE for indicating power control parameters. In addition to the field "CLI or TRPID" (CLI or TRPID), the example structure B of the MAC CE also includes a field "P0_and_PL_RS1" and a field "P0_and_PL_RS2". The field "P0_and_PL_RS1" indicates the power control parameters to be used for the first uplink control channel (e.g., Figure 8 The first PUCCH811) is shown as P 0_UE value and the first path loss RS, while the field "P0_and_PL_RS2" indicates the path loss RS used for the second uplink control channel (e.g., Figure 8 The second PUCCH 812) is shown as P 0_UEvalue and the second path loss RS.

[0103] Table 2 Example structure of MAC CE A

[0104]

[0105] Table 3 shows an example structure C of a MAC CE for indicating power control parameters. The example structure C of a MAC CE includes fields of a bitmap S7...S0. A bit Si (i=0,...,7) with a value of "1" activates the P to be used for the uplink control channel. 0_UE The i-th power control configuration of the value, the path loss RS index and / or the closed loop index value (i>=0). An example power control configuration may be as follows.

[0106]

[0107] Table 3 Example structure of MAC CE C

[0108]

[0109] In such an example embodiment, several advantages can be achieved. For example, the use of MAC CE can improve the resource utilization efficiency of PUCCH in the UL. In addition, there is no need to update the specifications of RRC and no need to configure spatial information.

[0110] Now back to the reference Figure 7 The terminal device 120 determines 715 a first target power for performing communications on the first uplink control channel and a second target power for performing communications on the second uplink control channel based on the first reference power and the second reference power. In some example embodiments, the first reference power Pl may be used to determine 715 a first target power for performing communications on the first uplink control channel and a second target power for performing communications on the second uplink control channel based on the first reference power and the second reference power. initial and the second reference power P2 initial The actual power for the first PUCCH and the second PUCCH is adjusted. The terminal device 120 performs 720 communication on the first uplink control channel with the first target power and performs 720 communication on the second uplink control channel with the second target power.

[0111] In some example embodiments, transmissions on the first uplink control channel and the second uplink channel may be performed with the same power. That is, the first target power and the second target power may be the same. If the first uplink control channel precedes the second uplink control channel in the time domain, the terminal device 120 may determine a time gap between the end of the first uplink control channel and the beginning of the second uplink control channel. If the time gap is lower than a threshold gap, the terminal device 120 may determine a common target power for performing communications on the first uplink control channel and the second uplink control channel based on the first reference power and the second reference power. For example, a maximum or minimum value of the first reference power and the second reference power may be used as the common power.

[0112] Now refer to Figure 9 , Figure 9 Schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure is shown. Figure 9 As shown, a first DCI 901 may schedule a first PUCCH 911, and a second DCI 902 may schedule a second PUCCH 912. The first DCI 901 may correspond to a first TRP 130-1. For example, the first DCI 901 may be monitored within a first CORESET 931, which may be configured to the first TRP 130-1. Similarly, the second DCI 902 may correspond to a second TRP 130-2. For example, the second DCI 902 may be monitored within a second CORESET group 932, which may be configured to the second TRP 130-2.

[0113] The first reference power or indicated power for transmission on the first PUCCH 911 may be denoted as P1 initial , and the second reference power or indicated power for transmission on the second PUCCH 912 may be denoted as P2 initial .like Figure 9 As shown, the first PUCCH 911 does not overlap with the second PUCCH 912 and precedes the second PUCCH 912. The terminal device 120 may determine a time gap 920 between the end of the first PUCCH 911 and the beginning of the second PUCCH 912. The terminal device 120 may determine whether the time gap 920 exceeds a threshold gap. The threshold gap may be determined based on (e.g., equal to or slightly greater than) the time for the terminal device 120 to adjust the transmit power.

[0114] If the time gap 920 is less than the threshold gap, the terminal device 120 may perform transmission on the first PUCCH 911 and the second PUCCH 912 at a common power. The common power may be P1initial and P2 initial The maximum value of P1 initial and P2 initial Alternatively, the common power can be based on P1 initial and P2 initial Determined power, such as P1 initial and P2 initial The average value of .

[0115] If the time gap 920 is equal to or greater than the threshold gap, the terminal device 120 may respectively initial The transmission is performed on the first PUCCH 911 with a transmission power of P1 initial Transmission is performed on the first PUCCH 911 with a transmission power of 1. In other words, the first reference power is determined as the first target power, and the second reference power is determined as the second target power.

[0116] In some example embodiments, if the first uplink control channel and the second uplink control channel overlap in the time domain, transmit power may be shared between the first uplink control channel and the second uplink control channel. Terminal device 120 may determine whether the sum of the first reference power and the second reference power exceeds the maximum power. If the sum of the first reference power and the second reference power exceeds the maximum power, terminal device 120 may determine the first target power and the second target power such that the sum of the first target power and the second target power is less than the maximum power.

[0117] Now refer to Figure 10 , Figure 10 Schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure is shown. Figure 10 As shown, a first DCI 1001 may schedule a first PUCCH 1011, and a second DCI 1002 may schedule a second PUCCH 1012. The first DCI 1001 may correspond to a first TRP 130-1. For example, the first DCI 1001 may be monitored within a first CORESET group 1031, which may be assigned to the first TRP 130-1. Similarly, the second DCI 1002 may correspond to a second TRP 130-2. For example, the second DCI 1002 may be monitored within a second CORESET group 1032, which may be assigned to the second TRP 130-2.

[0118] A maximum power P can be configured for each of the first TRP and the second TRP. CMAX For example, the first maximum power P CMAX，1may correspond to the first TRP 130-1, and the second maximum power P CMAX，2 The first target power for transmitting on the first PUCCH 1011 and the second target power for transmitting on the second PUCCH 1012 may be denoted as P1 and P2, respectively. The total transmit power may be shared between the first PUCCH 1011 and the second PUCCH 1012 so that the sum of the first target power P1 and the second target power P2 is no greater than the first maximum power P1. CMAX，1 and the second maximum power P CMAX，2 That is, the following equation (2) will be satisfied:

[0119] P1+P2≤P CMAX，1 +P CMAX，2 (2)

[0120] If the terminal device 120 determines the first reference power P1 initial and the second reference power P2 initial The sum exceeds the first maximum power P CMAX，1 and the second maximum power P CMAX，2 The sum of P1 initial +P2 initial >P CMAX，1 +P CMAX，2 , the terminal device 120 can be based on the first reference power P1 initial and the second reference power P2 initial The first target power P1 and the second target power P2 can be based on the first reference power P1. initial and the second reference power P2 initial For example, the ratio of P1 to P2 may be equal to P1 initinal With P2 initial ratio.

[0121] The duration for sharing the PUCCH transmission power between the two PUCCHs may be determined by the union of the duration of the first PUCCH and the duration of the second PUCCH. Figure 10 As shown, power allocation between the first PUCCH 1011 and the second PUCCH 1012 occurs during time interval 1020 .

[0122] Figure 11 1 shows a flow chart of an example method 1100 according to some embodiments of the present disclosure. The method 1100 may be performed in a manner such as Figure 1It should be understood that the method 1100 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited thereto. For the purpose of discussion, reference will be made to Figure 1 Method 1100 is described from the perspective of terminal device 120.

[0123] At block 1110, terminal device 120 determines a first beam for a first physical shared channel scheduled by the control information. In some example embodiments, the first beam may be a default beam used before the control information is decoded, and / or the first beam may be a default beam used before being switched to a new beam indicated by the control information. At block 1120, terminal device 120 determines a second beam for a second physical shared channel scheduled by the control information. The second beam is different from the first beam.

[0124] In some example embodiments, terminal device 120 may select a CORESET from a set of CORESETs configured to monitor control information, and determine a beam associated with the selected CORESET as a first beam. Terminal device 120 may also select a TCI state from a set of TCI states available for a second physical shared channel, and determine a beam corresponding to the selected TCI state as a second beam.

[0125] In some example embodiments, the terminal device 120 may select a CORESET from a group of CORESETs configured to monitor control information, and the selected CORESET may be associated with at least two beams. The terminal device 120 may also select the first beam and the second beam from the at least two beams.

[0126] In some example embodiments, terminal device 120 may select a first TCI state from a first set of TCI states available for a first physical shared channel, and determine a beam corresponding to the first TCI state as the first beam. Terminal device 120 may also select a second TCI state from a second set of TCI states available for a second physical shared channel, and determine a beam corresponding to the second TCI state as the second beam.

[0127] In some example embodiments, the terminal device 120 may determine a time offset between reception of the control information and reception of the second physical shared channel.If the time offset exceeds a predetermined threshold, the terminal device 120 may determine the second beam based on the control information.

[0128] At block 1130 , the terminal device 120 performs communication on a first physical shared channel via a first beam and performs communication on a second physical shared channel via a second beam.

[0129] In some example embodiments, terminal device 120 may determine a time within a time interval during which control information is received. Terminal device 120 may communicate on a first physical shared channel via a first beam before the time interval, and may communicate on a second physical shared channel via a second beam after the time interval.

[0130] In some example embodiments, terminal device 120 may communicate on a first physical shared channel via a first beam using a first resource having a frequency higher than a threshold frequency. Terminal device 120 may communicate on a second physical shared channel via a second beam using a second resource having a frequency higher than a threshold frequency.

[0131] In some example embodiments, the control information is received in a first time interval. The terminal device 120 may communicate on a first physical shared channel via a first beam in the first time interval and on a second physical shared channel via a second beam in a second time interval, the second time interval being subsequent to the first time interval.

[0132] In some example embodiments, terminal device 120 may further determine a first reference power for performing communication on a first uplink control channel and a second reference power for performing communication on a second uplink control channel, the first uplink control channel and the second uplink control channel being scheduled by different control information. Terminal device 120 may determine a first target power for performing communication on the first uplink control channel and a second target power for performing communication on the second uplink control channel based on the first reference power and the second reference power. Terminal device 120 may perform communication on the first uplink control channel with the first target power and perform communication on the second uplink control channel with the second target power.

[0133] Figure 12 1 shows a flow chart of an example method 1200 according to some embodiments of the present disclosure. The method 1200 may be implemented at the terminal device 120, such as Figure 1 It should be understood that method 1200 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard. For discussion purposes, reference will be made to Figure 1 The method 1200 is described from the perspective of the terminal device 120 .

[0134] At block 1210, the terminal device 120 determines a first reference power for performing communications on a first uplink control channel and a second reference power for performing communications on a second uplink control channel.The first uplink control channel and the second uplink control channel are scheduled by different control information.

[0135] In some example embodiments, terminal device 120 may obtain a set of power control parameters specific to the terminal device configured by the network device. Terminal device 120 may select two power control parameters from the set of power control parameters, each power control parameter being used to determine one of the first reference power and the second reference power.

[0136] In some example embodiments, the first uplink control channel is scheduled by first control information, and the second uplink control channel is scheduled by second control information. Terminal device 120 may determine a first reference signal for determining a path loss for the first uplink control channel and a second reference signal for determining a path loss for the second uplink control channel based on the first control information and the second control information.

[0137] In some example embodiments, terminal device 120 may determine an SSB / PBCH block associated with the first control information and determine the first reference signal based on the SSB / PBCH block. Terminal device 120 may select a CORESET from a set of CORESETs configured to monitor the second control information and determine the second reference signal based on the selected CORESET.

[0138] In some example embodiments, the terminal device 120 may select a first CORESET from a first group of CORESETs configured to monitor the first control information, and determine the first reference signal based on the first CORESET. The terminal device 120 may select a second CORESET from a second group of CORESETs configured to monitor the second control information, and determine the second reference signal based on the second CORESET.

[0139] In some example embodiments, terminal device 120 may receive a medium access control (MAC) control element (CE) from network device 110, the MAC CE including at least a field indicating a power control parameter. Terminal device 120 may determine the first reference power and the second reference power based on the MAC CE.

[0140] At block 1220 , the terminal device 120 determines a first target power for performing communications on the first uplink control channel and a second target power for performing communications on the second uplink control channel based on the first reference power and the second reference power.

[0141] In some example embodiments, the first uplink control channel precedes the second uplink control channel in the time domain. Terminal device 120 may determine a time gap between the end of the first uplink control channel and the beginning of the second uplink control channel. If the time gap is below a threshold gap, terminal device 120 may determine a common target power for performing communications on the first uplink control channel and communications on the second uplink control channel based on the first reference power and the second reference power.

[0142] Alternatively, in some example embodiments, if the time gap exceeds the threshold gap, the terminal device 120 may determine the first reference power as the first target power and the second reference power as the second target power.

[0143] In some example embodiments, the first uplink control channel overlaps with the second uplink control channel in the time domain. Terminal device 120 may determine whether a first sum of the first reference power and the second reference power exceeds the maximum power. If the first sum of the first reference power and the second reference power exceeds the maximum power, terminal device 120 may determine the first target power and the second target power such that the second sum of the first target power and the second target power is less than the maximum power.

[0144] At block 1230 , the terminal device 120 performs communications on the first uplink control channel with a first target power and performs communications on the second uplink control channel with a second target power.

[0145] Figure 13 is a simplified block diagram of a device 1300 suitable for implementing embodiments of the present disclosure. The device 1300 can be considered as Figure 1 Another example implementation of the network device 110, TRP 130, or terminal device 130 is shown. Thus, the device 1300 may be implemented at the network device 110, TRP 130, or terminal device 130, or may be implemented as at least a portion of the network device 110, TRP 130, or terminal device 130.

[0146] As shown, device 1300 includes a processor 1310, a memory 1320 coupled to processor 1310, a suitable transmitter (TX) and receiver (RX) 1340 coupled to processor 1310, and a communication interface coupled to TX / RX 1340. Memory 1320 stores at least a portion of program 1330. TX / RX 1340 is configured for bidirectional communication. TX / RX 1340 has at least one antenna to facilitate communication, although in practice, the access nodes referred to in this application may have several. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 interface for bidirectional communication between base stations, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and a base station, a Un interface for communication between a base station and a relay node (RN), or a Uu interface for communication between a base station and a terminal device.

[0147] Program 1330 is assumed to include program instructions that, when executed by associated processor 1310, enable device 1300 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1 to 12 The embodiments herein may be implemented by computer software executable by the processor 1310 of the device 1300, or by hardware, or by a combination of software and hardware. The processor 1310 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1310 and the memory 1320 may form a processing component 1350 suitable for implementing various embodiments of the present disclosure.

[0148] As a non-limiting example, memory 1320 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology (e.g., non-transitory computer-readable storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory). Although only one memory 1320 is shown in device 1300, there can be several physically distinct memory modules in device 1300. As a non-limiting example, processor 1310 can be of any type suitable for a local technology network and can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor, and a processor based on a multi-core processor architecture. Device 1300 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock of a synchronized master processor.

[0149] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0150] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions (e.g., instructions contained in a program module) that are executed in a device on a target real processor or a target virtual processor to perform the above-mentioned Figure 2 、 Figure 7 、 Figure 11 、 Figure 12 Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. Machine-executable instructions for program modules can be executed on a local device or on a distributed device. In a distributed device, program modules can be located in both local and remote storage media.

[0151] The program code for executing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0152] The program code described above may be embodied on a machine-readable medium, which may be any tangible medium containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0153] In addition, although described operation in a particular order, this should not be understood as requiring to perform these operations in the particular order shown or to perform these operations in order, or requiring to perform all shown operations to obtain desired results. In some cases, multitasking and parallel processing may be advantageous. Equally, although included some specific implementation details in the above discussion, these should not be interpreted as limiting the scope of the present disclosure, but rather as a description of the possible specific features of a particular embodiment. Some features described in the context of a separate embodiment also can be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment also can be implemented separately in multiple embodiments or realized with any suitable sub-combination.

[0154] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method performed by a terminal device, comprising: determining a physical uplink control channel (PUCCH) transmission power in a PUCCH transmission opportunity, wherein the determining comprises: determining a downlink path loss estimate by using a first reference signal (RS) resource index, Wherein, based on the fact that a higher-layer parameter indicating at least one RS to be used for PUCCH path loss estimation is not provided, the first RS resource index provides an RS resource configured with quasi-co-located QCL type D in the transmission configuration indication TCI state of the control resource set CORESET, and the CORESET has the lowest index in the active bandwidth part BWP of the serving cell. The method according to claim 1 , wherein the high-level parameter is pathlossReferenceRSs.

3. A terminal device, comprising: The processor is configured to cause the terminal device to: determining a physical uplink control channel (PUCCH) transmission power in a PUCCH transmission opportunity, wherein the terminal device is caused to determine the transmission power by determining a downlink path loss estimate by using a first reference signal (RS) resource index, Wherein, based on the fact that a higher-layer parameter indicating at least one RS to be used for PUCCH path loss estimation is not provided, the first RS resource index provides an RS resource configured with quasi-co-located QCL type D in the transmission configuration indication TCI state of the control resource set CORESET, and the CORESET has the lowest index in the active bandwidth part BWP of the serving cell. The terminal device according to claim 3 , wherein the high-layer parameter is pathlossReferenceRSs.

Images