Computer readable medium, user equipment, and method for wireless communication

Abstract

The present application relates to devices and components, including apparatus, systems and methods for resolving spatial conflicts between physical downlink control channel beams and default physical downlink shared channel beams in wireless communication systems.

Description

Background Art

[0001] The 3rd Generation Partnership Project (3GPP) network specifies that multiple transmit and receive points (TRPs) may send downlink transmissions to a user equipment (UE). The UE may have multiple antenna panels configured to receive these downlink transmissions. If the UE does not have sufficient time to process control information before receiving a downlink transmission, the UE may not obtain sufficient information about how to configure the antenna panels for proper reception of the downlink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 A network environment according to some embodiments is shown.

[0003] Figure 2 Downlink transmission according to some embodiments is shown.

[0004] Figure 3 Downlink transmission according to some embodiments is shown.

[0005] Figure 4 Downlink transmission according to some embodiments is shown.

[0006] Figure 5 Downlink transmission according to some embodiments is shown.

[0007] Figure 6 Downlink transmission according to some embodiments is shown.

[0008] Figure 7 An operational flow / algorithm structure according to some embodiments is shown.

[0009] Figure 8 An operational flow / algorithm structure according to some embodiments is shown.

[0010] Fig. 9 An operational flow / algorithm structure according to some embodiments is shown.

[0011] Fig.10 A receiving component of a user equipment is shown according to some embodiments.

[0012] Fig.11 User equipment according to some embodiments is shown.

[0013] Fig.12 A gNB according to some embodiments is shown. DETAILED DESCRIPTION

[0014] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), or a digital signal processor (DSP). In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0017] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0018] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0019] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0021] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0023] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0027] Figure 1 A network environment 100 is shown according to some embodiments. The network environment 100 may include a UE 104 and a gNB 108. The gNB 108 may be a base station that provides a wireless access cell, such as a 3GPP New Radio (NR) cell through which the UE 104 can communicate with the gNB 108. The UE 104 and the gNB 108 may communicate over an air interface compatible with 3GPP technical specifications, such as those defining fifth generation (5G) NR system standards.

[0028] The gNB 108 may include a gNB controller 112 coupled to one or more TRPs (e.g., TRP 116 and TRP 120). In general, the gNB controller 112 may perform most operations of the communication protocol stack, including scheduling, while the TRPs 116 and 120 act as distributed antennas. In some embodiments, the TRPs 116 and 120 may perform some low-level operations of the communication protocol stack (e.g., emulating physical (PHY) layer operations).

[0029] gNB 108 may use TRPs 116 and 122 to geographically separate points where signals may be transmitted to or received from UE 104. This may increase flexibility using multiple-input, multiple-output, and beamforming enhancements for communicating with UE 104. TRPs 116 and 120 may be used to transmit the same or different downlink transmissions to UE 104. In some embodiments, the distributed transmit / receive capabilities provided by TRPs 116 and 120 may be used for coordinated multi-point or carrier aggregation systems.

[0030] The gNB 108 may transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and mapping transport channels onto physical channels. Logical channels may transmit data between the radio link control (RLC) layer and the medium access control (MAC) layer; transport channels may transmit data between the MAC and PHY layers; and physical channels may transmit information across the air interface.

[0031] Physical channels may include a physical broadcast channel (PBCH); a physical downlink control channel (PDCCH); and a physical downlink shared channel (PDSCH).

[0032] The PBCH may be used to broadcast a master information block (MIB) to provide information that facilitates access to NR cells. The MIB may include a system frame number, a cell barring flag, and information that may be used to receive a system information block 1 (SIB1). The MIB and SIB1 may be used to transmit minimum system information that provides a basic set of parameters that a UE 104 may use to initially access or obtain any other system information.

[0033] The PBCH may be transmitted in a synchronization signal (SS) / PBCH block along with a physical synchronization signal (PSS) and a secondary synchronization signal (SSS). The SS / PBCH block (SSB) may be used by the UE 104 during a cell search procedure and for beam selection.

[0034] The PDSCH may be used to transmit end-user application data, Signaling Radio Bearer (SRB) messages, system information messages (in addition to, for example, the MIB), and paging messages.

[0035] The PDCCH may convey downlink control information (DCI), which is used by the scheduler of the gNB controller 112 to allocate both uplink and downlink resources. The DCI may also be used to provide uplink power control commands, configure the slot format, or indicate that preemption has occurred.

[0036] In some embodiments, UE 104 may include multiple antenna elements in one or more antenna panels that allow for receive or transmit beamforming. Figure 1A UE 104 with two antenna panels (Panel 1 and Panel 2) is shown. In the downlink direction, the UE 104 can select a beam to receive downlink transmissions based on the SSB and the channel state information-reference signal (CSI-RS). When in a radio resource control (RRC) idle mode, the UE 104 can perform initial acquisition using the SSB and the physical random access channel (PRACH) preamble during a random access procedure to establish uplink and downlink beam pairs. These initial beam pairs can correspond to relatively wide beams. The UE 104 can then enter an RRC connected mode and initiate a beam refinement process to select a beam that is more directional and has a higher gain. The beam refinement process can be based on the CSI-RS.

[0037] Although beamforming may be performed in both frequency range (FR) 1 (410 MHz to 7125 MHz) and FR2 (24250 MHz to 52600 MHz), receive beamforming at the UE 104 may be more applicable in FR2 because the UE 104 can have more antennas due to the shorter wavelength.

[0038] Transmissions using different antenna ports may experience different radio channels. However, in some cases, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler shift, Doppler spread, average delay, delay spread or spatial reception parameters (e.g., characteristics associated with the angle of arrival of the downlink received signal at the UE). Antenna ports that share one or more of these large-scale radio channel characteristics may be considered to be quasi-co-located (QCL) with each other. 3GPP has specified four types of QCL to indicate which specific channel characteristics are shared. In QCL Type A, antenna ports share Doppler shift, Doppler spread, average delay and delay spread. In QCL Type B, antenna ports share Doppler shift, and Doppler spread is shared. In QCL Type C, antenna ports share Doppler shift and average delay. In QCL Type D, antenna ports share spatial receiver parameters.

[0039] The gNB 108 may provide transmission configuration indicator (TCI) status information to the UE 104 to indicate the QCL relationship between antenna ports used for reference signals (e.g., SSB or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). The gNB 108 may use a combination of RRC signaling, MAC control element signaling, and DCI to inform the UE 104 of these QCL relationships.

[0040] Initially, the gNB 108 may configure multiple TCI states for the UE 104 via RRC signaling. In some embodiments, up to 128 TCI states may be configured for the PDSCH via, for example, the PDSCH-config information element, and up to 64 TCI states may be configured for the PDCCH via, for example, the PDCCH-config information element. Each TCI state may include a cell identifier, a bandwidth part identifier, an indication of the associated SS / PBCH block or CSI-RS, and an indication of the QCL type. After the initial configuration, the TCI state may be set to inactive.

[0041] The gNB 108 may then transmit an activation command, for example, via a MAC control element. The activation command may activate up to eight combinations of one or two TCI states, corresponding to eight code points of the TCI field in the DCI. One or more specific TCI states may then be dynamically selected and signaled using the TCI field in the DCI to indicate which of the active TCI states are applicable for PDSCH resource allocation.

[0042] The gNB 108 may transmit the PDCCH using resource elements belonging to a control resource set (CORESET). The search space configuration may refer to a specific CORESET to define the search space, e.g., a specific set of resource blocks and symbols that the UE 104 attempts to decode the PDCCH.

[0043] The gNB 108 may configure up to three CORESETs for the active downlink bandwidth portion of the serving cell. A CORESET may be configured by a ControlResourceSet information element, which defines the frequency domain resources to indicate the resource blocks allocated to the CORESET, defines the duration (which may be 1, 2, or 3 orthogonal frequency division multiplexing (OFDM) symbols) to indicate the number of symbols allocated to the CORESET, and defines the QCL information to support successful reception of the PDCCH.

[0044] The QCL information in the ControlResourceSet information element may be provided by listing the identities of the TCI states. The TCI states identified in the ControlResourceSet information element may be a subset of the TCI states defined in the PDSCH-config in the active downlink bandwidth portion to which the CORESET belongs. If the ControlResourceSet information element provides only a single TCI state, the UE 104 may assume a QCL relationship between the PDCCH and the reference signals specified by that TCI state. If multiple TCI states are listed, the UE 104 may rely on an activation command as described above to identify the TCI state to apply.

[0045] In some embodiments, the gNB 108 may configure one or more CORESET pools to facilitate the use of multiple PDCCHs that may potentially schedule PDSCHs that fully or partially overlap in time. To configure a CORESET pool, the gNB 108 may include a CORESET pool index in the ControlResourceSet IE to associate a CORESET with a corresponding CORESET pool. In some embodiments, the gNB 108 may configure up to two different CORESET pools.

[0046] gNB 108 may operate in single DCI mode or multi-DCI mode. In single DCI mode, one TRP may transmit DCI to schedule PDSCH transmissions from multiple TRPs. For example, TRP 116 may transmit DCI 1 to schedule both PDSCH 1 from TRP 116 and PDSCH 2 from TRP 120. In multi-DCI mode, each TRP may transmit its own DCI to schedule its own PDSCH transmissions. For example, TRP 116 may transmit DCI 1 to schedule PDSCH 1 from TRP 116, and TRP 120 may transmit DCI 2 to schedule PDSCH 2 from TRP 120.

[0047] In various implementations, gNB 108 may use different multiplexing techniques to schedule PDSCH 1 and PDSCH 2. In a first example, frequency division multiplexing (FDM) may be used by providing different resource block group (RBG) sets for different PDSCH transmissions. In a second example, space division multiplexing (SDM) may be used by providing different DMRS code division multiplexing (CDM) sets for different PDSCH transmissions. In a third example, time division multiplexing (TDM) may be used by transmitting PDSCH transmissions in different OFDM symbols.

[0048] For multi-TRP operation using a single DCI mode, in some scenarios, the UE 104 may need to select a default PDSCH TCI state from the activated combination. For example, if the UE 104 supports receive beamforming and the scheduling offset between the PDCCH and PDSCH is below a threshold, the UE 104 may not have sufficient time to receive and process the DCI to determine the selected TCI state. Therefore, the UE 104 (and therefore the gNB 108) may need to continue operating based on the default assumption of the TCI state of the PDSCH.

[0049] In some embodiments, when the scheduling offset is below a threshold, gNB 108 may enable UE 104 to receive PDSCH using two default beams. The scheduling offset may be the time between the DCI and the scheduled PDSCH. In some embodiments, the scheduling offset may be determined based on the last symbol of the scheduled DCI and the first symbol of the scheduled PDSCH. The threshold may be based on the capabilities of UE 104 and, in some embodiments, may be reported from UE 104 to gNB 108 in a UE capability report.

[0050] In some embodiments, the gNB 108 may enable two default beams by providing appropriate RRC parameters in a serving cell configuration information element that is used to configure (e.g., add or modify) a serving cell for the UE 104. For single DCI mode, the RRC parameter may be the enableTwoDefaultTCIStates RRC parameter. If enabled, the default PDSCH beam may be based on the lowest TCI code point among the active code points that include two TCI states. For multi-DCI mode, the RRC parameter may be the enableDefaultTCIStatePerCoresetPoolIndex RRC parameter. If enabled, the default PDSCH beam may be based on the CORESET with the lowest identifier in the most recent timeslot among the CORESETs in each CORESET pool.

[0051] In some cases, enabling multiple default beams to receive PDSCH transmissions may result in spatial collisions between the PDSCH transmissions and other PDCCH transmissions in the same or different serving cells. Therefore, various embodiments describe operations that can be used to handle spatial collisions between PDCCH and default PDSCH beams in multiple DCI modes and single DCI modes. Collision handling can be described with reference to FDM, TDM, and CDM schemes.

[0052] Figure 2 A downlink transmission 200 is shown according to some embodiments. The downlink transmission 200 may be located in a first serving cell on a first component carrier (CC 1) and in a second serving cell on a second component carrier (CC 2). The component carriers may be part of a carrier aggregation implementation where one of the serving cells is a primary serving cell and the other serving cell is a secondary serving cell. In other embodiments, the serving cells may be different primary serving cells. The serving cells may be located in the same frequency band or in the same frequency band group.

[0053] Serving cell 1 may include PDCCH 204 scheduling PDSCH 212 and PDCCH 208 scheduling PDSCH 216. PDCCH 204 and PDSCH 212 may be transmitted from TRP 116, while PDCCH 208 and PDSCH 216 may be transmitted from TRP 120. Thus, this may represent multi-DCI mode operation.

[0054] The scheduling offset between PDCCH 204 / PDSCH 212 and PDCCH 208 / PDSCH 216 may be less than a predetermined threshold 220, which may be based on UE capabilities. Thus, UE 104 may determine a plurality of default beams to receive PDSCH transmissions.

[0055] PDCCH 204 may be transmitted on resource elements of CORESET 1. CORESET 1 may be configured with a pool index equal to 0 and a TCI state equal to 3. Parameters of CORESET 1 may indicate that antenna panel 1 should be configured with a third receive beam. The beam indicated or associated with a CORESET may be determined by beam management operations (e.g., initial acquisition and refinement as described above) based on reference signals and QCL / TCI information defined by the corresponding CORESET. As used herein, receive beams may be numbered 1 to 4 starting from the bottom beam. Use of this numbering scheme facilitates the present description but is generally arbitrary. Other beam numbering schemes and numbers of beams may be used in various embodiments.

[0056] PDCCH 208 may be transmitted on resource elements of CORESET 3. CORESET 3 may be configured with a pool index equal to 1 and a TCI state equal to 5. Parameters of CORESET 3 may indicate that antenna panel 2 should be configured with a first receive beam.

[0057] A third PDCCH, PDCCH 224, may be transmitted in the second serving cell. PDCCH 224 may be transmitted on resource elements of CORESET 2. CORESET 2 may be configured with a pool index equal to 0 and a TCI state equal to 4. Parameters of CORESET 2 may indicate that the first antenna panel should be configured with a fourth receive beam.

[0058] UE 104 may initially configure its first antenna panel and second antenna panel to have a default PDSCH beam based on CORESET 1 and 3. Thus, at a first time period, e.g., t=0, UE 104 may configure antenna panel 1 to have a third receive beam (based on CORESET 1) and antenna panel 2 to have a first receive beam (based on CORESET 3) to receive PDSCH transmissions.

[0059] In some embodiments, for each CORESET pool, if there is an existing CORESET in the same serving cell or another serving cell, the default PDSCH beam for the CORESET pool may be based on the existing CORESET. Figure 2 , when PDCCH 224 is received, it overlaps with a PDSCH transmission, and therefore there is an existing CORESET for CORESET pool 0. UE 104 may then set a default PDSCH beam based on that existing CORESET (i.e., CORESET 2). Thus, at a second time period, e.g., t=1, UE 104 may configure antenna panel 1 to have a fourth beam (based on CORESET 4). This may configure UE 104 to correctly receive PDCCH 224.

[0060] In some embodiments, the first time period may correspond to a first time slot, in which UE 104 may receive PDSCH 212, and the second time period may correspond to a second time slot, in which UE 104 may receive PDSCH 216. However, in other embodiments, the first time period and the second time period may correspond to time periods greater than or less than one time slot.

[0061] In some embodiments, UE 104 may still be able to receive PDSCH in the second time period using two beams, one beam per CORESET pool. In the embodiment shown, the second beam may be the first beam for antenna panel 2 based on CORESET 3.

[0062] In some implementations, if the existing CORESET is from another serving cell that is not configured in multiple DCI mode, or the existing CORESET does not have a configured CORESET pool index, the UE 104 may continue to operate based on one of two options.

[0063] In a first option, UE 104 may assume that the CORESET pool index is equal to 0 or 1. If UE 104 assumes that the CORESET pool index is equal to 0, then UE 104 may Figure 2 If UE 104 assumes that the CORESET pool index is equal to 1, UE 104 may utilize beam number 4 for panel 2. For example, the default beam configuration from CORESET 2 may replace the default beam configuration from CORESET 3.

[0064] In a second option, the UE 104 may configure a default PDSCH beam based on one TCI from an existing CORESET. For example, in a second time period, the UE 104 may configure antenna panel 1 to have a fourth beam based on CORESET 2 and deactivate antenna panel 2.

[0065] In some embodiments, UE 104 may detect multiple existing CORESETs in the same serving cell or in a common frequency band or frequency band group. In these embodiments, UE 104 may determine the priority of the existing CORESETs. The default PDSCH beam may then be set based on the CORESET with the highest relative priority.

[0066] In some embodiments, the UE 104 may determine the CORESET with the highest relative priority for each CORESET pool and select that CORESET to establish the default PDSCH beam. For example, consider that the UE 104 determines that there are two CORESETs for pool 0 at a given time (e.g., CORESET 1 and CORESET 2, with CORESET 1 being the higher priority CORESET), and there is one CORESET for pool 1 at a given time (e.g., CORESET 3). In this case, the UE 104 may select a first default PDSCH beam based on CORESET 1 of pool 0, and a second default PDSCH beam based on CORESET 3 of pool 1.

[0067] The CORESET priority of each CORESET pool may be determined based on the search space associated with the CORESET. Parameters of the search space that may be used to establish the priority may include, but are not limited to, search space type (common search space (CSS) or UE-specific search space (USS)), periodicity, size, CORESET ID, etc. If two CORESETs are associated with a common search space, the priority may be based on the subtype, such as whether the search space is type 0, type 0A, type 1, type 2, or type 3. Although not limited to this, in some embodiments, CSS may take precedence over USS; CORESETs corresponding to CSS sets with lower indices may take precedence over CORESETs corresponding to CSS sets with higher indices; and CORESETs corresponding to USS sets with lower indices may take precedence over CORESETs corresponding to USS sets with higher indices, and so on.

[0068] Figure 3 A downlink transmission 300 is shown according to some embodiments. The downlink transmission 300 may be based on a FDM or SDM transmission scheme.

[0069] The downlink transmission 300 may be located in a first serving cell on a first component carrier (CC 1) and in a second serving cell on a second component carrier (CC 2). The component carriers may be part of a carrier aggregation implementation where one of the serving cells is a primary serving cell and the other serving cell is a secondary serving cell. In other implementations, the serving cells may be different primary serving cells. The serving cells may be located in the same frequency band or in the same frequency band group.

[0070] Serving cell 1 may include PDCCH 304 that schedules PDSCH 308 and PDSCH 312. PDCCH 304 and PDSCH 308 may be transmitted from TRP 116, while PDSCH 312 may be transmitted from TRP 120. Thus, this may represent a single DCI mode operation.

[0071] The scheduling offset between the PDCCH 304 and the PDSCH transmission may be less than a predetermined threshold 320, which may be based on UE capabilities. Accordingly, the UE 104 may determine a plurality of default beams to receive the PDSCH transmission.

[0072] UE 104 may select a default TCI that is equal to the TCI state in the lowest code point of the active TCI state that includes the two TCI state combinations. For this description, the two TCI states are considered to be TCI 1 and TCI 2.

[0073] If there are no other CORESETs, then UE 104 may configure its antenna panel based on the default TCI. For example, UE 104 may configure antenna panel 1 to have a first receive beam (e.g., based on TCI 1) during a first time period, and may configure antenna panel 2 to have a first receive beam (e.g., based on TCI 2).

[0074] In some embodiments, for the FDM / SDM scheme, if there is an existing CORESET in the same serving cell or another serving cell, the default PDSCH beam may be based on the beam of the existing CORESET. In some embodiments, the UE 104 may receive the PDSCH using the beam based on the existing CORESET and the first beam or the second beam based on the default TCI. Therefore, referring to Figure 3 , when PDCCH 316 is received, there is an existing CORESET, for example, CORESET 2. Therefore, UE 104 may configure antenna panel 1 to have a fourth beam (based on CORESET 2) during a second time period (eg, t=1).

[0075] Figure 4A downlink transmission 400 is shown according to some embodiments. The downlink transmission 400 may be based on a FDM or SDM transmission scheme.

[0076] Downlink transmission 400 may be similar to those described above with reference to downlink transmission 300. However, instead of utilizing the existing CORESET beam and the first / second default TCI beams to receive PDSCH as described above, UE 104 may utilize only the CORESET beam to receive PDSCH.

[0077] Therefore, when PDCCH 416 is received and there is an existing CORESET (e.g., CORESET 2), UE 104 may configure antenna panel 1 to have a fourth beam (based on CORESET 2) during a second time period (e.g., t=1). The second antenna panel may be deactivated and therefore not used for reception of the corresponding PDSCH (e.g., PDSCH 412).

[0078] refer to Figure 3 and Figure 4 The single DCI mode operation described with respect to the FDM / SDM scheme may be considered as alternatives to each other. In some embodiments, the gNB 108 may configure the UE 104 to use one of the two options. The control signaling may be higher layer signaling, such as, but not limited to, RRC signaling or MAC signaling (e.g., MAC control element). In some embodiments, the UE 104 may send an indication in a UE capability report indicating whether it supports one or both of these options. If the UE 104 supports both options, the UE 104 may select one of these options based on control signaling or other predefined configuration information from the gNB 108.

[0079] In some embodiments, similar to the above reference Figure 2As described above, multiple CORESETs may exist in the same serving cell or in serving cells in a common frequency band or frequency band group at a given time. For single DCI mode, the UE may also determine the priority of the multiple CORESETs and select the CORESET with the highest relative priority for the default PDSCH beam. In some embodiments, a priority may be determined for each CORESET pool. If there are existing CORESETs from two CORESET pools, the UE 104 may select two beams to receive the PDSCH. In some embodiments, the UE 104 may determine the CORESET priority across the CORESET pools. For example, if CORESET pool 1 includes a high priority CORESET and a medium priority CORESET, and CORESET pool 2 includes a low priority CORESET, the UE 104 may select beams corresponding to the two CORESETs in CORESET pool 1 for receiving the PDSCH.

[0080] The relative priority of CORESET can be based on the above reference Figure 2 The associated search space.

[0081] Figure 5 A downlink transmission 500 according to some embodiments is shown. The downlink transmission 500 may be based on a TDM transmission scheme.

[0082] Similar to downlink transmissions 300 and 400, downlink transmission 500 may correspond to single DCI mode operation. Downlink transmission 500 includes PDCCH 504 scheduling a first PDSCH transmission opportunity 508 for PDSCH transmission from TRP 116 and scheduling a second PDSCH transmission opportunity 512 for PDSCH transmission from TRP 120.

[0083] like Figure 5 As shown, to receive PDCCH 504, the UE may configure panel 1 to have beam 3 based on CORESET 1. If no other CORESET exists after receiving PDCCH 504, the UE 104 may configure panel 1 to have a first default PDSCH beam based on one of the default TCIs (e.g., TCI 1) in a first time period (t=0). The first time period may be a time slot in which PDSCH transmission opportunity 1 508 occurs.

[0084] In some embodiments, for a TDM scheme using a single DCI mode operation, if there is an existing CORESET in the same serving cell or another serving cell, the UE 104 may set the default PDSCH beam for the current transmission opportunity based on the beam of the existing CORESET. Figure 5, when PDCCH 516 is received, there is an existing CORESET, e.g., CORESET 2. Therefore, UE 104 may configure antenna panel 1 to have a fourth beam (based on CORESET 2) during a second time period (e.g., t=1). Therefore, UE 104 may apply a default PDSCH beam to transmission opportunities that do not conflict with other CORESETs based on the default TCI, and may apply an existing CORESET beam to transmission opportunities that conflict with other CORESETs.

[0085] In an embodiment where multiple CORESETs exist at a particular time, the UE 104 may determine which of the multiple CORESETs has the highest priority and apply the beam corresponding to that CORESET to the corresponding transmission opportunity. This may be done similarly as described elsewhere herein.

[0086] Figure 6 A downlink transmission 600 according to some embodiments is shown. The downlink transmission 600 may be based on a TDM transmission scheme.

[0087] Downlink transmission 600 may be similar to those described above with reference to downlink transmission 500. However, in this embodiment, instead of applying a default PDSCH beam to transmission opportunities that do not conflict with a CORESET based on a default TCI, the UE 104 may apply a CORESET beam to all transmission opportunities. Figure 6 Because PDCCH 616 conflicts with PDSCH transmission opportunity 2 612 , UE 104 may set the default PDSCH beam to the fourth beam on panel 1 (based on CORESET 2 ) for all transmission opportunities (eg, PDSCH transmission opportunity 1 608 and PDSCH transmission opportunity 2 612 ).

[0088] refer to Figure 5 and Figure 6 The single DCI mode operation described with respect to the FDM scheme may be considered alternatives to each other. In some embodiments, the gNB 108 may configure the UE 104 to use one of the two options. For example, if both options are available, the gNB 108 may determine that one option is preferable over the other in certain scenarios. For example, when the TDM scheme is an intra-slot TDM scheme when two PDSCH transmission opportunities are located in the same time slot, the gNB 108 may determine that Figure 6 Alternatively, when the TDM scheme is an inter-slot TDM scheme where two PDSCH transmission opportunities are located in different time slots, the gNB 108 may determine Figure 5 The options embodied may be advantageous.

[0089] The control signaling may be higher layer signaling, such as, but not limited to, RRC signaling or all MAC signaling (e.g., MAC control elements). In some embodiments, the UE 104 may send an indication in a UE capability report indicating whether it supports one or both of these options. If the UE 104 supports both options, the UE 104 may select one of these options based on control signaling or other predefined configuration information from the gNB 108.

[0090] In some embodiments, the UE 104 may provide measurement reports for different measurement process identifiers, each measurement process identifier being associated with a specific reference signal (e.g., SSB / CSI-RS). It may be assumed that reference signals with the same measurement process ID are received by the same antenna panel. It may be assumed that reference signals with different measurement process IDs are received by different panels and may be received simultaneously. If there is an existing CORESET, the UE 104 may measure the reference signal and provide a corresponding measurement report based on its TCI instead of the measurement signal associated with the default PDSCH TCI with the same measurement process ID. If there are multiple existing CORESETs with TCI from the same measurement process ID, the UE 104 may select one CORESET with the highest priority instead of the default PDSCH TCI with the same measurement process ID as the basis for the measurement result report. The priorities of multiple existing CORESETs may be based on the search space associated with the corresponding CORESET.

[0091] If a reference signal has not been reported or the report is expired, the measurement report for this measurement process ID may be based on a default value, such as 0.

[0092] Figure 7 An operational flow / algorithm structure 700 according to some embodiments may be included. The operational flow / algorithm structure 700 may be performed or implemented by a UE (such as UE 104 or 1100) or a component thereof (eg, baseband processor 1104A).

[0093] The operation flow / algorithm structure 700 may include: at 704, receiving DCI from a TRP to schedule a PDSCH transmission. In some embodiments, the DCI may include DCI from a first / second TRP that schedules a first / second PDSCH transmission, respectively. In other embodiments, the DCI may include DCI from a first TRP that schedules both a first PDSCH transmission and a second PDSCH transmission. The first PDSCH transmission and the second PDSCH transmission may be scheduled using an FDM approach, an SDM approach, or a TDM approach.

[0094] The DCI may be included in a corresponding PDCCH transmission, each PDCCH transmission being transmitted on a resource element associated with a corresponding CORESET. The CORESET may include a TCI state that the UE may use to determine QCL information in order to facilitate making a determination of a beam for receiving the corresponding PDCCH transmission. The UE may configure the first antenna panel and the second antenna panel to receive the PDCCH transmission based on the beam determined by the corresponding CORESET.

[0095] The operation flow / algorithm structure 700 also includes: at 708, configuring the first antenna panel and the second antenna panel to receive the PDSCH transmission using the first default beam and the second default beam. The first default beam and the second default beam for receiving the PDSCH transmission may default to the same beam as the beam for receiving the PDCCH transmission, that is, the beam based on the CORESET associated with the PDCCH that transmits the scheduling DCI.

[0096] The operation flow / algorithm structure 700 may also include, at 712, detecting a PDCCH overlapping with the PDSCH transmission. The UE may determine that a CORESET exists during reception of the PDSCH transmission by detecting a PDCCH associated with an existing CORESET that overlaps with the PDSCH transmission. The overlapping PDCCH may be in the same serving cell as the PDSCH transmission, or may be in another serving cell in a common frequency band or frequency band group as the serving cell of the PDSCH transmission.

[0097] The operational flow / algorithm structure 700 may also include, at 716, reconfiguring the antenna panel to have a third default beam. The third default beam may be based on an existing CORESET. In some embodiments, one of the antenna panels may be reconfigured with the third default beam while the other antenna panel remains configured with the first or second default beam. In other embodiments, only the antenna panel reconfigured with the third default beam may be activated.

[0098] Figure 8 An operational flow / algorithm structure 800 according to some embodiments may be included. The operational flow / algorithm structure 800 may be performed or implemented by a UE (such as UE 104 or 1100) or a component thereof (eg, baseband processor 1104A).

[0099] The operational flow / algorithm structure 800 may include, at 804, receiving a DCI to schedule a PDSCH transmission.

[0100] In some embodiments, the DCI may include one DCI from the first TRP to schedule two PDSCH transmissions from multiple TRPs. Therefore, this embodiment may be a single DCI mode embodiment.

[0101] The operational flow / algorithm structure 800 may also include, at 808, configuring the antenna panel to use a first default beam based on a default TCI state.

[0102] In a single DCI mode implementation, the UE may be configured with two default TCI states. For example, the base station may provide an enableTwoDefaultTCIStates RRC parameter that enables two default TCI states. The UE may determine which two TCI states are enabled as defaults based on the lowest TCI code point indicating the two TCI states. The first default beam is set based on one of the two TCI states.

[0103] The operational flow / algorithm structure 800 may also include, at 812, identifying overlapping PDCCH transmissions that will use resource elements of the CORESET. The overlapping PDCCH transmissions may cause the CORESET to exist during reception of the PDSCH transmission. Thus, according to some embodiments, the UE may reconfigure the antenna panel to use a second default beam based on the existing CORESET as shown at 816 of the operational flow / algorithm structure 800.

[0104] In some embodiments, the UE may configure the second antenna panel to have a default beam based on a second default TCI state of the two default TCI states. In some embodiments, the second antenna panel may be configured with a default beam based on the second default TCI state regardless of whether the first antenna panel is configured with the first default beam or the second default beam. In other embodiments, the second antenna panel may be deactivated when the first antenna panel is reconfigured with the second default beam.

[0105] Fig. 9 An operational flow / algorithm structure 900 according to some embodiments may be included. In some embodiments, the operational flow / algorithm structure 900 may be performed or implemented by a gNB (e.g., gNB 108 or gNB 1200) or a component thereof (e.g., baseband processor 1204A).

[0106] The operational flow / algorithm structure 900 may include receiving a UE capability report at 904. The capability report may provide an indication of whether the UE is capable of using two default beams.

[0107] The operation flow / algorithm structure 900 may also include: at 908, generating and transmitting configuration information to enable two default beams, and providing a control indication indicating whether to use one beam or two beams in the presence of overlapping PDCCH transmissions. For example, the control indication may indicate whether, in the presence of an existing CORESET, the UE should: (1) receive PDSCH using the CORESET beam and the first / second default TCI beam; or (2) receive PDSCH using only the CORESET beam. For another example, the control indication may indicate whether, in the presence of an existing CORESET, the UE should: (1) apply the default PDSCH beam to transmission opportunities that do not conflict with the existing CORESET (e.g., based on the default TCI state) and apply the existing CORESET beam to transmission opportunities that conflict with the existing CORESET; or (2) apply the existing CORESET beam to all transmission opportunities.

[0108] In various implementations, the configuration information may be transmitted via one or more control signals. The control signals may include, for example, RRC signaling, MAC signaling, or DCI.

[0109] Fig.10 A receiving component 1000 of a UE 104 according to some embodiments is shown. The receiving component 1000 may include a first antenna panel, panel 1 1004, and a second antenna panel, panel 2 1008. Each antenna panel may include a plurality of antenna elements.

[0110] The antenna panels may be coupled to respective analog beamforming (BF) components. For example, panel 1 1004 may be coupled to analog BF component 1012 and panel 2 1008 may be coupled to analog BF component 1016.

[0111] The analog BF components may be coupled to one or more radio frequency (RF) chains. For example, the analog BF components 1012 may be coupled to one or more RF chains 1020, and the analog BF components 1016 may be coupled to one or more RF chains 1024. The RF chains may amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to the digital BF components 1028. The digital BF components 1028 may provide the baseband (BB signal) for further BB processing.

[0112] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights to analog / digital BF components to provide receive beams at corresponding antenna panels. These BF weights may be determined by the control circuitry based on received reference signals and corresponding QCL / TCI information as described herein. In some embodiments, the BF weights may be phase shift values ​​provided to the phase shifters of the analog BF components 1012 or complex weights provided to the digital BF components 1028. In some embodiments, the BF components and antenna panels may operate together to provide a dynamic phased array capable of steering a beam in a desired direction.

[0113] In various embodiments, beamforming may include analog beamforming, pure digital beamforming, or hybrid analog digital beamforming.Digital beamforming may utilize separate RF chains corresponding to antenna elements, respectively.

[0114] Fig.11 FIG. 1 shows a UE 1100 according to some embodiments. The UE 1100 may be similar to Figure 1 UE 104, and can basically be used with Figure 1 UE 104 is interchanged.

[0115] UE 1100 may be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device; a loose IoT device. In some embodiments, the UE may be a RedCap UE or an NR-Light UE.

[0116] UE 1100 may include a processor 1104, RF interface circuitry 1108, memory / storage 1112, a user interface 1116, a sensor 1120, a driver circuit 1122, a power management integrated circuit "PMIC" 1124, antenna structures 1126, and a battery 1128. The components of UE 1100 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.11 The block diagram of UE 1100 is intended to show a high-level view of certain of the components of UE 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0117] Components of UE 1100 may be coupled to various other components via one or more interconnects 1132, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0118] The processor 1104 may include processor circuits such as a baseband processor circuit "BB" 1104A, a central processor unit circuit "CPU" 1104B, and a graphics processor unit circuit "GPU" 1104C. The processor 1104 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1112) to cause the UE 1100 to perform operations as described herein.

[0119] In some embodiments, the baseband processor circuit 1104A can access the communication protocol stack 1136 in the memory / storage device 1112 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1104A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1108.

[0120] The baseband processor circuit 1104A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM ("CP-OFDM") in the uplink or downlink, and discrete Fourier transform spread OFDM ("DFT-S-OFDM") in the uplink.

[0121] The memory / storage 1112 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1136) that may be executed by one or more processors in the processor 1104 to cause the UE 1100 to perform various operations described herein. The memory / storage 1112 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1100. In some embodiments, some of the memory / storage 1112 may be located on the processor 1104 itself (e.g., L1 cache and L2 cache), while other memory / storage 1112 is located outside the processor 1104 but is accessible via a memory interface. The memory / storage 1112 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0122] The RF interface circuit 1108 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1100 to communicate with other devices through a radio access network. The RF interface circuit 1108 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0123] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1126 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1104.

[0124] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1126.

[0125] In various embodiments, the RF interface circuit 1108 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0126] Antenna 1126 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1126 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multi-input, multi-output communications. Antenna 1126 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1126 may have one or more panels that are designed for a specific frequency band including a band in FR1 or FR2.

[0127] The user interface circuit 1116 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1100. The user interface 1116 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device for accepting input, including in particular one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1100.

[0128] Sensors 1120 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0129] The driver circuit 1122 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1100. The driver circuit 1122 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1100. For example, the driver circuit 1122 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1120 and controlling and allowing access to the sensor circuit 1120, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0130] A power management integrated circuit “PMIC” 1124 may manage power provided to various components of the UE 1100. Specifically, with respect to the processor 1104, the PMIC 1124 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0131] In some embodiments, the PMIC 1124 may control or otherwise be part of various power saving mechanisms of the UE 1100. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1100 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1100 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handovers, etc. are performed. The UE 1100 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers off again. The UE 1100 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will incur significant latency, and it is assumed that latency is acceptable.

[0132] The battery 1128 can power the UE 1100, but in some examples, the UE 1100 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1128 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 1128 can be a typical lead-acid car battery.

[0133] Fig.12 A gNB 1200 is shown according to some embodiments. The gNB node 1200 may be similar to the gNB 128 and may be substantially interchangeable therewith.

[0134] gNB 1200 may include a processor 1204, an RF interface circuit 1208, a core network (CN) interface circuit 1212, a memory / storage device circuit 1216, and an antenna structure 1226.

[0135] Components of gNB 1200 may be coupled to various other components via one or more interconnects 1228.

[0136] The processor 1204, RF interface circuit 1208, memory / storage circuit 1216 (including communication protocol stack 1210), antenna structure 1226 and interconnect 1228 may be similar to those of reference Fig.11 Like-named elements are shown and described.

[0137] The CN interface circuitry 1212 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network "5GC" compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the gNB 1200 via optical fiber or wireless backhaul. The CN interface circuitry 1212 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1212 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0138] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0139] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0140] Example

[0141] In the following sections, additional exemplary embodiments are provided.

[0142] Embodiment 1 includes a method of operating a UE, the method comprising: receiving multiple downlink control information (DCI) from multiple transmit and receive points (TRPs) to schedule multiple physical downlink shared channel (PDSCH) transmissions; based on a first control resource set (CORESET) and a second CORESET associated with the multiple DCIs, configuring a first antenna panel to use a first default beam and configuring a second antenna panel to use a second default beam to receive the multiple PDSCH transmissions; detecting a physical downlink control channel (PDCCH) associated with a third CORESET that overlaps with at least one of the PDSCH transmissions; and based on the third CORESET, reconfiguring the first antenna panel to have a third default beam to receive at least a portion of the multiple PDSCH transmissions.

[0143] Embodiment 2 includes the method according to embodiment 1 or some other embodiment herein, further comprising configuring the first antenna panel to use a first default beam based on the first CORESET, and the first CORESET and the third CORESET are associated with a first CORESET pool.

[0144] Embodiment 3 includes the method according to embodiment 1 or some other embodiment herein, further comprising receiving at least a portion of the multiple PDSCH transmissions using the second default beam and the third default beam after the first panel is reconfigured with the third default beam.

[0145] Embodiment 4 includes the method according to embodiment 1 or some other embodiment herein, further comprising receiving at least a portion of the multiple PDSCH transmissions using only the third default beam after the first panel is reconfigured with the third default beam.

[0146] Embodiment 5 includes the method of embodiment 1 or some other embodiment herein, wherein the multiple PDSCH transmissions are scheduled in a first component carrier and the PDCCH is detected in a second component carrier.

[0147] Embodiment 6 includes the method of embodiment 5 or some other embodiment herein, wherein the first component carrier and the second component carrier are in a common frequency band or frequency band group.

[0148] Embodiment 7 includes a method according to embodiment 1 or some other embodiment herein, wherein the PDCCH is a first PDCCH, the third CORESET is in a first CORESET pool, and the method further includes: detecting a second PDCCH associated with a fourth CORESET in the first CORESET pool, wherein the second PDCCH overlaps with the first PDCCH; determining that the first PDCCH has a higher priority than the second PDCCH; and reconfiguring the first antenna panel to have a third default beam based on the first PDCCH having a higher priority.

[0149] Embodiment 8 includes the method of embodiment 7 or some other embodiment herein, wherein determining that the first PDCCH has a higher priority includes comparing search spaces of the third CORESET and the fourth CORESET.

[0150] Embodiment 9 includes a method according to embodiment 8 or some other embodiment herein, wherein comparing the search spaces of the fourth CORESET and the third CORESET includes comparing search space parameters including search space type, search space subtype, periodicity, or identifier.

[0151] Embodiment 10 includes the method described in one or some other embodiment of the present invention, further comprising generating a report based on a synchronization signal block or a channel state information-reference signal, wherein the measurement process identifier is taken from the transmission configuration indicator (TCI) of the PDCCH.

[0152] Embodiment 11 includes a method of operating a UE, the method comprising: receiving downlink control information (DCI) from a first transmit and receive point (TRP) to schedule multiple physical downlink shared channel (PDSCH) transmissions from corresponding multiple TRPs; configuring an antenna panel to use a first default beam based on a default transmission configuration indicator (TCI) state; identifying overlapping physical downlink control channel (PDCCH) transmissions that will use resource elements of a control resource set (CORESET); and reconfiguring the antenna panel to use a second default beam based on the CORESET.

[0153] Embodiment 12 includes a method according to embodiment 11 or some other embodiment herein, wherein the antenna panel is a first antenna panel, the multiple PDSCH transmissions are frequency division multiplexing or space division multiplexing transmissions, the default TCI state is a first default TCI state, and the method further includes: configuring the second antenna panel to use a third default beam based on the second default TCI state.

[0154] Embodiment 13 includes a method according to embodiment 12 or some other embodiment herein, wherein after reconfiguring the first antenna panel, the method further includes: receiving at least a portion of the multiple PDSCH transmissions using the first antenna panel using a second default beam and the second antenna panel using a third default beam.

[0155] Embodiment 14 includes a method according to embodiment 12 or some other embodiment herein, wherein after reconfiguring the first antenna panel, the method includes utilizing the first antenna panel using a second default beam to receive at least a portion of the multiple PDSCH transmissions, and deactivating the second antenna panel.

[0156] Embodiment 15 includes a method according to embodiment 11 or some other embodiment herein, further comprising: receiving control signaling from a base station to indicate whether the UE will use one antenna panel or two antenna panels to receive PDSCH transmissions when there are one or more overlapping PDCCH transmissions.

[0157] Embodiment 16 includes the method according to embodiment 11 or some other embodiment herein, further comprising: transmitting a UE capability report to a base station, the UE capability report including an indication of whether the UE is capable of using one antenna panel or two antenna panels to receive a PDSCH transmission when there are one or more overlapping PDCCH transmissions.

[0158] Embodiment 17 includes a method according to embodiment 11 or some other embodiment herein, wherein the overlapping PDCCH transmission is a first overlapping PDCCH transmission, the CORESET is a first CORESET, and the method further includes: identifying a second overlapping PDCCH transmission that will use resource elements of a second CORESET; determining that the first CORESET has a higher priority than the second CORESET; and reconfiguring the antenna panel to use a second default beam based on the first CORESET having a higher priority.

[0159] Embodiment 18 includes the method of embodiment 17 or some other embodiment herein, wherein determining that the first CORESET has a higher priority includes comparing search spaces of the first CORESET and the second CORESET.

[0160] Embodiment 19 includes a method for operating a base station, the method comprising: receiving a user equipment (UE) capability report, the UE capability report including an indication of whether the UE is capable of using one or two default beams to receive a physical downlink shared channel (PDSCH) transmission when there are one or more overlapping physical downlink control channel (PDCCH) transmissions; based on the UE capability report, transmitting configuration information and a control indication to the UE, the configuration information being used to enable the use of two default beams to receive PDSCH transmissions, the control indication indicating whether the UE will use one or two default beams to receive PDSCH transmissions when there are one or more overlapping PDCCH transmissions.

[0161] Embodiment 20 includes the method according to embodiment 19 or some other embodiment herein, further comprising: transmitting one or more DCIs to schedule multiple PDSCH transmission opportunities, wherein the multiple PDSCH opportunities are scheduled with a scheduling offset less than a predetermined threshold, and the control indication is used to indicate that the UE will use a default beam to receive PDSCH transmissions in all of the multiple PDSCH transmission opportunities.

[0162] Example 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1 to 20, or any other method or process described herein.

[0163] Embodiment 22 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Embodiments 1 to 20 or any other method or process described herein.

[0164] Embodiment 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0165] Embodiment 24 may include methods, techniques or processes described or related to any one of Embodiments 1 to 20, or parts or components thereof.

[0166] Embodiment 25 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 20.

[0167] Embodiment 26 may include a signal as described or related to any one of Embodiments 1 to 20, or a portion or component thereof.

[0168] Embodiment 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of Embodiments 1 to 20, or otherwise described in the present disclosure.

[0169] Embodiment 28 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or as otherwise described in this disclosure.

[0170] Embodiment 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any of the above embodiments 1 to 64, or a portion or component thereof, or otherwise described in the present disclosure.

[0171] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0172] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0173] Embodiment 32 may include signals in a wireless network as shown and described herein.

[0174] Embodiment 33 may include a method of communicating in a wireless network as shown and described herein.

[0175] Embodiment 34 may include a system for providing wireless communications as shown and described herein.

[0176] Embodiment 35 may include an apparatus for providing wireless communications as shown and described herein.

[0177] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0178] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. One or more computer-readable storage media having instructions which, when executed by one or more processors, cause a user equipment (UE) to perform the following operations: Processing first downlink control information DCI to determine scheduling of first physical downlink shared channel PDSCH transmission; processing a second DCI to determine scheduling for a second PDSCH transmission; configuring a first antenna panel to receive the first PDSCH transmission using a first default beam based on a first control resource set CORESET associated with the first DCI, wherein the first CORESET is configured with a first CORESET pool index; configuring a second antenna panel to receive the second PDSCH transmission using a second default beam based on a second CORESET associated with the second DCI, wherein the second CORESET is configured with a second CORESET pool index; detecting a physical downlink control channel (PDCCH) associated with a third CORESET configured with the first CORESET pool index, wherein the PDCCH overlaps with the first PDSCH transmission; as well as Based on the first CORESET and the third CORESET being configured with the first CORESET pool index, the first antenna panel is reconfigured to have a third default beam to receive the PDCCH.

2. The one or more computer-readable media of claim 1, wherein the instructions, when executed, further cause the UE to: After the first antenna panel is reconfigured with the third default beam, at least a portion of the first PDSCH transmission or the second PDSCH transmission is received using the second default beam and the third default beam.

3. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the UE to: After the first antenna panel is reconfigured with the third default beam, at least a portion of the first PDSCH transmission or the second PDSCH transmission is received using only the third default beam. 4 . The one or more computer-readable media of claim 1 , wherein the first PDSCH transmission or the second PDSCH transmission is scheduled in a first component carrier and the PDCCH is detected in a second component carrier.

5. The one or more computer-readable media of claim 4, wherein the first component carrier and the second component carrier are in a common frequency band or frequency band group.

6. The one or more computer-readable media of claim 1 , wherein the PDCCH is a first PDCCH, the third CORESET is in a first CORESET pool, and the instructions when executed further cause the UE to: Detecting a second PDCCH associated with a fourth CORESET in the first CORESET pool, wherein the second PDCCH overlaps with the first PDCCH; Determining that the first PDCCH has a higher priority than the second PDCCH; as well as Based on the first PDCCH having the higher priority, the first antenna panel is reconfigured to have the third default beam.

7. The one or more computer-readable media of claim 6, wherein to determine that the first PDCCH has the higher priority, the UE is to: The search spaces of the third CORESET and the fourth CORESET are compared.

8. The one or more computer-readable media of claim 7, wherein to compare the search spaces of the third CORESET and the fourth CORESET, the UE is to compare search space parameters, the search space parameters comprising a search space type, a search space subtype, a periodicity, or an identifier.

9. The one or more computer-readable media according to any one of claims 1 to 8, wherein the instructions, when executed, further cause the UE to: A report is generated based on a synchronization signal block or a channel state information-reference signal, wherein the report includes a measurement process identifier taken from a transmission configuration indicator TCI of the PDCCH.

10. A user equipment UE, the UE comprising: Antenna panels; and A processing circuit is coupled to the antenna panel, and is used for: receiving downlink control information DCI from a first transmission and reception point TRP to schedule a plurality of physical downlink shared channel PDSCH transmissions from a corresponding plurality of TRPs; selecting a first default transmission configuration indicator TCI state and a second default TCI state based on a lowest TCI codepoint having two TCI states; configuring the first antenna panel to use a first default beam based on the first default TCI state; configuring the second antenna panel to use a second default beam based on the second default TCI state; identifying overlapping physical downlink control channel (PDCCH) transmissions that are to use resource elements of a control resource set (CORESET) associated with a third default TCI state; determining that the third default TCI state is different from the first default TCI state and the second default TCI state; as well as Based on the third default state and based on determining that the third default TCI state is different from the first default TCI state and the second default TCI state, the first antenna panel is reconfigured to use a third default beam. The UE according to claim 10 , wherein the plurality of PDSCH transmissions are frequency division multiplexing transmissions or space division multiplexing transmissions.

12. The UE according to claim 11, wherein after reconfiguring the first antenna panel, the processing circuit is further configured to: At least a portion of the plurality of PDSCH transmissions are received using the first antenna panel using the third default beam and the second antenna panel using the second default beam.

13. The UE according to claim 11, wherein after reconfiguring the first antenna panel, the processing circuit is further configured to: At least a portion of the plurality of PDSCH transmissions is received with the first antenna panel using the third default beam, and the second antenna panel is deactivated.

14. The UE according to claim 10, wherein the processing circuit is further configured to: Control signaling is received from a base station to indicate whether the UE is to use one antenna panel or two antenna panels to receive a PDSCH transmission when there are one or more overlapping PDCCH transmissions.

15. The UE according to claim 10, wherein the processing circuit is further configured to: A UE capability report is transmitted to a base station, the UE capability report including an indication of whether the UE is capable of receiving a PDSCH transmission using one antenna panel or two antenna panels when there are one or more overlapping PDCCH transmissions.

16. The UE according to any one of claims 10 to 15, wherein the overlapped PDCCH transmission is a first overlapped PDCCH transmission, the CORESET is a first CORESET, and the processing circuit is further configured to: identifying a second overlapped PDCCH transmission that will use resource elements of a second CORESET; Determining that the first CORESET has a higher priority than the second CORESET; as well as Based on the first CORESET having the higher priority, the first antenna panel is reconfigured to use the third default beam.

17. The UE of claim 16, wherein in order to determine that the first CORESET has the higher priority, the processing circuit is configured to compare search spaces of the first CORESET and the second CORESET.

18. A method of wireless communication, comprising: Processing first downlink control information DCI to determine scheduling of first physical downlink shared channel PDSCH transmission; processing a second DCI to determine scheduling for a second PDSCH transmission; configuring a first antenna panel to receive the first PDSCH transmission using a first default beam based on a first control resource set CORESET associated with the first DCI, wherein the first CORESET is configured with a first CORESET pool index; configuring a second antenna panel to receive the second PDSCH transmission using a second default beam based on a second CORESET associated with the second DCI, wherein the second CORESET is configured with a second CORESET pool index; detecting a physical downlink control channel (PDCCH) associated with a third CORESET configured with the first CORESET pool index, wherein the PDCCH overlaps with the first PDSCH transmission; as well as Based on the first CORESET and the third CORESET being configured with the first CORESET pool index, the first antenna panel is reconfigured to have a third default beam to receive the PDCCH.

19. The method according to claim 18, further comprising: After the first antenna panel is reconfigured with the third default beam, at least a portion of the first PDSCH transmission or the second PDSCH transmission is received using the second default beam and the third default beam.

20. The method of claim 18, wherein the first PDSCH transmission or the second PDSCH transmission is scheduled in a first component carrier, and the PDCCH is detected in a second component carrier.

Images