Method, apparatus, and computer-readable medium for multiple TRP transmission

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer-readable media for multiple transmit and receive point (TRP) transmissions. In an example embodiment, a communication method includes determining, at a network device, a first configuration of a first set of resources for a first TRP coupled to the network device, and a second configuration of a second set of resources for a second TRP coupled to the network device, the first set of resources and the second set of resources being used for downlink shared channel transmissions, and the first set of resources and the second set of resources not overlapping in the frequency domain. The method also includes sending the first configuration to the first TRP and sending the second configuration to the second TRP.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of communications, and more particularly, to methods, devices, and computer-readable media for multiple transmit and receive point (TRP) transmissions. Background Art

[0002] Communication technologies have been developed in various communication standards to provide common protocols that enable different wireless devices to communicate at the 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 Third Generation Partnership Project (3GPP). It is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards by using OFDMA with a cyclic prefix (CP) on the downlink (DL) and uplink (UL), better support mobile broadband Internet access, and support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0003] In NR, a network device (e.g., gNodeB) may be equipped with multiple TRPs or antenna panels. That is, the network device may communicate with a terminal device (e.g., user equipment UE) via one or more of the multiple TRPs. Various indications may be sent to the terminal device via different TRPs to indicate to the terminal device the resources configured for the scheduled transmission. Therefore, it is necessary to address the issue of resource conflicts caused by indications from different TRPs. Summary of the Invention

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

[0005] In a first aspect, a communication method is provided. The method includes: determining, at a network device, a first configuration of a first set of resources for a first transmit and receive point (TRP) coupled to the network device, and a second configuration of a second set of resources for a second TRP coupled to the network device, the first set of resources and the second set of resources being used for downlink shared channel transmission, and the first set of resources and the second set of resources being non-overlapping in the frequency domain; and sending the first configuration to the first TRP and sending the second configuration to the second TRP.

[0006] In a second aspect, a communication method is provided. The method includes: receiving, at a transmit and receive point (TRP), a first configuration of a first set of resources from a network device coupled to the TRP, the first set of resources not overlapping with a second set of resources in a frequency domain, the second set of resources being determined by the network device for use in another TRP coupled to the network device, the first set of resources and the second set of resources being used for downlink shared channel transmission; and performing downlink shared channel transmission based on the first set of resources.

[0007] In a third aspect, a communication method is provided. The method includes: in response to receiving a random access preamble from a terminal device at a transmission and reception point (TRP), determining a set of resources for downlink shared channel transmission with the terminal device; and sending an indication of the determined set of resources to another TRP communicating with the terminal device, so that the other TRP communicates with the terminal device using resources other than the determined set of resources.

[0008] In a fourth aspect, a communication method is provided. The method includes: determining, at a terminal device, a first set of resources for a first transmission based on a first indication received via a first transmit and receive point (TRP) coupled to a network device, the first transmission to be performed between the terminal device and the network device via the first TRP; determining, based on a second indication received via a second TRP coupled to the network device, a second set of resources for a second transmission to be performed between the terminal device and the network device via the second TRP; and in response to the first set of resources and the second set of resources overlapping in at least one of a time domain and a frequency domain, performing at least one of the first transmission and the second transmission to reduce interference between the first transmission and the second transmission.

[0009] In a fifth aspect, a communication method is provided. The method includes: at a terminal device, sending a scheduling request for allocation of uplink resources to a network device; receiving a response from the network device, the response indicating the uplink resources allocated to the terminal device; and, using the uplink resources, sending cell-specific information to the network device, the cell-specific information including a cell index of a serving cell and transmission control information for the serving cell provided by the network device to the terminal device.

[0010] In a sixth aspect, a communication method is provided. The method includes: receiving, at a network device, a scheduling request for allocation of uplink resources from a terminal device; sending a response to the terminal device, the response indicating the uplink resources allocated to the terminal device; and receiving, by using the uplink resources, cell-specific information from the network device, the cell-specific information including a cell index of a serving cell and transmission control information for the serving cell provided by the network device to the terminal device.

[0011] In a seventh aspect, a device is provided, comprising a processor and a memory, the memory being coupled to the processing unit and storing thereon instructions, which, when executed by the processing unit, cause the device to perform the method according to the first aspect.

[0012] In an eighth aspect, a device is provided, comprising a processor and a memory, wherein the memory is coupled to the processing unit and stores instructions thereon, which, when executed by the processing unit, cause the device to perform the method according to the second aspect.

[0013] In a ninth aspect, a device is provided, comprising a processor and a memory, wherein the memory is coupled to the processing unit and stores instructions thereon, which, when executed by the processing unit, cause the device to perform the method according to the third aspect.

[0014] In a tenth aspect, a device is provided, comprising a processor and a memory, the memory being coupled to the processing unit and storing thereon instructions, which, when executed by the processing unit, cause the device to perform the method according to the fourth aspect.

[0015] In an eleventh aspect, a device is provided, comprising a processor and a memory, wherein the memory is coupled to the processing unit and stores instructions thereon, which, when executed by the processing unit, cause the device to perform the method according to the fifth aspect.

[0016] In a twelfth aspect, a device is provided, comprising a processor and a memory, wherein the memory is coupled to the processing unit and stores instructions thereon, which, when executed by the processing unit, cause the device to perform the method according to the sixth aspect.

[0017] In a thirteenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the first aspect.

[0018] In a fourteenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the second aspect.

[0019] In a fifteenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the third aspect.

[0020] In a sixteenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the fourth aspect.

[0021] In a seventeenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the fifth aspect.

[0022] In an eighteenth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the sixth aspect.

[0023] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] 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:

[0025] Figure 1 is a schematic diagram of a communication environment in which embodiments according to some aspects of the present disclosure may be implemented;

[0026] Figure 2 is a schematic diagram illustrating the process of multi-TRP transmission;

[0027] Figure 3 A flowchart illustrating an example method according to some embodiments of the present disclosure is shown;

[0028] Figure 4 shows a schematic diagram illustrating resources for different TRPs according to some embodiments of the present disclosure;

[0029] Figure 5 A flowchart illustrating an example method according to some embodiments of the present disclosure is shown;

[0030] Figure 6 A flowchart illustrating an example method according to some embodiments of the present disclosure is shown;

[0031] Figure 7 shows a schematic diagram illustrating resources for different TRPs according to some embodiments of the present disclosure;

[0032] Figure 8 A flowchart illustrating an example method according to some embodiments of the present disclosure is shown;

[0033] Figure 9A shows a schematic diagram illustrating the handling of transmission conflicts according to some embodiments of the present disclosure;

[0034] Figure 9B shows a schematic diagram illustrating the handling of transmission conflicts according to some embodiments of the present disclosure;

[0035] Figure 9Cshows a schematic diagram illustrating the handling of transmission conflicts according to some embodiments of the present disclosure;

[0036] Figure 9D shows a schematic diagram illustrating the handling of transmission conflicts according to some embodiments of the present disclosure;

[0037] Figure 9E shows a schematic diagram illustrating the handling of transmission conflicts according to some embodiments of the present disclosure;

[0038] Figure 10 is a schematic diagram of a communication environment in which embodiments according to some aspects of the present disclosure may be implemented;

[0039] Figure 11 is a schematic diagram illustrating a process of cell-specific information transmission according to some embodiments of the present disclosure;

[0040] Figure 12 A flowchart illustrating an example method according to some embodiments of the present disclosure is shown;

[0041] Figure 13 A flowchart illustrating an example method according to some embodiments of the present disclosure; and

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

[0043] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0044] 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 the purpose of illustrating and helping those skilled in the art to understand and implement the present disclosure, without placing any limitation on the scope of the present disclosure. In addition to the methods described below, the disclosure described herein can be implemented in various other ways.

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

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

[0047] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. 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 appliances that enable wireless or wired Internet access and browsing.

[0048] 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 interpreted as open terms, meaning "including but not limited to." The term "based on" should be interpreted as "based at least in part on." The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment." The term "another embodiment" should be interpreted as "at least one other embodiment." The terms "first," "second," etc. may refer to different or the same objects. Additional definitions, both explicit and implicit, may be included below.

[0049] In some examples, 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 one can choose among many functional alternatives for use, and that such a choice is not necessarily better, smaller, higher, or otherwise superior to other choices.

[0050] Several enhancements are required for the transmission of multiple TRPs / panels over multiple physical downlink control channels (PDCCHs). It has been agreed that for UEs supporting multiple TRPs / panels over multiple PDCCHs and scheduling one physical downlink shared channel (PDSCH) per PDCCH, at least for enhanced mobile broadband (eMBB) with non-ideal backhaul, several constraints are supported. One constraint is that a UE can be scheduled over multiple PDCCHs with fully overlapping / partially overlapping / non-overlapping PDSCHs in both the time and frequency domains. The constraint includes that if a UE can be scheduled over multiple PDCCHs with fully / partially overlapping PDSCHs, it is not expected that the UE will have different DMRS configurations with respect to the actual number of front-loaded demodulation reference signal (DMRS) symbols, the actual number of additional DMRS, the actual DMRS symbol positions, and the DMRS configuration type. Further study is required for other constraints, such as the PDSCH mapping type from two co-scheduled PDSCHs and the alignment of the PRG-level grids from multiple TRPs.

[0051] As described above, a UE can receive different indications from multiple TRPs coupled to the same gNodeB. Based on an indication from one of the multiple TRPs, the UE can determine the resources configured for transmission between the UE and the gNodeB; based on an indication from another TRP in the multiple TRPs, the UE can determine another resource configured for transmission between the UE and the gNodeB. If the two resources overlap in the time and / or frequency domains, a transmission conflict occurs for the UE.

[0052] Embodiments of some aspects of the present invention provide a solution for multi-TRP transmission to solve one or more of the above-mentioned transmission conflict problems and other potential problems. Transmission conflicts can be handled on the gNodeB and TRP sides. Additionally or alternatively, transmission conflicts can be handled on the UE side. Figure 1 - Figure 9 describes in detail the principles and implementation of these aspects of the present disclosure.

[0053] Figure 1 An example communication network 100 is shown in which embodiments of some aspects of the present disclosure may be implemented. The network 100 includes a network device 110 and a terminal device 120 served by the network device 110. The service area of ​​the network device 110 is referred to as a cell 102. It should be understood that the number of network devices and terminal devices is for illustrative purposes only and is not intended to be limiting. The network 100 may include any appropriate number of network devices and terminal devices 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 the cell 102 and served by the network device 110.

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

[0055] 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 comply with any appropriate standard, including but not limited to, new radio access (NR), long term evolution (LTE), LTE evolution, advanced LTE (LTE-A), wideband code division multiple access (WCDMA), code division multiple access (CDMA), cdma2000, and global system for mobile communications (GSM). In addition, communications can be performed according to any generation of communication protocols currently known or to be 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 wireless networks and radio technologies mentioned above 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.

[0056] like Figure 1 As shown in FIG, the network device 110 is coupled to two TRPs 131 and 132 and can communicate with the terminal device 120 via the two TRPs 131 and 132. In the following, the TRP 131 may also be referred to as a first TRP, and the TRP 132 may also be referred to as a second TRP. The first TRP 131 and the second TRP 132 may be included in the same service cell provided by the network device 110 (e.g., Figure 1 102) or different serving cells. Although some embodiments of the present disclosure are described with reference to the first TRP 131 and the second TRP 132 within the same serving cell provided by the network device 110, these embodiments are only intended to illustrate and 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. It should be understood that the present disclosure described herein can be implemented in various ways other than the one described below.

[0057] In an embodiment, the terminal device 120 may receive different indications about the configured resources from the network device 110 via the two TRPs 131 and 132. For example, the terminal device 120 may receive different downlink control information (DCI) from the network device 110 via the two TRPs 131 and 132.

[0058] Figure 2 2 is a schematic diagram illustrating a process 200 for multiple TRP transmissions. Network device 110 sends 205 a first indication to terminal device 120 via first TRP 131. Terminal device 120 may determine 210 a first set of resources for the first transmission based on the first indication. Network device 110 sends 215 a second indication to terminal device 120 via second TRP 131. Terminal device 120 may determine 220 a second set of resources for the second transmission based on the second indication. In some embodiments, network device 110 may coordinate between the two TRPs 131 and 132, and no transmission collision may occur at terminal device 120. Reference will be made to FIG. Figure 3-Figure 7 In some embodiments, if a transmission conflict occurs, the terminal device 120 may determine 225 a target transmission and perform 230 at least the target transmission. Figure 8 - Figure 9 describes this embodiment.

[0059] Figure 3 A flow chart of an example method 300 according to some embodiments of the present disclosure is illustrated. The method 300 may be performed in Figure 1 It should be understood that the method 300 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 respect. For the purpose of discussion, reference will be made to Figure 1 Method 300 is described.

[0060] At block 310, network device 110 determines a first configuration of a first set of resources for a first TRP 131 coupled to network device 110, and a second configuration of a second set of resources for a second TRP 132 coupled to network device 110. The first set of resources and the second set of resources are used for downlink shared channel transmission, and the first set of resources and the second set of resources do not overlap in the frequency domain.

[0061] The resources configured for the first TRP 131 and the second TRP 132 may occupy different locations in the frequency domain, such as different resource blocks (RBs). Figure 4 , which shows a schematic diagram 400 illustrating resource configurations for different TRPs according to some embodiments of the present disclosure. Figure 4In the example shown, the height of resource 421 (in the frequency domain) may correspond to the RBs configured for the first TRP 131, and the height of resource 422 may correspond to the RBs configured for the second TRP 132. The RBs configured for TRP 131 and TRP 132 do not overlap with each other.

[0062] At block 320, the network device 110 sends the first configuration to the first TRP 131 and sends the second configuration to the second TRP 132. For example, the first configuration and the second configuration may be included in radio resource control (RRC) signaling.

[0063] Figure 5 A flow chart of an example method 500 according to some embodiments of the present disclosure is illustrated. The method 500 may be performed in a manner such as Figure 1 It should be understood that the method 500 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 respect. For the purpose of discussion, reference will be made to Figure 1 and Figure 4 The method 500 is described with respect to the first TRP 131 .

[0064] At block 510, a first TRP 131 receives a first configuration of a first set of resources from a network device 110 coupled to the first TRP 131. The first set of resources does not overlap in the frequency domain with a second set of resources, which is determined by the network device 110 for use with a second TRP 132 coupled to the network device 110. The first set of resources and the second set of resources are used for downlink shared channel transmissions.

[0065] At block 520, the first TRP 131 performs a downlink shared channel transmission based on the first set of resources. Figure 4 In the example shown, a first DCI 401 scrambled with a cell radio network temporary identifier (C-RNTI) is sent to the terminal device 120 via the first TRP 131. The terminal device 120 may determine resources 421 configured for the PDSCH based on the first DCI 401.

[0066] Similar actions may be taken by the second TRP 132. A second DCI 401 scrambled with a random access radio network temporary identifier (RA-RNTI) or a paging radio network temporary identifier (P-RNTI) is sent to the terminal device 120 via the second TRP 132. The terminal device 120 may determine the resources 422 configured for another PDSCH based on the second DCI 402.

[0067] For the purpose of discussion, the PDSCH corresponding to a particular DCI will be referred to according to the type of RNTI associated with the particular DCI. Figure 4 As shown in , the PDSCH corresponding to the DCI scrambled with C-RNTI is called C-RNTIPDSCH. The DCI associated with the C-RNTI PDSCH can be a non-fallback DCI, which is usually used after the RRC configuration for the UE. The DMRS configuration for the transmission and reception of C-RNTIPDSCH can be configured by RRC signaling. The fallback DCI is similar to the DCI formats 1_0 and 0_0 in 3GPP NR, where the corresponding DMRS configuration can be used before the configuration of the RRC signaling, for example based on the default configuration. Similarly, the PDSCH corresponding to the DCI scrambled with RA-RNTI / P-RNTI / System Information (SI)-RNTI / Modulation-Coding-Scheme (MCS)-C-RNTI is called RA-RNTI PDSCH / P-RNTIPDSCH / SI-RNTIPDSCH / MCS-C-RNTIPDSCH. The DMRS configuration used for the transmission and reception of RA-RNTIPDSCH / P-RNTIPDSCH / SI-RNTIPDSCH / MCS-C-RNTI PDSCH and C-RNTIPDSCH indicated by fallback DCI may be different from the DMRS configuration of C-RNTIPDSCH. As used herein, the term "C-RNTIPDSCH" without a prefix may refer to a PDSCH indicated by a non-fallback DCI scrambled with C-RNTI; the term "C-RNTIPDSCH indicated by fallback DCI" may refer to a PDSCH indicated by a fallback DCI scrambled with C-RNTI.

[0068] Since the first set of resources and the second set of resources configured by the network device 110 do not overlap in the frequency domain, the resources 421 used for C-RNTIPDSCH via the first TRP 131 do not overlap with the resources 422 used for RA-RNTI / P-RNTIPDSCH via the second TRP 132. In this way, both C-RNTIPDSCH and RA-RNTI / P-RNTIPDSCH transmissions can be performed by the terminal device 120 via the first TRP 131 and the second TRP 132, respectively. Other types of PDSCH transmissions (such as SI-RNTI / MCS-C-RNTIPDSCH transmissions and C-RNTIPDSCH indicated by fallback DCI) are similar to RA-RNTI / P-RNTIPDSCH transmissions. In this way, C-RNTIPDSCH transmissions via one TRP and other PDSCH transmissions via another TRP are supported. The non-overlapping resources 421 and 422 can ensure that rate matching of the resources 421 and 422 can be performed independently without being affected by different DMRS configurations on different resources.

[0069] In the above case, coordination between TRPs is implemented by network device 110. In some cases, coordination between TRPs may be implemented by the TRPs. Figure 6 A flow chart of an example method 600 according to some embodiments of the present disclosure is illustrated. The method 600 may be performed in a manner such as Figure 1 It should be understood that the method 600 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 respect. For the purpose of discussion, reference will be made to Figure 1 and Figure 7 The method 600 is described with respect to the second TRP 132 . Figure 7 Shown is a diagram 700 illustrating resources for different TRPs according to some embodiments of the present disclosure.

[0070] If, at block 610, the second TRP 132 receives a random access preamble from the terminal device 120, the process proceeds to block 620. For example, the second TRP 132 receives a physical random access channel (PRACH) preamble on the PRACH. The terms "PRACH preamble" and "random access preamble" may be used interchangeably herein. At block 620, the second TRP 132 determines a set of resources for downlink shared channel transmission with the terminal device 120. For example, the second TRP 132 may determine a set of resources 722, and an indication of the set of resources 722 may be included in the DCI 702 to be sent to the terminal device 120.

[0071] At block 630, the second TRP 132 sends an indication of the determined set of resources to another TRP communicating with the terminal device 120. For example, the second TRP 132 may send information about a set of resources 722 to the first TRP 131 to indicate to the first TRP 131 that the set of resources 722 will be occupied by the second TRP 132 for transmitting RA-RNTIPDSCH. In this way, the first TRP 131 may use resources other than the determined set of resources 722 to communicate with the terminal device 120. For example, the first TRP 131 may determine the resources 721 to be used for C-RNTIPDSCH transmission with the terminal device 120.

[0072] In some embodiments, the second TRP 132 determines a duration between the current moment and the moment of reception when the random access preamble is received (e.g., at block 610). If the duration exceeds a threshold duration, the second TRP 132 may send a random access response to the terminal device 120. The threshold duration may be greater than, for example, four time slots. The threshold duration should be greater than or equal to the latency for the second TRP 132 to communicate with the first TRP 131. In this way, the second TRP 132 is expected to send a random access response to the terminal device 120 after a predetermined delay (e.g., greater than four time slots) in order to ensure communication between the first TRP 131 and the second TRP 132 regarding the determined set of resources for RA-RNTI transmission.

[0073] In this case, the terminal device 120 may determine resources 721 based on the DCI 701 received via the first TRP 131, and may determine resources 722 based on the DCI 702 received via the second TRP 132. The resources 721 used for the C-RNTIPDSCH and the resources 722 used for the RA-RNTIPDSCH do not overlap with each other. Both the C-RNTIPDSCH and the RA-RNTIPDSCH may be received by the terminal device 120.

[0074] In the above cases, transmission conflicts are handled at the gNodeB and / or TRP side. In some cases, or when the backhaul is not ideal, transmission conflicts can be handled at the UE side. Figure 8 A flow chart of an example method 800 according to some embodiments of the present disclosure is illustrated. The method 800 may be performed in Figure 1 It should be understood that the method 800 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 respect. For the purpose of discussion, reference will be made to Figure 1 and Figures 9A-9E Method 800 is described.

[0075] At block 810, the terminal device 120 determines a first set of resources for a first transmission based on a first indication received via a first TRP 131 coupled to the network device 110. The first transmission is to be performed between the terminal device 120 and the network device 110 via the first TRP 131. The first indication may be included in, for example, Figure 9A DCI 901 shown in Figure 9B DCI 903 shown in Figure 9C DCI 905 shown in Figure 9D DCI 907 and Figure 9E The first set of resources may be, for example, Figure 9A The resources shown in 921, Figure 9B The resources shown in 923, Figure 9C The resources shown in 925, Figure 9D The resources shown in 927 and Figure 9E , as described in detail below.

[0076] At block 820, terminal device 120 determines a second set of resources for a second transmission based on a second indication received via a second TRP 132 coupled to network device 110. The second transmission is to be performed between terminal device 120 and network device 110 via second TRP 132. The second indication may be included in, for example, Figure 9A DCI 902 shown in Figure 9B DCI 904 shown in Figure 9C DCI 906 shown in Figure 9D The DCI 908 and Figure 9E The second set of resources may be, for example, Figure 9A The resources shown in 922, Figure 9B The resources shown in 924, Figure 9C The resources shown in 926, Figure 9D The resources shown in 928 and Figure 9E The resources 978 shown in , as described in detail below.

[0077] At block 830, terminal device 120 determines whether the first set of resources and the second set of resources overlap in at least one of the time domain and the frequency domain. If terminal device 120 determines that the first set of resources and the second set of resources overlap in the time domain and / or the frequency domain, the process proceeds to block 840. At block 840, terminal device 120 performs at least one of the first transmission and the second transmission to reduce interference between the first transmission and the second transmission.

[0078] In some embodiments, terminal device 120 may perform at least one of the first transmission and the second transmission based on at least one of the following: an RNTI type associated with the first indication and the second indication; a service type of the first transmission and the second transmission; a link direction of the first transmission and the second transmission; an information type related to the first transmission and the second transmission; and a carrier type configured for the first transmission and the second transmission. These embodiments are described in detail below.

[0079] In some embodiments, if both the first transmission and the second transmission are downlink shared channel transmissions, the terminal device 120 may determine a first RNTI type associated with the first indication and a second RNTI type associated with the second indication. The terminal device 120 may then perform at least one of the first transmission and the second transmission based on the determined RNTI type. For example, if the first RNTI type indicates that the first indication is scrambled using a C-RNTI, and the first RNTI type is different from the second RNTI type, the terminal device 120 may perform the second transmission.

[0080] Figure 9A Schematic diagram 910 illustrating the handling of transmission conflicts according to some embodiments of the present disclosure is shown. Figure 9A As shown in FIG, DCI 901 received via a first TRP 131 indicates resources 921 for C-RNTIPDSCH transmission between the network device 110 and the terminal device 120 via the first TRP 131, and DCI 902 received via a second TRP 132 indicates resources 922 for RA / P / SI / MCS-C-RNTIPDSCH transmission between the network device 110 and the terminal device 120 via the second TRP 132. Resources 921 and resources 922 overlap in both the time domain and the frequency domain, that is, the physical resource blocks (PRBs) overlap. Since C-RNTIPDSCH and RA / P / SI / MCS-C-RNTIPDSCH come from different TRPs and have different quasi-co-location (QCL) assumptions, the terminal device 120 needs to handle transmission conflicts.

[0081] In this embodiment, in the case of PRB overlap, the RA / P / SI / MCS-C-RNTIPDSCH from the second TRP 132 takes precedence over the C-RNTI PDSCH from the first TRP 131. That is, the terminal device 120 will receive the RA / P / SI / MCS-C-RNTIPDSCH via the second TRP 132. In the case where the RA / P / SI / MCS-C-RNTIPDSCH is received by the terminal device 120 and the C-RNTIPDSCH is discarded, for example, the terminal device 120 may further feed back a NACK for the deprioritized C-RNTI PDSCH to the first TRP 131.

[0082] In some embodiments, for example, in the event of a slot format indicator (SFI) conflict, the terminal device 120 may prioritize one of the first transmission and the second transmission based on the DL / UL service type. If the first transmission is a downlink shared channel transmission and the second transmission is an uplink transmission, the terminal device 120 may determine a first priority based on the first service type of the first transmission, and may determine a second priority based on the second service type of the second transmission. If the first priority is higher than the second priority, the terminal device 120 may perform the first transmission. If the first priority is the same as the second priority, the terminal device 120 may perform the second transmission, i.e., the terminal device 120 may perform the uplink transmission.

[0083] Figure 9B Schematic diagram 920 illustrating the handling of transmission conflicts according to some embodiments of the present disclosure is shown. Figure 9B As shown in FIG, DCI 903 received via the first TRP 131 indicates resources 923 for PDSCH transmission between the network device 110 and the terminal device 120 via the first TRP 131, and DCI 904 received via the second TRP 132 indicates resources 924 for PUSCH / Physical Uplink Control Channel (PUCCH) transmission between the network device 110 and the terminal device 120 via the second TRP 132. Resources 923 and resources 924 overlap in both the time domain and the frequency domain, i.e., PRB overlap. For symbols 913 and 914, a link direction conflict occurs as an SFI conflict. Resource 923 can be configured for RA / P / SI / MCS-C-RNTIPDSCH.

[0084] In one embodiment, PDSCH transmission for a certain service type may have a higher priority. As an example, if resource 923 is configured for MCS-C-RNTIPDSCH associated with ultra-high reliability low latency communication (URLLC), and resource 924 is configured for PUCCH or PUSCH associated with eMBB, the terminal device 120 may use resource 923 to receive MCS-C-RNTIPDSCH, and PUCCH / PUSCH transmission may be discarded. As another example, when resource 923 is configured for MCS-C-RNTI PDSCH, i.e., for URLLC, regardless of the service type associated with PUCCH / PUSCH transmission, the terminal device 120 may use resource 923 to receive MCS-C-RNTIPDSCH and discard PUCCH / PUSCH transmission. Additionally, RA / P / SI-RNTIPDSCH transmission may also have a higher priority than PUCCH / PUSCH transmission. Thus, in this embodiment, RA / P / SI / MCS-C-RNTIPDSCH transmission takes precedence over PUSCH / PUCCH transmission.

[0085] In another embodiment, regardless of the service type of the PUCCH transmission, the PUCCH transmission may have a higher priority. For example, PUCCH transmission takes precedence over RA / P / SI / MCS-C-RNTIPDSCH transmission, which in turn takes precedence over PUSCH transmission other than PUSCH transmission carrying uplink control information. PUSCH transmission carrying uplink control information may have a higher priority than PUCCH transmission. In this embodiment, if resource 924 is configured for PUCCH or PUSCH transmission carrying uplink control information, the terminal device 120 will use resource 924 instead to send PUCCH or PUSCH, and PDSCH may be discarded.

[0086] Figure 9C Schematic diagram 930 is shown illustrating the handling of transmission conflicts according to some embodiments of the present disclosure. Figure 9C As shown in FIG, DCI 905 received via the first TRP 131 indicates resources 925 for PDSCH transmission between the network device 110 and the terminal device 120 via the first TRP 131, and DCI 906 received via the second TRP 132 indicates resources 926 for PUSCH / PUCCH transmission between the network device 110 and the terminal device 120 via the second TRP 132. Resources 925 and 926 overlap in both the time domain and the frequency domain. Resource 925 can be configured for C-RNTIPDSCH.

[0087] exist Figure 9C In the example shown, PUCCH or PUSCH transmissions take precedence over PDSCH transmissions. For example, if resources 925 are configured for C-RNTIPDSCH associated with a service type (e.g., eMBB), and resources 926 are configured for PUCCH or PUSCH associated with the same service type (e.g., eMBB), the terminal device 120 may perform PUCCH / PUSCH transmissions, and the C-RNTIPDSCH transmissions may be discarded by the terminal device 120. In the event that the PDSCH transmission is discarded, the terminal device 120 may feedback a NACK in the PUCCH transmission using resources 931 indicated in the DCI 905.

[0088] In some embodiments, when the first transmission is a PDSCH transmission, even if the PDSCH transmission is deprioritized relative to another transmission ( Figure 9A and Figure 9C In the example shown in ), the terminal device 120 may also receive the PDSCH. In such an embodiment, the terminal device 120 may determine the number of resources for the first transmission (e.g., Figure 9C metric of the PDSCH transmission shown in ). This metric can be an actual coding rate, a ratio of overlapping resources to allocated resources, etc. If the determined metric is below a threshold, the terminal device 120 may also perform the first transmission. For example, if the actual coding rate is below a threshold (e.g., 0.95), the terminal device 120 may also perform the first transmission in addition to the second transmission.

[0089] for Figure 9C In the example shown in , the terminal device 120 can determine a metric for PDSCH transmission based on the overlap between resource 925 and resource 926. For example, the terminal device 120 can determine the actual coding rate based on the total number of PRBs of resource 925, the number of PRBs in resource 925 that overlap with resource 926, and the preconfigured coding rate. If the determined coding rate is lower than a predefined threshold (e.g., 0.95), this means that the degree of overlap between resources 925 and 926 is relatively low, and the transmission conflict can have a limited impact on the decoding of PDSCH. In this case, in addition to PUCCH or PUSCH transmission, the terminal device 120 can use resource 925 to receive PDSCH. Therefore, the terminal device 120 will not feedback NACK. In addition, if the buffer size of the terminal device 120 is sufficient, the PDSCH transmission may not be discarded.

[0090] for Figure 9AIn the example shown in , the terminal device 120 may determine a coding rate for C-RNTI PDSCH transmission. If the coding rate is below a predefined threshold, the terminal device 120 may also receive C-RNTI PDSCH.

[0091] In some embodiments, if both the first transmission and the second transmission are uplink transmissions, the terminal device 120 may determine whether data or control information is to be transmitted in the first transmission and the second transmission. If control information is to be transmitted in the first transmission and data is to be transmitted in the second transmission, the terminal device 120 may perform the first transmission.

[0092] Figure 9D Schematic diagram 940 is shown illustrating the handling of transmission conflicts according to some embodiments of the present disclosure. Figure 9D As shown in the figure, the DCI 907 received via the first TRP 131 indicates resources 927 for PUCCH transmission between the network device 110 and the terminal device 120 via the first TRP 131, and the DCI 908 received via the second TRP 132 indicates resources 928 for PUSCH transmission between the network device 110 and the terminal device 120 via the second TRP 132.

[0093] exist Figure 9D In the example shown, PUCCH transmissions take precedence over PUSCH transmissions other than PUSCH transmissions carrying uplink control information, and PUSCH transmissions carrying uplink control information take precedence over PUCCH transmissions. Thus, the terminal device 120 may use resource 927 to transmit PUCCH, and PUSCH transmissions may be discarded (e.g., Figure 9D Alternatively, the terminal device 120 may use resource 928 to transmit a PUSCH carrying uplink control information, and the PUCCH transmission may be discarded. It will be appreciated that although resource 927 and resource 928 are Figure 9D It is illustrated as overlapping in both the time and frequency domains, but for PUCCH transmission and PUSCH transmission, the overlap of resources only in the time domain may cause transmission collision.

[0094] In some embodiments, if both the first transmission and the second transmission are uplink shared channel transmissions, the terminal device 120 may determine a first carrier type for the first transmission and a second carrier type for the second transmission. The carrier type may be determined based on an indication, such as a DCI, for the first transmission and the second transmission. The terminal device 120 may then perform one of the first transmission and the second transmission based on a priority of the carrier type. For example, if the first carrier type is indicated as a normal uplink carrier (NUL) and the second carrier type is indicated as a supplementary uplink carrier (SUL), the terminal device 120 may perform the transmission based on the priority of the NUL and the SUL. For example, if the SUL is prioritized, the terminal device 120 may perform the second transmission.

[0095] Figure 9E Schematic diagram 950 is shown illustrating the handling of transmission conflicts according to some embodiments of the present disclosure. Figure 9E As shown in the figure, the DCI 951 received via the first TRP 131 indicates resources 977 for the first PUSCH transmission between the network device 110 and the terminal device 120 via the first TRP 131, and the DCI 952 received via the second TRP 132 indicates resources 978 for the second PUSCH transmission between the network device 110 and the terminal device 120 via the second TRP 132.

[0096] The terminal device 120 may prioritize the above two PUSCH transmissions based on the carrier type indicated for the PUSCH transmission. Figure 9E As shown in , the terminal device 120 can determine that the first PUSCH using resource 977 is indicated as having NUL, and the second PUSCH using resource 978 is indicated as having SUL. The terminal device 120 can determine the carrier type from DCI 951 and DCI 952, in which at least one field is used to indicate the carrier type configured for uplink transmission. Figure 9E In the example shown, PUSCH transmissions configured with SUL take precedence over PUSCH transmissions configured with NUL.The terminal device 120 may transmit a second PUSCH using resources 978, and the first PUSCH may be dropped.

[0097] In some other embodiments, the terminal device 120 may prioritize the two PUSCH transmissions described above based on a TRP ID or a control resource set (CORESET) ID associated with a TRP. The terminal device 120 may prioritize a PUSCH transmission indicated via a reference TRP (e.g., the first TRP 131). The terminal device 120 may prioritize a PUSCH transmission indicated via a TRP with a lower TRPID value. As an example, if the TRP ID of the first TRP 131 is 0 and the TRP ID of the second TRP 132 is 1, the terminal device 120 may send the first PUSCH using resource 977, and the second PUSCH may be discarded.

[0098] Alternatively or additionally, the terminal device 120 may prioritize the above two PUSCH transmissions based on the CORESET ID of the CORESET in which the corresponding DCI is sent. For example, the terminal device 120 may prioritize the PUSCH transmission indicated in the DCI that is sent in the CORESET with the lower COREST ID value. As an example, if DCI 951 is sent in a COREST with a CORESET ID of 2 and DCI 952 is sent in a COREST with a CORESET ID of 5, the terminal device 120 may use resource 977 to send the first PUSCH and the second PUSCH may be discarded. It should be noted that a CORESET with a specific CORESET ID may be assigned to a specific TRP. Each CORESET ID may be explicitly assigned a TRP ID value that indicates the associated TRP. For example, the TRP ID may be one-bit, where a bit value of 0 means the first TRP and a bit value of 1 means the second TRP. Each CORESET ID may also be implicitly assigned a TRP without assigning a TRP ID, where the CORESET itself is used to identify the TRP, and the CORESTID is the same as the TRPID.

[0099] The above describes the handling of transmission conflicts between two PDSCHs, one PDSCH and one PUCCH / PUSCH, and two PUSCHs. For two PUCCHs whose resources overlap in the time domain, the terminal device 120 can transmit the two PUCCHs through frequency division multiplexing (FDM). The terminal device 120 can also control the transmission power of one or both of the two PUCCHs. For example, the terminal device 120 can set the PUCCH transmission power P in PUCCH transmission opportunity i to PUCCHb,,f,c (i,q u ,q d ,l) is determined as:

[0100]

[0101] The parameter "a" represents the power scaling ratio for one or both of the two PUCCHs. The power scaling ratio "a" may be pre-configured for the terminal device 120 or indicated by the DCI. The power scaling ratio "a" is used to split the transmit power of the terminal device 120 between the two PUCCHs, where each PUCCH may have a different power scaling ratio. When the sum of the indicated transmit powers exceeds the maximum transmit power limit supported by the terminal device 120, the power scaling ratio is used to reduce the actual transmit power used for each PUCCH.

[0102] The above has been described with respect to transmission conflicts. Figure 3 - Two or more aspects described in FIG. 9 may be appropriately combined to handle the transmission collision problem.

[0103] The following will refer to Figure 10-13 Further aspects regarding transmission of cell-specific information are described. Figure 10 An example communication network 1000 is shown in which embodiments of some aspects of the present disclosure may be implemented. The network 1000 includes a network device 1010 and a terminal device 1020 served by the network device 1010. The network 1000 may provide one or more serving cells 1001, 1002 to serve the terminal device 1020, wherein each serving cell corresponds to a component carrier (CC). It should be understood that the number of network devices, terminal devices, and serving cells is for illustrative purposes only and does not represent any limitation. The network 1000 may include any appropriate number of network devices, terminal devices, and serving cells suitable for implementing embodiments of the present disclosure.

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

[0105] Carrier aggregation (CA) may be supported in the network 1000, in which two or more carriers (CCs) are aggregated to support a wider bandwidth. In CA, the network device 1010 may provide a plurality of serving cells, including one Pcell 1001 and at least one Scell ​​1002, to the terminal device 1020. The terminal device 1020 may establish a radio resource control (RRC) connection with the network device 1010 on the Pcell 1001. Once the RRC connection between the network device 1010 and the terminal device 1020 is established and the Scell ​​1002 is activated via higher layer signaling, the Scell ​​1002 may provide additional radio resources.

[0106] It should be understood that Figure 1 The configuration of the Pcell 1001 and Scell ​​1002 shown in FIG is for illustration purposes only and does not impose any limitation. The Pcell 1001 and Scell ​​1002 may be in different Figure 10 The configuration shown in .

[0107] In some embodiments, the network device 1010 is configured to implement beamforming technology and transmit signals to the terminal device 1020 via multiple beams. The terminal device 1020 is configured to receive the signals transmitted by the network device 1010 via the multiple beams. There may be different beams associated with the Pcell 1001 and the Scell ​​1002. Figure 1 As shown in FIG, DL beams 1011 and 1012 are respectively associated with Pcell 1001 and Scell ​​1002. It should be understood that Pcell 1001 and Scell ​​1002 may have more beams associated therewith.

[0108] As described above, a beam failure may occur on the Pcell 1001 or the Scell ​​1002. For example, the terminal device 1020 may detect a beam failure of a beam previously configured for communication with the network device 110. Then, a beam failure recovery procedure may be initiated. Specifically, the terminal device 120 may identify a new beam for recovering from the beam failure. For example, the terminal device 120 may select beam 1012 as a new candidate beam from the available beams on the Scell ​​1002, for example, based on the quality of the available beams. For ease of discussion, the new beam identified by the terminal device 120 will be referred to as the selected beam 1012 below. Similarly, if a beam failure occurs on the Pcell 1001, the terminal device 1020 may select a new beam (e.g., beam 1011) for recovering from the beam failure.

[0109] A cell-specific beam failure recovery (BFR) request may be sent to the network device 110 to indicate on which cell and the selected beam the BFR occurs. In addition, in the CA scenario, the channel state information (CSI) report is also cell-specific. Figure 11-13 Embodiments of some aspects of the present disclosure are described in detail to illustrate the transmission of such cell-specific information.

[0110] Figure 11 is a diagram illustrating a process 1100 for cell-specific information transmission according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 Process 1100 is described.

[0111] The terminal device 1020 sends 1105 a scheduling request for allocation of uplink resources to the network device 1010. The scheduling request may be a normal PRACH transmission on the PRACH. In this case, the PRACH transmission may be based on contention-based random access (CBRA). Alternatively, the scheduling request may be a dedicated scheduling request (SR) sent on the PUCCH or PRACH. The dedicated scheduling request may be identified by a specific sequence or sent in a specific time and / or frequency resource.

[0112] After receiving the scheduling request from the terminal device 1020, the network device 1010 allocates uplink resources to the terminal device 1020. The network device 1010 then sends 1110 a response to the terminal device 1020, indicating the uplink resources allocated to the terminal device 1020. The response may be sent on a physical downlink control channel (PDCCH) and may include downlink control information (DCI) indicating an UL grant on a PUSCH. In the case where the scheduling request is a dedicated scheduling request for BFR or CSI reporting, the response may also include a resource indication of the physical uplink control channel, such as a PUCCH resource indicator (PRI).

[0113] The terminal device 1020 sends 1115 cell-specific information to the network device 1010 using uplink resources. The cell-specific information includes a cell index of a serving cell provided by the network device 1010 to the terminal device 1020 and includes transmission control information for the serving cell. For example, in the case of BFR on Pcell 1001, the cell-specific information may include the cell index of Pcell 1001 and the selected beam 1011. In the case of CSI reporting of Scell ​​1002, the cell-specific information may include the cell index of Scell ​​1002 and the CSI on Scell ​​1002. If the scheduling request is a normal PRACH transmission, the cell-specific information may be sent in a medium access control (MAC) control element (CE). If the scheduling request is a dedicated scheduling request for BFR or CSI reporting, the cell-specific information may be carried by an uplink control indication (UCI).

[0114] In some embodiments, the network device 1010 may send 1120 a further response to the terminal device 1020. In the case of BFR, the response may be a BFR response.

[0115] Example embodiments are now described in detail to illustrate the transmission of a BFR request or CSI based on process 1100. In some example embodiments, process 1100 may be a normal CBRA procedure for BFR for Pcell 1001 or Scell ​​1002. In such embodiments, the scheduling request may be a PRACH transmission and the BFR request may be included in a MAC CE.

[0116] The beam failure recovery request may include the beam index of the selected beam and the cell index of the serving cell with the beam failure. Accordingly, the structure of the MAC CE may be designed as shown in Table 1. The field "LCID" indicates whether the MAC CE is for beam failure recovery or normal CBRA. For example, the field "LCID" having a predefined value (e.g., 33) may indicate that the MAC CE is for BFR, and the field "LCID" having a value other than the predefined value may indicate that the MAC CE is for normal CBRA. The field "Serving Cell ID" indicates the cell index with the beam failure, and the field "RS ID" indicates the beam index of the new beam. For example, in 3GPP NR, a "Serving Cell ID" is defined, in which 5 bits are used to indicate a specific cell among a maximum of 32 cells in carrier aggregation. In the case of BFR on Pcell 1001, the field "Serving Cell ID" may be the cell ID of Pcell 1001, and the field "RS ID" may be the beam index of beam 1011 selected by terminal device 1020. In the case of BFR on Scell ​​1002, the field "Serving Cell ID" may be the cell ID of Scell ​​1002, and the field "RS ID" may be the beam index of beam 1011. Although not shown, there may be reserved bits in the MAC-CE structure to align the length of the MAC-CE information to an integer number of bytes.

[0117] Table 1 MAC CE field options for BFR

[0118] Field 1: LCID Field 2: Serving cell ID Field 3: RS ID Predefined values Pcell cell ID Pcell new beam ID Predefined values Scell ​​cell ID Scell ​​new beam ID Other values

[0119] In some example embodiments, if the value of the "Serving Cell ID" field indicates the cell ID of Pcell 1001 and the transmission of the scheduling request 1105 is associated with a beam ID in Pcell 1001, the MAC-CE field "RS ID" may be ignored or set to a special state value. In this case, the beam ID associated with the transmission of the scheduling request 1105 is considered to be a new beam ID for Pcell 1001. Furthermore, in this case, for a BFR event in Pcell 1001, network device 1010 may not need to send a response to the MAC-CE-based beam failure request. Terminal device 1020 may consider that the BFR request was successfully received by network device 1010, and corresponding settings such as timers for retransmission of the BFR are stopped or reset.

[0120] In some example embodiments, process 1100 may be a dedicated procedure for BFR for Pcell 1001 or Scell ​​1002. In such embodiments, as described above, a dedicated scheduling request may be sent on the PUCCH or PRACH, and network device 1010 may allocate PUCCH resources to terminal device 1020 for sending the BFR request. Terminal device 1020 may send UCI on the PUCCH based on the PRI indicated by network device 1010. The BFR request may be included in the UCI.

[0121] Accordingly, the structure of the UCI can be designed as shown in Table 2. Similar to Table 1, the "Serving Cell ID" field indicates the cell index with beam failure, and the "RS ID" field indicates the beam index of the new beam. In the case of BFR on Pcell 1001, the "Serving Cell ID" field may be the cell ID of Pcell 1001, and the "RS ID" field may be the beam index of beam 1011 selected by terminal device 1020. In the case of BFR on Scell ​​1002, the "Serving Cell ID" field may be the cell ID of Scell ​​1002, and the "RS ID" field may be the beam index of beam 1011. Since the BFR request is sent in a dedicated procedure, fields similar to the "LCID" field in Table 1 can be omitted.

[0122] Table 2 UCI field options for BFR

[0123] Field 1: Serving cell ID Field 2: RS ID Pcell cell ID Pcell new beam ID Scell ​​cell ID Scell ​​new beam ID

[0124] In some example embodiments, process 1100 may be a dedicated procedure for CSI reporting for Pcell 1001 or Scell ​​1002. In such embodiments, as described above, a dedicated scheduling request may be sent on the PUCCH or PRACH, and network device 1010 may allocate PUCCH resources to terminal device 1020 for transmitting the CSI report. Terminal device 1020 may transmit UCI on the PUCCH based on the PRI from network device 1010. The CSI report may be included in the UCI. The CSI reporting implemented in this procedure may be used for beam reporting or CSI acquisition.

[0125] Accordingly, the structure of the UCI can be designed as shown in Table 3. The "Serving Cell ID" field indicates the cell index of the serving cell, and the "Attribute" field indicates the attributes of the corresponding serving cell, such as CQI / PMI / RI. In the case of a CSI report for Pcell 1001, the "Serving Cell ID" field can be the cell ID of Pcell 1001. In the case of a CSI report for Scell ​​1002, the "Serving Cell ID" field can be the cell ID of Scell ​​1002. Since the CSI report is transmitted in a dedicated procedure in this embodiment, fields similar to the "LCID" field shown in Table 1 can be omitted.

[0126] Table 3 UCI fields used for CSI reporting

[0127] Field 1: Serving cell ID Field 2: Attributes Pcell cell ID Properties of PCell Scell ​​cell ID Scell ​​Properties

[0128] Figure 12 A flowchart of an example method 1200 according to some embodiments of the present disclosure is shown. The method 1200 may be performed in Figure 10 It should be understood that the 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 respect. For the purpose of discussion, reference will be made to Figure 10 Describe method 1200.

[0129] At block 1210, the terminal device 1020 sends a scheduling request for allocation of uplink resources to the network device 1010. At block 1220, the terminal device 1020 receives a response from the network device 1010 indicating the uplink resources allocated to the terminal device 1020.

[0130] At block 1230, the terminal device 1020 transmits cell-specific information to the network device 1010 by using uplink resources. The cell-specific information includes a cell index of a serving cell provided by the network device 1010 to the terminal device 1020 and transmission control information for the serving cell.

[0131] In some embodiments, sending the scheduling request includes sending a random access preamble, receiving the response includes receiving downlink control information with an uplink grant, and sending the cell-specific information includes sending a beam failure recovery request in a MAC CE. The beam failure recovery request includes a cell index and a beam index of a beam available on the serving cell.

[0132] In some embodiments, sending the scheduling request includes sending a dedicated scheduling request, receiving the response includes receiving a resource indication of a physical uplink control channel, and sending the cell-specific information includes sending a beam failure recovery request in an uplink control indication. The beam failure recovery request includes a cell index and a beam index of a beam available on the serving cell.

[0133] In some embodiments, sending the scheduling request includes sending a dedicated scheduling request, receiving the response includes receiving a resource indication of a physical uplink control channel, and sending the cell-specific information includes sending channel state information in an uplink control indication. The channel state information includes a cell index.

[0134] Figure 13 A flowchart of an example method 1300 according to some embodiments of the present disclosure is shown. The method 1300 may be performed in Figure 10 It should be understood that the method 1300 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 respect. For the purpose of discussion, reference will be made to Figure 10 Method 1300 is described.

[0135] At block 1310, the network device 1010 receives a scheduling request for allocation of uplink resources from the terminal device 1020. At block 1320, the network device 1010 sends a response to the terminal device 1020 indicating the uplink resources allocated to the terminal device 1020.

[0136] At block 1330, the network device 1010 receives cell-specific information from the network device 1020 by using uplink resources. The cell-specific information includes a cell index of a serving cell provided by the network device 1010 to the terminal device 1020 and transmission control information for the serving cell.

[0137] In some embodiments, receiving the scheduling request includes receiving a random access preamble, sending the response includes sending downlink control information with an uplink grant, and receiving the cell-specific information includes receiving a beam failure recovery request in a MAC CE. The beam failure recovery request includes a cell index and a beam index of a beam available on the serving cell.

[0138] In some embodiments, receiving the scheduling request includes receiving a dedicated scheduling request, sending the response includes sending a resource indication of a physical uplink control channel, and receiving the cell-specific information includes receiving a beam failure recovery request in an uplink control indication. The beam failure recovery request includes a cell index and a beam index of a beam available on the serving cell.

[0139] In some embodiments, receiving the scheduling request comprises receiving a dedicated scheduling request, sending the response comprises sending a resource indication of a physical uplink control channel, and receiving the cell-specific information comprises receiving channel state information in an uplink control indication. The channel state information comprises a cell index.

[0140] Figure 14 is a simplified block diagram of a device 1400 suitable for implementing embodiments of the present disclosure. The device 1400 can be considered as Figure 1 The network device 110 or terminal device 120 shown in FIG. Figure 10 10 or terminal device 1020. Thus, device 1400 may be implemented at, or as at least a portion of, network device 110 or terminal device 120 or network device 1010 or terminal device 1020.

[0141] As shown, device 1400 includes a processor 1410, a memory 1420 coupled to processor 1410, an appropriate transmitter (TX) and receiver (RX) 1440 coupled to processor 1410, and a communication interface coupled to TX / RX 1440. Memory 1420 stores at least a portion of program 1430. TX / RX 1440 is configured for bidirectional communication. TX / RX 1440 has at least one antenna to facilitate communication, but in practice, the access nodes referred to in this application may have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME) / Serving Gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0142] Program 1430 is assumed to include program instructions that, when executed by associated processor 1410, enable device 1400 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figure 3 、 Figure 5 、 Figure 6 、 Figure 8 、 Figure 12 and Figure 13 The embodiments herein may be implemented by computer software executable by the processor 1410 of the device 1400, or by hardware, or by a combination of software and hardware. The processor 1410 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1410 and the memory 1420 may form a processing component 1450 suitable for implementing various embodiments of the present disclosure.

[0143] Memory 1420 can be of any type suitable for the local technology network and can be implemented using any appropriate data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1420 is shown in device 1400, there can be several physically distinct memory modules in device 1400. Processor 1410 can be of any type suitable for the local technology network and, by way of non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1400 can have multiple processors, such as application-specific integrated circuit chips, which are time-slave to a clock synchronized with a main processor.

[0144] 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 present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representation, 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.

[0145] 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 a computer program product that is executed in a device on a target real or virtual processor to implement the above-referenced Figure 3 、 Figure 5 、 Figure 6 、 Figure 8 、 Figure 12 and Figure 13 Computer-executable instructions for any of the processes or methods described herein, such as those included in program modules. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., which perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided between program modules. Machine-executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0146] Program code for implementing the disclosed method can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, it causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0147] The program code above may be embodied on a machine-readable medium, which may be any tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. 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 electrical, 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 would include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable reader read-only memory (EPROM or flash memory), 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.

[0148] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in a continuous order or that all described operations be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these details should not be interpreted as limiting the scope of this disclosure, but rather as describing features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any appropriate subcombination.

[0149] 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 communication method, comprising: determining, at a terminal device, a first set of resources for a first transmission to be performed between the terminal device and the network device via a first transmission and reception point (TRP) coupled to the network device based on a first indication received via the first TRP; determining, based on a second indication received via a second TRP coupled to the network device, a second set of resources for a second transmission to be performed between the terminal device and the network device via the second TRP; as well as In response to the first set of resources and the second set of resources overlapping in at least one of a time domain and a frequency domain, at least one of the first transmission and the second transmission is performed to reduce interference between the first transmission and the second transmission.

2. The method of claim 1 , wherein performing at least one of the first transmission and the second transmission comprises: The at least one of the first transmission and the second transmission is performed based on at least one of: an RNTI type associated with the first indication and the second indication, service types of the first transmission and the second transmission, the link directions of the first transmission and the second transmission, the type of information associated with the first transmission and the second transmission, and A carrier type configured for the first transmission and the second transmission.

3. The method of claim 1 , wherein performing at least one of the first transmission and the second transmission comprises: In response to both the first transmission and the second transmission being downlink shared channel transmissions, determining a first RNTI type associated with the first indication and a second RNTI type associated with the second indication; as well as The second transmission is performed in response to the first RNTI type indicating that the first indication is scrambled with a cell-RNTI (C-RNTI) and the first RNTI type is different from the second RNTI type.

4. The method of claim 1 , wherein performing at least one of the first transmission and the second transmission comprises: In response to the first transmission being a downlink shared channel transmission and the second transmission being an uplink transmission, determining a first priority based on a first service type of the first transmission and determining a second priority based on a second service type of the second transmission; as well as In response to the first priority being higher than the second priority, the first transmission is performed.

5. The method according to claim 4, further comprising: In response to the first priority being the same as the second priority, the second transmission is performed.

6. The method according to claim 3 or 5, further comprising: determining a coding rate for the first transmission based on the first set of resources and the second set of resources; as well as In response to the coding rate being lower than a threshold, the first transmission is performed.

7. The method of claim 1 , wherein performing at least one of the first transmission and the second transmission comprises: in response to both the first transmission and the second transmission being uplink transmissions, determining whether data or control information is to be sent in the first transmission and the second transmission; as well as In response to control information being sent in the first transmission and data being sent in the second transmission, the first transmission is performed.

8. The method of claim 1 , wherein performing the at least one of the first transmission and the second transmission comprises: In response to both the first transmission and the second transmission being uplink shared channel transmissions, determining a first carrier type for the first transmission and a second carrier type for the second transmission; as well as In response to the first carrier type being indicated as a normal uplink carrier and the second carrier type being indicated as a supplemental uplink carrier, the second transmission is performed.

9. A device comprising: processor; as well as A memory is coupled to the processor and stores thereon instructions, which, when executed by the processor, cause the apparatus to perform the method according to any one of claims 1 to 8.

Images