Terminal device, network device, and method

Abstract

The embodiments of the present disclosure relate to a communication method, an apparatus, and a computer-readable medium. A terminal device receives a first physical downlink control channel (PDCCH) indicating a first transmission configuration indication (TCI) state and a second PDCCH indicating a second TCI state from a network device. If the reception of the second PDCCH is after the reception of the first PDCCH, the terminal device communicates with the network device using the second TCI. In this way, ambiguity between the two TCI states is avoided. Also, unnecessary beam switching is avoided.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to communication methods, apparatuses, and computer-readable media.

Background Art

[0002] In the RAN#86 meeting of the third generation partnership project (3GPP), enhancements for multi-beam operation have been agreed upon that mainly target frequency range 2 (FR2) and are also applicable to frequency range 1 (FR1). In order to facilitate more efficient (lower latency and overhead) beam management for the downlink (DL) and uplink (UL), it has been agreed to identify and specify features. For example, it has been proposed to support a common beam for the transmission and reception of data and control information for the DL and UL. It has also been proposed to support an integrated Transmission Configuration Indication (TCI) framework for DL and UL beam indication.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Overall, embodiments of the present disclosure provide a method, apparatus, and computer-readable medium for redundant version determination.

Means for Solving the Problems

[0004] In a first aspect, a communication method is provided. The method includes, at a terminal device, receiving from a network device a first physical downlink control channel (PDCCH) indicating a first transmission configuration indicator (TCI) state, receiving from the network device a second PDCCH indicating a second TCI state, and in accordance with a determination that the reception of the second PDCCH is after the reception of the first PDCCH, communicating with the network device using the second TCI state after a certain period of time.

[0005] In a second aspect, a communication method is provided. The method includes, at a terminal device, receiving from a network device a first number of activated transmission configuration indicator (TCI) code points, and receiving from the network device a setting of a second number of code points within a downlink control information (DCI) field, where the second number is less than the first number, and where one predetermined value of the DCI field indicates the same TCI state that has already been applied for communication with the network device.

[0006] In a third aspect, a communication method is provided. The method includes, at a network device, transmitting to a terminal device a first physical downlink control channel (PDCCH) indicating a first transmission configuration indicator (TCI) state, transmitting to the terminal device a second PDCCH indicating a second TCI state, and in accordance with a determination that the reception of the second PDCCH is after the reception of the first PDCCH, communicating with the terminal device using the second TCI state after a certain period of time.

[0007] In a fourth aspect, a communication method is provided. The method includes, in a network device, transmitting a first number of activated transmission configuration indicator (TCI) code points to a terminal device, and transmitting a setting of a second number of code points in a downlink control information (DCI) field to the terminal device. The second number is less than the first number, and one predetermined value of the DCI field indicates the same TCI state that has already been applied for communication with the network device.

[0008] In a fifth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method described in the first aspect of the present disclosure.

[0009] In a sixth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method described in the second aspect of the present disclosure.

[0010] In a seventh aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method described in the third aspect of the present disclosure.

[0011] In an eighth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method described in the fourth aspect of the present disclosure.

[0012] In a ninth aspect, a computer-readable medium storing instructions is provided. When the instructions are executed on at least one processor, the at least one processor is caused to execute the method according to the first, second, third, or fourth aspect of the present disclosure.

[0013] Other features of the present disclosure will be readily understood from the following description.

Brief Description of the Drawings

[0014] Some embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings, so as to make the above and other objects, features and advantages of the present disclosure more apparent.

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 3C

Figure 3D

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Embodiments for Carrying Out the Invention

[0015] Here, the principles of the present disclosure will be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing the present disclosure, without suggesting any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the methods described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art of the present disclosure.

[0017] As used herein, the term "terminal device" means any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Everything (IoE) devices, machine type communication (MTC) devices, in-vehicle devices for V2X communication, etc. Here, "X" in V2X represents a pedestrian, a vehicle, or infrastructure / network, or an image acquisition device such as a digital camera, a game device, a music storage and playback device, or an Internet appliance enabling wireless or wired Internet access and browsing. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Also, the term "network device" means a device that can provide or host a cell or coverage with which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmission and reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), femto node, pico node, and other low-power nodes.

[0018] In one embodiment, the terminal device can be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node, and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information regarding different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information regarding the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the re - settings of the terminal device set by the second network device may be transmitted from the second network device directly or via the first network device to the terminal device.

[0019] As used herein, the singular forms "a", "an", and "the" include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprising" and its variants should be understood as open - ended terms meaning "including, but not limited to". The term "based on" should be understood as "at least partially based on". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Terms such as "first", "second", etc. may refer to different or the same objects. There may be other explicit and implicit definitions below.

[0020] In some instances, a value, procedure, or device is referred to as "best", "lowest", "highest", "minimum", "maximum", etc. Such descriptions are intended to indicate that a selection can be made from among a number of available functional alternatives, and it will be understood that such a selection need not be better, smaller, higher, or otherwise preferable to other selections.

[0021] As used herein, the term "circuit" can mean a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be an analog and / or digital hardware circuit in combination with software / firmware. As yet another example, a circuit may be any portion of a hardware processor having software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device such as a terminal device or 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 a portion thereof that requires software / firmware for operation, although the software may not be present if not required for operation. As used herein, the term "circuit" also includes a hardware circuit or only one or more processors, or a portion of a hardware circuit or one or more processors, and the implementation of its (or their) accompanying software and / or firmware.

[0022] As used herein, the term "TRP" means an antenna array (having one or more antenna elements) available to a network device located at a specific geographical location. Although some embodiments of the present disclosure have been described with reference to multi-TRP as an example, these embodiments are for illustrative purposes only, to help those skilled in the art understand and implement the present disclosure, and do not imply any limitation regarding the scope of the present disclosure. It should be understood that the content of the present disclosure described herein can be implemented in various ways different from the methods described below.

[0023] Generally speaking, in the case of uplink (UL) transmission, one TRP usually corresponds to one SRS resource set. As used herein, the term "single TRP for UL" means that a single SRS resource set is used to perform the associated transmission (e.g., PUSCH transmission), and the term "multi-TRP for UL" means that multiple SRS resource sets are used to perform the associated transmission (e.g., PUSCH transmission).

[0024] As described above, there is an extension for multi-beam operation mainly targeting FR2 but also applicable to FR1. a. Identify and define features that facilitate more efficient (lower latency and overhead) DL / UL beam management to support higher in-cell and inter-cell mobility centered on L1 / L2 and / or more configured TCI states. i. Common beams for DL and UL, especially for data and control transmission / reception in intra-band CA. ii. Integrated TCI framework for DL and UL beam indication. iii. Extension of the signaling mechanism for the above features to improve latency and efficiency by using more dynamic control signaling (as opposed to RRC).

[0025] It is proposed to indicate combined or separate DL / UL beam indications from an active TCI state by supporting L1-based beam indication using at least UE-specific (unicast) DCI. The existing DCI formats 1_1 and 1_2 are reused for beam indication and support a mechanism for the UE to confirm successful decoding of the beam indication by sending an acknowledgement. The ACK / NAK of the PDSCH scheduled by the DCI carrying the beam indication may also be used as an ACK for the DCI.

[0026] It is also proposed to support the activation of one or more TCI states via a media access control (MAC) control element (CE) similar to Release 15 / 16. For at least a single activated TCI state, the activated TCI state is applied.

[0027] For beam indication with Rel-17 integrated TCI, DCI formats 1_1 / 1_2 without DL allocation are supported, and the acknowledgement / negative acknowledgement (ACK / NACK) mechanism is utilized in the same way as the mechanism for semi-persistent scheduling (SPS) PDSCH release with both type 1 and type 2 hybrid automatic repeat request - acknowledgement (HARQ-ACK) codebooks. When the UE successfully receives the beam indication DCI, it reports an ACK.

[0028] For the type-1 HARQ-ACK codebook, the location of the ACK information in the HARQ-ACK codebook is determined based on the virtual PDSCH indicated by the TDRA field in the beam indication DCI, based on the time domain allocation list configured for the PDSCH. For the type-2 HARQ-ACK codebook, the location of the ACK information in the HARQ-ACK codebook is determined according to the same rules for SPS release. The ACK is reported within the PUCCH after k slots at the end of PDCCH reception, where k is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, or when the PDSCH-to-HARQ_feedback timing indicator does not exist in the DCI, dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCI-Format1-2-r16 is provided.

[0029] When used for beam indication, the configured scheduling radio network temporary identifier (CS-RNTI) is used to scramble the CRC for the DCI. The values of the following DCI fields are set as follows. RV = all "1", MCS = all "1", NDI = 0, and for FDRA type 0, all "0", for FDRA type 1, all "1", or for dynamicSwitch, all "0" (the same as Table 10.2-4 in TS38.213).

[0030] The TCI field may be used to signal 1) the combined DL / UL TCI state, 2) the DL-only TCI state (for separate DL / UL TCIs), 3) the UL-only TCI state (for separate DL / UL TCIs).

[0031] Additionally, in Rel-16, the following DCI fields are used, namely, the identifier for the DCI format, the carrier indicator, the bandwidth part indicator, the time domain resource assignment (TDRA), the downlink assignment index (if configured), the transmit power control (TPC) command for the scheduled PUCCH, the PUCCH resource indicator, and the PDSCH-to-HARQ_feedback timing indicator (if present). The remaining unused DCI fields and code points are reserved for Release 17.

[0032] It is also proposed to support the UE reporting whether it supports TCI updates by DCI format 1_1 / 1_2. For UEs that support TCI updates by DCI format 1_1 / 1_2, they must support TCI updates by using DCI 1_1 / 1_2 with a DL assignment, and the support for the above features of TCI updates by DCI format 1_1 / 1_2 without a DL assignment is optional for the UE.

[0033] In the beam indication based on Rel-17 DCI, regarding the application time of the beam indication, the first slot is after at least X ms or Y symbols of the last symbol of the acknowledgment response of the combined or separate DL / UL beam indication.

[0034] According to TS 38.212 section 7.3.1.2.2 format 1_1, when the upper layer parameter tci-PresentInDCI is not enabled, the transmission setting indication is 0 bits, otherwise it is 3 bits as defined in clause 5.1.5 of [6, TS38.214]. According to TS 38.212 section 7.3.1.2.3 format 1_2, when the upper layer parameter tci-PresentDCI-1-2 is not set, the transmission setting indication is 0 bits, otherwise it is 1 or 2 or 3 bits determined by the upper layer parameter tci-PresentDCI-1-2 as defined in clause 5.1.5 of [6, TS38.214].

[0035] The UE receives an activation command as described in 6.1.3.14 of [10, TS 38.321] to map up to 8 TCI states to the code points of the DCI field "Transmission Configuration Indication" within one CC / DL BWP or within a set of CC / DL BWPs. When a set of TCI state IDs is activated for the set of CC / DL BWPs determined by the indicated CC in the available list of CCs in the activation command, the same set of TCI state IDs is applied for all DL BWPs within the indicated CC.

[0036] If the UE supports 2 TCI states within the code point of the DCI field "Transmission Configuration Indication", the UE may receive an activation command as described in clause 6.1.3.24 of "10,TS 38.321", and the activation command is used to map up to 8 combinations of 1 or 2 TCI states to the code point of the DCI field "Transmission Configuration Indication". The UE is not expected to receive more than 8 TCI states in the activation command.

[0037] In DCI format 1_2, if the DCI field "Transmission Configuration Indication" exists and the number of code points S in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is less than the number of TCI code points activated by the activation command, only the first S activated code points are applicable to DCI format 1_2 as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321]. For example, when the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 1 bit, S = 2. For another example, when the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 2 bits, S = 4. For another example, when the number of bits for the DCI field "Transmission Configuration Indication" of DCI format 1_2 or the number of bits for the upper layer parameter tci-PresentDCI-1-2 is 3 bits, S = 8.

[0038] Furthermore, DCI formats 1_1 / 1_2 with DL allocation and DCI formats 1_1 / 1_2 without DL allocation may be used for dynamic beam indication. When the beam indication is indicated by a DCI format with DL scheduling, the ACK / NACK of the PDSCH can be used to indicate the ACK of the beam indication, and after the timing, the indicated beam can be applied.

[0039] However, when a new beam is applied from the first slot that is at least X ms or Y symbols after the last symbol of the confirmation response, there may be cases where the same slot is identified for some HARQ-ACK feedbacks (especially in the case of sub-slot HARQ-ACK feedback), there are several new beams applicable from the same first slot, and it is necessary to clarify which one should be applied. Further, the first PDCCH with data scheduling and the second PDCCH without data scheduling are such that the first PDCCH is before the second PDCCH, and the first HARQ-ACK feedback for the first PDCCH may be after the second HARQ-ACK feedback for the second PDCCH. The first PDCCH with data scheduling and the second PDCCH without data scheduling are such that the first PDCCH is before the second PDCCH, and the first HARQ-ACK feedback for the data scheduling based on the first PDCCH may be after the second HARQ-ACK feedback for the second PDCCH. When the TCI field exists, the sizes of the TCI fields in DCI formats 1_1 and 1_2 may be different, and there may be cases where some TCI code points cannot be indicated by DCI format 1_2.

[0040] To solve at least some of the above problems, a solution regarding beam indication has been proposed. The terminal device receives from the network device a first PDCCH indicating a first TCI state and a second PDCCH indicating a second TCI state. When the reception of the second PDCCH is after the reception of the first PDCCH, the terminal device communicates with the network device using the second TCI. In this way, the uncertainty between the two TCI states is avoided. Also, unnecessary beam switching is avoided.

[0041] FIG. 1 is a schematic diagram of a communication system capable of implementing an embodiment of the present disclosure. A communication system 100, which is part of a communication network, includes terminal devices 110-1, 110-2, …, 110-N, which can be collectively referred to as “terminal devices 110”. The number N can be any suitable integer. For the purpose of illustration only, the embodiments of the present disclosure will be described with reference to terminal device 110-1.

[0042] The communication system 100 further includes a network device 120. In the communication system 100, the network device 120 and the terminal devices 110 can communicate data and control information with each other. The number of devices shown in FIG. 1 is shown for illustrative purposes only and does not imply any limitation.

[0043] Communication in the communication system 100 can be realized according to any suitable communication protocol, including but not limited to cellular communication protocols such as the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol known currently or developed in the future. Further, the communication may utilize any suitable wireless communication technology, including but not limited to code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technology known currently or developed in the future.

[0044] Embodiments of the present disclosure can be applied to any suitable scenario. For example, embodiments of the present disclosure can be implemented on an NR device with reduced capabilities. Alternatively, embodiments of the present disclosure can be implemented within one of NR multi-input multi-output (MIMO), enhanced NR side link, NR systems operating at frequencies higher than 52.6 GHz, extended NR operations up to 71 GHz, narrowband mono Internet of Things (NB-IoT) / enhanced machine type communication (eMTC) on non-terrestrial networks (NTN), NTN, UE power saving enhancement, NR coverage enhancement, NB-IoT and LTE-MTC, integrated access and backhaul (IAB), NR multicast and broadcast services, or enhanced multi-radio dual connectivity.

[0045] It should be understood that the number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and does not imply any limitation to the present disclosure. The communication network 100 may include any suitable number of network devices, terminal devices, and / or TRPs suitable for implementing embodiments of the present disclosure.

[0046] In some embodiments, the TRP may be explicitly associated with different upper layer configured identities. For example, the upper layer configured identities may be associated with a control resource set (CORESET), a group of CORESETs, a reference signal (RS), a set of RSs, a transmission configuration indication (TCI) state, or a group of TCI states, which are used to distinguish transmissions between different TRPs and the terminal device 110-1. When the terminal device 110-1 receives two DCIs from two CORESETs associated with different upper layer configured identities, the two DCIs are indicated from different TRPs. Further, the TRP may be implicitly identified by dedicated configuration to a physical channel or signal. For example, a dedicated CORESET, an RS, and a TCI state associated with the TRP are used to identify transmissions from different TRPs to the terminal device 110. For example, when the terminal device 110-1 receives a DCI from a dedicated CORESET, the DCI is indicated from the TRP associated with the dedicated CORESET. In some embodiments, the RS may be at least one of CSI-RS, SRS, positioning RS, uplink DMRS, downlink DMRS, uplink PTRS, and downlink PTRS.

[0047] In iterative transmission or reception via two TRPs, the network device 120 may select an iterative mode from among a plurality of available iterative modes. The iterative mode may define a transmission method for the network device 120 to use the two TRPs in cooperation, such as a multiplexing mode between the two TRPs and respective resource allocations for the two TRPs.

[0048] For example, a scheme for URLLC based on multi-TRP / multi-panel, which is scheduled by at least a single downlink control information (DCI), may be specified as follows.

[0049] Scheme 1 (SDM): There are n (n ≦ N s ) TCI states in a single slot, and there are overlapping time and frequency resource allocations.

[0050] Method 1a: Each transmission occasion is the same layer or set of layers of a TB, and each layer or set of layers is associated with one TCI and one set of DMRS ports. A single codeword with one RV is used across all spatial layers or sets of layers. From the perspective of the UE, different coded bits are mapped to different layers or sets of layers according to the same mapping rules as in Rel-15.

[0051] Method 1b: Each transmission occasion is the same layer or set of layers of a TB, and each layer or set of layers is associated with one TCI and one set of DMRS ports. A single codeword with one RV is used for each spatial layer or set of layers. The RVs corresponding to each spatial layer or set of layers may be the same or different. When the total number of layers ≤ 4, the mapping of the codeword to the layers is a future research topic.

[0052] Method 1c: One transmission occasion is one layer of the same TB having one DMRS port associated with a plurality of TCI state indices, or one layer of the same TB having a plurality of DMRS ports associated one-to-one with a plurality of TCI state indices.

[0053] In addition, it has been shown that it is also possible to discuss applying different MCS / modulation orders to different layers or sets of layers.

[0054] Method 2 (FDM): There are n (n ≤ N f ) TCI states in a single slot, and there are non-overlapping frequency resource allocations. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single / plurality of DMRS ports are associated with all non-overlapping frequency resource allocations.

[0055] Mode 2a: A single codeword with one RV is used across all resource allocations. From the perspective of the UE, a common RB mapping (the mapping from codeword to layer in Rel-15) is applied across all resource allocations. In some embodiments, the terminal device may be set or configured to have FDMschemeA by upper layer parameters. For example, the upper layer parameters may be RRC parameters. For example, the upper layer parameters may be URLLCSchemeEnabler.

[0056] Mode 2b: A single codeword with one RV is used for each non-overlapping frequency resource allocation. The RVs corresponding to each non-overlapping frequency resource allocation may be the same or different. In some embodiments, the terminal device may be set or configured to have FDMschemeB by upper layer parameters. For example, the upper layer parameters may be RRC parameters. For example, the upper layer parameters may be URLLCSchemeEnabler.

[0057] Additionally, it has been shown that it is also arguable to apply different MCS / modulation orders for different non-overlapping frequency resource allocations. It has also been shown that the details regarding the allocation granularity and time domain allocation of the frequency resource allocation mechanism for FDM 2a / 2b are arguable.

[0058] Mode 3 (TDM or intra-slot duplication): n (n ≤ N) within a single slot t1) There are TCI states, and there are non-overlapping time resource allocations. Each transmission occasion of the TB has one TCI and one RV, and the time granularity is a mini-slot. All transmission occasions within a slot use a common MCS with the same single or multiple DMRS ports. The RV / TCI states may be the same or different among transmission occasions. Channel estimate interpolation across mini-slots with the same TCI index is a future research topic. In some embodiments, the terminal device may be set or configured to have TDMschemeA by upper layer parameters. For example, the upper layer parameters may be RRC parameters. For example, the upper layer parameter is URLLCSchemeEnabler.

[0059] Method 4 (TDM or inter-slot duplication): n (n ≤ N t2 ) TCI states and K (n ≤ K) different slots. Each transmission occasion of the TB has one TCI and one RV. All transmission occasions across the K slots use a common MCS with the same single or multiple DMRS ports. The RV / TCI states may be the same or different among transmission occasions. Channel estimate interpolation across slots with the same TCI index is a future research topic.

[0060] Additionally, before transmitting data to the terminal device 110, the network device 120 may transmit control information associated with the data transmission. For example, the control information may schedule a set of resources for data transmission and include various transmission parameters related to data transmission defined in the 3GPP specifications, such as one or more TCI states, frequency domain resource assignment (FDRA), time domain resource assignment (TDRA) that can include a slot offset and a start / length indicator value, a demodulation reference signal (DMRS) group, and a redundancy version (RV). It should be understood that the transmission parameters indicated in the control information 135 are not limited to those listed above. Embodiments of the present disclosure may be similarly applicable to control information including any transmission parameters.

[0061] Hereinafter, the terms "transmission occasion", "reception occasion", "iteration", "transmission", "reception", "PDSCH transmission occasion", "PDSCH iteration", "PUSCH transmission occasion", "PUSCH iteration", "PUCCH occasion", "PUCCH iteration", "iterative transmission", "iterative reception", "PDSCH transmission", "PDSCH reception", "PUSCH transmission", "PUSCH reception", "PUCCH transmission", "PUCCH reception", "RS transmission", "RS reception", "communication", "transmission", and "reception" may be used interchangeably. The terms "TCI state", "set of QCL parameters", "QCL parameter", "QCL assumption", and "QCL configuration" may be used interchangeably. The terms "TCI field", "TCI state field", and "transmission configuration indication" may be used interchangeably. The terms "transmission occasion", "transmission", "iteration", "reception", "reception occasion", "monitoring occasion", "PDCCH monitoring occasion", "PDCCH transmission occasion", "PDCCH transmission", "PDCCH candidate", "PDCCH reception occasion", "PDCCH reception", "search space", "CORESET", "multi-chance", and "PDCCH iteration" may be used interchangeably. Hereinafter, the terms "PDCCH iteration", "iterative PDCCH", "iterative PDCCH signal", "PDCCH candidates configured for the same scheduling", "PDCCH", "PDCCH candidate", and "linked PDCCH candidates" may be used interchangeably. The terms "DCI" and "DCI format" may be used interchangeably. In some embodiments, the embodiments of the present disclosure may be applied to PDSCH and PUSCH scheduling. Hereinafter, PDSCH scheduling will be described as an example. For example, the embodiments of the present disclosure may be applied to PUSCH by replacing "transmission" with "reception" and / or "reception" with "transmission". The terms "PDSCH" and "PUSCH" may be used interchangeably. The terms "transmission" and "reception" may be used interchangeably.

[0062] As specified in the 3GPP specification (TS 38.214), the UE is configured to have a list of up to M TCI state settings within the higher layer parameter PDSCH-Config, and is able to decode the PDSCH from the detected PDCCH having DCI for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI state includes parameters for setting the quasi-collocation relationship between one or two downlink reference signals and the DMRS ports of the PDSCH, the DMRS ports of the PDCCH, or the channel state information reference signal (CSI-RS) ports of the CSI-RS resources. The quasi-collocation relationship is set by the higher layer parameter qcl-Type1 of the first downlink (DL) RS and (if configured) qcl-Type2 of the second DL RS. In the case of two DL RSs, the QCL types must not be the same whether referring to the same DL RS or different DL RSs. The quasi-collocation type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can be one of the following values. - "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread} - "QCL-TypeB": {Doppler shift, Doppler spread} - "QCL-TypeC": {Doppler shift, average delay} - "QCL-TypeD": {Spatial reception parameters}

[0063] The UE receives an activation command described in the clause "TCI state activation / deactivation for UE-specific PDSCH MAC CE" (e.g., clause 6.1.3.14) or the clause "Extended TCI state activation / deactivation for UE-specific PDSCH MAC CE" (e.g., clause 6.1.3) of "TS 38.321" for mapping up to eight TCI states respectively to the code points of the DCI field "Transmission Configuration Indication" within one CC / DL BWP or within a set of CC / DL BWPs. When a set of TCI state IDs is activated for a set of CC / DL BWPs determined by the indicated CC in the activation command, the same set of TCI state IDs is applied to all DL BWPs within the indicated CC.

[0064] If the UE supports two TCI states within the code point of the DCI field "Transmission Configuration Indication", the UE may receive an activation command as described in the clause "TCI state activation / deactivation for UE-specific PDSCH MAC CE" or the clause "Activation / deactivation of extended TCI state for UE-specific PDSCH MAC CE" (e.g., sub-clauses of clause 6.1.3.14 or 6.1.3) of "TS 38.321", and the activation command is used to map up to eight combinations of one or two TCI states to the code point of the DCI field "Transmission Configuration Indication". The UE is not expected to receive more than eight TCI states in the activation command.

[0065] The DCI format 1_2 has a DCI field "Transmission Configuration Indication". When the number of code points S in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is less than the number of TCI code points activated by the activation command, only the first S activated code points are applicable for DCI format 1_2 as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321].

[0066] When the UE transmits a PUCCH with HARQ-ACK information within slot n corresponding to the PDSCH carrying the activation command, the indicated mapping between the TCI state and the code points of the DCI field "Transmission Configuration Indication" shall apply from the first slot after the slot

Number

[0067] In some embodiments, if the UE is configured to have the upper layer parameter tci-PresentInDCI set to "enabled", or if tci-PresentInDCI-ForFormat1_2 is configured for the CORESET that schedules the PDSCH, the UE assumes that a TCI field is present in the DCI (e.g., DCI format 1_1 or DCI format 1_2) of the PDCCH transmitted in the CORESET. If tci-PresentInDCI or tci-PresentInDCI-ForFormat1_2 is not configured for the CORESET that schedules the PDSCH, or if the PDSCH is scheduled by a DCI (e.g., DCI format 1_0), the UE assumes that no TCI field is present in the DCI (e.g., DCI format 1_1 or DCI format 1_2 or DCI format 1_0) of the PDCCH transmitted in the CORESET. If the PDSCH is scheduled by a DCI format without a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is greater than or equal to the threshold timeDurationForQCL (if applicable) based on the reported UE capabilities [13, TS 38.306] for determining PDSCH antenna port quasi-collocation, the UE assumes that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0068] If tci-PresentInDCI is set to "enabled", or tci-PresentInDCI-ForFormat1_2 is set for the CORESET that schedules the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to timeDurationForQCL (if applicable), then after the UE receives the initial upper layer configuration of the TCI state and before receiving the activation command, the UE may assume that the DMRS ports of the PDSCH of the serving cell are quasi-collocated with the SS / PBCH block determined in the first access procedure, with respect to "QCL-TypeA" and, if applicable, also with respect to "QCL-TypeD". The value of timeDurationForQCL is based on the reported UE capabilities.

[0069] If the UE is configured to have the upper layer parameter tci-PresentInDCI set to "enabled" for the CORESET that schedules the PDSCH, the UE shall assume that a TCI field is present in the DCI of the PDCCH transmitted in the CORESET (e.g., DCI format 1_1). If the UE is configured to have the upper layer parameter tci-PresentInDCI-ForFormat1_2 for the CORESET that schedules the PDSCH, the UE shall assume that a TCI field with the DCI field size indicated by tci-PresentInDCI-ForFormat1_2 is present in the DCI of the PDCCH transmitted in the CORESET (e.g., DCI format 1_2). If the PDSCH is scheduled by a DCI format without a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationForQCL (if applicable) based on the reported UE capabilities [TS 38.306] for determining the PDSCH antenna port quasi-collocation, the UE shall assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0070] If the PDSCH is scheduled by a DCI format with a TCI field, and the TCI field in the DCI within the scheduling component carrier refers to an activated TCI state within the scheduling component carrier or DL BWP, the UE determines the PDSCH antenna port quasi-collocation using the TCI state according to the value of the "Transmission Configuration Indication" field in the detected PDCCH having the DCI. If the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to a threshold timeDurationForQCL based on the UE capabilities reported in [TS 38.306], the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-collocated with the RSs within the TCI state with respect to the QCL type parameters provided by the indicated TCI state. If the UE is configured to have a single-slot PDSCH, the indicated TCI state should be based on the activated TCI state within the slot having the scheduled PDSCH. If the UE is configured to have a multi-slot PDSCH, the indicated TCI state should be based on the activated TCI state within the first slot having the scheduled PDSCH, and the UE should expect the activated TCI state to be the same across the slots having the scheduled PDSCH.The UE is configured to have a CORESET associated with a search space set for cross-carrier scheduling. When the PDCCH carrying the scheduling DCI and the PDSCH scheduled by the DCI are transmitted on the same carrier, the UE expects that tci-PresentInDCI is set to "enabled" or tci-PresentInDCI-ForFormat1_2 is set for the CORESET. If one or more of the TCI states set for the serving cell scheduled by the search space set include "QCL-TypeD", the UE expects that the time offset between the reception of the detected PDCCH within the search space set and the corresponding PDSCH is greater than or equal to the threshold timeDurationForQCL.

[0071] Regardless of the settings of tci-PresentInDCI and tci-PresentInDCI-ForFormat1_2 in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one of the configured TCI states for the serving cell of the scheduled PDSCH includes the qcl-Type set to "typeD",

[0072] - For the QCL parameter used for the PDCCH quasi - co - location indication of the CORESET associated with the monitored search space having the lowest controlResourceSetId within the last slot monitored by the UE among one or more CORESETs in the active BWP of the serving cell, the UE may assume that the DM - RS ports of the PDSCH of the serving cell are quasi - co - located with the RS. In this case, if the qcl - Type set to "typeD" of the PDSCH DM - RS is different from the qcl - Type of the PDCCH DM - RS that overlaps within at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET. This also applies to the case of in - band CA (when the PDSCH and the CORESET are in different component carriers).

[0073] - If the UE is configured to have enableDefaultTCIStatePerCoresetPoolIndex and is configured to have a higher - layer parameter PDCCH - Config that contains two different coresetPoolIndex values in different ControlResourceSets,

[0074] - For the QCL parameter used for the PDCCH quasi-collocation indication of the CORESET associated with the lowest controlResourceSetId among the monitored search spaces associated with the CORESET configured to have the same coresetPoolIndex value as the PDCCH scheduling the PDSCH, in the last slot monitored by the UE among one or more CORESETs associated with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH within the active BWP of the serving cell, it may be assumed that the DM-RS ports of the PDSCH associated with the coresetPoolIndex value of the serving cell are quasi-collocated with the RS. In this case, if the "QCL-TypeD" of the PDSCH DM-RS overlaps within at least one symbol and is different from that of the PDCCH DM-RS associated with the same coresetPoolIndex, the UE is expected to prioritize the reception of the PDCCH associated with that CORESET. This also applies to the case of intra-band CA (when the PDSCH and the CORESET are in different component carriers).

[0075] - If the UE is configured to have enableTwoDefaultTCI-States and at least one TCI code point indicates two TCI states, the UE may assume that the DM-RS ports or PDSCH transmission occasions of the serving cell's PDSCH are quasi-collocated with the RS with respect to the QCL parameters associated with the TCI state corresponding to the lowest code point among the TCI code points including two different TCI states. If the UE is configured by the upper layer parameter repetitionScheme set to "tdmSchemeA", or is configured to have the upper layer parameter repetitionNumber, in accordance with clause 5.1.2.1, based on the activated TCI state within the slot having the first PDSCH transmission occasion, the indicated TCI state is replaced with the TCI state corresponding to the lowest code point among the TCI code points including two different TCI states, thereby determining the mapping of the TCI state to the PDSCH transmission occasion. In this case, if the "QCL-TypeD" within both TCI states corresponding to the lowest code point among the TCI code points including two different TCI states is different from that of the PDCCH DM-RS that overlaps within at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to the case of in-band CA (when the PDSCH and the CORESET are in different component carriers).

[0076] - In any of the above cases, if none of the configured TCI states for the serving cell of the scheduled PDSCH is configured to have a qcl-Type set to "typeD", the UE should obtain other QCL assumptions from the indicated TCI state for the scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0077] If a PDCCH carrying scheduling DCI is received in one component carrier, the PDSCH scheduled by the DCI is on another component carrier, and the UE is configured to have enableDefaultBeam-ForCCS,

[0078] - timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μ PDCCH < μ PDSCH then an additional timing delay

Number

[0079] - In both cases, when the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and the DL DCI does not have a TCI field, the UE obtains its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable to the PDSCH in the active BWP of the scheduled cell.

[0080] For the periodic CSI-RS resources within the NZP-CSI-RS-ResourceSet configured to have the upper layer parameter trs-Info, the UE should expect the TCI-State to indicate one of the following quasi-collocation types.

[0081] - "typeC" with an SS / PBCH block, and, if applicable, "typeD" with the same SS / PBCH block, or - "typeC" with an SS / PBCH block, and "typeD" with CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have a higher layer parameter repetition, if applicable, or For an aperiodic CSI-RS resource within an NZP-CSI-RS-ResourceSet configured to have a higher layer parameter trs-Info, the UE should expect the TCI-State to indicate a qcl-Type set to "typeA" that has a periodic CSI-RS resource within the NZP-CSI-RS-ResourceSet configured to have the higher layer parameter trs-Info, and, if applicable, a qcl-Type where the qcl type having the same periodic CSI-RS resource is set to "typeD".

[0082] For a periodic CSI-RS resource within an NZP-CSI-RS-ResourceSet configured not to have a higher layer parameter trs-Info and not to have a higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-collocation types.

[0083] - "typeA" with CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have a higher layer parameter trs-Info, and, if applicable, "typeD" with the same CSI-RS resources, or - "typeA" with CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have a higher layer parameter trs-Info, and, if applicable, "typeD" with an SS / PBCH block, or - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter trs-Info, and, if applicable, "typeD" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter repetition, or - "typeB" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter trs-Info when "typeD" is not applicable.

[0084] For periodic CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-collocation types.

[0085] - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter trs-Info, and, if applicable, "typeD" having the same CSI-RS resources, or - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter trs-Info, and, if applicable, "typeD" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the higher layer parameter repetition, or - "typeC" having an SS / PBCH block, and, if applicable, "typeD" having the same SS / PBCH block.

[0086] For the DM-RS of PDCCH, the UE should expect the TCI-State to indicate one of the following quasi-collocation types.

[0087] - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter trs-Info, and "typeD" having the same CSI-RS resources if applicable, or - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter trs-Info, and "typeD" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter repetition if applicable, or - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured not to have the upper layer parameter trs-Info and not to have the upper layer parameter repetition, and "typeD" having the same CSI-RS resources if applicable.

[0088] For the DM-RS of PDSCH, the UE should expect the TCI-State to indicate one of the following quasi-collocation types.

[0089] - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter trs-Info, and "typeD" having the same CSI-RS resources if applicable, or - "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter trs-Info, and "typeD" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to have the upper layer parameter repetition if applicable, or "typeA" having CSI-RS resources within an NZP-CSI-RS-ResourceSet configured to not have the upper layer parameter trs-Info and not have the upper layer parameter repetition, and "typeD" having the same CSI-RS resources when applicable.

[0090] If a PDCCH carrying scheduling DCI is received in one component carrier and the PDSCH scheduled by the DCI is on another component carrier, timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. When μPDCCH < μPDSCH, an additional timing delay d is added to timeDurationForQCL, where when the subcarrier spacing for the PDCCH is 15 kHz, d is defined as 8 symbols, or when the subcarrier spacing for the PDCCH is 30 kHz, it is defined as 8 symbols, or when the subcarrier spacing for the PDCCH is 60 kHz, it is defined as 14 symbols. For example, whether the symbol is a PDCCH symbol or (as defined in Table 5.2.1.5.1a-1 of TS 38.214, for example) is based on the subcarrier spacing of the PDCCH. In both cases, if tci-PresentInDCI is set to "enabled" and the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and if tci-PresentInDCI is not set, the UE obtains its QCL assumption for the scheduled PDSCH from the activated TCI state having the lowest ID applicable to the PDSCH in the active BWP of the scheduled cell.

[0091] As specified in the 3GPP specification (TS 38.214), when the UE is configured to have the upper layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", or "TDMSchemeA", if two TCI states are indicated within the code point of the DCI field "Transmission Configuration Indication" and the DMRS ports within one CDM (Code Domain Multiplexing) group are indicated within the DCI field "Antenna Port(s)", and two TCI states are indicated in the DCI, and the UE is configured to "FDMSchemeA", the UE shall receive a single PDSCH transmission occasion of the TBs where each TCI state is associated with a non-overlapping frequency domain resource allocation as described in the clause "Physical resource block (PRB) bundling" in TS 38.214 (for example, clause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is configured to "FDMSchemeB", the UE shall receive two PDSCH transmission occasions of the same TB where each TCI state is associated with a PDSCH transmission occasion having a non-overlapping frequency domain resource allocation for other PDSCH transmission occasions as described in the clause "Physical resource block (PRB) bundling" in TS 38.214 (for example, clause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is configured to "TDMSchemeA", the UE shall receive two PDSCH transmission occasions of the same TB where each TCI state is associated with a PDSCH transmission occasion having a non-overlapping time domain resource allocation for other PDSCH transmission occasions as described in the clause "Resource allocation in the time domain" in TS 38.214 (for example, clause 5.1.2.1), and both of the two PDSCH transmission occasions shall be received within a predetermined slot.

[0092] If the UE is configured by the higher layer parameter PDSCH-config which indicates at least one entry in the pdsch-TimeDomainAllocationList containing RepNumR16 within PDSCH-TimeDomainResourceAllocation, the UE may expect that, together with the DCI field "Time domain resource assignment" indicating an entry containing RepNum16 within PDSCH-TimeDomainResourceAllocation, one or two TCI states are indicated within the code point of the DCI field "Transmission Configuration Indication" and one DM-RS port within one CDM group is indicated within the DCI field "Antenna Port(s)". If two TCI states are indicated in the "Transmission Configuration Indication" field in the DCI, the UE may expect to receive multiple slot-level PDSCH transmission occasions of the same TB where two TCI states are used over multiple PDSCH transmission occasions, as described in "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1). If one TCI state is indicated in the "Transmission Configuration Indication" field in the DCI, the UE may expect to receive multiple slot-level PDSCH transmission occasions of the same TB where one TCI state is used over multiple PDSCH transmission occasions, as described in "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1).

[0093] If the UE is not signaled a DCI in the DCI field "Time domain resource assignment" that indicates an entry in the pdsch-TimeDomainAllocationList that contains RepNumR16 within PDSCH-TimeDomainResourceAllocation, and two TCI states are signaled within the code point of the DCI field "Transmission Configuration Indication" and two DM-RS ports within two CDM groups are signaled within the DCI field "Antenna Port(s)", the UE may expect to receive a single PDSCH where the association between the DM-RS ports and the TCI states is as defined in the clause "DMRS reception procedure" in TS 38.214 (e.g., clause 5.1.6.2).

[0094] If the UE is not signaled a DCI in the DCI field "Time domain resource assignment" that indicates an entry in the pdsch-TimeDomainAllocationList that contains RepNumR16 within PDSCH-TimeDomainResourceAllocation, and one TCI state is signaled within the code point of the DCI field "Transmission Configuration Indication", the UE procedure for receiving the PDSCH upon detection of the PDCCH shall follow the clause "UE procedure for receiving the physical downlink shared channel" in TS 38.214 (e.g., clause 5.1).

[0095] Hereinafter, the terms "FDMSchemeA" and "Scheme 2a" may be used interchangeably. The terms "FDMSchemeB" and "Scheme 2b" may be used interchangeably. The terms "TDMSchemeA" and "Scheme 3" may be used interchangeably. The terms "RepNumR16" and "Scheme 4" may be used interchangeably.

[0096] As specified in the 3GPP specification (TS 38.214), when the UE is set by the upper layer parameter RepSchemeEnabler set to "TDMSchemeA" and the DM-RS ports within one CDM group indicated in the DCI field "antenna port", the number of PDSCH transmission occasions is derived from the number of TCI states indicated by the DCI field "Transmission Configuration Indication" of the scheduling DCI. When two TCI states are indicated by the DCI field "Transmission Configuration Indication", the UE is expected to receive two PDSCH transmission occasions, where the first TCI state is applied to the first PDSCH transmission occasion, and the resource allocation in the time domain for the first PDSCH transmission occasion follows the clause "Resource Allocation in the Time Domain" in TS 38.214 (for example, clause 5.1.2.1). The second TCI state is applied to the second PDSCH transmission occasion, and the second PDSCH transmission occasion should have the same number of symbols as the first PDSCH transmission occasion. If the UE is set by the upper layer having a value

Number

Number

Number

[0097] As defined in the 3GPP specification (TS 38.214), when the UE is configured by the higher layer parameter PDSCH-config that indicates at least one entry in the pdsch-TimeDomainAllocationList containing RepNumR16 within PDSCH-TimeDomainResourceAllocation, two TCI states are indicated by the DCI field "Transmission Configuration Indication" and the DCI field "Time domain resource assignment" that indicates an entry in the pdsch-TimeDomainAllocationList containing RepNumR16 within PDSCH-TimeDomainResourceAllocation and a DM-RS port within one CDM group in the DCI field "Antenna Port(s)". The same SLIV (Start and length indicator value) is applied to all PDSCH transmission occasions. The first TCI state is applied to the first PDSCH transmission occasion, and the resource allocation in the time domain for the first PDSCH transmission occasion follows the clause "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1). When the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is equal to 2, the second TCI state is applied to the second PDSCH transmission occasion. When the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is greater than 2, the UE may be further configured to activate CycMapping or SeqMapping within RepTCIMapping. When CycMapping is activated, the first and second TCI states are applied to the first and second PDSCH transmission occasions respectively, and the same TCI mapping pattern continues to be applied to the remaining PDSCH transmission occasions.When SeqMapping is enabled, the first TCI state is applied to the first and second PDSCH transmissions, the second TCI state is applied to the third and fourth PDSCH transmissions, and the same TCI mapping pattern continues to be applied to the remaining PDSCH transmission occasions. The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For all PDSCH transmission occasions associated with the first TCI state, the applied redundancy version is derived according to Table 5.1.2.1-2 [TS 38.214], where n is counted considering only the PDSCH transmission occasions associated with the first TCI state. The redundancy version for the PDSCH transmissions associated with the second TCI state is derived according to Table 5.1.2.1-3 (TS 38.214), where each redundancy version rv. sThe additional shift operation for [[ID=]] is set by the upper layer parameter RVSeqOffset, and n is counted considering only the PDSCH transmission occasion associated with the second TCI state. When one TCI state is indicated by the DCI field "Transmission Configuration Indication", an entry in the pdsch-TimeDomainAllocationList that includes RepNumR16 within PDSCH-TimeDomainResourceAllocation, and the DCI field "Time domain resource assignment" that indicates a DM-RS port within one CDM group within the DCI field "Antenna Port(s)", the same SLIV is applied for all PDSCH transmission occasions, and the first PDSCH transmission occasion follows the clause "Resource Allocation in the Time Domain" in TS 38.214 (e.g., clause 5.1.2.1), where the same TCI state is applied for all PDSCH transmission occasions. The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For all PDSCH transmission occasions, the applicable redundancy version is derived according to Table 5.1.2.1-2 [TS 38.214], where n is counted considering the PDSCH transmission occasion. Otherwise, the UE is expected to receive a single PDSCH transmission occasion, and the resource allocation in the time domain follows the clause "Resource Allocation in the Time Domain" in TS 38.214 (e.g., clause 5.1.2.1).

[0098] Table 5.1.2.1-2: Redundancy Version Applied When pdsch-AggregationFactor Exists

Table 1

[0099] Table 5.1.2.1-3: Redundancy Version Applied for the Second TCI State When RVSeqOffset Exists

Table 2

[0100] For a UE configured to have a higher layer parameter RepSchemeEnabler set to "FDMSchemeA" or "FDMSchemeB" as defined in 3GPP specification (TS 38.214), when two TCI states are indicated within the code point of the DCI field "Transmission Configuration Indication" and the DM-RS ports within one CDM (Code Domain Multiplexing) group are indicated within the DCI field "Antenna Port(s)",

Number

Number

Number

Number

[0101] For a UE configured by the higher layer parameter RepSchemeEnabler set to 「FDMSchemeB」, and when two TCI states are indicated within the code point of the DCI field 「Transmission Configuration Indication」 for the UE and a DM-RS port within one CDM group is indicated within the DCI field 「Antenna Port(s)」, each PDSCH transmission shall comply with the provisions of the clause 「Physical Downlink Shared Channel」 in [TS 38.211] (e.g., clause 7.3.1), and its mapping to resource elements shall be determined by the allocated PRBs for the corresponding TCI state of the PDSCH transmission occasion. When a single transmission layer is scheduled for the UE, the UE should expect only a maximum of two code blocks for each PDSCH transmission occasion. When two transmission layers are scheduled, the UE should expect only a single code block for each PDSCH transmission occasion. For two PDSCH transmission occasions, the applicable redundancy version is derived according to Table 5.1.2.1-2 in [TS 38.214], where n = 0, 1 is applied to the first and second TCI states respectively.

[0102] In some embodiments, the terminal device 110-1 may be configured to have a first PDCCH candidate and a second PDCCH candidate, where the first PDCCH candidate and the second PDCCH candidate are linked. For example, the linked first PDCCH candidate and second PDCCH candidate are applied to PDCCH repetitions. For another example, the linked first PDCCH candidate and second PDCCH candidate are applied to the same scheduling. For example, the scheduling may be at least one of downlink data scheduling, PDSCH scheduling, uplink data scheduling, PUSCH scheduling, downlink RS scheduling, uplink RS scheduling, and PUCCH scheduling.

[0103] In some embodiments, the terminal device 110-1 may be configured to have a plurality of control resource sets (i.e., CORESET).

[0104] In some embodiments, the CORESET is within the frequency domain

Number

Number

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

[0106] In some embodiments, a procedure for determining physical downlink control channel candidates for the terminal device 110 may be defined. That is, a CCE index is determined for each of a plurality of PDCCH candidates that may be used for PDCCH transmission between the network device 120 and the terminal device 110. When a CCE index is determined for a PDCCH candidate, the terminal device 110-1 can perform blind detection on these PDCCH candidates. When PDCCH transmission is detected or received in a PDCCH candidate, the terminal device 110-1 may decode it to obtain information such as DCI.

[0107] In some embodiments, the terminal device 110-1 may assume that the demodulation reference signal (DM-RS) antenna port associated with PDCCH reception within a CORESET is quasi-co-located (QCLed) with one or more reference signals (RSs) set by the transmission control indicator (TCI) state indicated for the CORESET (if applicable).

[0108] In some embodiments, if a media access control (MAC) control element (CE) activation command indicating the TCI state for the CORESET is not received after the most recent random access procedure that was not started by a PDCCH order triggering a non-competing random access procedure, the terminal device 110-1 may assume that the DM-RS antenna port associated with PDCCH reception within the CORESET is quasi-co-located (QCLed) with the synchronization signal / physical broadcast channel (SS / PBCH) block identified by the UE during the most recent random access procedure, and the one or more reference signals (RSs) are set by the TCI state indicated for the CORESET (if applicable).

[0109] In some embodiments, the network device 120 may transmit a configuration (e.g., 210) indicating N PDCCH candidates to the terminal device 110, where N is a positive integer. For example, 1 ≦ N ≦ 32. In another example, N = 2. For example, this configuration may be transmitted via any of radio resource control (RRC) signaling, medium access control (MAC) control element (CE), and downlink control information (DCI).

[0110] In some embodiments, the network device 120 may transmit one or more configurations for a first PDCCH candidate and a second PDCCH candidate to the terminal device 110. In some embodiments, the first PDCCH candidate may be included in a first search space or a first set of search spaces. In some embodiments, the first search space or the first set of search spaces may be associated with a first control resource set (CORESET). In some embodiments, the first CORESET may be associated with a first transmit configuration indicator (TCI) state T1 or a first set Q1 of quasi co-location (QCL) parameters, and may be configured to have them. In some embodiments, the second PDCCH candidate may be included in a second search space or a second set of search spaces. In some embodiments, the second search space or the second set of search spaces may be associated with a second CORESET. In some embodiments, the second CORESET may be associated with a second TCI state T2 or a second set Q2 of QCL parameters, and may be configured to have them. In some embodiments, T1 may be different from T2. In some embodiments, Q1 may be different from Q2.

[0111] In some embodiments, the first PDCCH candidate and the second PDCCH candidate may be set to be explicitly linked / associated together. For example, the terminal device 110-1 can know the link / association before decoding. In some embodiments, there may be a first PDCCH / DCI transmitted / received within the first PDCCH candidate. In some embodiments, there may be a second PDCCH / DCI transmitted / received within the second PDCCH candidate. In some embodiments, the number of DCI payloads and / or encoded bits and / or CCEs within the first PDCCH / DCI is the same as that of the second PDCCH / DCI. In some embodiments, the first PDCCH / DCI and the second PDCCH / DCI schedule the same communication between the network device 120 and the terminal device 110. For example, the communication may be at least one of PDSCH, PUSCH, sounding reference signal (SRS), channel state information reference signal (CSI-RS), transport block, change of active UL BWP, change of active DL BWP, and PUCCH.

[0112] In some embodiments, the network device 120 may send a setting to the terminal device 110 indicating that the first PDCCH candidate and the second PDCCH candidate are linked together for PDCCH repetition. In some embodiments, the network device 120 may send a setting to the terminal device 110 indicating that the first search space (or the first search space set or the first CORESET) and the second search space (or the second search space set or the second CORESET) are linked together. For example, this setting may be sent from the network device 120 to the terminal device 110-1 via any one of radio resource control (RRC) signaling, media access control (MAC) control element (CE), and DCI. For example, the first PDCCH candidate and the second PDCCH candidate may be used to carry a single or the same DCI format (or DCI payload).

[0113] In some embodiments, the first PDCCH candidate may end before or prior to the second PDCCH candidate in the time domain.

[0114] In some embodiments, the network device 120 may transmit at least one setting related to the first CORESET and the second CORESET to the terminal device 110.

[0115] In some embodiments, at least one configuration can configure a first set of search spaces associated with a first CORESET. In some embodiments, at least one configuration can configure a second set of search spaces associated with a second CORESET. In some embodiments, at least one configuration can configure a first set of PDCCH candidates within a first search space of the first set of search spaces. In some embodiments, at least one configuration can configure a second set of PDCCH candidates within a second search space of the second set of search spaces. In some embodiments, at least one configuration may be set such that a first PDCCH candidate within a first search space of the first set of search spaces associated with the first CORESET is linked, associated, or related to a second PDCCH candidate within a second search space of the second set of search spaces associated with the second CORESET. For example, the terminal device knows the link or association or relationship before decoding the PDCCH or DCI within the first and second PDCCH candidates. In some embodiments, the first and second PDCCH candidates may be used for PDCCH repetition. For example, the encoding and / or rate matching of the PDCCH or DCI within the first PDCCH candidate and / or the second PDCCH candidate is based on one repetition (e.g., the PDCCH or DCI within one of the first and second PDCCH candidates). For example, for other repetitions, the same encoded bits are repeated. For another example, each repetition has the same number of control channel elements (CCEs) and encoded bits and corresponds to the same DCI payload. In some embodiments, at least one configuration may be transmitted / received via at least one of RRC signaling, MAC CE, and DCI.

[0116] In some embodiments, the PDCCH candidates in the first search space set are linked to the PDCCH candidates in the second search space set based on two PDCCH candidates having the same aggregation level and the same candidate index. For example, the aggregation level of the first PDCCH candidate is the same as the aggregation level of the second PDCCH candidate. For another example, the candidate index of the first PDCCH candidate is the same as the candidate index of the second PDCCH candidate.

[0117] In some embodiments, the network device 120 may transmit one or more configurations of the third CORESET to the terminal device 110. The one or more configurations may indicate two active TCI states for the third CORESET. For example, the terminal device 110-1 may detect / decipher a PDCCH within a search space set associated with a third CORESET having two active TCI states.

[0118] In some embodiments, the network device 120 may transmit one or more configurations for a first number of PDSCH / PUSCH / PUCCH transmissions / receptions / repetitions / occasions to the terminal device 110. For example, the first number is represented as G. For example, 1≤G≤32. For another example, G may be at least one of {1, 2, 3, 4, 5, 6, 7, 8, 16, 32}. In some embodiments, the network device 120 may transmit scheduling for a first number of PDSCH / PUSCH / PUCCH transmissions / receptions / repetitions / occasions within a single DCI / PDCCH or within a linked PDCCH candidate to the terminal device 110. In some embodiments, two TCI states (e.g., a first TCI state and a second TCI state) or two spatial relation information (e.g., a first spatial relation information and a second spatial relation information) may be indicated / set within a single DCI / PDCCH or within a PDCCH within a linked PDCCH candidate.

[0119] In some embodiments, when M≧2, there may be two PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasion sets (e.g., set 1 and set 2) for a plurality of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions. Set 1 has a second number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions (the second number is G1, G1 is a positive integer, e.g., G1 = G / 2 or G1 = ceil(G / 2) or G1 = floor(G / 2)), and set 2 has a third number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions (the third number is G2, G2 = G−G1). In some embodiments, set 1 of the PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions is transmitted / received with a first TCI state or first spatial relation information, and set 2 of the PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions is transmitted / received with a second TCI state or second spatial relation information.

[0120] In some embodiments, the network device 120 may set a mapping type for the terminal device 110. For example, the mapping type may indicate the association between the TCI state and PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasion. In some embodiments, the network device 120 may set a cyclic mapping type (e.g., 210) for the terminal device 110, and the network device may set the first number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions to be greater than 2. Also, the first and second TCI states are respectively applied to the first and second PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions, and the same TCI mapping pattern continues to be applied to the remaining PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions. In some embodiments, the network device 120 may set a sequential mapping type for the terminal device 110, and the network device may set the first number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions to be greater than 2. Also, the first TCI state is applied to the first and second PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions, the second TCI state is applied to the third and / or fourth PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions, and the same TCI mapping pattern continues to be applied to the remaining PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions. In some embodiments, the network device 120 may set the first number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasions to be 2. Also, the first TCI state is applied to the first PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasion, and the second TCI state is applied to the second PDSCH / PUSCH / PUCCH transmission / reception / repetition / occasion.

[0121] For a UE configured to have a higher layer repetitionScheme set to 「fdmSchemeA」 or 「fdmSchemeB」, when two TCI states are indicated within the code point of the DCI field 「Transmission Configuration Indication」 and the DM-RS ports within one CDM group are indicated within the DCI field 「Antenna Port(s)」, the UE receives a single PT-RS port associated with the DM-RS antenna port with the lowest index among the DM-RS antenna ports assigned for the PDSCH. The PT-RS frequency density is determined by the number of PRBs associated with each TCI state, and the PT-RS resource element mapping is associated with the PRBs assigned for each TCI state.

[0122] In addition to normal data communication, the network device 120 may transmit RS in the downlink to the terminal device 110-1. Similarly, the terminal device 110-1 may transmit RS to the network device 120 in the uplink. Generally, RS is a signal sequence (also referred to as 「RS sequence」) known to both the network device 120 and the terminal device 110. For example, the RS sequence may be generated and transmitted by the network device 120 based on certain rules, and the terminal device 110-1 may estimate the RS sequence based on the same rules. In another example, the RS sequence may be generated and transmitted by the network device 110-1 based on certain rules, and the network device 120 may estimate the RS sequence based on the same rules. Examples of RS may include, but are not limited to, downlink or uplink demodulation reference signals (DMRS), CSI-RS, sounding reference signals (SRS), phase tracking reference signals (PTRS), tracking reference signals (TRS), micro-time frequency tracking reference signals (TRS), CSI-RS for tracking, positioning reference signals (PRS), etc.

[0123] In addition to normal data communication, the network device 120 can transmit DCI to the terminal device 110 via PDCCH. The DCI may indicate resource allocation for data transmission in DL or UL. At the same time, the DMRS associated with the PDCCH can also be transmitted from the network device 120 to the terminal device 110. The DMRS can be used by the terminal device 110-1 for channel demodulation. Then, the terminal device 110-1 may attempt to blindly decode the DCI within the search space associated with the control information set (CORESET). As used herein, "CORESET" and / or the search space refer to a set of resource element groups where the terminal device attempts to blindly decode the DCI. The search space indicating the start time and periodicity for monitoring the PDCCH within the CORESET may be shown to the terminal device 110. In response to successfully decoding the DCI, the terminal device 110-1 may accordingly perform UL and / or DL data transmission with the network device 120 (for example, data transmission via PDSCH and / or PUSCH (Physical Uplink Shared Channel)).

[0124] The network device 120 may communicate data and control information to the terminal device 110-1 via a plurality of beams (also referred to as "DL beams"). The terminal device 110-1 may also communicate data and control information to the network device 120 via a plurality of beams (also referred to as "UL beams"). In the 3GPP specifications for New Radio (NR), a beam is also defined and indicated by the parameters of a transmission configuration indicator. For example, there may be a transmission configuration indication (TCI) field in the DCI. The value of the TCI field may be referred to as a "TCI code point". The TCI code point may indicate one or more TCI states. Each TCI state includes parameters for setting a quasi-collocation (QCL) relationship between one or two DL and / or UL reference signals and the DMRS ports of PDSCH, the DMRS ports of PDCCH, the DMRS ports of PUSCH, the DMRS ports of PUCCH, the SRS ports of SRS resources, or the CSI-RS ports of CSI-RS resources.

[0125] In some embodiments, the communication between the network device 120 and the terminal device 110-1 may be within the same component carrier (CC) or within the same bandwidth part (BWP).

[0126] In the present disclosure, the terms "time threshold", "threshold", and "timing" may be used interchangeably. The terms "first threshold", "first time threshold", and "threshold A" may be used interchangeably. The terms "second threshold", "second time threshold", and "threshold B" may be used interchangeably. The terms "transmit", "receive", "transmission", "reception", "scheduling", "schedule", "buffering", "buffer", "detection", "detect", "monitoring", and "monitor" may be used interchangeably. The terms "predetermined", "determined", "set", "indicated", "signaled", and "reported" may be used interchangeably. The terms "setting", "indication", "information", "signaling", and "parameter" may be used interchangeably. The terms "set", "subset", and "group" may be used interchangeably. The terms "acknowledgment", "positive acknowledgment", "ACK", "hybrid automatic repeat request acknowledgment", "HARQ-ACK", "negative acknowledgment", "NACK", "NAK", "ACK / NACK", and "ACK / NAK" may be used interchangeably.

[0127] In some embodiments, for the terminal device 110, a first time threshold H1 and / or a second time threshold H2 may exist. For example, the first time threshold H1 and / or the second time threshold H2 may be predefined for the terminal device 110. For another example, the first time threshold H1 and / or the second time threshold H2 may be defined based on the capabilities of the terminal device 110. For another example, the first time threshold H1 and / or the second time threshold H2 may be set for the terminal device via at least one of RRC, MAC CE, and DCI. In some embodiments, the first time threshold H1 may be the same as or different from the second time threshold H2. In some embodiments, the first time threshold H1 and / or the second time threshold H2 may be the same as the threshold timeDurationForQCL or beamSwitchTiming defined in TS 38.214 or TS 38.306.

[0128] In some embodiments, the first time threshold H1 may be a duration for determining a TCI state for PDSCH or for beam switching. In some embodiments, the first time threshold H1 may indicate a predetermined / set period. The predetermined / set period may be Xi ms / us / slot / symbol / sub-slot, where Xi is an integer. For example, 1≦Xi≦336. For example, the predetermined period Xi may be 7, 14, or 28 symbols, for example, 7, 14, or 28 symbols when the subcarrier spacing is 60KHz, and may be 14 or 28 symbols when the subcarrier spacing is 120KHz. In another example, the predetermined period Xi may be L slots, where L is an integer and L may be any of {0,1,2,3,4,5,6,7,8}.

[0129] In some embodiments, the second time threshold H2 may be a duration for the application timing of the indicated / updated TCI state. In some embodiments, the second time threshold H2 may indicate a predetermined / set period. The predetermined / set period may be Yi ms / us / slot / symbol / sub-slot, where Yi is an integer. For example, 1≦Yi≦336. For example, the predetermined period Yi may be 7, 14, or 28 symbols, for example, 7, 14, or 28 symbols when the subcarrier spacing is 60KHz, and may be 14 or 28 symbols when the subcarrier spacing is 120KHz. In another example, the predetermined period Yi may be M slots, where M is an integer and M may be any of {0,1,2,3,4,5,6,7,8}.

[0130] In some embodiments, the first time threshold H1 may indicate a predetermined / set period after the last symbol of the PDCCH (represented as "PDCCH P") that schedules the PDSCH. For example, the predetermined / set period may be Xi ms / us / slot / symbol / subslot. For example, the predetermined period may be 7, 14, or 28 symbols. For example, when the subcarrier spacing is 60 KHz, it may be 7, 14, or 28 symbols, and when the subcarrier spacing is 120 KHz, it may be 14 or 28 symbols. For example, the predetermined / set period may depend on the UE capabilities reported by the terminal device 110.

[0131] In some embodiments, there is an application timing for beam indication or TCI state indication. In some embodiments, the application timing may be the first slot or the first sub - slot that is at least X ms or Y symbols after the last symbol of the acknowledgement response of the combined or separate DL / UL beam indication. For example, Y may be an integer, and 1 ≤ Y ≤ 336. In some embodiments, a slot may include 12 or 14 symbols. In some embodiments, a sub - slot may include S symbols. S is an integer, and 1 ≤ S ≤ 14. For example, S may be at least one of {2, 4, 7}. In some embodiments, the beam indication is indicated in DCI within PDCCH. For example, the DCI within PDCCH may schedule PDSCH or may not schedule PDSCH. In some embodiments, the gap between the last symbol of DCI and the first slot or the first sub - slot should satisfy the capabilities of the terminal device. In some embodiments, the acknowledgement response of the combined or separate DL / UL beam indication may be the acknowledgement response of the PDSCH scheduled by DCI. For example, in the case where DCI schedules PDSCH. In some embodiments, the acknowledgement response of the combined or separate DL / UL beam indication may be the acknowledgement response of DCI. For example, in the case where DCI does not schedule PDSCH.

[0132] In some embodiments, the terminal device may receive or detect DCI (e.g., represented as "DCI_t") within the PDCCH, and the DCI indicates a combined DL / UL TCI state or separate DL / UL TCI states or a DL TCI state or a UL TCI state or a pair of DL / UL TCI states. In some embodiments, the second time threshold H2 may indicate a predetermined / set period after the first or last symbol of the PDCCH or the first or last symbol of the acknowledgment response of the indication. In some embodiments, the indicated combined DL / UL TCI state or separate DL / UL TCI states or DL TCI state or UL TCI state or pair of DL / UL TCI states 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 or the second time threshold H2. For example, when a combined DL / UL TCI state is indicated within the DCI, the combined DL / UL TCI state 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 or the second time threshold H2. For another example, when a DL TCI state is indicated within the DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing or the second time threshold H2. For another example, when a UL TCI state is indicated within the DCI, the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing or the second time threshold H2. For another example, when a pair of DL / UL TCI states is indicated within the DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after the application timing or the second time threshold H2, and the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after the application timing or the second time threshold H2.

[0133] In some embodiments, the terminal device 110-1 may receive an indication indicating a downlink TCI state (or a set of beams or QCL parameters), and the source reference signal within the TCI state provides QCL information for reception in at least the PDSCH and all CORESETs within a component carrier (CC). For example, the PDSCH is dedicated or UE-specific.

[0134] In some embodiments, the terminal device 110-1 may receive an indication indicating an uplink TCI state (or a beam or spatial relationship), and the source reference signal within the TCI state provides a reference for determining an uplink transmission spatial filter for at least dynamic grants or all PUCCH resources within a PUSCH and CC based on configured grants. For example, the PUCCH is dedicated or UE-specific.

[0135] In some embodiments, the terminal device 110-1 may receive an indication indicating a combined TCI state (or a set of beams or QCL parameters), and the TCI state refers to a common source reference signal used to determine at least both downlink QCL information and an uplink transmission spatial filter.

[0136] In some embodiments, the terminal device 110-1 may receive an indication indicating a downlink TCI state (or a set of beams or QCL parameters) and an uplink TCI state (or a beam or spatial relationship). The source reference signal within the DL TCI state provides QCL information for reception in at least the PDSCH and all CORESETs within a component carrier (CC), and the source reference signal within the TCI state provides a reference for determining an uplink transmission spatial filter for at least a PUSCH based on dynamic grants or configured grants and all PUCCH resources within a CC. For example, the PUCCH is dedicated or UE-specific. For another example, the PDSCH is dedicated or UE-specific.

[0137] In some embodiments, the terminal device 110-1 may be configured to have two or more (e.g., represented as M, where M is a positive integer. For example, M may be 2, 3, or 4) downlink TCI states, and / or the terminal device 110-1 may receive an indication indicating one of the M TCI states, and the source reference signal within the one of the M TCI states or within the indicated one TCI state provides QCL information for reception in at least a subset of the CORESETs within the PDSCH and / or the CC. For example, the PDSCH may be dedicated or UE-specific.

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

[0139] In some embodiments, the terminal device 110-1 is configured to have two or more (e.g., represented as M, where M is a positive integer. For example, M may be 2, 3, or 4) combined DL / UL TCI states, and / or may receive an indication indicating one of the M combined TCI states, and each TCI state of the M TCI states or the indicated one TCI state refers to at least a common source reference signal used to determine both downlink QCL information and uplink transmission spatial filter.

[0140] In some embodiments, the terminal device 110-1 may be configured to have two or more (e.g., represented as M, where M is a positive integer. For example, M may be 2, 3, or 4) downlink TCI states, and the terminal device 110-1 may be configured to have two or more (e.g., represented as N, where N is a positive integer. For example, N may be 2, 3, or 4) uplink TCI states, and / or the terminal device 110-1 may receive an indication indicating one from the M downlink TCI states and one from the N uplink TCI states. The source reference signal in each DL TCI state within the M DL TCI states or the indicated one DL TCI state provides QCL information for reception in at least a subset of the PDSCH and / or CORESET within a component carrier (CC), and the source reference signal in each TCI state within the N TCI states or the indicated one UL TCI state provides a reference for determining an uplink transmission spatial filter for at least a dynamic grant or a subset of PUSCH and / or PUCCH resources within the CC based on a configured grant. For example, the PUCCH is dedicated or UE-specific. For another example, the PDSCH is dedicated or UE-specific.

[0141] Hereinafter, DCI_t is used to describe the DCI for the combined DL / UL TCI state indication or for the separate DL / UL TCI state indication. Hereinafter, the terms "DCI", "PDCCH", "DCI_t", "DCI for combined DL / UL TCI state indication", "DCI for separate DL / UL TCI state indication", "DCI for DL TCI state indication", "DCI for UL TCI state indication", "PDCCH for combined DL / UL TCI state indication", "PDCCH for separate DL / UL TCI state indication", "PDCCH for DL TCI state indication", "PDCCH for UL TCI state indication", "DCI for TCI state indication", and "PDCCH for TCI state indication" may be used interchangeably.

[0142] In some embodiments, the DCI may be used to indicate a TCI state for a combined DL / UL TCI state indication or for separate DL / UL TCI state indications. Also, the DCI may schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). In some embodiments, the HARQ of the PDSCH scheduled by the DCI may be used as an ACK for the DCI. For example, the DCI may be DCI_t.

[0143] In some embodiments, the DCI may be used to indicate a TCI state for a combined DL / UL TCI state indication or for separate DL / UL TCI state indications. Also, the DCI may not schedule a PDSCH (e.g., DCI format 1_1 and format 1_2). In some embodiments, the HARQ of the DCI may be introduced to indicate whether the DCI or the TCI state indication was successful. For example, the DCI may be DCI_t.

[0144] 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 a certain application timing.

[0145] In some embodiments, the HARQ mechanism for semi-persistent scheduling (SPS) PDSCH release may be reused for the HARQ of DCI_t, and there is no PDSCH scheduling in DCI_t.

[0146] In some embodiments, 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 combined DL / UL TCI state indication or separate DL / UL TCI state indication. Also, the DCI may not schedule the PDSCH (e.g., DCI formats 1_1 and 1_2). In some embodiments, upon successful reception / decoding of the DCI, the terminal device 110-1 may report an ACK. In some embodiments, upon failed reception / decoding of the DCI, the terminal device 110-1 may report a NACK. For example, the ACK and / or NACK may be reported on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). In some embodiments, the terminal device 110-1 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 at least one of RRC, MAC CE, and DCI. In some embodiments, the DCI is received / detected on the PDCCH.

[0147] In some embodiments, for HARQ-ACK information bits, the terminal device 110-1 generates an acknowledgement response (ACK) when the terminal device 110-1 detects a DCI format that provides an SPS PDSCH release or beam indication scrambled with a CS-RNTI, or when the transport block is correctly decoded, and generates a negative acknowledgement response (NACK) when the terminal device 110-1 fails to correctly decode the transport block. A HARQ-ACK information bit value of 0 represents a NACK, and a HARQ-ACK information bit value of 1 represents an ACK.

[0148] In some embodiments, the terminal device 110-1 may be configured / shown to have a first TCI state for receiving all or a subset of PDSCH and / or CORESET. Also, the terminal device 110-1 may receive or detect a first PDCCH using the first TCI state, and the PDCCH is within a first CORESET. A second TCI state may be indicated in the DCI received or detected in the first PDCCH for the terminal device 110-1. In some embodiments, the DCI in the first PDCCH may or may not schedule a first PDSCH or a first PUSCH. In some embodiments, the terminal device 110-1 may report the decoding result or HARQ-ACK information for at least one of the DCI, the first PDCCH, or the first PDSCH to the network device 120. For example, the decoding result or HARQ-ACK information may be transmitted / reported within a PUCCH or within a second PUSCH. In some embodiments, after the applicable timing or after a second time threshold H2, the terminal device 110-1 may receive all or a subset of PDSCH and / or CORESET using the second TCI state. For example, the terminal device 110-1 may receive a second PDCCH using the second TCI state, and the second PDCCH is within a second CORESET. For another example, the terminal device 110-1 may receive a second PDCCH using the second TCI state, and the second PDCCH is within the first CORESET.

[0149] FIG. 2 is a signaling diagram regarding communication between a network device and a terminal device according to some embodiments of the present disclosure. For the sake of explanation, process 200 will be described with reference to FIG. 1. As shown in FIG. 1, the network device 120 and the terminal device 110-1 may be involved in process 200.

[0150] In some embodiments, the terminal device 110-1 may be configured / shown to have a third TCI for receiving all or a subset of PDSCH and / or CORESET. For example, the third TCI is applied at the time (or within a slot / sub-slot) for the first PDCCH reception. In some embodiments, the network device 120 transmits the first PDCCH to the terminal device 110-1 (2010). The terminal device 110-1 may receive or detect the first PDCCH using the third TCI. For example, the first PDCCH is within the first CORESET. In some embodiments, the first TCI may be indicated in the first DCI received or detected in the first PDCCH at the terminal device 110-1. In some embodiments, the first DCI may schedule the PDSCH or may not schedule the PDSCH. In some embodiments, the terminal device 110-1 may report to the network device 120 the decoding result or the first HARQ-ACK information for at least one of the first DCI or the first PDCCH or the PDSCH scheduled by the first DCI. For example, the decoding result or the first HARQ-ACK information may be transmitted / reported within the first PUCCH or within the first PUSCH. In some embodiments, the terminal device 110-1 may be configured / shown to have a fourth TCI for receiving all or a subset of PUSCH and / or PUCCH. For example, the fourth TCI is applied at the time (or within a slot / sub-slot) for the first PUCCH or the first PUSCH transmission. For example, the terminal device 110-1 may transmit the first PUCCH or the first PUSCH using the fourth TCI.

[0151] In some embodiments, the network device 120 transmits the second PDCCH to the terminal device 110-1 (2020). In some embodiments, the terminal device 110-1 may receive or detect the second PDCCH using the fifth TCI or the third TCI. For example, the second PDCCH is within the first CORESET. For another example, the second PDCCH is within the second CORESET, where the settings for the first CORESET and the settings for the second CORESET are different. In some embodiments, the second TCI may be indicated in the second DCI received or detected in the second PDCCH for the terminal device 110-1. In some embodiments, the second DCI may or may not schedule the PDSCH. In some embodiments, the terminal device 110-1 may report to the network device 120 the decoding result or the second HARQ-ACK information for at least one of the second DCI or the second PDCCH or the PDSCH scheduled by the second DCI. For example, the decoding result or the second HARQ-ACK information may be transmitted / reported within the second PUCCH or the second PUSCH. For example, the terminal device 110-1 may transmit the second PUCCH or the second PUSCH using the fourth TCI or the sixth TCI. In some embodiments, the terminal device 110-1 may be configured / indicated to have the fifth TCI for receiving all or a subset of the PDSCH and / or CORESET. For example, the fifth TCI is applied at the time for receiving the second PDCCH (or within a slot / sub-slot). In some embodiments, the terminal device 110-1 may be configured / indicated to have the sixth TCI for receiving all or a subset of the PUSCH and / or PUCCH. For example, the sixth TCI is applied at the time for transmitting the second PUCCH or the second PUSCH (or within a slot / sub-slot).

[0152] In some embodiments, the first TCI may be the first DL TCI state within the first pair of the first DL TCI state or the DL / UL TCI state, and the second TCI may be the second DL TCI state within the second pair of the second DL TCI state or the DL / UL TCI state. In some embodiments, the first TCI may be the first UL TCI state within the first pair of the first UL TCI state or the DL / UL TCI state, and the second TCI may be the second UL TCI state within the second pair of the second UL TCI state or the DL / UL TCI state. In some embodiments, the first DL TCI state may be different from the second DL TCI state. In some embodiments, the first UL TCI state may be different from the second UL TCI state. In some embodiments, the first pair of the DL / UL TCI state may be different from the second pair of the DL / UL TCI state. In some embodiments, the first TCI may be the first combined DL / UL TCI state, and the second TCI may be the second combined DL / UL TCI state. In some embodiments, the first combined DL / UL TCI state may be different from the second combined DL / UL TCI state.

[0153] In some embodiments, the third TCI may be the third combined DL / UL TCI state. In some embodiments, the third TCI may be the third DL TCI state. In some embodiments, the third TCI may be the third DL TCI state within the third pair of the DL / UL TCI state. In some embodiments, the fifth TCI may be the fifth combined DL / UL TCI state. In some embodiments, the fifth TCI may be the fourth DL TCI state. In some embodiments, the fifth TCI may be the fourth DL TCI state within the fifth pair of the DL / UL TCI state.

[0154] In some embodiments, the fourth TCI may be a fourth combined DL / UL TCI state. In some embodiments, the fourth TCI may be a third UL TCI state. In some embodiments, the fourth TCI may be the third UL TCI state within a fourth pair of DL / UL TCI states. In some embodiments, the sixth TCI may be a sixth combined DL / UL TCI state. In some embodiments, the sixth TCI may be a fourth UL TCI state. In some embodiments, the sixth TCI may be the fourth UL TCI state within a sixth pair of DL / UL TCI states.

[0155] In some embodiments, the third DL TCI state or the fourth DL TCI state may be the same as, or different from, the first DL TCI state or the second DL TCI state. In some embodiments, the third DL TCI state may be the same as, or different from, the fourth DL TCI state. In some embodiments, the third combined DL / UL TCI state or the fourth combined DL / UL TCI state or the fifth combined DL / UL TCI state or the sixth combined DL / UL TCI state may be the same as, or different from, the first combined DL / UL TCI state or the second combined DL / UL TCI state. In some embodiments, the third pair of DL / UL TCI states, or the fourth pair of DL / UL TCI states, or the fifth pair of DL / UL TCI states, or the sixth pair of DL / UL TCI states may be the same as, or different from, the second pair of DL / UL TCI states or the first pair of DL / UL TCI states.

[0156] In some embodiments, the first PDCCH may start or end before or prior to the second PDCCH. For example, the first or last symbol of the first PDCCH may be before or prior to the first or last symbol of the second PDCCH.

[0157] In some embodiments, the time and / or frequency resources for the first PUCCH or the first PUSCH are different from the time and / or frequency resources for the second PUCCH or the second PUSCH. In some embodiments, the first PUCCH or the first PUSCH may be within a slot or a sub-slot (e.g., represented as n1). In some embodiments, the second PUCCH or the second PUSCH may be within a slot or a sub-slot (e.g., represented as n2). For example, n1 is different from n2. For example, n1 is after n2, or not before n2. For another example, n1 is before or prior to n2. In some embodiments, the first PUCCH or the first PUSCH may start or end after, or subsequent to, the second PUCCH or the second PUSCH. For example, the first or last symbol of the first PUCCH or the first PUSCH may be after or subsequent to the first or last symbol of the second PUCCH or the second PUSCH. In some embodiments, the first PUCCH or the first PUSCH may start or end before, or prior to, the second PUCCH or the second PUSCH. For example, the first or last symbol of the first PUCCH or the first PUSCH may be before or prior to the first or last symbol of the second PUCCH or the second PUSCH.

[0158] In some embodiments, the first application timing for the first TCI may be the first one slot or the first one sub - slot that is X ms or Y symbols after the last symbol of the first PUCCH or the first PUSCH. In some embodiments, the second application timing for the second TCI may be the first one slot or the first one sub - slot that is X ms or Y symbols after the last symbol of the second PUCCH or the second PUSCH. In some embodiments, the slot or sub - slot for the first application timing for the first TCI may be the same as the slot or sub - slot for the second application timing for the second TCI. In some embodiments, the first HARQ - ACK information corresponding to the first DCI or the PDSCH scheduled by the first DCI may be ACK. In some embodiments, the second HARQ - ACK information corresponding to the second DCI or the PDSCH scheduled by the second DCI may be ACK. In some embodiments, the first HARQ - ACK information and the second HARQ - ACK information may be transmitted within different time and / or frequency resources. For example, the time / frequency resource may be a PUSCH resource or a PUCCH resource.

[0159] In some embodiments, the terminal device 110 - 1 may receive all or a subset of the PDSCH and / or CORESET using the second TCI from the first one slot or the first one sub - slot, or after / applying the application timing. In some embodiments, the terminal device 110 - 1 may transmit all or a subset of the PUSCH and / or PUCCH using the second TCI from the first one slot or the first one sub - slot, or after / applying the application timing.

[0160] Figs. 3A to 3D show examples of the setting of one or two PDCCHs for the terminal device 110. The one or two PDCCHs are applied to the same scheduling of communication between the network device 120 and the terminal devices 110-1 to 110. For example, the communication may be at least one of a PDCCH, a PDSCH, a PUSCH, a PUCCH, a downlink RS, and an uplink RS.

[0161] In the example of Fig. 3A, the TCI state 1-11 may be set for the terminal device 110-1 to monitor the PDCCH within the CORESET / search space. As shown in Fig. 3A, the terminal device 110-1 may receive the PDCCH 311 using the TCI state 1-1 for communication scheduling. In some embodiments, there may be one or more TCI states or spatial relation information indicated within the PDCCH 311 for communication scheduling.

[0162] In the example of FIG. 3B, the TCI state 2-1 may be set for the terminal device 110-1 to monitor the first PDCCH within the first CORESET / search space, and the TCI state 2-2 may be set for the terminal device 110-1 to monitor the second PDCCH within the second CORESET / search space. For example, the scheduling of the communication in the first PDCCH and the schedule of the communication in the second PDCCH may be independent or separated. As shown in FIG. 3B, the terminal device 110-1 may receive the PDCCH 321 using the TCI state 2-1 for the first scheduling of the communication. In some embodiments, there may be one or more TCI states or spatial relationship information indicated within the PDCCH 321 for the first scheduling of the communication. As also shown in FIG. 3B, the terminal device 110-1 may receive the PDCCH 322 using the TCI state 2-2 for the second scheduling of the communication. In some embodiments, there may be one or more TCI states or spatial relationship information indicated within the PDCCH 322 for the second scheduling of the communication. In some embodiments, the PDCCH 321 and the PDCCH 322 may not overlap, partially overlap, or completely overlap in the time domain and / or the frequency domain. In some embodiments, the first communication and the second communication may not overlap, partially overlap, or completely overlap in the time domain and / or the frequency domain.

[0163] In the example of FIG. 3C, TCI state 3-1 may be set for the terminal device 110-1 to monitor the first PDCCH within the first CORESET / search space, and TCI state 3-2 may be set for the terminal device 110-1 to monitor the second PDCCH within the second CORESET / search space. According to some embodiments of the present disclosure, the first CORESET / search space and the second CORESET / search space are set to be linked. For example, the first PDCCH and the second PDCCH are applied to schedule the same communication between the network device 120 and the terminal device 110-1. For another example, the payload or information within the first PDCCH and the second PDCCH is the same. As shown in FIG. 3C, the terminal device 110-1 may receive the PDCCH 331 using the TCI state 3-1 for communication scheduling, and the terminal device 110-1 may receive the PDCCH 332 using the TCI state 3-2 for the same communication scheduling. In some embodiments, one or more TCI states or spatial relationship information indicated within the PDCCH 331 and the PDCCH 332 for communication scheduling may exist.

[0164] In the example of FIG. 3D, the TCI state 4-1 and the TCI state 4-2 may be set for the terminal device 110-1 to monitor the PDCCH within the CORESET / search space. As shown in FIG. 3D, the terminal device 110-1 may receive the PDCCH 341 using the TCI state 4-1 and the TCI state 4-2 for communication scheduling. In some embodiments, one or more TCI states or spatial relationship information indicated within the PDCCH 341 for communication scheduling may exist.

[0165] If the reception of the second PDCCH is later than the reception of the first PDCCH, the terminal device 110-1 communicates with the network device 120 using the second TCI after a certain period, or after / applying the timing / from the applying timing (2030).

[0166] In an exemplary embodiment, the terminal device 110-1 may transmit a second hybrid automatic repeat request (HARQ) feedback corresponding to a second scheduling based on a second PDCCH. The terminal device 110-1 may transmit a first HARQ feedback corresponding to a first scheduling based on a first PDCCH. In some embodiments, if the transmission of the first HARQ feedback is after or subsequent to the transmission of the second HARQ feedback, the terminal device 110-1 may communicate with the network device 120 using the second TCI after that period, or after the application timing / from the application timing. The first scheduling may be a PDSCH scheduling based on a first PDCCH. The second scheduling may be a TCI state without a PDSCH scheduling based on a second PDCCH, or a pair of TCI state indications. In other embodiments, the second scheduling may be a PDSCH scheduling based on a second PDCCH.

[0167] Alternatively, if the first TCI state is applicable and the second TCI state is not applicable, the terminal device 110-1 may communicate with the network device using the first TCI state.

[0168] Figure 4 shows a schematic diagram for applying beam / TCI states according to some exemplary embodiments. As shown in Figure 4, the terminal device 110-1 may receive or detect the PDCCH 411, and the DCI detected within the PDCCH 411 may indicate the first TCI. Also, the PDCCH 411 or the DCI detected within the PDCCH 411 may schedule the PDSCH or may not schedule it. Further, the terminal device 110-1 may report the HARQ feedback 413 to the network device 120 regarding the PDSCH scheduled by the PDCCH 411 or regarding the DCI within the PDCCH 411. For example, the HARQ feedback 413 is ACK. The terminal device 110-1 may receive or detect the PDCCH 421, and the DCI detected within the PDCCH 421 may indicate the second TCI. Also, the PDCCH 421 or the DCI detected within the PDCCH 421 may schedule the PDSCH or may not schedule it. Further, the terminal device 110-1 may report the HARQ feedback 423 to the network device 120 regarding the PDSCH scheduled by the PDCCH 421 or regarding the DCI within the PDCCH 421. For example, the HARQ feedback 423 is ACK. For example, the terminal device 110-1 may be configured / shown to have a third TCI for receiving all or a subset of the PDSCH and / or CORESET. For example, the third TCI is applied at the time for receiving the PDCCH 411 (or within a slot / sub-slot). For example, the terminal device 110-1 may receive the PDCCH 411 using the third TCI. For example, the terminal device 110-1 may receive the PDCCH 421 using the third TCI. For another example, the terminal device 110-1 may receive the PDCCH 421 using the fourth TCI, where the fourth TCI may be configured / shown for the terminal device 110-1 to receive all or a subset of the PDSCH and / or CORESET at the time for receiving the PDCCH 421 (or within a slot / sub-slot). For example, the third TCI may be the same as or different from the fourth TCI.In some embodiments, the application timing for the first TCI and the application timing for the second TCI may be the same, for example, TIMING 404 shown in FIG. 4. In this case, within one slot or sub-slot, there are two or more applicable beam / TCI states. The number of applicable beam / TCI states may be any integer. It should be noted that the number of PDCCHs is merely an example and not a limitation. In this case, the beam / TCI corresponding to the latest or subsequent PDCCH is applied. For example, as shown in FIG. 4, the beam / TCI indicated within PDCCH 421 is applied after TIMING 404 or from TIMING 404. The terminal device 110-1 may communicate with the network device 120 using the second TCI after or from timing 404. In this way, the uncertainty regarding the network device and the terminal device can be avoided.

[0169] In some embodiments, the terminal device 110-1 may be configured / shown to have a third TCI for receiving all or a subset of PDSCH and / or CORESET. For example, the third TCI is applied at the time for receiving the first PDCCH (or within a slot / sub-slot). In some embodiments, the network device 120 may transmit the first PDCCH to the terminal device 110-1. The terminal device 110-1 may receive or detect the first PDCCH using the third TCI. For example, the first PDCCH is within the first CORESET. In some embodiments, the first TCI may be indicated in the first DCI received or detected in the first PDCCH at the terminal device 110-1. In some embodiments, the first DCI may or may not schedule the PDSCH. In some embodiments, the terminal device 110-1 may report to the network device 120 the decoding result or the first HARQ-ACK information for at least one of the first DCI or the first PDCCH or the PDSCH scheduled by the first DCI. For example, the decoding result or the first HARQ-ACK information may be transmitted / reported within the first PUCCH or the first PUSCH. In some embodiments, the terminal device 110-1 may be configured / shown to have a fourth TCI for receiving all or a subset of PUSCH and / or PUCCH. For example, the fourth TCI is applied at the time for transmitting the first PUCCH or the first PUSCH (or within a slot / sub-slot). For example, the terminal device 110-1 may transmit the first PUCCH or the first PUSCH using the fourth TCI.

[0170] In some embodiments, the network device 120 may transmit a second PDCCH to the terminal device 110-1. In some embodiments, the terminal device 110-1 may receive or detect the second PDCCH using a fifth TCI or a third TCI. For example, the second PDCCH is within a first CORESET. For another example, the second PDCCH is within a second CORESET, where the settings for the first CORESET are different from the settings for the second CORESET. In some embodiments, a second TCI may be indicated in a second DCI received or detected in the second PDCCH for the terminal device 110-1. In some embodiments, the second DCI may not schedule a PDSCH. In some embodiments, the terminal device 110-1 may report a decoding result or second HARQ-ACK information for the second DCI or the second PDCCH to the network device 120. For example, the decoding result or the second HARQ-ACK information may be transmitted / reported within a second PUCCH or a second PUSCH. For example, the terminal device 110-1 may transmit the second PUCCH or the second PUSCH using a fourth TCI or a sixth TCI. In some embodiments, the terminal device 110-1 may be set / indicated to have a fifth TCI for receiving all or a subset of the PDSCH and / or CORESET. For example, the fifth TCI is applied at the time for receiving the second PDCCH (or within a slot / sub-slot). In some embodiments, the terminal device 110-1 may be set / indicated to have a sixth TCI for receiving all or a subset of the PUSCH and / or PUCCH. For example, the sixth TCI is applied at the time for transmitting the second PUCCH or the second PUSCH (or within a slot / sub-slot).

[0171] In some embodiments, the first TCI may be the first DL TCI state within a first pair of the first DL TCI state or the DL / UL TCI state, and the second TCI may be the second DL TCI state within a second pair of the second DL TCI state or the DL / UL TCI state. In some embodiments, the first TCI may be the first UL TCI state within a first pair of the first UL TCI state or the DL / UL TCI state, and the second TCI may be the second UL TCI state within a second pair of the second UL TCI state or the DL / UL TCI state. In some embodiments, the first DL TCI state may be different from the second DL TCI state. In some embodiments, the first UL TCI state may be different from the second UL TCI state. In some embodiments, the first pair of the DL / UL TCI states may be different from the second pair of the DL / UL TCI states. In some embodiments, the first TCI may be the first combined DL / UL TCI state, and the second TCI may be the second combined DL / UL TCI state. In some embodiments, the first combined DL / UL TCI state may be different from the second combined DL / UL TCI state.

[0172] In some embodiments, the third TCI may be the third combined DL / UL TCI state. In some embodiments, the third TCI may be the third DL TCI state. In some embodiments, the third TCI may be the third DL TCI state within a third pair of the DL / UL TCI states. In some embodiments, the fifth TCI may be the fifth combined DL / UL TCI state. In some embodiments, the fifth TCI may be the fourth DL TCI state. In some embodiments, the fifth TCI may be the fourth DL TCI state within a fifth pair of the DL / UL TCI states.

[0173] In some embodiments, the fourth TCI may be a fourth combined DL / UL TCI state. In some embodiments, the fourth TCI may be a third UL TCI state. In some embodiments, the fourth TCI may be the third UL TCI state within a fourth pair of DL / UL TCI states. In some embodiments, the sixth TCI may be a sixth combined DL / UL TCI state. In some embodiments, the sixth TCI may be a fourth UL TCI state. In some embodiments, the sixth TCI may be the fourth UL TCI state within a sixth pair of DL / UL TCI states.

[0174] In some embodiments, the third DL TCI state or the fourth DL TCI state may be the same as or different from the first DL TCI state or the second DL TCI state. In some embodiments, the third DL TCI state may be the same as or different from the fourth DL TCI state. In some embodiments, the third combined DL / UL TCI state or the fourth combined DL / UL TCI state or the fifth combined DL / UL TCI state or the sixth combined DL / UL TCI state may be the same as or different from the first combined DL / UL TCI state or the second combined DL / UL TCI state. In some embodiments, the third pair of DL / UL TCI states, or the fourth pair of DL / UL TCI states, or the fifth pair of DL / UL TCI states, or the sixth pair of DL / UL TCI states may be the same as or different from the second pair of DL / UL TCI states or the first pair of DL / UL TCI states.

[0175] In some embodiments, the first PDCCH may start or end before or prior to the second PDCCH. For example, the first or last symbol of the first PDCCH may be before or prior to the first or last symbol of the second PDCCH.

[0176] In some embodiments, the time and / or frequency resources for the first PUCCH or the first PUSCH are different from the time and / or frequency resources for the second PUCCH or the second PUSCH. In some embodiments, the first PUCCH or the first PUSCH may be within a slot or a sub-slot (e.g., represented as n1). In some embodiments, the second PUCCH or the second PUSCH may be within a slot or a sub-slot (e.g., represented as n2). For example, n1 is different from n2. For example, n1 is after n2 or not before n2. In some embodiments, the first PUCCH or the first PUSCH may start or end after or subsequent to the second PUCCH or the second PUSCH. For example, the first or last symbol of the first PUCCH or the first PUSCH may be after or subsequent to the first or last symbol of the second PUCCH or the second PUSCH.

[0177] In some embodiments, the first application timing for the first TCI may be the first one slot or the first one sub - slot that is X ms or Y symbols after the last symbol of the first PUCCH or the first PUSCH. In some embodiments, the second application timing for the second TCI may be the first one slot or the first one sub - slot that is X ms or Y symbols after the last symbol of the second PUCCH or the second PUSCH. In some embodiments, the slot or sub - slot for the first application timing for the first TCI may be later than the slot or sub - slot for the second application timing for the second TCI. In some embodiments, the first HARQ - ACK information corresponding to the first DCI or the PDSCH scheduled by the first DCI may be ACK. In some embodiments, the second HARQ - ACK information corresponding to the second DCI or the PDSCH scheduled by the second DCI may be ACK. In some embodiments, the first HARQ - ACK information and the second HARQ - ACK information may be transmitted within different time and / or frequency resources. For example, the time / frequency resource may be a PUSCH resource or a PUCCH resource.

[0178] In some embodiments, the terminal device 110-1 may receive all or a subset of PDSCH and / or CORESET using a second TCI from a first one of the slots or a first one of the sub-slots, or after / from a second application timing. In some embodiments, the terminal device 110-1 may transmit all or a subset of PUSCH and / or PUCCH using a second TCI from a first one of the slots or a first one of the sub-slots, or after / from a second application timing. In some embodiments, the terminal device 110-1 may receive all or a subset of PDSCH and / or CORESET using a second TCI from a first one of the slots or a first one of the sub-slots, or after / from a first application timing. For example, the first TCI is not applied after or from the first application timing. In some embodiments, the terminal device 110-1 may transmit all or a subset of PUSCH and / or PUCCH using a second TCI from a first one of the slots or a first one of the sub-slots, or after / from a first application timing. For example, the first TCI is not applied after or from the first application timing.

[0179] In some embodiments, the terminal device 110-1 may receive a first PDCCH with data allocation. The terminal device 110-1 may also receive a second PDCCH without data allocation. As shown in FIG. 5, the terminal device 110-1 may receive or detect PDCCH 511, and the DCI detected within PDCCH 511 may indicate a first TCI. Also, PDCCH 511 or the DCI detected within PDCCH 511 may schedule PDSCH 512. Further, the terminal device 110-1 may report a HARQ feedback 513 for PDSCH 512 to the network device 120. For example, the HARQ feedback 513 is ACK. The terminal device 110-1 may receive or detect PDCCH 521, and the DCI detected within PDCCH 421 may indicate a second TCI. PDCCH 521 or the DCI detected within PDCCH 521 may not schedule a PDSCH. The terminal device 110-1 may report a HARQ feedback 523 for the DCI within PDCCH 521 to the network device 120. For example, the HARQ feedback 523 is ACK. For example, the terminal device 110-1 may be set / shown to have a third TCI for receiving all or a subset of PDSCH and / or CORESET. For example, the third TCI is applied at the time (or within a slot / sub-slot) for receiving PDCCH 511. For example, the terminal device 110-1 may receive PDCCH 511 using the third TCI. For example, the terminal device 110-1 may receive PDCCH 521 using the third TCI. For another example, the terminal device 110-1 may receive PDCCH 521 using a fourth TCI, where the fourth TCI may be set / shown to the terminal device 110-1 for receiving all or a subset of PDSCH and / or CORESET at the time (or within a slot / sub-slot) for receiving PDCCH 521. For example, the third TCI may be the same as or different from the fourth TCI.

[0180] In some embodiments, PDCCH 511 may start or end before or prior to PDCCH 521. For example, the first or last symbol of PDCCH 511 may be before or prior to the first or last symbol of PDCCH 521. In some embodiments, the PUCCH or PUSCH resource for HARQ feedback 513 may start or end after or subsequent to the PUCCH or PUSCH resource for HARQ feedback 523. In some embodiments, the PUCCH or PUSCH resource for HARQ feedback 513 may be within a slot or sub - slot (e.g., represented as n1). In some embodiments, the PUCCH or PUSCH resource for HARQ feedback 523 may be within a slot or sub - slot (e.g., represented as n2). For example, n1 is different from n2. For example, n1 is after n2 or not before n2. In some embodiments, the first or last symbol of the PUCCH or PUSCH resource for HARQ feedback 513 may be after or subsequent to the first or last symbol of the PUCCH or PUSCH resource for HARQ feedback 523. In some embodiments, the application timing for the first TCI is TIMING 504 shown in FIG. 4, and the application timing for the second TCI is TIMING 505 shown in FIG. 4. For example, TIMING 505 is before TIMING 504.

[0181] In some embodiments, the terminal device 110-1 may receive all or a subset of PDSCH and / or CORESET from TIMING 505 using the second TCI. In some embodiments, the terminal device 110-1 may transmit all or a subset of PUSCH and / or PUCCH from TIMING 505 using the second TCI. In some embodiments, the terminal device 110-1 may still receive all or a subset of PDSCH and / or CORESET from TIMING 504 using the second TCI. For example, the first TCI is not applied from TIMING 504. In some embodiments, the terminal device 110-1 may still transmit all or a subset of PUSCH and / or PUCCH from TIMING 504 using the second TCI. For example, the first TCI is not applied from TIMING 504.

[0182] Since PDCCH 521 does not schedule PDSCH and PDCCH 511 schedules PDSCH 512, the transmission of HARQ feedback 523 may be earlier than the transmission of HARQ feedback 513. The terminal device 110-1 may apply the second TCI after timing 505. In this case, the terminal device 110-1 does not have to apply the first TCI after timing 504. In other words, the first TCI may be ignored by the terminal device 110-1. Thus, the delay can be reduced and unnecessary beam switching can be avoided.

[0183] Alternatively, if the second TCI indicated in PDCCH 521 is not applicable or there is no applied TCI state indicated in PDCCH 521 and the first TCI indicated in PDCCH 511 is applicable, the terminal device 110-1 may apply the first TCI from, for example, TIMING 504. For example, if HARQ feedback 523 is NACK, then the TCI indicated in PDCCH 521 may not be applicable.

[0184] In some embodiments, the terminal device 110-1 may receive DCI of different DCI formats. For example, the terminal device 110-1 may receive DCI of DCI format 1_2 and DCI format 1_1. When there is a DCI field "Transmission Configuration Indication" in DCI format 1_2, and when the number S of code points in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is less than the number of TCI code points activated by an activation command, for example, as described in Articles 6.1.3.14 and 6.1.3.24 of [10, TS38.321], only the first S-1 activated code points are applied to DCI format 1_2, and the remaining code points for DCI format 1_2 (for example, the first or last code point) indicate the latest or currently applied TCI state (or the latest or currently indicated TCI state in DCI format 1_1, or the TCI state indicated in DCI format 1_1 in the latest PDCCH before or prior to the PDCCH having DCI format 1_2). For example, as shown in FIG. 6, DCI format 1_1 may include 3 bits in the TCI field. In this case, DCI format 1_1 has a maximum of 8 code points shown as TCI 611, TCI 612, TCI 613, TCI 614, TCI 615, TCI 616, TCI 617, and TCI 618. DCI format 1_2 may include 2 bits in the TCI field. In this case, DCI format 1_2 has a maximum of 4 code points shown as TCI 621, TCI 622, TCI 623, and TCI 624.In this case, three code points for DCI format 1_2 may be indicated or applied, and the remaining code points for DCI format 1_2 may indicate one of the most recent or currently applied TCI state, the most recent or currently indicated TCI state within DCI format 1_1, or the TCI state indicated within DCI format 1_1 in the most recent PDCCH prior to or before the PDCCH having DCI format 1_2. For example, TCI 621, TCI 622, TCI 623, and TCI 624 may be represented as "00", "01", "10", and "11", respectively. As an example only, TCI 621, TCI 622, and TCI 623 may be applied for format 1_2. In this case, if the DC field indicates "11", this may indicate that the DCI field indicates one of the most recent or currently applied TCI state, the most recent or currently indicated TCI state within DCI format 1_1, or the TCI state indicated within DCI format 1_1 in the most recent PDCCH prior to or before the PDCCH having DCI format 1_2. If the DCI field indicates any one of "00", "01", and "10", the terminal device 110-1 may determine the TCI state based on the DCI after the application timing.

[0185] In some embodiments, the sizes of the TCI fields within different DCI formats (e.g., DCI format 1_1 and DCI format 1_2) may be the same. In other words, the terminal device 110-1 does not expect different sizes of TCI fields within different DCI formats. For example, when the terminal device 110-1 is configured to have a dynamic beam / TCI state indication, the number of code points within the DCI field "Transmission Configuration Indication" of DCI format 1_2 is expected to be set to 8. For another example, when the terminal device 110-1 is configured to have a dynamic beam / TCI state indication, the number of bits within the DCI field "Transmission Configuration Indication" of DCI format 1_2 is expected to be set to 3 bits.

[0186] In some embodiments, the terminal device 110-1 may receive an activation command via, for example, at least one of RRC, MAC CE, or DCI. Also, the activation command is used to map a combination of a first number of TCI states or a group of a first number of TCI states to a code point in the DCI field "Transmission Configuration Indication". For example, within one CC / BWP or a set of CC / BWPs. In some embodiments, the first number may be represented as N1, and N1 is a positive integer. For example, 1 ≤ N1 ≤ 64. For another example, 1 ≤ N1 ≤ 8. In some embodiments, the group of TCI states may include G TCI states. G is a positive integer. For example, 1 ≤ G ≤ 8. For another example, G may be 1 or 2. For another example, G may be at least one of {1, 2, 3, 4}. In some embodiments, the number of TCI states within a group may be different for different code points. In some embodiments, the number of code points may be Nc. Nc may be 2, 4, or 8. For example, for DCI format 1_1, the number of code points may be 8. For another example, for DCI format 1_2, the number of code points may be 2, 4, or 8 set by the network device. For example, it is performed via RRC.

[0187] In some embodiments, the number of bits for the DCI field "Transmission Configuration Indication" in DCI format 1_1 may be 3 bits. For example, this is the case when the upper layer parameter tci-PresentInDCI is enabled. In some embodiments, the number of bits for the DCI field "Transmission Configuration Indication" in DCI format 1_2 may be set to 1, 2, or 3 bits. For example, this is the case when the upper layer parameter tci-PresentInDCI-1-2 is set. For example, when the number of bits is 1, the number of code points Nc is 2. For another example, when the number of bits is 2, the number of code points Nc is 4. For another example, when the number of bits is 3, the number of code points Nc is 8.

[0188] In some embodiments, the terminal device may have Nc code points set in the DCI field "Transmission Configuration Indication" of DCI format 1_2. In some embodiments, the first (Nc−1) or the last (Nc−1) code points in DCI format 1_2 are applied to indicate the first (Nc−1) TCI states or the first (Nc−1) combinations of N1 groups of TCI states from N1 TCI states or combinations of N1 groups of TCI states. In some embodiments, one of the Nc code points in DCI format 1_2 (e.g., the first one or the last one) may be applied to indicate that the TCI state has not been changed or updated. In some embodiments, one of the Nc code points in DCI format 1_2 (e.g., the first one or the last one) may be applied to indicate the currently or most recently applied, or the currently most recently applied TCI state.

[0189] In some embodiments, the terminal device 110-1 does not expect to be set such that the value of Nc is smaller than the value of N1. In some embodiments, the terminal device 110-1 is expected to be set to have an Nc value that is N1 or greater or greater than N1. For example, Nc≧N1.

[0190] Alternatively, when the DCI field "TCI" does not exist in DCI format 1_2, or when the DCI field "TCI" exists in DCI format 1_2, and the number S of code points in the DCI field "TCI" of DCI format 1_2 is 0 or 1, the terminal device 110-1 may assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied at the time when the PDSCH is scheduled within the active bandwidth part (BWP) of the serving cell (or within a slot / subslot).

[0191] In some embodiments, the terminal device 110-1 may be configured / shown to have a first TCI for receiving all or a subset of the PDSCH and / or CORESET. For example, the first TCI may be applied at the time for the first PDCCH reception (or within a slot / sub-slot). In some embodiments, the terminal device 110-1 may receive or detect DCI in the first PDCCH using the first TCI. In some embodiments, the DCI may be a DCI format that does not have a "Transmission Configuration Indication" field. For example, the DCI may be DCI format 1_0. In some embodiments, the number of bits for the "Transmission Configuration Indication" field in the DCI is 0. For example, the DCI may be DCI format 1_2. In some embodiments, the DCI may schedule the PDSCH. In some embodiments, the terminal device 110-1 may be configured / shown to have a second TCI for receiving all or a subset of the PDSCH and / or CORESET. For example, the second TCI may be applied at the time for the PDSCH reception (or within a slot / sub-slot). In some embodiments, the terminal device 110-1 may receive the PDSCH using the second TCI.

[0192] In some embodiments, the first TCI may be the first DL TCI state, or the first DL TCI state within the first pair of DL / UL TCI states, or the first combined DL / UL TCI state. In some embodiments, the second TCI may be the second DL TCI state, or the second DL TCI state within the second pair of DL / UL TCI states, or the second combined DL / UL TCI state. In some embodiments, the first TCI is different from the second TCI.

[0193] In some embodiments, the terminal device 110-1 may be configured / shown to have a third TCI for receiving all or a subset of PDSCH and / or CORESET. For example, the third TCI is applied at the time (or within a slot / sub-slot) for the first PDCCH reception. In some embodiments, the terminal device 110-1 may receive or detect the first PDCCH using the third TCI. For example, the first PDCCH is within the first CORESET. In some embodiments, the first TCI may be indicated in the first DCI received or detected in the first PDCCH in the terminal device 110-1. In some embodiments, the first DCI may schedule the PDSCH or may not schedule the PDSCH. In some embodiments, the terminal device 110-1 may report the decoding result or the first HARQ-ACK information for at least one of the first DCI or the first PDCCH or the PDSCH scheduled by the first DCI to the network device 120. For example, the decoding result or the first HARQ-ACK information may be transmitted / reported within the first PUCCH or within the first PUSCH. In some embodiments, the terminal device 110-1 may be configured / shown to have a fourth TCI for receiving all or a subset of PUSCH and / or PUCCH. For example, the fourth TCI is applied at the time (or within a slot / sub-slot) for the first PUCCH or the first PUSCH transmission. For example, the terminal device 110-1 may transmit the first PUCCH or the first PUSCH using the fourth TCI.

[0194] In some embodiments, the first application timing for the first TCI may be the first one slot or the first one sub - slot that is X ms or Y symbols after the last symbol of the first PUCCH or the first PUSCH. In some embodiments, the terminal device 110 - 1 may receive all or a subset of PDSCH and / or CORESET using the first TCI from the first one slot or the first one sub - slot, or after the first application timing / from the first application timing. In some embodiments, the terminal device 110 - 1 may transmit all or a subset of PUSCH and / or PUCCH using the first TCI from the first one slot or the first one sub - slot, or after the first application timing / from the first application timing.

[0195] In some embodiments, the terminal device 110 - 1 may not be expected to receive or detect the second PDCCH within a duration. Also, the DCI in the second PDCCH indicates the second TCI. For example, the second TCI is different from the first TCI. In some embodiments, the duration may be between the first or last symbol of the first PUCCH or the first PUSCH and the first symbol of the first application timing or the slot / sub - slot of the first application timing. In some embodiments, the duration may be between the first or last symbol of the first PDCCH and the first symbol of the first application timing or the slot / sub - slot of the first application timing. In some embodiments, the time and / or frequency resources for the second PUCCH or the second PUSCH corresponding to the second PDCCH are different from the time and / or frequency resources for the first PUCCH or the first PUSCH. In some embodiments, the first or last symbol for the second PUCCH or the second PUSCH corresponding to the second PDCCH is before or earlier than the first or last symbol of the first PUCCH or the first PUSCH. For example, the DCI in the second PDCCH may not schedule the PDSCH.

[0196] In some embodiments, the first TCI may be the first DL TCI state within a first pair of the first DL TCI state or the DL / UL TCI state, and the second TCI may be the second DL TCI state within a second pair of the second DL TCI state or the DL / UL TCI state. In some embodiments, the first TCI may be the first UL TCI state within a first pair of the first UL TCI state or the DL / UL TCI state, and the second TCI may be the second UL TCI state within a second pair of the second UL TCI state or the DL / UL TCI state. In some embodiments, the first DL TCI state may be different from the second DL TCI state. In some embodiments, the first UL TCI state may be different from the second UL TCI state. In some embodiments, the first pair of DL / UL TCI states may be different from the second pair of DL / UL TCI states. In some embodiments, the first TCI may be the first combined DL / UL TCI state, and the second TCI may be the second combined DL / UL TCI state. In some embodiments, the first combined DL / UL TCI state may be different from the second combined DL / UL TCI state.

[0197] In other embodiments, for enhanced mobile broadband (eMBB) services and ultra-reliable low latency (URLLC) services, the TCI state may be dynamically indicated or applied. In some embodiments, the terminal device 110-1 may receive the third PDCCH on the first CORESET using the first TCI and the first PDSCH using the first TCI. In this case, the terminal device 110-1 may transmit the first PUCCH to the network device 120 using the first TCI and transmit the first PUSCH to the network device 120 using the first TCI. Additionally, the terminal device 110-1 may receive the fourth PDCCH on the second CORESET using the second TCI and the second PDSCH using the second TCI. In this case, the terminal device 110-1 may transmit the second PUCCH to the network device 120 using the second TCI and transmit the second PUSCH to the network device 120 using the second TCI. For example, the corresponding CORESET for the first PDCCH is set for DCI format 1_1 and / or DCI format 1_0 / 0_1 / 0_0 / 0_2 / 2_0 / 2_1 / 2_2 / 2_3 (DCI format 1_2 is excluded), and the corresponding CORESET for the second PDCCH is set for DCI format 1_2 and / or DCI format 1_0 / 0_1 / 0_0 / 0_2 / 2_0 / 2_1 / 2_2 / 2_3 (DCI format 1_1 is excluded). As another example, the latest applied TCI state from DCI format 1_1 is applied for DCI format 1_0 / 0_1 / 0_0_0_2 / 2_2 / 2_0 / 2_1 / 2_2 / 2_3 and / or the corresponding schedule.

[0198] In some embodiments, when the reception of the first PDCCH and the reception of the second PDCCH are within a duration, the first TCI state and the second TCI state should be the same. In other words, it is expected that the indicated TCI states during the duration are the same. The duration may be of any suitable length. For example, the duration may be 1 slot. Alternatively, for another example, the duration may be a sub-slot. As another example, the duration may be a span for PDCCH monitoring. For another example, the duration may be a PDCCH monitoring occasion.

[0199] Alternatively, there may be a minimum duration between two different indicated TCI states. The minimum duration may be predefined or preconfigured. The minimum duration may be of any suitable length. For example, the minimum duration may be a slot. In this case, when the first PDCCH and the second PDCCH are transmitted within one slot, the first TCI state indicated in the first PDCCH and the second TCI state indicated in the second PDCCH may be the same. When the duration between the transmission of the first PDCCH and the transmission of the second PDCCH is longer than 1 slot, the first TCI state indicated in the first PDCCH and the second TCI state indicated in the second PDCCH may be different.

[0200] In other embodiments, when the first PDCCH indicates the first TCI state, the second PDCCH does not indicate the second TCI state. In other words, the terminal device 110-1 does not expect the second TCI state to be indicated when there is a first TCI applied. For example, the terminal device 110-1 does not expect the second TCI state to be indicated in the second PDCCH within the duration between the first PDCCH having the first TCI state indication and the application timing for the first TCI state. In this example, the resource for HARQ feedback corresponding to the first PDCCH is different from (or later than) the resource for HARQ feedback corresponding to the second PDCCH. The second TCI state may be different from the first TCI state. For example, the second PDCCH does not have data allocation.

[0201] In some embodiments, for the common TCI framework, the TCI state for the PDSCH scheduled by DCI 1_0 may be different from the PDCCH that schedules it. When the PDSCH is scheduled by a DCI format without a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is greater than or equal to the threshold timeDurationForQCL (if applicable), the terminal device 110-1 may assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied at the time when the PDSCH is scheduled within the active BWP of the serving cell (or within a slot / sub-slot). The threshold timeDurationForQCL may be determined based on the reported UE capabilities [13, TS 38.306] for determining PDSCH antenna port quasi-collocation.

[0202] Regarding the application time of the beam indication, the first slot for applying the beam is at least X ms or Y symbols after the last symbol of the confirmation response of the combined or separate DL / UL beam indication. The value of X / Y may depend on the first duration and the second duration. The first duration (which may be represented as Z) may be timeDurationForQCL or beamSwitchTiming, and the second duration (which may be represented as W) may be between the last symbol of the PDCCH for the beam indication and the last symbol of the confirmation response of the beam indication. Here, if Z is smaller than W, the value of X / Y may be 0. Alternatively, if Z is greater than or equal to W, the value of X / Y may be the difference between Z and W.

[0203] In some embodiments, there may be M TRPs serving the terminal device 110-1, where M is a positive integer. For example, 1≤M≤4. For another example, M = 2. In some exemplary embodiments, for each of the M TRPs, the terminal device 110-1 may be configured to have at least one of a control resource set (CORESET), an SRS resource set, a set of spatial relationship information, a transmission configuration indicator (TCI) state, and a QCL parameter set. That is, the terminal device 110-1 may be configured to have M CORESETs, M SRS resource sets, M sets of spatial relationship information, M TCI states, and / or M QCL parameters, each associated with the respective M TRPs. One of the M TRPs may be represented by a corresponding one within the M CORESETs, M SRS resource sets, M sets of spatial relationship information, M TCI states, and / or M QCL parameter sets.

[0204] In some embodiments, the SRS resource set is configured for codebook-based uplink transmission. In some exemplary embodiments, the SRS resource set is configured for non-codebook-based uplink transmission. In some embodiments, the first TRP may be associated with a first set of a first CORESET, a first SRS resource set, first spatial relation information, a first TCI state, and / or QCL parameters, and the second TRP may be associated with a second set of a second CORESET, a second SRS resource set, second spatial relation information, a second TCI state, and / or QCL parameters.

[0205] In some embodiments, the first TRP and the second TRP may correspond to different SRS resource sets. In the following text, the SRS resource set corresponding to the first TRP may be referred to as the first SRS resource set, and the SRS resource set corresponding to the second TRP may be referred to as the second SRS resource set.

[0206] In some embodiments, the DCI for scheduling the PUSCH of the terminal device 110-1 may include a plurality of SRS resource indicator (SRI) fields corresponding to the plurality of SRS resource sets. In some embodiments, the DCI may include two SRI fields. In the following text, the SRI field corresponding to the first SRS resource set may be referred to as the first SRI field, and the SRI field corresponding to the second SRS resource set may be referred to as the second SRI field.

[0207] In some embodiments, codebook-based PUSCH transmission and / or non-codebook-based PUSCH transmission are supported. For the multi-TRP PUSCH repetition pattern based on a single DCI, the non-codebook-based PUSCH transmission may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or parameters set semi-statically, where the DCI or parameters may each include first and second SRI fields corresponding to the first and second SRS resource sets. Additionally, for non-codebook-based PUSCH transmission, the first SRI field may be based on a conventional structure (e.g., the structure defined in Release 15 / 16 of the 3rd Generation Partnership Project (3GPP)) and may be used to indicate, for example, the number of SRS resources, the number of transmission layers (also referred to as "transmission rank"), etc. The second SRI field may indicate only the number of SRS resources, and the number of transmission layers is assumed to be the same as that of the first SRI field.

[0208] Additionally, for non-codebook-based multi-TRP PUSCH transmission, the first SRI field is used to determine an entry in the second SRI field that includes only SRI combinations corresponding to the rank (i.e., the number of layers) indicated by the first SRI field. The number of bits N2 for the second SRI field is determined by the maximum number of code points per rank among all ranks associated with the first SRI field. For each rank x, the first Kx code points are mapped to the Kx SRIs of rank x associated with the first SRI field, and the remaining

Number

[0209] In some exemplary embodiments, when a plurality of SRS resources are configured, the terminal device 110-1 may determine its PUSCH precoder and transmission rank based on the SRI, where the SRI is given by the SRS resource indicator in DCI format 0_1 and DCI format 0_2, or the SRI is given by a higher layer parameter, for example, srs-ResourceIndicator. The SRS-ResourceSet(s) applicable to the PUSCH scheduled by DCI format 0_1 and DCI format 0_2 are defined by the entries of the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 in SRS-config, respectively. The terminal device 110-1 may use one or more SRS resources for SRS transmission, where the maximum number of SRS resources in the SRS resource set and the maximum number of SRS resources that can be configured for the terminal device 110-1 for simultaneous transmission within the same symbol depend on the capabilities of the terminal device 110-1. The SRS resources transmitted simultaneously occupy the same resource block (RB). For each SRS resource, only one SRS port can be configured. One or two SRS resource sets may be configured to have the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook". The maximum number of SRS resources in the SRS resource set that can be configured for non-codebook based uplink transmission may be 4. The SRI indicated within slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission is before the PDCCH carrying the SRI.

[0210] Regarding the M-TRP PUSCH repetition pattern based on a single DCI, PUSCH transmission based on the codebook may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or parameters set semi-statically. The DCI or parameters may each include first and second SRI fields corresponding to the first and second SRS resource sets. Additionally, the DCI may each include two TPMI fields corresponding to the first and second TRPs. The TPMI is used to indicate a precoder corresponding to an SRS resource that is applied in layer {0…ν−1} and selected by the SRI when a plurality of SRS resources are set. Alternatively, when a single SRS resource is set within one SRS resource set, the TPMI is used to indicate a precoder corresponding to the SRS resource that is applied in layer {0…ν−1}. In some exemplary embodiments, the first TPMI field may include a TPMI index and the number of layers, and the second TPMI field may include only the second TPMI index. The same number of layers indicated within the first TPMI field is applied to the second TPMI field.

[0211] Furthermore, regarding multi-TRP PUSCH transmission based on the codebook (CB:codebook based), the first TPMI field is used to determine the entries of the second TPMI field, and the second TPMI field includes only the TPMIs corresponding to the rank (number of layers) indicated by the first TPMI field. The bit width of the second TPMI field is determined by the maximum number of TPMIs per rank among all ranks associated with the first TPMI field. For each rank y, the first K y code points of the second TPMI field are mapped in descending order of the code point index to the K y TPMIs of rank y associated with the first TPMI field, and the remaining

Number

[0212] In some embodiments, the terminal device 110-1 may determine its PUSCH transmission precoder based on the SRI, TPMI, and transmission rank, where the SRI, TPMI, and transmission rank are provided by the DCI fields of the SRS resource indicator, precoding information, and number of layers within DCI formats 0_1 and 0_2, or are provided by upper layer parameters, such as srs-ResourceIndicator and precodingAndNumberOfLayers. The SRS-ResourceSet(s) applicable to the PUSCH scheduled by DCI format 0_1 and DCI format 0_2 are defined by the entries of the upper layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 within SRS-config, respectively. The TPMI is used to indicate the precoder corresponding to the SRS resource selected by the SRI when applied in layers {0…ν−1} and multiple SRS resources are configured. Alternatively, when a single SRS resource is configured, the TPMI is used to indicate the precoder corresponding to the SRS resource applied in layers {0…ν−1}. The transmission precoder is selected from an uplink codebook having the number of antenna ports equal to the upper layer parameter nrofSRS-Ports within SRS-config. When the terminal device 110-1 is configured to have the upper layer parameter txConfig set to "codebook", the terminal device 110-1 may be configured to have at least one SRS resource. The SRI indicated within slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI.

[0213] Additionally, in some exemplary embodiments, the DCI may include a plurality of transmission power control (TPC) fields.

[0214] In some embodiments, the network device 110 may configure a plurality of SRS resource sets (for example, for uplink / PUSCH transmission based on a codebook, the plurality of SRS resource sets may be 1 or 2. For another example, for uplink / PUSCH transmission based on a non-codebook, the plurality of SRS resource sets may be 1 or 2) for the terminal device 110-1 (for example, the first SRS resource set is applied to PUSCH transmission via the first TRP, and the second SRS resource set is applied to PUSCH transmission via the second TRP). In some exemplary embodiments, the network device 110 may configure uplink / PUSCH transmission based on a codebook for the terminal device 110-1, and the network device 110 may configure one or two SRS resource sets for the terminal device 110-1. For example, the one or two SRS resource sets are applied to uplink / PUSCH transmission based on a codebook. In some exemplary embodiments, the network device 110 may configure uplink / PUSCH transmission based on a non-codebook for the terminal device 110-1, and the network device 110 may configure one or two SRS resource sets for the terminal device 110-1. For example, the one or two SRS resource sets are applied to uplink / PUSCH transmission based on a non-codebook. In some exemplary embodiments, the network device 110 may transmit DCI to the terminal device 110-1 to schedule at least one PUSCH transmission. In some exemplary embodiments, the DCI may include a plurality of SRI fields corresponding to a plurality of SRS resource sets. For example, the plurality of SRI fields may include a first SRI field and a second SRI field. Further, or additionally, the DCI may include a plurality of TPMI fields (for example, a first TPMI field and a second TPMI field) for codebook uplink / PUSCH transmission. Further, or additionally, the DCI may include a plurality of TPC fields (for example, a first TPC field and a second TPC field).

[0215] Additionally, dynamic switching between multi-TRP and / or multi-panel and single TRP may be supported. More specifically, when a single TRP transmission having a first TRP is dynamically indicated by DCI, the first SRS resource set is applied for PUSCH transmission. When a single TRP transmission having a second TRP is dynamically indicated by DCI, the second SRS resource set may be applied for PUSCH transmission. Alternatively, when a multi-TRP transmission is dynamically indicated, the first and second SRS resource sets may be applied for PUSCH transmission.

[0216] Additionally, the multi-TRP transmission may be associated with the order of the TRPs (i.e., the order of the multiple SRS resource sets applied for PUSCH transmission). An example of this order is that the terminal device 110-1 applies the first SRS resource set for the first PUSCH transmission / iteration of at least one PUSCH transmission. Another example of this order is that the terminal device 110-1 applies the second SRS resource set for the first PUSCH transmission / iteration of at least one PUSCH transmission.

[0217] In some exemplary embodiments, the terminal device 110-1 may be configured / shown / scheduled to have a set of PUSCH transmissions. The set of PUSCH transmissions may include a first subset of PUSCH transmissions and a second subset of PUSCH transmissions. In some exemplary embodiments, the precoder for the first subset of PUSCH transmissions / iterations may be determined based on at least one of a first SRI indicated by a first SRI field, a first TPMI / PMI field, and a transmission rank. The precoder for the second subset of PUSCH transmissions / iterations may be determined based on at least one of a second SRI indicated by a second SRI field, a second TPMI / PMI field, and a transmission rank.

[0218] In some exemplary embodiments, at least one SRS resource within a first SRS resource set may be applied to or associated with a first subset of PUSCH transmissions, and at least one SRS resource within a second SRS resource set may be applied to or associated with a second subset of PUSCH transmissions. In some exemplary embodiments, a first subset of PUSCH transmissions or a precoder for a first subset of PUSCH transmissions may be based on or corresponding to at least one SRS resource within the first SRS resource set, and a second subset of PUSCH transmissions or a precoder for a second subset of PUSCH transmissions may be based on or corresponding to at least one SRS resource within the second SRS resource set.

[0219] In some embodiments, if there are X SRS resources in a first resource set and Y SRS resources in a second resource set, X and Y are positive integers. For example, 1 ≦ X ≦ 4. For another example, 1 ≦ Y ≦ 4. In some embodiments, X is smaller than Y. In some embodiments, the size of a first SRI field is determined based on the value of X. For example, the number of bits for the first SRI field may be ceil(log2(X)). In some embodiments, the terminal device 110-1 may be set or indicated such that the first SRI field is associated with a second SRS resource set, and if X < Y, the first two ceil(log2(X)) RS resources within the second SRS resource set are indicated by the first SRI field.

[0220] In some embodiments, the terminal device 110-1 may be configured to have uplink transmission based on a codebook. Also, the terminal device 110-1 may be configured to have two SRS resource sets. In some embodiments, the first SRS resource set includes one SRS resource. Also, the second SRS resource set includes two, three, or four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the first SRS resource within the second SRS resource set is assumed or applied. For example, it is an SRS resource with a lower ID value. In some embodiments, the first SRS resource set includes two SRS resources. Also, the second SRS resource set includes three or four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the first two SRS resources within the second SRS resource set are assumed or applied. For example, they are two SRS resources with lower IDs. For example, the number of bits for the first SRI field is 1. For example, when the value of the first SRI field is shown as 0, the first SRS resource within the second SRS resource is assumed or applied. For another example, when the value of the first SRI field is shown as 1, the second SRS resource within the second SRS resource is assumed or applied. In some embodiments, the first SRS resource set includes three SRS resources. Also, the second SRS resource set includes four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the fourth SRS resource within the second SRS resource set is assumed or applied. For example, the number of bits for the first SRI field is 2. For example, when the value of the first SRI field is shown as 00, the first SRS resource within the second SRS resource is assumed or applied.For another example, when the value of the first SRI field is shown as 01, the second SRS resource within the second SRS resource is assumed or applied. For another example, when the value of the first SRI field is shown as 10, the third SRS resource within the second SRS resource is assumed or applied. For another example, when the value of the first SRI field is shown as 11, the fourth SRS resource within the second SRS resource is assumed or applied. For another example, when the terminal device 110-1 is shown to associate the first SRI field with the first SRS resource set, the value of the first SRI field having 11 is reserved.

[0221] In some embodiments, the terminal device 110-1 may be configured to have uplink transmission based on a non-codebook. Also, the terminal device 110-1 may be configured to have two SRS resource sets. In some embodiments, the first SRS resource set includes one SRS resource. Also, the second SRS resource set includes two, three, or four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the first SRS resource within the second SRS resource set is assumed or applied. For example, it is an SRS resource having a lower ID value. In some embodiments, the first SRS resource set includes two SRS resources. Also, the second SRS resource set includes three or four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the first two SRS resources within the second SRS resource set are assumed or applied. For example, they are two SRS resources having lower IDs. For example, the bit field within the first SRI field indicates one or two of the first two SRS resources within the second SRS resource set. In some embodiments, the first SRS resource set includes three SRS resources. Also, the second SRS resource set includes four SRS resources. In some embodiments, when the terminal device 110-1 is indicated to associate the first SRS field with the second SRS resource set, the first three SRS resources within the second SRS resource set are assumed or applied. For example, they are two SRS resources having lower IDs. For example, the bit field within the first SRI field indicates one, two, or three of the first three SRS resources within the second SRS resource set.

[0222] For example, the first SRI field may not be able to indicate all available candidates for the second SRS resource set. For example, for code point 01, the second SRS resource set is applied and the first SRI field is applied. However, there may be some SRS resources that cannot be indicated by the second SRI field. For example, for the codebook (CB), when X is 1 and Y is 2, the first SRI field is 0 bits. Also, for code point 01, the first SRI field is applied for the second SRS resource set. In this case, it is unclear which of the two SRS resources within the second resource set is applied. Therefore, according to some embodiments of the present disclosure, when the number of SRS resources in the first SRS resource set is X, the number of SRS resources in the second SRS resource set is Y, and X is smaller than Y, the first SRI field may be associated with the second SRS resource set. For example, the first 2^X SRS resources from the Y SRS resources may be indicated by the first SRI field. Table 1 below shows an example of the CB first SRI field, where X is 2 and Y is 4.

[0223] Table 1 TIFF0007704226000016.tif19150

[0224] According to Table 1, SRI "0" may indicate the first SRS resource, and SRI "1" may indicate the second SRS resource. Table 2 below shows an example of the NCB first SRI field, where X is 2 and Y is 4.

[0225] Table 2 TIFF0007704226000017.tif31150

[0226] According to Table 2, indexes "0" and "2" may indicate the first SRS resource, and indexes "1" and "2" may indicate the second SRS resource.

[0227] Figure 7 is a flowchart of an exemplary method 700 according to an embodiment of the present disclosure. For illustrative purposes only, method 700 can be implemented in the terminal device 110-1 as shown in FIG. 1.

[0228] At block 710, the terminal device 110-1 receives a first PDCCH from the network device 120. The first PDCCH indicates a first TCI state.

[0229] At block 720, the terminal device 110-1 receives a second PDCCH from the network device 120. The second PDCCH indicates a second first TCI state.

[0230] At block 730, if the reception of the second PDCCH is after the reception of the first PDCCH, the terminal device 110-1 communicates with the network device 120 using a second TCI state after a certain period.

[0231] In some embodiments, the terminal device 110-1 may send a second HARQ feedback corresponding to a second scheduling based on the second PDCCH to the network device 120. Also, the terminal device 110-1 may send a first HARQ feedback corresponding to a first scheduling based on the first PDCCH to the network device 120. If the transmission of the first HARQ feedback is after the transmission of the second HARQ feedback, the terminal device 110-1 may communicate with the network device using the second TCI after that period. In this case, the first scheduling may be a PDSCH scheduling based on the first PDCCH. The second scheduling may be a TCI state indication without a PDSCH scheduling based on the second PDCCH, or may be a PDSCH scheduling based on the second PDCCH. In an exemplary embodiment, if the first TCI is applicable and the second TCI state is not applicable, the terminal device 110-1 may communicate with the network device using the first TCI after that period.

[0232] The first field of the first TCI state in the first PDCCH contains a first number of bits, the second field of the second TCI state in the second PDCCH contains a second number of bits, and when the second number is less than the first number, a predetermined bit value in the second field indicates the first TCI state.

[0233] Alternatively or additionally, the terminal device 110-1 may communicate with the network device using the first TCI. For example, the terminal device 110-1 may receive a third PDCCH from the network device 120 in a first control resource set (CORESET) using the first TCI. Additionally, the terminal device 110-1 may receive a first physical downlink shared channel (PDSCH) from the network device 120 using the first TCI. Additionally or alternatively, the terminal device 110-1 may transmit a first physical uplink control channel (PUCCH) to the network device 120 using the first TCI. Also, the terminal device 110-1 may transmit a first physical uplink shared channel (PUSCH) to the network device 120 using the first TCI.

[0234] In other embodiments, the terminal device 110-1 may receive a fourth PDCCH from the network device 120 in a second control resource set (CORESET) using the second TCI. Alternatively, the terminal device 110-1 may receive a second physical downlink shared channel (PDSCH) from the network device 120 using the second TCI. Additionally, the terminal device 110-1 may transmit a second physical uplink control channel (PUCCH) to the network device 120 using the first TCI. Alternatively or additionally, the terminal device 110-1 may transmit a second physical uplink shared channel (PUSCH) to the network device 120 using the second TCI.

[0235] In some embodiments, if the reception of the first PDCCH and the reception of the second PDCCH are within the duration, the first TCI state is the same as the second TCI state.

[0236] FIG. 8 is a flowchart of an exemplary method 800 according to an embodiment of the present disclosure. For illustrative purposes only, method 800 can be implemented in a terminal device 110-1 as shown in FIG. 1.

[0237] In block 810, the terminal device 110-1 receives a first number of activated transmission configuration indicator (TCI) code points from the network device 120.

[0238] In block 820, the terminal device 110-1 receives the setting of a second number of code points within the downlink control information (DCI) field from the network device 120. The second number is less than the first number, and one predetermined value of the DCI field indicates the same TCI state already applied for communication with the network device.

[0239] Alternatively or additionally, the terminal device 110-1 may communicate with the network device using the first TCI. For example, the terminal device 110-1 may receive a third PDCCH from the network device 120 in a first control resource set (CORESET) using the first TCI. Additionally, the terminal device 110-1 may receive a first physical downlink shared channel (PDSCH) from the network device 120 using the first TCI. Additionally or alternatively, the terminal device 110-1 may transmit a first physical uplink control channel (PUCCH) to the network device 120 using the first TCI. Also, the terminal device 110-1 may transmit a first physical uplink shared channel (PUSCH) to the network device 120 using the first TCI.

[0240] In other embodiments, the terminal device 110-1 may receive a fourth Physical Downlink Control Channel (PDCCH) from the network device 120 in a second Control Resource Set (CORESET) using a second Transmission Configuration Indicator (TCI). Alternatively, the terminal device 110-1 may receive a second Physical Downlink Shared Channel (PDSCH) from the network device 120 using a second TCI. Additionally, the terminal device 110-1 may transmit a second Physical Uplink Control Channel (PUCCH) to the network device 120 using a first TCI. Alternatively or additionally, the terminal device 110-1 may transmit a second Physical Uplink Shared Channel (PUSCH) to the network device 120 using a second TCI.

[0241] FIG. 9 is a flowchart of an exemplary method 900 according to an embodiment of the present disclosure. For illustrative purposes only, method 900 can be implemented in a network device 120-1 as shown in FIG. 1.

[0242] In block 910, the network device 120 transmits a first PDCCH to the terminal device 110-1. The first PDCCH indicates a first TCI state.

[0243] In block 920, the network device 120 transmits a second PDCCH to the terminal device 110-1. The second PDCCH indicates a second TCI state.

[0244] In block 930, if the reception of the second PDCCH is after the reception of the first PDCCH, the network device 120 communicates with the terminal device 110-1 using the second TCI state after a certain period.

[0245] In some embodiments, the network device 120 may receive, from the terminal device 110-1, a second HARQ feedback corresponding to a second scheduling based on a second PDCCH. The network device 120 may receive, from the terminal device 110-1, a first HARQ feedback corresponding to a first scheduling based on a first PDCCH. Additionally, if the reception of the first HARQ feedback is after the reception of the second HARQ feedback, the network device 120 may communicate with the terminal device 110-1 using the second TCI after a certain period. In this case, the first scheduling is PDSCH scheduling based on the first PDCCH, and the second scheduling is a TCI state indication without PDSCH scheduling based on the second PDCCH or PDSCH scheduling based on the second PDCCH.

[0246] Alternatively, if the first TCI is applicable and the second TCI state is not applicable, the network device 120 may communicate with the terminal device using the first TCI after a certain period.

[0247] In some embodiments, if a first field of a first TCI state in a first PDCCH includes a first number of bits, a second field of a second TCI state in a second PDCCH includes a second number of bits, and the second number is less than the first number, a predetermined bit value in the second field indicates the first TCI state.

[0248] Alternatively or additionally, the network device 120 may communicate with the terminal device using the first TCI. For example, the network device 120 may transmit the third PDCCH to the terminal device 110-1 in the first control resource set (CORESET) using the first TCI. Also, the network device 120 may transmit the first physical downlink shared channel (PDSCH) to the terminal device 110-1 using the first TCI. Alternatively or additionally, the network device 120 may receive the first physical uplink control channel (PUCCH) from the terminal device 110-1 using the first TCI. Additionally, the network device 120 may receive the first physical uplink shared channel (PUSCH) from the terminal device 110-1 using the first TCI.

[0249] In other embodiments, the fact that the network device 120 may communicate with the terminal device using the second TCI includes at least one of transmitting the fourth PDCCH to the terminal device in the second control resource set (CORESET) using the second TCI, transmitting the second physical downlink shared channel (PDSCH) to the terminal device using the second TCI, receiving the second physical uplink control channel (PUCCH) from the terminal device using the first TCI, or receiving the second physical uplink shared channel (PUSCH) from the terminal device using the second TCI.

[0250] In some embodiments, if the reception of the first PDCCH and the reception of the second PDCCH are within a continuous time period, the first TCI state is the same as the second TCI state.

[0251] FIG. 10 is a flowchart of an exemplary method 1000 according to an embodiment of the present disclosure. For illustrative purposes only, the method 1000 may be implemented in the network device 120-1 as shown in FIG. 1.

[0252] In block 1010, the network device 120 transmits a first number of activated transmission configuration indicator (TCI) code points to the terminal device 110-1.

[0253] In block 1020, the network device 120 transmits the setting of a second number of code points within the downlink control information (DCI) field to the terminal device 110-1. The second number is less than the first number, and one predetermined value of the DCI field indicates the same TCI state that has already been applied for communication with the network device.

[0254] As an alternative or in addition, the network device 120 may communicate with the terminal device 110-1 using the first TCI. For example, the network device 120 may transmit a third PDCCH to the terminal device 110-1 in a first control resource set (CORESET) using the first TCI. In addition, the network device 120 may transmit a first physical downlink shared channel (PDSCH) to the terminal device 110-1 using the first TCI. In addition or as an alternative, the network device 120 may receive a first physical uplink control channel (PUCCH) from the terminal device 110-1 using the first TCI. The network device 120 may receive a first physical uplink shared channel (PUSCH) from the terminal device 110-1 using the first TCI.

[0255] As an alternative or in addition, the network device 120 may communicate with the terminal device 110-1 using a second TCI. For example, the network device 120 may transmit a fourth PDCCH to the terminal device 110-1 in a second control resource set (CORESET) using a first TCI. In addition, the network device 120 may transmit a second physical downlink shared channel (PDSCH) to the terminal device 110-1 using a second TCI. As an addition or alternative, the network device 120 may receive a second physical uplink control channel (PUCCH) from the terminal device 110-1 using a second TCI. The network device 120 may receive a second physical uplink shared channel (PUSCH) from the terminal device 110-1 using a second TCI.

[0256] In some embodiments, the terminal device comprises a circuit, and the circuit receives a first physical downlink control channel (PDCCH) indicating a first transmission configuration indicator (TCI) state from a network device, receives a second PDCCH indicating a second TCI state from the network device, and is configured to communicate with the network device using the second TCI state after a certain period according to a determination that the reception of the second PDCCH is after the reception of the first PDCCH.

[0257] In some embodiments, the terminal device comprises a circuit, and the circuit is further configured to transmit a second hybrid automatic repeat request (HARQ) feedback corresponding to a second scheduling based on the second PDCCH to the network device, and transmit a first HARQ feedback corresponding to a first scheduling based on the first PDCCH to the network device. The terminal device comprises a circuit, and the circuit is configured to communicate with the network device using the second TCI state by communicating with the network device using the second TCI after the certain period according to a determination that the transmission of the first HARQ feedback is after the transmission of the second HARQ feedback.

[0258] In some embodiments, the first scheduling is PDSCH scheduling based on a first PDCCH, and the second scheduling is a TCI state indication without PDSCH scheduling based on a second PDCCH or PDSCH scheduling based on a second PDCCH.

[0259] In some embodiments, the terminal device includes a circuit, and the circuit is further configured to perform the communication with the network device using the first TCI after a certain period according to a determination that the first TCI is applicable and the second TCI state is not applicable.

[0260] In some embodiments, a first field of a first TCI state in a first PDCCH includes a first number of bits, a second field of a second TCI state in a second PDCCH includes a second number of bits, and when the second number is less than the first number, a predetermined bit value in the second field indicates the first TCI state.

[0261] In some embodiments, the terminal device includes a circuit, and the circuit is further configured to perform the communication with the network device using the first TCI. In some embodiments, the terminal device includes a circuit, and the circuit is further configured to receive a third PDCCH from the network device in a first control resource set (CORESET) using the first TCI, receive a first physical downlink shared channel (PDSCH) from the network device using the first TCI, transmit a first physical uplink control channel (PUCCH) to the network device using the first TCI, or transmit a first physical uplink shared channel (PUSCH) to the network device using the first TCI, and is configured to perform the communication with the network device using the first TCI by at least one of the above.

[0262] In some embodiments, the terminal device comprises a circuit, and the circuit is further configured to receive, from the network device, a fourth Physical Downlink Control Channel (PDCCH) in a second Control Resource Set (CORESET) using the second Transmission Configuration Indicator (TCI), receive, from the network device, a second Physical Downlink Shared Channel (PDSCH) using the second TCI, transmit, to the network device, a second Physical Uplink Control Channel (PUCCH) using the first TCI, or transmit, to the network device, a second Physical Uplink Shared Channel (PUSCH) using the second TCI, so as to perform the communication with the network device using the second TCI by at least one of the above.

[0263] In some embodiments, when the reception of the first PDCCH and the reception of the second PDCCH are within a continuous time period, the first TCI state is the same as the second TCI state.

[0264] In some embodiments, the terminal device comprises a circuit, and the circuit is configured to receive, from the network device, a first number of activated Transmission Configuration Indicator (TCI) code points, and receive, from the network device, a setting of a second number of code points within a Downlink Control Information (DCI) field, where the second number is less than the first number, and one predetermined value of the DCI field indicates the same TCI state that has already been applied to the communication with the network device.

[0265] In some embodiments, the terminal device includes a circuit, and the circuit is further configured to perform the communication with the network device using the TCI state. In some embodiments, the terminal device includes a circuit, and the circuit is further configured to receive, from the network device, a Physical Downlink Control Channel (PDCCH) in a Control Resource Set (CORESET) using the TCI state, receive a Physical Downlink Shared Channel (PDSCH) from the network device using the TCI state, transmit a Physical Uplink Control Channel (PUCCH) to the network device using the TCI state, or transmit a Physical Uplink Shared Channel (PUSCH) to the network device using the TCI state. The circuit is configured to perform the communication with the network device using the TCI state by at least one of the above operations.

[0266] In some embodiments, the network device includes a circuit, and the circuit is configured to transmit a first Physical Downlink Control Channel (PDCCH) indicating a first Transmission Configuration Indicator (TCI) state to a terminal device, transmit a second PDCCH indicating a second TCI state to the terminal device, and according to a determination that reception of the second PDCCH is after reception of the first PDCCH, be configured to perform communication with the terminal device using the second TCI state after a certain period.

[0267] In some embodiments, the network device includes a circuit, and the circuit is configured to receive, from the terminal device, a second hybrid automatic repeat request (HARQ) feedback corresponding to a second scheduling based on the second PDCCH, and a first HARQ feedback corresponding to a first scheduling based on the first PDCCH. In some embodiments, the network device includes a circuit, and the circuit is configured to, according to a determination that reception of the first HARQ feedback is after reception of the second HARQ feedback, after a certain period, communicate with the terminal device using the second TCI state by communicating with the terminal device using the second TCI.

[0268] In some embodiments, the first scheduling is PDSCH scheduling based on a first PDCCH, and the second scheduling is a TCI state indication without PDSCH scheduling based on a second PDCCH or PDSCH scheduling based on a second PDCCH.

[0269] In some embodiments, the network device includes a circuit, and the circuit is configured to, according to a determination that the first TCI is applicable and the second TCI state is not applicable, after a certain period, communicate with the terminal device using the first TCI.

[0270] In some embodiments, a first field of a first TCI state in a first PDCCH includes a first number of bits, a second field of a second TCI state in a second PDCCH includes a second number of bits, and when the second number is less than the first number, a predetermined bit value in the second field indicates the first TCI state.

[0271] In some embodiments, the network device includes a circuit, and the circuit is configured to communicate with the terminal device using the first TCI. In some embodiments, the network device includes a circuit, and the circuit is configured to transmit a third PDCCH to the terminal device in a first control resource set (CORESET) using the first TCI, transmit a first physical downlink shared channel (PDSCH) to the terminal device using the first TCI, receive a first physical uplink control channel (PUCCH) from the terminal device using the first TCI, or receive a first physical uplink shared channel (PUSCH) from the terminal device using the first TCI. The circuit is configured to communicate with the terminal device using the first TCI by at least one of the above.

[0272] In some embodiments, the network device includes a circuit, and the circuit is configured to transmit a fourth PDCCH to the terminal device in a second control resource set (CORESET) using the second TCI, transmit a second physical downlink shared channel (PDSCH) to the terminal device using the second TCI, receive a second physical uplink control channel (PUCCH) from the terminal device using the first TCI, or receive a second physical uplink shared channel (PUSCH) from the terminal device using the second TCI. The circuit is configured to communicate with the terminal device using the second TCI by at least one of the above.

[0273] In some embodiments, when the reception of the first PDCCH and the reception of the second PDCCH are within a continuous time period, the first TCI state is the same as the second TCI state.

[0274] In some embodiments, the network device includes a circuit, and the circuit is configured to transmit a first number of activated transmission configuration indicator (TCI) code points to a terminal device and transmit a configuration of a second number of code points within a downlink control information (DCI) field to the terminal device, where the second number is less than the first number, and one predetermined value of the DCI field indicates the same TCI state that has already been applied for communication with the network device.

[0275] In some embodiments, the network device includes a circuit, and the circuit is configured to communicate with the terminal device using the TCI state. In some embodiments, the network device includes a circuit, and the circuit is configured to communicate with the terminal device using the TCI state by at least one of transmitting a physical downlink control channel (PDCCH) to the terminal device in a control resource set (CORESET) using the TCI state, transmitting a physical downlink shared channel (PDSCH) to the terminal device using the TCI state, receiving a physical uplink control channel (PUCCH) from the terminal device using the TCI state, or receiving a physical uplink shared channel (PUSCH) from the terminal device using the TCI state.

[0276] FIG. 11 is a schematic block diagram of an apparatus 1100 suitable for implementing embodiments of the present disclosure. Apparatus 1100 can be considered as another exemplary embodiment of the network device 120 or the terminal device shown in FIG. 1. Thus, apparatus 1100 can be implemented in a terminal device 110 or a network device 120, or as at least a part thereof.

[0277] As shown in the figure, the apparatus 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX / RX 1140. The memory 1110 stores at least a part of the program 1130. The TX / RX 1140 is used for two-way communication. The TX / RX 1140 has at least one antenna to facilitate communication, but the access node mentioned in this specification may actually have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 interface for two-way 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.

[0278] The program 1130 is assumed to include program instructions that enable the apparatus 1100 to operate in accordance with the embodiments of the present disclosure when executed by the associated processor 1110, as described herein with reference to FIGS. 2 to 10. The embodiments herein may be realized by computer software executable by the processor 1110 of the apparatus 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present disclosure. Further, the combination of the processor 1110 and the memory 1020 may form processing means suitable for realizing various embodiments of the present disclosure.

[0279] Memory 1120 may be of any type suitable for a local technology network, and by way of non-limiting example, may be implemented using any suitable data storage technology such as a non-transitory computer-readable storage medium, a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, a fixed memory, and a removable memory. Although only one memory 1120 is shown within apparatus 1000, there may be several physically different memory modules within apparatus 1000. Processor 1110 may be of any type suitable for a local technology network, and by way of non-limiting example, may include one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Apparatus 1100 may have a specific-purpose integrated circuit chip that is temporally dependent on a clock that synchronizes a plurality of processors, such as a main processor.

[0280] Overall, various embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, 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, a microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are 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, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0281] 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 are executed within an apparatus on a target physical processor or virtual processor to perform the processes or methods described above with reference to FIGS. 2 to 10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of the program modules may be combined or divided among the program modules as needed. The machine-executable instructions of the program modules may be executed within a local or distributed apparatus. In a distributed apparatus, the program modules may be located in both local and remote storage media.

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

[0283] The above program code may be implemented on a machine-readable medium, which may be any tangible medium that can be utilized by or associated with an instruction execution system, apparatus, or device and that can contain or store a program for use by or in connection with the same. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing media. More specific examples of the machine-readable storage medium may include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0284] Note that although the operations have been described in a particular order, it should be understood that such operations may be performed in the particular order shown or in a sequential order, or that all of the operations described may be required to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while some specific implementation details have been included in the above discussion, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some of the features described in the context of individual embodiments may be combined in a single embodiment to be realized. Conversely, the various features described in the context of a single embodiment may be implemented separately in multiple embodiments or in any suitable sub-combination.

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

Claims

Means for receiving information regarding two or more transmission configuration indicator (TCI) states Means for transmitting a physical uplink control channel (PUCCH) having a positive hybrid automatic repeat request acknowledgment (HARQ-ACK), or a physical uplink shared channel (PUSCH) having the positive HARQ-ACK comprising The two or more TCI states are different from the previously indicated TCI states The two or more TCI states are applied from a first slot, and the first slot is a duration of at least one or more symbols after the last symbol of the PUCCH or the PUSCH One of the two or more TCI states carried by the latest downlink control information (DCI) at a time corresponding to the positive HARQ-ACK is applied from the first slot Terminal device One of the two or more TCI states is one of a downlink (DL) TCI state, an uplink (UL) TCI state, or a combined DL / UL TCI state The terminal device according to claim 1 The format for the DCI includes DCI format 1_1 or DCI format 1_2 The terminal device according to claim 1 The duration is set via radio resource control (RRC) signaling The terminal device according to claim 1 The number of the one or more symbols within the duration is 1 or more and 336 or less The terminal device according to claim 1 Means for transmitting information regarding two or more transmission configuration indicator (TCI) states Means for receiving a physical uplink control channel (PUCCH) having a positive hybrid automatic repeat request acknowledgment (HARQ-ACK), or a physical uplink shared channel (PUSCH) having the positive HARQ-ACK comprising The two or more TCI states are different from the previously indicated TCI states The two or more TCI states are applied from a first slot, and the first slot is a duration of at least one or more symbols after the last symbol of the PUCCH or the PUSCH ​ ​ ​ ​ One of the two or more TCI states carried by the latest downlink control information (DCI) at the time corresponding to the positive HARQ-ACK is applied from the first slot. Network device. **Claim 7** One of the one TCI state among the two or more TCI states is one of a downlink (DL) TCI state, an uplink (UL) TCI state, or a combined DL / UL TCI state. The network device according to claim 6. **Claim 8** The duration is set via radio resource control (RRC) signaling. The network device according to claim 6. **Claim 9** The number of the one or more symbols within the duration is 1 or more and 336 or less. The network device according to claim 6. **Claim 10** A method executed by a terminal device, comprising: Receiving information regarding two or more transmission configuration indicator (TCI) states; Transmitting a physical uplink control channel (PUCCH) having a positive hybrid automatic repeat request acknowledgment (HARQ-ACK), or a physical uplink shared channel (PUSCH) having the positive HARQ-ACK; including The two or more TCI states are different from the previously indicated TCI states; The two or more TCI states are applied from a first slot, and the first slot is a duration of at least one or more symbols after the last symbol of the PUCCH or the PUSCH; One of the two or more TCI states carried by the latest downlink control information (DCI) at the time corresponding to the positive HARQ-ACK is applied from the first slot. Method. **Claim 11** A method executed by a network device, comprising: Transmitting information regarding two or more transmission configuration indicator (TCI) states; Receiving a physical uplink control channel (PUCCH) having a positive hybrid automatic repeat request acknowledgment (HARQ-ACK), or a physical uplink shared channel (PUSCH) having the positive HARQ-ACK; including The two or more TCI states are different from the previously indicated TCI states; The above two or more TCI states are applied from a first slot, and the first slot is a duration of at least one or more symbols after the last symbol of the PUCCH or the PUSCH, One of the above two or more TCI states carried by the latest downlink control information (DCI) at a time corresponding to the positive HARQ-ACK is applied from the first slot, Method.

Images