Method and device for determining TCI state

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present invention relates to a method and an apparatus for determining a transmission configuration indication (TCI) state in a wireless communication system. A method performed by a user equipment (UE) includes receiving downlink control information (DCI) indicating a first TCI state in a first control resource set (CORESET); and receiving, in radio resource control (RRC) signaling, (i) a first indicator that configures a value of the CORESETPoolIndex associated with the first CORESET, and (ii) a second indicator. The method further includes: identifying an association between a value of the CORESETPoolIndex and the first TCI state based on the first indicator; identifying, based on the second indicator, whether reception is enabled while the indicated TCI state can be applied; and determining, based on the identification, one or more spatial filters for receiving a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied, wherein the PDSCH is associated with a value of the CORESETPoolIndex.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems. More particularly, the present disclosure relates to determining a transmission configuration indication (TCI) state in a wireless communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands (including 28 GHz and 39 GHz) called millimeter waves. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz (THz) frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC) and massive machine type communication (mMTC), standardization of the following technologies is already underway: beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance; support parameter sets (e.g., operating multiple subcarrier spacings) for efficient use of millimeter wave resources and dynamic operation of time slot formats; initial access technology, definition and operation of bandwidth part (BWP) for supporting multi-beam transmission and broadband; new channel coding methods (such as low-density parity check (LDPC) codes for large-scale data transmission and polarization codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions on the improvement and performance enhancement of initial 5G mobile communication technology are ongoing, and there is already physical layer standardization on technologies such as: Vehicle-to-Everything (V2X) technology, which is used for autonomous vehicles to assist driving decisions and improve user convenience based on information about the location and status of the vehicle transmitted by the vehicle; New Radio Unlicensed (NR-U), which aims to ensure that the system operates in compliance with various regulatory requirements in unlicensed frequency bands; NR UE energy saving; Non-Terrestrial Network (NTN); which is UE-satellite direct communication used to provide coverage in areas where terrestrial network communications are not available; and positioning.

[0005] In addition, the following technologies are being standardized in terms of air interface architecture / protocols: Industrial Internet of Things (IIoT) to support new services through interworking and integration with other industries; Integrated Access and Backhaul (IAB) to provide nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; Mobility Enhancement, including conditional handover and dual active protocol stack (DAPS) handover; and Two-step Random Access (2-step RACH for NR) to simplify the random access process. The following technologies are also being standardized in terms of system architecture / services: 5G baseline architecture (e.g., service-based architecture or service-based interface) to combine network function virtualization (NFV) and software-defined network (SDN) technologies; and Mobile Edge Computing (MEC) to receive services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, and it is therefore expected that there will be a need to enhance the functions and performance of 5G mobile communication systems and the integrated operation of connected devices. To this end, new research related to the following technologies is planned: Extended Reality (XR) for effectively supporting Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance improvement and complexity reduction through Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve not only as a basis for developing the following technologies: new waveforms for securing coverage in the terahertz band for 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS), but will also serve as a basis for developing the following technologies: full-duplex technologies for enhancing frequency efficiency and improving system networks for 6G mobile communication technology; AI-based communication technologies for achieving system optimization using satellites and AI from the design stage and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for achieving services at a complexity level that exceeds the limits of UE operating capabilities by leveraging ultra-high-performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Currently, there is a need for enhanced determination of Transmission Configuration Indication (TCI) status in wireless communication systems.

[0010] Technical Solution

[0011] The present disclosure relates to wireless communication systems, and more particularly, to determining TCI status in wireless communication systems.

[0012] In one embodiment, a UE is provided. The UE includes a transceiver configured to: receive downlink control information (DCI) indicating a first TCI state in a first control resource set (CORESET); and receive (i) a first indicator configuring a value of CORESETPoolIndex associated with the first CORESET and (ii) a second indicator in radio resource control (RRC) signaling. The UE also includes a processor operably connected to the transceiver. The processor is configured to: identify an association between the value of CORESETPoolIndex and the first TCI state based on the first indicator; identify whether to enable simultaneous reception before the indicated TCI state can be applied based on the second indicator; and determine one or more spatial filters for receiving a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied based on the identification, wherein the PDSCH is associated with the value of CORESETPoolIndex.

[0013] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to: transmit DCI indicating a first TCI state in a first CORESET; and transmit (i) a first indicator configuring a value of CORESETPoolIndex associated with the first CORESET and (ii) a second indicator in RRC signaling. The first indicator indicates a first indication of an association between the value of CORESETPoolIndex and the first TCI state. The second indicator indicates whether a second indication received simultaneously before the indicated TCI state can be applied is enabled. One or more spatial filters associated with a PDSCH before the indicated TCI state can be applied are indicated based on the first indication and the second indication. The PDSCH is associated with the value of CORESETPoolIndex.

[0014] In yet another embodiment, a method for operating a UE is provided. The method includes: receiving a DCI indicating a first TCI state in a first CORESET; and receiving (i) a first indicator configuring a value of CORESETPoolIndex associated with the first CORESET and (ii) a second indicator in RRC signaling. The method also includes: identifying an association between the value of CORESETPoolIndex and the first TCI state based on the first indicator; identifying whether to enable simultaneous reception before the indicated TCI state can be applied based on the second indicator; and determining one or more spatial filters for receiving a PDSCH before the indicated TCI state can be applied based on the identification, wherein the PDSCH is associated with the value of CORESETPoolIndex.

[0015] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.

[0016] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document.The term "connection" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other.The terms "transmit", "receive" and "communication" and their derivatives cover direct and indirect communication.The terms "include" and "comprise" and their derivatives mean including but not limited to.The term "or" is inclusive, meaning and / or.The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, included in, connected to, connected to, connected to, connected to, connected to, can communicate with, collaborate with, interlace, juxtapose, be adjacent to, be coupled to, coupled to, have, have characteristics, have a relationship with, or have a relationship with, etc.The term "controller" means any device, system or part thereof that controls at least one operation.Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware.The function associated with any particular controller can be centralized or distributed, whether local or remote. The phrase "at least one of" when used with a list of items means that different combinations of one or more of the listed items may be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0017] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation with a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit instantaneous electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and then rewrite data, such as rewritable optical disks or erasable memory devices.

[0018] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0019] Advantageous Effects of the Invention

[0020] According to various embodiments of the present disclosure, determining a transmission configuration indication (TCI) state in a wireless communication system may be efficiently enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0022] Figure 1 An example of a wireless network according to an embodiment of the present disclosure is shown;

[0023] Figure 2 An example of a gNB according to an embodiment of the present disclosure is shown;

[0024] Figure 3 An example of a UE according to an embodiment of the present disclosure is shown;

[0025] Figure 4 shows examples of wireless transmit and receive paths according to the present disclosure;

[0026] Figure 5 shows examples of wireless transmit and receive paths according to the present disclosure;

[0027] Fig. 6A An example of a wireless system beam according to an embodiment of the present disclosure is shown;

[0028] Figure 6B An example of multi-beam operation according to an embodiment of the present disclosure is shown;

[0029] Figure 7 An example of an antenna structure according to an embodiment of the present disclosure is shown;

[0030] Figure 8 An example of a multiple transmission and reception point system according to an embodiment of the present disclosure is shown;

[0031] Fig. 9 An example of determining a default TCI state for PSDCH reception according to an embodiment of the present disclosure is shown;

[0032] Fig.10 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0033] Fig.11 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0034] Fig.12 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0035] Fig.13 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0036] Fig.14 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0037] Fig.15 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0038] Fig.16 An example of a signaling flow for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0039] Fig.17 An example of a signaling flow for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0040] Fig.18 An example of a signaling flow for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0041] Fig.19 An example of a priority rule for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0042] Fig. 20 An example of a priority rule for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0043] Fig.21 An example of following a priority rule to determine a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0044] Fig. 22 An example of following a priority rule to determine a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0045] Fig.23 An example of following a priority rule to determine a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0046] Fig.24 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0047] Fig.25 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0048] Fig.26 An example of determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0049] Fig. 27 An example of TCI code point mapping for a default TCI state according to an embodiment of the present disclosure is shown;

[0050] Fig.28 An example of TCI code point mapping for a default TCI state according to an embodiment of the present disclosure is shown;

[0051] Fig.29An example of a priority rule for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0052] Fig.30 An example of following a priority rule to determine a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown;

[0053] Fig.31 A block diagram of a terminal (or user equipment (UE)) according to an embodiment of the present disclosure is shown; and

[0054] Fig.32 A block diagram of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0055] With all the technical activities around the world for various candidate technologies from industry and academia, the momentum for 5th Generation (5G) or New Radio (NR) mobile communications has been increasing recently. Candidate enablers for 5G / NR mobile communications include massive antenna technology; moving from traditional cellular frequency bands to high frequencies to provide beamforming gain and support increased capacity; new waveforms (e.g., new radio access technologies (RATs)) for flexible adaptation to various services / applications with different requirements; and new multiple access schemes for supporting massive connectivity, among others.

[0056] Discussed below Figures 1 to 32 The various embodiments used to describe the principles of the present disclosure in this patent document are only for illustration and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0057] The following documents are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v16.1.0, "NR; Physical Channels and Modulation"; 3GPP TS 38.212 v16.1.0, "NR; Multiplexing and Channel Coding"; 3GPP TS 38.213 v16.1.0, "NR; Physical Layer Procedures for Control"; 3GPP TS 38.214 v16.1.0, "NR; Physical Layer Procedures for Data"; 3GPP TS 38.321 v16.1.0, "NR; Medium Access Control (MAC) Protocol Description"; and 3GPP TS 38.331 v16.1.0, "NR; Radio Resource Control (RRC) Protocol Description".

[0058] In order to meet the increased demand for wireless data traffic since the deployment of 4G communication systems and to realize various vertical applications, 5G / NR communication systems have been deployed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G / NR communication systems.

[0059] In addition, in 5G / NR communication systems, development of system network improvements is underway based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, and so on.

[0060] The discussion of 5G systems and frequency bands associated therewith is for reference only, as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even higher versions of deployments that may use terahertz (THz) frequency bands.

[0061] the following Figures 1 to 3 Various embodiments are described that are implemented in a wireless communication system and utilizing Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figures 1 to 3 The description is not intended to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0062] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0063] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0064] The gNB 102 provides wireless broadband access to a network 130 for a plurality of first user equipments (UEs) located within a coverage area 120 of the gNB 102. The plurality of first UEs include: a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device such as a cellular phone, a wireless laptop, a wireless PDA, etc. The gNB 103 provides wireless broadband access to the network 130 for a plurality of second UEs within a coverage area 125 of the gNB 103. The plurality of second UEs include UE 115 and UE 116. In some embodiments, one or more of the gNBs 101 to 103 may communicate with each other and with the UEs 111 to 116 using 5G / NR, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A), WiMAX, WiFi, or other wireless communication technologies.

[0065] Depending on the network type, the term "base station" or "BS" may refer to any component (or set of components) configured to provide wireless access to a network (e.g., a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wirelessly capable devices). The base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G / NR 3rd Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user device". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0066] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as generally circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0067] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for determination of TCI status in a wireless communication system. In certain embodiments, one or more of gNBs 101-103 include circuitry, programming, or a combination thereof for determination of TCI status in a wireless communication system.

[0068] Although Figure 1 An example of a wireless network is shown, but Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, gNBs 102 to 103 may each communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks (e.g., external telephone networks or other types of data networks).

[0069] Figure 2 An example gNB 102 is shown according to an embodiment of the present disclosure. Figure 2 The embodiment of gNB 102 shown is for illustration only, and Figure 1 gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 2 The scope of this disclosure is not limited to any particular implementation of the gNB.

[0070] like Figure 2 As shown, the gNB 102 includes multiple antennas 205a to 205n, multiple transceivers 210a to 210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0071] RF transceivers 210a to 210n receive incoming RF signals from antennas 205a to 205n, such as signals transmitted by UEs in network 100. Transceivers 210a to 210n downconvert incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in transceivers 210a to 210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. Controller / processor 225 may further process the baseband signals.

[0072] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or the controller / processor 225 receives analog or digital data (e.g., voice data, network data, email, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-convert the baseband or IF signals into RF signals that are transmitted via the antennas 205a-205n.

[0073] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of UL channel signals and the transmission of DL channel signals by the transceivers 210a to 210n in accordance with well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication functionality. For example, the controller / processor 225 may support beamforming or directional routing operations, in which outgoing / incoming signals from / to multiple antennas 205a to 205n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 225 may support any of a variety of other functionality in the gNB 102.

[0074] The controller / processor 225 is also capable of executing programs and other processes (such as processes for determining TCI status in a wireless communication system) resident in the memory 230. The controller / processor 225 may move data into or out of the memory 230 as required by the executing process.

[0075] The controller / processor 225 is also connected to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 can support communication via any appropriate wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a cellular communication system supporting 5G / NR, LTE, or LTE-A), the interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 can allow the gNB 102 to communicate with a larger network (e.g., the Internet) via a wired or wireless local area network or via a wired or wireless connection. The interface 235 includes any suitable structure such as an Ethernet or transceiver that supports communication via a wired or wireless connection.

[0076] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0077] Although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 Each component shown. In addition, Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0078] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only, and Figure 1 UEs 111 to 115 may have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of the UE.

[0079] like Figure 3 As shown, UE 116 includes antenna 305, transceiver 310, and microphone 320. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, input 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0080] Transceiver 310 receives incoming RF signals transmitted by a gNB of network 100 from antenna 305. Transceiver 310 downconverts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to speaker 330 (e.g., for voice data) or is processed by processor 340 (e.g., for web browsing data).

[0081] The TX processing circuitry in the transceiver 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (e.g., web data, email, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 305.

[0082] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the transceiver 310 to receive DL channel signals and transmit UL channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0083] The processor 340 may also be capable of executing other processes and programs resident in the memory 360, such as processes for determination of TCI status in a wireless communication system.

[0084] Processor 340 can move data into or out of memory 360 as needed by the executing process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0085] Processor 340 is also coupled to input 350 and display 355m, which may include, for example, a touch screen, a keypad, etc. An operator of UE 116 may use input 350 to enter data into UE 116. Display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0086] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0087] Although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The various components in may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Additionally, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0088] Figure 4 and Figure 5 Example wireless transmit and receive paths according to the present disclosure are shown. In the following description, transmit path 400 may be described as being implemented in a gNB (such as, gNB 102), and receive path 500 may be described as being implemented in a UE (such as, UE 116). However, it is understood that receive path 500 may be implemented in a gNB and transmit path 400 may be implemented in a UE. In some embodiments, receive path 500 is configured to support determination of TCI status in a wireless communication system.

[0089] like Figure 4 The transmit path 400 shown includes a channel coding and modulation block 405, a serial to parallel (S to P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P to S) block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. Figure 5The receive path 500 shown includes a down converter (DC) 555, a remove cyclic prefix block 560, a serial to parallel (S to P) block 565, a size N fast Fourier transform (FFT) block 570, a parallel to serial (P to S) block 575, and a channel decoding and demodulation block 580.

[0090] like Figure 4 As shown, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding) and modulates the input bits, for example using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM), to generate a sequence of frequency-domain modulation symbols.

[0091] The serial to parallel block 410 converts (e.g., demultiplexes) the serially modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 102 and the UE 116. The size-N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time domain output signal. The parallel to serial block 420 converts (e.g., multiplexes) the parallel time domain output symbols from the size-N IFFT block 415 to generate a serial time domain signal. The add cyclic prefix block 425 inserts a cyclic prefix into the time domain signal. The up-converter 430 modulates (e.g., up-converts) the output of the add cyclic prefix block 425 to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0092] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and operations opposite to those at gNB 102 are performed at UE 116.

[0093] like Figure 5 As shown, the down converter 555 down-converts the received signal to the baseband frequency, and the remove cyclic prefix block 560 removes the cyclic prefix to generate a serial time domain baseband signal. The serial to parallel block 565 converts the time domain baseband signal to a parallel time domain signal. The size N FFT block 570 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel to serial block 575 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.

[0094] Each of gNBs 101 to 103 may implement a similar method as that for transmitting in the downlink to UEs 111 to 116. Figure 4 The transmission path 400 shown in FIG. 4 and may be implemented similarly to the transmission path 400 received from UEs 111 to 116 in the uplink. Figure 5Receive path 500 is shown. Similarly, each of UEs 111 to 116 can implement transmit path 400 for transmitting to gNBs 101 to 103 in the uplink, and can implement receive path 500 for receiving from gNBs 101 to 103 in the downlink.

[0095] Can be implemented using hardware only or a combination of hardware and software / firmware Figure 4 and Figure 5 As a specific example, Figure 4 and Figure 5 At least some of the components in can be implemented with software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 415 can be implemented as a configurable software algorithm, wherein the value of size N can be modified according to the implementation.

[0096] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. It will be appreciated that the value of the variable N may be any integer (e.g., 1, 2, 3, 4, etc.) for the DFT and IDFT functions, and the value of the variable N may be any integer (e.g., 1, 2, 4, 8, 16, etc.) as a power of two for the FFT and IFFT functions.

[0097] although Figure 4 and Figure 5 Examples of wireless transmit and receive paths are shown, but Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5 The various components in the can be combined, further subdivided or omitted, and additional components can be added according to specific needs. Figure 4 and Figure 5 It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

[0098] The time unit for DL ​​signaling or for UL signaling on a cell is called a time slot and may include one or more symbols. The bandwidth (BW) unit is called a resource block (RB). One RB includes multiple subcarriers (SC). For example, a time slot may have a duration of one millisecond, and a RB may have a bandwidth of 180 KHz and include 12 SCs, where the inter-SC spacing is 15 KHz. A time slot may be a full DL time slot or a full UL time slot, or a mixed time slot similar to a special subframe in a time division duplex (TDD) system.

[0099] DL signals include data signals that convey information content, control signals that convey DL control information (DCI), and reference signals (RS) also known as pilot signals. The gNB transmits data information or DCI through the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). PDSCH or PDCCH can be transmitted through a variable number of time slot symbols including one time slot symbol. In the case where the UE receives the PDCCH, the spatial setting for PDCCH reception can be indicated to the UE based on the configuration of the value of the TCI state of the CORESET. The spatial setting for PDSCH reception can be indicated to the UE based on the configuration of the higher layer or based on the value of the TCI state indicated by the DCI format received by the scheduling PDSCH. The gNB can configure the UE to receive signals on the cell within the DL bandwidth part (BWP) of the cell DL BW.

[0100] The gNB transmits one or more of multiple types of RS including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily intended for UEs to perform measurements and provide channel state information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reports (IMRs), CSI interference measurement (CSI-IM) resources associated with non-zero power CSI-RS (ZP CSI-RS) configurations are used. The CSI process consists of NZP CSI-RS and CSI-IM resources. The UE can determine the CSI-RS transmission parameters through DL control signaling or high-layer signaling (such as RRC signaling from the gNB). The transmission instance of the CSI-RS can be indicated by DL control signaling or configured by high-layer signaling. DMRS is transmitted only in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0101] The UL signal also includes a data signal conveying information content, a control signal conveying a UL control signal (UCI), a DMRS associated with data or UCI demodulation, a sounding RS (SRS) enabling the gNB to perform UL channel measurement, and a random access (RA) preamble enabling the UE to perform random access. The UE transmits data information or UCI through a physical UL shared channel (PUSCH) or a physical UL control channel (PUCCH), respectively. The PUSCH or PUCCH may be transmitted by a variable number of slot symbols including one slot symbol. The gNB may configure the UE to transmit a signal on a cell within the UL BWP of the cell UL BW.

[0102] UCI includes Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a data transport block (TB) in the PDSCH, a Scheduling Request (SR) indicating whether the UE has data in the UE's buffer, and a CSI report that enables the gNB to select appropriate parameters for PDSCH or PDCCH transmissions to the UE. The HARQ-ACK information can be configured to have a smaller granularity than per TB and can be per data code block (CB) or per data CB group, where a TB includes multiple data CBs.

[0103] The CSI report from the UE may include: a channel quality indicator (CQI) that informs the gNB of the maximum modulation and coding scheme (MCS) for the UE to detect a data TB at a predetermined block error rate (BLER) (such as 10% BLER); a precoding matrix indicator (PMI) that informs the gNB how to combine signals from multiple transmitter antennas according to the multiple-input multiple-output (MIMO) transmission principle; and a rank indicator (RI) that indicates the transmission rank of the PDSCH. UL RS includes DMRS and SRS. DMRS is transmitted only in the BW of the corresponding PUSCH or PUCCH transmission. The gNB can use DMRS to demodulate the information in the corresponding PUSCH or PUCCH. SRS is transmitted by the UE to provide UL CSI to the gNB, and for TDD systems, SRS transmission can also provide PMI for DL ​​transmission. In addition, in order to establish synchronization or initial high-layer connection with the gNB, the UE can transmit a physical random access channel.

[0104] In the present disclosure, a beam is determined by either: (1) TCI state, which establishes a quasi co-location (QCL) relationship between a source reference signal (e.g., synchronization signal / physical broadcast channel (PBCH) block (SSB) and / or CSI-RS) and a target reference signal; or (2) spatial relationship information, which establishes an association with a source reference signal (e.g., SSB or CSI-RS or SRS). In either case, the ID of the source reference signal identifies the beam.

[0105] The TCI state and / or the spatial relation reference RS may determine a spatial Rx filter for receiving a downlink channel at the UE or a spatial Tx filter for transmitting an uplink channel from the UE.

[0106] Fig. 6A An example wireless system beam 600 is shown in accordance with an embodiment of the present disclosure. Fig. 6A The illustrated embodiment of wireless system beam 600 is for illustration only.

[0107] like Fig. 6A As shown, in a wireless system, for a device 604, a beam 601 can be characterized by a beam direction 602 and a beam width 603. For example, a device 604 having a transmitter transmits radio frequency (RF) energy in the beam direction and within the beam width. A device 604 having a receiver receives RF energy toward the device in the beam direction and within the beam width. Fig. 6A As shown, device 605 at point A can receive from and transmit to device 604 because point A is within the beamwidth of the beam from device 604 traveling along the beam direction.

[0108] like Fig. 6A As shown, device 606 at point B cannot receive from and transmit to device 604 because B is outside the beamwidth of the beam from device 604 traveling along the beam direction. Although for illustration purposes, Fig. 6A The beams are shown in 2 dimensions (2D), but it may be apparent to one skilled in the art that the beams may be in 3 dimensions (3D), where the beam direction and beam width are defined in space.

[0109] Figure 6B An example multi-beam operation 650 is shown in accordance with an embodiment of the present disclosure. Figure 6B The illustrated embodiment of multi-beam operation 650 is for illustration only.

[0110] In wireless systems, a device can transmit and / or receive on multiple beams. This is called "multi-beam operation" and is Figure 6B Although for illustrative purposes, Figure 6B is in 2D, but it will be apparent to one skilled in the art that the beams may be in 3D, where beams may be transmitted to or received from any direction in space.

[0111] Rel.14 LTE and Rel.15 NR support up to 32 CSI-RS antenna ports, which enables the eNB to be equipped with a large number of antenna elements (such as 64 or 128). In this case, multiple antenna elements are mapped to one CSI-RS port. For mmWave bands, although the number of antenna elements can be larger for a given form factor, the number of CSI-RS ports (which can correspond to the number of digital precoding ports) is often limited due to hardware limitations (e.g., the feasibility of installing a large number of ADCs / DACs at mmWave frequencies, such as Figure 7 shown.

[0112] Figure 7 An example antenna structure 700 is shown in accordance with an embodiment of the present disclosure. Figure 7 The illustrated embodiment of antenna structure 700 is for illustration only.

[0113] In this case, one CSI-RS port maps to a large number of antenna elements that can be controlled by a set of analog phase shifters 701. One CSI-RS port can then correspond to a subarray that produces a narrow analog beam through analog beamforming 705. By changing the phase shifter set between symbols or subframes, this analog beam can be configured to sweep a wider angular range 720. The number of subarrays (equal to the number of RF chains) is proportional to the number of CSI-RS ports N. CSI-PORT The digital beam forming unit 710 performs the same CSI-PORT The analog beams are linearly combined to further increase the precoding gain. While the analog beams are wideband (and therefore not frequency selective), the digital precoding can vary between frequency subbands or resource blocks. Receiver operation can be similarly envisioned.

[0114] Since the aforementioned system utilizes multiple simulated beams for transmission and reception (where one or a small number of simulated beams are selected from a large number of simulated beams, for example, after a training duration performed from time to time), the term "multi-beam operation" is used to refer to the entire system aspect. For illustrative purposes, this includes indicating an assigned DL or UL TX beam (also referred to as "beam indication"); measuring at least one reference signal for calculating and performing beam reporting (also referred to as "beam measurement" and "beam reporting", respectively); and receiving DL or performing UL transmission via selecting a corresponding RX beam.

[0115] The above system is also applicable to higher frequency bands, such as >52.6 GHz. In this case, the system can only use analog beams. 2Absorption (oxygen absorption) losses (about 10 dB additional loss over a distance of 100 m), so a larger number and sharper simulated beams (and therefore a larger number of radiators in the array) may be needed to compensate for the additional path loss.

[0116] Figure 8 An example of a multiple transmit and receive point system 800 according to an embodiment of the present disclosure is shown. Figure 8 The illustrated embodiment of the multiple transmit and receive point system 800 is for illustration only.

[0117] The UE receives downlink control information from the network via one or more PDCCHs. The UE may use the downlink control information to configure one or more reception parameters / settings to decode a subsequent downlink data channel (i.e., PDSCH) transmitted from the network. Under certain settings, the UE may begin receiving and / or decoding the PDSCH after the UE has decoded the PDCCH and obtained the corresponding control information. In this case, the time offset between receiving the PDCCH and receiving the PDSCH exceeds a preconfigured threshold, for example, the preconfigured threshold may correspond to the time required to decode the PDCCH and adjust the reception parameters. The time offset between receiving the PDCCH and the PDSCH may be less than the threshold (e.g., the network may send the PDSCH close to the PDCCH in time or even overlapping with the PDCCH in time).

[0118] In this case, the UE may not be able to decode the PDSCH because they do not have enough time to decode the PDCCH to set the appropriate reception parameters (such as the receive spatial filter) for receiving / decoding the PDSCH. Therefore, one or more default TCI states need to be configured for PDSCH transmission, and therefore, one or more default receive beams need to be configured for the UE to buffer the PDSCH while the UE is in the process of receiving and / or decoding PDCCH control information. In a multi-TRP system ( Figure 8 In the embodiment of the present invention, a UE can simultaneously receive multiple PDSCHs from multiple physically non-co-located TRPs, and the configuration of the default TCI state / receive beam can be different from that of a single TRP operation. In addition, the configuration of the default TCI state / receive beam can also be different between multi-TRP systems based on single DCI (or single PDCCH) and multi-DCI (or multi-PDCCH).

[0119] For multi-TRP operation based on single PDCCH or single DCI, if the time offset between the received PDCCH and the received PDSCH is less than a threshold, the UE may assume that the DMRS ports of the PDSCH follow the QCL parameters indicated by the default TCI state, which may correspond to the lowest code point of the TCI code points containing two different TCI states activated for the PDSCH. For multi-TRP operation based on multiple PDCCH or multiple DCI (assuming CORESETPoolIndex is configured), if the time offset between the received PDCCH and the received PDSCH is less than a threshold, the UE may assume that the DMRS ports of the PDSCH follow the QCL parameters indicated by the default TCI state, which may be used for the PDCCH with the lowest CORESET index in the CORESET configured with the same CORESETPoolIndex value.

[0120] The default TCI state / receive beam configuration in 3GPP Rel.15 / 16 assumes that PDCCH and PDSCH can adopt different beams, and therefore, the UE can use different spatial filters to receive PDCCH and PDSCH beams. If a common TCI state / beam is used / configured for various types of channels (such as PDCCH and PDSCH), the configuration of the default TCI state / receive beam may be different from the existing solution (which, as described above, relies on the lowest CORESET ID / TCI code point). In addition, when configuring the default TCI state for multi-TRP operation, it may also be considered whether the UE can simultaneously receive PDSCH transmitted from a coordinated TRP.

[0121] The present disclosure provides various design options for configuring the default TCI state / receive beam in a multi-TRP system based on single DCI and multiple DCI. Specifically, a common TCI state / beam indication is used as a baseline framework for configuring the default TCI state. The UE may also follow the legacy behavior defined in 3GPP Rel.15 / 16 to determine the default receive beam in certain settings / situations, which is also discussed in the present disclosure.

[0122] Fig. 9 An example of determining a default TCI state 900 for PSDCH reception according to an embodiment of the present disclosure is shown. Fig. 9 The illustrated embodiment of determining a default TCI state 900 for PSDCH reception is for illustration only.

[0123] Common TCI states / beams for various types of channels (such as PDCCH and PDSCH) may be configured / indicated to the UE by the network. Fig. 9In FIG. 1 , a conceptual example of using DCI to indicate a common TCI for both PDCCH and PDSCH is presented. The common TCI signaled in the DCI at time t may take effect at t+timeDurationForQCL. Fig. 9 As shown in the illustrated example, the UE may be able to first decode PDCCH_A (delivering DCI indicating a common TCI) and obtain the necessary QCL parameters.

[0124] The UE can then follow the QCL parameters and set appropriate reception parameters (such as receive spatial filters) to receive and decode PDCCH_0 and PDSCH_0. However, the UE cannot set the receive parameters to decode PDSCH_1 according to the QCL configured in PDCCH_B (which conveys the DCI indicating the common TCI) because the time offset between receiving PDCCH_B and receiving PDSCH_1 is less than timeDurationForQCL. Therefore, the UE may need to follow the QCL indication in the default TCI state to set appropriate reception parameters, such as receive spatial filters (default receive beams). For example, the default TCI state may correspond to the common TCI indicated / configured in PDCCH_A. Depending on whether / how the common TCI state / beam is indicated and / or the synchronized PDSCH reception requirements for multi-TRP operation, there may be various other ways to configure the default TCI state or receive beam.

[0125] Figures 10 to 15 Examples of common TCI status / beam indications 1000 to 1500 in a multi-TRP system according to an embodiment of the present disclosure are shown. Figures 10 to 15 The illustrated embodiments of common TCI status / beam indications 1000 to 1500 in a multi-TRP system are for illustration only.

[0126] In a multi-TRP system based on multiple DCIs, different coordinated TRPs (e.g. Figure 8 TRP-1 and TRP-2 in the UE may transmit separate PDCCHs (and therefore separate PDSCHs) associated with different values ​​of the higher layer signaling index CORESETPoolIndex (if configured) to the UE. For example, Figure 8 TRP-1 in may transmit PDCCH-1 to the UE, and TRP-2 may transmit PDCCH-2 to the UE; PDCCH-1 may be associated with "CORESETPoolIndex=0", and PDCCH-2 may be associated with "CORESETPoolIndex=1"

[0127] In addition, if common TCI state / beam indication is enabled for multi-TRP operation, the UE may be configured with multiple common TCI states / beams (N_tci>1), each corresponding to one coordinated TRP. Under the multi-DCI framework, the common TCI states / beams and therefore their indication PDCCHs may also be associated with CORESETPoolIndex. Fig.10 A conceptual example is provided to characterize the common TCI status / beam indication in a multi-TRP system consisting of two coordinated TRPs. Fig.10 As shown, PDCCH-1_A comes from TRP-1 and indicates the common TCI state / beam (TCI-1_A) from TRP-1 to the UE.

[0128] In addition, PDCCH-1_A is associated with "CORESETPoolIndex=0". PDCCH-1_B indicates the common TCI state / beam (TCI-2_A) to the UE from TRP-2 and is associated with "CORESETPoolIndex=1". The UE can set the receive spatial filter based on TCI-1_A for receiving and / or decoding PDCCH-1_0 and PDSCH-1_0 because the time offset between them and PDCCH-1_A is less than timeDurationForQCL-1. Similarly, the UE may also be able to set appropriate receive spatial filters to receive and / or decode PDCCH-2_0 and PDSCH-2_0 from TRP-2 because the UE may have enough time (time offset less than timeDurationForQCL-2) to first decode PDCCH-2_A and extract the necessary QCL configuration / assumption for decoding subsequent PDCCH / PDSCH transmissions. The two thresholds timeDurationForQCL-1 and timeDurationForQCL-2 for TRP-1 and TRP-2 can be common or different. For example, the UE can use different receiving panels with different array configurations to receive PDCCH / PDSCH from different coordinated TRPs, resulting in different thresholds for different TRPs.

[0129] exist Fig.11, another example depicting a common TCI state / beam indication in a multi-TRP system is presented. In this example, the UE may receive PDSCH-1_1 from TRP-1 (their time offset is less than timeDurationForQCL-1) before PDCCH-1_A is fully decoded, and the UE may receive PDSCH-2_1 from TRP-2 (their time offset is less than timeDurationForQCL-2) before PDC CH-2_A is fully decoded. In this case, the UE may need to set an appropriate spatial receive filter (default receive beam) to buffer PDSCH-1_1 and PDSCH-2_1, independent of the common TCI state / beam indicated in PDCCH-1_A and PDCCH-2_A. Below, various design options for configuring a default TCI state / beam for PDSCH transmission in a multi-TRP system based on multi-DCI (or equivalently, determining a default receive beam for the UE to buffer PDSCH) are presented.

[0130] In an example of Option-1, if CORESETPoolIndex is configured and the first PDCCH carrying a common TCI status / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig.11 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1), the UE may assume that the QCL parameters for the DMRS port used for the PDSCH follow those of the default TCI state / beam, which may correspond to the common TCI state / beam indicated in the second PDCCH associated with the same CORESETPoolIndex (value) associated with the first PDCCH.

[0131] exist Fig.12 In the example above, a conceptual example showing option 1 is given. Fig.12As indicated in , the UE cannot use the common TCI state / beam indicated in PDCCH-1_C (the first PDCCH in option-1) to set the reception parameters for decoding PDSCH-1_1 because their time offset is less than timeDurationForQCL-1. According to option-1, the default TCI state for PDSCH-1_1 in this example is the common TCI state (TCI-1_B) indicated in PDCCH-1_B (the second PDCCH in option-1). This is because the time offset between receiving PDCCH-1_B and receiving PDSCH-1_1 exceeds timeDurationForQCL-1, and PDCCH-1_B and PDCCH-1_C share the same CORESETPoolIndex ("0"), that is, both of them are transmitted from the same TRP-1. In addition, among all PDCCHs carrying common TCI state / beam indications from TRP-1 and decoded by the UE, PDCCH-1_B is closest in time to PDSCH-1_1. It should be noted that in this case, the common TCI state / beam indicated in PDCCH-2_A cannot be configured as the default TCI state or beam for PDSCH-1_1 because the common TCI state / beam is associated with a different value ("1") of CORESETPoolIndex.

[0132] In an example of Option-2, if a PDCCH carrying a common TCI status / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig.11 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1 in , the UE may assume that the QCL parameters for the DMRS port used for PDSCH follow those of the default TCI state / beam, which may correspond to the previous common TCI state / beam indicated to the UE regardless of the transmit TRP. This design option does not depend on whether CORESETPoolIndex is configured.

[0133] exist Fig.13 A conceptual example of characterizing Option-2 is provided in Fig.12Unlike the example of Option-1 shown in , CORESETPoolIndex is not configured for the multi-DCI based multi-TRP system. Therefore, the default TCI state / beam used for PDSCH-1_1 from TRP-1 can correspond to the previous common TCI state / beam indicated to the UE. In this example, the previous common TCI state / beam indicated to the UE is TCI-2_A indicated in PDCCH-2_A from TRP-2. That is, among all PDCCHs that carry common TCI state / beam indications from both TRP-1 and TRP-2 and have been decoded by the UE, PDCCH-2_A is the PDCCH that is closest in time to PDSCH-1_1.

[0134] In an example of Option-3, if CORESETPoolIndex is configured and the first PDCCH carrying a common TCI status / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig. 9 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1), the UE may assume that the QCL parameters for the DMRS port used for the PDSCH follow those of the default TCI state / beam, which may be used for the nearest PDCCH (the third PDCCH) carrying a common TCI state / beam that is associated with the same CORESETPoolIndex (value) associated with the first PDCCH.

[0135] exist Fig.14In, a conceptual example of option-3 default TCI state / beam configuration in a multi-TRP system based on multi-DCI is presented. In this example, the UE cannot set the receive spatial filter to receive and / or decode PDSCH-1_1 according to the common TCI state / beam indicated in PDCCH-1_A because their time offset is less than timeDurationForQCL-1. However, the UE can use the same spatial receive filter as used to receive PDCCH-1_B to receive and / or decode PDSCH-1_1. This is because for PDSCH-1_1, PDCCH-1_B is the nearest PDCCH carrying the common TCI state / beam indication and shares the same CORESETPoolIndex (value) with PDCCH-1_A. Therefore, based on option-3, the UE can assume the same TCI state (and therefore, corresponding QCL parameters) for the DMRS port for PDSCH-1_1 as that for PDCCH-1_B (TCI'-1_B). It should be noted that TCI'-1_B for PDCCH-1_B can be activated by MAC-CE from the TCI state pool configured by RRC signaling. In addition, in this example, if PDCCH-1_B does not exist, the TCI state for PDCCH-1_A can be the default TCI state for PDSCH-1_1, because now PDCCH-1_A becomes the "third PDCCH" in Option-3.

[0136] In an example of Option-4, if a first PDCCH carrying a common TCI status / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig.11 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1 in , the UE may assume that the QCL parameters for the DMRS port used for PDSCH follow those of the default TCI state / beam, which may be used for the most recent PDCCH (the fourth PDCCH) carrying the common TCI state / beam indication, regardless of the transmit TRP. This design option does not depend on whether CORESETPoolIndex is configured.

[0137] Fig.15The example shown assumes that CORESETPoolIndex is not configured and that the nearest PDCCH conveying the common TCI state / beam for the PDSCH of interest (i.e., PDSCH-1_1 from TRP-1) is PDCCH-2_A from TRP-2. Based on Option-4, the default TCI state for PDSCH-1_1 can therefore be configured as TCI'-2_A for PDCCH-2_A. That is, the UE can receive PDSCH-1_1 using the same reception parameters as those used to receive PDCCH-2_A.

[0138] In one example of Option-5, the configuration of the default TCI state / beam for PDSCH follows the legacy procedure defined in 3GPP Rel.16 for multi-TRP based on multi-DCI. If CORESETPoolIndex is configured and the first PDCCH carrying a common TCI state / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig.11 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1), the UE may assume that the QCL parameters for the DMRS port used for the PDSCH follow those of the default TCI state / beam, which may be used for the nearest PDCCH with the lowest CORESET index in the CORESET configured with the same CORESETPoolIndex value associated with the first PDCCH.

[0139] In one example of Option-6, the configuration of the default TCI state / beam for PDSCH follows the conventional procedure defined in 3GPP Rel.15. If a first PDCCH carrying a common TCI state / beam indication is received (e.g., Fig.11 PDCCH-1_A in the received PDSCH (for example, Fig.11 The time offset between PDSCH-1_1) is less than a threshold value (for example, Fig.11 timeDurationForQCL-1 in the time slot), the UE may assume that the QCL parameters for the DMRS ports used for the PDSCH follow those of the default TCI state / beam, which may be used for the PDCCH with the lowest CORESET index in the CORESET associated with the monitored search space in the most recent timeslot. This design option does not depend on whether CORESETPoolIndex is configured.

[0140] In an example of option-7, if, for example, two CORESETPoolIndex values ​​(i.e., 0 and 1) are provided to the UE in PDCCH-Config, and when the scheduling / time offset between receiving a PDCCH and receiving a PDSCH (e.g., scheduled by the PDCCH) in the CORESET associated with the value of CORESETPoolIndex is less than a threshold (e.g., timeDurationforQCL), where the PDCCH may carry DCI (e.g., DCI format 1_1 or 1_2 with or without DL allocation), the DCI indicates one or more joint or separate DL / UL TCI states through one or more TCI code points for UE-specific reception on PDSCH / PDCCH or for PUSCH and all dedicated PUCCH resources granted based on dynamic grant / configuration.

[0141] For example, the UE may assume that the DMRS ports of the PDSCH are quasi-co-located (QCL'ed) with reference signals provided in two default TCI states (a first default TCI state and a second default TCI state), wherein the first (or second) default TCI state / beam may be a joint or separate DL TCI state indicated for receiving the PDCCH in a CORESET associated with a value of CORESETPoolIndex (e.g., 0), and the second (or first) default TCI state / beam may be a joint or separate DL TCI state indicated for receiving the PDCCH in a CORESET associated with a different value of CORESETPoolIndex (e.g., 1).

[0142] For another example, the UE may assume that the DMRS ports of the PDSCH are quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving PDCCH in a CORESET associated with a value of 0 for CORESETPoolIndex.

[0143] For another example, the UE may assume that the DMRS ports of the PDSCH are quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving PDCCH in a CORESET associated with a value of 1 for CORESETPoolIndex.

[0144] For another example, if the PDSCH is associated with a CORESETPoolIndex value of 0, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH in a CORESET associated with a CORESETPoolIndex value of 0 (or 1).

[0145] For another example, if the PDSCH is associated with a CORESETPoolIndex value of 1, the UE may assume that the DMRS ports of the PDSCH are quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH in a CORESET associated with a CORESETPoolIndex value of 1 (or 0).

[0146] In one example of Option-8, two CORESETPoolIndex values ​​(i.e., 0 and 1) may be provided to the UE, for example, in the PDCCH-Config. The UE may receive a first set of one or more PDCCHs / PDCCH candidates in one or more CORESETs associated with a value of 0 for CORESETPoolIndex, and a second set of one or more PDCCHs / PDCCH candidates in one or more CORESETs associated with a value of 1 for CORESETPoolIndex. When a scheduling / time offset between receiving a PDSCH (e.g., scheduled by one or more PDCCHs in the first or second set) and receiving each PDCCH in the first or second set is less than a threshold (e.g., timeDurationforQCL),

[0147] For example, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in two default TCI states (a first default TCI state and a second default TCI state), wherein the first (or second) default TCI state / beam may be a joint or separate DL TCI state indicated for receiving a PDCCH that starts at the earliest time or ends at the latest time among the PDCCHs in the first group, and the second (or first) default TCI state / beam may be a joint or separate DL TCI state indicated for receiving a PDCCH that starts at the earliest time or ends at the latest time among the PDCCHs in the second group.

[0148] For another example, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH with the earliest start time or the latest end time among the PDCCHs in the first group.

[0149] For another example, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH with the earliest start time or the latest end time among the PDCCHs in the second group.

[0150] For another example, if the PDSCH is associated with a CORESETPoolIndex value of 0, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH with the earliest start time or the latest end time among the PDCCHs in the first (or second) group.

[0151] For another example, if the PDSCH is associated with a value of 1 for CORESETPoolIndex, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH with the earliest start time or the latest end time among the PDCCHs in the second (or first) group.

[0152] For another example, the UE may assume that the DMRS port of the PDSCH is quasi-co-located (QCL'ed) with the reference signal provided in the default TCI state, where the default TCI state / beam may be a joint or individual DL TCI state indicated for receiving the PDCCH with the earliest start time or the latest end time among all PDCCHs in the first group and the second group.

[0153] Figures 16 to 18 1 shows an example of signaling flows 1600 to 1800 for a multi-TRP system based on multiple DCIs according to an embodiment of the present disclosure. The signaling flows 1600 to 1800 may be transmitted by a UE (e.g., Figure 1 111 to 116) and BS (e.g., as shown Figure 1 101 to 103) shown in the figure are executed. Figures 16 to 18The illustrated embodiments of signaling flows 1600 to 1800 for a multi-DCI based multi-TRP system are for illustration only. Figures 16 to 18 One or more of the components shown in the can be implemented in dedicated circuitry configured to perform the functions recited, or one or more of the components can be implemented by one or more processors executing instructions for performing the functions recited.

[0154] One or more of the above design options may be configured to the UE by the network to configure a default beam for receiving PDSCH in a multi-TRP system based on multiple DCIs (see Fig.16 ). In the following, four configuration methods are discussed.

[0155] In one example of method-I, the network indicates to the UE that only one design option (e.g., option-1) is followed to configure a default receive beam for receiving and / or decoding PDSCH. The configured design option applies to all coordinated TRPs in a multi-TRP system.

[0156] like Fig.16 As shown, in step 1602, the gNB sends necessary indications based on the options provided in the present disclosure. In step 1604, the UE follows the configuration based on the options provided by the gNB to determine the default beam for receiving and / or decoding the PDSCH from the coordinated TRP.

[0157] exist Fig.17 , a signaling process for following option-1 to configure and determine the default TCI state / beam for two coordinated TRPs (TRP-1 and TRP-2) in a multi-TRP system based on multi-DCI is depicted. In this example, the network indicates to the UE that only option-1 should be followed to configure the default receive beam for receiving and / or decoding PDSCH from TRP-1 and TRP-2. For example, according to option-1, the UE can configure the receive spatial filter to buffer PDSCH_1-1 from TRP-1 following the QCL parameters of the common TCI state / beam indicated in PDCCH_1-A. This is because the scheduling offset between PDCCH_1-B and PDSCH_1-1 is less than timeDurationForQCL-1, and PDCCH_1-A is the previous PDCCH carrying the common TCI state / beam indication. Similarly, the UE may configure the receive spatial filter to buffer PDSCH_2-1 from TRP-2 following the QCL parameters of the common TCI state / beam indicated in PDCCH_2-A.

[0158] like Fig.17As shown, in step 1702, the UE is configured by the network to set a default receive beam. In step 1704, TRP-1 sends a PDCCH-1_A public TCI state / beam indication. In step 1706, TRP-2 sends a PDCCH-2_A public TCI state / beam indication. In step 1708, TRP-1 sends a PDCCH-1_B public TCI state / beam indication to the UE. In step 1710, the UE uses a default receive beam configured based on the public TCI state / beam indicated in PDCCH-1_A to buffer PDSCH-1_1. In step 1712, TRP-1 sends PDSCH-1_1. In step 1714, TRP-2 sends a PDCCH-2_B public TCI state / beam indication. In step 1716, the UE buffers PDSCH-2_1 using a default receive beam based on the common TCI state / beam configuration indicated in PDCCH-2_A. In step 1718, TRP-2 sends PDSCH-2_1 to the UE.

[0159] In one example of method-II, the network indicates to the UE that only one design option is followed per TRP or per CORESETPoolIndex to configure a default receive beam for receiving and / or decoding PDSCH. The design options configured for different TRPs (or different CORESETPoolIndex values) may be different. For example, for a multi-TRP system based on multiple DCI consisting of two coordinated TRPs (TRP-1 and TRP-2), the network may indicate to the UE that option-1 is followed to configure a default receive beam for buffering PDSCH from TRP-1, and option-2 is followed to configure a default receive beam for buffering PDSCH from TRP-2 (see Fig.18 ). For another example, assuming that the common TCI state / beam indication is enabled for TRP-1 but not for TRP-2, the network can instruct the UE to follow option-1 to configure the default receive beam for buffering PDSCH from TRP-1, and to follow option-5 to configure the default receive beam for buffering PDSCH from TRP-2.

[0160] like Fig.18As shown, in step 1802, the gNB sends an indication for TRP-1 (e.g., associated with "CORESETPoolIndex=0"). In step 1804, the gNB sends an indication for TRP-2 (e.g., associated with "CORESETPoolIndex=1"). In step 1806, the UE follows the indication to determine a default beam for receiving and / or decoding a PDSCH from TRP-1, and follows the indication to determine a default beam for receiving and / or decoding a PDSCH from TRP-2.

[0161] In one example of Method-III, more than one (N_opt>1) design options, for example, Option-1 and Option-2, are configured to the UE by the network. In addition, priority rules and / or condition groups are configured to the UE by the network. Based on the priority rules and / or condition groups, the UE can determine the appropriate design options to follow (among all configured design options) to configure a default receive beam for buffering PDSCH. The configured design options and priority rules and / or condition groups are common to all coordinated TRPs in a multi-TRP system.

[0162] Fig.19 and Fig. 20 Examples of priority rules / orders 1900 and 2000 are shown in accordance with embodiments of the present disclosure. Fig.19 and Fig. 20 The illustrated embodiments of priority rules / orders 1900 and 2000 are for illustration only.

[0163] exist Fig.19 In , an example of depicting the priority rule / order is presented. Fig.19 In the figure shown, priority 0 is the highest priority, and priority 5 is the lowest priority. In this example, option-3 has the highest priority, followed by option-1, option-4, option-2, option-5, and option-6 has the lowest priority. For example, if both option-3 and option-2 are configured to the UE by the network, if CORESETPoolIndex is configured, the UE may follow option-3 to set the default receive beam for buffering PDSCH. Otherwise, if CORESETPoolIndex is not configured, the UE may follow option-2 to set the default receive beam for buffering PDSCH.

[0164] For another example, assume that option-2, option-5, and option-6 are configured to the UE by the network. If the common TCI state / beam indication is configured / enabled, the UE can follow option-2 to configure the default receive beam regardless of whether CORESETPoolIndex is configured. If the common TCI state / beam indication is not configured / enabled, but CORESETPoolIndex is configured, the UE can follow option-5 to set the default receive beam. Otherwise, the UE can fall back to option-6 to set the default receive beam for buffering PDSCH. Fig.19 Other priority rules / orderings than those shown are possible. Fig. 20 Another example of a priority rule / ranking is given in FIG. 1 . In this example, Option-1 and Option-3 have the same priority, and Option-2 and Option-4 have the same priority. Therefore, it may be better for the network not to configure the UE with design options (e.g., Option-1 and Option-3) with the same priority unless the UE can rely on other criteria / conditions to prioritize them.

[0165] Based on the above discussion, in addition to the priority rules / ranking, a condition group may also be indicated to the UE by the network. The UE may decide (among all configured design options) the appropriate design option to set the default receive beam for receiving / buffering PDSCH based on the indicated conditions. Fig. 20 As shown, condition A is associated with priority 0 to distinguish option-1 from option-3, and condition B is associated with priority 1 to distinguish option-2 from option-4. For example, if condition A is met, the UE may select option-1 instead of option-3 as the design option to follow to set an appropriate default receive beam. Otherwise, the UE may follow option-3. Similarly, if condition B is met, the UE may follow option-2 to configure a default receive beam for buffering PDSCH.

[0166] Figure 21 to Figure 23 Flowcharts of methods 2100 to 2300 for configuring and prioritizing rules / sorting according to embodiments of the present disclosure are shown. Methods 2100 to 2300 may be performed by a UE (e.g., Figure 1 111 to 116) as shown. Figure 21 to Figure 23 The embodiments of methods 2100 through 2300 shown are for illustration only. Figure 21 to Figure 23 One or more of the components shown in the can be implemented in dedicated circuitry configured to perform the functions recited, or one or more of the components can be implemented by one or more processors executing instructions for performing the functions recited.

[0167] exist Fig.21In , an algorithm flow chart showing the above process is presented, assuming that Option-1, Option-2, Option-3 and Option-4 are configured to the UE by the network as candidate design options to set a default receive beam for receiving and / or decoding PDSCH. Fig. 22 In FIG. 1 , another algorithm flow chart is depicted, assuming that Option-1, Option-2, Option-5 and Option-6 are configured to the UE by the network as candidate design options. Fig. 22 As can be seen, no additional conditions are required to prioritize between option-5 and option-6, except for checking whether CORESETPoolIndex is configured.

[0168] like Fig.21 As shown, in step 2102, at least one option provided in the present disclosure is configured to the UE through the network. In step 2102, the network configures the UE based on Fig. 20 priority rules / sorting. In step 2103, the UE determines whether CORESETPoolIndex is configured. In step 2104, the UE determines at least one option with priority 0. In step 2105, the UE determines at least one option with priority 1. In step 2106, the UE determines whether condition A is satisfied. In step 2107, the UE determines whether condition B is configured. In step 2108, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2110, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2109, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2111, the UE follows at least one option to configure a default receive beam for buffering PDSCH.

[0169] like Fig. 22 As shown, in step 2201, at least one option provided in the present disclosure is configured to the UE through the network. In step 2202, the network configures the UE based on Fig. 20priority rules / sorting. In step 2203, the UE determines whether the common TCI state / beam indication is configured / enabled. In step 2204, the UE determines at least one option with priority 0. In step 2205, the UE determines whether condition A is met. In step 2208, the UE determines whether CORESETPoolIndex is configured. In step 2206, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2209, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2207, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2211, the UE follows at least one option to configure a default receive beam for buffering PDSCH.

[0170] Fig. 20 Condition A and / or condition B shown in may correspond to a variety of possible conditions, as shown below.

[0171] In one example, condition A is used to Fig. 20 Prioritize between option-1 and option-3 under priority 0.

[0172] In one example of condition A.1, if the time offset between the PDSCH of interest and the previous PDCCH carrying the common TCI status / beam indication (the second PDCCH in option-1, which shares the same CORESETPoolIndex as the first PDCCH and has been decoded by the UE) is below a threshold (e.g., X ms / slot / symbol), option-1 has a higher priority than option-3.

[0173] In an example of condition A.2, if the time offset between the PDSCH of interest and the previous PDCCH carrying the common TCI state / beam indication (the second PDCCH in option-1, which shares the same CORESETPoolIndex as the first PDCCH and has been decoded by the UE) is lower than a threshold (e.g., X ms / time slot / symbol), but the receive beam configured according to the common TCI state / beam indicated in the second PDCCH and the receive beam used to receive the most recent PDCCH carrying the common TCI state / beam indication (the third PDCCH in option-3) are from different panels, option-3 has a higher priority than option-1.

[0174] In one example of condition A.3, if the UE can simultaneously receive the common beam indicated in the second PDCCH and the current beam from a different CORESETPoolIndex (TRP), option-1 has a higher priority than option-3.

[0175] In one example of condition A.4, if the UE can simultaneously receive the third PDCCH and the current beam from different CORESETPoolIndex (TRP), option-3 has a higher priority than option-1.

[0176] In one example, condition B is used to Fig. 20 Prioritize between option-2 and option-4 under priority 1.

[0177] In one example of condition B.1, if the time offset between the PDSCH of interest and the previous PDCCH carrying the common TCI status / beam indication (which has been decoded by the UE) is below a threshold (e.g., X ms / timeslot / symbol), option-2 has a higher priority than option-4.

[0178] In an example of condition B.2, if the time offset between the PDSCH of interest and the previous PDCCH carrying the common TCI state / beam indication (which has been decoded by the UE) is below a threshold (e.g., X ms / time slot / symbol), but the receive beam configured according to the common TCI state / beam indicated in the previous PDCCH and the receive beam used to receive the most recent PDCCH carrying the common TCI state / beam indication (the fourth PDCCH in Option-4) are from different panels, then Option-4 has a higher priority than Option-2.

[0179] Other conditions of Condition A.1, Condition A.2, Condition A.3, Condition B.1, and Condition B.2 are also possible. For Condition A.2 and Condition B.2, the UE may report receive antenna panel information (e.g., panel ID) and channel measurement reports to the network. For Condition A.3 and Condition A.4, a certain degree of backhaul coordination is required between TRPs, as one TRP may need to know the current transmit beam from another TRP (associated with different CORESETPoolIndex values).

[0180] All the above necessary conditions may be configured to the UE by the network. Then, the UE may be instructed by the network to use one or more of them. For example, if both option-1 and option-3 are configured, the UE may be instructed by the network to use only condition A.1, but the UE may be configured by the network with conditions A.1, A.2, A.3, A.4, A.5, B.1, and B.2.

[0181] In some cases, the UE may not be configured with any priority rules / ordering by the network (e.g. Fig.19 and Fig. 20), but rather configures a set of explicit conditions and the design options of the configuration. For example, three options, namely, option-1, option-3, and option-5, may first be configured to the UE by the network. In addition, three conditions, represented by condition X, condition Y, and condition Z, may be configured to the UE by the network. If condition X is met, the UE may follow option-1 instead of option-3. If condition Y is met, the UE may follow option-3 instead of option-5. If condition Z is met, option-5 has a higher priority than option-1. Fig.23 An example of how a UE can determine an appropriate design option (from Option-1, Option-3, and Option-5) according to configured conditions (Condition X, Condition Y, and Condition Z) is shown in FIG. Fig.23 As indicated in , the UE may follow Option-5 instead of Option-1 and Option-3 to configure the default receive beam for receiving PDSCH, if the UE is configured and follows Fig.19 and Fig. 20 This is not possible without the precedence rules / ordering in .

[0182] For example, Fig.23 Condition Z in may be: if the time offset between the PDSCH of interest and the previous PDCCH carrying the common TCI status / beam indication (the second PDCCH in option-1, which shares the same CORESETPoolIndex as the first PDCCH and has been decoded by the UE) is below a threshold (e.g., X ms / slot / symbol), then option-1 has a higher priority than option-5. Otherwise, the UE may configure a default receive beam according to option-5 instead of option-1, which is used to receive the nearest PDCCH with the lowest CORESET index in the CORESET configured with the same CORESETPoolIndex value associated with the first PDCCH.

[0183] like Fig.23As shown, in step 2301, at least one option provided in the present disclosure is configured to the UE through the network. In step 2302, the UE determines whether condition X is satisfied. In step 2303, the UE determines at least one option as a candidate design option. In step 2307, the UE determines at least one option as a candidate design option. In step 2304, the UE determines whether condition Z is satisfied. In step 2308, the UE determines whether condition Y is satisfied. In step 2305, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2309, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2306, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 2310, the UE follows at least one option to configure a default receive beam for buffering PDSCH.

[0184] In one embodiment of Method-IV, more than one (N_opt>1) design option per TRP (or per CORESETPoolIndex) is configured to the UE by the network. The design options configured for different TRPs may be mutually exclusive. For example, if CORESETPoolIndex is configured, Option-1 and Option-3 (associated with "CORESETPoolIndex=0") for TRP-1 and Option-2 and Option-5 (associated with "CORESETPoolIndex=1") for TRP-2 may be configured to the UE. Similar to Method III, one or more priority rules / rankings and / or one or more groups of conditions may be indicated to the UE by the network to help the UE determine the appropriate design options for each coordinated TRP. The priority rules / rankings and / or condition groups may be common to all TRPs and customized on a per-TRP basis. The detailed method for configuring and using priority rules / rankings and / or condition groups follows Figures 19 to 23 The method described in .

[0185] In a single DCI based multi-TRP system, a single PDCCH / DCI may be configured by the network to the UE to schedule PDSCH transmissions from different coordinated TRPs. For common TCI state / beam indication, the corresponding PDCCH may signal N_tci>1 common TCI state / beam, each common TCI state / beam corresponding to one coordinated TRP. For example, for a coordinated TRP consisting of two coordinated TRPs (e.g., Figure 8For a multi-TRP system consisting of TRP-1 and TRP-2 in the PDCCH, the TCI code point in the PDCCH indicating the common TCI state / beam to the UE can be expressed as (TCI#a, TCI#b), where TCI#a can represent the common TCI state for TRP-1, and TCI#b can represent the common TCI state for TRP-2. Fig.11 Similar to the example shown for a multi-TRP system based on multiple DCIs, the UE may also need to set a default receive beam for buffering PDSCH in a multi-TRP system based on a single DCI if the scheduling offset between the PDSCH of interest and the PDCCH carrying the common TCI status / beam indication is less than a predetermined threshold.

[0186] Figure 24 to Figure 26 Examples of common TCI status / beam indications 2400 to 2600 in a multi-TRP system according to an embodiment of the present disclosure are shown. Figure 24 to Figure 26 The illustrated embodiments of common TCI status / beam indication 2400 to 2600 in a multi-TRP system are for illustration only.

[0187] exist Fig.24 In the figure, a conceptual example is presented depicting a common TCI state / beam configuration in a multi-TRP system based on a single DCI. Fig.24 It is shown in the figure that the scheduling offset between PDSCH-1_0 / PDSCH-2_0 and PDCCH-A carrying the common TCI state / beam for both TRP-1 and TRP-2 exceeds timeDurationForQCL. Therefore, the UE can configure the receiving spatial filter for receiving and / or decoding PDSCH-1_0 and PDSCH-2_0 based on the QCL parameters in TCI-A_1 and TCI-A_2 indicated in PDCCH-A. However, the scheduling offset between PDSCH-1_1 / PDSCH-2_1 and PDCCH-B carrying the common TCI state / beam for both TRP-1 and TRP-2 is lower than the threshold timeDurationForQCL. In this case, the UE cannot set the receiving spatial filter for receiving and / or decoding PDSCH-1_1 and PDSCH-2_1 according to the QCL parameters of TCI-B_1 and TCI-B_2 indicated in PDCCH-B. Therefore, the UE needs to configure an appropriate default receive beam for buffering PDSCH-1-1 and PDSCH-2_1. In the following, several design options for configuring and determining the default TCI state / receive beam in a single DCI based multi-TRP system with common TCI state / beam indication are discussed.

[0188] In one example of Option-A, if a first PDCCH carrying a common TCI status / beam for all coordinated TRPs is received (e.g., Fig.24 PDCCH-B in the received PDSCH (for example, Fig.24 The time offset between PDSCH-1_1 and PDSCH-2_1 in the example is less than a threshold value (for example, Fig.24 timeDurationForQCL in , the UE may assume that the QCL parameters for the DMRS port for PDSCH follow those of the default TCI state / beam, which may correspond to the previous N_tci (>1) TCI states / beams (non-common TCI states / beams) indicated in a single DCI for all PDSCHs transmitted from the coordinated TRP.

[0189] exist Fig.25 In, a conceptual example describing the provided option-A is given. In this example, PDCCH-a is the previous PDCCH relative to PDCCH-B that signals DCI indicating two TCI states (i.e., TCI-a_1 and TCI-a_2) for PDSCH transmitted from TRP-1 and TRP-2. For example, (TCI-a_1, TCI-a_2) may correspond to one of the TCI code points (e.g., a total of eight TCI code points specified in 3GPP Rel.16) activated by MAC-CE from a TCI state pool configured by RRC. Since the scheduling offset between PDSCH-1_1 and PDCCH-B and between PDSCH-2_1 and PDCCH-B is less than timeDurationForQCL, the UE cannot configure the receive spatial filter for receiving PDSCH-1_1 and PDSCH-2_1 according to the QCL parameters of the common TCI state / beam indicated in PDCCH-B. According to Option-A, the UE may set a default receive beam for buffering PDSCH-1_1 and PDSCH-2_1 based on the QCL parameters of the TCI state / beam indicated in PDCCH-a.

[0190] In one example of Option-B, if a first PDCCH carrying a common TCI status / beam for all coordinated TRPs is received (e.g., Fig.24 PDCCH-B in the received PDSCH (for example, Fig.24 The time offset between PDSCH-1_1 and PDSCH-2_1 in the example is less than a threshold value (for example, Fig.24timeDurationForQCL in ), the UE may assume that the QCL parameters for the DMRS port for PDSCH follow those of the default TCI state / beam, which may correspond to the previous N_tci (>1) common TCI states / beams indicated in a single DCI for all coordinated TRPs.

[0191] Fig.26 A conceptual example of Option-B provided in configuring and determining the default receive beam is given in Fig.25 The example for option -A shown is different, Fig.26 The UE in can configure the default receive beam for buffering PDSCH-1_1 and PDSCH-2_1 based on the QCL parameters of the two common TCI states (TCI-A_1 and TCI-A_2) indicated in PDCCH-A. This is because in this example, TCI-A_1 and TCI-A_2 are the previous common TCI states (relative to those indicated in PDCCH-B) indicated in a single DCI (PDCCH-A) for all coordinated TRPs (TRP-1 and TRP-2).

[0192] In one example of Option-C, if a first PDCCH carrying a common TCI status / beam for all coordinated TRPs is received (e.g., Fig.24 PDCCH-B in the received PDSCH (for example, Fig.24 The time offset between PDSCH-1_1 and PDSCH-2_1 in the example is less than a threshold value (for example, Fig.24 timeDurationForQCL in , the UE may assume that the QCL parameters for the DMRS port used for PDSCH follow those of the default TCI state / beam, which may correspond to the lowest code point among the TCI code points containing N_tci (>1) different TCI states activated for PDSCH. This design option is similar to the configuration of the default TCI state specified in 3GPP Rel.16 for a single-DCI based multi-TRP system.

[0193] Fig. 27 and Fig.28 Examples of TCI code points 2700 and 2800 are shown according to an embodiment of the present disclosure. Fig. 27 and Fig.28 The illustrated embodiments of TCI code points 2700 and 2800 are for illustration only.

[0194] If you can Fig. 27As can be seen in the example shown, a total of 8 TCI code points are activated by MAC-CE for PDSCH from the TCI state pool configured by RRC. Each TCI code point corresponds to one or two TCI states. According to option-C, the default TCI state / beam can correspond to the lowest TCI code point containing two different TCI states. In this example, the default TCI states are TCI#1 and TCI#4, and the corresponding TCI code points are "010". The UE can be configured based on the QCL parameters of TCI#1 and TCI#4 for buffering PDSCH (for example, Fig.24 The default receive beam for PDSCH-1_1 and PDSCH-2_1).

[0195] In one example of Option-D, if a first PDCCH carrying a common TCI status / beam for all coordinated TRPs is received (e.g., Fig.24 PDCCH-B in the received PDSCH (for example, Fig.24 The time offset between PDSCH-1_1 and PDSCH-2_1 in the example is less than a threshold value (for example, Fig.24 timeDurationForQCL in the QCL), the UE may assume that the QCL parameters of the DMRS port used for PDSCH follow those of the default TCI state / beam, which may be configured by the network and indicated to the UE.

[0196] For example, N_tci (>1) common TCI states / beams may be explicitly configured / indicated to the UE by the network as the default TCI state or beam, so that the UE may configure the receive spatial filter for buffering the PDSCH transmitted from the coordinated TRP. For a multi-TRP system consisting of two TRPs (TRP-1 and TRP-2), (TCI#1, TCI#4) may be configured to the UE by the network as the default common TCI state. The UE may configure the QCL parameters for buffering the PDSCH (e.g., Fig.24 The default receive beams for PDSCH-1_1 and PDSCH-2_1) in the DMZ are used until the network updates / reconfigures the default public TCI state.

[0197] For another example, a pool of default TCI sets may be configured to the UE via high-level signaling (such as RRC) through the network. Each default TCI set may correspond to a single common TCI state or N_tci (>1) common TCI states. MAC-CE may activate one of the default TCI sets, and the UE may configure a default receive beam for buffering PDSCH according to the QCL parameters of the common TCI state indicated in the activated default TCI set. Fig.28In , two examples of default TCI sets are presented. Fig. 27 In the upper half of , the default TCI set can contain a single common TCI state (e.g., for single-TRP operation) or two common TCI states (e.g., for multi-TRP operation). Fig. 27 The default TCI set contains two common TCI states. If MAC-CE activates the default TCI set #2, such as Fig. 27 As shown in the lower part of , the UE can be configured based on the QCL parameters of TCI#1 and TCI#4 for buffering PDSCH (for example, Fig.24 The default receive beams for PDSCH-1_1 and PDSCH-2_1) in the MAC-CE are used until the MAC-CE activates a new default TCI set.

[0198] In one example of Option-E, the configuration of the default TCI state / beam for PDSCH follows the legacy procedure defined in 3GPP Rel.15. If a first PDCCH carrying a common TCI state / beam for all coordinated TRPs is received (e.g., Fig.24 PDCCH-B in the received PDSCH (for example, Fig.24 The time offset between PDSCH-1_1 and PDSCH-2_1) is less than a threshold value (for example, Fig.24 timeDurationForQCL in , the UE may assume that the QCL parameters for the DMRS port used for the PDSCH follow those of the default TCI state / beam, which may be used for the PDCCH with the lowest CORESET index in the CORESET associated with the monitored search space in the most recent timeslot.

[0199] In a multi-TRP system based on a single DCI, one or more of the above-mentioned design options may be configured to the UE by the network to configure a default beam for receiving PDSCH. For example, the network may indicate to the UE that only one design option (e.g., Option-A) is to be followed to configure a default receive beam for receiving and / or decoding PDSCH. For another example, more than one design option and a priority rule / sort and / or condition group may be indicated to the UE by the network, so that the UE may determine and follow the appropriate design option to configure a default receive beam for buffering PDSCH.

[0200] Fig.29An example of priority rules / sorting is given in , where priority 0 has the highest priority and priority 3 has the lowest priority. In this example, Option-B and Option-D belong to priority 0, Option-A and Option-C belong to priority 1, and Option-E corresponds to priority 3. For example, if Option-A and Option-B are indicated to the UE by the network, the UE can follow Option-B to configure the default receive beam as long as the common TCI state / beam indication is configured / enabled. For another example, assume that Option-C and Option-E are indicated to the UE by the network. If all TCI code points activated by the MAC-CE consist of a single TCI state, the UE can follow Option-E to set the default receive beam.

[0201] In some settings, design options belonging to the same priority order can be indicated / configured by the network to the UE, e.g. Fig.29 In the example shown, Option-B and Option-D are provided. In this case, the UE requires additional indications / conditions from the network so that the UE can prioritize one option over another. In this example, if the UE is configured with both Option-B and Option-D, Condition 1 may be indicated to the UE by the network. Similarly, if the UE is configured with both Option-A and Option-C, Condition 2 may be indicated to the UE by the network. In the following, several possibilities for Condition 1 and Condition 2 are presented.

[0202] In one example, condition 1 is used to Fig.29 Prioritize between option-B and option-D under priority 0.

[0203] In an instance of condition 1.1, if the default (common) TCI state / beam is explicitly configured to the UE by the network (e.g., a default TCI set is activated from a pool of default TCI sets, each of which consists of N_tci>1 common TCI states), Option -D has higher priority than Option -B.

[0204] In one instance of condition 1.2, it can be assumed that a default (common) TCI state / beam is explicitly configured to the UE by the network. Option-B has priority over Option-D if the previous N_tci (>1) common TCI states / beams (indicated in a single DCI for all coordinated TRPs) are different from the explicitly configured default (common) TCI state and / or are configured at a later time.

[0205] In an example of condition 1.3, if the reception default beam configured according to option-B and the beam used to receive the first PDCCH are from different panels, while the reception default beam configured according to option-D and the beam used to receive the first PDCCH are from the same panel, option-D has a higher priority than option-B.

[0206] In an example of condition 1.4, if the reception default beam configured according to option-D and the beam used to receive the first PDCCH are from different panels, while the reception default beam configured according to option-B and the beam used to receive the first PDCCH are from the same panel, option-B has a higher priority than option-D.

[0207] In one example, condition 2 is used to Fig.29 Prioritize between option-A and option-C under priority 1.

[0208] In one example of condition 2.1, if there is at least one TCI code point consisting of N_tci (>1) TCI states activated for PDSCH, option-A has a higher priority than option-C.

[0209] In one instance of condition 2.2, it can be assumed that there is at least one TCI code point consisting of N_tci(>1) TCI states activated for PDSCH. Option-C has a higher priority than Option-A if the previous N_tci(>1) TCI states / beams (non-common TCI states or beams) indicated in a single DCI for all coordinated TRPs are different from the N_tci(>1) TCI states / beams corresponding to the lowest TCI code point among all code points consisting of N_tci(>1) TCI states and / or are configured at a later time.

[0210] In an instance of condition 2.3, if the reception default beam configured according to option-A and the beam used to receive the first PDCCH are from different panels, while the reception default beam configured according to option-C and the beam used to receive the first PDCCH are from the same panel, option-C has a higher priority than option-A.

[0211] In an instance of condition 2.4, if the reception default beam configured according to option-C and the beam used to receive the first PDCCH are from different panels, while the reception default beam configured following option-A and the beam used to receive the first PDCCH are from the same panel, option-A has a higher priority than option-C.

[0212] Fig.29An example of priority rule 2900 for determining a default TCI state for PSDCH reception in a multi-TRP system according to an embodiment of the present disclosure is shown. Fig.29 The illustrated embodiment of priority rule 2900 for determining a default TCI state for PSDCH reception in a multi-TRP system is for illustration only.

[0213] remove Fig.29 Other priority rules / sorting other than those shown are also possible. In addition, other conditions other than those described above may also be implemented. It should be noted that for conditions 1.3, 1.4, 2.3, and 2.4, the UE may need to report to the network its reception panel information (e.g., panel ID) and channel measurement report. All of the above necessary conditions may be configured to the UE by the network. The UE may then be instructed by the network to use one or more of them. For example, if both Option-B and Option-D are configured, the UE may be instructed by the network to use only Condition 1.1, but Condition 1.1, 1.2, 1.3, 1.4, 2.1, 2.2, 2.3, and 2.4 may be first configured to the UE by the network.

[0214] In some cases, the UE may not be configured with any priority rules / ordering by the network (e.g. Fig.29 ), but rather configures a set of explicit conditions and the design options of the configuration. For example, three options, namely, option-A, option-B, and option-D, may be first configured to the UE by the network. In addition, three conditions, represented by condition I, condition II, and condition III, may be configured to the UE by the network. If condition I is met, the UE may follow option-A instead of option-B. If condition II is met, the UE may follow option-A instead of option-D. If condition III is met, option-B has a higher priority than option-D. Fig.30 An example characterizing how a UE can determine an appropriate design option (from Option-A, Option-B, and Option-D) according to configured conditions (Condition I, Condition II, and Condition III) is shown in FIG.

[0215] Fig.30 An example of determining a default TCI state 3000 for PSDCH reception in a multi-TRP system following a priority rule according to an embodiment of the present disclosure is shown. The method 3000 may be performed by a UE (e.g., Figure 1 111 to 116) as shown. Fig.30 The illustrated embodiment of method 3000 is for illustration only. Fig.30 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions described.

[0216] like Fig.30 As indicated in , the UE may follow Option-A instead of Option-B and Option-D to configure a default receive beam for receiving PDSCH, if the UE is configured and follows Fig.29 This is not possible if the precedence rules / ordering in . For example, Fig.30 Condition II in may be that the previous N_tci (>1) TCI states / beams (non-common TCI states / beams) indicated in a single DCI for all coordinated TRPs are different from the explicitly configured default (common) TCI states and / or are configured at a later time.

[0217] like Fig.30 As shown, in step 3001, at least one option provided in the present disclosure is configured to the UE through the network. In step 3002, the UE determines whether condition I is satisfied. In step 3003, the UE determines at least one option as a candidate design option. In step 3007, the UE determines at least one option as a candidate design option. In step 3004, the UE determines whether condition II is satisfied. In step 3008, the UE determines whether condition III is satisfied. In step 3005, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 3009, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 3006, the UE follows at least one option to configure a default receive beam for buffering PDSCH. In step 3010, the UE follows at least one option to configure a default receive beam for buffering PDSCH.

[0218] As specified in the present disclosure herein, in a (multi-DCI based) multi-TRP system, two values ​​(i.e., 0 and 1) of a CORESET pool index (represented by CORESETPoolIndex) may be indicated / provided / configured to a UE by the network, for example in PDCCH-Config, where each CORESET may be configured with a value of CORESETPoolIndex.

[0219] In addition, one or more TCI states / TCI state pairs for the same (or different) CORESET pool index values ​​may be indicated / provided / configured to the UE by the network, for example, via a beam indication MAC CE or a DCI associated with a CORESET pool index value (e.g., 0 or 1) (e.g., via one or more TCI code points of one or more TCI fields in a corresponding DCI format 1_1 / 1_2 with or without DL allocation), wherein under the unified TCI framework, the TCI state may be a joint DL and UL TCI state provided by TCI-State / DLorJointTCI-State or a separate DL TCI state or a separate UL TCI state provided by TCI-State / UL-TCIState for channels / signals (e.g., PDCCH, PDSCH, PUCCH, and PUSCH) associated with the same (or different) CORESET pool index value. TCI state, and a TCI state pair may include / contain a separate DL TCI state provided by TCI-State / DLorJointTCI-State or a separate UL TCI state provided by TCI-State / UL-TCIState for channels / signals (e.g., PDCCH, PDSCH, PUCCH, and PUSCH) associated with the same (or different) CORESET pool index value.

[0220] The UE may report capability signaling represented by twoBeamsMDCI to the network to indicate to the network that the UE is able to use / apply or is capable of using / applying two beams / TCI states to simultaneously receive one or more channels / signals, such as PDSCH, after the indicated beam may be applied (i.e., after the beam application time (BAT)), for example, wherein the one or more channels / signals may be associated with different CORESETPoolIndex values ​​(e.g., two values ​​of CORESTPoolIndex 0 and 1) or different physical layer cell identifiers (PCIs) (e.g., serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each pointing to a PCI list / set / pool configured by a higher layer (including at least for example, when / if one or more channels is a PDSCH, the PDSCH may be scheduled / activated by a PDCCH / DCI received in a CORESET associated / configured with different CORESETPoolIndex values ​​(e.g., two values ​​0 and 1 of CORESTPoolIndex) or different PCI (e.g., serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each pointing to an entry / PCI in a PCI list / set / pool configured by a higher layer (including at least a PCI other than serving cell PCI)), and the PDSCH may be a UE-specific PDSCH or a non-UE-specific PDSCH.

[0221] In addition, the network can indicate / configure / provide to the UE, for example via higher-layer RRC signaling / parameters (for example, via enableTwoBeamsMDCI or by setting enableTwoBeamsMDCI to "enabled") and / or MAC CE commands and / or DCI-based dynamic L1 signaling, that the UE can use / apply two beams / TCI states to simultaneously receive one or more channels / signals, such as PDSCH, for example after the indicated beam can be applied (i.e., after the beam application time BAT), where the one or more channels / signals can be associated with different CORESETPoolIndex values ​​(for example, two values ​​of CORESTPoolIndex, 0 and 1) or different PCI (for example, serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each of which points to an entry / PCI in a PCI list / set / pool configured by a higher layer (including at least PCI other than serving cell PCI)).

[0222] The UE may report capability signaling represented by twoDefaultBeamsMDCI to the network to indicate to the network that the UE is capable of using / applying or is capable of using / applying two beams / TCI states to simultaneously receive one or more channels / signals, such as PDSCH, when the scheduling offset is less than or equal to the threshold, wherein the one or more channels / signals may be associated with different CORESETPoolIndex values ​​(e.g., two values ​​0 and 1 of CORESTPoolIndex) or different PCI (e.g., serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each pointing to a PCI list / s configured by a higher layer (including at least a PCI other than serving cell PCI)). CORESETPoolIndex values ​​(e.g., two values ​​of CORESTPoolIndex, 0 and 1) or different PCI (e.g., serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each pointing to an entry / PCI in a PCI list / set / pool configured by a higher layer (including at least a PCI other than serving cell PCI)) may be scheduled / activated, and the PDSCH may be a UE-specific PDSCH or a non-UE-specific PDSCH.

[0223] In addition, the network may indicate / configure / provide to the UE, for example, via higher-layer RRC signaling / parameters (e.g., by enableTwoDefaultBeamsMDCI or by setting enableTwoDefaultBeamsMDCI to "enabled") and / or MAC CE commands and / or DCI-based dynamic L1 signaling, that the UE may use / apply two beam / TCI states to simultaneously receive one or more channels / signals, such as PDSCH, when the scheduling offset is less than or equal to the threshold specified herein by the present disclosure, wherein the one or more channels / signals may be associated with different CORESETPoolIndex values ​​(e.g., two values ​​of CORESTPoolIndex, 0 and 1) or different PCI (e.g., serving cell PCI and / or PCI other than serving cell PCI) values ​​or different PCI index values ​​(each pointing to an entry / PCI in a higher-layer configured PCI list / set / pool (including at least PCI other than serving cell PCI)).

[0224] For a CORESET pool index value (e.g., 0 or 1), the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of the TCI states associated with the CORESETPoolIndex value for receiving a PDSCH associated with the CORESETPoolIndex value (e.g., the TCI state is indicated in a beam indication DCI received in the CORESET associated / configured with the CORESETPoolIndex value) - for example, a PDSCH scheduled by a scheduling DCI received in the CORESET associated / configured with the CORESETPoolIndex value t_1 (e.g., in terms of time slots, symbols, etc.) after receiving the beam indication DCI (e.g., t_1 time slots / symbols after the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI).

[0225] In the present disclosure, t_1 may be referred to as a beam application time specified under a unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries a PDSCH allocation, and when the UE may transmit the last symbol of a PUCCH having HARQ-ACK information corresponding to a PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols may be applied. Determined on the carrier with the smallest SCS among the carriers to which beam indication is applied; (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols can be determined on the carrier with the smallest SCS among the carriers to which beam indication is applied.

[0226] Optionally, when the enableTwoBeamsMDCI specified by the present disclosure is configured / provided to the UE by the network, the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of TCI states associated with both CORESETPoolIndex values ​​0 and 1 (respectively) to simultaneously receive PDSCHs associated with both CORESETPoolIndex values ​​0 and 1 (respectively) (e.g., the TCI states are in the TCI state pairs associated with both CORESETPoolIndex values ​​0 and 1 (respectively)). The PDSCH is scheduled by one or more scheduling DCIs received in a CORESET associated / configured with both CORESETPoolIndex values ​​0 and 1 (respectively), for example, t_1 (e.g., in terms of time slot, symbol, etc.) after receiving the beam indication DCI (e.g., t_1 time slots / symbols after the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI), where the beam indication DCI can be received in the CORESET associated / configured with CORESETPoolIndex values ​​0 and / or 1 according to the network's configuration / indication via higher-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI, and / or among all beam indication DCIs received in the CORESET associated / configured with CORESETPoolIndex values ​​0 or 1, the beam indication DCI can be received at the earliest or latest time.

[0227] In the present disclosure, t_1 may be referred to as the beam application time specified under the unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries PDSCH allocation, and when the UE may transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols may be applied in the case where the beam indication is applied, for example, with a CORESETPoolIndex value of 0 and / or 1; (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; the first time slot and BeamAppTime_r17 symbols can both be determined on the carrier with the smallest SCS among the carriers associated with the CORESETPoolIndex value 0 and / or 1 to which the beam indication is applied.

[0228] In one example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a received in the CORESET associated / configured with the CORESETPoolIndex value 0 and, for example, the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value 0 scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, then the UE may use / apply one or more ( The UE may receive the PDSCH using the TCI state indicated previously (e.g., in the beam indication DCI_a' received in the CORESET associated / configured with the CORESETPoolIndex value 0 (or 1)) and / or when / if the UE is configured / provided with the enableTwoDefaultBeamsMDCI as specified herein by the present disclosure by the network (and / or set to "enabled"), then the UE may use / apply one or more (e.g., two) (previously) indicated TCI states for CORESETPoolIndex values ​​0 and 1 (e.g., in the beam indication DCI_a' received in the CORESET associated / configured with the CORESETPoolIndex value 0 (or 1)). SETPoolIndex values ​​0 and 1) to simultaneously receive, for example, PDSCHs associated with CORESETPoolIndex values ​​0 and 1, respectively, scheduled / activated by PDCCH / DCIs received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1) beam indication DCI_a' (e.g., all beam indication DCIs received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and / or 1) , received at the earliest or latest time) and the time offset between the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_a' is received at the latest time relative to the beam indication DCI_a, and / or (3) the TCI state indicated in the beam indication DCI_a' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_a' is one or two.

[0229] In another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b received in the CORESET associated / configured with the CORESETPoolIndex value 1 and, for example, the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value 1 scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, then the UE may use / apply one or more ( The UE may receive the PDSCH using the TCI state indicated previously (e.g., in the beam indication DCI_b' received in the CORESET associated / configured with the CORESETPoolIndex value 1 (or 0)) and / or when / if the UE is configured / provided with the enableTwoDefaultBeamsMDCI as specified herein by the present disclosure by the network (and / or set to "enabled"), then the UE may use / apply one or more (e.g., two) (previously) indicated TCI states for CORESETPoolIndex values ​​0 and 1 (e.g., in the beam indication DCI_b' received in the CORESET associated / configured with the CORESETPoolIndex value 1 (or 0)). SETPoolIndex values ​​0 and 1) to simultaneously receive, for example, PDSCHs associated with CORESETPoolIndex values ​​0 and 1, respectively, scheduled / activated by PDCCH / DCIs received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1) beam indication DCI_b' (e.g., all beam indication DCIs received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and / or 1) , received at the earliest or latest time) and the time offset between the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (2) the beam indication DCI_b' is received at the latest time relative to the beam indication DCI_b, and / or (3) the TCI state indicated in the beam indication DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_b' is one or two.

[0230] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a received in the CORESET associated / configured with the CORESETPoolIndex value 0 and the first symbol / time slot of the PDSCH associated with the CORESETPoolIndex value 0 scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if the UE is configured / provided by the network as specified in the present disclosure herein SETPoolIndex value 0 (or 1) (e.g., in beam indication DCI_a' received in a CORESET associated / configured with CORESETPoolIndex value 0 (or 1)), and (2) one or more (previously) indicated TCI states for CORESETPoolIndex value 1 (or 0) (e.g., in beam indication DCI_a' received in a CORESET associated / configured with CORESETPoolIndex value 1 (or 1)). RESETPoolIndex value 1 (or 0) associated / configured in the CORESET) to (simultaneously) receive the PDSCH, where (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b ...2 associated with the beam indication DCI_a. For example, the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / time slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the most recent time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two.

[0231] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b received in the CORESET associated / configured with the CORESETPoolIndex value 1 and the first symbol / time slot of the PDSCH associated with the CORESETPoolIndex value 1 scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, and / or when / if the UE is configured / provided by the network as specified in the present disclosure herein SETPoolIndex value 0 (or 1) (e.g., in beam indication DCI_a' received in a CORESET associated / configured with CORESETPoolIndex value 0 (or 1)), and (2) one or more (previously) indicated TCI states for CORESETPoolIndex value 1 (or 0), e.g., in beam indication DCI_a' received in a CORESET associated / configured with CORESETPoolIndex value 1 (or 1)). RESETPoolIndex value 1 (or 0) is associated / configured in the CORESET to (simultaneously) receive the PDSCH, where (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / time slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b .... For example, the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / time slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the most recent time relative to the beam indication DCI_b, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two.

[0232] The network may indicate / configure / provide to the UE, for example, via higher-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI, that inter-cell multi-TRP operation is enabled (e.g., for a multi-TRP framework based on MDCI).

[0233] For example, a high-level parameter InterCellMDCImTRP may be provided / configured to the UE by the network and is set to "enabled" or the UE may be configured with (SSB) information related to a PCI other than the serving cell PCI, for example, SSB-MTC-AdditionalPCI; for this case, each CORESET corresponding to a different CORESETPoolIndex value provided by the ControlResourceSet may be associated with a different physical cell ID, for example, via an activated / indicated TCI state of (for) the CORESET, where a CORESET associated / configured with one CORESETPoolIndex value (e.g., 0) may be associated with the serving cell physical cell ID, and a CORESET associated / configured with another CORESETPoolIndex value (e.g., 1) may be associated with a PCI other than the serving cell PCI. For a CORESET pool index value (e.g., 0 or 1) and thus the corresponding / associated PCI as specified herein by the present disclosure, the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of the TCI states associated with the CORESETPoolIndex value (and thus, the corresponding / associated PCI value) for receiving a PDSCH associated with the CORESETPoolIndex value (and thus, the corresponding / associated PCI value) (e.g., the TCI state is indicated in a beam indication DCI received in the CORESET associated / configured with the CORESETPoolIndex value) - for example, the PDSCH is scheduled by a scheduling DCI received in the CORESET associated / configured with the CORESETPoolIndex value t_1 (e.g., in terms of time slots, symbols, etc.) after receiving the beam indication DCI (e.g., t_1 time slots / symbols after the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI).In the present disclosure, t_1 may be referred to as a beam application time specified under a unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries a PDSCH allocation, and when the UE may transmit the last symbol of a PUCCH having HARQ-ACK information corresponding to a PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols may be applied. Determined on the carrier with the smallest SCS among the carriers to which beam indication is applied; (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols can be determined on the carrier with the smallest SCS among the carriers to which beam indication is applied.

[0234] Optionally, when enableTwoBeamsMDCI specified by the present disclosure herein is configured / provided to the UE by the network, the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of TCI states associated (respectively) with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) to simultaneously receive PDSCHs associated (respectively) with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) (e.g., the TCI states are between the TCI states (respectively) with CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values)). The PDSCH is scheduled by one or more scheduling DCIs received in the CORESET associated / configured with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) (respectively), which may be indicated in one or more beam indication DCIs received in the CORESET associated / configured with both (respectively) CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) - for example, t_1 (e.g., in terms of timeslots, symbols, etc.) after receiving the beam indication DCI (e.g., t_1 timeslots / symbols after the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI), whereby the PDSCH may be scheduled via higher layer RRC signaling / parameters and / or MAC The CE command and / or dynamic DCI-based L1 signaling receives the beam indication DCI in the CORESET associated / configured with (respectively) CORESETPoolIndex value 0 and / or 1 (and therefore, the corresponding / associated PCI value) according to the network's configuration / instruction, and / or the beam indication DCI may be received at the earliest or latest time among all beam indication DCIs received in the CORESET associated / configured with the CORESETPoolIndex value 0 or 1 (and therefore, the corresponding / associated PCI value).

[0235] In the present disclosure, t_1 may be referred to as a beam application time specified under a unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries a PDSCH allocation, and when the UE may transmit the last symbol of a PUCCH having HARQ-ACK information corresponding to a PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and the BeamAppTime_r17 symbols may be applied in the application of the beam indication, for example, with a CORESETPoolIndex value of 0 and / or 1 (and therefore, the corresponding / associated P CI value); (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; the first time slot and BeamAppTime_r17 symbols can both be determined on the carrier with the smallest SCS among the carriers associated with the beam indication, for example, CORESETPoolIndex values ​​0 and / or 1 (and therefore, the corresponding / associated PCI value) to which the beam indication is applied.

[0236] In one example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 0) associated with the serving cell PCI and, for example, the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value (and, therefore, the serving cell PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, then the UE may use / apply the scheduling offset for the CORESETPoolIndex value (and, Thus, the UE receives the PDSCH in accordance with one or more (previously) indicated TCI states of the serving cell PCI (e.g., in a beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with the serving cell PCI), and / or when / if the UE is configured / provided by the network with enableTwoDefaultBeamsMDCI as specified in the present disclosure herein (and / or set to "enabled"), the UE may use / apply the TCI states for CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated serving cell PCI and the beam indication DCI_a' except for the serving cell PCI). one or more (e.g., two) (previously) indicated TCI states of one or more (e.g., two) (previously) indicated TCI states (e.g., in beam indication DCI_a' received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively) to simultaneously receive, for example, PDSCHs associated with CORESETPoolIndex values ​​0 and 1, respectively (and therefore, the corresponding / associated serving cell PCI and PCI other than the serving cell PCI) scheduled / activated by PDCCH / DCI received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1) the beam indication DC the time offset between I_a' (e.g., the earliest or latest time received among all beam indication DCIs received in the CORESET associated / configured with CORESETPoolIndex value 0 and / or 1 and thus corresponding serving cell PCI and PCI other than serving cell PCI) and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_a' is received at the latest time relative to the beam indication DCI_a,and / or (3) the TCI state indicated in the beam indication DCI_a' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_a' is one or two, and / or (5) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled). ,

[0237] In another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_b received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a PCI other than the serving cell PCI and, for example, the first symbol / timeslot of a PDSCH associated with the CORESETPoolIndex value (and, therefore, a PCI other than the serving cell PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, then the UE may use / apply the CORESETPoolIndex value for the CORESETPoolIndex value. dex value (and therefore, PCI other than the serving cell PCI) for one or more (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a PCI other than the serving cell PCI) to receive a PDSCH, and / or when / if the UE is configured / provided by the network with enableTwoDefaultBeamsMDCI as specified herein (and / or set to "enabled"), then the UE may use / apply the TCI states for CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated one or more (e.g., two) (previously) indicated TCI states of one or more (e.g., two) of a serving cell PCI and a PCI other than the serving cell PCI (e.g., in beam indication DCI_b' received in a CORESET associated with / configured with CORESETPoolIndex values ​​0 and 1, respectively) to simultaneously receive, for example, PDSCHs associated with CORESETPoolIndex values ​​0 and 1, respectively (and therefore, the corresponding / associated serving cell PCI and PCI other than the serving cell PCI), respectively, scheduled / activated by PDCCH / DCI received in a CORESET associated with / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1 ) the time offset between the beam indication DCI_b' (e.g., the time duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / slot of the PDSCH) and the PDSCH is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (2) the beam indication DCI_b' is received at the latest time relative to the beam indication DCI_b,and / or (3) the TCI state indicated in the beam indication DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_b' is one or two, and / or (5) the PDSCH can be at least a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled). ,

[0238] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 0) associated with the serving cell PCI and the first symbol / time slot of the PDSCH associated with the CORESETPoolIndex value (and therefore, the serving cell PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if the UE is configured / provided by the network as disclosed in the present invention When enableTwoDefaultBeamsMDCI is specified herein (and / or is set to "enabled"), the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value associated with a serving cell PCI (e.g., 0)) and (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value associated with a PCI other than the serving cell PCI (e.g., 1 ) of one or more (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a PCI other than the serving cell PCI) to (simultaneously) receive a PDSCH, wherein (1) a time offset between the beam indication DCI_a' and the PDSCH (e.g., a duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two,And / or (6) the PDSCH may be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (e.g., when enableTwoDefaultBeamsMDCI is configured / enabled).

[0239] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 1) associated with the PCI other than the serving cell PCI and the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value (and therefore, the PCI other than the serving cell PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, and / or when / if the UE is configured / provided by the network as in the present invention When enableTwoDefaultBeamsMDCI as specified herein is disclosed (and / or set to "enabled"), the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a serving cell PCI) to receive at least non-UE-specific (or common) PDSCHs, and (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 0) associated with a serving cell PCI to receive at least non-UE-specific (or common) PDSCHs, and (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 0) associated with a serving cell PCI to receive at least non-UE-specific (or common) PDSCHs. one or more (previously) indicated TCI states of a PoolIndex value (e.g., 1) (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a PCI other than a serving cell PCI) to receive at least a UE-specific PDSCH, wherein (1) a time offset between the beam indication DCI_a' and the PDSCH (e.g., a duration / difference between a last symbol / slot of a PDCCH / PDCCH candidate carrying the beam indication DCI_a' and a first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState,and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two, and / or (6) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled). ,

[0240] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of a PDCCH / PDCCH candidate carrying beam indication DCI_a received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a serving cell PCI and, for example, the first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, serving cell PCI) scheduled by beam indication DCI_a) is less than or equal to t_1 associated with beam indication DCI_a, and / or when / if enableTwoDefaultBeamsMDCI as specified in the present disclosure is configured / provided to the UE by the network (and / or set to “enabled”), then the UE may use / apply (1) for beam indication DCI_a associated with a serving cell PCI. (e.g., CORESETPoolIndex="0") or a PCI other than the serving cell PCI (e.g., CORESETPoolIndex="1"), and (2) the lowest CORESET in the CORESETs configured with the same value of CORESETPoolIndex associated with the serving cell PCI (e.g., CORESETPoolIndex="0") or a PCI other than the serving cell PCI (e.g., CORESETPoolIndex="1") in the most recent timeslot in which one or more CORESETs associated with the same value of CORESETPoolIndex were monitored by the UE within the active BWP of the serving cell. one or more indicated TCI states of a CORESET associated with a monitored search space of an ID to (simultaneously) receive a PDSCH, wherein (1) a time offset between beam indication DCI_a' and the PDSCH (e.g., a duration / difference between a last symbol / slot of a PDCCH / PDCCH candidate carrying beam indication DCI_a' and a first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_a' is received at a recent time relative to the beam indication DCI_a, and / or (3) the TCI state indicated in the beam indication DCI_a' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_a' is one or two, and / or (5) the PDSCH may be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (e.g.,When enableTwoDefaultBeamsMDCI is configured / enabled).

[0241] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 1) associated with the PCI other than the serving cell PCI and, for example, the first symbol / time slot of the PDSCH associated with the CORESETPoolIndex value (and therefore, the PCI other than the serving cell PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, and / or when / if the UE is configured / provided by the network as described in the present disclosure When enableTwoDefaultBeamsMDCI as specified herein is turned on (and / or set to “enabled”), the UE may use / apply (1) the lowest CORESET among the CORESETs configured with the same value of CORESETPoolIndex associated with the serving cell PCI (e.g., CORESETPoolIndex = “0”) or a PCI other than the serving cell PCI (e.g., CORESETPoolIndex = “1”) in the most recent timeslot in which one or more CORESETs associated with the same value of CORESETPoolIndex were monitored by the UE within the active BWP of the serving cell. (1) one or more indicated TCI states of a CORESET associated with a monitored search space with an ID to receive at least a non-UE-specific (or common) PDSCH, and (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 1) associated with a PCI other than a serving cell PCI (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a PCI other than a serving cell PCI) to receive at least a UE-specific PDSCH, which (1) the time offset between the beam indication DCI_b' and the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (2) the beam indication DCI_b' is received at the latest time relative to the beam indication DCI_b, and / or (3) the TCI state indicated in the beam indication DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in the beam indication DCI_b' is one or two,And / or (5) the PDSCH may be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (e.g., when enableTwoDefaultBeamsMDCI is enabled / configured).

[0242] Optionally, when inter-cell multi-TRP operation is enabled, as specified in the present disclosure herein, each CORESET corresponding to a different CORESETPoolIndex value provided by a ControlResourceSet may be associated with a different physical cell ID, for example via an activation / indication TCI state of (for) the CORESET, wherein a CORESET associated / configured with one CORESETPoolIndex value (e.g., 0) may be associated with a first PCI other than the serving cell physical cell ID, and a CORESET associated / configured with another CORESETPoolIndex value (e.g., 1) may be associated with a second PCI other than the serving cell PCI. For a CORESET pool index value (e.g., 0 or 1) and thus the corresponding / associated PCI as specified herein by the present disclosure, the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of the TCI states associated with the CORESETPoolIndex value (and thus, the corresponding / associated PCI value) for receiving a PDSCH associated with the CORESETPoolIndex value (and thus, the corresponding / associated PCI value) (e.g., the TCI state is indicated in a beam indication DCI received in the CORESET associated / configured with the CORESETPoolIndex value) - for example, the PDSCH is scheduled by a scheduling DCI received in the CORESET associated / configured with the CORESETPoolIndex value t_1 (e.g., in terms of time slots, symbols, etc.) after receiving the beam indication DCI (e.g., t_1 time slots / symbols after the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI).

[0243] In the present disclosure, t_1 may be referred to as a beam application time specified under a unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries a PDSCH allocation, and when the UE may transmit the last symbol of a PUCCH having HARQ-ACK information corresponding to a PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols may be applied. Determined on the carrier with the smallest SCS among the carriers to which beam indication is applied; (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and BeamAppTime_r17 symbols can be determined on the carrier with the smallest SCS among the carriers to which beam indication is applied.

[0244] Optionally, when enableTwoBeamsMDCI specified by the present disclosure herein is configured / provided to the UE by the network, the UE may be able to use / apply one or more of the indicated TCI states / TCI state pairs of TCI states associated (respectively) with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) to simultaneously receive PDSCHs associated (respectively) with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) (e.g., the TCI states are between the TCI states (respectively) with CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values)). The PDSCH is scheduled by one or more scheduling DCIs received in the CORESET associated / configured with both CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) (respectively), which may be indicated in one or more beam indication DCIs received in the CORESET associated / configured with both (respectively) CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated PCI values) - for example, t_1 (e.g., in terms of timeslots, symbols, etc.) after receiving the beam indication DCI (e.g., t_1 timeslots / symbols after the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI), whereby the PDSCH may be scheduled via higher layer RRC signaling / parameters and / or MAC The CE command and / or dynamic DCI-based L1 signaling receives the beam indication DCI in the CORESET associated / configured with (respectively) CORESETPoolIndex value 0 and / or 1 (and therefore, the corresponding / associated PCI value) according to the network's configuration / instruction, and / or the beam indication DCI may be received at the earliest or latest time among all beam indication DCIs received in the CORESET associated / configured with the CORESETPoolIndex value 0 or 1 (and therefore, the corresponding / associated PCI value).

[0245] In the present disclosure, t_1 may be referred to as a beam application time specified under a unified TCI framework, which is defined as follows: (1) When / if the beam indication DCI also carries a PDSCH allocation, and when the UE may transmit the last symbol of a PUCCH having HARQ-ACK information corresponding to a PDSCH scheduled by the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, then one or more indicated TCI states may be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; both the first time slot and the BeamAppTime_r17 symbols may be applied in the application of the beam indication, for example, with a CORESETPoolIndex value of 0 and / or 1 (and therefore, the corresponding / associated P CI value); (2) when / if the beam indication DCI does not carry PDSCH allocation, and when the UE can transmit the last symbol of the PUCCH with HARQ-ACK information corresponding to the beam indication DCI, and if one or more indicated TCI states are different from the previously indicated TCI states, one or more indicated TCI states can be applied starting from the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH; the first time slot and BeamAppTime_r17 symbols can both be determined on the carrier with the smallest SCS among the carriers associated with the beam indication, for example, CORESETPoolIndex values ​​0 and / or 1 (and therefore, the corresponding / associated PCI value) to which the beam indication is applied.

[0246] In one example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 0) associated with the first PCI and, for example, the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value (and, therefore, the first PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, then the UE may use / apply one or more of the CORESETPoolIndex value (and, therefore, the first PCI) for the CORESETPoolIndex value. The UE may receive a PDSCH with multiple (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI), and / or when / if the UE is configured / provided by the network with enableTwoDefaultBeamsMDCI as specified herein (and / or set to "enabled"), the UE may use / apply one or more (e.g., two) (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI) for receiving a PDSCH, and / or when / if the UE is configured / provided with enableTwoDefaultBeamsMDCI as specified herein by the present disclosure (and / or set to "enabled"), the UE may use / apply one or more (e.g., two) (previously) indicated TCI states (e.g., , in beam indication DCI_a' received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively), to simultaneously receive, for example, PDSCHs associated with CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated first and second PCIs) scheduled / activated by PDCCH / DCI received in CORESETs associated / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1) beam indication DCI_a' (for example, in beam indication DCI_a' associated / associated with CORESETPoolIndex values ​​0 and / or 1, and therefore, the corresponding first and / or second PCIs) =t_1, where (1) the time offset between beam indication DCI_a' (e.g., the earliest or latest received time among all beam indication DCIs received in the configured CORESET associated with CORESETPoolIndex value 0 and / or 1 and thus corresponding to the first PCI and / or second PCI) and PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with beam indication DCI_a,and / or (2) beam indication DCI_a' is received at the latest time relative to beam indication DCI_a, and / or (3) the TCI state indicated in beam indication DCI_a' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in beam indication DCI_a' is one or two, and / or (5) PDSCH can be UE-specific PDSCH and / or non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is enabled / configured). ,

[0247] In another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b received in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 1) associated with the second PCI and, for example, the first symbol / timeslot of the PDSCH associated with the CORESETPoolIndex value (and, therefore, the second PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, then the UE may use / apply one of the CORESETPoolIndex value (and, therefore, the second PCI) associated with the CORESETPoolIndex value. or multiple (previously) indicated TCI states (e.g., in beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with the second PCI) to receive the PDSCH, and / or when / if the UE is configured / provided by the network with enableTwoDefaultBeamsMDCI as specified herein by the present disclosure (and / or set to "enabled"), the UE may use / apply one or more (e.g., two) (previously) indicated TCI states (e.g., in beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with the second PCI) for receiving the PDSCH, and / or when / if the UE is configured / provided with enableTwoDefaultBeamsMDCI as specified herein by the present disclosure (and / or set to "enabled"), the UE may use / apply one or more (e.g., two) (previously) indicated TCI states (e.g., For example, in a beam indication DCI_b' received in a CORESET associated / configured with CORESETPoolIndex values ​​0 and 1, respectively), to simultaneously receive, for example, a PDSCH associated with CORESETPoolIndex values ​​0 and 1 (and therefore, the corresponding / associated first and second PCIs) scheduled / activated by a PDCCH / DCI received in a CORESET associated / configured with CORESETPoolIndex values ​​0 and 1, respectively, wherein (1) a beam indication DCI_a' (for example, in a beam indication DCI_b' received in a CORESET associated / configured with CORESETPoolIndex values ​​0 and / or 1, respectively, and therefore, the corresponding / associated first PCI and second PCI =t_1, where (1) the time offset between the beam indication DCI_b' (e.g., the earliest or latest received time among all beam indication DCIs received in the configured CORESET associated with CORESETPoolIndex value 0 and / or 1 and thus corresponding to the first PCI and / or second PCI) and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b,and / or (2) beam indication DCI_b' is received at the latest time relative to beam indication DCI_b, and / or (3) the TCI state indicated in beam indication DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (4) the number of TCI states indicated in beam indication DCI_b' is one or two, and / or (5) PDSCH can be at least UE-specific PDSCH and / or non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is enabled / configured). ,

[0248] In yet another example, when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI and, for example, a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, the first PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI and a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, the first PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if a t_1 is configured / provided to the UE by the network as described in the present invention. When enableTwoDefaultBeamsMDCI as specified herein is disclosed (and / or set to "enabled"), the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI) for a CORESETPoolIndex value (e.g., 0) associated with a first PCI, and (2) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI. one or more (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI) to (simultaneously) receive a PDSCH, wherein (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_b' is received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI, the time offset between I_b' and PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two,And / or (6) the PDSCH may be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (e.g., when enableTwoDefaultBeamsMDCI is enabled / configured).

[0249] In yet another example, when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI and, for example, a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, a second PCI) scheduled by the beam indication DCI_a') is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI and a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, a second PCI) scheduled by the beam indication DCI_a') is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if a UE is configured / provided by the network When enableTwoDefaultBeamsMDCI is enabled (and / or set to "enabled") as specified herein, the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., received in a beam indication DCI_a' in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI) for a CORESETPoolIndex value (e.g., 0) associated with a first PCI, and (2) one or more (previously) indicated TCI states (e.g., received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI. one or more (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI) to (simultaneously) receive a PDSCH, wherein (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_b' is received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI, to (simultaneously) receive a PDSCH, wherein (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the beam indication DCI_b' is received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI the time offset between I_b' and PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (separate) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two,And / or (6) the PDSCH may be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (e.g., when enableTwoDefaultBeamsMDCI is configured / enabled).

[0250] In yet another example, when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI and, for example, a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, the first PCI) scheduled by the beam indication DCI_a) is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if an e is configured / provided to the UE by the network as specified in the present disclosure herein nableTwoDefaultBeamsMDCI (and / or set to "enabled"), the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI) to receive at least a UE-specific PDSCH, and / or (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 1) associated with a second PCI. multiple (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated with / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI) to receive at least a UE-specific PDSCH, and / or (3) one or more (previously) indicated TCI states for a serving cell PCI (e.g., in a beam indication DCI received in a CORESET associated with / configured with a serving cell PCI) to receive at least a non-UE-specific (or common) PDSCH, wherein (1) a beam indication DCI_a' is a time offset between the PDSCH and the beam indication DCI (e.g., a beam indication DCI carrying the beam indication DCI_b'). (i) the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a,and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two, and / or (6) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled). ,

[0251] In yet another example, when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_b received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI and, for example, a first symbol / timeslot of a PDSCH associated with a CORESETPoolIndex value (and, therefore, a second PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, and / or when / if an e is configured / provided to the UE by the network as specified in the present disclosure herein nableTwoDefaultBeamsMDCI (and / or set to "enabled"), the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in beam indication DCI_a' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI) to receive at least a UE-specific PDSCH, and / or (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 1) associated with a second PCI. multiple (previously) indicated TCI states (e.g., in a beam indication DCI_b' received in a CORESET associated with / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI) to receive at least a UE-specific PDSCH, and / or (3) one or more (previously) indicated TCI states for a serving cell PCI (e.g., in a beam indication DCI received in a CORESET associated with / configured with a serving cell PCI) to receive at least a non-UE-specific (or common) PDSCH, wherein (1) a beam indication DCI_a' is a time offset between the PDSCH and the beam indication DCI (e.g., a beam indication DCI carrying the beam indication DCI_b'). (i) the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g., the duration / difference between the last symbol / timeslot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / timeslot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a,and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two, and / or (6) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled). ,

[0252] In yet another example, when / if the scheduling offset (e.g., the duration / difference between the last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_a received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with a first PCI and, for example, the first symbol / timeslot of a PDSCH associated with the CORESETPoolIndex value (and, therefore, the first PCI) scheduled by the beam indication DCI_a is less than or equal to t_1 associated with the beam indication DCI_a, and / or when / if enableTwoDefaultBeamsMDCI as specified herein is configured / provided to the UE by the network (and / or is set to “enabled”), then the UE may use / apply (1) one or more (previously) indicated TCI states for the CORESETPoolIndex value (e.g., 0) associated with the first PCI (e.g., 0) in the CORESET associated / configured with the CORESETPoolIndex value (e.g., 0) associated with the first PCI; RESET) to receive at least the UE-specific PDSCH, and / or (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 1) associated with the second PCI (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with the second PCI) to receive at least the UE-specific PDSCH, and / or (3) in a recent timeslot (in which one or more CORESETs associated with the same value of the serving cell PCI or CORESETPoolIndex are monitored by the UE within the active BWP of the serving cell), the CORESET with the lowest CORESET associated / configured with the serving cell PCI or configured with the same value of the CORESETPoolIndex associated with the first PCI (e.g., CORESETPoolIndex="0") or the second PCI (e.g., CORESETPoolIndex="1") The TCI state of one or more indications of the CORESET associated with the monitored search space of the ID is determined to receive at least a non-UE-specific (or common) PDSCH, wherein (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / time slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g.,(difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two, and / or (6) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled).

[0253] In yet another example, when / if a scheduling offset (e.g., a duration / difference between a last symbol / timeslot of a PDCCH / PDCCH candidate carrying a beam indication DCI_b received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with a second PCI and, for example, a first symbol / timeslot of a PDSCH associated with the CORESETPoolIndex value (and, therefore, the second PCI) scheduled by the beam indication DCI_b) is less than or equal to t_1 associated with the beam indication DCI_b, and / or when / if enableTwoDefaultBeamsMDCI as specified herein is configured / provided to the UE by the network (and / or is set to “enabled”), then the UE may use / apply (1) one or more (previously) indicated TCI states (e.g., in CORESET associated / configured with a CORESETPoolIndex value (e.g., 0) associated with the first PCI; RESET) to receive at least the UE-specific PDSCH, and / or (2) one or more (previously) indicated TCI states for a CORESETPoolIndex value (e.g., 1) associated with the second PCI (e.g., in a beam indication DCI_b' received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 1) associated with the second PCI) to receive at least the UE-specific PDSCH, and / or (3) in a recent timeslot (in which one or more CORESETs associated with the same value of the serving cell PCI or CORESETPoolIndex are monitored by the UE within the active BWP of the serving cell), the CORESET with the lowest CORESET associated / configured with the serving cell PCI or configured with the same value of the CORESETPoolIndex associated with the first PCI (e.g., CORESETPoolIndex="0") or the second PCI (e.g., CORESETPoolIndex="1") The TCI state of one or more indications of the CORESET associated with the monitored search space of the ID is determined to receive at least a non-UE-specific (or common) PDSCH, wherein (1) the time offset between the beam indication DCI_a' and the PDSCH (e.g., the duration / difference between the last symbol / time slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_a' and the first symbol / time slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_a, and / or (2) the time offset between the beam indication DCI_b' and the PDSCH (e.g.,(difference between the last symbol / slot of the PDCCH / PDCCH candidate carrying the beam indication DCI_b' and the first symbol / slot of the PDSCH) is greater than or equal to t_1 associated with the beam indication DCI_b, and / or (3) the beam indication DCI_a' and / or DCI_b' are received at the latest time relative to the beam indication DCI_a, and / or (4) the TCI state indicated in the beam indication DCI_a' and / or DCI_b' is a joint or (individual) DL TCI state provided by TCI-State or DLorJoint-TCIState, and / or (5) the number of TCI states indicated in the beam indication DCI_a' and / or DCI_b' is one or two, and / or (6) the PDSCH can be a UE-specific PDSCH and / or a non-UE-specific (or common) PDSCH (for example, when enableTwoDefaultBeamsMDCI is configured / enabled).

[0254] As specified in the present disclosure herein, the network may indicate / configure / provide to the UE that inter-cell multi-TRP operation is enabled (e.g., under a unified TCI framework), for example, via higher-layer RRC signaling / parameters (e.g., higher-layer parameters represented by InterCellMdciMtrp) and / or MAC CE commands and / or L1 signaling based on dynamic DCI. When the UE is provided / configured by the network, for example, the higher-layer parameter InterCellMdciMtrp is set to "enabled", and / or when two values ​​of CORESETPoolIndex (i.e., 0 and 1) are provided to the UE in PDCCH-Config, and / or when a list / set / pool of one or more PCIs including at least one PCI other than the serving cell PCI is provided / configured / indicated to the UE by the network, for example, via higher-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI, according to those specified in this document of the present disclosure, a value of 0 (or 1) of CORESETPoolIndex and thus at least the corresponding CORESET configured with the same value of 0 (or 1) of CORESETPoolIndex can be associated with the serving cell PCI, and a value of 1 (or 0) of CORESETPoolIndex and thus at least the corresponding CORESET configured with the same value of 1 (or 0) of CORESETPoolIndex can be associated with the PCI other than the serving cell PCI.

[0255] One or more indicated TCI states associated with the value of CORESETPoolIndex (e.g., when one or more TCI states are indicated in DCI received in a CORESET associated / configured with the value of CORESETPoolIndex) may also be associated with a PCI (e.g., a serving cell PCI or a PCI other than a serving cell PCI).

[0256] In one example, a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool may be provided / indicated / configured in a high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State that configures the TCI state; the TCI state (e.g., when activated / indicated in a corresponding beam activation / indication MAC CE or DCI) is associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) provided / configured / indicated in the corresponding high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State. Optionally, when the high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State that configures the TCI state does not include / include / indicate / contain a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool, the TCI state (e.g., when activated / indicated in a corresponding beam activation / indication MAC CE or DCI) is associated with the serving cell PCI.

[0257] In another example, a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool may be provided / indicated / configured in a high-level parameter configuring a list / group of TCI states / TCI state IDs; in this case, the TCI state or TCI state ID configured / provided in the list / group of TCI states / TCI state IDs may be associated with the PCI or PCI index provided / indicated / configured therein. Optionally, a CORESETPoolIndex associated with, for example, a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool may be provided / indicated / configured in a high-level parameter configuring a list / group of TCI states / TCI state IDs; in this case, the TCI state or TCI state ID configured / provided in the list / group of TCI states / TCI state IDs may be associated with the CORESETPoolIndex value indicated therein and therefore the PCI or PCI index associated with the CORESETPoolIndex.

[0258] In yet another example, when a TCI state is indicated in a beam indication DCI received in a CORESET associated / configured with a value of 0 (or 1) for CORESETPoolIndex (e.g., by one or more TCI code points of one or more TCI fields in DCI format 1_1 / 1_2 with or without DL allocation), the indicated TCI state may be associated with a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the value of 0 (or 1) for CORESETPoolIndex. When a TCI state is indicated in a beam indication DCI received in a CORESET associated / configured with a value of 1 (or 0) for CORESETPoolIndex (e.g., by one or more TCI code points of one or more TCI fields in DCI format 1_1 / 1_2 with or without DL allocation), the indicated TCI state may be associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the value of 1 (or 0) for CORESETPoolIndex.

[0259] In yet another example, the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) may indicate / contain / include / configure / include the value of CORESETPoolIndex; for this design example, all TCI states activated by the beam indication / activation MAC CE may be associated with the CORESETPoolIndex indicated / provided therein and therefore a PCI or PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the CORESETPoolIndex. For example, when the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) indicates / contains / includes / configures / includes a CORESETPoolIndex value of 0 (or 1), all TCI states activated by the beam indication MAC CE can be associated with the CORESETPoolIndex value of 0 (or 1) and therefore the PCI (e.g., serving cell PCI) or PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the CORESETPoolIndex value of 0 (or 1). When the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) indicates / contains / includes / configures / includes a value of 1 (or 0) for CORESETPoolIndex, all TCI states activated by the beam indication MAC CE can be associated with the value of 1 (or 0) for CORESETPoolIndex and therefore the PCI (e.g., a PCI other than the serving cell PCI) or PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the value of 1 (or 0) for CORESETPoolIndex.

[0260] In yet another example, the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) may indicate / contain / include / configure / include a PCI value or a PCI index (pointing to an entry / PCI in a PCI list / set / pool); for this design example, all TCI states activated by the beam indication / activation MAC CE may be associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI list / set / pool).

[0261] In yet another example, the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) may indicate / contain / include / configure / include one or more values ​​of CORESETPoolIndex. Each of the TCI states activated / indicated in the beam indication / activation MAC CE may be associated with a value of CORESETPoolIndex indicated / provided therein (e.g., 0 or 1) and thus a PCI or PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the CORESETPoolIndex. For example, when the TCI state activated / indicated by the beam indication MAC CE is associated with a value of 0 (or 1) of CORESETPoolIndex provided / indicated therein, the TCI state may be associated with a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the value of 0 (or 1) of CORESETPoolIndex. When the TCI state activated / indicated by the beam indication MAC CE is associated with a value of 1 (or 0) for CORESETPoolIndex provided / indicated therein, the TCI state may be associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) associated with the value of 1 (or 0) for CORESETPoolIndex.

[0262] In yet another example, the beam indication / activation MAC CE (e.g., (enhanced) TCI state activation / deactivation MAC CE) may indicate / contain / include / configure / comprise one or more PCI values ​​or PCI indexes (each pointing to an entry / PCI in a PCI list / set / pool). Each of the TCI states activated / indicated in the beam indication / activation MAC CE may be associated with a PCI value or a PCI index (pointing to an entry / PCI in a PCI list / set / pool).

[0263] As specified in the present disclosure herein, the enabling of inter-cell multi-TRP operation (e.g., under a unified TCI framework) may be indicated / configured / provided to the UE by the network, for example, via higher-layer RRC signaling / parameters (e.g., higher-layer parameters represented by InterCellMdciMtrp) and / or MAC CE commands and / or L1 signaling based on dynamic DCI. When the higher-layer parameter InterCellMdciMtrp is provided / configured to the UE by the network, for example, as being set to "enabled", and / or when two values ​​(i.e., 0 and 1) of CORESETPoolIndex are provided to the UE in PDCCH-Config, and / or when a list / set / pool of one or more PCIs including at least one PCI other than the serving cell PCI is provided / configured / indicated to the UE by the network, for example, via higher-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI, the TCI state may be associated with a PCI (e.g., a serving cell PCI or a PCI other than the serving cell PCI) according to those specified in the present disclosure herein.

[0264] For example, a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool may be provided / indicated / configured in a high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State that configures the TCI state; therefore, the TCI state may be associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) provided / configured / indicated in the corresponding high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State. In addition, when the high-level parameter TCI-State, DLorJointTCI-State, or ULTCI-State that configures the TCI state does not contain / include / indicate / contain a PCI or a PCI index pointing to an entry / PCI in a PCI list / set / pool, the TCI state may be associated with the serving cell PCI. Different values ​​of CORESETPoolIndex (e.g., 0 and 1) may be associated with different PCI values ​​via one or more TCI states activated / indicated in a beam activation / indication MAC CE or DCI.

[0265] In one example, one or more TCI state lists / groups may be configured to the UE by the network using a higher-level RRC, wherein the TCI state list / group may contain / include / include one or more TCI states and be associated with the value of CORESETPoolIndex. For example, the CORESETPoolIndex value may be provided / indicated / configured in a higher-level RRC parameter configuring the TCI state list / group.

[0266] In another example, when one or more TCI states associated with a PCI or a PCI index as specified herein by the present disclosure are indicated in a beam indication DCI received in a CORESET associated / configured with a CORESETPoolIndex value (e.g., 0 or 1), the CORESETPoolIndex value may also be associated with a PCI or a PCI index. For example, when one or more TCI states associated with a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) as specified herein by the present disclosure are indicated in a beam indication DCI received in a CORESET associated / configured with a CORESETPoolIndex value of 0 (or 1), the CORESETPoolIndex value of 0 (or 1) may be associated with a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool). When the beam indication DCI received in a CORESET associated / configured with a value of 1 (or 0) for CORESETPoolIndex indicates one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI list / set / pool) as specified in the present disclosure herein, the value of 1 (or 0) for CORESETPoolIndex may be associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0267] In yet another example, a beam indication / activation MAC CE (e.g., (enhanced) unified TCI state activation / deactivation MAC CE) may indicate / provide / include / comprise / contain a CORESETPoolIndex value. Furthermore, one or more (or all) of the TCI states activated by the beam indication / activation MAC CE may be associated with a PCI / PCI index, according to those specified herein by the present disclosure. Thus, the CORESETPoolIndex value may be associated with a PCI / PCI index via one or more (or all) of the activated TCI states in the MAC CE.

[0268] In yet another example, a beam indication / activation MAC CE (e.g., (enhanced) unified TCI state activation / deactivation MAC CE) may indicate / provide / include / comprise / contain one or more CORESETPoolIndex values, each CORESETPoolIndex value being associated with one or more TCI states activated / indicated therein. When the TCI state activated by the MAC CE associated with the value of CORESETPoolIndex is associated with a PCI / PCI index in accordance with those specified herein in the present disclosure, the CORESETPoolIndex value is also associated with the PCI / PCI index.

[0269] The UE may use / apply one or more TCI states associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and activated / indicated by a beam indication / activation MAC CE or a DCI in accordance with those specified in the present disclosure herein to receive one or more channels (e.g., PDCCH and / or PDSCH) and / or signals (such as CSI-RS) associated / configured with the value of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein and / or transmit one or more channels (such as PUCCH and / or PUSCH) and / or signals (such as SRS) associated / configured with the value of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0270] In one example, the UE may use / apply one or more TCI states associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MAC CE or a DCI activation / indication according to those specified in this disclosure herein to receive / monitor PDCCH candidates received in a CORESET associated / configured with a value of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) according to those specified in this disclosure herein. For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MAC CE or a DCI activation / indication according to those specified in this disclosure herein to receive / monitor PDCCH candidates received in a CORESET associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) according to those specified in this disclosure herein.

[0271] In addition, the UE can use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam-indicated / activated MACCE or a DCI activated / indicated MACCE in accordance with those specified in the present disclosure herein to receive / monitor PDCCH candidates received in a CORESET associated / configured with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0272] In another example, the UE may use / apply one or more TCI states associated with a PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MAC CE or a DCI activation / indication in accordance with those specified in the present disclosure herein to receive a PDSCH activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with the value of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein.

[0273] For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MAC CE or a DCI activation / indication according to those specified in the present disclosure herein to receive a PDSCH activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0274] In addition, the UE can use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MACCE or a DCI activation / indication according to those specified in the present disclosure herein to receive a PDSCH activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with a value of 1 (or 0) of the CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0275] In another example, the UE may use / apply one or more TCI states associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MAC CE or a DCI activation / indication in accordance with those specified in the present disclosure herein to receive / configured CSI-RS associated with a value of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein.

[0276] For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MAC CE or a DCI activation / indication according to those specified in the present disclosure herein to receive / configured CSI-RS associated with / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0277] In addition, the UE may use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MACCE or a DCI activation / indication in accordance with those specified in the present disclosure herein to receive / configured CSI-RS associated with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool). Regarding the association between CSI-RS resources and the value of CORESETPoolIndex or PCI or PCI index, the following examples may be provided.

[0278] In one example, a CORESETPoolIndex value, or an indicator representing / indicating a CORESETPoolIndex value, or an indicator representing / indicating one or more TCI states associated / specific to a CORESETPoolIndex value, or a PCI value or a PCI index pointing to an entry / PCI in a PCI list / set / pool may be provided / indicated / configured in a higher-layer RRC parameter associated / configured with a CSI-RS resource set containing / including / containing / configuring / providing CSI-RS resources. Here, the higher-layer RRC parameter may be CSI-AssociatedReportConfigInfo, CSI-ResourceConfig, CSI-ReportConfig, NZP-CSI-RS-ResourceSet, etc. of CSI-AperiodicTriggerState.

[0279] In another example, if a CSI-RS resource is activated / triggered by a DCI / PDCCH received in a CORESET associated / configured with a value of CORESETPoolIndex, then the CSI-RS resource is associated / specific to that value of CORESETPoolIndex.

[0280] In another example, when (enhanced) group-based beam reporting for MTRP operation is enabled, a value of 0 (or 1) of CORESETPoolIndex may be associated with a first aperiodic CSI resource set (and, therefore, the CSI-RS resources configured / provided therein) in the CSI-AssociateReportConfigInfo of the CSI-AperiodicTriggerState, and a value of 1 (or 0) of CORESETPoolIndex may be associated with a second aperiodic CSI resource set (and, therefore, the CSI-RS resources configured or provided therein) in the CSI-AssociateReportConfigInfo of the CSI-AperiodicTriggerState. In addition to the above / specified fixed rules, the association between the CORESETPoolIndex value and the first / second aperiodic CSI resource set in the CSI-AssociateReportConfigInfo of the CSI-AperiodicTriggerState may also be indicated / configured / provided to the UE by the network, for example, via higher-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI.

[0281] In another example, the UE may use / apply one or more TCI states associated with a PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) and beam indicated / activated MAC CE or DCI activated / indicated in accordance with those specified in the present disclosure herein to transmit a PUCCH associated / configured with the value of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein.

[0282] For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MAC CE or a DCI activation / indication in accordance with those specified in the present disclosure herein to transmit a PUCCH associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0283] In addition, the UE may use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activated MACCE or a DCI activated / indicated, in accordance with those specified herein in the present disclosure, to transmit a PUCCH associated / configured with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool). In order to associate a PUCCH resource with the value of CORESETPoolIndex, a CORESETPoolIndex value, an indicator representing / indicating a CORESETPoolIndex value, or an indicator indicating one or more TCI states associated with / specific to the CORESETPoolIndex value may be provided / indicated / configured in higher-layer RRC signaling / parameters configuring a PUCCH resource or a PUCCH resource group containing / including / including the PUCCH resource, and / or a MAC CE command and / or L1 signaling based on dynamic DCI.

[0284] In another example, the UE may use / apply one or more TCI states associated with a PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MAC CE or a DCI activation / indication in accordance with those specified in the present disclosure herein to transmit a PUSCH (e.g., dynamic grant (DG) PUSCH and type-2 configured grant (CG) PUSCH) activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with a value of CORESETPoolIndex associated with a PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein.

[0285] For example, the UE may use / apply one or more TCI states activated / indicated by a beam indication / activation MAC CE or a DCI associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) in accordance with those specified in the present disclosure herein to transmit a PUSCH (e.g., DG PUSCH and Type-2CG PUSCH) activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0286] In addition, the UE may use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam-indicated / activated MACCE or a DCI-activated / indicated PUSCH (e.g., DG PUSCH and Type-2CG PUSCH) in accordance with those specified in the present disclosure herein to transmit a PUSCH activated / scheduled by a DCI / PDCCH received in a CORESET associated / configured with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0287] In another example, the UE may use / apply one or more TCI states associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indicated / activated MAC CE or a DCI activated / indicated according to those specified in the present disclosure herein to transmit an SRS associated / configured with the value of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) according to those specified in the present disclosure herein.

[0288] For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam indication / activation MAC CE or a DC activation / indication according to those specified in the present disclosure herein to transmit an SRS associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0289] In addition, the UE may use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool), a beam-indicated / activated MACCE or a DCI activated / indicated, in accordance with those specified in the present disclosure herein to transmit an SRS associated / configured with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0290] Regarding the association between the SRS resource and the value of CORESETPoolIndex or the PCI or PCI index, the following examples may be provided.

[0291] In one example, if the SRS resource is activated / triggered by a DCI / PDCCH received in a CORESET associated / configured with a value of CORESETPoolIndex, the SRS resource is associated / specific to that value of CORESETPoolIndex.

[0292] In another example, when two SRS resource sets (a first SRS resource set and a second SRS resource set) are configured with a usage set to "codebook" or "non-codebook", a value of 0 (or 1) or a PCI (e.g., a serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) of CORESETPoolIndex may be associated with the first SRS resource set (and, therefore, the SRS resources configured / provided therein), and a value of 1 (or 0) or another PCI (e.g., a PCI other than the serving cell PCI) or another PCI index (pointing to another entry / PCI in a PCI set / list / pool) of CORESETPoolIndex may be associated with the second SRS resource set (and, therefore, the SRS resources configured / provided therein). In addition to the above / specified fixed rules, the association between the CORESETPoolIndex value and the first / second SRS resource set may also be indicated / configured / provided to the UE by the network, for example, via high-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI.

[0293] In another example, the UE may use / apply one or more TCI states associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indicated / activated MAC CE or a DCI activated / indicated according to those specified in the present disclosure herein to receive / transmit one or more RRC configured channels / signals (e.g., Type-1CG PUSCH) associated / configured with a value of CORESETPoolIndex associated with a PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) according to those specified in the present disclosure herein.

[0294] For example, the UE may use / apply one or more TCI states associated with a PCI (e.g., serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam indication / activation MAC CE or a DCI activation / indication in accordance with those specified in the present disclosure herein to receive / transmit one or more RRC configured channels / signals (e.g., Type-1CG PUSCH) associated / configured with a value of 0 (or 1) of CORESETPoolIndex associated with the PCI or a PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0295] In addition, the UE can use / apply one or more TCI states associated with a PCI (e.g., a PCI other than the serving cell PCI) or a PCI index (pointing to an entry / PCI in a PCI set / list / pool) and a beam-indicated / activated MACCE or DCI activated / indicated according to those specified in the present disclosure herein to receive / transmit one or more RRC-configured channels / signals (e.g., Type-1CG PUSCH) associated / configured with a value of 1 (or 0) of CORESETPoolIndex associated with the PCI or PCI index (pointing to an entry / PCI in a PCI set / list / pool).

[0296] For example, regarding the association between Type-1CG PUSCH and the value of CORESETPoolIndex or PCI or PCI index, the following example may be provided.

[0297] In one example, a CORESETPoolIndex value, or an indicator representing / indicating a CORESETPoolIndex value, or an indicator representing / indicating one or more TCI states associated with / specific to the CORESETPoolIndex value, or a PCI value or PCI index (pointing to an entry / PCI in a PCI set / list / pool) may be provided / indicated / configured in a higher-layer RRC parameter (e.g., ConfiguredGrantConfig) of a configuration type-1CG PUSCH.

[0298] In another example, when two SRS resource sets (a first SRS resource set and a second SRS resource set) are configured with a usage set to "codebook" or "non-codebook", the SRS resource set index / ID may be provided / indicated / configured in a higher-layer RRC parameter (e.g., ConfiguredGrantConfig) configuring the Type-1CG PUSCH. If the SRS resource set index / ID of the first (or second) SRS resource set is indicated / provided / configured in a higher-layer RRC parameter (e.g., ConfiguredGrantConfig) configuring the Type-1CGPUSCH, the Type-1CG PUSCH is associated with the first (or second) SRS resource set. Therefore, if the (first or second) SRS resource set is associated / specific to the value of CORESETPoolIndex according to those specified herein in the present disclosure, the Type-1CG PUSCH associated with the SRS resource set may also be associated / specific to the value of CORESETPoolIndex.

[0299] As specified in the present disclosure herein, one or more TCI states configured / activated / indicated by a TCI state list / group and / or beam indication / activation MAC CE and / or beam indication DCI may be associated with a PCI or PCI index (pointing to an entry / PCI in a PCI list / set / pool). For one or more channels / signals associated / configured with a PCI / PCI index, the UE may use / apply one or more configured / activated / indicated TCI states associated with the (same) PCI / PCI index.

[0300] The association between one or more channels / signals and PCI / PCI index may be according to one or more of the following examples.

[0301] In one example for PDCCH reception, a PDCCH / PDCCH candidate may be received in a CORESET associated / configured with a CORESETPoolIndex value; since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein in the present disclosure, the PDCCH / PDCCH candidate may also be associated with the PCI / PCI index. As specified / described herein in the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to receive a PDCCH / PDCCH candidate associated with the same PCI / PCI index.

[0302] In another example for PDSCH reception, the PDSCH may be scheduled / activated by one or more PDCCH / DCI received in a CORESET associated / configured with a CORESETPoolIndex value; since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein by the present disclosure, the PDSCH scheduled / activated by the PDCCH / DCI may also be associated with the PCI / PCI index. As specified / described herein by the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to receive the PDSCH associated with the same PCI / PCI index.

[0303] In another example for PUCCH transmission, the association between a CORESETPoolIndex value or a PCI or a PCI index and one or more PUCCH resources may be indicated / provided / configured to the UE by the network, for example, via high-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI. For example, a CORESETPoolIndex value or a PCI value or a PCI index may be provided / indicated / configured in high-layer RRC signaling / parameters and / or MAC CE commands that configure / indicate one or more PUCCH resources. For another example, one or more indicators indicating an association between a CORESETPoolIndex value or a PCI value or a PCI index and one or more PUCCH resources may be provided / indicated / configured in high-layer RRC signaling / parameters and / or MAC CE commands that configure / indicate one or more PUCCH resources. Since a CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein in accordance with the present disclosure, the corresponding PUCCH resource may also be associated with a PCI / PCI index. As specified / described herein, the UE may then use / apply the TCI state associated with the PCI / PCI index to transmit PUCCH resources associated with the same PCI / PCI index.

[0304] In yet another example for PUSCH transmission, the PUSCH may be scheduled / activated by one or more PDCCH / DCI received in a CORESET associated / configured with a CORESETPoolIndex value; since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein in the present disclosure, the PUSCH scheduled / activated by the PDCCH / DCI may also be associated with the PCI / PCI index. As specified / described herein in the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to transmit a PUSCH associated with the same PCI / PCI index.

[0305] In another example for CSI-RS reception, the network may indicate / provide / configure the association between a CORESETPoolIndex value or a PCI or a PCI index and one or more CSI-RS resources to the UE, for example, via high-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI. For example, a CORESETPoolIndex value or a PCI value or a PCI index may be provided / indicated / configured in a high-layer RRC signaling / parameter (e.g., CSI resource set / setting / trigger status) and / or a MAC CE command that configures / indicates / trigger one or more CSI-RS resources. For another example, one or more indicators indicating the association between a CORESETPoolIndex value or a PCI value or a PCI index and one or more CSI-RS resources may be provided / indicated / configured in a high-layer RRC signaling / parameter (e.g., CSI resource set / setting / trigger status) and / or a MAC CE command that configures / indicates / trigger one or more CSI-RS resources. Since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein by the present disclosure, the corresponding CSI-RS resource may also be associated with the PCI / PCI index. As specified / described herein by the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to receive the CSI-RS resource associated with the same PCI / PCI index.

[0306] In another example for SRS transmission, the association between a CORESETPoolIndex value or a PCI or a PCI index and one or more SRS resources may be indicated / provided / configured to the UE by the network, for example, via high-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI. For example, a CORESETPoolIndex value or a PCI value or a PCI index may be provided / indicated / configured in a high-layer RRC signaling / parameter (e.g., SRS resource set / setting / trigger status) and / or a MAC CE command that configures / indicates / trigger one or more SRS resources. For another example, one or more indicators indicating an association between a CORESETPoolIndex value or a PCI value or a PCI index and one or more SRS resources may be provided / indicated / configured in a high-layer RRC signaling / parameter (e.g., SRS resource set / setting / trigger status) and / or a MAC CE command that configures / indicates / trigger one or more SRS resources. Since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein by the present disclosure, the corresponding SRS resource may also be associated with the PCI / PCI index. As specified / described herein by the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to transmit the SRS resource associated with the same PCI / PCI index.

[0307] In another example of transmission / reception of configured channels / signals (including semi-persistent scheduling (SPS) PDSCH reception, periodic PUCCH transmission, configuration grant (CG) PUCCH transmission, etc.), the network may indicate / provide / configure the association between the CORESETPoolIndex value or PCI or PCI index and one or more configured channels / signals as described herein by the present disclosure, for example, via high-layer RRC signaling / parameters and / or MAC CE commands and / or L1 signaling based on dynamic DCI to the UE. For example, the CORESETPoolIndex value or PCI value or PCI index may be provided / indicated / configured in high-layer RRC signaling / parameters (e.g., SPS-Config, PUCCH-Config, ConfiguredGrantConfig, etc.) and / or MAC CE commands that configure / indicate / trigger one or more configured channels / signals. For another example, one or more indicators indicating the association between a CORESETPoolIndex value or a PCI value or a PCI index and one or more configured channels / signals as described herein may be provided / indicated / configured in a higher-layer RRC signaling / parameter (e.g., SPS-Config, PUCCH-Config, ConfiguredGrantConfig, etc.) and / or a MAC CE command that configures / indicates / trigger one or more configured channels / signals. Since the CORESETPoolIndex value may be associated with a PCI / PCI index according to those specified herein by the present disclosure, the corresponding configured channel / signal may also be associated with a PCI / PCI index. As specified / described herein by the present disclosure, the UE may then use / apply the TCI state associated with the PCI / PCI index to transmit / receive a configured channel / signal as described herein by the present disclosure that is associated with the same PCI / PCI index.

[0308] Fig.31 A block diagram of a terminal (or user equipment (UE)) according to an embodiment of the present disclosure is shown.

[0309] like Fig.31 As shown, the terminal according to the embodiment may include a transceiver 3110, a memory 3120 and a processor (or controller) 3130. The transceiver 3110, the memory 3120 and the processor (or controller) 3130 of the terminal may operate according to the communication method of the above-mentioned terminal. However, the components of the terminal are not limited thereto. For example, the terminal may include Fig.31 3100, the transceiver 3110, and the memory 3120 may be implemented as a single chip. In addition, the processor (or controller) 3130 may include at least one processor.

[0310] Transceiver 3110 refers to a terminal station receiver and a terminal transmitter collectively, and can transmit a signal to a base station or another terminal / receive a signal from a base station or another terminal. The signal transmitted to or received from the terminal may include control information and data. Transceiver 3110 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for low-noise amplification and down-conversion of the received signal. However, this is only an example of transceiver 3110, and the components of transceiver 3110 are not limited to RF transmitters and RF receivers.

[0311] In addition, the transceiver 3110 may receive a signal through a wireless channel and output it to the processor 3130 , and transmit a signal output from the processor (or controller) 3130 through a wireless channel.

[0312] The memory 3120 may store programs and data required for the operation of the terminal. In addition, the memory 3120 may store control information or data included in a signal obtained by the terminal. The memory 3120 may be a storage medium (e.g., a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media).

[0313] The processor (or controller) 3130 may control a series of processes so that the terminal operates as described above. For example, the processor (or controller) 3130 may receive a data signal and / or a control signal, and the controller 3130 may determine a result of receiving a signal transmitted by a base station and / or other terminals.

[0314] Fig.32 A block diagram of a base station according to an embodiment of the present disclosure is shown.

[0315] like Fig.32 As shown, the base station of the present disclosure may include a transceiver 3210, a memory 3220, and a processor (or controller) 3230. The transceiver 3210, the memory 3220, and the processor (or controller) 3230 of the base station may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include Fig.32 3200. In addition, the processor (or controller) 3230, the transceiver 3210, and the memory 3220 may be implemented as a single chip. In addition, the processor (or controller) 3230 may include at least one processor.

[0316] The transceiver 3210 collectively refers to a base station receiver and a base station transmitter, and can transmit signals to / receive signals from a terminal, another base station, and / or a core network function (or entity). The signals transmitted to or received from the base station may include control information and data. The transceiver 3210 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for low-noise amplification and down-conversion of the received signal. However, this is only an example of the transceiver 3210, and the components of the transceiver 3210 are not limited to the RF transmitter and the RF receiver.

[0317] In addition, the transceiver 3210 may receive a signal through a wireless channel and output it to the processor 3230 , and transmit a signal output from the processor (or controller) 3230 through a wireless channel.

[0318] The memory 3220 may store programs and data required for the operation of the base station. In addition, the memory 3220 may store control information or data included in a signal obtained by the base station. The memory 3220 may be a storage medium (e.g., ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media).

[0319] The processor (or controller) 3230 may control a series of processes so that the base station operates as described above. For example, the processor (or controller) 3230 may receive a data signal and / or a control signal, and the processor (or controller) 3230 may determine a result of receiving a signal transmitted by a terminal and / or a core network function.

[0320] The methods according to the embodiments described in the claims or the detailed description of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0321] When the electrical structure and method are implemented in software, a computer-readable recording medium having one or more programs (software modules) recorded thereon may be provided. One or more programs recorded in the computer-readable recording medium are configured to be executable by one or more processors in an electronic device. One or more programs include instructions for executing the methods of the embodiments described in the claims or the detailed description of the present disclosure.

[0322] The program (e.g., software module or software) may be stored in random access memory (RAM), non-volatile memory, including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, compact disk-ROM (CD-ROM), digital versatile disk (DVD), another type of optical storage device, or magnetic tape cassette. Alternatively, the program may be stored in a memory system that includes a combination of some or all of the foregoing memory devices. In addition, each memory device may include multiple.

[0323] The program may also be stored in an attachable storage device that can be accessed via a communication network such as the Internet, an intranet, a local area network (LAN), a wireless LAN (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected to an apparatus according to an embodiment of the present disclosure via an external port. Another storage device on the communication network may also be connected to an apparatus that performs an embodiment of the present disclosure.

[0324] In the foregoing embodiments of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form according to the embodiments. However, the singular or plural form is appropriately selected for ease of explanation, and the present disclosure is not limited thereto. Therefore, the elements expressed in plural form may also be configured as a single element, and the elements expressed in singular form may also be configured as multiple elements.

[0325] Although the drawings show different examples of user equipment, various changes may be made to the drawings. For example, the user equipment may include any number of each component in any suitable arrangement. In general, the drawings do not limit the scope of the present disclosure to any particular configuration. In addition, although the drawings show operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0326] Any of the above-described variations may be used independently or in combination with at least one other variation.

[0327] The above flow charts illustrate exemplary methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of steps, the individual steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0328] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be proposed to those skilled in the art. The present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A user equipment UE, comprising: The transceiver is configured as: Receiving downlink control information DCI indicating a first transmission configuration indication TCI state in a first control resource set CORESET; as well as receiving in radio resource control (RRC) signaling (i) a first indicator configuring a CORESETPoolIndex value associated with the first CORESET and (ii) a second indicator; as well as a processor operably coupled to the transceiver, the processor being configured to: identifying an association between the CORESETPoolIndex value and the first TCI state based on the first indicator; identifying, based on the second indicator, whether simultaneous reception is enabled before the indicated TCI state can be applied; as well as Based on the identification, one or more spatial filters are determined for receiving a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied, wherein the PDSCH is associated with the CORESETPoolIndex value.

2. The UE according to claim 1, wherein: The processor is further configured to: In a case where the CORESETPoolIndex value is 0, identifying that the first TCI state is associated with a CORESETPoolIndex value of 0; and When the CORESETPoolIndex value is 1, it is identified that the first TCI state is associated with the CORESETPoolIndex value 1.

3. The UE according to claim 1, wherein: The indicated TCI state is applicable starting from the following time slots: The first time slot of at least timeDurationForQCL symbols after the last symbol of the physical downlink control channel PDCCH carrying the DCI indicating the TCI status; The first time slot of at least BeamAppTime_r17 symbols after the last symbol of a physical uplink control channel PUCCH with hybrid automatic repeat request HARQ-acknowledgement ACK information, the HARQ-ACK information corresponding to a PDSCH scheduled by a DCI indicating the TCI state; or the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH with HARQ-ACK information corresponding to the DCI indicating the TCI state, and The processor is also configured to determine the first time slot and the BeamAppTime_r17 symbols based on a carrier having a minimum subcarrier spacing SCS among the carriers to which the indicated TCI state and the CORESETPoolIndex value are applied.

4. The UE according to claim 1, wherein: In a case where the second indicator indicates that the simultaneous reception is not enabled, the processor is further configured to determine the one or more spatial filters based on at least one of: the first TCI state; A TCI state for receiving a physical downlink control channel PDCCH carrying the DCI; and The TCI state for receiving the PDCCH of the CORESET having the lowest CORESET index among the CORESETs configured with the CORESETPoolIndex value in the most recent slot monitored in the search space.

5. A base station BS, comprising: The transceiver is configured as: Transmitting downlink control information DCI indicating a first transmission configuration indication TCI state in a first control resource set CORESET; as well as transmitting in radio resource control (RRC) signaling (i) a first indicator configuring a CORESETPoolIndex value associated with the first CORESET and (ii) a second indicator, The first indicator indicates a first indication, and the first indication is used to indicate the association between the CORESETPoolIndex value and the first TCI state. The second indicator indicates a second indication, and the second indication is used to indicate whether simultaneous reception is enabled before the indicated TCI state can be applied, wherein one or more spatial filters associated with a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied are indicated based on the first indication and the second indication, and The PDSCH is associated with the CORESETPoolIndex value.

6. The BS according to claim 5, wherein: In the case where the CORESETPoolIndex value is 0, the first TCI state is associated with the CORESETPoolIndex value 0; as well as When the CORESETPoolIndex value is 1, the first TCI state is associated with the CORESETPoolIndex value of 1.

7. The BS according to claim 5, wherein: The indicated TCI state is applicable starting from the following time slots: The first time slot of at least timeDurationForQCL symbols after the last symbol of the physical downlink control channel PDCCH carrying the DCI indicating the TCI status; The first time slot of at least BeamAppTime_r17 symbols after the last symbol of a physical uplink control channel PUCCH with hybrid automatic repeat request HARQ-acknowledgement ACK information, the HARQ-ACK information corresponding to a PDSCH scheduled by a DCI indicating the TCI state; or the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH with HARQ-ACK information corresponding to the DCI indicating the TCI state, and The first time slot and the BeamAppTime_r17 symbols are based on a carrier having a minimum subcarrier spacing SCS among the carriers to which the indicated TCI state and the CORESETPoolIndex value are applied.

8. The BS according to claim 5, wherein: The second indicator indicates that the simultaneous reception is not enabled, and The one or more spatial filters are determined based on at least one of: the first TCI state; A TCI state for receiving a physical downlink control channel PDCCH carrying the DCI; and The TCI state for receiving the PDCCH of the CORESET having the lowest CORESET index among the CORESETs configured with the CORESETPoolIndex value in the most recent slot monitored in the search space.

9. A method performed by a user equipment UE, the method comprising: Receiving downlink control information DCI indicating a first transmission configuration indication TCI state in a first control resource set CORESET; as well as receiving in radio resource control (RRC) signaling (i) a first indicator configuring a CORESETPoolIndex value associated with the first CORESET and (ii) a second indicator; as well as identifying an association between the CORESETPoolIndex value and the first TCI state based on the first indicator; identifying, based on the second indicator, whether simultaneous reception is enabled before the indicated TCI state can be applied; as well as Based on the identification, one or more spatial filters are determined for receiving a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied, wherein the PDSCH is associated with the CORESETPoolIndex value.

10. The method according to claim 9, wherein: Identifying an association between the CORESETPoolIndex value and the first TCI state further includes: In a case where the CORESETPoolIndex value is 0, identifying that the first TCI state is associated with a CORESETPoolIndex value of 0; and When the CORESETPoolIndex value is 1, it is identified that the first TCI state is associated with the CORESETPoolIndex value 1.

11. The method according to claim 9, wherein: The indicated TCI state is applicable starting from the following time slots: The first time slot of at least timeDurationForQCL symbols after the last symbol of the physical downlink control channel PDCCH carrying the DCI indicating the TCI status; The first time slot of at least BeamAppTime_r17 symbols after the last symbol of a physical uplink control channel PUCCH with hybrid automatic repeat request HARQ-acknowledgement ACK information, the HARQ-ACK information corresponding to a PDSCH scheduled by a DCI indicating the TCI state; or the first time slot of at least BeamAppTime_r17 symbols after the last symbol of the PUCCH with HARQ-ACK information corresponding to the DCI indicating the TCI state, and The method also includes: determining the first time slot and the BeamAppTime_r17 symbols based on a carrier having a minimum subcarrier spacing SCS among the carriers to which the indicated TCI state and the CORESETPoolIndex value are applied.

12. The method according to claim 9, wherein: The second indicator indicates that the simultaneous reception is not enabled, and Determining the one or more spatial filters further comprises determining the one or more spatial filters based on at least one of: the first TCI state; A TCI state for receiving a physical downlink control channel PDCCH carrying the DCI; and The TCI state for receiving the PDCCH of the CORESET having the lowest CORESET index among the CORESETs configured with the CORESETPoolIndex value in the most recent slot monitored in the search space.

13. A method performed by a base station BS, the method comprising: Transmitting downlink control information DCI indicating a first transmission configuration indication TCI state in a first control resource set CORESET; as well as transmitting in radio resource control (RRC) signaling (i) a first indicator configuring a CORESETPoolIndex value associated with the first CORESET and (ii) a second indicator, The first indicator indicates a first indication, and the first indication is used to indicate the association between the CORESETPoolIndex value and the first TCI state. The second indicator indicates a second indication, and the second indication is used to indicate whether simultaneous reception is enabled before the indicated TCI state can be applied, wherein one or more spatial filters associated with a physical downlink shared channel (PDSCH) before the indicated TCI state can be applied are indicated based on the first indication and the second indication, and The PDSCH is associated with the CORESETPoolIndex value.

14. The method according to claim 13, further comprising: transmitting, in a second CORESET, a DCI indicating a second TCI state; wherein, when the CORESETPoolIndex value corresponding to the second CORESET is 0, the second TCI state is associated with the CORESETPoolIndex value 0; and In which, when the CORESETPoolIndex value corresponding to the second CORESET is 1, the second TCI state is associated with the CORESETPoolIndex value 1.

15. The method according to claim 13, further comprising: transmitting, in a second CORESET, a DCI indicating a second TCI state; The RRC signaling includes a third indicator configured with a first physical cell identifier PCI for the first CORESET and a second PCI for the second CORESET; and The third indicator indicates a first association between the first DCI and the first TCI state and a second association between the second PCI and the second TCI state.

Images