Terminal device, network device, terminal device communication method, and network device communication method

Abstract

The embodiments of the present disclosure relate to a communication method, an apparatus, and a computer storage medium. According to the embodiments of the present disclosure, a terminal device transmits, to a network device, first Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information corresponding to a first Downlink Control Information (DCI) in a first Physical Downlink Control Channel (PDCCH), where the first DCI indicates a first Transmission Configuration Indicator (TCI) state. If a condition is met, the terminal device applies the first TCI state. In this way, the terminal device can know when and / or whether to apply the indicated TCI state.

Description

[Technical field]

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

[0002] In the RAN#86 meeting of the 3rd Generation Partnership Project (3GPP), it has been agreed to support enhancements for multi-beam operation, mainly targeting Frequency Range 2 (FR2) but also applicable to Frequency Range 1 (FR1). It has been agreed to identify and specify features to facilitate more efficient (lower latency and overhead) downlink (DL) and uplink (UL) beam management. For example, it has been proposed to support common beams for transmission and reception of data and control information for DL ​​and UL, especially for intra-band carrier aggregation (CA). It has also been proposed to support a unified Transmission Configuration Indication (TCI) framework for DL ​​and UL beam indication. However, the current 3GPP specification does not provide details on when to apply the indicated TCI states. Summary of the Invention [Problem to be solved by the invention]

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

[0004] In a first aspect, a method of communication is provided, the method including: transmitting, in a terminal device, to a network device, first Hybrid Automatic Repeat request - ACKnowledgement (HARQ-ACK) information corresponding to first Downlink Control Information (DCI) in a first Physical Downlink Control CHannel (PDCCH), the first DCI indicating a first Transmission Configuration Indicator (TCI) state.

[0005] In a second 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 perform the following operations: transmitting, in the terminal device, to a network device, first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to first downlink control information (DCI) in a first physical downlink control channel (PDCCH), where the first DCI indicates a first transmission configuration indicator (TCI) state.

[0006] In a third aspect, a computer readable medium is provided having instructions stored thereon that, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect above.

[0007] In a fourth aspect, there is provided a computer program product stored on a computer readable medium and including machine executable instructions that, when executed, cause a machine to perform a method according to the first aspect above.

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

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

[0010] [Figure 1] FIG. 1 illustrates an exemplary communications network in which embodiments of the present disclosure may be implemented.

[0011] [Diagram 2] FIG. 2 is a signaling diagram for signaling communication in accordance with some embodiments of the present disclosure.

[0012] [Diagram 3] FIG. 1 is a schematic diagram of an out-of-order hybrid automatic repeat request (HARQ) in accordance with some embodiments of the present disclosure.

[0013] [Figure 4] 1 is a flowchart of an exemplary method according to an embodiment of the present disclosure.

[0014] [Diagram 5] 1 is a flowchart of an exemplary method according to an embodiment of the present disclosure.

[0015] [Figure 6] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0016] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0019] As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "some embodiments" and "embodiments" should be understood as "at least some embodiments." The term "another embodiment" should be understood as "at least one other embodiment." Terms such as "first," "second," and the like may refer to different or the same object. The following may include other explicit and implicit definitions.

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

[0021] In the 3GPP RAN#86 meeting, it has been agreed to support enhancements for multi-beam operation, mainly targeted at FR2 but also applicable to FR1. It has been agreed to identify and specify features to facilitate more efficient (lower latency and overhead) DL and UL beam management. For example, it has been proposed to support common beams for transmission and reception of data and control information for DL ​​and UL, especially for in-band CA. It has also been proposed to support a unified TCI framework for DL ​​and UL beam indication. However, the current 3GPP specification does not provide details on when to apply the indicated TCI states. For example, it is not clear how to address out-of-order HARQ. It is also unclear whether to apply the indicated TCI states.

[0022] In order to solve at least the above and / or potential problems, a solution for beam management is proposed. According to an embodiment of the present disclosure, a terminal device transmits to a network device first Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information corresponding to a first Downlink Control Information (DCI) in a first Physical Downlink Control Channel (PDCCH), the first DCI indicating a first Transmission Configuration Indicator (TCI) state. If a condition is met, the terminal device applies the first TCI state. Thus, the terminal device understands when and / or whether to apply the indicated TCI state.

[0023] FIG. 1 illustrates an exemplary communication network 100 in which embodiments of the present disclosure may be implemented. As illustrated in FIG. 1, the network 100 includes a network device 110. For example, the network device 110 may be configured to have two TRPs / panels 120-1 and 120-2 (collectively or individually referred to as TRPs 120). The network 100 further includes a terminal device 130 served by the network device 110. It should be understood that the number of network devices, terminal devices, and TRPs illustrated in FIG. 1 are for illustrative purposes only and no limitation to the present disclosure is implied. The network 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure.

[0024] As used herein, the term "terminal device" refers to 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, Internet of Everything (IoE) devices, Machine Type Communication (MTC) devices, Ultra-Reliable Low latency Communication (URLLC) devices, in-vehicle devices for V2X communication, etc., where the "X" in V2X represents a pedestrian, vehicle or infrastructure / network, or an image capture device such as a digital camera, a gaming device, a music storage and playback device, or an Internet appliance that allows wireless or wired Internet access and browsing. For the purposes of explanation, some embodiments will be described below with reference to a UE as an example of a terminal device 130.

[0025] The term "network equipment" or "base station" (BS) as used herein means equipment capable of providing or hosting a cell or coverage within which terminal equipment can communicate. Examples of network equipment 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. The term "TRP" means an antenna array (having one or more antenna elements) available to a network equipment located at a particular geographical location. For example, a network equipment may be coupled to multiple TRPs at different geographical locations to achieve better coverage. It should be understood that a TRP may be referred to as a "panel", which may refer to an antenna array (having one or more antenna elements) or a group of antennas.

[0026] In one embodiment, the terminal device 130 may be connected to a first network device and a second network device (not shown in FIG. 1). One of the first network device and the second network device may be in a master node and the other in 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 may be an eNB and the second RAT device is a gNB. Information about the different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 130. In one embodiment, the first information may be transmitted from the first network device to the terminal device 130, and the second information may be transmitted from the second network device to the terminal device 130 directly or via the first network device. In one embodiment, information regarding the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device configured by the second network device may be transmitted to the terminal device directly from the second network device or via the first network device. This information may be transmitted via any of Radio Resource Control (RRC) signaling, Media Access Control (MAC) control elements (CE), or Downlink Control Information (DCI).

[0027] In the communication network 100, the network device 110 can communicate data and control information to the terminal device 130, and the terminal device 130 can also communicate data and control information to the network device 110. The link from the network device 110 to the terminal device 130 is called the downlink (DL), and the link from the terminal device 130 to the network device 110 is called the uplink (UL).

[0028] Communications in network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), and the like. Additionally, communications may be performed according to any generation of communication protocols now known or developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols.

[0029] 1, the network device 110 may communicate with the terminal device 130 via TRPs 120-1 and 120-2. In the following text, the TRP 120-1 may be referred to as a first TRP, and the TRP 120-2 may be referred to as a second TRP. Each of the TRPs 120 may provide multiple beams for communicating with the terminal device 130.

[0030] In some embodiments, the first and second TRPs 120 may be explicitly associated with different higher layer configured identities. For example, the higher layer configured identities may be associated with a control resource set (CORESET), reference signal (RS), or transmission configuration indication (TCI) state used to distinguish transmissions between different TRPs 120 and the terminal device 130. When the terminal device 130 receives two DCIs in two CORESETs associated with different higher layer configured identities, the two DCIs are indicated from different TRPs. Furthermore, the first and second TRPs 120 may be implicitly identified by dedicated configuration to physical channels or signals. For example, a dedicated CORESET, RS, and TCI state associated with the TRPs are used to distinguish transmissions to the terminal device 130 from different TRPs. For example, when the terminal device 130 receives a DCI from a dedicated CORESET, the DCI is indicated from the associated TRP dedicated to the CORESET.

[0031] In the repeated transmission or reception via the two TRPs 120, the network device 110 may select a repetition scheme from among multiple available repetition schemes. The repetition scheme may specify a transmission method for the network device 110 to use the two TRPs 120 in a coordinated manner, such as a multiplexing scheme between the two TRPs 120 and respective resource allocation for the two TRPs 120.

[0032] For example, the scheme for multi-TRP / multi-panel based URLLC scheduled by at least a single downlink control information (DCI) may be as follows:

[0033] Method 1 (SDM: Space Division Multiplexing): n (n≦N s) TCI states, and there are overlapping time and frequency resource allocations.

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

[0035] Scheme 1b: Each transmission opportunity is a layer or set of layers of the same 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 RV corresponding to each spatial layer or set of layers may be the same or different. For total number of layers≦4, the mapping of codewords to layers is for further study.

[0036] Scheme 1c: One transmission opportunity is one layer of the same TB with one DMRS port associated with multiple TCI state indexes, or one layer of the same TB with multiple DMRS ports associated one-to-one with multiple TCI state indexes.

[0037] Additionally, it is shown that it is also possible to apply different MCS / modulation orders to different layers or sets of layers.

[0038] Method 2 (FDM: Frequency Division Multiplexing): n (n≦N f ) TCI states, with non-overlapping frequency resource allocations. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single / multiple DMRS ports are associated with all the non-overlapping frequency resource allocations.

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

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

[0041] Additionally, it is shown that it is possible to discuss the application of different MCS / modulation orders for different non-overlapping frequency resource allocations. It is also shown that the details of the frequency resource allocation mechanism for FDM 2a / 2b, in terms of allocation granularity, time domain allocation, etc., can be discussed.

[0042] Method 3 (TDM (Time Division Multiplexing) or intra-slot repetition): n (n≦N t1) TCI states, and there are non-overlapping time resource allocations. Each transmission opportunity in a TB has one TCI and one RV, and the time granularity is a minislot. All transmission opportunities in a slot use a common MCS with the same single or multiple DMRS ports. The RV / TCI states may be the same or different between transmission opportunities. Channel estimate interpolation across minislots with the same TCI index is a topic for further study. In some embodiments, the terminal device may be configured or set to have TDMschemeA by higher layer parameters. For example, the higher layer parameters may be RRC parameters. For example, the higher layer parameters are URLLCSchemeEnabler.

[0043] Method 4 (TDM or slot repetition): n (n ≤ N t2 ) TCI states and K (n≦K) different slots. Each transmission opportunity in TB has one TCI and one RV. All transmission opportunities 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 between transmission opportunities. Channel estimate interpolation across slots with the same TCI index is a topic for future research.

[0044] In some embodiments, before transmitting data to the terminal device 130 (e.g., via TRP 120-1 and / or 120-2), the network device 110 may transmit control information associated with the transmission of the data. For example, the control information may schedule a set of resources for the data transmission and indicate various transmission parameters related to the data transmission defined in the 3GPP specifications, such as one or more TCI states, Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), which may include slot offset and start / length indicator values, Demodulation Reference Signal (DMRS) group, Redundancy Version (RV). It should be understood that the transmission parameters indicated in the control information 135 are not limited to those listed above. The embodiments of the present disclosure may be equally applicable to control information including any transmission parameters.

[0045] In the following, the terms "transmission opportunity", "reception opportunity", "repetition", "transmission", "reception", "PDSCH transmission opportunity", "PDSCH repetition", "PUSCH transmission opportunity", "PUSCH repetition", "PUCCH opportunity", "PUCCH repetition", "repetitive transmission", "repetitive 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 parameters", "QCL assumption" and "QCL setting" may be used interchangeably. The terms "TCI field", "TCI state field" and "transmission setting indication" may be used interchangeably. The terms "transmission opportunity", "transmission", "repetition", "reception", "reception opportunity", "monitoring opportunity", "PDCCH monitoring opportunity", "PDCCH transmission opportunity", "PDCCH transmission", "PDCCH candidate", "PDCCH reception opportunity", "PDCCH reception", "search space", "CORESET", "multiple chances", and "PDCCH repetition" may be used interchangeably. In the following, the terms "PDCCH repetition", "repeated PDCCH", "repeated PDCCH signal", "PDCCH candidate configured for the same scheduling", "PDCCH", "PDCCH candidate" and "linked PDCCH candidate" 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, and in the following, PDSCH scheduling is described as an example. For example, the embodiments of the present disclosure may be applied to PUSCH by replacing "transmit" with "receive" and / or "receive" with "transmit". The terms "PDSCH" and "PUSCH" may be used interchangeably. The terms "transmit" and "receive" may be used interchangeably.The terms "common beam", "common beam update / indication", "unified TCI state", "unified TCI state update / indication", "beam indication", "TCI state indication", "TCI_state_r17", "tci_StateId_r17", "TCI_state_r17 indicating unified TCI state", "TCI state shared / applied for all or a subset of CORESET on PDSCH and UE-dedicated reception", "Rel-17 TCI state", "TCI state with tci_StateId_r17", "TCI state configured for TCI state update in unified TCI framework", "TCI state indicated in DCI for common beam update / indication", "TCI state indicated in DCI and applied to all / subset of CORESET and PDSCH" may be used interchangeably. The terms "subset of CORESET", "subset of TCI states", "subset of unified TCI states", "subset of downlink (unified) TCI states", and "subset of combined (unified) TCI states" may be used interchangeably. The terms "subset of PUCCH," "subset of TCI states," "subset of unified TCI states," "subset of uplink (unified) TCI states," and "subset of combined (unified) TCI states" may be used interchangeably.

[0046] As specified in the 3GPP specification (TS 38.214), a UE is configured with a list of up to T TCI state configurations in the higher layer parameter PDSCH-Config to be able to decode PDSCH from a detected PDCCH with DCI targeted for the UE and a given serving cell, where T depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI state includes parameters for setting up a quasi-co-location relationship between one or two downlink reference signals and a DMRS port of the PDSCH, a DMRS port of the PDCCH, or a Channel State Information-Reference Signal (CSI-RS) port of a CSI-RS resource. The quasi-co-location relationship is set by the higher layer parameters qcl-Type1 of the first downlink (DL) RS and qcl-Type2 of the second DL RS (if configured). For two DL RSs, the QCL types must not be the same whether they refer 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}

[0047] The UE receives an activation command according to clause "TCI state activation / deactivation for a UE specific PDSCH MAC CE" (e.g. clause 6.1.3.14) of TS 38.321 or clause "Extended TCI state activation / deactivation for a UE specific PDSCH MAC CE" (e.g. clause 6.1.3) of TS 38.321, which is used to map up to eight TCI states to code points of the DCI field "Transmission Configuration Indication" within one CC / DL BWP or within a set of CC / DL BWPs, respectively. If a set of TCI state IDs is activated for a set of CC / DL BWPs where the available list of CCs is determined by the indicated CC in the activation command, the same set of TCI state IDs applies for all DL BWPs within the indicated CC.

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

[0049] If DCI format 1_2 has a DCI field "Transmission Configuration Indication" 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 applied for DCI format 1_2 as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321].

[0050] If the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying an activation command, the indicated mapping between the TCI state and the codepoint of the DCI field "Transmission Configuration Indication" is The SCS setting for PUCCH shall be applied from the first slot after TIFF2025503561000002.tif634, where is the SCS setting for PUCCH. If tci-PresentInDCI is set to "enabled" or tci-PresentDCI-1-2 is configured for a CORESET scheduling a PDSCH and the time offset between reception of DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL (if applicable), after the UE has received the initial higher layer configuration of the TCI state and before receiving the activation command, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the SS / PBCH block determined in the first access procedure for qcl-Type set to "typeA" and, if applicable, also for qcl-Type set to "typeD".

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

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

[0053] If the UE is configured with the higher layer parameter tci-PresentInDCI set to "enabled" for the CORESET scheduling the PDSCH, the UE shall assume that a TCI field is present in the DCI of the PDCCH transmitted on the CORESET (e.g., DCI format 1_1). If the UE is configured with the higher layer parameter tci-PresentInDCI-ForFormat1_2 for the CORESET scheduling 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 on the CORESET (e.g., DCI format 1_2). If a PDSCH is scheduled with a DCI format in which the TCI field is not present and the time offset between reception of the DL DCI and the corresponding PDSCH is greater than or equal to a threshold timeDurationForQCL (if applicable) based on the reported UE capabilities [TS 38.306] for determining PDSCH antenna port quasi-co-location, 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.

[0054] If the PDSCH is scheduled with a DCI format in which the TCI field is present and the TCI field in the DCI in the scheduling component carrier points to an activated TCI state in the scheduling component carrier or DL ​​BWP, the UE shall determine the PDSCH antenna port quasi-co-location using the TCI state according to the value of the "Transmission Configuration Indication" field in the detected PDCCH with DCI. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL based on the reported UE capabilities [TS 38.306], the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS in the TCI state with respect to the QCL type parameter given by the indicated TCI state. If the UE is configured to have a single-slot PDSCH, the indicated TCI state shall be based on the activated TCI state in the slot with 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 in the first slot that has a scheduled PDSCH, and the UE should want the activated TCI state to be the same across slots that have a scheduled PDSCH.If a UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and a PDCCH carrying a scheduling DCI and a PDSCH scheduled by the DCI are transmitted on the same carrier, the UE expects tci-PresentInDCI to be set to 'enabled' or tci-PresentInDCI-ForFormat1_2 to be configured for CORESET, and if one or more of the TCI states configured for the serving cells scheduled by the search space set include 'QCL-TypeD', the UE expects the time offset between reception of a detected PDCCH in the search space set and the corresponding PDSCH to be greater than or equal to a threshold timeDurationForQCL.

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

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

[0057] If the UE is configured with enableDefaultTCIStatePerCoresetPoolIndex and the UE is configured with higher layer parameter PDCCH-Config that includes two different coresetPoolIndex values ​​in different ControlResourceSets,

[0058] The UE may assume that the DM-RS port of the PDSCH associated with the value of coresetPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameters used for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space with the lowest controlResourceSetId among the CORESETs configured to have the same coresetPoolIndex value as the PDCCH scheduling the PDSCH in the last slots where one or more CORESETs associated with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH in the active BWP of the serving cell are monitored by the UE. In this case, the UE is expected to prioritize the reception of the PDCCH associated with the CORESET if the "QCL-TypeD" of the PDSCH DM-RS overlaps in at least one symbol and is different from that of the PDCCH DM-RS associated with the same coresetPoolIndex. This also applies in the case of intra-band CA (when the PDSCH and CORESET are in different component carriers).

[0059] If the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS port of the PDSCH of the serving cell or the PDSCH transmission opportunity is quasi-co-located with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint of the TCI codepoints containing two different TCI states. If the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or configured with the higher layer parameter repetitionNumber, it determines the mapping of TCI states to PDSCH transmission opportunities according to clause 5.1.2.1 based on the activated TCI states in the slot with the first PDSCH transmission opportunity by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint of the TCI codepoints containing two different TCI states. In this case, the UE is expected to prioritize the reception of the PDCCH associated to the CORESET if the "QCL-TypeD" in both TCI states corresponding to the lowest codepoint of the TCI codepoints containing two different TCI states differs from that of the overlapping PDCCH DM-RS within at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are in different component carriers).

[0060] 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 qcl-Type set to "typeD", the UE should derive other QCL assumptions from the indicated TCI state for the scheduled PDSCH, regardless of the time offset between reception of the DL DCI and the corresponding PDSCH.

[0061] If a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by the DCI is on another component carrier, and the UE is configured with enableDefaultBeam-ForCCS, - timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μ PDCCH <μ PDSCH If so, additional timing delay TIFF2025503561000003.tif1019 is added to timeDurationForQCL, where d is defined in 5.2.1.5.1a-1 or d is zero. - In both cases, if the offset between reception of the DL DCI and the corresponding PDSCH is smaller than the threshold timeDurationForQCL, and if the TCI field is not present in the DL DCI, the UE derives 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.

[0062] For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE should expect the TCI-State to indicate one of the following quasi-co-location types: - "typeC" with SS / PBCH blocks and, if applicable, "typeD" with the same SS / PBCH blocks, or - "type C" with SS / PBCH blocks and, if applicable, "type D" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0063] For aperiodic CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the UE should expect the TCI-State to indicate qcl-Type set to "typeA" with periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and, if applicable, qcl-Type with the same periodic CSI-RS resources set to "typeD".

[0064] For periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet that does not have the higher layer parameter trs-Info and is configured with no higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-colocation types: - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, if applicable, "typeD" with SS / PBCH blocks, or - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or - "typeB" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info if "typeD" is not applicable.

[0065] For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE should expect the TCI-State to indicate one of the following quasi-co-location types: - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or - "typeC" with SS / PBCH blocks and, if applicable, "typeD" with the same SS / PBCH blocks.

[0066] For DM-RS of PDCCH, the UE should expect the TCI-State to indicate one of the following quasi-co-location types: - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and "typeD" with the same CSI-RS resources, if applicable.

[0067] For DM-RS of PDSCH, the UE should expect the TCI-State to indicate one of the following quasi-co-location types: - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, "typeD" with the same CSI-RS resources, or - "typeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, if applicable, "typeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or - "typeA" with CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and "typeD" with the same CSI-RS resources, if applicable.

[0068] When a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by the DCI is on another component carrier, timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCHIf tci-PresentInDCI is set to "enabled" and the offset between the reception of DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and if tci-PresentInDCI is not set, the UE derives its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable for the PDSCH in the scheduled cell's active BWP.

[0069] As specified in the 3GPP specification (TS 38.214), if the UE is configured with the higher layer parameter RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", "TDMSchemeA", the UE shall indicate two TCI states in the codepoint of the DCI field "Transmission Configuration Indication" and indicate the DMRS ports in one Code Domain Multiplexing (CDM) group in the DCI field "Antenna Port(s)". If two TCI states are indicated in the DCI and the UE is configured to "FDMSchemeA", the UE shall receive a single PDSCH transmission opportunity for the TB with each TCI state associated with a non-overlapping frequency domain resource allocation as described in the clause "Physical resource block (PRB) bundling" in TS 38.214 (e.g., clause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is configured to "FDMSchemeB", the UE should receive two PDSCH transmission opportunities of the same TB, where each TCI state is associated with a PDSCH transmission opportunity with a non-overlapping frequency domain resource allocation with respect to other PDSCH transmission opportunities, as described in TS 38.214 clause "Physical resource block (PRB) bundling" (e.g. clause 5.1.2.3). If two TCI states are indicated in the DCI and the UE is configured to "TDMSchemeA", the UE should receive two PDSCH transmission opportunities of the same TB, where each TCI state is associated with a PDSCH transmission opportunity with a non-overlapping time domain resource allocation with respect to other PDSCH transmission opportunities, as described in TS 38.214 clause "Resource allocation in the time domain" (e.g. clause 5.1.2.1), and all two PDSCH transmission opportunities should be received within a given slot.

[0070] If the UE is configured by the higher layer parameter PDSCH-config indicating at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, the UE may expect one or two TCI states to be indicated in the codepoint of the DCI field "Transmission Configuration Indication" and a DM-RS port in one CDM group to be indicated in the DCI field "Antenna Port(s)", together with the DCI field "Time domain resource assignment" indicating an entry containing RepNumR16 in PDSCH-TimeDomainResourceAllocation. 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 opportunities of the same TB, where two TCI states are used across multiple PDSCH transmission opportunities, 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 opportunities of the same TB, where one TCI state is used across multiple PDSCH transmission opportunities, as described in "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1).

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

[0072] If the UE has not been indicated a DCI where the DCI field "Time domain resource assignment" indicates an entry in the pdsch-TimeDomainAllocationList containing RepNumR16 in the PDSCH-TimeDomainResourceAllocation and one TCI state is indicated in the codepoint of the DCI field "Transmission Configuration Indication", the UE procedure for receiving the PDSCH upon detection of a PDCCH shall follow the clause "UE procedures for receiving the physical downlink shared channel" in TS 38.214 (e.g. clause 5.1).

[0073] In the following, the terms "FDMSchemeA" and "Scheme2a" may be used interchangeably. The terms "FDMSchemeB" and "Scheme2b" may be used interchangeably. The terms "TDMSchemeA" and "Scheme3" may be used interchangeably. The terms "RepNumR16" and "Scheme4" may be used interchangeably.

[0074] As specified in the 3GPP specification (TS 38.214), if the UE is configured with the higher layer parameter RepSchemeEnabler set to "TDMSchemeA" and the DM-RS port in one CDM group indicated in the DCI field "Antenna Port", the number of PDSCH transmission opportunities is derived from the number of TCI states indicated by the DCI field "Transmission Configuration Indication" of the scheduling DCI. If two TCI states are indicated by the DCI field "Transmission Configuration Indication", the UE is expected to receive two PDSCH transmission opportunities, where the first TCI state applies to the first PDSCH transmission opportunity, and the resource allocation in the time domain for the first PDSCH transmission opportunity follows the clause "Resource allocation in the time domain" in TS 38.214 (e.g., clause 5.1.2.1). The second TCI state applies to the second PDSCH transmission opportunity, which should have the same number of symbols as the first PDSCH transmission opportunity. When configured by higher layers with TIFF2025503561000004.tif44, the UE shall determine whether the first symbol of the second PDSCH transmission opportunity is greater than or equal to the last symbol of the first PDSCH transmission opportunity. It should be determined that TIFF2025503561000005.tif starts 44 symbols later. By the UE if TIFF2025503561000006.tif11153TIFF2025503561000007.tif44 is not configured via higher layer parameter StartingSymbolOffsetK. It should be assumed that the UE is TIFF2025503561000008.tif513. The UE does not expect to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity. For two PDSCH transmission opportunities, the applied redundancy version is derived according to table 5.1.2.1-2 of TS 38.214, where n=0, 1 applies to the first and second TCI states, respectively. Otherwise, the UE is expected to receive a single PDSCH transmission opportunity and the resource allocation in the time domain follows clause "Resource allocation in the time domain" of TS 38.214 (e.g. clause 5.1.2.1).

[0075] As specified in the 3GPP specification (TS 38.214), if the UE is configured with the higher layer parameter PDSCH-config indicating at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, and two TCI states are indicated by the DCI field "Transmission Configuration Indication" and the DCI field "Time domain resource assignment" indicating an entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation and a DM-RS port in one CDM group in the DCI field "Antenna Port(s)", then the same SLIV (Start and length indicator value) applies to all PDSCH transmission opportunities, a first TCI state applies to the first PDSCH transmission opportunity, and the resource allocation in the time domain for the first PDSCH transmission opportunity is determined by the TS 38.214. 38.214 clause "Resource Allocation in the Time Domain" (e.g. clause 5.1.2.1). If the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is equal to 2, the second TCI state is applied to the second PDSCH transmission opportunity. If the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation is greater than 2, the UE may be further configured to enable CycMapping or SeqMapping in RepTCIMapping. If CycMapping is enabled, the first and second TCI states are applied to the first and second PDSCH transmission opportunities, respectively, and the same TCI mapping pattern continues to be applied to the remaining PDSCH transmission opportunities.If SeqMapping is enabled, the first TCI state applies to the first and second PDSCH transmissions, the second TCI state applies to the third and fourth PDSCH transmissions, and the same TCI mapping pattern continues to be applied to the remaining PDSCH transmission opportunities. The UE may expect that each PDSCH transmission opportunity is limited to two transmission layers. For all PDSCH transmission opportunities 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 PDSCH transmission opportunities associated with the first TCI state. The redundancy version for 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 is set by the higher layer parameter RVSeqOffset, and n is counted considering only PDSCH transmission opportunities associated with the second TCI state. If one TCI state is indicated by the DCI field "Transmission Configuration Indication" and the DCI field "Time domain resource assignment" indicating an entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation and a DM-RS port in one CDM group in the DCI field "Antenna Port(s)", the same SLIV applies for all PDSCH transmission opportunities, and the first PDSCH transmission opportunity is according to the clause "Resource allocation in the time domain" in TS 38.214 (e.g. clause 5.1.2.1), and the same TCI state applies for all PDSCH transmission opportunities. The UE may expect that each PDSCH transmission opportunity is limited to two transmission layers. For every PDSCH transmission opportunity, the applied redundancy version is derived according to Table 5.1.2.1-2 [TS 38.214], where n is counted considering the PDSCH transmission opportunity. Otherwise, the UE is expected to receive a single PDSCH transmission opportunity 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). Table 5.1.2.1-2: Redundancy version applied when pdsch-AggregationFactor is present JPEG2025503561000009.jpg36164 Table 5.1.2.1-3: Redundancy version applied for the second TCI state when RVSeqOffset is present JPEG2025503561000010.jpg44164

[0076] For a UE configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeA" or "FDMSchemeB" as specified in the 3GPP specification (TS 38.214), if the UE receives two TCI states indicated in the codepoints of the DCI field "Transmission Configuration Indication" and a DM-RS port in one Code Domain Multiplexing (CDM) group indicated in the DCI field "Antenna Port(s)", If TIFF2025503561000011.tif815 is determined as "broadband", the first TIFF2025503561000012.tif1113 PRBs are assigned to the first TCI state, and the remaining TIFF2025503561000013.tif1013 PRBs are assigned to the second TCI state, where n PRB is the total number of allocated PRBs for the UE. If TIFF2025503561000014.tif815 is determined to be one of the values ​​{2,4}, then the even PRGs within the allocated frequency domain resources are assigned to the first TCI state and the odd PRGs within the allocated frequency domain resources are assigned to the second TCI state. The UE does not expect to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity.

[0077] For a UE configured with the higher layer parameter RepSchemeEnabler set to "FDMSchemeB" and if the UE has two TCI states indicated in the DCI field "Transmission Configuration Indication" codepoints and a DM-RS port in one CDM group indicated in the DCI field "Antenna Port(s)", each PDSCH transmission shall follow clause "Physical downlink shared channel" of [TS 38.211] (e.g. clause 7.3.1) and its mapping to resource elements shall be determined by the assigned PRB for the corresponding TCI state of the PDSCH transmission opportunity, and the UE shall expect only a maximum of two code blocks for each PDSCH transmission opportunity if a single transmission tier is scheduled and only a single code block for each PDSCH transmission opportunity if two transmission tiers are scheduled. For the two PDSCH transmission opportunities, the redundancy version to be applied is derived according to Table 5.1.2.1-2 of [TS 38.214], where n=0, 1 applies to the first and second TCI states, respectively.

[0078] In some embodiments, the terminal device 130 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 the second PDCCH candidate are applied for PDCCH repetition. For another example, the linked first PDCCH candidate and the second PDCCH candidate are applied for 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.

[0079] In some embodiments, terminal device 130 may be configured with multiple control resource sets (ie, CORESETs).

[0080] In some embodiments, the CORESET is a frequency domain TIFF2025503561000015.tif827 resource blocks (RBs) and TIFF2025503561000016.tif may consist of 853 symbols. In some embodiments, a Control Channel Element (CCE) consists of 6 Resource Element Groups (REG), where a REG is equal to one resource block in one Orthogonal Frequency Division Multiplexing (OFDM) symbol. In some embodiments, the REGs in a control resource set are numbered in a time-first increasing order, starting with 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set.

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

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

[0083] In some embodiments, the terminal device 130 may assume that the demodulation reference signal (DM-RS) antenna port associated with PDCCH reception in a CORESET is quasi-co-located (QCL) with one or more reference signals (RS) configured by the transmission control indicator (TCI) state indicated for that CORESET (if applicable).

[0084] In some embodiments, if a medium access control (MAC) control element (CE) activation command indicating a TCI state for a CORESET is not received after a most recent random access procedure that was not initiated by a PDCCH order triggering a contention-free random access procedure, the terminal device 130 may assume that the DM-RS antenna port associated with PDCCH reception in the CORESET is quasi-co-located (QCL) 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 (RS) are configured according to the TCI state indicated for the CORESET (if applicable).

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

[0086] In some embodiments, the network device 110 may transmit to the terminal device 130 one or more configurations (e.g., 210) for the first PDCCH candidate and the second PDCCH candidate. In some embodiments, the first PDCCH candidate may be included in a first search space or a first search space set. In some embodiments, the first search space or the first search space set may be associated with a first CORESET. In some embodiments, the first CORESET may be associated with or configured to have a first TCI state T1 or a first set of QCL parameters Q1. In some embodiments, the second PDCCH candidate may be included in a second search space or a second search space set. In some embodiments, the second search space or the second search space set may be associated with a second CORESET. In some embodiments, the second CORESET may be associated with or configured to have a second TCI state T2 or a second set of QCL parameters Q2. In some embodiments, T1 may be different from T2. In some embodiments, Q1 may be different from Q2.

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

[0088] In some embodiments, the network device 110 may transmit a configuration (e.g., 210) to the terminal device 130 indicating that the first PDCCH candidate and the second PDCCH candidate are linked together for PDCCH repetition. In some embodiments, the network device 110 may transmit a configuration (e.g., 210) to the terminal device 130 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, the configuration may be transmitted from the network device 110 to the terminal device 130 via any of radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), and a 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).

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

[0090] In some embodiments, the network device 110 may transmit at least one configuration (eg, 210) regarding the first CORESET and the second CORESET to the terminal device 130.

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

[0092] In some embodiments, a PDCCH candidate in a first search space set is linked with a PDCCH candidate in a 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.

[0093] In some embodiments, network device 110 may transmit one or more configurations (e.g., 210) for a third CORESET to terminal device 130. The one or more configurations may indicate two active TCI states for the third CORESET. For example, terminal device 130 may detect / decode a PDCCH in a search space set associated with a third CORESET that has two active TCI states.

[0094] In some embodiments, network device 110 may transmit one or more configurations (e.g., 210) for a first number of PDSCH / PUSCH / PUCCH transmissions / receptions / repetitions to terminal device 130. 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, network device 110 may transmit scheduling (e.g., 210) for a first number of PDSCH / PUSCH / PUCCH transmissions / receptions / repetitions / opportunities to terminal device 130 within a single DCI / PDCCH or within PDCCHs within linked PDCCH candidates. In some embodiments, two TCI states (e.g., a first TCI state and a second TCI state) or two spatial relationship information (e.g., a first spatial relationship information and a second spatial relationship information) may be indicated / configured within a single DCI / PDCCH or within a PDCCH within linked PDCCH candidates.

[0095] In some embodiments, the terminal device 130 may be configured or indicated to have M activated unified TCI states. For example, the unified TCI state may be a downlink TCI state or a combined TCI state. M may be a positive integer. For example, M may be at least one of {1, 2, 3, 4}.

[0096] In some embodiments, the terminal device 130 may be configured or indicated to have N activated unified TCI states. For example, the unified TCI state may be an uplink TCI state or a combined TCI state. N may be a positive integer. For example, N may be at least one of {1, 2, 3, 4}.

[0097] In some embodiments, when M≧2, there may be two PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunity sets (e.g., set 1 and set 2) for multiple PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunities, where set 1 has a second number of PDSCH / PUSCH / PUCCH transmission / reception / repetitions / opportunities (the second number is G1, where 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 / repetitions / opportunities (the third number is G2, where G2=G-G1). In some embodiments, set 1 of PDSCH / PUSCH / PUCCH transmission / reception / repetitions / opportunities is transmitted / received in a first TCI state or with first spatial relationship information, and set 2 of PDSCH / PUSCH / PUCCH transmission / reception / repetitions / opportunities is transmitted / received in a second TCI state or with second spatial relationship information.

[0098] In some embodiments, the network device 110 may configure (e.g., 210) the terminal device 130 with a mapping type. For example, the mapping type may indicate an association between a TCI state and a PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunity. In some embodiments, the network device 110 may configure (e.g., 210) the terminal device 130 with a cyclic mapping type, and the network device may configure a first number of PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunities greater than two. Also, the first and second TCI states apply to the first and second PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunities, respectively, and the same TCI mapping pattern continues to apply to the remaining PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunities. In some embodiments, the network device 110 may configure (e.g., 210) the terminal device 130 with a sequential mapping type, and the network device may configure a first number of PDSCH / PUSCH / PUCCH transmission / reception / repetitions to be greater than two, and a first TCI state is applied to the first and second PDSCH / PUSCH / PUCCH transmission / reception / repetitions, a second TCI state is applied to the third and / or fourth PDSCH / PUSCH / PUCCH transmission / reception / repetitions, and the same TCI mapping pattern continues to be applied to the remaining PDSCH / PUSCH / PUCCH transmission / reception / repetitions. In some embodiments, the network device 110 may configure (e.g., 210) the first number of PDSCH / PUSCH / PUCCH transmission / reception / repetitions to be two. Also, the first TCI state applies to a first PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunity, and the second TCI state applies to a second PDSCH / PUSCH / PUCCH transmission / reception / repetition / opportunity.

[0099] If a UE configured with higher layer repetitionScheme set to "fdmSchemeA" or "fdmSchemeB" has two TCI states indicated in the codepoint of the DCI field "Transmission Configuration Indication" and a DM-RS port in one CDM group indicated in the DCI field "Antenna Port(s)", the UE receives a single PT-RS port associated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports allocated for the PDSCH, the PT-RS frequency density is determined by the number of PRBs associated with each TCI state, and a PT-RS resource element mapping is associated to the allocated PRB for each TCI state.

[0100] In addition to normal data communication, the network device 110 may transmit an RS to the terminal device 130 in the downlink. Similarly, the terminal device 130 may transmit an RS to the network device 110 in the uplink. In general, an RS is a signal sequence (also called an "RS sequence") that is known to both the network device 110 and the terminal device 130. For example, the RS sequence may be generated and transmitted by the network device 110 based on a certain rule, and the terminal device 130 may estimate the RS sequence based on the same rule. In another example, the RS sequence may be generated and transmitted by the terminal device 130 based on a certain rule, and the network device 110 may estimate the RS sequence based on the same rule. Examples of RS may include, but are not limited to, a downlink or uplink demodulation reference signal (DMRS), a CSI-RS, a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a tracking reference signal (TRS), a fractional time-frequency tracking reference signal (TRS), a CSI-RS for tracking, a positioning reference signal (PRS), etc.

[0101] In addition to normal data communication, the network device 110 may transmit a DCI to the terminal device 130 via a PDCCH. The DCI may indicate resource allocation for data transmission in DL or UL. At the same time, a DMRS associated with the PDCCH may also be transmitted from the network device 110 to the terminal device 130. The DMRS may be used by the terminal device 130 for channel demodulation. The terminal device 130 may then attempt to blindly decode the DCI within a search space associated with a control resource set (CORESET). As used herein, "CORESET" and / or search space refers to a set of resource element groups in which the terminal device attempts to blindly decode the DCI. A search space indicating a start time and periodicity for monitoring the PDCCH in the CORESET may be indicated to the terminal device 130. In response to successfully decoding the DCI, the terminal device 130 may accordingly perform UL and / or DL ​​data transmission with the network device 110 (e.g., data transmission via a PDSCH and / or a PUSCH (Physical Uplink Shared Channel)).

[0102] The network device 110 may communicate data and control information to the terminal device 130 via multiple beams (also referred to as "DL beams"). The terminal device 130 may also communicate data and control information to the network device 110 via multiple beams (also referred to as "UL beams"). In the 3GPP specifications for New Radio (NR), the beams are also defined and indicated by a transmission configuration indicator parameter. 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-co-location (QCL) relationship between one or two DL and / or UL reference signals and a DMRS port of a PDSCH, a DMRS port of a PDCCH, a DMRS port of a PUSCH, a DMRS port of a PUCCH, an SRS port of an SRS resource, or a CSI-RS port of a CSI-RS resource.

[0103] In some embodiments, there may be an application timing for the beam indication or the TCI status indication. In some embodiments, the application timing may be a first slot or a first sub-slot that is at least Y symbols after the last symbol of the acknowledgement of the combined or separate DL / UL beam indication or TCI status 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. In some embodiments, S may be an integer and 1≦S≦14. For example, S may be at least one of {2, 4, 7}. In some embodiments, the TCI status is indicated in a DCI in a PDCCH. For example, the DCI in a PDCCH may schedule a PDSCH or may not schedule a PDSCH. In some embodiments, the gap between the last symbol of the DCI and the first slot or the first sub-slot should meet the capability of the terminal device. In some embodiments, the acknowledgement of the combined or separate DL / UL beam indication may be an acknowledgement of a PDSCH scheduled by the DCI, for example if the DCI schedules a PDSCH. In some embodiments, the acknowledgement of the combined or separate DL / UL beam indication may be an acknowledgement of the DCI, for example if the DCI does not schedule a PDSCH.

[0104] In some embodiments, DCI (e.g. DCI format 1_1 / 1_2 with DL allocation and DCI format 1_1 / 1_2 without DL allocation) may be used for dynamic beam indication. In some embodiments, DCI with DL scheduling or PDSCH scheduling may indicate a TCI state, and HARQ or ACK and / or NACK for PDSCH or DL ​​scheduling may be used to indicate an acknowledgement of the TCI state indication. After application timing, the indicated TCI state may be applied. For example, the indicated TCI state may be applied to PDSCH and / or PDCCH and / or PUSCH and / or PUCCH and / or downlink RS and / or uplink RS.

[0105] In some embodiments, terminal device 130 may receive or detect a DCI (e.g., represented as “DCI_t”) in a PDCCH, which indicates a combined DL / UL TCI state or separate DL / UL TCI state or DL ​​TCI state or UL TCI state or pair of DL / UL TCI states. In some embodiments, the first time threshold may indicate a predefined / configured period of time after the first or last symbol of the PDCCH or the first or last symbol of the indication acknowledgment. In some embodiments, the indicated combined DL / UL TCI state or separate DL / UL TCI state 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 an application timing or first time threshold. For example, if a combined DL / UL TCI state is indicated in a 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 an application timing or a first time threshold. As another example, if a DL TCI state is indicated in a DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after an application timing or a first time threshold. As another example, if a UL TCI state is indicated in a DCI, the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after an application timing or a first time threshold. As another example, if a pair of DL / UL TCI states is indicated in the DCI, the DL TCI state may be applied to the PDSCH and / or CORESET and / or downlink RS after an application timing or a first time threshold, and the UL TCI state may be applied to the PUSCH and / or PUCCH and / or uplink RS after an application timing or a first time threshold. In some embodiments, the first time threshold may be the same as the threshold.

[0106] In some embodiments, the terminal device 130 may receive an indication of a TCI state in a DCI. In some embodiments, the terminal device 130 may transmit a PUCCH with HARQ-ACK information corresponding to the DCI carrying the indication (e.g., the DCI may have no DL allocation) and / or corresponding to a PDSCH scheduled by the DCI carrying the indication (e.g., the DCI may have a DL allocation), and the indicated TCI state may be applied from an application timing for the indicated TCI state. In some embodiments, the application timing may be a first slot that is at least Y symbols after the last symbol of the PUCCH. For example, the HARQ-ACK information may be an ACK or an acknowledgement. In some embodiments, the indicated TCI state may be applied if at least one of the indicated TCI states is different from at least one of the previously indicated TCI states.

[0107] In some embodiments, the terminal device 130 may receive an indication of the TCI state in a DCI. For example, the TCI state may be a combined TCI state. In some embodiments, the terminal device 130 may transmit a PUCCH with HARQ-ACK information corresponding to the DCI carrying the indication (e.g., the DCI may have no DL allocation) and / or corresponding to a PDSCH scheduled by the DCI carrying the indication (e.g., the DCI may have a DL allocation), and the indicated TCI state may be applied from an application timing for the indicated TCI state. In some embodiments, the application timing may be a first slot that is at least Y symbols after the last symbol of the PUCCH. For example, the HARQ-ACK information may be an ACK or an acknowledgement. In some embodiments, the indicated TCI state may be applied if the indicated TCI state is different from a previously indicated TCI state.

[0108] In some embodiments, terminal device 130 may receive an indication of the DL TCI state and / or the UL TCI state in a DCI. In some embodiments, terminal device 130 may transmit a PUCCH with HARQ-ACK information corresponding to the DCI carrying the indication (e.g., the DCI may have no DL allocation) and / or corresponding to a PDSCH scheduled by the DCI carrying the indication (e.g., the DCI may have a DL allocation), and the indicated DL TCI state and / or UL TCI state may be applied from an application timing for the indicated DL TCI state and / or UL TCI state. In some embodiments, the application timing may be a first slot that is at least Y symbols after the last symbol of the PUCCH. For example, the HARQ-ACK information may be an ACK or an acknowledgement. In some embodiments, the indicated DL TCI state and / or UL TCI state may be applied if the indicated DL TCI state is different from a previously indicated DL TCI state and / or if the indicated UL TCI state is different from a previously indicated UL TCI state.

[0109] In some embodiments, a DCI indicating at least one of semi-persistent (SPS) PDSCH release, secondary cell (Scell) dormancy not scheduling PDSCH reception, and a TCI status update not scheduling PDSCH reception may be referred to as a DCI with associated HARQ-ACK information not scheduling PDSCH reception.

[0110] In some embodiments, the HARQ-ACK information may include two or more HARQ-ACK information bits.

[0111] In some embodiments, for the HARQ-ACK information bits, if terminal device 130 detects DCI or correctly decodes a transport block or code block group (CBG), terminal device 130 may generate a positive acknowledgement (ACK), where the DCI may provide an SPS PDSCH release or indicate a TCI status update.

[0112] In some embodiments, for a HARQ-ACK information bit, if the terminal device 130 does not correctly decode a transport block or a code block group (CBG), the terminal device 130 may generate a negative acknowledgement (NACK). In some embodiments, a HARQ-ACK information bit value of 0 may represent a NACK. In some embodiments, a HARQ-ACK information bit value of 1 may represent an ACK.

[0113] In some embodiments, terminal device 130 may be configured to have a code block group transmission. For example, terminal device 130 may be provided with or configured to have a PDSCH-CodeBlockGroupTransmission for the serving cell. In some embodiments, terminal device 130 may receive a PDSCH scheduled by a DCI (e.g., DCI format 1_1 or DCI format 1_2). In some embodiments, there may be one or two transport blocks in the PDSCH. In some embodiments, there may be more than one code block group (CBG) or code block (CB) in a transport block or in one of the two transport blocks. In some embodiments, terminal device 130 may be provided with or configured to have a maximum number of CBGs. For example, the maximum number is For example, The value of TIFF2025503561000018.tif619 may be at least one of {2, 4, 6, 8}. TIFF2025503561000019.tif619 HARQ-ACK information bits may be generated.

[0114] In some embodiments, there may be a number of code blocks (CBs) (e.g., the number may be denoted as C, where C is a positive integer) in a transport block, and the terminal device 130 may determine a number of CBGs (e.g., the number may be denoted as N_CBG) for the transport block. For example, N_CBG is a positive integer. In some embodiments, N_CBG is The minimum value between TIFF2025503561000020.tif619 and C. For example, TIFF2025503561000021.tif673. In some embodiments, there may be at least one Code Block (CB) within the CBG.

[0115] In some embodiments, the terminal device 130 may generate a number of HARQ-ACK information bits for a transport block. For example, the number may be For example, The file is TIFF2025503561000023.tif629.

[0116] In some embodiments, if terminal device 130 correctly receives or decodes all code blocks of a CBG, terminal device 130 may generate an ACK for the HARQ-ACK information bits of the CBG. In some embodiments, if terminal device 130 does not correctly receive or decode at least one code block of the CBG, terminal device 130 may generate a NACK for the HARQ-ACK information bits of the CBG. In some embodiments, if terminal device 130 receives two transport blocks, terminal device 130 may combine the HARQ-ACK information bits for the CBG of the second transport block after the HARQ-ACK information bits for the CBG of the first transport block.

[0117] In some embodiments, the HARQ-ACK codebook is In some embodiments, the transport block may include 619 HARQ-ACK information bits. TIFF2025503561000025.tif641, the terminal device 130 A NACK value may be generated for (each of) the 643 HARQ-ACK information bits.

[0118] In some embodiments, when terminal device 130 generates a HARQ-ACK codebook in response to a retransmission of a transport block that corresponds to the same HARQ process as a previous transmission of the transport block, terminal device 130 may generate an ACK for each CBG that terminal device 130 correctly decoded in the previous transmission of the transport block.

[0119] In some embodiments, the terminal device 130 is TIFF2025503561000027.tif Correctly detects or decodes each of the 620 CBGs, and If the transport blocks are not correctly detected or decoded for 620 CBGs, the terminal device 130: A NACK value may be generated for each of the 620 CBGs.

[0120] 2 is a signaling diagram for signaling communication according to some embodiments of the present disclosure. For illustrative purposes, the process 200 will be described with reference to FIG. 1. As shown in FIG. 1, the process 200 may involve network device 110 and terminal device 130. In some embodiments, the process 200 may involve TRP 120-1 and TRP 120-2 and terminal device 130 as shown in FIG.

[0121] 2, the network device 110 may configure / transmit one or more configurations to the terminal device 130 (2001). In some embodiments, the one or more configurations may include at least one of a TCI state configuration, a CORESET configuration, a search space configuration, a PDCCH configuration, a PDSCH configuration, a PUSCH configuration, a PUCCH configuration, a control information configuration for data transmission / reception, a reference signal (RS) transmission / reception configuration, and a repetition / transmission / reception mode configuration.

[0122] The network device 110 transmits a first PDCCH to the terminal device 130 (2010). The first PDCCH includes a first DCI. The first DCI indicates a first TCI state. In some embodiments, the first PDCCH may be received from the TRP 120-1. For example, as shown in FIG. 3, the TRP 120-1 may transmit a PDCCH 311 to the terminal device 130. The PDCCH 311 may include a first DCI indicating TCI state 1.

[0123] In some embodiments, prior to the transmission of the first PDCCH, the network device 110 may transmit a second PDCCH to the terminal device 130 (2005). The second PDCCH includes a second DCI. The second DCI indicates a second TCI state. In some embodiments, the second PDCCH may be received from the TRP 120-2. For example, as shown in FIG. 3, the TRP 120-2 may transmit a PDCCH 321 to the terminal device 130. The PDCCH 321 may include a second DCI indicating TCI state 2.

[0124] The terminal device 130 transmits (2020) first HARQ-ACK information to the network device 110. The first HARQ-ACK information corresponds to a first DCI in the first PDCCH. In some embodiments, the first HARQ-ACK information may be transmitted to the TRP 120-1. For example, as shown in FIG. 3, the TRP 120-1 may receive HARQ-ACK information 331 from the terminal device 130. The HARQ-ACK information 331 may correspond to a DCI in the PDCCH 311.

[0125] In some embodiments, the terminal device 130 may transmit 2040 the second HARQ-ACK information to the network device 110. The second HARQ-ACK information corresponds to a second DCI in the second PDCCH. In some embodiments, the second HARQ-ACK information may be transmitted to the TRP 120-2. For example, as shown in FIG. 3, the TRP 120-2 may receive HARQ-ACK information 332 from the terminal device 130. The HARQ-ACK information 332 may correspond to a DCI in the PDCCH 321.

[0126] Continuing to refer to FIG. 2, if the condition is met, the terminal device 130 applies the first TCI state (2030). For example, as shown in FIG. 3, the terminal device 130 may apply TCI state 1 at timing 340. There may be more than Y symbols between the HARQ-ACK information 331 and the timing 340. In some embodiments, the terminal device 130 may apply the first TCI state to all PUCCHs. Alternatively, the terminal device 130 may apply the first TCI state to a subset of PUCCHs. For example, some PUCCHs (e.g., represented as PUCCH_na) may be configured to apply or not apply the indicated TCI state. In some embodiments, not applying the first TCI state may be conditionally configured if the CORESET is configured to not apply the indicated TCI state. The PUCCHs that do not apply the indicated TCI state may be applied to HARQ-ACK feedback for PDSCHs scheduled by the CORESET (that does not apply the indicated TCI state).

[0127] In some embodiments, the timing for applying or applying (2030) the first TCI state may be later than or after the timing for transmission of the second HARQ-ACK information or the first / start symbol or the last / end symbol.

[0128] In some embodiments, the timing for applying or applying (2030) the first TCI state may be before the timing for transmission of the second HARQ-ACK information or the first / start symbol or the last / end symbol.

[0129] In some embodiments, the condition may include that at least one bit value of the HARQ-ACK information corresponding to the first DCI or corresponding to a PDSCH scheduled by the first DCI is an ACK. Table 1 below shows an example according to some embodiments. Table 1 TIFF2025503561000030.tif79151

[0130] In some embodiments, the terminal device 130 may receive or detect a DCI, which may indicate a unified DCI state, and which may schedule at least one PDSCH. In some embodiments, there may be two transport blocks in the PDSCH. In some embodiments, there may be at least one CBG in the transport block in the PDSCH. In some embodiments, there may be at least one CBG in at least one of the two transport blocks in the PDSCH. In some embodiments, there may be at least one HARQ-ACK information bit in the HARQ-ACK information for the PDSCH. In some embodiments, if at least one HARQ-ACK information bit for the PDSCH scheduled by the DCI is ACK and / or if the unified TCI state is different from the previously indicated / applied unified TCI state, the unified TCI state is applied after the application timing. In some embodiments, if any one HARQ-ACK information bit for the PDSCH scheduled by the DCI is NACK, the unified TCI state is not applied after the application timing.

[0131] In some embodiments, the condition may include that the first TCI state is set for a TCI update in a unified TCI framework. Alternatively or additionally, the condition may include that the first TCI state is a unified TCI state. In some embodiments, the condition may include that the first TCI state is set to have tci-StateId-r17. In some embodiments, the condition may include that the first TCI state is labeled with a parameter that is tci-StateId-r17 or r17. In some other embodiments, the condition may include that the first TCI state is different from the seventh TCI state. The seventh TCI state may be at least one of a previous applied unified TCI state, a previous indicated unified TCI state, or a currently applied unified TCI state.

[0132] In some embodiments, the condition may include that the first DCI is not a DCI that schedules a semi-persistent scheduling (SPS) activation. Alternatively or additionally, the condition may include that the first DCI is not a DCI that schedules an SPS release. In other embodiments, the condition may include that the first DCI is a DCI that carries a unified TCI state or a TCI state for a TCI state update or a TCI state configured to have tci-StateId-r17. In some embodiments, the condition may include that the first PDCCH is not a PDCCH in a control resource set (CORESET) that is not configured to share or apply the unified TCI state. Alternatively or additionally, the condition may include that the first PDCCH is a PDCCH in a CORESET that is configured to share or apply the unified TCI state. Table 2 below shows an example according to some embodiments. Table 2 TIFF2025503561000031.tif89144

[0133] In some embodiments, the terminal device 130 may receive or detect a DCI, which may schedule at least one of SPS scheduling activation, SPS release, and Scell ​​dormancy, the value of the TCI field (if present) in the DCI may be ignored, and the indicated TCI state in the TCI field may not apply or may be ignored. For example, the DCI may not schedule PDSCH reception. As another example, the DCI may schedule PDSCH reception.

[0134] In some embodiments, terminal device 130 may be configured to have a CORESET. In some embodiments, the CORESET may be configured to not share or apply the indicated unified TCI state or the TCI state indicated for the PDCCH and / or PDSCH. In some embodiments, the CORESET may not be configured to have an indication or configuration to share or apply the indicated unified TCI state. In some embodiments, there may be a TCI field in the DCI in the PDCCH in the CORESET. In some embodiments, terminal device 130 may receive or detect the DCI, the value of the TCI field in the DCI (if present) may be ignored, and the indicated TCI state in the TCI field may not be applied or may be ignored.

[0135] In some embodiments, the HARQ-ACK information may include two or more HARQ-ACK information bits. Alternatively or additionally, the PDSCH may include two transport blocks, where each transport block may correspond to one HARQ-ACK information bit. In some other embodiments, the PDSCH may include one transport block. In some embodiments, the at least one transport block in the PDSCH may include two or more Code Block Groups (CBGs), where each CBG may correspond to one HARQ-ACK information bit.

[0136] In some embodiments, as described above, the terminal device 130 may receive the first PDCCH and the second PDCCH. In this case, the condition may include that the transmission of the first HARQ-ACK information is later than or subsequent to the transmission of the second HARQ-ACK information. In some embodiments, the condition may include that the transmission of the first HARQ-ACK information is earlier than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH. In some embodiments, the condition may include that the start symbol or end symbol of the resource for the transmission of the first HARQ-ACK information is earlier than the start symbol or end symbol of the resource for the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH. In some embodiments, if the transmission of the first HARQ-ACK information is after or later than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is before or earlier than the end symbol of the second PDCCH, the terminal device 130 may decide to ignore or not apply the first TCI state.

[0137] For example, in some embodiments, the second TCI state corresponding to a codepoint in the TCI field in the second PDCCH and the first TCI state corresponding to a codepoint in the TCI field in the first PDCCH may be applied to the same M and / or N subsets in case of combined HARQ-ACK feedback. In case of out-of-order HARQ feedback, in the second HARQ-ACK feedback 332, the TCI state indicated in the PDCCH 322 prior to the PDCCH 311 may not be applied (e.g., even if different from the current TCI state) after the beam application timing. The HARQ-ACK information corresponding to the PDCCH 322 may be included in the second HARQ-ACK feedback 332, and the HARQ-ACK information corresponding to the PDCCH 311 may be included in the HARQ-ACK feedback 331. The PDCCH 311 is the PDCCH with an indication of the TCI state that has been applied or will be applied based on the first HARQ-ACK feedback 331. The first HARQ-ACK feedback 331 may be any one earlier than the second HARQ feedback 332 or the last HARQ feedback.

[0138] In some embodiments, if the CORESET is configured not to share or apply the indicated TCI state (i.e., the first TCI state), the TCI state for the PDCCH in the CORESET may be activated by the MAC CE. If M is greater than 1, the CORESET may still be included in one of the M subsets of the CORESET. The TCI state for the PDSCH in the CORESET may follow the PDCCH or be indicated in the TCI field. For example, the network device 110 may transmit a MAC CE to the terminal device 130 (2050). The MAC CE may include activation of a third TCI state for the CORESET. The CORESET may be configured not to share or apply the unified TCI state. The network device 110 may also transmit a third PDCCH in the CORESET (2060). The third PDCCH may schedule a third PDSCH. In this case, the terminal device 130 may apply at least one quasi-co-location (QCL) parameter to the third PDSCH as associated with the third TCI state, or may apply at least one QCL parameter to the third PDSCH as associated with the fourth TCI state. The fourth TCI state may be indicated for the third PDSCH in a TCI field in the third PDCCH. In some embodiments, there may be no scheduling of a PUSCH for the third PDCCH in the CORESET.

[0139] In some embodiments, the spatial relationship information for PUSCHs scheduled by a PDCCH may be applied to all or a subset of PUCCHs corresponding to the subset of the CORESET, or may be according to the UL TCI or combined TCI indicated / applied by PDCCHs in the same subset of the CORESET that share / apply the indicated Rel-17 TCI state. For example, the terminal device 130 may apply a spatial domain filter to a subset of PUSCHs corresponding to a subset of the CORESET as associated with an uplink TCI state. Alternatively, the terminal device 130 may apply a spatial domain filter to a subset of PUSCHs corresponding to a subset of the CORESET as associated with a combined TCI state. In some other embodiments, the terminal device 130 may apply the spatial domain filter to all PUSCHs corresponding to a subset of the CORESET as associated with an uplink TCI state. In some embodiments, the terminal device 130 may apply the spatial domain filter to all PUSCHs corresponding to a subset of the CORESET as associated with a combined TCI state. Additionally, terminal device 130 may apply the spatial domain filter to a subset of PUSCHs indicated by a PDCCH in a subset of a CORESET that applies a first TCI state as associated with the uplink TCI state or combined TCI state. In some embodiments, terminal device 130 may apply the spatial domain filter to all PUSCHs indicated by a PDCCH in a subset of a CORESET that applies a first TCI state as associated with the uplink TCI state or combined TCI state.

[0140] Alternatively, the spatial relationship information for the PDCCH-scheduled PUSCH may be according to the TCI state for the PDCCH or the PDSCH. For example, terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the third TCI state. Alternatively, terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the fourth TCI state.

[0141] In some other embodiments, the spatial relationship information for the PUSCH scheduled by the PDCCH may follow the TCI state configured / activated for the PUCCH with the lowest index among PUCCH_na (at least for the PUSCH scheduled by DCI format 0_0). For example, the terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the fifth TCI state. In this case, the fifth TCI state may be configured for the PUCCH with the lowest index among the PUCCHs, and the PUCCH may be configured not to share or apply the unified TCI state.

[0142] In some embodiments, the spatial relationship information for the PUCCHs may be according to an UL TCI or combined TCI that is applied to all or a subset of the PUCCHs corresponding to a subset of a CORESET. For example, terminal device 130 may apply a spatial domain filter to a subset of the PUCCHs corresponding to the subset of a CORESET as associated with an uplink TCI state or combined TCI state. In other embodiments, terminal device 130 may apply the spatial domain filter to all PUCCHs corresponding to the subset of a CORESET as associated with an uplink TCI state or combined TCI state.

[0143] Alternatively, the spatial relationship information for the PUCCH may be according to the TCI state for the PDCCH or the PDSCH. For example, the terminal device 130 may apply the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the third TCI state. In another embodiment, the terminal device 130 may apply the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the fourth TCI state.

[0144] In some embodiments, the spatial relationship information for the PUCCH may be according to the TCI state configured / activated for the PUCCH_na, for example, the terminal device 130 may apply a spatial domain filter to the PUCCH as associated with the sixth TCI state, where the sixth TCI state is configured for the PUCCH.

[0145] In some embodiments, if M>1, in the TCI field in the PDCCH in one subset of the CORESET, (e.g. for DL) each code point corresponds to only one DL TCI or combined TCI state, which may be applied to the subset of the CORESET after the beam application timing, and / or (e.g. for UL) each code point corresponds to no UL TCI or combined TCI state, or to only one UL TCI or combined TCI state, which may be applied to one of the N subsets of PUCCH and / or PUSCH scheduled by the PDCCH in the subset of the CORESET. In some embodiments, there may be a one-to-one mapping between M and N, i.e., a PDCCH in one subset of the M subsets of the CORESET may indicate at most one UL or combined TCI state for one of the N subsets of PUCCH and PUSCH scheduled by the PDCCH in the subset of the CORESET. If M>N, the PDCCH in one of the N subsets selected from the M subsets (e.g., the first N subsets or those with the lowest N values ​​of subset index) may indicate the TCI status for one of the N subsets of PUCCH and PUSCH scheduled by the PDCCH in the subset of CORESET, respectively. For the other MN subsets, in some embodiments, the PDCCH in one of the last MN subsets of CORESET does not indicate the UL TCI status and / or the combined TCI status (updates / indicates only DL TCI for the MN subsets of CORESET and the corresponding PDSCH). The PDCCH does not schedule a PUSCH. The spatial relationship of the PUSCH scheduled by the PDCCH may follow one of the N subsets.Alternatively, for the other MN subsets, a PDCCH in one of the last MN subsets of CORESET may indicate a UL TCI state for one of the N subsets of PUCCHs and PUSCHs scheduled by a PDCCH in that subset. If a set of activated TCI states corresponding to a subset is a combined TCI state, it should be included in the N subsets from the M subsets.

[0146] In some embodiments, the maximum value between M and N may be 2. For example, if both M and N are 2, there may be a one-to-one mapping between M and N. Alternatively, M may be 2 (a first subset of CORESET, denoted as M1, and a second subset of CORESET, denoted as M2), and N may be 1. In this case, the TCI state indicated in the PDCCH in M1 may apply to the PDCCH and corresponding PDSCH in M1, and may apply to all PUCCHs and PUSCHs scheduled by the PDCCH in M1. The TCI state indicated in the PDCCH in M2 may apply to the PDCCH and corresponding PDSCH in M2. In some embodiments, each code point in the TCI field in the PDCCH in M2 may correspond only to DL-only TCI states (non-UL TCI states and non-combined TCI states). In some embodiments, the PDCCH in M2 may not schedule a PUSCH. In some embodiments, the PUSCH scheduled by the PDCCH in M2 may follow the UL or combined TCI state indicated in the first PDCCH. Alternatively, the PUCCH for HARQ-ACK feedback corresponding to the PDSCH scheduled by the PDCCH in M2 may follow the UL or combined TCI state indicated in the PDCCH in M1. In other embodiments, at least one codepoint in the TCI field in the second PDCCH may correspond to a UL TCI state (e.g., a non-combined TCI state). For example, the indicated UL TCI state may apply to the PUCCH and PUSCH (which may be scheduled by the first PDCCH and / or the second PDCCH).

[0147] In some embodiments, for indication of a spatial filter (e.g., UL beam) for uplink transmission, up to N UL TCI states (or combined TCI states) may be mapped to one TCI code point in the DCI in the PDCCH in one subset of the CORESET, with each TCI state corresponding to one subset of the PUCCH. In some other embodiments, the configured / activated UL TCI states may be divided into N groups (e.g., each group includes TCI states that do not overlap / overlap with any one of the other groups), and the PDCCH in one subset of the CORESET can indicate any one of the activated UL TCI states. For example, the spatial filter for a PUSCH scheduled by a PDCCH and / or a PUCCH corresponding to a PDSCH scheduled by a PDCCH or for HARQ-ACK feedback corresponding to a PDCCH may be based on the (current) applied UL TCI state for a subset of PUCCHs, which is determined as the subset corresponding to the indicated UL TCI state (i.e., the subset is the subset that includes the indicated UL TCI state). In some embodiments, the DCI in the PDCCH may include an indication of the index of the subset of PUCCHs. In other embodiments, one SRS resource set may include two or more SRS resources, where each SRS resource corresponds to one subset of PUCCHs, and in case of PUSCH scheduling, the spatial filter for the PUSCH may be based on the (current) applied TCI state for the subset of PUCCHs corresponding to the indicated SRS resources.

[0148] In some embodiments, M may be 1 and N may be 2 (a first subset of PUCCH, e.g., N1, a second subset of PUCCH, e.g., N2). In this case, one SRS resource set includes two or more SRS resources, each SRS resource corresponding to one subset of PUCCH, and in the case of PUSCH scheduling, the spatial filter for PUSCH may be based on the (current) applied TCI state for the subset of PUCCH corresponding to the indicated SRS resource. For example, if the indicated SRS resource in the DCI for PUSCH scheduling corresponds to N1, the spatial filter for PUSCH may be based on the applied TCI state for N1. Alternatively, if the indicated SRS resource in the DCI for PUSCH scheduling corresponds to N2, the spatial filter for PUSCH may be based on the applied TCI state for N2.

[0149] In some embodiments, if the DL and UL multi-TRP configurations are different, the HARQ-ACK feedback mode may be different. For example, if the first number of subsets of CORESET is not greater than the second number of subsets of the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), the HARQ-ACK feedback mode is set to be separate. For example, if M = N>1 (e.g., 1-to-1 mapping) and / or M < N (e.g., each subset of N corresponds to only one subset of M), the HARQ-ACK feedback mode may be assumed / expected to be separate or may not be set.

[0150] Alternatively, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH, and the first group of subsets of CORESET corresponds to the first group of subsets of PUCCH or PUSCH and the second group of subsets of CORESET corresponds to the second group of subsets of PUCCH or PUSCH, the first HARQ-ACK feedback mode within the first group of subsets of CORESET or the second group of subsets of CORESET is configured to be combined, and the second HARQ-ACK feedback mode between the first and second groups of subsets of CORESET is configured to be separate.

[0151] In some embodiments, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH, and the second number of subsets of PUCCH or PUSCH is 1, the HARQ-ACK feedback mode is set to be combined. For example, if M>N (e.g., each subset of CORESET corresponds to only one subset of PUCCH) and / or at least one of M, N>1 (and at least one subset of CORESET corresponds to the same subset of PUCCH), a first group of subsets of CORESET (M_G1) corresponds to N1, a second group of subsets of CORESET (M_G2) corresponds to N2, and within the first group M_G1 or the second group M_G2, the HARQ-ACK feedback mode may be assumed / expected to be combined, and between the first group and the second group, the HARQ-ACK feedback mode may be assumed / expected to be separate.

[0152] In some other embodiments, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH and the second number of subsets of PUCCH or PUSCH is 1, the HARQ-ACK feedback mode is set to be separate. In this case, according to the determination that there are two PUCCHs with HARQ-ACK information in one slot, the terminal device 130 may multiplex the HARQ-ACK information in one PUCCH. For example, if M≧2, N=1, the HARQ-ACK feedback mode may be assumed or expected to be combined. Alternatively, if the HARQ-ACK feedback mode is set as separate and there are two PUCCHs with HARQ-ACK information in one slot, the HARQ-ACK information may be multiplexed in one PUCCH and transmitted in a later or earlier PUCCH resource or with a lower ID. The two PUCCH resources may overlap in symbols.

[0153] In some embodiments, in case of separate HARQ-ACK feedback modes or one-to-one mapping between M and N (M=N>1), the determined / indicated PUCCH resource index within a PDCCH in one subset of M may be a relative index within one subset of N that corresponds to a subset of CORESET. For example, a PUCCH resource group may be reused for a subset of PUCCHs. Alternatively, in case of the PUCCH resource index being absolute (or indexed across N subsets), the determined / indicated PUCCH resource index within a PDCCH in one subset of M may not be expected to be a PUCCH included in a subset of PUCCHs that does not correspond to a subset of CORESET.

[0154] 4 is a flow chart of an example method 400 according to an embodiment of the present disclosure. The method 400 may be implemented in any suitable device. For illustrative purposes only, the method 400 may be implemented in a terminal device 130, such as that shown in FIG.

[0155] In block 410, the terminal device 130 transmits the first HARQ-ACK information to the network device 110. The first HARQ-ACK information corresponds to the first DCI in the first PDCCH. In some embodiments, the first HARQ-ACK information may be transmitted to the TRP 120-1.

[0156] In some embodiments, the terminal device 130 may transmit the second HARQ-ACK information to the network device 110. The second HARQ-ACK information corresponds to the second DCI in the second PDCCH. In some embodiments, the second HARQ-ACK information may be transmitted to the TRP 120-2.

[0157] In block 420, if the condition is met, the terminal device 130 applies the first TCI state. In some embodiments, the terminal device 130 may apply the first TCI state to all PUCCHs. Alternatively, the terminal device 130 may apply the first TCI state to a subset of PUCCHs. For example, some PUCCHs (e.g., represented as PUCCH_na) may be configured to apply or not apply the indicated TCI state. In some embodiments, not applying the first TCI state may be conditionally configured if the CORESET is configured to not apply the indicated TCI state. The PUCCHs that do not apply the indicated TCI state may be applied to HARQ-ACK feedback for PDSCHs scheduled by the CORESET (that does not apply the indicated TCI state).

[0158] In some embodiments, the condition may include that at least one bit value of the HARQ-ACK information corresponding to the first DCI or corresponding to a PDSCH scheduled by the first DCI is ACK.

[0159] In some embodiments, the condition may include that the first TCI state is set for a TCI update in a unified TCI framework. Alternatively or additionally, the condition may include that the first TCI state is a unified TCI state. In some embodiments, the condition may include that the first TCI state is set to have tci-StateId-r17. In some embodiments, the condition may be labeled with a parameter where the first TCI state is tci-StateId-r17 or r17. In some other embodiments, the condition may include that the first TCI state is different from a seventh TCI state. The seventh TCI state may be at least one of a previous applied unified TCI state, a previous indicated unified TCI state, or a currently applied unified TCI state.

[0160] In some embodiments, the condition may include that the first DCI is not a DCI that schedules a semi-persistent scheduling (SPS) activation. Alternatively or additionally, the condition may include that the first DCI is not a DCI that schedules an SPS release. In other embodiments, the condition may include that the first DCI is a DCI that carries a unified TCI state or a TCI state for a TCI state update or a TCI state configured to have tci-StateId-r17. In some embodiments, the condition may include that the first PDCCH is not a PDCCH in a control resource set (CORESET) that is not configured to share or apply the unified TCI state. Alternatively or additionally, the condition may include that the first PDCCH is a PDCCH in a CORESET that is configured to share or apply the unified TCI state.

[0161] In some embodiments, the HARQ-ACK information may include two or more HARQ-ACK information bits. Alternatively or additionally, the PDSCH may include two transport blocks, where each transport block may correspond to one HARQ-ACK information bit. In some other embodiments, the PDSCH may include one transport block. In some embodiments, the at least one transport block in the PDSCH may include two or more Code Block Groups (CBGs), where each CBG may correspond to one HARQ-ACK information bit.

[0162] In some embodiments, as described above, the terminal device 130 may receive the first PDCCH and the second PDCCH. In this case, the condition may include that the transmission of the first HARQ-ACK information is later than or subsequent to the transmission of the second HARQ-ACK information. In some embodiments, the condition may include that the transmission of the first HARQ-ACK information is earlier than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH. In some embodiments, the condition may include that the start symbol or end symbol of the resource for the transmission of the first HARQ-ACK information is earlier than the start symbol or end symbol of the resource for the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH. In some embodiments, if the transmission of the first HARQ-ACK information is after or later than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is before or earlier than the end symbol of the second PDCCH, the terminal device 130 may decide to ignore or not apply the first TCI state.

[0163] In some embodiments, terminal device 130 may receive or detect a first DCI in a PDCCH in a first subset (e.g., M1) of the CORESET, where the first DCI may indicate a first TCI state. In some embodiments, terminal device 130 may receive or detect a second DCI in a second PDCCH in a second subset (e.g., M2) of the CORESET, where the second DCI may indicate a second TCI state. For example, the first TCI state and the second TCI state may be different. For example, at least one of the downlink TCI state, the uplink TCI state, and the combined TCI state of the first TCI state may be different from at least one of the downlink TCI state, the uplink TCI state, and the combined TCI state of the second TCI state. In some embodiments, terminal device 130 may transmit first HARQ-ACK information for the first DCI or for a PDSCH scheduled by the first DCI. For example, the first HARQ-ACK information may be transmitted in a first uplink resource. For example, the first uplink resource may be a first PUCCH resource or a first PUSCH resource. In some embodiments, the terminal device 130 may transmit second HARQ-ACK information for a second DCI or for a PDSCH scheduled by a second DCI. For example, the second HARQ-ACK information may be transmitted in a second uplink resource. For example, the second uplink resource may be a second PUCCH resource or a second PUSCH resource. In some embodiments, the first uplink resource may be different from the second uplink resource.

[0164] In some embodiments, the first TCI state may be applied after a first application timing, which may be a first slot or a first subslot that is Y symbols after the last symbol of the first app link resource. In some embodiments, the second TCI state may be applied after a second application timing, which may be a first slot or a first subslot that is Y symbols after the last symbol of the second app link resource.

[0165] In some embodiments, the first PDCCH may be earlier or earlier than the second PDCCH. For example, at least one of the start symbol, the first symbol, the end symbol and the last symbol of the first PDCCH may be earlier or earlier than at least one of the start symbol, the first symbol, the end symbol and the last symbol of the second PDCCH. In some embodiments, the first uplink resource may be later or later than the second uplink resource. For example, at least one of the slot, the start symbol, the first symbol, the end symbol and the last symbol of the first uplink resource may be later or later than at least one of the slot, the start symbol, the first symbol, the end symbol and the last symbol of the second uplink resource. In some embodiments, the first application timing may be later or later than the second application timing. In some embodiments, the first TCI state may not be applied or may be ignored after the first application timing. In some embodiments, at least one of the HARQ-ACK information bits in the first HARQ-ACK information may be an ACK. In some embodiments, at least one of the HARQ-ACK information bits in the second HARQ-ACK information may be an ACK. In some embodiments, the first HARQ-ACK information may be in a first HARQ-ACK codebook in a first uplink resource. In some embodiments, the second HARQ-ACK information may be in a second HARQ-ACK codebook in a second uplink resource.

[0166] In some embodiments, in the first HARQ-ACK codebook in the first uplink resource, a TCI state indicated in the first PDCCH (if present) before or earlier than the second PDCCH is not applied after the beam application timing (e.g., even if different from the current TCI state), HARQ-ACK information corresponding to the first PDCCH is included in the first HARQ-ACK codebook, and HARQ-ACK information corresponding to the second PDCCH is included in the second HARQ-ACK codebook, where the second PDCCH is a PDCCH having an indication of a TCI state that has already been applied or will be applied based on the second HARQ-ACK codebook in the second uplink resource, and the second HARQ-ACK codebook is any one earlier than the first HARQ-ACK codebook in the first uplink resource or the last HARQ-ACK codebook (e.g., the last uplink resource).

[0167] In some embodiments, to determine the TCI state to be applied after the application timing, only TCI states indicated in a PDCCH that is later than or subsequent to the PDCCH indicating the TCI state to be applied are considered.

[0168] In some embodiments, if the CORESET is configured not to share or apply the indicated TCI state (i.e., the first TCI state), the TCI state for the PDCCH in the CORESET may be activated by the MAC CE. If M is greater than 1, the CORESET may still be included in one of the M subsets of the CORESET. The TCI state for the PDSCH in the CORESET may follow the PDCCH or be indicated in the TCI field.

[0169] In some embodiments, the spatial relationship information for PUSCHs scheduled by a PDCCH may be applied to all or a subset of PUCCHs corresponding to the subset of the CORESET, or may be according to the UL TCI or combined TCI indicated / applied by PDCCHs in the same subset of the CORESET that share / apply the indicated Rel-17 TCI state. For example, the terminal device 130 may apply a spatial domain filter to a subset of PUSCHs corresponding to a subset of the CORESET as associated with an uplink TCI state. Alternatively, the terminal device 130 may apply a spatial domain filter to a subset of PUSCHs corresponding to a subset of the CORESET as associated with a combined TCI state. In some other embodiments, the terminal device 130 may apply the spatial domain filter to all PUSCHs corresponding to a subset of the CORESET as associated with an uplink TCI state. In some embodiments, the terminal device 130 may apply the spatial domain filter to all PUSCHs corresponding to a subset of the CORESET as associated with a combined TCI state. Additionally, terminal device 130 may apply the spatial domain filter to a subset of PUSCHs indicated by a PDCCH in a subset of a CORESET that applies a first TCI state as associated with the uplink TCI state or combined TCI state. In some embodiments, terminal device 130 may apply the spatial domain filter to all PUSCHs indicated by a PDCCH in a subset of a CORESET that applies a first TCI state as associated with the uplink TCI state or combined TCI state.

[0170] Alternatively, the spatial relationship information for the PDCCH-scheduled PUSCH may be according to the TCI state for the PDCCH or the PDSCH. For example, terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the third TCI state. Alternatively, terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the fourth TCI state.

[0171] In some other embodiments, the spatial relationship information for the PUSCH scheduled by the PDCCH may follow the TCI state configured / activated for the PUCCH with the lowest index among PUCCH_na (at least for the PUSCH scheduled by DCI format 0_0). For example, the terminal device 130 may apply a spatial domain filter to the PUSCH scheduled by the third PDCCH as associated with the fifth TCI state. In this case, the fifth TCI state may be configured for the PUCCH with the lowest index among the PUCCHs, and the PUCCH may be configured not to share or apply the unified TCI state.

[0172] In some embodiments, the spatial relationship information for the PUCCHs may be according to an UL TCI or combined TCI that is applied to all or a subset of the PUCCHs corresponding to a subset of a CORESET. For example, terminal device 130 may apply a spatial domain filter to a subset of the PUCCHs corresponding to the subset of a CORESET as associated with an uplink TCI state or combined TCI state. In other embodiments, terminal device 130 may apply the spatial domain filter to all PUCCHs corresponding to the subset of a CORESET as associated with an uplink TCI state or combined TCI state.

[0173] Alternatively, the spatial relationship information for the PUCCH may be according to the TCI state for the PDCCH or the PDSCH. For example, the terminal device 130 may apply the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the third TCI state. In another embodiment, the terminal device 130 may apply the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the fourth TCI state.

[0174] In some embodiments, the spatial relationship information for the PUCCH may be according to the TCI state configured / activated for the PUCCH_na, for example, the terminal device 130 may apply a spatial domain filter to the PUCCH as associated with the sixth TCI state, where the sixth TCI state is configured for the PUCCH.

[0175] In some embodiments, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH and the second number of subsets of PUCCH or PUSCH is 1, the HARQ-ACK feedback mode is set to be separate. In this case, according to the determination that there are two PUCCHs with HARQ-ACK information in one slot, the terminal device 130 may multiplex the HARQ-ACK information in one PUCCH. For example, if M≧2, N=1, the HARQ-ACK feedback mode may be assumed or expected to be combined. Alternatively, if the HARQ-ACK feedback mode is set as separate and there are two PUCCHs with HARQ-ACK information in one slot, the HARQ-ACK information may be multiplexed in one PUCCH and transmitted in a later or earlier PUCCH resource or with a lower ID. The two PUCCH resources may overlap in symbols.

[0176] In some embodiments, in case of separate HARQ-ACK feedback modes or one-to-one mapping between M and N (M=N>1), the determined / indicated PUCCH resource index within a PDCCH in one subset of M may be a relative index within one subset of N that corresponds to a subset of CORESET. For example, a PUCCH resource group may be reused for a subset of PUCCHs. Alternatively, in case of the PUCCH resource index being absolute (or indexed across N subsets), the determined / indicated PUCCH resource index within a PDCCH in one subset of M may not be expected to be a PUCCH included in a subset of PUCCHs that does not correspond to a subset of CORESET.

[0177] 5 is a flow chart of an example method 500 according to an embodiment of the present disclosure. The method 500 may be implemented in any suitable device. For illustrative purposes only, the method 500 may be implemented in the network device 110-1 as shown in FIG.

[0178] In block 510, the network device 110 transmits a second PDCCH to the terminal device 130. The second PDCCH includes a second DCI. The second DCI indicates a second TCI status. In some embodiments, the second PDCCH may be received from the TRP 120-2.

[0179] In block 520, the network device 110 transmits a first PDCCH to the terminal device 130. The first PDCCH includes a first DCI. The first DCI indicates a first TCI status. In some embodiments, the first PDCCH may be received from the TRP 120-1.

[0180] At block 530, the network device 110 receives first HARQ-ACK information from the terminal device 130. The first HARQ-ACK information corresponds to the first DCI in the first PDCCH. In some embodiments, the first HARQ-ACK information may be transmitted to the TRP 120-1.

[0181] At block 540, the network device 110 receives second HARQ-ACK information from the terminal device 130. The second HARQ-ACK information corresponds to a second DCI in the second PDCCH. In some embodiments, the second HARQ-ACK information may be transmitted to the TRP 120-2.

[0182] In some embodiments, a terminal device comprises a circuit configured to: transmit, in the terminal device, to a network device, first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to first downlink control information (DCI) in a first physical downlink control channel (PDCCH), the first DCI indicating a first transmission configuration indicator (TCI) state, and apply the first TCI state in response to a condition being met.

[0183] In some embodiments, the condition comprises: at least one bit value of the HARQ-ACK information corresponding to the first DCI or corresponding to a physical downlink shared channel (PDSCH) scheduled by the first DCI is an acknowledgement (ACK); the first TCI state is configured for TCI updating in a unified TCI framework; the first TCI state is a unified TCI state; the first TCI state is configured to have tci-StateId-r17; the first TCI state is marked with a parameter that is tci-StateId-r17 or r17; the first TCI state is different from a seventh TCI state, which is at least one of a previous applied unified TCI state, a previous indicated unified TCI state, or a currently applied unified TCI state; the DCI is not a DCI scheduling semi-persistent scheduling (SPS) activation, the first DCI is not a DCI scheduling SPS release, the first DCI is a DCI carrying a unified TCI state or a TCI state for TCI state update or a TCI state configured to have tci-StateId-r17, the first PDCCH is not a PDCCH in a control resource set (CORESET) that is not configured to share or apply the unified TCI state, or the first PDCCH is a PDCCH in a CORESET that is configured to share or apply the unified TCI state.

[0184] In some embodiments, the HARQ-ACK information includes two or more HARQ-ACK information bits.

[0185] In some embodiments, the PDSCH includes two transport blocks, each transport block corresponding to one HARQ-ACK information bit.

[0186] In some embodiments, the PDSCH comprises one transport block.

[0187] In some embodiments, at least one transport block in the PDSCH includes two or more Code Block Groups (CBGs), each CBG corresponding to one HARQ-ACK information bit.

[0188] In some embodiments, the terminal device comprises a circuit, the circuit being configured in the terminal device to transmit to the network device second HARQ-ACK information corresponding to a second DCI in a second PDCCH, the second DCI indicating a second TCI state.

[0189] In some embodiments, the conditions include at least one of: the transmission of the first HARQ-ACK information is later than or later than the transmission of the second HARQ-ACK information; the transmission of the first HARQ-ACK information is earlier than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH; or the start symbol or end symbol of a resource for the transmission of the first HARQ-ACK information is earlier than the start symbol or end symbol of a resource for the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH.

[0190] In some embodiments, the terminal device comprises a circuit configured to determine to ignore or not apply the first TCI state when the transmission of the first HARQ-ACK information is after or later than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is before or earlier than the end symbol of the second PDCCH.

[0191] In some embodiments, if the first number of subsets of the CORESET is not greater than the second number of subsets of the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), the HARQ-ACK feedback modes are configured to be separate.

[0192] In some embodiments, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH, and the first group of subsets of CORESET corresponds to the first group of subsets of PUCCH or PUSCH and the second group of subsets of CORESET corresponds to the second group of subsets of PUCCH or PUSCH, then the first HARQ-ACK feedback mode within the first group of subsets of CORESET or the second group of subsets of CORESET is configured to be combined, and the second HARQ-ACK feedback mode between the first and second groups of subsets of CORESET is configured to be separate.

[0193] In some embodiments, if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH and the second number of subsets of PUCCH or PUSCH is 1, the HARQ-ACK feedback mode is configured to be combined.

[0194] In some embodiments, the HARQ-ACK feedback mode is configured to be separate if the first number of subsets of CORESET is greater than the second number of subsets of PUCCH or PUSCH and the second number of subsets of PUCCH or PUSCH is 1. The terminal device comprises a circuit, the circuit configured to multiplex the HARQ-ACK information in one PUCCH according to a determination that there are two PUCCHs having HARQ-ACK information in one slot.

[0195] In some embodiments, the terminal device comprises circuitry configured to apply the first TCI state to all PUCCHs or to apply the first TCI state to a subset of PUCCHs.

[0196] In some embodiments, the terminal device comprises a circuit configured to receive activation of a third TCI state for a CORESET configured in a media access control control element (MAC CE) to not share or apply the unified TCI state, receive a third PDCCH in the CORESET scheduling a third PDSCH, and apply at least one quasi-co-location (QCL) parameter as associated with the third TCI state for the third PDSCH or apply at least one QCL parameter as associated with a fourth TCI state, the fourth TCI state being indicated for the third PDSCH in a TCI field in the third PDCCH.

[0197] In some embodiments, there is no scheduling of a PUSCH for a third PDCCH in the CORESET.

[0198] In some embodiments, the terminal device comprises a circuit configured to: apply a spatial domain filter to a subset of PUSCHs corresponding to a subset of a CORESET as associated with an uplink TCI state; apply a spatial domain filter to a subset of the PUSCHs corresponding to the subset of the CORESET as associated with a combined TCI state; apply the spatial domain filter to all PUSCHs corresponding to the subset of the CORESET as associated with the uplink TCI state; apply the spatial domain filter to all PUSCHs corresponding to the subset of the CORESET as associated with the combined TCI state; apply the spatial domain filter to a subset of PUSCHs indicated by a PDCCH in the subset of the CORESET that applies the first TCI state as associated with the uplink TCI state or the combined TCI state; or apply the spatial domain filter to all PUSCHs indicated by a PDCCH in the subset of the CORESET that applies the first TCI state as associated with the uplink TCI state or the combined TCI state.

[0199] In some embodiments, the terminal device comprises a circuit configured to apply a spatial domain filter to a PUSCH scheduled by a third PDCCH associated with a third TCI state, or to apply a spatial domain filter to a PUSCH scheduled by a third PDCCH associated with a fourth TCI state.

[0200] In some embodiments, the terminal device comprises a circuit, the circuit being configured to apply a spatial domain filter to a PUSCH scheduled by the third PDCCH as associated with a fifth TCI state, the fifth TCI state being configured for a PUCCH having a lowest index among the PUCCHs, and the PUCCH being configured not to share or apply the unified TCI state.

[0201] In some embodiments, the terminal device may comprise a circuit, the circuit being configured to apply a spatial domain filter to a subset of PUCCHs corresponding to a subset of the CORESET as associated with an uplink TCI state or the combined TCI state, or to apply the spatial domain filter to all PUCCHs corresponding to a subset of the CORESET as associated with the uplink TCI state or the combined TCI state.

[0202] In some embodiments, the terminal device comprises a circuit configured to apply the spatial domain filter to a PUCCH for a third HARQ-ACK information transmission corresponding to a third PDSCH scheduled by the third PDCCH as associated with the third TCI state, or to apply the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the fourth TCI state.

[0203] In some embodiments, the terminal device may comprise a circuit, the circuit may be configured to apply a spatial domain filter to the PUCCH as associated with a sixth TCI state, the sixth TCI state being configured for the PUCCH.

[0204] 6 is a schematic block diagram of an apparatus 600 suitable for implementing embodiments of the present disclosure. The apparatus 600 may be considered as another exemplary implementation of the network apparatus 110 or the terminal apparatus 130 shown in FIG. 1. Thus, the apparatus 600 may be implemented in or as at least a part of the network apparatus 110 or the terminal apparatus 130 as shown in FIG.

[0205] As shown, the apparatus 600 comprises a processor 610, a memory 620 coupled to the processor 610, a suitable transmitter (TX) and receiver (RX) 640 coupled to the processor 610, and a communication interface coupled to the TX / RX 640. The memory 610 stores at least a portion of a program 630. The TX / RX 640 is used for bidirectional communication. The TX / RX 640 has at least one antenna to facilitate communication, although the access nodes referred to herein may in practice have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME) / Serving-GateWay (S-GW) and an eNB, an Un interface for communication between an eNB and a Relay Node (RN), or an Uu interface for communication between an eNB and a terminal device.

[0206] The program 630 is assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 1-5. The embodiments of the present disclosure may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 610 and the memory 620 may form a processing means 650 suitable for implementing various embodiments of the present disclosure.

[0207] The memory 620 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. Although only one memory 620 is shown in the device 600, there may be several physically different memory modules in the device 600. The processor 610 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP) and a processor based on a multi-core processor architecture. The device 600 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0208] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure have been illustrated and described using block diagrams, flow charts, or some 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 examples, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0209] 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 a program module, that execute in a device on a target real or virtual processor to perform the process or method described above with reference to Figures 1-5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as appropriate. The machine-executable instructions of the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.

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

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

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

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

[0214] As used herein, the term "terminal device" refers to any device having wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (Iota) devices, Ultra-Reliable Low Latency Communications (URLLC) devices, Internet of Anything (Iowa) devices, machine type communication (MTC) devices, vehicle-mounted devices for V2X communications where X stands for pedestrian, vehicle, or infrastructure / network, devices for integrated access and integrated access and backhaul (IAB), satellite-based or airborne vehicles in non-terrestrial networks (NTN) including High Altitude Platforms (HAPs) including satellites and Unmanned Aircraft Systems (UASs), extended reality (XR) devices including different types of reality such as augmented reality (AR), mixed reality (MR), virtual reality (VR), unmanned aerial vehicles (UAVs), which are aircraft without a human pilot and commonly referred to as drones, high speed trains (HSTs), and other types of real-world applications. These include, but are not limited to, devices on a train, image capture devices such as digital cameras, sensor game devices, music storage and playback devices, or Internet appliances that allow wireless or wired Internet access and browsing. The "Terminal Device" may further have "multicast / broadcast" capabilities to support public safety and mission-critical V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, wireless services, over-the-air software distribution, group communication, and Iota applications. It may also incorporate one or more Subscriber Identity Modules (SIMs), known as multi-SIMs.The term "terminal equipment" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless equipment.

[0215] The term "network device" refers to a device capable of providing or hosting a cell or coverage in which a terminal device can communicate. Examples of network devices include, but are not limited to, a Node B (node ​​or NB), an evolved node (node ​​or eNB), a next generation node (gNB), a transmit / receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an IAB node, a femto node, a pico node, a low power node such as a reconfigurable intelligent surface (RIS), etc.

[0216] The terminal device or network device may have the capability of artificial intelligence (AI) or machine learning. Generally, it includes a model trained from a large amount of data collected for a specific function and can be used to predict some information.

[0217] The terminal device or network device may operate on several frequency ranges, such as FR1 (410 MHz-7125 MHz), FR2 (24.25 GHz-71 GHz), frequency bands greater than 100 GHz, and Tera Hertz (THz). It can also operate on licensed / unlicensed / shared spectrum. The terminal device may have two or more connections with the network device under Multi-Radio Dual Connectivity (MR-DC) application scenarios. The terminal device or network device can operate in full duplex, flexible duplex, and cross division duplex modes.

[0218] Embodiments of the present disclosure may be implemented in test equipment, such as, for example, a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal equipment, a test network equipment, a channel emulator, and the like.

[0219] Embodiments of the present disclosure may be performed in accordance with any generation of communication protocols now known or developed in the future, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or sixth generation (6G) networks.

Claims

1. 1. A method of communication comprising: In a terminal device, transmitting first Hybrid Automatic Repeat request - ACKnowledgement (HARQ-ACK) information corresponding to first Downlink Control Information (DCI) in a first Physical Downlink Control Channel (PDCCH) to a network device, the first DCI indicating a first Transmission Configuration Indicator (TCI) state; applying the first TCI state in response to a condition being satisfied; The method includes:

2. The condition is At least one bit value of the HARQ-ACK information corresponding to the first DCI or corresponding to a Physical Downlink Shared CHANNEL (PDSCH) scheduled by the first DCI is an acknowledgement (ACK); the first TCI state is configured for TCI update in a unified TCI framework; the first TCI state being a unified TCI state; the first TCI state is set to have tci-StateId-r17; the first TCI state being identified with a parameter that is tci-StateId-r17 or r17; the first TCI state is different from a seventh TCI state, which is at least one of a previous applied unified TCI state, a previous indicated unified TCI state, or a currently applied unified TCI state; The first DCI is not a DCI for scheduling a semi-persistent scheduling (SPS) activation; The first DCI is not a DCI for scheduling an SPS release; the first DCI is a DCI conveying a unified TCI state or a TCI state for TCI state update or a TCI state configured to have tci-StateId-r17; The first PDCCH is not a PDCCH in a control resource set (CORESET) or a reference signal (RS) that is not configured to share or apply the unified TCI state; or The first PDCCH is a PDCCH in a CORESET configured to share or apply the unified TCI state; The method of claim 1 , comprising at least one of:

3. The HARQ-ACK information includes two or more HARQ-ACK information bits. The method of claim 2.

4. The PDSCH includes two transport blocks, each of which corresponds to one HARQ-ACK information bit. The method of claim 2.

5. The PDSCH includes one transport block. The method of claim 2.

6. At least one transport block in the PDSCH includes two or more Code Block Groups (CBGs), each CBG corresponding to one HARQ-ACK information bit. The method of claim 2.

7. The method further includes, in the terminal device, transmitting second HARQ-ACK information corresponding to a second DCI in a second PDCCH to the network device, wherein the second DCI indicates a second TCI state. The method of claim 1.

8. The condition is the transmission of the first HARQ-ACK information is subsequent to or subsequent to the transmission of the second HARQ-ACK information; the transmission of the first HARQ-ACK information is earlier than the transmission of the second HARQ-ACK information, and the end symbol of the first PDCCH is later than the end symbol of the second PDCCH; or a start symbol or an end symbol of a resource for transmitting the first HARQ-ACK information is earlier than a start symbol or an end symbol of a resource for transmitting the second HARQ-ACK information, and an end symbol of the first PDCCH is later than an end symbol of the second PDCCH; The method of claim 7, comprising at least one of:

9. determining to ignore or not apply the first TCI state if the transmission of the first HARQ-ACK information is after or later than the transmission of the second HARQ-ACK information and the end symbol of the first PDCCH is before or earlier than the end symbol of the second PDCCH; The method of claim 1 further comprising:

10. If the first number of subsets of the CORESET is not greater than the second number of subsets of the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), the HARQ-ACK feedback modes are configured to be separate. The method of claim 1.

11. If the first number of subsets of the CORESET is greater than the second number of subsets of the PUCCH or PUSCH, and the first group of subsets of the CORESET corresponds to the first group of subsets of the PUCCH or PUSCH, and the second group of subsets of the CORESET corresponds to the second group of subsets of the PUCCH or PUSCH, A first HARQ-ACK feedback mode in the first group of subsets of a CORESET or the second group of subsets of a CORESET is configured to be combined; A second HARQ-ACK feedback mode between the first and second groups of subsets of CORESET is configured to be distinct. The method of claim 1.

12. If the first number of subsets in the CORESET is greater than the second number of subsets of the PUCCH or PUSCH, and the second number of subsets of the PUCCH or PUSCH is 1, the HARQ-ACK feedback mode is configured to be combined. The method of claim 1.

13. If the first number of the subsets of the CORESET is greater than the second number of the subsets of the PUCCH or the PUSCH, and the second number of the subsets of the PUCCH or the PUSCH is 1, the HARQ-ACK feedback modes are configured to be separate, and the method includes: and multiplexing the HARQ-ACK information in one PUCCH according to determining that there are two PUCCHs having HARQ-ACK information in one slot. The method of claim 1.

14. Applying the first TCI condition comprises: applying the first TCI state to all PUCCHs; or applying the first TCI state to a subset of PUCCHs; 2. The method of claim 1, comprising:

15. receiving, in a media access control control element (MAC CE), an activation of a third TCI state for a CORESET configured to not share or apply the unified TCI state; receiving, in the CORESET, a third PDCCH scheduling a third PDSCH; applying at least one Quasi Co-Location (QCL) parameter as associated with the third TCI state for the third PDSCH or applying at least one QCL parameter as associated with a fourth TCI state, the fourth TCI state being indicated for the third PDSCH in a TCI field in the third PDCCH; The method of claim 1 further comprising:

16. There is no scheduling of PUSCH for the third PDCCH in the CORESET. The method of claim 15.

17. applying a spatial domain filter to a subset of the PUSCH corresponding to a subset of the CORESET as associated with an uplink TCI state; applying a spatial domain filter to the subset of PUSCHs corresponding to the subset of CORESETs as associated with a combined TCI state; applying the spatial domain filter to all PUSCHs corresponding to the subset of CORESETs as associated with the uplink TCI state; applying the spatial domain filter to all PUSCHs corresponding to the subset of CORESETs as associated with the associated TCI state; applying the spatial domain filter to a subset of PUSCHs indicated by a PDCCH in the subset of CORESETs to which the first TCI state applies as associated with the uplink TCI state or the combined TCI state; or applying the spatial domain filter to all PUSCHs indicated by PDCCHs in the subset of CORESETs to which the first TCI state applies as associated with the uplink TCI state or the combined TCI state; The method of claim 15 further comprising one of:

18. applying a spatial domain filter to a PUSCH scheduled by the third PDCCH as associated with the third TCI state; or applying a spatial domain filter to a PUSCH scheduled by the third PDCCH as associated with the fourth TCI state; The method of claim 15 further comprising one of:

19. and applying a spatial domain filter to a PUSCH scheduled by the third PDCCH as associated with a fifth TCI state, the fifth TCI state being configured for a PUCCH having a lowest index among the PUCCHs, the PUCCH being configured not to share or apply the unified TCI state. The method of claim 15.

20. applying a spatial domain filter to a subset of PUCCHs corresponding to a subset of said CORESET as associated with an uplink TCI state or said combined TCI state; or applying the spatial domain filter to all PUCCHs corresponding to a subset of the CORESET as associated with the uplink TCI state or the combined TCI state; The method of claim 15 further comprising one of:

21. applying the spatial domain filter to a PUCCH for a third HARQ-ACK information transmission corresponding to a third PDSCH scheduled by the third PDCCH as associated with the third TCI state; or applying the spatial domain filter to the PUCCH for the third HARQ-ACK information transmission corresponding to the third PDSCH scheduled by the third PDCCH as associated with the fourth TCI state; 20. The method of claim 16, further comprising one of:

22. and applying a spatial domain filter to the PUCCH as associated with a sixth TCI state, the sixth TCI state being configured for the PUCCH.

17. The method of claim 16.

23. 1. A terminal device comprising: a processor; and a memory coupled to the processor and storing instructions, The instructions, when executed by the processor, perform a method according to any one of claims 1 to 22. Terminal device.

24. storing instructions which, when executed on at least one processor, cause said at least one processor to carry out a method according to any one of claims 1 to 22; Computer-readable medium.

Images