Method and terminal device

Abstract

To provide methods, devices and computer readable media for multi-TRP communication.SOLUTION: In a plurality of Transmission and Reception Point (TRP) communications, a terminal device determines a downlink pathloss estimate using a first reference signal (RS) resource, and determines transmission power of Physical Uplink Control Channel (PUCCH) transmission. If a higher layer parameter indicating at least one RS used for PUCCH pathloss estimation is not provided, the first RS resource corresponds to a second RS resource formed by quasi-colocation (QCL) type D in a Transmission Configuration Indication (TCI) state of a control resource set (CORESET) having a minimum index in an active bandwidth part (BWP) of a serving cell.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, devices, and computer storage media for multiple transmit / receive point (TRP) communications. [Background technology]

[0002] Various communication standards are being developed to provide public protocols that enable various wireless devices to communicate at municipal, national, regional, and global levels. One example of an emerging communication standard is New Radio (NR), e.g., 5G radio access. NR is a set of extensions 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)) may be equipped with multiple TRPs or multiple antenna panels. That is, the network device may 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) may be used to schedule multiple physical downlink shared channels (PDSCHs), or different DCIs may be used to schedule multiple physical uplink control channels (PUCCHs). Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, exemplary embodiments of the present disclosure provide a method, device, and computer storage medium for multi-TRP communication. [Means for solving the problem]

[0005] In a first aspect, a communication method is provided, the method including determining a first beam for a first physical shared channel scheduled by control information, the method further including determining a second beam, different from the first beam, for a second physical shared channel scheduled by the control information, the second beam performing communication on the first physical shared channel via the first beam and performing communication 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 are scheduled by different control information. The method further 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 further 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 communications is provided. The device includes a processor and a memory. The memory is coupled to the processor and has instructions stored therein. When executed by the processor, the instructions cause the device to perform operations. The operations include determining a first beam for a first physical shared channel scheduled by control information. The operations further include determining a second beam, different from the first beam, for a second physical shared channel scheduled by the control information. The operations further include performing communications on the first physical shared channel via the first beam and performing communications on the second physical shared channel via the second beam.

[0008] In a fourth aspect, a device for communications is provided. The device includes a processor and a memory. The memory is coupled to the processor and has instructions stored therein. When executed by the processor, the instructions cause the device to perform operations. The operations include determining 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. The operations further include determining, based on the first reference power and the second reference power, a first target power for performing the communications on the first uplink control channel and a second target power for performing the communications on the second uplink control channel. The operations further include performing the communications on the first uplink control channel at the first target power and the second target power.

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

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

[0011] Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0012] Hereinafter, several embodiments of the present disclosure will be described in more detail in the drawings, which will make the above and other objects, features, and advantages of the present disclosure more apparent.

[0013] [Figure 1] 1 illustrates an exemplary communication network in which some embodiments of the present disclosure may be implemented.

[0014] [Figure 2] 1 shows a schematic diagram of an exemplary process according to some embodiments of the present disclosure.

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

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

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

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

[0019] [Figure 7]1 shows a schematic diagram of an exemplary process according to some embodiments of the present disclosure.

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

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

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

[0023] [Figure 11] 1 illustrates an exemplary method according to some embodiments of the present disclosure.

[0024] [Figure 12] 1 illustrates an exemplary method according to some embodiments of the present disclosure.

[0025] [Figure 13] FIG. 1 is a schematic block diagram of a device adapted to implement an embodiment of the present disclosure.

[0026] In all the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0027] The principles of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that the descriptions of these embodiments are merely for illustrative purposes, to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitations 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 otherwise defined, 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] The term "network device" or "base station" (BS) as used herein refers to a device capable of providing or hosting a cell or coverage over 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 (eNode B or eNB), a next generation Node B (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a femto node, a pico node, etc. For discussion purposes, the following text describes some embodiments 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, cell phones, smart phones, personal digital assistants (PDAs), handheld computers, image capture devices such as digital cameras, gaming devices, music storage and playback devices, or Internet devices capable of wirelessly or wiredly accessing or browsing the Internet.

[0031] When used in context, the singular forms "a," "an," and "the" are intended to include the plural form unless the context clearly dictates otherwise. The term "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "an 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. can refer to different or the same object. Other definitions may be included, both explicitly and implicitly, in the following description.

[0032] In some instances, values, processes, or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate choices among multiple functional alternatives used, and that such choices are not necessarily better, lesser, higher, or more preferred than other choices.

[0033] In one embodiment, a terminal device can be connected to a first network device and a second network device. One of the first network device and the second network device can be a master node and the other can be a secondary node. The first network device and the second network device can use different radio access technologies (RATs). In one embodiment, the first network device can be a first RAT device, and the second network device can 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 the different RATs can be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, the first information can be transmitted from the first network device to the terminal device, and the second information can 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 for the terminal device configured by the second network device can be transmitted from the second network device via the first network device. Additionally, information related to a reconfiguration for the terminal device configured by the second network device may be transmitted from the second network device to the terminal device directly or via the first network device.

[0034] FIG. 1 illustrates an exemplary communication network 100 in which embodiments of certain aspects of the present disclosure may be implemented. The network 100 includes a network device 110. The network device 110 is coupled to two TRPs / panels 130-1 and 130-2 (collectively referred to as TRPs 130 or individually referred to as TRPs 130). The network 100 further includes a terminal device 120 served by the network device 110. The serving area of ​​the network device 110 is referred to as a 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 in any way. The 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 within the cell 102 and may be served by the 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 in a particular geographic location. For example, a network device may achieve better coverage by combining with multiple TRPs in different geographic locations. Alternatively or additionally, multiple TRPs may be incorporated into a network device, 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." A TRP may also refer to an antenna array (having one or more antenna elements) or an antenna set. It should also be understood that a TRP may refer to a logical concept that can be physically realized in various ways.

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

[0037] Depending on the communication technology, network 100 may 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. Communications discussed with respect to network 100 may conform to any appropriate 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. Communications may also be performed based on any currently known or future generation of communication protocols. 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 techniques described herein may be used in the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, some aspects of these technologies are described below with respect to LTE, and LTE terminology is used in much of the description below.

[0038] 1, the network device 110 can communicate with the terminal device 120 via TRPs 130-1 and 130-2. In the following text, the TRP 130-1 may also be referred to as a first TRP, and the TRP 130-2 may also be referred to as a second TRP. Each of the TRPs 130 can provide multiple beams for communication with the terminal device 120. The first TRP 130-1 and the second TRP 130-2 may be included in the same serving cell (e.g., cell 102 shown in FIG. 1) provided by the network device 110, or may be included 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 in the same serving cell 102 provided by the network device 110, these embodiments are merely for illustrative purposes to assist those skilled in the art in understanding and practicing the present disclosure and are not intended to imply any limitation on the scope of the present disclosure. Embodiments of the present disclosure may also be implemented in a network in which the TRPs 130 are in different serving cells provided by the network device 110. It should be understood that the present disclosure described herein can be implemented in various ways other than those described below.

[0040] As described above, in some multi-TRP communication schemes, a single DCI may be used to schedule multiple PDSCHs, or different DCIs may be used to schedule multiple PUCCHs. For example, a network device may schedule two PDSCHs using a single DCI, where each PDSCH corresponds to one of two TRPs. It takes time for a terminal device to decode the DCI to determine information about the two PDSCHs. Before the DCI is decoded, the terminal device may not have knowledge of the beams indicated by the network device for the two PDSCHs. This may result in delays when performing PDSCH transmission. To reduce the delay, the terminal device may perform PDSCH transmission using a default beam before the DCI is decoded. However, when there are two PDSCHs requiring different beams, such as in the case of two TRPs, it is necessary to determine how to select a beam 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 included in the transmission configuration indicator (TCI) status. As used herein, the beam for PDSCH is used for reception.

[0042] Exemplary embodiments of the present disclosure provide a solution for multi-TRP communication that supports beam selection for different PDSCHs or for different parts of a PDSCH, thereby reducing downlink transmission latency and achieving high performance.

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

[0044] 2, the network device 110 may transmit control information (e.g., DCI) to the terminal device 120 (205). The control information may schedule multiple physical shared channels, each 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 second TRP 130-2.

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

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

[0047] In some exemplary embodiments, both the first beam and the second beam may be default beams. Referring to FIG. 3, FIG. 3 shows a schematic diagram 300 illustrating multiple PDSCHs according to some embodiments of the present disclosure. As shown in FIG. 3, DCI 301 may schedule a first PDSCH 311 corresponding to a first TRP 130-1 and a second PDSCH 312 corresponding to a second TRP 130-2. Time 321 represents the time when monitoring of the PDCCHs ends, and time 322 represents the time when decoding of DCI 301 is completed and / or the new beam indicated by DCI 301 is ready to receive the PDSCH.

[0048] Because DCI 301 has not been decoded, in the time interval between time 321 and time 322, terminal device 120 may use two different default beams to perform communication on PDSCHs (e.g., first PDSCH 311 and second PDSCH 312). It should be noted that the PDSCHs scheduled by a single DCI are referred to as the first PDSCH and second PDSCH, but may also be referred to as a first portion of the PDSCH and a second portion of the PDSCH.

[0049] In some exemplary embodiments, the first beam may be determined based on a control resource set (CORESET) configured to monitor control information. A CORESET set or a 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. As shown in FIG. 3, CORESET 331 and CORESET 332 may be configured in the terminal device 120 to monitor the PDCCH. Also, DCI 301 may be monitored in CORESET 331. A 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 may correspond to the first TRP 130-1 in other ways.

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

[0051] In some exemplary 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 at least two TCI states having QCL Type-D information. 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 configured to monitor control information (i.e., exemplary CORESET 331 shown in FIG. 3 ).

[0052] As another example, the first beam and the second beam may be determined based on a CORESET having the lowest CORESET ID. As shown in FIG. 3, 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 a CORESET having the lowest CORESET ID from the CORESET set or CORESET group (e.g., CORESETs 331 and 332).

[0053] In some demonstrative 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 the MAC CE for a PDSCH (e.g., the first PDSCH 311) corresponding to the first TRP 130-1. Meanwhile, the second set of TCI states may be activated by the MAC CE for a PDSCH (e.g., the second PDSCH 312) corresponding to the second TRP 130-2. 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 a TCI state having the lowest ID in each set of TCI states.

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

[0055] 2, after determining the first beam and the second beam, the terminal device 120 performs communication on the first physical shared channel via the first beam and performs communication on the second physical shared channel via the second beam (220). For example, the terminal device 120 can 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 exemplary embodiments, when performing communications, a switch between the first beam and the second beam is performed based on criteria defined in the time domain. Referring now to FIG. 4, FIG. 4 shows a schematic diagram 400 illustrating multiple PDSCHs according to some embodiments of the present disclosure. As shown in FIG. 4, DCI 401 can schedule a first PDSCH 411 corresponding to a first TRP 130-1 and a second PDSCH 412 corresponding to a second TRP 130-2. Time 421 represents the time when monitoring of the PDCCH ends, and time 422 represents the time when decoding of DCI 401 is completed and / or the new beam indicated by DCI 401 is ready to receive the PDSCH.

[0057] 4, DCI 401, first PDSCH 411, and second PDSCH 412 are all in the same slot 410. Because 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 times 421 and 422. For example, a first beam may be used before time 423, and a second beam may be used after time 423. Thus, a receive beam switch occurs at time 423. The first and second beams may be determined as described with respect to any of the example embodiments above.

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

[0059] In some exemplary embodiments, one or more CORESETs having a search space (SS) to monitor may be associated with Ultra Reliability Low Latency Communication (URLLC). 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. In such exemplary embodiments, a URLLC CORESET may be prioritized over a non-URLLC CORESET. The above example regarding a default beam for a 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. If 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. If only a non-URLLC CORESET having an SS for monitoring DCI exists in a slot, a transmission scheme based on a single TRP may be applied.

[0060] In some exemplary embodiments, when performing communications, switching between the first beam and the second beam is performed based on criteria defined in the frequency domain. Referring now to FIG. 5, FIG. 5 shows a schematic diagram 500 illustrating multiple PDSCHs in accordance with some embodiments of the present disclosure. As shown in FIG. 5, DCI 501 can schedule a first PDSCH 511 corresponding to a first TRP 130-1 and a second PDSCH 512 corresponding to a second TRP 130-2. Time 521 represents the time when monitoring of the PDCCHs ends, and time 522 represents the time when decoding of DCI 501 is completed and / or the new beam indicated by DCI 501 is ready to receive the PDSCH.

[0061] 5, DCI 501, first PDSCH 511, and second PDSCH 512 are all in the same slot 510. Because DCI 501 has not been decoded, in the time interval between time 521 and time 522, terminal device 120 may perform communication on the PDSCH using a default beam. For example, a first beam may be used for resources whose frequencies are above threshold frequency 523, and a second beam may be used for resources whose frequencies are below threshold frequency 523. In this manner, receive beam switching occurs at threshold frequency 523. The first and second beams may be determined as described with respect to any of the above example embodiments.

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

[0063] In some embodiments, a URLLC CORESET may be prioritized over a non-URLLC CORESET, as described above with reference to Figure 4. For example, CORESET 531 for monitoring DCI 501 is a URLLC CORESET, and CORESET 532 is a non-URLLC CORESET. If URLLC CORESET 531 and non-URLLC CORESET 532 overlap in the time domain for DCI monitoring and the beams associated with the two CORESETs are different, the DCI monitoring associated with URLLC CORESET 531 may be prioritized and the DCI monitoring associated with CORESET 531 may be ignored.

[0064] Some exemplary embodiments in which both the first beam and the second beam are default receive beams have been described above. In some exemplary embodiments, one of the first beam and the second beam may not be the default receive beam but may be a beam determined based on control information. Referring now to FIG. 6, FIG. 6 is a schematic diagram illustrating multiple PDSCHs according to some embodiments of the present disclosure. As shown in FIG. 6, DCI 601 may schedule a first PDSCH 611 corresponding to a first TRP 130-1 and a second PDSCH 612 corresponding to a second TRP 130-2. Time 621 represents the time at which monitoring of the PDCCHs ends.

[0065] As shown in FIG. 6 , the DCI 601 and the first PDSCH 611 are in the same slot 610. The second PDSCH 612 is in the slot 620 after the slot 610. In this case, the terminal device 120 can communicate over the first PDSCH 611 using the first beam. The first beam may be the default beam described with respect to any of the example embodiments above. Because the second PDSCH 612 is scheduled in the next slot 620, the DCI 601 may be decoded before the reception of the second PDSCH 612. In this manner, the second beam may be determined based on the DCI 601 without using the default beam.

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

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

[0068] As one example, when the field “tci-PresentlnDCI” is set to “enabled” and tci-PresentlnDCI is not set to Radio Resource Control (RRC) connected mode, if the offset between the reception of the DL DCI and the reception of the corresponding first part of the PDSCH is smaller than timeDurationForQCL, the terminal device may assume that the demodulation reference signal (DM-RS) port of the first part of the PDSCH (or in other words, the first PDSCH) of the serving cell is quasi-co-located with the RS for the QCL parameter used in the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space having the lowest CORESET-ID in the most recent slot, where one or more CORESETs in the active bandwidth portion (BWP) of the serving cell are monitored by the terminal device in the most recent slot. If the offset between reception of the DL DCI and reception of the corresponding second part of the PDSCH is greater than a threshold timeDurationForQCL, the terminal device determines the quasi-co-location of the antenna ports for the second part of the PDSCH using the TCI state, which is based on the value of the 'Transmission Configuration Indication' field of the detected PDCCH that carries the DCI.

[0069] Some exemplary embodiments have been described above to explain, for example, determining a receive beam for a PDSCH in a multi-TRP scenario. In this way, by using a default receive beam, the delay due to decoding of control information can be reduced. Furthermore, the delay due to beam switching can also be reduced.

[0070] As mentioned above, in some multi-TRP communication schemes, different DCIs may be used to schedule multiple PUCCHs, which may correspond to different TRPs, and therefore a power control mechanism between such PUCCHs needs to be addressed.

[0071] The terminal device calculates the PUCCH transmission power P PUCCH,b,f,c (i,q u ,q d , i) can be determined. TIFF0007729373000001.tif11157(1)

[0072] term P O_PUCCH,b,f,c (q u ) is the component P O_NORMAL_PUCCH and component P O_UE_PUCCH (q u ) and the cell-specific parameter P O_NORMAL_PUCCH is P O_NORMAL and is given in the field "in PUCCH-ConfigCommon". O_UE_PUCCH (q u ) is P O_UE This can be referred to as "pO-Set" included in PUCCH-PowerControl. b,f,c (q d ) is the RS resource index q d is the downlink path loss estimate calculated by the terminal device using b,f,c (q d ) may also be referred to herein as a path loss RS.

[0073] In the multi-TRP communication scheme, the above parameter P O_NORMAL , P O_UE , the path loss RS and the closed-loop index l need to be determined. Also, the actual power for transmitting on the PUCCH corresponding to different TRPs may need to be adjusted.

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

[0075] 7, the network device 110 may transmit (705) different control information to the terminal device 120. For example, the network device 110 may transmit different DCIs corresponding to different TRPs. The different control information may schedule different uplink control channels.

[0076] Referring now to FIG. 8, FIG. 8 shows a schematic diagram 800 illustrating multiple PUCCHs according to some embodiments of the present disclosure. As shown in FIG. 8, a first DCI 801 can schedule a first PUCCH 811, and a second DCI 802 can schedule a second PUCCH 812. The first DCI 801 can correspond to a first TRP 130-1. For example, the first DCI 801 can be monitored in a first CORESET group 831. The first CORESET group 831 can be configured for the first TRP 130-1. Similarly, the second DCI 802 can correspond to a second TRP 130-2. For example, the second DCI 802 can be monitored in a second CORESET group 832. The second CORESET group 832 can be configured for the second TRP 130-2.

[0077] 7 again, the terminal device 120 determines a first reference power P1 for performing communication 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 is determined (710). initial and second reference power P2 initial can be determined based on the above-mentioned formula (1). In the following, some exemplary embodiments will be presented to determine the above-mentioned parameter P O_NORMAL , P O_UE , a method for determining the path loss RS and the closed-loop index l will be described.

[0078] In some exemplary embodiments, different TRPs or different CORESET groups are determined by a cell-specific parameter P O_NORMAL For example, the network device 110 may support different values ​​of the parameter P O_NORMALTwo values ​​can be set for TRP_ID, where each of the two values ​​corresponds to one TRP or one CORESET group. The two values ​​may be included in the radio resource control (RRC) signaling of the terminal device 120. Exemplary information elements for indicating these values ​​may be as follows: TIFF0007729373000002.tif2996

[0079] It should be understood that the above information elements are provided for illustrative purposes only and are not intended to be limiting, and values ​​may be indicated to terminal device 120 in a variety of suitable ways.

[0080] In this exemplary embodiment, P for PUCCH according to DCI corresponding to CORESET group / TRP O_NORMAL A value can be associated with the CORESET group / TRP. In the example shown in FIG. 8, P for the first PUCCH 811 O_NORMAL The value can be determined based on the example information element "p0-normal_TRP1". O_NORMAL The value can be determined based on the example information element "p0-normal_TRP2".

[0081] In some exemplary embodiments, P for different PUCCHs O_UE The value may be determined in a default manner, for example, without specific instructions from the network device 110. The terminal device 120 may use the P O_UE Get a set of values ​​and use this P O_UE Select two values ​​from the set of values ​​to set the reference power P1 initial and P2 initial For example, the default value used by the terminal device 120 may be, for example, P0-PUCCH-Id with values ​​0 and 1. O_UE It may be a value.

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

[0083] In some exemplary embodiments, terminal device 120 uses a default path loss RS to set a reference power P1 initial and P2 initial A first path loss RS of the first uplink control channel can be determined based on the first control information, and a second path loss RS can be determined based on the second control information.

[0084] In some exemplary embodiments, terminal device 120 may determine a pathloss 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 first control information and determine a first pathloss RS based on the SSB / PBCH block. Terminal device 120 may further select a CORESET from a group of CORESETs configured to monitor second control information and determine a second pathloss RS based on the selected CORESET.

[0085] In other words, if the terminal device 120 is not provided with pathlossReferenceRSs, or before the terminal device 120 is provided with dedicated upper layer parameters, the terminal device 120 may use RS resources obtained from the SS / PBCH block that the terminal device 120 uses to obtain a Master Information Block (MIB) for the first TRP to calculate the pathloss PL for the first uplink control channel. b,f,c (qd The terminal device 120 may calculate the PL for the second uplink control channel using the RS resources corresponding to the QCL RSs of the CORESET with the lowest ID associated with the second TRP. b,f,c (q d ) may be calculated.

[0086] 8, the first pathloss RS for the first PUCCH 811 may be determined based on the SS / PBCH block that the terminal device 120 uses to obtain the MIB for the first TRP 130-1. The second pathloss RS for the second PUCCH 812 may be determined based on the CORESET (e.g., having the lowest ID) in the second CORESET group 832 corresponding to the second TRP 130-2.

[0087] In some exemplary embodiments, terminal device 120 may determine a pathloss 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 pathloss RS based on the first CORESET. Terminal device 120 may further select a second CORESET from a second group of CORESETs configured to monitor second control information and determine a second pathloss RS based on the second CORESET.

[0088] In other words, if the terminal device 120 is not provided with pathlossReferenceRSs, or before the terminal device 120 is provided with dedicated upper layer parameters, the terminal device 120 uses RS resources corresponding to the QCL RS of the CORESET with the lowest ID associated with the first TRP, and calculates the pathloss PL for the first uplink control channel. b,f,c (q dThe terminal device 120 may use the RS resources corresponding to the QCL RSs of the CORESET with the lowest ID associated with the second TRP to calculate the path loss PL b,f,c (q d ) may be calculated.

[0089] 8, the first pathloss 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. The second pathloss 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.

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

[0091] In some exemplary embodiments, a UE-specific parameter P O_UEOne or more of the values, path loss RS, and closed loop index (CLI) may be indicated by the MAC CE from the network device 110. Table 1 shows an example structure A of a MAC CE for indicating power control parameters. In this example, the field "LCI or TRPID" (CLI or TRPID) may be used to indicate the closed loop index l and / or the corresponding TRP. In this case, the UE-specific parameters P for the first PUCCH and the second PUCCH O_UE The value and path loss RS may be determined as described in the exemplary embodiment above, or in any other suitable manner. Table 1: Exemplary structure of MAC CE A TIFF0007729373000003.tif36111

[0092] 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 a MAC CE further includes a field "PO_and_PL_RS1" and a field "PO_and_PL_RS1". The field "PO_and_PL_RS1" indicates the PUCCH used for the first uplink control channel (e.g., the first PUCCH 811 shown in FIG. 8). O_UE The field "PO_and_PL_RS2" indicates the P value and the first path loss RS used for the second uplink control channel (e.g., the second PUCCH 812 shown in FIG. 8). O_UE The values ​​and second path loss RS are shown. Table 2: Exemplary structure of MAC CE B TIFF0007729373000004.tif39112

[0093] Table 3 shows an example MAC CE structure C for indicating power control parameters. The example MAC CE structure C includes fields of bitmap S7...S0. Bits S i (i=0,...,7) with value "1" indicate P used for uplink control channels. O_UEActivate the i-th power control setting of value, path loss RS index, and / or closed loop index value (i>=0). Exemplary power control settings can be as follows: TIFF0007729373000005.tif35114 Exemplary structure of MAC CE C TIFF0007729373000006.tif37116

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

[0095] Referring again to Figure 7, the terminal device 120 determines (715) 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. In some exemplary embodiments, the first reference power P1 initial and second reference power P2 initial The terminal device 120 may adjust the actual power of the first PUCCH and the second PUCCH based on the first target power and the second target power. The terminal device 120 may perform 720 communication on the first uplink control channel using the first target power and may perform 720 communication on the second uplink control channel using the second target power.

[0096] In some exemplary embodiments, transmissions on the first uplink control channel and the second uplink channel may be performed at 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 start of the second uplink control channel. If the time gap is less 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, the maximum or minimum value of the first reference power and the second reference power may be used as the common power.

[0097] Referring now to FIG. 9, FIG. 9 shows a schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure. As shown in FIG. 9, a first DCI 901 can schedule a first PUCCH 911, and a second DCI 902 can schedule a second PUCCH 912. The first DCI 901 can correspond to a first TRP 130-1. For example, the first DCI 901 can be monitored in a first CORESET group 931. The first CORESET group 931 can be configured for the first TRP 130-1. Similarly, the second DCI 902 can correspond to a second TRP 130-2. For example, the second DCI 902 can be monitored in a second CORESET group 932. The second CORESET group 932 can be configured for the second TRP 130-2.

[0098] The first reference power, or power indicated for transmission on the first PUCCH 911, is P1 initial On the other hand, the second reference power, or the power indicated for transmission on the second PUCCH 912, can be expressed as P2 initial9, the first PUCCH 911 does not overlap with 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 start 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) a time for the terminal device 120 to adjust its transmit power.

[0099] If the time gap 920 is smaller than the threshold gap, the terminal device 120 may transmit at a common power in both the first PUCCH 911 and the second PUCCH 912. The common power may be P1 initial and P2 initial It may be the maximum value of P1 initial and P2 initial Alternatively, the common power may be the minimum value of P1 initial and P2 initial For example, P1 initial and P2 initial It may be the average value of

[0100] If the time gap 920 is equal to or greater than the threshold gap, the terminal device 120 may separately initial The first PUCCH 911 is transmitted at a transmit power of P1 initial Therefore, transmission can be performed on the first PUCCH 911 with this transmission power. 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.

[0101] In some exemplary embodiments, when 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.

[0102] Referring now to FIG. 10, FIG. 10 shows a schematic diagram illustrating multiple PUCCHs according to some embodiments of the present disclosure. As shown in FIG. 10, a first DCI 1001 can schedule a first PUCCH 1011, and a second DCI 1002 can schedule a second PUCCH 1012. The first DCI 1001 can correspond to a first TRP 130-1. For example, the first DCI 1001 can be monitored in a first CORESET group 1031. The first CORESET group 1031 can be configured for the first TRP 130-1. Similarly, the second DCI 1002 can correspond to a second TRP 130-2. For example, the second DCI 1002 can be monitored in a second CORESET group 1032. A second CORESET group 1032 can be configured for a second TRP 130-2.

[0103] Maximum power P CMAX can be set for each of the first TRP and the second TRP. For example, the first maximum power P CMAX,1 corresponds to the first TRP130-1, and the second maximum power P CMAX,2may correspond to the second TRP 130-2. For ease of discussion, the first target power for performing transmission in the first PUCCH 1011 and the second target power for performing transmission in the second PUCCH 1012 may be denoted as P1 and P2, respectively. The sum of the first target power P1 and the second target power P2 is the first maximum power P CMAX,1 and the second maximum power P CMAX,2 The total transmission power can be shared between the first PUCCH 1011 and the second PUCCH 1012 so that the total transmission power is equal to or less than the sum of (1) and (2). That is, the following equation (2) is satisfied. TIFF0007729373000007.tif560(2)

[0104] 1st reference power P1 initial and the second reference power P2 initial The sum of the first maximum power P CMAX,1 and the second maximum power P CMAX,2 If the terminal device 120 determines that the sum of P1 initial +P2 initial > P CMAX,1 +P CMAX,2 If so, the terminal device 120 sets the first reference power P1 initial and second reference power P2 initial The actual power for PUCCH transmission can be adjusted based on the first target power P1 and the second target power P2. initial and second reference power P2 initial For example, the ratio of P1 to P2 may be determined based on P1 initial and P2 initial It may be equal to the ratio of

[0105] The duration for which the PUCCH transmit power is shared between the two PUCCHs may be determined by the union of the duration of the first PUCCH and the duration of the second PUCCH. As shown in Figure 10, the power allocation between the first PUCCH 1011 and the second PUCCH 1012 occurs during time interval 1020.

[0106] 11 illustrates a flowchart of an example method 1100 according to some embodiments of the present disclosure. Method 1100 may be implemented in terminal device 120 shown in FIG. 1. It should be understood that method 1100 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect. For purposes of discussion, method 1100 will be described from the perspective of terminal device 120 with reference to FIG. 1.

[0107] In block 1110, terminal device 120 determines a first beam for a first physical shared channel scheduled by the control information. In some exemplary embodiments, the first beam may be a default beam used before the control information is decoded and / or a default beam used before switching to a new beam indicated by the control information. In 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.

[0108] In some exemplary embodiments, the terminal device 120 may select a CORESET from a group of CORESETs configured to monitor control information and determine a beam associated with the selected CORESET as the first beam. The terminal device 120 may further select a TCI state from a set of TCI states available in the second physical shared channel and determine a beam corresponding to the selected TCI state as the second beam.

[0109] In some demonstrative embodiments, terminal device 120 may select a CORESET from a group of CORESETs for which it is configured to monitor control information. The selected CORESET may be associated with at least two beams. Terminal device 120 may further select a first beam and a second beam from the at least two beams.

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

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

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

[0113] In some demonstrative embodiments, terminal device 120 may determine a time within the time interval at which control information is received, and may perform communication on a first physical shared channel via a first beam before that time and on a second physical shared channel via a second beam after that time.

[0114] In some exemplary embodiments, terminal device 120 may perform communication on a first physical shared channel via a first beam using first resources whose frequency exceeds a threshold frequency, and terminal device 120 may perform communication on a second physical shared channel via a second beam using second resources whose frequency exceeds a threshold frequency.

[0115] In some exemplary embodiments, terminal device 120 receives control information in a first time interval. Terminal device 120 may perform communications 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 is after the first time interval.

[0116] In some exemplary embodiments, terminal device 120 may further determine a first reference power for performing communication on the first uplink control channel and a second reference power for performing communication on the second uplink control channel. The first uplink control channel and the second uplink control channel are 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 using the first target power and perform communication on the second uplink control channel using the second target power.

[0117] 12 illustrates a flowchart of an exemplary method 1200 according to some embodiments of the present disclosure. Method 1200 may be implemented in terminal device 120, as shown in FIG. 1. It should be understood that method 1200 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect. For purposes of discussion, method 1200 will be described from the perspective of terminal device 120 with reference to FIG. 1.

[0118] In block 1210, the terminal device 120 determines 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.

[0119] In some demonstrative embodiments, terminal device 120 may obtain a set of power control parameters specific to the terminal device, configured by a network device, and may select two power control parameters from the set of power control parameters, each power control parameter for determining one of the first reference power and the second reference power.

[0120] In some exemplary embodiments, the first uplink control channel is scheduled by the first control information, and the second uplink control channel is scheduled by the second control information. Terminal device 120 may determine, based on the first control information and the second control information, 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.

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

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

[0123] In some demonstrative embodiments, terminal device 120 may receive a media access control (MAC) control element (CE) from network device 110. The MAC CE includes at least a field indicating power control parameters. Terminal device 120 may determine a first reference power and a second reference power based on the MAC CE.

[0124] In block 1220, the terminal device 120 determines 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.

[0125] In some exemplary 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 start of the second uplink control channel. If the time gap is less than a threshold gap, terminal device 120 may determine a common target power for performing both 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.

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

[0127] In some exemplary 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 a 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 first target power and second target power such that a second sum of the first target power and the second target power is less than the maximum power.

[0128] At block 1230, the terminal device 120 performs communication on a first uplink control channel using a first target power and performs communication on a second uplink control channel using a second target power.

[0129] 13 is a simplified block diagram of an apparatus 1300 suitable for implementing embodiments of the present disclosure. The device 1300 can be considered another example implementation of the network device 110, the TRP 130, or the terminal device 130 shown in FIG. 1. Thus, the device 1300 can be implemented in the network device 110, the TRP 130, or the terminal device 130, or can be implemented as at least a part of the network device 110, the TRP 130, or the terminal device 130.

[0130] 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 a program 1330. TX / RX 1340 is used for bidirectional communication. TX / RX 1340 has at least one antenna to facilitate communication; in practice, access nodes described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network components, 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.

[0131] Assuming that the program 1330 includes program instructions that, when executed by an associated processor 1310, can cause the device 1300 to perform operations according to embodiments of the present disclosure, as described herein with reference to FIGS. 1-12. The embodiments of the present disclosure may be implemented by computer software executable by the processor 1310 of the device 1300, by hardware, or by a combination of software and hardware. The processor 1310 can be configured to implement embodiments of the present disclosure. Additionally, the combination of the processor 1310 and the memory 1320 can constitute a processing element 1350 suitable for implementing embodiments of the present disclosure.

[0132] By way of non-limiting example, memory 1320 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology (e.g., computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memory, etc.). Although only one memory 1320 is shown in device 1300, multiple physically distinct memory modules may be installed in device 1300. By way of example, processor 1310 may be of any type suitable for a local technology network and may include, but is not limited to, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor, and a processor based on a multi-core processor configuration. Device 1300 may have multiple processors, e.g., application-specific integrated circuit chips time-slaved to a clock that synchronizes a master processor.

[0133] Generally, embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. While aspects of embodiments of the present disclosure may be shown and described as block diagrams, flowcharts, or represented by some other graphic representation, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented in, for example, but not limited to, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0134] The present disclosure further provides at least one computer program product tangibly stored on a computer-readable, non-transitory storage medium. The computer program product includes computer-executable instructions (e.g., instructions contained in program modules) that execute on a target real or virtual processor device to perform the processes or methods described above with reference to Figures 2, 7, 11, and 12. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split among program modules as desired. Device-executable instructions contained in program modules may be executed in a local device or in a distributed device. In a distributed device, program modules may reside in both local and remote storage media.

[0135] The program code for carrying out the methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, the program code can perform the functions / operations specified in the flowcharts and / or block diagrams. The program code can be executed entirely on a machine, or partially on a machine, or as a separate software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0136] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program used by or in connection 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 one or more electrical connections of cables, a portable computer magnetic 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.

[0137] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order or sequence shown, or performing all of the operations shown, is required to achieve desired results. In some situations, multiple tasks and parallel processing may be advantageous. Similarly, while the above discussion includes several specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be unique to particular embodiments. Some features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments alone or in any suitable subcombination.

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

Claims

1. determining a physical uplink control channel (PUCCH) transmit power in a PUCCH transmission opportunity; The determining includes determining a downlink path loss estimate by using a first reference signal (RS) resource index; When 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 in quasi-colocation (QCL) type D in a transmission configuration indicator (TCI) state of a control resource set (CORESET) having a lowest index in an active bandwidth portion (BWP) of a serving cell. A method performed by a terminal device.

2. The upper layer parameter is pathlossReferenceRSs. The method of claim 1.

3. A means for determining a physical uplink control channel (PUCCH) transmission power for a PUCCH transmission opportunity, The means for determining a transmit power includes means for determining a downlink path loss estimate by using a first reference signal (RS) resource index; When 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 in quasi-colocation (QCL) type D in a transmission configuration indicator (TCI) state of a control resource set (CORESET) having a lowest index in an active bandwidth portion (BWP) of a serving cell. Terminal device.

4. The upper layer parameter is pathlossReferenceRSs. The terminal device according to claim 3 .

Images