Terminal device, network device, and communication method

Abstract

The embodiments of the present disclosure relate to a method, an apparatus, and a computer-readable storage medium for communication. The method includes, in a terminal device, determining an uplink resource for at least one uplink transmission. The method further includes performing the at least one uplink transmission based on at least one of a number of TCI states associated with the uplink resource or a number of uplink resource sets associated with the uplink resource, based on one TCI state or two or more transmission configuration indicator (TCI) states, where each uplink resource set corresponds to a TCI state. In this way, a multi-TRP-based physical uplink control channel (PUCCH) transmission is enabled.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to communication methods, apparatus, and computer storage media. [Background technology]

[0002] Multiple input multiple output (MIMO) technology has been widely used in conventional wireless communication systems in which multiple antenna elements are used by both network equipment and terminal devices for communication. To improve the reliability and robustness of communications between network equipment and terminal devices, multi-transmission and reception point (multi-TRP / MTRP) (and multi-panel reception) technology has been proposed and discussed for downlink data transmission (e.g., physical downlink shared channel (PDSCH)) in Release 16 of the 3rd generation partnership project (3GPP®). In Release 17, multi-TRP transmission is extended to other physical channels (e.g., physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH)) based on the combined transmission configuration indicator (TCI) / spatial relationship framework of 3GPP Releases 15 / 16. Meanwhile, in Release 17, an integrated TCI framework was developed to replace / complement the Release 15 / 16 TCI / spatial relations framework for beam display.

[0003] So far, several proposals for multi-TRP scenarios have been discussed and some agreement has been reached, but there are still several open issues that need to be discussed so that multi-TRP transmissions can be better supported. Summary of the Invention [Problem to be solved by the invention]

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

[0005] In a first aspect, a method of communication is provided, the method including: determining, in a terminal device, uplink resources for at least one uplink transmission, the method further including performing the at least one uplink transmission based on one TCI state or two or more TCI states based on at least one of a number of TCI states associated with the uplink resource or a number of uplink resource sets associated with the uplink resource, where each uplink resource set corresponds to a TCI state.

[0006] In a second aspect, a method of communications is provided, the method including receiving, at a terminal device, a downlink control information (DCI) message indicating at least two TCI states used by the terminal device, the method further including performing at least one of receiving a PDCCH based on one of the at least two TCI states or receiving a PDSCH based on at least one of the at least two TCI states.

[0007] In a third aspect, a method of communication is provided, the method including receiving, at a terminal device, a DCI message for scheduling at least one PDSCH, the DCI message indicating at least one of a first indication indicating a number of TCIs for the at least one PDSCH, a second indication indicating one of a plurality of TCI states for the at least one PDSCH, the second indication indicating that the plurality of TCI states apply to at least one downlink channel, or a third indication indicating a TCI order for the at least one PDSCH, the method further including receiving the at least one PDSCH based on the DCI.

[0008] In a fourth aspect, a method of communication is provided, the method including: receiving, in a terminal device, a second message from a network device, the second message indicating at least one mapping, each mapping indicating a correspondence between a TCI codepoint and at least one TCI state; and applying the at least one TCI state indicated by the second message after an application timing if the at least one TCI state satisfies an application condition.

[0009] In a fifth aspect, a method of communication is provided, the method including: determining, in a network device, uplink resources for at least one uplink transmission, the method further including receiving the uplink transmission from a terminal device based on one TCI state or two or more TCI states based on at least one of a number of TCI states associated with the uplink resources or a number of uplink resource sets associated with the uplink resources, each of the uplink resource sets corresponding to a TCI state.

[0010] In a sixth aspect, a method of communication is provided, the method including: transmitting, in a network device, a DCI message to a terminal device, the DCI message indicating at least two TCI states used by the terminal device; and performing at least one of transmitting a PDCCH based on one of the at least two TCI states or transmitting a PDSCH based on at least one of the at least two TCI states.

[0011] In a seventh aspect, a method of communication is provided, the method including, in a network device, transmitting a DCI message for scheduling at least one PDSCH to a terminal device, the DCI message indicating at least one of a first indication indicating a number of TCIs for the at least one PDSCH, a second indication indicating one of a plurality of TCI states for the at least one PDSCH, the second indication indicating that the plurality of TCI states apply to at least one downlink channel, or a third indication indicating a TCI order for the at least one PDSCH, the method further including transmitting the at least one PDSCH to the terminal device based on the DCI.

[0012] In an eighth aspect, a method of communication is provided, the method including: in a network device, transmitting a second message to a terminal device, the second message indicating at least one mapping, each mapping indicating a correspondence between a TCI codepoint and at least one TCI state; and applying the at least one TCI state indicated by the second message after an application timing if the TCI state satisfies an application condition.

[0013] In a ninth aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the first aspect of the present disclosure.

[0014] In a tenth aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the second aspect of the present disclosure.

[0015] In an eleventh aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the third aspect of the present disclosure.

[0016] In a twelfth aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the fourth aspect of the present disclosure.

[0017] In a thirteenth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the fifth aspect of the present disclosure.

[0018] In a fourteenth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the sixth aspect of the present disclosure.

[0019] In a fifteenth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the seventh aspect of the present disclosure.

[0020] In a sixteenth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the eighth aspect of the present disclosure.

[0021] In a seventeenth aspect, there is provided a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to any one of the first to eighth aspects of the present disclosure.

[0022] It should be understood that this Summary of the Invention is not intended to identify key or essential features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0023] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the accompanying drawings.

[0024] [Figure 1A] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 1B] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 1C] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 illustrates a signaling flow for communication in accordance with some exemplary embodiments of the present disclosure. [Figure 3] FIG. 10 illustrates an exemplary application timing. [Figure 4A] FIG. 1 illustrates an exemplary scenario in which embodiments of the present disclosure can be implemented. [Figure 4B] FIG. 10 illustrates an exemplary application timing. [Figure 5] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure. [Figure 6] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure. [Figure 7] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure. [Figure 8] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure. [Figure 9]4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure. [Figure 10] 4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure. [Figure 11] 4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure. [Figure 12] 4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure. [Figure 13] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0025] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0026] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways different from those described below.

[0027] 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 pertains.

[0028] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but do not necessarily mean that each embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0029] While the terms "first," "second," and the like may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] The terminology used herein is used only for the purpose of describing particular embodiments and is not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. It should be further understood that, as used herein, the terms "comprise," "include," "have," "comprise," "comprises," and / or "have" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0031] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0032] As used herein, the term "network device" refers to a device capable of providing or hosting a cell or coverage area in which a terminal device 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 New Radio Access Node B (gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a low-power node such as a femto node or a pico node, a satellite network device, an aircraft network device, etc. For illustrative purposes, some exemplary embodiments will be described below with reference to an eNB as an example of a network device.

[0033] As used herein, the term "terminal" refers to any end device that may be capable of wireless communication. By way of example and not limitation, a terminal may be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, imaging terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms “terminal device,” “communications device,” “terminal,” “user equipment,” and “UE” may be used interchangeably.

[0034] As used herein, the term "communication network" refers to a network conforming to any appropriate communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), etc. Furthermore, communications between terminal devices and network devices in a communication network may be implemented in accordance with any appropriate generation of communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and / or any other protocol now known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development of communications, there will naturally be future types of communications technologies and systems in which the present disclosure can be embodied, which should not be considered to limit the scope of the present disclosure to only the aforementioned systems.

[0035] As used herein, the term "circuitry" may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes an implementation of a hardware circuit or one or more processors only, or a hardware circuit or portion of one or more processors and its / their accompanying software and / or firmware.

[0036] While the functions described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functions may be implemented in user equipment devices (e.g., mobile phones, tablet computers, laptop computers, desktop computers, mobile IoT devices, or fixed IoT devices). For example, the user equipment devices may include corresponding capabilities described in connection with fixed and / or wireless network nodes, as appropriate. The user equipment devices may be user equipment and / or control devices such as chipsets or processors configured to control the user equipment when installed within the user equipment. Examples of such functions include a bootstrap server function and / or a home subscriber server, which may be implemented within the user equipment devices by providing the user equipment devices with software configured to cause the user equipment devices to perform from the perspective of these functions / nodes.

[0037] The wireless communication network includes at least one network device and at least one terminal device, and the network device and the terminal device may communicate via uplink transmissions (e.g., PUSCH and PUCCH) or downlink transmissions (e.g., PDSCH and PDCCH).

[0038] As mentioned above, multi-TRP techniques have already been proposed and discussed, mainly for downlink data transmission (e.g., PDSCH) in 3GPP Release 16. For example, 3GPP Release 16 proposes that multi-TRP-based PDSCH may be realized via ultra-reliable low latency communication (URLLC) FDMed scheme or URLLC TDMed scheme.

[0039] In Relief 17, there was discussion about strengthening support for the introduction of multi-TRP. For example, it is proposed to identify and specify functionality to improve the reliability and robustness of physical channels other than PDSCH (e.g., PDCCH, PUSCH, PUCCH) using multi-TRP and / or multi-panel based on the 3GPP Release 15 / 16 TCI / Spatial Relationship Framework.

[0040] Unlike the multi-TRP based PDSCH solution proposed in Release 16, the multi-TRP based PUCCH proposed in Release 17 is proposed to be realized with two spatial relationships. Specifically, one PUCCH resource is activated with two spatial relationships and / or associated with two sets of power control parameters (each set including a path loss reference signal (PL-RS) ID). Also, for inter-slot repetition, the number of slots is set for the PUCCH resource, while for intra-slot repetition, the PUCCH resource is repeated for two consecutive sub-slots within a slot.

[0041] Additionally, the concept of an aggregated TCI is introduced. Specifically, the aggregated TCI state indicated in the DCI indicates (updates) the TCI state for future transmissions, and the TCI state is applied after the application timing. That is, the aggregated TCI state cannot be used to switch from a current single-TRP-based transmission to a multi-TRP-based transmission.

[0042] In short, so far, schemes for different channels (e.g., PDSCH PDCCH, PUSCH, PUCCH) have been described separately, and the unified TCI framework has also been described separately from the TCI state schemes described in Releases 15 and 16. In this case, multi-TRP-based transmission cannot be well supported.

[0043] It is proposed to have more discussion on the unified TCI framework in the upcoming Release 18. According to some embodiments of the present disclosure, it is possible to improve the unified TCI based procedures for configuring / activating beams / TCI states / channel resources.

[0044] In this disclosure, some terms may refer to the same or similar physical meaning and may be used interchangeably. Some illustrative examples are given below: The terms "old TCI state", "previously indicated TCI state", "active TCI state", "activated TCI state", "applied TCI state", "currently applied TCI state", and "current TCI state" may be used interchangeably. The terms "new TCI state", "indicated TCI state", "applied TCI state", and "used TCI state" may be used interchangeably. The terms "common beam", "common beam update / indication", "combined TCI state", "combined TCI state update / indication", "beam indication", "combined TCI state", "TCI state for downlink and uplink", "TCI state for downlink", "downlink TCI state", "TCI state for downlink only", "TCI state for uplink", "TCI state for uplink only", "uplink TCI state", "separate TCI state", "separate DL / UL TCI state", "TCI state indication", "TCI_state_r17", "tci_StateId_r17", "TCI_state_r17 indicating combined TCI state", "TCI state shared / applied for all or a subset of CORESET on PDSCH and UE-dedicated reception", "Rel-17 TCI state", "TCI state with tci_StateId_r17", "TCI state configured for TCI state update in combined TCI framework", "TCI state indicated in DCI for common beam update / indication", "TCI state indicated in DCI and applicable to all / subset of CORESET and PDSCH" may be used interchangeably. The terms "precoder", "precoding", "precoding matrix", "beam", "spatial relationship information", "spatial relationship info", "TPMI", "precoding information", "precoding information and number of layers", "precoding matrix indicator (PMI)", "precoding matrix indicator", "transmit precoding matrix indication", "precoding matrix indication", "TCI state", "transmit configuration indicator", "quasi co-location (QCL)", "quasi co-location", "QCL parameters", "QCL assumption", "QCL relationship", "QCL configuration" and "spatial relationship" may be used interchangeably. The terms "transmit opportunity," "transmit," "repeat," "receive," "receive opportunity," "monitoring opportunity," "transmit opportunity," and "candidate" may be used interchangeably. The terms "DCI" and "DCI format" may be used interchangeably. The terms "time threshold", "threshold", "application timing", "beam application timing", and "timing" may be used interchangeably. The terms "applied," "activated," "indicated," and "effective" may be used interchangeably. The terms "acknowledgment", "positive acknowledgement", "ACK", "hybrid automatic repeat request-acknowledgment", "HARQ-ACK", "negative acknowledgement", "NACK", "NAK", "ACK / NACK" and "ACK / NAK" may be used interchangeably. The terms "CORESET (sub)group", "(sub)set of CORESET", "(sub)set of TCI states", "(sub)set of integrated TCI states", "(sub)set of downlink (integrated) TCI states", and "(sub)set of combined (integrated) TCI states" may be used interchangeably. The terms "(sub)set of PUCCH", "(sub)set of TCI states", "(sub)set of integrated TCI states", "(sub)set of uplink (integrated) TCI states", and "(sub)set of combined (integrated) TCI states" may be used interchangeably. The terms "single TRP", "single TCI state", "single TCI", "S-TCI", "single CORESET", "single control resource set pool", "S-TRP" and "S-TCI state" may be used interchangeably. The terms "multi-TRP", "multi-TCI state", "multi-CORESET", "multi-controlled resource set pool", "multi-TRP", "multi-TCI state", "multi-TCI", "multi-CORESET" and "multi-controlled resource set pool", "MTRP" and "M-TCI", "M-TPR" may be used interchangeably. The terms "pool," "set," "subset," "group," and "subgroup" may be used interchangeably.

[0045] As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to a network device located at a particular geographic location. Although some embodiments of the present disclosure have been described with reference to a multi-TRP scenario (or a single-TRP scenario) as an example, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0046] Generally speaking, a panel refers to one or more antenna elements deployed in a terminal device or network device, and in this regard, the terms "panel," "panel type," "antenna element," "antenna array," "transmit / receive point," "TRP" (and their equivalents) may be used interchangeably.

[0047] In the following, DCI_t may be used to describe a DCI indicating a TCI state for the downlink and uplink, or indicating at least one of a TCI state for the downlink and a TCI state for an uplink indication. In the following, the terms “DCI,” “PDCCH,” “DCI_t,” “DCI for TCI state for downlink and uplink indication,” “DCI for TCI state for downlink indication,” “DCI for TCI state for uplink indication,” “DCI for TCI state for downlink and uplink indication,” “PDCCH for TCI state for downlink and uplink indication,” “PDCCH for TCI state for uplink indication,” “PDCCH for TCI state for downlink indication and TCI state for uplink indication,” “DCI for TCI state indication,” and “PDCCH for TCI state indication” may be used interchangeably.

[0048] Example environment 1A illustrates an exemplary communication network 100 in which embodiments of the present disclosure may be implemented. Communication network 100 includes network device 110-1 and optional network device 110-2 (collectively or individually referred to as network device 110). Network device 110 may provide services to end device 120. For purposes of explanation, network device 110-1 will be referred to as first network device 110-1, and network device 110-2 will be referred to as second network device 110-2. Furthermore, first network device 110-1 and second network device 110-1 may communicate with each other.

[0049] In the environment 100, a link from a network device 110 (e.g., a first network device 110-1 or a second network device 110-2) to a terminal device 120 is referred to as a downlink, and a link from a terminal device 120 to a network device 110 (e.g., a first network device 110-1 or a second network device 110-2) is referred to as an uplink. In a downlink, the first network device 110-1 or the second network device 110-2 is a transmitting (TX) device (or transmitter), and the terminal device 120 is a receiving (RX) device (or receiver). In an uplink, the terminal device 120 is a transmitting TX device (or transmitter), and the first network device 110-1 or the second network device 110-2 is an RX device (or receiver).

[0050] In some embodiments, network device 110 and terminal device 120 may communicate using a direct link / channel.

[0051] Additionally, in the example of Figure 1A, multi-TRP transmission is also supported. As shown in Figure 1A, terminal device 120 may communicate with two TRPs, namely, TRPs 130-1 and 130-2 (collectively or individually referred to as TRPs 130). For purposes of explanation, TRP 130-1 will be referred to as the first TRP 130-1, and TRP 130-2 will be referred to as the second TRP 130-2.

[0052] Furthermore, both single-TRP and multi-TRP transmission modes are supported by the example of Figure 1A. Specifically, in single-TRP mode, the terminal device 120 communicates with the network via either the first TRP 130-1 or the second TRP 130-2. Alternatively, in multi-TRP mode, the terminal device 120 communicates with the network via both the first TRP 130-1 and the second TRP 130-2.

[0053] Additionally, to support multiple TRPs and / or panels, the network device 110 may include one or more TRPs / panels. For example, the network device 110 may be coupled to multiple TRPs / panels in different geographic locations to achieve better coverage. In one particular exemplary embodiment, the first network device 110-1 includes a first TRP / panel 130-1 and a second TRP / panel 130-2. Alternatively, in another particular exemplary embodiment, the first network device 110-1 and the second network device 110-2 include a first TRP / panel 130-1 and a second TRP / panel 130-2, respectively.

[0054] In some embodiments, TRP 130 may be explicitly associated with different higher-layer configured identities. For example, the higher-layer configured identities may be associated with a CORESET, a group of CORESETs, an RS, a set of RSs, a TCI state, or a group / set of TCI states. For example, the higher-layer configured identities may be used to distinguish transmissions between different TRPs and terminal device 120. In some embodiments, if terminal device 120 receives two DCI messages from two CORESETs associated with different higher-layer configured identities, the two DCI messages are indicated as coming from different TRPs 130.

[0055] Alternatively, the TRP 130 may be implicitly identified by a dedicated configuration for a physical channel or signal. For example, a dedicated CORESET, RS, and TCI state associated with the TRP 130 may be used to distinguish transmissions from different TRPs 130 to the terminal device 120. In some embodiments, when the terminal device 120 receives a DCI message from a dedicated CORESET, the DCI message is indicated from the associated TRP dedicated to the corresponding CORESET.

[0056] In some embodiments, the network device 110 may configure multiple control resource sets (CORESETs) for the terminal device 120.

[0057] Additionally, the multiple CORESETs may be divided into different groups / subsets / pools. In one particular exemplary embodiment, the first TRP 130-1 and the second TRP 130-2 are associated with different CORESET pools. For example, the first TRP 130-1 is associated with a first CORESET group and the second TRP 130-2 is associated with a second CORESET group.

[0058] Accordingly, other resources (e.g., uplink resources, reference signal (RS) resources) may also be divided into different groups / subsets / pools. In one particular exemplary embodiment, the first TRP 130-1 and the second TRP 130-2 are associated with different resource sets. For example, the first TRP 130-1 is associated with a first uplink resource set (e.g., a first PUCCH resource set) / first RS set, while the second TRP 130-2 is associated with a second uplink resource set (e.g., a second PUCCH resource set) / second RS set. In some embodiments, the RS may be at least one of a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), and a fractional time and frequency tracking reference signal (TRS).

[0059] In some embodiments, the CORESET is a

number

number

[0060] In some embodiments, one CORESET may be associated with one or more search space sets. One search space set may include or be associated with one or more PDCCH candidates. In some embodiments, a PDCCH monitoring period and / or a slot offset and / or a symbol index within a slot may be configured for each search space set. In some embodiments, a PDCCH candidate may be associated with or correspond to a search space.

[0061] In some embodiments, a procedure may be defined for determining PDCCH candidates for terminal device 120. That is, a CCE index is determined for each of multiple PDCCH candidates that may be used for PDCCH transmission between network device 110 and terminal device 120. Once the CCE indexes for the PDCCH candidates are determined, terminal device 120 may perform blind detection on these PDCCH candidates. Once a PDCCH transmission is detected or received on a PDCCH candidate, terminal device 120 may decode it to obtain information such as DCI.

[0062] In some embodiments, terminal device 120 may assume that the DM-RS antenna ports associated with PDCCH reception within a CORESET are quasi-co-located (QCLed) with one or more RSs configured by the TCI state indicated for that CORESET (if applicable).

[0063] In some embodiments, if a medium access control (MAC) control element (CE) activation command indicating a TCI state for a CORESET is not received after a most recent random access procedure that was not initiated by a PDCCH order triggering a contention-free random access procedure, terminal device 120 may assume that the DM-RS antenna port associated with PDCCH reception in the CORESET is quasi-co-located (QCLed) with a synchronization signal / physical broadcast channel (SS / PBCH) block identified by terminal device 120 during the most recent random access procedure, and the one or more RSs are configured according to the TCI state indicated for the CORESET (if applicable).

[0064] Furthermore, a unified TCI framework is supported in the communication network 100. In some embodiments, the network device 110 may preconfigure multiple TCI states for the terminal device 120, for example, via radio resource control (RRC) signaling. The multi-TRP / single-TRP transmission may then be scheduled by either a single DCI message or multiple DCI messages (i.e., multiple DCI / M-DCI). Specifically, one or more preconfigured TCI states may be indicated by a single / multiple DCI messages.

[0065] 1A, when the single DCI mode is applied, the terminal device 120 receives a single DCI message from the first TRP 130-1. It should be understood that the single DCI message may also be received from the second TRP 130-2. Alternatively, when the multi-DCI mode is applied, the terminal device 120 receives two DCI messages from the first TRP 130-1 and the second TRP 130-2, respectively. By applying the indicated TCI state, the first TRP 130-1 and the second TRP 130-2 can be selectably activated to achieve directional transmission.

[0066] In some embodiments, the indicated TCI state may be a combined downlink / uplink TCI state (i.e., a combined DL / UL TCI state) or either a downlink TCI state and / or an uplink TCI state. In some embodiments, the combined DL / UL TCI state may be a TCI state for both the downlink and the uplink. In some embodiments, the downlink TCI state may be a TCI state for the downlink. In some embodiments, the uplink TCI state may be a TCI state for the uplink.

[0067] For purposes of explanation, the parameters M and N are defined as follows: M: refers to the number of indicated / applied TCI states for downlink transmissions supported by terminal device 120. Additionally, in some embodiments, M may be one of {0, 1, 2, 3, 4}. N: refers to the number of indicated / applied TCI states for uplink transmissions supported by terminal device 120. Additionally, in some embodiments, M may be one of {0, 1, 2, 3, 4}.

[0068] Some example scenarios for different values ​​of M and / or N are listed below. If M=1: · DL TCI: The source reference signal in the DL TCI (similar to Rel.15, if qcl_Type2 is configured in addition to qcl_Type1, there are two) provides QCL information for UE-specific reception on at least the PDSCH and all CORESETs in the component carrier (CC). If N=1: ·UL TCI: The source reference signal in the UL TCI provides the reference for determining the UL TX spatial filter for at least the dynamically granted / configured grant-based PUSCH and all dedicated PUCCH resources in the CC. When M=N=1: · Combined DL / UL TCI: The TCI refers to at least a common source reference RS that is used to determine both the DL QCL information and the UL TX spatial filter. · Separate DL / UL TCI: DL TCI and UL TCI are different (and therefore separate). If M>1: DL TCI: Each of the M source reference signals (or 2M if qcl_Type2 is configured in addition to qcl_Type1) provides QCL information for at least one of the M beam pair links for UE-dedicated reception on a subset of the CORESET within the PDSCH and / or CC. If N>1: UL TCI: Each of the N source reference signals in the N UL TCIs provides a reference for determining the UL TX spatial filter for one of the N beam pair links associated with at least a subset of the dynamically granted / configured grant-based PUSCH and / or dedicated PUCCH resources in the CC. If M>1 and / or N>1: Combined DL / UL TCI: The TCI refers to at least a common source reference RS that is used to determine both the DL QCL information and the UL TX spatial filter. In this case, M=N. Separate DL / UL TCIs: The M DL TCIs and the N UL TCIs are different (and therefore separate).

[0069] In some embodiments, terminal device 120 may be configured or indicated to have M activated joint TCI states, where M is a positive integer, e.g., M may be one of {1, 2, 3, 4}, in some embodiments, the joint TCI state may be a TCI state for the downlink or a TCI state for the downlink and uplink.

[0070] In some embodiments, terminal device 120 may be configured or indicated to have N activated aggregate TCI states. In some embodiments, the aggregate TCI state may be a TCI state for the uplink or a combined TCI state for the downlink and uplink, where N is a positive integer, e.g., N may be one of {1, 2, 3, 4}.

[0071] Network device 110 may communicate data and / or downlink control information and / or RS to terminal device 120 via multiple beams (also referred to as "DL beams"). Terminal device 120 may also communicate data and / or uplink control information and / or RS to network device 110 via multiple beams (also referred to as "UL beams"). In the 3GPP specifications for NR, beams are also defined and indicated by TCI parameters. For example, a TCI field may be present in a DCI. The value of the TCI field may be referred to as a "TCI codepoint." The TCI codepoint may indicate one or more TCI states. Each TCI state includes parameters for setting a quasi-co-location (QCL) relationship between one or two DL and / or UL reference signals and a DMRS port of a PDSCH, a DMRS port of a PDCCH, a DMRS port of a PUSCH, a DMRS port of a PUCCH, an SRS port of an SRS resource, or a CSI-RS port of a CSI-RS resource.

[0072] In some embodiments, there may be adaptive timing for beam indication or TCI status indication.

[0073] In some embodiments, the application timing may be the first slot or first subslot that is at least Y symbols after the last symbol of the beam indication or TCI status indication acknowledgment. In one particular exemplary embodiment, Y may be an integer, e.g., 1≦Y≦336. In another particular exemplary embodiment, Y may be an integer, e.g., Y may be one of {7, 14, 28, 224, 336}.

[0074] In some embodiments, a slot may include 12 or 14 (OFDM) symbols. In some embodiments, a subslot may include S symbols, where S is an integer, e.g., 1≦S≦14. In one particular exemplary embodiment, S may be one of {2, 4, 7}. In some embodiments, the TCI status is indicated in a DCI in a PDCCH. Specifically, the DCI in a PDCCH may schedule a PDSCH or may not schedule a PDSCH. In some embodiments, the gap between the last symbol of a DCI and the first slot or first subslot should meet the capabilities of the terminal device. In some embodiments, the acknowledgement of the TCI status indication may be an acknowledgement of a PDSCH scheduled by the DCI, for example, if the DCI schedules a PDSCH. In some embodiments, the acknowledgement of the TCI status indication may be an acknowledgement of the DCI. In some embodiments, if the DCI does not schedule a PDSCH. For example, the application timing may also be expressed as a beam application timing.

[0075]

number

[0076] In some embodiments, slot n may be a slot in which terminal device 120 may transmit a PUCCH with HARQ-ACK information, which may correspond to an activation command. In one particular exemplary embodiment, the activation command may be carried in a PDSCH. In another particular exemplary embodiment, the activation command may be a MAC CE message. In another particular example, the activation command may be used to activate at least one TCI state. In another particular example, the activation command may be used to indicate a mapping between at least one TCI state and at least one code point, which may be included in a DCI field "Transmission Configuration Indication."

[0077] In some embodiments, the value of n may be a non-negative integer, for example:

number

[0078] In some embodiments, DCI (e.g., DCI format 1_1 / 1_2 with DL allocation and DCI format 1_1 / 1_2 without downlink allocation) may be used for TCI state indication. In some embodiments, a DCI with downlink scheduling or PDSCH scheduling may indicate at least one TCI state, and HARQ or ACK and / or NACK for PDSCH or downlink scheduling may be used to indicate an acknowledgment of the at least one TCI state indication. Furthermore, the indicated TCI state may be applied after the application timing. For example, it may be applied to the PDSCH and / or PDCCH and / or PUSCH and / or PUCCH and / or downlink RS and / or uplink RS.

[0079] In some embodiments, terminal device 120 may receive or detect a DCI (e.g., represented as “DCI_t”) in the PDCCH, which may indicate a TCI state for the downlink and uplink, or a TCI state for the downlink, or a TCI state for the uplink, or a pair of a TCI state for the downlink and a TCI state for the uplink.

[0080] In some embodiments, the indicated TCI state for the downlink and uplink, or the indicated TCI state for the downlink, or the indicated TCI state for the uplink, or the pair of the indicated TCI state for the downlink and TCI state for the uplink may be applied to the PDSCH and / or CORESET and / or PUSCH and / or PUCCH and / or uplink RS and / or downlink RS after the application timing.

[0081] In one particular exemplary embodiment, if the TCI state for the downlink and uplink is indicated in the DCI, the TCI state for the downlink and uplink may be applied to the PDSCH and / or CORESET and / or PUSCH and / or PUCCH and / or uplink RS and / or downlink RS after the application timing. In another particular exemplary embodiment, if the TCI state for the downlink is indicated in the DCI, the TCI state for the downlink may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing. In another particular exemplary embodiment, if the TCI state for the uplink is indicated in the DCI, the TCI state for the uplink may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing. In another particular exemplary embodiment, if a pair of a TCI state for the downlink and a TCI state for the uplink is indicated in the DCI, the TCI state for the downlink may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing, and the TCI state for the uplink may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing.

[0082] In some embodiments, terminal device 120 may receive an indication indicating a TCI state (or set of beams or QCL parameters) for the downlink, in which the source RS in the TCI state provides at least QCL information for reception on the PDSCH and all CORESETs in the CC. In one particular exemplary embodiment, the PDSCH is dedicated or UE-specific.

[0083] In some embodiments, terminal device 120 may receive an indication of a TCI state (or beam or spatial relationship) for the uplink, where the source RS in the TCI state provides a reference for determining the uplink transmit spatial filter for all PUCCH resources in at least a dynamic grant or grant-based PUSCH and CC to be configured, e.g., the PUCCH may be dedicated or UE-specific.

[0084] In some embodiments, the terminal device 120 may receive an indication indicating a TCI state (or a set of beams or QCL parameters) for the downlink and uplink, the TCI state referring to at least a common source RS used to determine both the downlink QCL information and the uplink transmit spatial filter.

[0085] In some embodiments, terminal device 120 may receive an indication indicating a TCI state (or beam or set of QCL parameters) for the downlink and a TCI state (or beam or spatial relationship) for the uplink, where the source RS in the TCI state for the downlink provides QCL information for reception on at least the PDSCH and all CORESETs in the CC, and the source RS in the TCI state for the uplink provides a reference for determining uplink transmit spatial filters for at least the dynamic grant or configured grant-based PUSCH and all PUCCH resources in the CC. In one particular exemplary embodiment, the PUCCH is dedicated or UE-specific. In another particular exemplary embodiment, the PDSCH is dedicated or UE-specific.

[0086] In some embodiments, terminal device 120 may be configured to have two or more (e.g., denoted as M, where M is a positive integer, e.g., M may be one of {1, 2, 3, 4}) TCI states for the downlink, and / or terminal device 120 may receive an indication indicating one of M TCI states, where a source RS in the one of the M TCI states or in the indicated one TCI state provides QCL information for reception on at least a subset of the PDSCH and / or CORESET in the CC. In one particular exemplary embodiment, the PDSCH is dedicated or UE-specific.

[0087] In some embodiments, terminal device 120 may be configured to have two or more (e.g., represented as N, where N is a positive integer, e.g., N may be one of {1, 2, 3, 4}) TCI states for the uplink, and / or terminal device 120 may receive an indication indicating one of the N TCI states, where a source RS within the one of the N TCI states or within the indicated TCI state provides a reference for determining an uplink transmit spatial filter for at least a dynamic grant or a subset of PUSCH and / or PUCCH resources within the configured grant-based PUSCH and / or CC. In one particular exemplary embodiment, the PUCCH is dedicated or UE-specific.

[0088] In some embodiments, the terminal device 120 may be configured to have two or more (e.g., represented as M, where M is a positive integer, e.g., M may be one of {1, 2, 3, 4}) TCI states for the downlink and uplink, and / or may receive an indication indicating one of M TCI states for the downlink and uplink, where each TCI state or the indicated one TCI state among the M TCI states references at least a common source reference signal used to determine both the downlink QCL information and the uplink transmit spatial filter.

[0089] In some embodiments, terminal device 120 may be configured to have two or more TCI states for the downlink (e.g., denoted as M, where M is a positive integer, e.g., M may be one of {1, 2, 3, 4}), and terminal device 120 may be configured to have two or more TCI states for the uplink (e.g., denoted as N, where N is a positive integer, e.g., N may be one of {1, 2, 3, 4}), and / or terminal device 120 may be configured to have one of M TCI states for the downlink and one of N TCI states for the uplink. and the source RS in each TCI state among the M downlink TCI states or the indicated downlink TCI state provides QCL information for reception on at least a subset of the PDSCH and / or CORESET in the CC, and the source RS in each TCI state among the N uplink TCI states or the indicated uplink TCI state provides a reference for determining an uplink transmit spatial filter for at least a dynamic grant or a grant-based PUSCH configured and / or a subset of the PUCCH resources in the CC. In one particular exemplary embodiment, the PUCCH is dedicated or UE-specific. In another particular exemplary embodiment, the PDSCH is dedicated or UE-specific.

[0090] In the following, DCI_t may be used to describe a DCI indicating a TCI state for the downlink and uplink, or indicating at least one of a TCI state for the downlink and a TCI state for an uplink indication. In the following, the terms “DCI,” “PDCCH,” “DCI_t,” “DCI for TCI state for downlink and uplink indication,” “DCI for TCI state for downlink indication,” “DCI for TCI state for uplink indication,” “DCI for TCI state for downlink and uplink indication,” “PDCCH for TCI state for downlink and uplink indication,” “PDCCH for TCI state for uplink indication,” “PDCCH for TCI state for downlink indication and TCI state for uplink indication,” “DCI for TCI state indication,” and “PDCCH for TCI state indication” may be used interchangeably.

[0091] In some embodiments, the DCI may be used to indicate a TCI status for the downlink and the uplink, or to indicate at least one of a TCI status for the downlink and a TCI status for the uplink. Furthermore, the DCI may schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). For example, the DCI may be DCI_t. In some embodiments, HARQ of the PDSCH scheduled by the DCI may be used as an ACK for the DCI.

[0092] In some embodiments, the DCI may be used to indicate the TCI status for the downlink and the uplink, or to indicate at least one of the TCI status for the downlink and the TCI status for the uplink. Furthermore, the DCI may not schedule the PDSCH (e.g., DCI format 1_1 and format 1_2). For example, the DCI may be DCI_t. In some embodiments, HARQ of the DCI may be introduced to indicate whether the DCI or TCI status indication was successful.

[0093] In some embodiments, if the decoding result of DCI_t or the decoding result of the PDSCH scheduled by DCI_t is ACK, the indicated TCI state may be applied to all or a subset of the PDSCH and / or CORESET after the application timing.

[0094] In some embodiments, the HARQ mechanism of Transmit semi persistent scheduling (SPS) PDSCH release may be reused for HARQ of DCI_t, where there is no PDSCH scheduling.

[0095] In some embodiments, a DCI (e.g., DCI_t) may be used to indicate one or more TCI states. For example, the one or more TCI states may be for at least one of the downlink and the uplink, or a TCI state for the downlink and a TCI state for the uplink. Furthermore, the DCI may not schedule a PDSCH (e.g., DCI format 1_1 and format 1_2).

[0096] In some embodiments, upon successful reception / decoding of the DCI, terminal device 120 may report an ACK. In some embodiments, upon unsuccessful reception / decoding of the DCI, terminal device 120 may report a NACK. For example, the ACK and / or NACK may be reported in the PUCCH or PUSCH.

[0097] In some embodiments, terminal device 120 may be configured to have one type of HARQ codebook. For example, the type may be at least one of Type 1 (e.g., semi-static), Type 2 (e.g., dynamic), and Type 3 (one-time feedback). For example, the type may be configured via RRC, MAC CE, or DCI. In some embodiments, DCI is received / detected on the PDCCH.

[0098] In some embodiments, for the HARQ-ACK information bit, terminal device 120 generates an ACK if terminal device 120 detects a DCI format providing SPS PDSCH release or beam indication scrambled with the CS-RNTI or if terminal device 120 correctly decodes the transport block, and generates a NACK if terminal device 120 does not correctly decode the transport block. In one particular exemplary embodiment, a HARQ-ACK information bit value of 0 represents a NACK, and a HARQ-ACK information bit value of 1 represents an ACK.

[0099] In some embodiments, terminal device 120 may be configured / indicated to have a first TCI state for reception of all or a subset of a PDSCH and / or a CORESET. Furthermore, terminal device 120 may receive or detect a first PDCCH using the first TCI state, where the PDCCH is in the first CORESET. Terminal device 120 may be indicated with a second TCI state in DCI received or detected in the first PDCCH. In some embodiments, DCI in the first PDCCH may or may not schedule the first PDSCH or the first PUSCH.

[0100] In some embodiments, terminal device 120 may report a decoding result or HARQ-ACK information for at least one of the DCI, the first PDCCH, or the first PDSCH to network device 110. In some embodiments, the decoding result or HARQ-ACK information may be transmitted / reported in the PUCCH or the second PUSCH.

[0101] In some embodiments, after the application timing, terminal device 120 may receive all or a subset of the PDSCH and / or CORESET using the second TCI state. In one particular exemplary embodiment, terminal device 120 may receive a second PDCCH using the second TCI state, where the second PDCCH is in the second CORESET. In another particular exemplary embodiment, terminal device 120 may receive a second PDCCH using the second TCI state, where the second PDCCH is in the first CORESET.

[0102] Furthermore, the network device 110 may provide one or more serving cells, and the first TRP 130-1 and the second TRP 130-2 may be included in the same serving cell or different serving cells. In other words, both inter-cell and intra-cell transmissions are supported by the example of FIG. 1A.

[0103] Figure 1B illustrates an example scenario for the communication network 100 shown in Figure 1A. In the example of Figure 1B, a first TRP 130-1 and a second TRP 130-2 are included in the same serving cell 140. In this case, multi-TRP transmission is performed as an intra-cell transmission.

[0104] 1C illustrates another exemplary scenario for the communication network 100 shown in FIG. 1A. In the example of FIG. 1C, the first TRP 130-1 and the second TRP 130-2 are included in different serving cells 140-1 and 140-2. In this case, multi-TRP transmission is performed as an inter-cell transmission.

[0105] Communications in the communication environment 100 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communications may be performed according to any currently known or future-developed generation of communications protocols. Examples of communications 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, fifth generation (5G), 5.5G, 5G-Advanced networks, or sixth generation (6G) communications protocols.

[0106] It should be understood that the number of devices (i.e., terminal devices 120, network devices 110, TRPs 130, and cells 140) and their connection relationships and types as shown in Figures 1A-1C are for illustrative purposes only and do not imply any limitations. Communication network 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure.

[0107] Process Example The principles and embodiments of the present disclosure will now be described in detail with reference to Figure 2, which shows a signaling chart illustrating a communication process 200 according to some embodiments of the present disclosure. For illustrative purposes, the process 200 will be described with reference to Figures 1A-1C.

[0108] Process 200 may involve terminal device 120, network device 110 (either or both of first network device 110-1 or second network device 110-2), and TRP 230 (including at least one of first TRP 230-1 and second TRP 230-2).

[0109] Additionally, the first TRP 130-1 is connected to the first network device 110-1, and the second TRP 130-2 is connected to the first network device 110-1 / second network device 110-2. Additionally, the first TRP 130-1 and the second TRP may be in the same serving cell or in different serving cells.

[0110] In the following text, several embodiments of the present disclosure will be described with reference to two TRPs, but these embodiments are for illustrative purposes only, to help those skilled in the art understand and practice the present disclosure, and do not imply any limitations on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0111] Furthermore, it should be understood that operations at the terminal device 120 and the network device 110 should be coordinated. In other words, the network device 110 and the terminal device 120 should have a common understanding of settings, states, parameters, etc. Such a common understanding may be achieved through any suitable interaction between the network device 110 and the terminal device 120, or by both the network device 110 and the terminal device 120 applying the same rules / policies. In the following, some operations are described from the perspective of the terminal device 120, but it should be understood that the corresponding operations should be performed by the network device 110. Similarly, some operations are described from the perspective of the network device 110, but it should be understood that the corresponding operations should be performed by the terminal device 120. For brevity, some identical or similar content will be omitted herein.

[0112] Additionally, in the following description, several interactions are performed between terminal device 120 and network device 110. It should be understood that the interactions may be realized in one signaling / message or multiple signaling / messages, including system information, RRC messages, DCI messages, uplink control information (UCI) messages, media access control (MAC) control elements (CEs), etc. The present disclosure is not limited in this respect.

[0113] Also, although features / operations are described separately in particular exemplary embodiments, it should be understood that, unless expressly indicated to the contrary, these features / operations described in different exemplary embodiments may be used in any suitable combination.

[0114] Example process for configuration Optionally, according to some embodiments of the present disclosure, terminal device 120 and network device 110 may communicate relevant settings to enable embodiments of the present disclosure described below. During this interactive procedure, certain rules associated with embodiments of the present disclosure may be defined, and relevant redefined / newly introduced parameters / settings may be exchanged between terminal device 120 and network device 110.

[0115] See Figure 2. As shown in Figure 2, the network device 110 may send 210 the associated configuration (i.e., the first message) to the terminal device 120.

[0116] In some embodiments, the associated configuration may be included in an RRC message. In some other embodiments, the associated configuration may be included in any other suitable signaling / message, including but not limited to a DCI message, a MAC CE, etc.

[0117] Furthermore, according to some embodiments of the present disclosure, some resource configurations can be improved, which are described in detail below.

[0118] Settings for CORESET In some embodiments, the network device 110 transmits at least one first message (e.g., an RRC message, for brevity referred to as the first message) to the terminal device 120, where the at least one first message indicates multiple CORESETs and / or multiple TCI states.

[0119] Optionally, the concept of a CORESET group may be introduced. Specifically, there are M DL / combined TCI states (denoted as T_1, T_2, ... T_M), where M is an integer and may be one of {2, 3, 4}. Therefore, there may be M CORESET groups (i.e., M subsets of CORESET denoted as C_1, C_2, ... C_M), and each CORESET group (and corresponding PDSCH) may be associated with one of the M TCI states. For example, C_1 is associated with T_1, C_2 is associated with T_2, etc.

[0120] In view of the introduced CORESET group concept, a CORESET may be associated with one or more CORESET groups.

[0121] In one particular exemplary embodiment, the CORESET may be configured, for example via an RRC message, a MAC CE message, or a DCI message, to have a parameter, which may be an index of the group (represented as CORESETPoolIndex).

[0122] In some embodiments, when M=2 (e.g., in the case of multi-DCI-based multi-TRP), there may be two CORESET groups / subsets of CORESETs based on the setting of CORESETPoolIndex. Specifically, group C_1 may be a CORESET with no setting of CORESETPoolIndex or a CORESET with a setting of CORESETPoolIndex with a value of 0, while group C_2 may be a CORESET with a setting of CORESETPoolIndex with a value of 1.

[0123] Below are some example settings for CORESET.

number

[0124] Thus, the CORESET configuration may be more suitable for multi-TRP scenarios.

[0125] Configuration for uplink resources In some embodiments, the network device 110 sends a first message (eg, an RRC message) to the terminal device 120, where the first message indicates a number of uplink resources (eg, PUCCH resources) and a number of TCI states.

[0126] Optionally, the concept of an uplink resource set (e.g., a PUCCH resource set) may be introduced. Specifically, there are N UL / combined TCI states (denoted as T_1, T_2, ... T_N), where N is an integer and may be one of {2, 3, 4}. Therefore, there may be N PUCCH resource sets (e.g., N PUCCH resource sets denoted as P_1, P_2, ... P_N), where each PUCCH resource set may be associated with one of the N TCI states. For example, P_1 is associated with T_1, P_2 is associated with T_2, etc.

[0127] In view of the introduced uplink resource set concept, an uplink resource may be associated with one or more uplink resource sets.

[0128] In some embodiments, each uplink resource is associated with two or more uplink resource sets.

[0129] In one particular exemplary embodiment, the uplink resource may be configured with a parameter, for example via an RRC message, a MAC CE message, or a DCI message, which may be a group index.

[0130] Alternatively, in another particular exemplary embodiment, the parameters configured for the uplink resources may reuse conventional parameters (e.g., PUCCH-ResourceGroup). The following are some examples of configurations for the uplink resources:

number

[0131] In the particular exemplary embodiment, each group may be associated with one of N TCI states.

[0132] Additionally, in some embodiments, there may be a configuration of associations between at least one CORESET group and at least one PUCCH resource set. In one particular example, each uplink resource is associated with one or more CORESET groups, e.g., the uplink resource is configured to have one or more CORESETPoolIndexes.

[0133] Thus, the configuration of uplink resources may be more suitable for multi-TRP scenarios.

[0134] Setting for RS According to some embodiments of the present disclosure, it is possible to improve the configuration for the RS.

[0135] In some embodiments, for RSs (e.g., Channel State Information RSs (CSI-RSs)) configured to share an indicated aggregate TCI state, there may be a configuration that indicates whether the RS is associated with or based on a particular CORESET group or a particular TCI state. In one particular exemplary embodiment, the RS may be configured to have one of the following: a CORESETPoolIndex, an index of the TCI state, etc.

[0136] In some embodiments, for RSs (e.g., SRSs) configured to share the indicated aggregate TCI state, there may be a configuration indicating which uplink resource set or which TCI state of the N TCI states the RS is associated with or based on. In one particular exemplary embodiment, the RS (e.g., SRS) may be configured to have one of an uplink resource set index, a TCI state index, etc.

[0137] Thus, the RS configuration may be more suitable for multi-TRP scenarios.

[0138] Example process for activation Continuing with reference to Figure 2, after the above setup procedure, network device 110 may send one or more second messages (eg, MAC CE messages) to terminal device 120 (220).

[0139] In some embodiments, the second message indicates at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0140] Thus, using the second message, at least one DL / combined TCI state may be activated for the corresponding CORESET group.

[0141] Alternatively or additionally, in some embodiments, the second message indicates at least one association, where each of the at least one association indicates an association between an uplink resource set and at least one TCI state.

[0142] Thus, with the second message, at least one UL / combined TCI state may be activated for the corresponding uplink resource set.

[0143] Exemplary Process for Uplink Transmission As mentioned above, when N>1 (i.e., N uplink TCI states), each of the N source RSs in the N uplink TCI states provides a reference for determining an uplink TX spatial filter for one of the N beam pair links associated with at least a subset of the dynamically granted / configured grant-based PUSCH and / or dedicated PUCCH resources in the CC.

[0144] In view of this, multi-TRP based PUCCH transmission may be achieved by establishing an association between uplink resources and two or more UL / combined TCI states (or two or more uplink PUCCH resource sets).

[0145] In one particular exemplary embodiment, for multi-TRP-based PUCCH transmission in an integrated TCI framework (i.e., N>1), there are N PUCCH resource sets, each PUCCH resource set associated with two or more of the N UL / combined TCI states (or two or more PUCCH resource sets).

[0146] Continuing to refer to FIG. 2, terminal device 120 (and network device 110) may determine uplink resources (e.g., PUCCH resources) for at least one uplink transmission. Terminal device 120 may then perform the at least one uplink transmission with network device 110 accordingly (240). Specifically, the at least one uplink transmission may be → number of TCI states associated with the uplink resource, or → the number of uplink resource sets associated with the uplink resource, may be performed based on one TCI state or two or more TCI states, based on at least one of:

[0147] Thus, for multi-TRP based PUCCH, dynamic switching between single-TRP and multi-TRP is possible.

[0148] In some embodiments, terminal device 120 performs at least one uplink transmission based on one TCI state when an uplink resource is associated with one TCI state or one uplink resource set. Alternatively, in some embodiments, terminal device 120 performs at least one uplink transmission based on more than one TCI state when an uplink resource is associated with more than one TCI state or more than one uplink resource set.

[0149] In some embodiments, one uplink resource (e.g., a PUCCH resource) may be associated with K uplink resource sets. In one example, 1≦K≦N. In another example, 1≦K≦2. Specifically, if the PUCCH resource is associated with one uplink resource set, the transmission of the PUCCH resource is transmitted based on a single TRP. In one particular embodiment, for DCI format 1_x, the determined PUCCH resource for HARQ-ACK feedback is transmitted based on the indicated TCI state associated with the uplink resource set.

[0150] Alternatively, if a PUCCH resource is associated with two or more uplink resource sets (i.e., K>1), the transmission of the PUCCH resource is transmitted based on multi-TRP. In one particular embodiment, the PUCCH resource is associated with two uplink resource sets (i.e., a first uplink resource set and a second uplink resource set). In this particular embodiment, for DCI format 1_x, the determined PUCCH resource for HARQ-ACK feedback is transmitted based on a first indicated TCI state associated with the first uplink resource set and a second indicated TCI state associated with the second uplink resource set.

[0151] Additionally, the at least one uplink transmission may also be performed based on a repetition parameter configured for the at least one uplink transmission (eg, a repetition parameter configured in an RRC message).

[0152] In some embodiments, the terminal device 120 may be configured to have two PUCCH resource sets (e.g., a first PUCCH resource set and a second PUCCH resource set). Furthermore, each PUCCH resource set may include at least one PUCCH resource. In some embodiments, there may be a TCI state associated with or applied to each PUCCH resource set (e.g., a TCI state for the downlink and uplink or a TCI state for the uplink). Furthermore, the first TCI state may be associated with or applied to the first PUCCH resource set, while the second TCI state may be associated with or applied to the second PUCCH resource set. Specifically, the first TCI state may be different from the second TCI state.

[0153] In some embodiments, one PUCCH resource may be configured to be associated with one or two PUCCH resource sets. In some embodiments, when a PUCCH resource is associated with one PUCCH resource set, PUCCH transmission may be based on a single TRP. In some embodiments, when a PUCCH resource is associated with a first PUCCH resource set, PUCCH transmission may be based on a first TCI state. Alternatively, in some other embodiments, when a PUCCH resource is associated with a second PUCCH resource set, PUCCH transmission may be based on a second TCI state.

[0154] In some embodiments, if a PUCCH resource is associated with two PUCCH resource sets, the PUCCH transmission may be based on multiple TRPs. For example, if a PUCCH resource is associated with a first PUCCH resource set and a second PUCCH resource set, the PUCCH transmission may be based on a first TCI state and a second TCI state. In some embodiments, the PUCCH transmission includes at least one transmission opportunity, and each transmission opportunity may be based on one of the first TCI state and the second TCI state. Alternatively, in some other embodiments, the PUCCH transmission may be based on the first TCI state and the second TCI state simultaneously.

[0155] In one particular embodiment, there may be an indication of a PUCCH resource within the DCI (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2). In some embodiments, the PUCCH resource may be used for HARQ-ACK feedback. Alternatively, in some other embodiments, the indicated PUCCH resource may be transmitted based on the indicated / applied TCI state associated with the PUCCH resource set.

[0156] Specifically, in some embodiments, if the repetition parameter configured for the at least one uplink transmission is greater than 1, terminal device 120 performs the uplink transmission using two or more transmission opportunities based on the two or more TCI states, where each transmission opportunity is associated with one of the two or more TCI states. Additionally, in some embodiments, the number of the two or more transmission opportunities is based on the repetition parameter.

[0157] In one particular embodiment, when the number of repetitions of the PUCCH repetition is greater than 1 (e.g.,

number

[0158] Alternatively, in some embodiments, if the configured repetition parameter for the at least one uplink transmission is absent or equal to 1, terminal device 120 performs the uplink transmission based on the two or more TCI states. For example, terminal device 120 performs uplink transmission based on the two or more TCI states within one transmission opportunity.

[0159] In one particular embodiment, if the repetition parameter is not present or the number of PUCCH repetitions is equal to 1 (e.g.,

number

[0160] Additionally, in some scenarios, terminal device 120 supports up to two uplink TCI states to be configured. For such scenarios, in some embodiments, if the uplink resource is associated with three or more TCI states, terminal device 120 performs the at least one uplink transmission based on two TCI states determined from the three or more TCI states.

[0161] In some embodiments, the two TCI states are: → two TCI states with lower identifiers, → two TCI states with higher identifiers, → The two most recently used TCI states, or two TCI states determined by the terminal device 120 or the network device 110; It is one of them.

[0162] Similarly, in some embodiments, if the uplink resource is associated with three or more TCI states, the terminal device 120 performs the at least one uplink transmission based on two uplink resource sets determined from the three or more uplink resource sets.

[0163] In some embodiments, the two TCI states are: → two uplink resource sets with lower identifiers, → two uplink resource sets with higher identifiers, → The two most recently used uplink resource sets, or → two uplink resource sets determined by the terminal device 120 or the network device 110; It is one of them.

[0164] Additionally, some transmission parameters (e.g., uplink power control parameters) are required for uplink transmission. In some embodiments, if uplink power control parameters are not associated with or included in an uplink / combined TCI state, a set of power control parameters may be configured for the PUCCH resource. Specifically, if a PUCCH resource is associated with K uplink resource sets (where K>1 or K=2), K sets of power control parameters may be configured for the PUCCH resource.

[0165] Furthermore, a path loss RS is also required for uplink transmission. In some embodiments, if a path loss RS is not associated with or included in an uplink / combined TCI state, a path loss RS may be configured for the PUCCH resource. Specifically, if a PUCCH resource is associated with K uplink resource sets (where K>1 or K=2), K path loss RSs may be configured for the PUCCH resource.

[0166] As mentioned above, in the unified TCI framework, the applicable TCI state is indicated in the DCI message. However, in some scenarios, the terminal device 120 may need to perform uplink transmission before receiving the DCI message. The following describes how to handle such scenarios.

[0167] In some embodiments, terminal device 120 may transmit uplink signals as follows: → At least one TCI state currently in use, → TCI state associated with the uplink resource, → one or more TCI states used by the terminal equipment, as indicated by at least one downlink control information (DCI) message, or → at least one spatial domain filter used for the PUSCH, and the PUSCH is at least one of a PUSCH scheduled by a random access response (RAR) uplink grant, a Message A (MsgA) PUSCH, or a PUSCH scheduled during an initial access procedure.

[0168] In some embodiments, before the terminal device 120 receives and applies the first instance of the integrated TCI status indication, transmissions on all PUSCH resources are performed based on the same spatial domain filter as PUSCH transmissions scheduled by an RAR uplink grant or MsgA PUSCH.

[0169] Additionally, when an uplink resource is associated with two or more TCI states or two or more uplink resource sets (i.e., a multi-TRP scenario), it is not guaranteed that all associated TCI states are available, for example, the associated TCI states have not yet been indicated by the DCI message or have not yet been applied according to the application timing. The following describes how to handle such scenarios.

[0170] In some embodiments, the terminal device 120 performs uplink transmission based on two or more TCI states if at least one of the two or more TCI states associated with the uplink resource is indicated and applied after the application timing. Some example processes are described below.

[0171] In some embodiments, when the terminal device 120 receives and applies a first instance of the integrated TCI state indication, transmission of the first and / or second subset of PUCCH resources may be performed based on the same spatial domain filter as the first and second transmission opportunities of the PUSCH scheduled by the RAR UL grant or MsgA PUSCH, respectively.

[0172] Additionally, in some embodiments, if the determined PUCCH resource is associated with the first and second uplink resource sets, multi-TRP transmission is applied to the PUCCH resource.

[0173] In some embodiments, if the terminal device 120 has already received and applied a first aggregated TCI state indication (e.g., for a first uplink resource set) but has not received and applied a first instance of a second aggregated TCI state indication (e.g., for a second uplink resource set), the terminal device 120 may perform a multi-TRP PUCCH transmission using two TCI states (i.e., the first aggregated TCI state, the second TCI state replaced by a spatial domain filter for PUSCH transmissions scheduled by an RAR UL grant or MsgA PUSCH).

[0174] Alternatively, if terminal device 120 has already received and applied a first integrated TCI state indication (e.g., for a first uplink resource set) but has not received and applied a first instance of a second integrated TCI state indication (e.g., for a second uplink resource set), and the determined PUCCH resource is associated only with the first uplink resource set, terminal device 120 may perform a single TRP transmission for the PUCCH resource (based on the first integrated TCI state). Furthermore, if the determined PUCCH resource is associated only with the second uplink resource set, a single TRP transmission is applied for the PUCCH resource (based on a spatial domain filter for PUSCH transmissions scheduled by an RAR UL grant or MsgA·PUSCH). Additionally, if the determined PUCCH resource is associated with both the first and second uplink resource sets, terminal device 120 may perform a single TRP transmission for the PUCCH resource (based on the first integrated TCI state).

[0175] In this way, it is possible to enable multi-TRP based PUCCH transmission independently of the PDSCH transmission scheme, and furthermore, multi-DCI based multi-TRP PDSCH transmission can be jointly applied together with multi-TRP based PUCCH transmission.

[0176] Exemplary Process for Downlink Transmission As described above, for M>1 (i.e., M downlink TCI states), each of the M source RSs (or 2M if qcl_Type2 is configured in addition to qcl_Type1) in the M DL TCIs provides QCL information for at least one of the M beam pair links for UE-dedicated reception on a subset of CORESETs in the PDSCH and / or CC.

[0177] According to some embodiments of the present disclosure, for an integrated TCI framework, multi-TRP based PDSCH transmission is possible.

[0178] In some embodiments, it is possible to realize a multi-TRP based PDSCH transmission without introducing the concept of a CORESET group, i.e., there is only one CORESET group for a CORESET configured to apply a given TCI state, in which case all CORESETs are in one CORESET group and one of two TCI states applies to a CORESET.

[0179] Continuing with reference to FIG. 2, as shown in FIG. 2, network device 110 transmits a DCI message to terminal device 120 (230), where the DCI message indicates at least two TCI states to be used by terminal device 120. Next, network device 110 transmits a PDCCH based on the at least two TCI states (250). For example, network device 110 transmits the PDCCH based on one of the following: a first TCI state of the at least two TCI states; a TCI state with a lower or lowest ID; or a TCI state with a higher or highest ID. Additionally, network device 110 transmits a PDSCH based on at least one of the at least two TCI states. In one exemplary embodiment, network device 110 transmits a PDSCH based on a TCI state different from the TCI state used by the PDCCH. In another exemplary embodiment, network device 110 transmits a PDSCH based on two TCI states.

[0180] In some embodiments, if terminal device 120 does not receive and apply the first instance of any integrated TCI state indication, terminal device 120 assumes that the corresponding DMRS antenna port of the PDCCH / PDSCH is quasi-co-located (e.g., denoted QCL_A in the following as QCLed) with the SS / PBCH block identified by the UE during the initial access procedure, or with the SS / PBCH block or CSI-RS resource identified by terminal device 120 during a random access procedure initiated by reconfiguration with synchronization procedure.

[0181] In some embodiments, before applying the at least two TCI states, the terminal device 120 receives the PDCCH or PDSCH based on the assumption that the DMRS port of the PDCCH or PDSCH is quasi-co-located with the RS identified during the initial access procedure or the random access procedure.

[0182] Alternatively, in some embodiments, before applying the at least two indicated TCI states, the terminal device 120 receives a PDCCH or a PDSCH based on one applied TCI state (i.e., a single TRP).

[0183] In one particular embodiment, if the terminal device 120 has already received a DCI having a first instance of an aggregated TCI state indication but the terminal device 120 has not applied the indicated aggregated TCI state, the terminal device 120 assumes that the DMRS ports of the PDCCH or PDSCH are quasi-co-located in QCL_A (single TRP transmission applies for the scheduled PDSCH in the DCI), regardless of where one or two DL / combined aggregated TCI states are indicated and regardless of whether single TRP / multiple TRP transmission mode is indicated in the DCI.

[0184] Alternatively, or additionally, if the terminal device 120 has already received a DCI having a first instance of an integrated TCI state indication but the terminal device 120 has not applied the indicated integrated TCI state, the terminal device 120 performs a single TRP transmission for the PDSCH scheduled by the DCI before the UE applies the indicated integrated TCI state.

[0185] For better understanding, reference is now made to Figure 3, which illustrates application timing 300. In the specific example of Figure 3, channel transmissions (including PDSCH 310, PDCCH 320, and PDSCH 330) are performed based on the assumption that the PDSCH or DMRS port of the PDSCH is quasi-co-located with the RS identified during the initial access procedure or random access procedure. Also, channel transmissions (including PDSCH 310, PDCCH 320, and PDSCH 330) are performed based on a single TRP.

[0186] Furthermore, the indicated aggregated TCI state may be applied according to the application timing. The application timing of the indicated aggregated TCI state may be considered complete if at least one indicated aggregated TCI state has already been applied. For example, if there is only one indicated aggregated TCI state, the terminal device 120 applies the indicated aggregated TCI state according to the application timing. For another example, if there are two or more indicated aggregated TCI states, the terminal device 120 applies the first TCI state (or a TCI state with a lower / higher ID) of the two or more indicated aggregated TCI states to the CORESET.

[0187] In some embodiments, if only one indicated aggregated TCI state is applied (within a slot) and the terminal device 120 detects a DCI message, the DM-RS antenna port of the PDSCH scheduled by the DCI is performed based on the indicated aggregated TCI state, and regardless of whether one or two DL / combined aggregated TCI states are indicated and regardless of whether single TRP / multiple TRP transmission mode is indicated in the DCI, single TRP transmission is assumed / applied for the PDSCH scheduled by the DCI before the UE applies the indication of two aggregated TCI states.

[0188] In some embodiments, if the following conditions are met: two indicated combined TCI states are applied (within a slot); the offset between the receipt of the DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL; and at least one configured TCI state for the serving cell of the scheduled PDSCH includes a qcl type set to "typeD", the two indicated combined TCI states are assumed for the PDSCH (as default beams). Furthermore, whether one or two of the TCI states apply to the PDSCH is determined based on an indication in the DCI (e.g., a single / multiple TRP transmission mode indication).

[0189] In addition to the above, the concept of a CORESET group may be introduced to realize multi-TRP-based PDSCH transmission. Such an exemplary process is described below.

[0190] In some embodiments, terminal device 120 receives a first message, the first message indicating multiple CORESETs, each of the multiple CORESETs associated with one or more CORESET groups.

[0191] In some embodiments, for a CORESET configured to apply the indicated TCI state, there are two CORESET groups (a first CORESET group and a second CORESET group), and the first TCI state applies to the first CORESET group and the second TCI state applies to the second CORESET group.

[0192] Next, the terminal device 120 receives at least one second message associated with one or more CORESET groups, where the second message indicates at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0193] According to some embodiments of the present disclosure, terminal device 120 may receive a DCI message for scheduling at least one PDSCH, and terminal device 120 may receive the at least one PDSCH based on the DCI.

[0194] In some embodiments, the DCI message indicates a first indication indicating a number of TCIs for the at least one PDSCH.

[0195] Alternatively or additionally, the DCI message indicates a second indication, wherein the second indication indicates one of a plurality of TCI states for the at least one PDSCH, the plurality of TCI states being applied to at least one downlink channel.

[0196] Alternatively or additionally, the DCI message indicates a third indication, where the third indication indicates a TCI order for the at least one PDSCH.

[0197] In some embodiments, within the TCI field of the DCI, each code point is mapped to one DL / combined TCI state, which is applied to the corresponding CORESET group after the application timing.

[0198] In some embodiments, terminal device 120 may receive a DCI, which may schedule at least one PDSCH. In some embodiments, there may be a field within the DCI, which may indicate the number of TCI states for the at least one PDSCH.

[0199] In one particular exemplary embodiment, the bit size for the field may be 1. For example, there may be two possible values ​​in the field (a first value and a second value). The first value may indicate that the at least one PDSCH may be based on one TCI state. For example, the TCI state may apply to the CORESET in which the DCI is received.

[0200] Alternatively, in another particular exemplary embodiment, the second value may indicate that the at least one PDSCH may be based on two TCI states. For example, one of the two TCI states may apply to a first CORESET in which DCI is received. The other of the two TCI states may apply to a second CORESET, which may be in a different CORESET group from the CORESET group of the first CORESET. For example, the first value may be 0 and the second value may be 1. For another example, the first value may be 1 and the second value may be 0.

[0201] In the case of a single DCI based multi-TRP transmission, there is a field in the DCI to indicate single TRP or multi-TRP transmission (if present) for the scheduled PDSCH.

[0202] In one particular example, the DCI includes a 1-bit field, where a value of "0" / "1" indicates a single-TRP transmission (based on the currently applied first TCI state) and a value of "1" / "0" indicates a multi-TRP transmission (based on the currently applied first and second TCI states).

[0203] In another specific example, the DCI includes a 2-bit field, where the four values ​​of the 2 bits indicate single TRP (first TCI), multi TRP (order 1, first TCI, second TCI), multi TRP (order 2, second TCI, first TCI), and single TRP (second TCI), respectively.

[0204] In another specific example, the DCI includes a 3-bit field, where different values ​​of the 3 bits indicate single TRP (first TCI), multi-TRP (order 1, first TCI, second TCI), multi-TRP (order 2, second TCI, first TCI), single TRP (second TCI), and simultaneous multi-TRP reception, respectively.

[0205] In some embodiments, within the TCI field of the DCI, each code point is mapped to one or two DL / combined TCI states. In one particular exemplary embodiment, the same MAC CE message may be used for code point mapping. Furthermore, a first DL / combined TCI state is applied to a first CORESET group after an application timing, and a second DL / combined TCI state (if two TCI states are indicated in the DCI) is applied to a second CORESET group. Alternatively, in another particular exemplary embodiment, separate MAC CEs may be used for code point mapping. Specifically, for each CORESET group, the one TCI state within the DL / combined TCI state or the first DL / combined TCI state is applied to the CORESET group after an application timing, and the second TCI state (if present) is applied to the other CORESET group after an application timing.

[0206] In some embodiments, in the case of a single-DCI-based multi-TRP transmission, there is a field in the DCI to indicate a single-TRP or a multi-TRP transmission (if present) for the scheduled PDSCH. In one particular example, the DCI includes a 1-bit field, where a value of '0' / '1' indicates a single-TRP transmission (based on the currently applied first TCI state) and a value of '1' / '0' indicates a multi-TRP transmission (based on the currently applied first and second TCI states). In another particular example, the DCI includes a 2-bit field, where four values ​​of the 2 bits indicate single TRP (first TCI), multi TRP (order 1, first TCI, second TCI), multi TRP (order 2, second TCI, first TCI), and single TRP (second TCI), respectively.

[0207] Thus, the single DCI may indicate whether a single-TRP PDSCH or a multi-TRP PDSCH is applied. For better understanding, reference is now made to FIG. 4A and FIG. 4B, where FIG. 4A illustrates an example scenario 400 in which embodiments of the present disclosure can be implemented, and FIG. 4B illustrates example application timing 450. As shown in FIG. 1A, terminal device 120 communicates with TRPs 130-1 and 130-2 based on first and second TCI states. As shown in FIG. 4B, terminal device 120 receives a DCI message indicating a single-TRP or multi-TRP transmission, which may be, for example, any of the first, second, and third indications described above. Then, as described above, the next scheduled PDSCH may be performed based on the DCI.

[0208] Example Process for Activating a TCI State In a related solution, the terminal device applies a TCI state after receiving a DC message. Specifically, it has been agreed that at least a UE-specific (unicast) DCI is used to support L1-based beam direction, thereby indicating combined or separate DL / UL beam direction from the active TCI state.

[0209] According to some embodiments of the present disclosure, the time point for applying the TCI state may be accelerated.

[0210] Specifically, in some embodiments, terminal device 120 receives a second message (e.g., a MAC CE message) from network device 110 indicating at least one mapping, where each mapping indicates a correspondence between a TCI codepoint and at least one TCI state, and terminal device 120 applies the at least one TCI state indicated by the second message after an application timing if the at least one TCI state satisfies an application condition.

[0211] In some embodiments, terminal device 120 may determine whether an applicable condition is met based on one or more parameters, such as: → number of TCI states for downlink transmissions supported by terminal device 120, → number of TCI states for uplink transmissions supported by terminal device 120, → the number of TCI states for downlink transmission indicated by the second message, → the number of TCI states for uplink transmission indicated in the second message, → TCI state for downlink transmission indicated by the second message, → TCI state for uplink transmission indicated by the second message, → number of TCI states for the CORESET group indicated by the second message, → the number of TCI states for the uplink resource set indicated in the second message, → the number of TCI states for the RS set indicated in the second message, → number of CORESET groups configured for the terminal device, → the number of uplink resource sets configured for the terminal device, or → number of RS sets configured for the terminal device, It is listed as:

[0212] It should be understood that the above examples of the one or more parameters are provided for illustrative purposes only and do not imply any limitations. In other exemplary embodiments, other parameters may be applied. The present disclosure is not limited in this respect.

[0213] In some embodiments, the network device 120 → The TCI state is the only TCI state for uplink transmissions, → The TCI state is the only TCI state for downlink transmissions, → the TCI state is the only TCI state for the CORESET group, → The TCI state is the only TCI state for the uplink resource set, or → the TCI state is the only TCI state for the RS set, If one of the following conditions is met, it is determined that the TCI state satisfies the applicable condition.

[0214] It should be understood that the above example conditions for determining whether a TCI state satisfies the applicable conditions are provided for illustrative purposes only and do not imply any limitations. In other example embodiments, other conditions may be defined. The present disclosure is not limited in this respect.

[0215] In some embodiments, if only one code point is activated by the MAC CE message (e.g., mapped to only one TCI state for the downlink and uplink. For another example, mapped to at least one of a TCI state for the downlink and a TCI state for the uplink), the single TCI state is applied after the MAC CE activation timing (e.g., 3 ms after the HARQ-ACK feedback). In other words, if only one code point is activated by the MAC CE message, a DCI message indicating the only TCI state is not necessary. Terminal device 120 may apply the only TCI state after the application timing for the MAC CE message.

[0216] In one particular exemplary embodiment, if a UE (i.e., terminal device 120) transmits a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying an activation command, the indicated mapping between the TCI state and the codepoint of the DCI field "Transmission Configuration Indication" is

number

[0217] In some embodiments, if there is only one activated [TCI-State] set in [tci-StateId_r17] for DL ​​and UL, the one activated [TCI-State] set in [tci-StateId_r17] is

number

[0218] In some embodiments, if there is only one activated [TCI-State] set in [tci-StateId_r17] for DL ​​only and / or there is only one activated [TCI-State] set in [tci-StateId_r17] for UL only, the one activated [TCI-State] set in [tci-StateId_r17] is used for the slot

number

[0219] In some embodiments, if there is only one activated [TCI-State] configured in [tci-StateId_r17] for DL ​​and UL, or if there is only one activated [TCI-State] configured in [tci-StateId_r17] for DL ​​only and / or there is only one activated [TCI-State] configured in [tci-StateId_r17] for UL only, the activated [TCI-State] configured in [tci-StateId_r17] is the slot

number

[0220] Additionally, since there is no need for a DCI message indicating only one TCI state, the TCI field in the DCI may not be present.

[0221] Specifically, in some embodiments, for DCI format 1_1, if the upper layer parameter tci-PresentInDCI is not enabled or if the number of code points in this field is 1, the transmission configuration indication (TCI field) is 0 bit.

[0222] Specifically, in some embodiments, for DCI format 1_2, if the upper layer parameter tci-PresentDCI-1-2 is not set or if the number of code points S in this field is 1, the transmission configuration indication (TCI field) is 0 bit.

[0223] In some embodiments, if only one or at most one DL / combined TCI state is activated for a subset (M>1) of CORESETs or for all CORESETs (M=1), the activated DL / combined TCI state applies from the first slot after MAC CE confirmation.

[0224] In some embodiments, if only one or at most one UL / combined TCI state is activated for a subset (N>1) of PUCCHs or for all PUCCHs (N=1), the activated UL / combined TCI state applies from the first slot after MAC CE confirmation.

[0225] For better understanding, some example scenarios for different values ​​of M and N are described in Table 1 below. [Table 1] TIFF0007758213000014.tif232168

[0226] In some embodiments, for a single DCI based multi-TRP transmission (i.e., M>1), if there are M CORESET groups and for each subset of CORESET there is only one DL or combined TCI state activated by the MAC CE, then the DL or combined TCI state should be applied to each subset from the first slot after MAC CE confirmation.

[0227] Alternatively, in some embodiments, for a single DCI-based multi-TRP transmission (i.e., M>1), if there is only one CORESET group (i.e., there is no concept of all CORESETs or CORESET groups) and only one DL or combined TCI state is activated for a subset of DL channels / RSs, then only one of the M TCI states applies to all CORESETs. For example, an activated TCI state may apply to each subset after MAC CE confirmation, and one of the M TCI states may apply to all CORESETs after MAC CE confirmation. In one particular exemplary embodiment, if a single codepoint maps to two DL or combined TCI states, then the first TCI state or the TCI state with the lowest ID applies to all CORESETs, and the single-TRP or multi-TRP transmission is indicated by a field in the DCI. Alternatively, in another exemplary embodiment, if there are two or more code points, the lowest code point with DL or associated TCI status or DL ​​or associated TCI status with the lower / lowest ID applies to all CORESETs.

[0228] Alternatively, in some embodiments, for a single DCI-based multi-TRP transmission (i.e., M>1), if there is only one subset of CORESET (i.e., there is no concept of all CORESETs or CORESET groups) and only one DL or combined TCI state is activated for a subset of DL channels / RSs, any one of the M TCI states may be further indicated by the DCI to be applied to all CORESETs. In one particular exemplary embodiment, the activated TCI state may be applied to each subset of DL channels / RSs (excluding PDCCH) respectively after MAC CE confirmation. Additionally, in another exemplary embodiment, for a CORESET (configured to share an indicated combined TCI state), one DL TCI state indicated in the DCI (if only one DL TCI state maps to a codepoint) or the first DL TCI state of two indicated DL TCI states (if two DL TCI states map to a codepoint) is applied after beam application timing.

[0229] In some embodiments, terminal device 120 may transmit HARQ-ACK information in slot n corresponding to at least one of at least one DCI carrying the TCI state indication and having no downlink allocation and at least one PDSCH scheduling according to the at least one DCI carrying the TCI state indication, and the indicated TCI state may be applied after the application timing. In one particular exemplary embodiment, the indicated TCI state may be different from a previously indicated TCI state. In one particular exemplary embodiment, the HARQ-ACK information may be an ACK.

[0230] In some embodiments, the HARQ-ACK information may be transmitted within the PUCCH resource. In some embodiments, there may be at least one PUSCH transmission within slot n, and the HARQ-ACK information may be multiplexed within the PUSCH resource. The application timing may be the first slot or the first subslot that is at least Y symbols after the last symbol of the PUSCH resource. For example, Y may be an integer, where 1≦Y≦336. For another example, Y may be one of {7, 14, 28, 224, 336}. In some embodiments, a slot may include 12 or 14 symbols. In some embodiments, a subslot may include S symbols, where S is an integer, where 1≦S≦14. For example, S may be one of {2, 4, 7}.

[0231] In some embodiments, if the PUCCH resources used for the repetition of the PUCCH transmission by terminal device 120 include first and second spatial configurations or first and second sets of power control parameters, and terminal device 120 is provided with subslotLengthForPUCCH, terminal device 120 may transmit the PUCCH transmission and the first and second repetitions of the UCI consecutively within the slot, and terminal device 120 may:

number

[0232]

number

[0233] Example method 5 is a flowchart of an exemplary method 500 according to some embodiments of the present disclosure. For example, the method 500 may be implemented in a terminal device 120 such as those shown in FIGS. 1A-1C.

[0234] At block 510, terminal device 120 determines uplink resources for at least one uplink transmission.

[0235] In block 520, the terminal device 120 performs at least one uplink transmission based on one TCI state or two or more TCI states based on at least one of the number of TCI states associated with the uplink resource or the number of uplink resource sets associated with the uplink resource, where each uplink resource set corresponds to a TCI state.

[0236] In some embodiments, the terminal device 120 performing at least one uplink transmission includes at least one of performing the at least one uplink transmission based on one TCI state if the uplink resource is associated with one TCI state or one uplink resource set, or performing the at least one uplink transmission based on two or more TCI states if the uplink resource is associated with two or more TCI states or two or more uplink resource sets.

[0237] In some embodiments, the terminal device 120 performing at least one uplink transmission based on two or more TCI states includes at least one of performing uplink transmission using two or more transmission opportunities based on two or more TCI states when a repetition parameter configured for the at least one uplink transmission is greater than one, each transmission opportunity being associated with one of the two or more TCI states, or performing uplink transmission based on two or more TCI states when a repetition parameter configured for the at least one uplink transmission is absent or equal to one.

[0238] In some embodiments, the terminal device 120 performing an uplink transmission includes at least one of performing at least one uplink transmission based on two TCI states determined from the three or more TCI states when the uplink resource is associated with three or more TCI states, or performing at least one uplink transmission based on two uplink resource sets determined from the three or more uplink resource sets when the uplink resource is associated with three or more uplink resource sets.

[0239] In some embodiments, the two TCI states are one of two TCI states with lower identifiers, two TCI states with higher identifiers, two most recently used TCI states, or two TCI states determined by the terminal device 120 or the network device 110.

[0240] In some embodiments, the two uplink resource sets are one of two uplink resource sets with lower identifiers, two uplink resource sets with higher identifiers, two most recently used uplink resource sets, or two uplink resource sets determined by the terminal device 120 or the network device 110.

[0241] In some embodiments, the terminal device 120 receives a first message from the network device 110, the first message indicating at least one uplink resource, each associated with one or more uplink resource sets, and a plurality of TCI states.

[0242] In some embodiments, the terminal device 120 receives a second message from the network device indicating at least one association, each of the at least one association indicating an association between an uplink resource set and at least one TCI state.

[0243] In some embodiments, the terminal device 120 performs uplink transmission based on at least one of the following: at least one TCI state currently in use; a TCI state associated with an uplink resource; one or more TCI states used by the terminal device 120 indicated by the at least one DCI message; or at least one spatial domain filter used for a PUSCH, where the PUSCH is at least one of a PUSCH scheduled by an RAR uplink grant, an MsgA PUSCH, or a PUSCH scheduled during an initial access procedure.

[0244] In some embodiments, the terminal device 120 performs uplink transmission based on two or more TCI states if at least one of the two or more TCI states associated with the uplink resource is indicated and applied after the application timing.

[0245] 6 is a flowchart of an example method 600 according to some embodiments of the present disclosure. For example, the method 600 may be implemented in a terminal device 120 such as those shown in FIGS. 1A-1C.

[0246] In block 610 , terminal device 120 receives a DCI message indicating at least two TCI states used by terminal device 120 .

[0247] In block 620, the terminal device 120 performs at least one of receiving a PDCCH based on one of the at least two TCI states or receiving a PDSCH based on at least one of the at least two TCI states.

[0248] In some embodiments, before applying the at least two indicated TCI states, the terminal device 120 receives the PDCCH or PDSCH based on at least one of: assuming that the DMRS port of the PDCCH or PDSCH is quasi-co-located with the RS identified during the initial access procedure or the random access procedure; or one applied TCI state.

[0249] 7 is a flowchart of an example method 700 according to some embodiments of the present disclosure. For example, the method 700 may be implemented in a terminal device 120 such as those shown in FIGS. 1A-1C.

[0250] In block 710, the terminal device 120 receives DCI for scheduling at least one PDSCH, the DCI message indicating at least one of a first indication indicating the number of TCIs for the at least one PDSCH, a second indication indicating one of a plurality of TCI states for the at least one PDSCH, where the plurality of TCI states apply to at least one downlink channel, or a third indication indicating a TCI order for the at least one PDSCH.

[0251] In block 720, terminal device 120 receives the at least one PDSCH based on the DCI.

[0252] In some embodiments, terminal device 120 receives a first message from network device 110 indicating a plurality of CORESETs, each of the plurality of CORESETs associated with a CORESET group.

[0253] In some embodiments, the terminal device 120 is configured to receive at least one second message associated with one or more CORESET groups from the network device 110, the at least one second message indicating at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0254] 8 is a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in a terminal device 120 such as those shown in FIGS. 1A-1C.

[0255] At block 810, terminal device 120 receives a second message from network device 110 indicating at least one mapping at terminal device 120, each mapping indicating a correspondence between a TCI codepoint and at least one TCI state.

[0256] In block 820, terminal device 120 determines whether at least one TCI state satisfies an applicable condition.

[0257] In block 830, the terminal device 120 applies the at least one TCI state indicated by the second message after the application timing if the at least one TCI state satisfies the application condition.

[0258] In some embodiments, the terminal device 120 determines whether the application condition is met based on at least one of the following: the number of TCI states for downlink transmission supported by the terminal device 120; the number of TCI states for uplink transmission supported by the terminal device 120; the number of TCI states for downlink transmission indicated by the second message; the number of TCI states for uplink transmission indicated in the second message; the TCI states for downlink transmission indicated by the second message; the TCI states for uplink transmission indicated by the second message; the number of TCI states for CORESET groups indicated by the second message; the number of TCI states for uplink resource sets indicated in the second message; the number of TCI states for RS sets indicated in the second message; the number of CORESET groups configured for the terminal device 120; the number of uplink resource sets configured for the terminal device 120; or the number of RS sets configured for the terminal device 120.

[0259] In some embodiments, the network device 120 determines that the TCI state satisfies the applicable condition if one of the following is met: the TCI state is the only TCI state for uplink transmission, the TCI state is the only TCI state for downlink transmission, the TCI state is the only TCI state for the CORESET group, the TCI state is the only TCI state for the uplink resource set, or the TCI state is the only TCI state for the RS set.

[0260] 9 is a flowchart of an example method 900 according to some embodiments of the present disclosure. For example, the method 900 may be implemented in a network device 110 such as those shown in FIGS. 1A-1C.

[0261] At block 910, the network device 110 determines uplink resources for at least one uplink transmission.

[0262] In block 920, the network device 110 receives an uplink transmission from the terminal device 120 based on one TCI state or two or more TCI states based on at least one of the number of TCI states associated with the uplink resource or the number of uplink resource sets associated with the uplink resource, each of the uplink resource sets corresponding to a TCI state.

[0263] In some embodiments, the network device 110 receiving at least one uplink transmission includes at least one of receiving at least one uplink transmission based on one TCI state if the uplink resource is associated with one TCI state or one uplink resource set, or receiving at least one uplink transmission based on two or more TCI states if the uplink resource is associated with two or more TCI states or two or more uplink resource sets.

[0264] In some embodiments, the network device 110 receiving at least one uplink transmission based on two or more TCI states includes at least one of: receiving at least one uplink transmission using two or more transmission opportunities based on the two or more TCI states if a repetition parameter configured for the at least one uplink transmission is greater than one, each transmission opportunity being associated with one of the two or more TCI states; or receiving at least one uplink transmission based on the two or more TCI states if a repetition parameter configured for the at least one uplink transmission is absent or equal to one.

[0265] In some embodiments, the network device 110 receiving at least one uplink transmission includes at least one of: performing the at least one uplink transmission based on two TCI states determined from the three or more TCI states when the uplink resource is associated with three or more TCI states; or receiving the uplink transmission based on two uplink resource sets determined from the three or more uplink resource sets when the uplink resource is associated with three or more uplink resource sets.

[0266] In some embodiments, the two TCI states are one of two TCI states with lower identifiers, two TCI states with higher identifiers, two most recently used TCI states, or two TCI states determined by the terminal device 120 or the network device 110.

[0267] In some embodiments, the two uplink resource sets are one of two uplink resource sets with lower identifiers, two uplink resource sets with higher identifiers, two most recently used uplink resource sets, or two uplink resource sets determined by the terminal device 120 or the network device 110.

[0268] In some embodiments, the network device 110 transmits a first message to the terminal device 120, the first message indicating at least one uplink resource, each associated with one or more uplink resource sets, and a plurality of TCI states.

[0269] In some embodiments, the network device 110 transmits a second message to the terminal device 120 indicating at least one association, each of the at least one association indicating an association between an uplink resource set and at least one TCI state.

[0270] In some embodiments, the network device 110 receives uplink transmissions based on at least one of the following: at least one TCI state currently in use, a TCI state associated with an uplink resource, one or more TCI states used by the terminal device 120 indicated by the at least one DCI message, or at least one spatial domain filter used for a PUSCH, where the PUSCH is at least one of a PUSCH scheduled by an RAR uplink grant, an MsgA PUSCH, or a PUSCH scheduled during an initial access procedure.

[0271] In some embodiments, the network device 110 receives an uplink transmission based on two or more TCI states if at least one of the two or more TCI states associated with the uplink resource is indicated and applied after the application timing.

[0272] 10 is a flowchart of an example method 1000 according to some embodiments of the present disclosure. For example, the method 1000 may be implemented in a network device 110 such as those shown in FIGS. 1A-1C.

[0273] In block 1010 , network device 110 transmits a DCI message to terminal device 120 indicating at least two TCI states used by terminal device 120 .

[0274] In block 1020, the network device 110 performs at least one of transmitting a PDCCH based on one of the at least two TCI states or transmitting a PDSCH based on at least one of the at least two TCI states.

[0275] In some embodiments, before applying the at least two indicated TCI states, the network device 110 transmits the PDCCH or PDSCH based on at least one of: the DMRS port of the PDCCH or PDSCH transmission being quasi-co-located with an RS identified during the initial access procedure or the random access procedure; or one applied TCI state.

[0276] 11 is a flowchart of an example method 1100 according to some embodiments of the present disclosure. For example, the method 1100 may be implemented in a network device 110 such as those shown in FIGS. 1A-1C.

[0277] In block 1110, the network device 110 transmits a DCI message for scheduling at least one PDSCH to the terminal device 120, the DCI message indicating at least one of a first indication indicating the number of TCIs for the at least one PDSCH, a second indication indicating one of a plurality of TCI states for the at least one PDSCH, the second indication indicating that the plurality of TCI states are applied to at least one downlink channel, and a third indication indicating a TCI order for the at least one PDSCH.

[0278] In block 1120, network device 110 transmits the at least one PDSCH to terminal device 120 based on the DCI.

[0279] In some embodiments, the network device 110 transmits a first message to the terminal device 120 indicating a plurality of CORESETs, each of the plurality of CORESETs being associated with a CORESET group.

[0280] In some embodiments, the network device 110 sends at least one second message associated with one or more CORESET groups to the terminal device 120, the at least one second message indicating at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0281] 12 is a flowchart of an example method 1200 according to some embodiments of the present disclosure. For example, the method 1200 may be implemented in a network device 110 such as those shown in FIGS. 1A-1C.

[0282] At block 1210, network device 110 transmits a second message to terminal device 120 indicating at least one mapping, each mapping indicating a correspondence between a TCI codepoint and at least one TCI state.

[0283] In block 1220, the network device 110 determines whether the TCI status meets the applicable conditions.

[0284] In block 1230, the network device 110 applies the at least one TCI state indicated by the second message after the application timing if the TCI state satisfies the application condition.

[0285] In some embodiments, the network device 110 determines whether the application condition is met based on at least one of the number of TCI states for downlink transmission supported by the terminal device 120, the number of TCI states for uplink transmission supported by the terminal device 120, the number of TCI states for downlink transmission indicated by the second message, the number of TCI states for uplink transmission indicated in the second message, one TCI state for downlink transmission indicated by the second message, one TCI state for uplink transmission indicated by the second message, the number of TCI states for CORESET groups indicated by the second message, the number of TCI states for uplink resource sets indicated in the second message, the number of TCI states for RS sets indicated in the second message, the number of CORESET groups configured for the terminal device 120, the number of uplink resource sets configured for the terminal device 120, or the number of RS sets configured for the terminal device 120.

[0286] In some embodiments, the network device 110 determines that the TCI state satisfies the applicable condition if one of the following is met: the TCI state is the only TCI state for uplink transmission, the TCI state is the only TCI state for downlink transmission, the TCI state is the only TCI state for the CORESET group, the TCI state is the only TCI state for the uplink resource set, or the TCI state is the only TCI state for the RS set.

[0287] Device example In some exemplary embodiments, the terminal device 120 comprises circuitry configured to determine uplink resources for at least one uplink transmission and to perform the at least one uplink transmission based on one TCI state or two or more TCI states based on at least one of the number of TCI states associated with the uplink resource or the number of uplink resource sets associated with the uplink resource, where each uplink resource set corresponds to a TCI state.

[0288] In some embodiments, the terminal device 120 performing at least one uplink transmission includes at least one of performing the at least one uplink transmission based on one TCI state if the uplink resource is associated with one TCI state or one uplink resource set, or performing the at least one uplink transmission based on two or more TCI states if the uplink resource is associated with two or more TCI states or two or more uplink resource sets.

[0289] In some embodiments, the circuitry further includes at least one of: performing the at least one uplink transmission based on the two or more TCI states using two or more transmission opportunities when a repetition parameter configured for the at least one uplink transmission is greater than one, each transmission opportunity being associated with one of the two or more TCI states; or performing the uplink transmission based on the two or more TCI states when a repetition parameter configured for the at least one uplink transmission is absent or equal to one.

[0290] In some embodiments, the circuitry further comprises: performing at least one of: if the uplink resource is associated with three or more TCI states, performing at least one uplink transmission based on two TCI states determined from the three or more TCI states; or, if the uplink resource is associated with three or more uplink resource sets, performing at least one uplink transmission based on two uplink resource sets determined from the three or more uplink resource sets.

[0291] In some embodiments, the two TCI states are one of two TCI states with lower identifiers, two TCI states with higher identifiers, two most recently used TCI states, or two TCI states determined by the terminal device 120 or the network device 110.

[0292] In some embodiments, the two uplink resource sets are one of two uplink resource sets with lower identifiers, two uplink resource sets with higher identifiers, two most recently used uplink resource sets, or two uplink resource sets determined by the terminal device 120 or the network device 110.

[0293] In some embodiments, the circuitry is further configured to receive a first message from the network device 110, the first message indicating at least one uplink resource, each associated with one or more uplink resource sets, and a plurality of TCI states.

[0294] In some embodiments, the circuitry is further configured to receive a second message from the network device 110 indicating at least one association, each of the at least one association indicating an association between an uplink resource set and at least one TCI state.

[0295] In some embodiments, the circuitry is further configured to perform uplink transmission based on at least one of: at least one TCI state currently in use; a TCI state associated with an uplink resource; one or more TCI states used by the terminal device 120 indicated by the at least one DCI message; or at least one spatial domain filter used for a PUSCH, wherein the PUSCH is at least one of a PUSCH scheduled by an RAR uplink grant, an MsgA PUSCH, or a PUSCH scheduled during an initial access procedure.

[0296] In some embodiments, the circuitry is further configured to perform an uplink transmission based on the two or more TCI states if at least one of the two or more TCI states associated with the uplink resource is indicated and applied after the application timing.

[0297] In some exemplary embodiments, the terminal device 120 comprises circuitry configured to receive a DCI message indicating at least two TCI states used by the terminal device 120 and perform at least one of receiving a PDCCH based on one of the at least two TCI states or receiving a PDSCH based on at least one of the at least two TCI states.

[0298] In some embodiments, the circuitry is further configured to receive the PDCCH or PDSCH based on at least one of: assuming that a DMRS port of the PDCCH or PDSCH is quasi-co-located with an RS identified during the initial access procedure or the random access procedure, or one applied TCI state, before applying the at least two indicated TCI states.

[0299] In some exemplary embodiments, terminal device 120 comprises circuitry configured to receive DCI for scheduling at least one PDSCH, the DCI message indicating at least one of a first indication indicating a number of TCIs for the at least one PDSCH, a second indication indicating one of a plurality of TCI states for the at least one PDSCH, where the plurality of TCI states apply to at least one downlink channel, or a third indication indicating a TCI order for the at least one PDSCH, and is configured to receive at least one PDSCH based on the DCI.

[0300] In some embodiments, the circuitry is further configured to receive a first message from the network device 110 indicating a plurality of CORESETs, each of the plurality of CORESETs associated with a CORESET group.

[0301] In some embodiments, the circuitry is further configured to receive at least one second message from the network device 110 associated with one or more CORESET groups, the at least one second message indicating at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0302] In some exemplary embodiments, the terminal device 120 comprises circuitry configured to receive, at the terminal device 120, a second message from the network device 110 indicating at least one mapping, each mapping indicating a correspondence between a TCI code point and at least one TCI state, determine whether the at least one TCI state satisfies an application condition, and apply the at least one TCI state indicated by the second message after an application timing if the at least one TCI state satisfies the application condition.

[0303] In some embodiments, the circuitry is further configured to determine whether the application condition is met based on at least one of the number of TCI states for downlink transmissions supported by the terminal device 120, the number of TCI states for uplink transmissions supported by the terminal device 120, the number of TCI states for downlink transmissions indicated by the second message, the number of TCI states for uplink transmissions indicated in the second message, the TCI states for downlink transmissions indicated by the second message, the TCI states for uplink transmissions indicated by the second message, the number of TCI states for CORESET groups indicated by the second message, the number of TCI states for uplink resource sets indicated in the second message, the number of TCI states for RS sets indicated in the second message, the number of CORESET groups configured for the terminal device 120, the number of uplink resource sets configured for the terminal device 120, or the number of RS sets configured for the terminal device 120.

[0304] In some embodiments, the circuitry is further configured to determine that the TCI state satisfies the applicable condition if one of the following is met: the TCI state is the only TCI state for uplink transmission, the TCI state is the only TCI state for downlink transmission, the TCI state is the only TCI state for a CORESET group, the TCI state is the only TCI state for an uplink resource set, or the TCI state is the only TCI state for an RS set.

[0305] In some exemplary embodiments, the network device 110 comprises circuitry configured to determine uplink resources for at least one uplink transmission and receive the uplink transmission from the terminal device 120 based on one TCI state or two or more TCI states based on at least one of the number of TCI states associated with the uplink resource or the number of uplink resource sets associated with the uplink resource, each of the uplink resource sets corresponding to a TCI state.

[0306] In some embodiments, the circuitry further comprises: receiving at least one uplink transmission based on one TCI state if the uplink resource is associated with one TCI state or one uplink resource set; or receiving at least one uplink transmission based on two or more TCI states if the uplink resource is associated with two or more TCI states or two or more uplink resource sets.

[0307] In some embodiments, the circuitry further includes at least one of: receiving the at least one uplink transmission based on the two or more TCI states using two or more transmit opportunities if a configured repetition parameter for the at least one uplink transmission is greater than one, each transmit opportunity being associated with one of the two or more TCI states; or receiving the at least one uplink transmission based on the two or more TCI states if the configured repetition parameter for the at least one uplink transmission is absent or equal to one.

[0308] In some embodiments, the circuitry further includes at least one of: if the uplink resource is associated with three or more TCI states, performing the at least one uplink transmission based on two TCI states determined from the three or more TCI states; or if the uplink resource is associated with three or more uplink resource sets, receiving the uplink transmission based on two uplink resource sets determined from the three or more uplink resource sets.

[0309] In some embodiments, the two TCI states are one of two TCI states with lower identifiers, two TCI states with higher identifiers, two most recently used TCI states, or two TCI states determined by the terminal device 120 or the network device 110.

[0310] In some embodiments, the two uplink resource sets are one of two uplink resource sets with lower identifiers, two uplink resource sets with higher identifiers, two most recently used uplink resource sets, or two uplink resource sets determined by the terminal device 120 or the network device 110.

[0311] In some embodiments, the circuitry further transmits a first message to the terminal device 120, the first message indicating at least one uplink resource, each associated with one or more uplink resource sets, and a plurality of TCI states.

[0312] In some embodiments, the circuitry is further configured to transmit a second message to the terminal device 120 indicating at least one association, each of the at least one association indicating an association between an uplink resource set and at least one TCI state.

[0313] In some embodiments, the circuitry is further configured to receive uplink transmissions based on at least one of: at least one TCI state currently in use; a TCI state associated with an uplink resource; one or more TCI states used by the terminal device 120 indicated by the at least one DCI message; or at least one spatial domain filter used for a PUSCH, wherein the PUSCH is at least one of a PUSCH scheduled by an RAR uplink grant, an MsgA PUSCH, or a PUSCH scheduled during an initial access procedure.

[0314] In some embodiments, the circuitry is further configured to receive an uplink transmission based on the two or more TCI states if at least one of the two or more TCI states associated with the uplink resource is indicated and applied after the application timing.

[0315] In some exemplary embodiments, the network device 110 comprises circuitry configured to transmit a DCI message to the terminal device 120 indicating at least two TCI states used by the terminal device 120, and to perform at least one of transmitting a PDCCH based on one of the at least two TCI states, or transmitting a PDSCH based on at least one of the at least two TCI states.

[0316] In some embodiments, the circuitry is further configured to, before applying the at least two indicated TCI states, transmit the PDCCH or PDSCH based on at least one of: a DMRS port of the PDCCH or PDSCH transmission being quasi-co-located with an RS identified during the initial access procedure or the random access procedure, or one applied TCI state.

[0317] In some exemplary embodiments, the network device 110 comprises circuitry configured to transmit, at the network device 110, a DCI for scheduling at least one PDSCH to the terminal device 120, the DCI message indicating at least one of: a first indication indicating a number of TCIs for the at least one PDSCH; a second indication indicating one of a plurality of TCI states for the at least one PDSCH, the second indication indicating one of the TCI states being applied to at least one downlink channel; and a third indication indicating a TCI order for the at least one PDSCH, and to transmit the at least one PDSCH to the terminal device 120 based on the DCI.

[0318] In some embodiments, the circuitry is further configured to transmit a first message to terminal device 120 indicating a plurality of CORESETs, each of the plurality of CORESETs associated with a CORESET group.

[0319] In some embodiments, the circuitry is further configured to transmit at least one second message associated with one or more CORESET groups to the terminal device 120, the at least one second message indicating at least one association, each association indicating an association between a CORESET group and at least one TCI state.

[0320] In some exemplary embodiments, the network device 110 comprises circuitry configured to send a second message to the terminal device 120 indicating at least one mapping, each mapping indicating a correspondence between a TCI code point and at least one TCI state, determine whether the TCI state satisfies an application condition, and apply the at least one TCI state indicated by the second message after an application timing if the TCI state satisfies the application condition.

[0321] In some embodiments, the circuitry is further configured to determine whether the application condition is met based on at least one of the following: the number of TCI states for downlink transmissions supported by the terminal device 120; the number of TCI states for uplink transmissions supported by the terminal device 120; the number of TCI states for downlink transmissions indicated by the second message; the number of TCI states for uplink transmissions indicated in the second message; one TCI state for downlink transmissions indicated by the second message; one TCI state for uplink transmissions indicated by the second message; the number of TCI states for CORESET groups indicated by the second message; the number of TCI states for uplink resource sets indicated in the second message; the number of TCI states for RS sets indicated in the second message; the number of CORESET groups configured for the terminal device 120; the number of uplink resource sets configured for the terminal device 120; or the number of RS sets configured for the terminal device 120.

[0322] In some embodiments, the circuitry is further configured to determine that the TCI state satisfies the applicable condition if one of the following is met: the TCI state is the only TCI state for uplink transmission, the TCI state is the only TCI state for downlink transmission, the TCI state is the only TCI state for a CORESET group, the TCI state is the only TCI state for an uplink resource set, or the TCI state is the only TCI state for an RS set.

[0323] 13 is a schematic block diagram of an apparatus 1300 suitable for implementing embodiments of the present disclosure. The apparatus 1300 can be considered as another exemplary implementation of the terminal device 120 and the network devices 110-1 and 110-2 shown in FIGS. 1A-1C. Accordingly, the apparatus 1300 may be implemented in, or as at least a part of, the terminal device 120 and the network devices 110-1 and 110-2.

[0324] As shown, the apparatus 1300 includes a processor 1310, a memory 1320 coupled to the processor 1310, a suitable transmitter (TX) and receiver (RX) 1340 coupled to the processor 1310, and a communication interface coupled to the TX / RX 1340. The memory 1320 stores at least a portion of a program 1330. The TX / RX 1340 is used for bidirectional communication. The TX / RX 1340 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have multiple antennas. The communication interface may represent any interface required 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.

[0325] The program 1330 is assumed to include program instructions that, when executed by the associated processor 1310, enable the device 1300 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2-12. The embodiments herein 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 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1310 and the memory 1320 may form a processing means 1350 suitable for implementing various embodiments of the present disclosure.

[0326] Memory 1320 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, 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. While only one memory 1320 is shown in device 1300, several physically distinct memory modules may be present within device 1300. Processor 1310 may be of any type suitable for a local technology network and may include, by way of non-limiting example, 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 1300 may have multiple processors, for example, application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0327] Overall, various 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 executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0328] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, that execute within a device on a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 2-12. Generally, 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 between program modules as desired. The machine-executable instructions of the program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0329] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0330] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated 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 aforementioned media. More specific examples of a machine-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0331] It should be noted that, although operations have been described in a particular order, it should not be understood that performing such operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0332] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as 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 terminal device, and means for receiving, from a network device, first downlink control information (DCI) for scheduling at least one physical downlink shared channel (PDSCH), the first DCI including a first field and a second field, the first field including at least one transmission configuration indication (TCI). the second field indicates a TCI state of two previously indicated TCI states, the second field indicates that a first TCI state of the two previously indicated TCI states, a second TCI state of the two previously indicated TCI states, or both of the two previously indicated TCI states apply to the at least one PDSCH, and the at least one TCI state applies from a first slot that is Y symbols after a last symbol of a positive hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the first DCI or corresponding to the at least one PDSCH, where Y is an integer; means for receiving the at least one PDSCH from the network device based on the first DCI; Equipped with Terminal device.

2. The two previously indicated TCI states are indicated by a second DCI, and the at least one TCI state is different from the two previously indicated TCI states. The terminal device according to claim 1 .

3. The at least one TCI state is associated with a first TCI codepoint; means for receiving a medium access control element (MACCE) message from the network device, the MAC CE message being mapped only to a second TCI codepoint; means for applying a TCI state associated with the second TCI codepoint; Further provided with The terminal device according to claim 1 .

4. means for receiving a control resource set (CORESET) configuration from the network device, the configuration indicating which of the two previously indicated TCI states applies to the CORESET; Further provided with The terminal device according to claim 1 .

5. A network device, means for transmitting, to a terminal device, first downlink control information (DCI) for scheduling at least one physical downlink shared channel (PDSCH), the first DCI including a first field and a second field, the first field including at least one transmission configuration indication (TCI); the second field indicates a TCI state of two previously indicated TCI states, the second field indicates that a first TCI state of the two previously indicated TCI states, a second TCI state of the two previously indicated TCI states, or both of the two previously indicated TCI states apply to the at least one PDSCH, and the at least one TCI state applies from a first slot that is Y symbols after a last symbol of a positive hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the first DCI or corresponding to the at least one PDSCH, where Y is an integer; means for transmitting the at least one PDSCH to the terminal device based on the first DCI; Equipped with Network equipment.

6. The two previously indicated TCI states are indicated by a second DCI, and the at least one TCI state is different from the two previously indicated TCI states. The network device according to claim 5 .

7. The method of claim 6, wherein the at least one TCI state is associated with a first TCI codepoint; means for transmitting a medium access control element (MAC) message to the terminal device, wherein the MAC CE message maps only to a second TCI codepoint, and a TCI state associated with the second TCI codepoint is applied to the terminal device; Further provided with The network device according to claim 5 .

8. means for transmitting a configuration of a control resource set (CORESET) to the terminal device, the configuration indicating which of the two previously indicated TCI states applies to the CORESET; Further provided with The network device according to claim 5 .

9. 1. A method of communication performed by a terminal device, comprising: and receiving, from a network device, first downlink control information (DCI) for scheduling at least one physical downlink shared channel (PDSCH), the first DCI including a first field and a second field, the first field including at least one transmission configuration indication (TCI). the second field indicates a TCI state of a previously indicated two TCI states, a second TCI state of the previously indicated two TCI states, or both of the previously indicated two TCI states are applied to the at least one PDSCH, and the at least one TCI state is applied from a first slot that is Y symbols after a last symbol of a positive hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the first DCI or corresponding to the at least one PDSCH, where Y is an integer; receiving the at least one PDSCH from the network device based on the first DCI; Including, method.

10. The two previously indicated TCI states are indicated by a second DCI, and the at least one TCI state is different from the two previously indicated TCI states.

10. The method of claim 9.

11. The at least one TCI state is associated with a first TCI codepoint; receiving a medium access control element (MACCE) message from the network device, the MAC CE message mapping only to a second TCI codepoint; applying a TCI state associated with the second TCI codepoint; further comprising:

10. The method of claim 9.

12. receiving a control resource set (CORESET) configuration from the network device, the configuration indicating which of the two previously indicated TCI states apply to the CORESET; further comprising:

10. The method of claim 9.

13. 1. A method of communication performed by a network device, comprising: transmitting, to a terminal device, first downlink control information (DCI) for scheduling at least one physical downlink shared channel (PDSCH), the first DCI including a first field and a second field, the first field including at least one transmission configuration indication (TCI); the second field indicates a TCI state of a previously indicated two TCI states, a second TCI state of the previously indicated two TCI states, or both of the previously indicated two TCI states are applied to the at least one PDSCH, and the at least one TCI state is applied from a first slot that is Y symbols after a last symbol of a positive hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the first DCI or corresponding to the at least one PDSCH, where Y is an integer; transmitting the at least one PDSCH to the terminal device based on the first DCI; Including, method.

14. The two previously indicated TCI states are indicated by a second DCI, and the at least one TCI state is different from the two previously indicated TCI states. The method of claim 13.

15. The method according to claim 1, wherein the at least one TCI state is associated with a first TCI codepoint; sending a medium access control element (MACCE) message to the terminal device, the MAC CE message mapping only to a second TCI codepoint, and a TCI state associated with the second TCI codepoint being applied to the terminal device; further comprising: The method of claim 13.

16. sending a configuration of a control resource set (CORESET) to the terminal device, the configuration indicating which of the two previously indicated TCI states applies to the CORESET; further comprising: The method of claim 13.

Images