Computer-readable medium, user equipment, and method of wireless communication

Abstract

The embodiment of the invention relates to a computer readable medium, user equipment and a wireless communication method. The present application relates to devices and components, including apparatuses, systems, and methods for resolving spatial collisions between a physical downlink control channel beam and a default physical downlink shared channel beam in a wireless communication system.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 5, 2020, entering the Chinese national stage on January 17, 2023, with the Chinese national application number 202080104790.1 and the invention title of "Computer-readable Medium, User Equipment and Method for Wireless Communication". Background Art

[0002] The 3rd Generation Partnership Project (3GPP) network stipulates that multiple transmit and receive points (TRPs) can send downlink transmissions to a user equipment (UE). The UE can have multiple antenna panels configured to receive these downlink transmissions. If the UE does not have enough time to process the control information before receiving the downlink transmission, the UE may not be able to obtain sufficient information on how to configure these antenna panels for correct reception of the downlink transmission. Brief Description of the Drawings

[0003] Figure 1 Shows a network environment according to some embodiments.

[0004] Figure 2 Shows a downlink transmission according to some embodiments.

[0005] Figure 3 Shows a downlink transmission according to some embodiments.

[0006] Figure 4 Shows a downlink transmission according to some embodiments.

[0007] Figure 5 Shows a downlink transmission according to some embodiments.

[0008] Figure 6 Shows a downlink transmission according to some embodiments.

[0009] Figure 7 Shows an operation flow / algorithm structure according to some embodiments.

[0010] Figure 8 Shows an operation flow / algorithm structure according to some embodiments.

[0011] Figure 9 Shows an operation flow / algorithm structure according to some embodiments.

[0012] Figure 10 Shows a receiving component of a user equipment according to some embodiments.

[0013] Figure 11 Shows a user equipment according to some embodiments.

[0014] Figure 12 Shows a gNB according to some embodiments. Detailed Description

[0015] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, technologies, etc., in order to provide a thorough understanding of various aspects of the embodiments. However, it will be apparent to those skilled in the art who have benefited from the present disclosure that various aspects of the embodiments may be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0016] The following is a glossary of terms that may be used in the present disclosure.

[0017] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or group), or memories (shared, dedicated, or group) configured to provide the described function, application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system on a chip (SoC)), or digital signal processors (DSPs). In some embodiments, a 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 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 the hardware element and the program code may be referred to as a particular type of circuit.

[0018] As used herein, the term "processor circuit" refers to, is part of, or includes the following: 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 on computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0019] As used herein, the term "interface circuit" refers to a circuit, a part of such circuit, or a circuit including a circuit that implements 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.

[0020] As used herein, the term "user equipment" or "UE" refers to a device of a remote user having radio communication capabilities and capable of describing network resources in a communication network. Additionally, 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. Further, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0021] As used herein, the term "computer system" refers to any type of interconnected electronic device, computer device, or their components. Additionally, the term "computer system" or "system" may refer to various components of a computer communicatively coupled to each other. Further, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems communicatively coupled to each other and configured to share computing resources or networking resources.

[0022] 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 particular device, such as a computer device, a mechanical device, a memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and applications, workload units, etc. "Hardware resources" may refer to computing, storage, or networking resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or networking resources provided by a virtualization infrastructure to applications, devices, systems, etc. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides services and may include computing resources or networking resources. System resources may be considered a set of coherent functions, network data objects, or services accessible via a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0023] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or a data stream. 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 that represents a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection established between two devices for transmitting and receiving information.

[0024] As used herein, terms such as "instantiate", "instantiation", etc. refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

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

[0026] 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 networked computers, networked hardware, network equipment, network nodes, virtualized network functions, etc.

[0027] 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 content. An information element may include one or more additional information elements.

[0028] 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. For example, the UE 104 may communicate with the gNB 108 through a 3GPP New Radio (NR) cell. The UE 104 and the gNB 108 may communicate through an air interface compatible with 3GPP technical specifications (such as those 3GPP technical specifications that define the fifth-generation (5G) NR system standard).

[0029] The gNB 108 may include a gNB controller 112 coupled to one or more TRPs (e.g., TRP 116 and TRP 120). Generally, the gNB controller 112 may perform most of the 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-layer operations of the communication protocol stack (e.g., analog physical (PHY) layer operations).

[0030] gNB 108 may use TRPs 116 and 122 to geographically separate the points from which signals may be transmitted to or received from UE 104. This may increase the flexibility of using multi-input, multi-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 in a coordinated multi-point or carrier aggregation system.

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

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

[0033] The PBCH may be used to broadcast a master information block (MIB) to provide information facilitating access to an NR cell. The MIB may include a system frame number, a cell barred flag, and information usable to receive 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 UE 104 may use to initially access or obtain any other system information.

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

[0035] The PDSCH may be used to convey end-user application data, signaling radio bearer (SRB) messages, system information messages (other than e.g., the MIB), and paging messages.

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

[0037] In some embodiments, UE 104 may include multiple antenna elements in one or more antenna panels that allow for receive or transmit beamforming. Figure 1UE 104 with two antenna panels (Panel 1 and Panel 2) is shown. In the downlink direction, UE 104 can select beams to receive downlink transmissions based on SSB and Channel State Information - Reference Signal (CSI-RS). When in Radio Resource Control (RRC) idle mode, UE 104 can perform initial acquisition during the random access procedure using SSB and Physical Random Access Channel (PRACH) preambles to establish uplink and downlink beam pairs. These initial beam pairs can correspond to relatively wide beams. UE 104 can then enter RRC connected mode and initiate a beam refinement process to select more directional and higher-gain beams. The beam refinement process can be based on CSI-RS.

[0038] Although beamforming can be performed in both Frequency Range (FR) 1 (410 MHz to 7125 MHz) and FR2 (24250 MHz to 52600 MHz), beamforming for reception at UE 104 can be more applicable to FR2 because UE 104 can have more antennas due to the shorter wavelength.

[0039] Transmissions using different antenna ports can experience different radio channels. However, in some cases, different antenna ports can share common radio channel characteristics. For example, different antenna ports can have similar Doppler drift, 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 sharing one or more of these large-scale radio channel characteristics can 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 TypeA, the antenna ports share Doppler drift, Doppler spread, average delay, and delay spread. In QCL Type B, the antenna ports share Doppler drift and Doppler spread is shared. In QCL TypeC, the antenna ports share Doppler drift and average delay. In QCL TypeD, the antenna ports share spatial receiver parameters.

[0040] gNB 108 can provide Transmission Configuration Indicator (TCI) state information to UE 104 to indicate the QCL relationship between the antenna ports for reference signals (e.g., SSB or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). gNB 108 can use a combination of RRC signaling, MAC control element signaling, and DCI to notify UE 104 of these QCL relationships.

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

[0042] gNB 108 may then transmit an activation command via, for example, 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 apply to the PDSCH resource allocation.

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

[0044] gNB 108 may configure up to three CORESETs for the active downlink bandwidth part of the serving cell. The CORESET may be configured by the 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.

[0045] 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 in the active downlink bandwidth part to which the CORESET belongs as defined in the PDSCH-config. If the ControlResourceSet information element provides only a single TCI state, UE 104 may assume the QCL relationship between the PDCCH and the reference signal specified by that TCI state. If multiple TCI states are listed, UE 104 may rely on the activation command as described above to identify the TCI states to apply.

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

[0047] gNB 108 may operate in a single DCI mode or a multi-DCI mode. In the 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 PDSCH1 from TRP 116 and PDSCH 2 from TRP 120. In the multi-DCI mode, each TRP may transmit its own DCI to schedule its own PDSCH transmission. 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.

[0048] In various embodiments, 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, spatial-division multiplexing (SDM) may be used by providing different DMRS code-division multiplexing (CDM) groups for different PDSCH transmissions. In a third example, time-division multiplexing (TDM) may be used by transmitting PDSCH transmissions in different OFDM symbols.

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

[0050] In some embodiments, when the scheduling offset is below a threshold, gNB 108 may enable UE 104 to receive the 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 UE104 and, in some embodiments, may be reported from UE 104 to gNB 108 in a UE capability report.

[0051] In some embodiments, gNB 108 may enable two default beams by providing appropriate RRC parameters in the serving cell configuration information element that is used to configure (e.g., add or modify) the serving cell of UE 104. For the 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 the multi DCI mode, the RRC parameter may be the enableDefaultTCIStatePerCoresetPoolIndex RRC parameter. If enabled, the default PDSCH beam may be based on the CORESET among the CORESETs in each CORESET pool that has the lowest identifier in the most recent time slot.

[0052] In some cases, enabling multiple default beams to receive PDSCH transmissions may result in a spatial conflict between the PDSCH transmissions and other PDCCH transmissions in the same or different serving cells. Accordingly, various embodiments describe operations that may be used to handle the spatial conflict between the PDCCH and the default PDSCH beams in the multi DCI mode and the single DCI mode. The conflict handling may be described with reference to FDM, TDM, and CDM schemes.

[0053] Figure 2 A downlink transmission 200 is shown in accordance with some embodiments. The downlink transmission 200 may be 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 the same frequency band group.

[0054] The serving cell 1 may include a PDCCH 204 that schedules the PDSCH 212 and a PDCCH 208 that schedules the PDSCH 216. The PDCCH 204 and the PDSCH 212 may be transmitted from the TRP 116, while the PDCCH 208 and the PDSCH 216 may be transmitted from the TRP 120. Thus, this may represent multi-DCI mode operation.

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

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

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

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

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

[0060] 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 that CORESET pool may be based on that existing CORESET. Thus, referring to Figure 2 , when PDCCH 224 is received, it overlaps with the PDSCH transmission, and thus there is an existing CORESET for CORESET pool 0. Then, UE 104 may set the default PDSCH beam based on that existing CORESET (i.e., CORESET 2). Thus, in the second time period, e.g., t = 1, UE 104 may configure antenna panel 1 to have the fourth beam (based on CORESET4). This may configure UE 104 to correctly receive PDCCH 224.

[0061] In some embodiments, the first time period may correspond to the first time slot, in which UE 104 may receive PDSCH 212, and the second time period may correspond to the 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 a time period greater than or less than one time slot.

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

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

[0064] In the 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, UE 104 may operate as Figure 2 shown and described above. 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.

[0065] In a second option, the UE 104 may configure a default PDSCH beam based on a 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 and deactivate antenna panel 2 based on CORESET 2.

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

[0067] 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 a default PDSCH beam. For example, consider that the UE 104 determines that there are two CORESETs (e.g., CORESET 1 and CORESET 2, where CORESET 1 is the higher-priority CORESET) for pool 0 at a given time, and there is one CORESET (e.g., CORESET 3) for pool 1 at the given time. 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.

[0068] The CORESET priorities for each CORESET pool may be determined based on the search space associated with the CORESET. The parameters of the search space that may be used to establish priorities may include, but are not limited to, search space type (e.g., 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, e.g., whether the search space is type 0, type 0A, type 1, type 2, or type 3. Although not limited thereto, in some embodiments, CSS may have a higher priority than USS; a CORESET corresponding to a CSS set with a lower index may have a higher priority than a CORESET corresponding to a CSS set with a higher index; and a CORESET corresponding to a USS set with a lower index may have a higher priority than a CORESET corresponding to a USS set with a higher index, and so on.

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

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

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

[0072] The scheduling offset between PDCCH 304 and PDSCH transmission can be less than a predetermined threshold 320, which can be based on UE capabilities. Thus, UE 104 can determine multiple default beams to receive PDSCH transmission.

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

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

[0075] 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 can be based on the beam of the existing CORESET. In some embodiments, UE 104 can use the beam based on the existing CORESET and the first or second beam based on the default TCI to receive PDSCH. Thus, referring Figure 3 , when PDCCH 316 is received, there is an existing CORESET, e.g., CORESET 2. Thus, UE 104 can configure antenna panel 1 to have a fourth beam (based on CORESET 2) during a second time period (e.g., t = 1).

[0076] Figure 4Shows a downlink transmission 400 according to some embodiments. The downlink transmission 400 may be based on an FDM or SDM transmission scheme.

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

[0078] So, when the PDCCH 416 is received and there is an existing CORESET (e.g., CORESET 2), the 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 thus not used for the reception of the corresponding PDSCH (e.g., PDSCH 412).

[0079] Reference Figure 3 and Figure 4 The single DCI mode operation described with respect to the FDM / SDM 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. The control signaling may be high-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 the 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 from the gNB 108 or other predefined configuration information.

[0080] In some embodiments, similar to those described above with reference to Figure 2As described above, multiple CORESETs can exist in the same serving cell or serving cells in a common frequency band or frequency band group at a given time. For single DCI mode, the UE can also determine the priorities of the multiple CORESETs and select the CORESET with the highest relative priority for the default PDSCH beam. In some embodiments, priorities can be determined for each CORESET pool. If there are existing CORESETs from two CORESET pools, the UE 104 can select two beams to receive the PDSCH. In some embodiments, the UE 104 can determine CORESET priorities across 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 can select the beams corresponding to the two CORESETs in CORESET pool 1 for receiving the PDSCH.

[0081] The relative priority of a CORESET can be based on the associated search space referenced above Figure 2 as described.

[0082] Figure 5 A downlink transmission 500 is shown in accordance with some embodiments. The downlink transmission 500 can be based on a TDM transmission scheme.

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

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

[0085] In some embodiments, for a TDM scheme operating in single DCI mode, if there is one existing CORESET in the same serving cell or another serving cell, the UE 104 can set the default PDSCH beam for the current transmission opportunity based on the beam of the existing CORESET. Thus, referring to Figure 5When the PDCCH 516 is received, there is an existing CORESET, e.g., CORESET 2. Thus, the 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). Thus, the UE 104 may apply the default PDSCH beam based on the default TCI to transmission opportunities that do not conflict with other CORESETs, and may apply the existing CORESET beam to transmission opportunities that conflict with other CORESETs.

[0086] In embodiments where multiple CORESETs exist at a particular time, the UE 104 may determine which CORESET among the multiple CORESETs has the highest priority and apply the beam corresponding to that CORESET to the corresponding transmission opportunity. This may be done similar to that described elsewhere herein.

[0087] Figure 6 A downlink transmission 600 is shown in accordance with some embodiments. The downlink transmission 600 may be based on a TDM transmission scheme.

[0088] The downlink transmission 600 may be similar to those described above with reference to the downlink transmission 500. However, in this embodiment, instead of applying the default PDSCH beam based on the default TCI to transmission opportunities that do not conflict with the CORESET, the UE 104 may apply the CORESET beam to all transmission opportunities. Thus, referring to Figure 6 Since the PDCCH 616 conflicts with the PDSCH transmission opportunity 2612, the UE 104 may set the default PDSCH beam to the fourth beam (based on CORESET 2) on Panel 1 for all transmission opportunities (e.g., PDSCH transmission opportunity 1 608 and PDSCH transmission opportunity 2612).

[0089] Referring to Figure 5 and Figure 6 The single DCI mode operations 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 more preferable than the other in certain scenarios. For example, when the TDM scheme is an intra-slot TDM scheme where two PDSCH transmission opportunities are in the same time slot, the gNB 108 may determine that Figure 6 the option embodied by Figure 5 may be advantageous. Alternatively, when the TDM scheme is an inter-slot TDM scheme where two PDSCH transmission opportunities are in different time slots, the gNB 108 may determine that

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

[0091] In some embodiments, UE 104 may provide measurement reports for different measurement process identifiers, each measurement process identifier 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 one existing CORESET, UE 104 may measure the reference signal and provide the corresponding measurement report based on its TCI rather than the measurement signal associated with the default PDSCH TCI having the same measurement process ID. If there are multiple existing CORESETs with TCI from the same measurement process ID, UE 104 may select one CORESET with the highest priority rather than the default PDSCH TCI having the same measurement process ID as the basis for reporting the measurement result. The priorities of multiple existing CORESETs may be based on the search space associated with the respective CORESETs.

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

[0093] Figure 7 It may include an operation flow / algorithm structure 700 according to some embodiments. The operation flow / algorithm structure 700 may be executed or implemented by a UE (such as UE 104 or 1100) or its components (e.g., baseband processor 1104A).

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

[0095] The DCI can be included in the corresponding PDCCH transmission, and each PDCCH transmission is transmitted on the resource elements associated with the corresponding CORESET. The CORESET can include a TCI state, and the UE can use this TCI state to determine the QCL information to facilitate the determination of the beam for receiving the corresponding PDCCH transmission. The UE can configure the first antenna panel and the second antenna panel to receive the PDCCH transmission based on the beam determined by the corresponding CORESET.

[0096] The operation flow / algorithm structure 700 further 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 can default to the same beam as the beam for receiving the PDCCH transmission. That is, based on the beam of the CORESET associated with the PDCCH that transmits the scheduling DCI.

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

[0098] The operation flow / algorithm structure 700 may further include: at 716, reconfiguring the antenna panel to have a third default beam. The third default beam can be based on the existing CORESET. In some embodiments, one of the antenna panels in the antenna panel can 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 can be activated.

[0099] Figure 8 It may include an operation flow / algorithm structure 800 according to some embodiments. The operation flow / algorithm structure 800 can be executed or implemented by a UE (such as UE 104 or 1100) or its components (e.g., the baseband processor 1104A).

[0100] The operation flow / algorithm structure 800 can include: at 804, receiving DCI to schedule the PDSCH transmission.

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

[0102] The operation procedure / algorithm structure 800 may further include: at 808, configuring the antenna panel to use a first default beam based on a default TCI state.

[0103] 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.

[0104] The operation procedure / algorithm structure 800 may further include: at 812, identifying overlapping PDCCH transmissions of resource elements that will use the CORESET. The overlapping PDCCH transmissions may cause the CORESET to be present during the 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 operation procedure / algorithm structure 800.

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

[0106] Figure 9 It may include an operation procedure / algorithm structure 900 according to some embodiments. In some embodiments, the operation procedure / algorithm structure 900 may be executed or implemented by a gNB (e.g., gNB 108 or gNB 1200) or its components (e.g., the baseband processor 1204A).

[0107] The operation procedure / algorithm structure 900 may include: at 904, receiving a UE capability report. The capability report may provide an indication of whether the UE is capable of using two default beams.

[0108] The operation procedure / algorithm structure 900 may further 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 that in the presence of an existing CORESET, the UE should: (1) receive the PDSCH using the CORESET beam and the first / second default TCI beams; or (2) receive the PDSCH only using the CORESET beam. As another example, the control indication may indicate that 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.

[0109] In various embodiments, 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.

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

[0111] The antenna panel may be coupled to a corresponding analog beamforming (BF) component. For example, panel 1 1004 may be coupled to the analog BF component 1012, and panel 2 1008 may be coupled to the analog BF component 1016.

[0112] The analog BF component may be coupled to one or more radio frequency (RF) chains. For example, the analog BF component 1012 may be coupled to one or more RF chains 1020, and the analog BF component 1016 may be coupled to one or more RF chains 1024. The RF chain 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 can be provided to the digital BF component 1028. The digital BF component 1028 may provide a baseband (BB signal) for further BB processing.

[0113] In various embodiments, control circuitry that may reside in a baseband processor may provide BF weights to an analog / digital BF component to provide a receive beam at a corresponding antenna panel. 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 phase shifters of the analog BF component 1012 or complex weights provided to the digital BF component 1028. In some embodiments, the BF component and the antenna panel may operate together to provide a dynamic phased array capable of steering a beam of light in a desired direction.

[0114] In various embodiments, beamforming may include analog beamforming, all-digital beamforming, or hybrid analog-digital beamforming. All-digital beamforming may utilize separate RF chains corresponding to individual antenna elements.

[0115] Figure 11 Shown is a UE 1100 according to some embodiments. The UE 1100 may be similar to Figure 1 the UE 104 and may be substantially interchangeable with Figure 1 the UE 104.

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

[0117] The UE 1100 may include a processor 1104, an RF interface circuit 1108, a memory / storage device 1112, a user interface 1116, sensors 1120, a drive circuit 1122, a power management integrated circuit "PMIC" 1124, an antenna structure 1126, and a battery 1128. The components of the UE 1100 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 11 The block diagram is intended to show a high-level view of certain of the components of the UE 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the shown components may occur in other implementations.

[0118] Components of the 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 expansion), transmission line, trace, optical connector, etc., that allows various circuit components (on common or different chips or chip sets) to interact with each other.

[0119] The processor 1104 may include processor circuitry such as baseband processor circuitry “BB” 1104A, central processing unit circuitry “CPU” 1104B, and graphics processing unit circuitry “GPU” 1104C. The processor 1104 may include any type of circuit or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from the memory / storage 1112) to cause the UE 1100 to perform the operations described herein.

[0120] In some embodiments, the baseband processor circuitry 1104A may access the communication protocol stack 1136 in the memory / storage 1112 to communicate via a 3GPP-compliant network. Generally, the baseband processor circuitry 1104A may 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 stratum. In some embodiments, the PHY layer operations may additionally / alternatively be performed by components of the RF interface circuit 1108.

[0121] The baseband processor circuitry 1104A may generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some embodiments, the waveforms 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.

[0122] The memory / storage device 1112 may include one or more non-transitory computer-readable media that include instructions (e.g., communication protocol stack 1136) that may be executed by one or more of the processors 1104 to cause the UE 1100 to perform the various operations described herein. The memory / storage device 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 device 1112 may be located on the processors 1104 themselves (e.g., L1 cache and L2 cache), while other memory / storage device 1112 is located external to the processors 1104 but may be accessed via a memory interface. The memory / storage device 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.

[0123] The RF interface circuit 1108 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1100 to communicate with other devices via 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.

[0124] In the receive path, the RFEM may receive a 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 receiver of the transceiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1104.

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

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

[0127] Antenna 1126 may include antenna elements to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. These antenna elements may be arranged into one or more antenna panels. Antenna 1126 may have an antenna panel with an omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communication. Antenna 1126 may include a microstrip antenna, a printed antenna fabricated 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 of a band included in FR1 or FR2.

[0128] User interface circuit 1116 includes various input / output (I / O) devices that are designed to enable a user to interact with UE 1100. User interface 1116 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise communicating information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary state indicators such as a light-emitting diode “LED” and multi-character visual outputs), or more complex outputs such as a display device or a touchscreen (e.g., a liquid crystal display “LCD”, an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of UE 1100.

[0129] Sensor 1120 may include a device, module, or subsystem aimed at detecting an event or change in its environment and sending information about the detected event (sensor data) to some other device, module, subsystem, etc. Examples of such sensors particularly include: an inertial measurement unit including an accelerometer, a gyroscope, or a magnetometer; a microelectromechanical system or a nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; 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 devices; etc.

[0130] The drive circuit 1122 may include software elements and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled with the UE 1100. The drive circuit 1122 may include various drivers, allowing other components to interact with or control various input / output (I / O) devices that may be present within or connected to the UE 1100. For example, the drive circuit 1122 may include: a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for obtaining sensor readings from the sensor circuit 1120 and controlling and allowing access to the sensor circuit 1120, a driver for obtaining the 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.

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

[0132] 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 remains connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state called discontinuous reception mode (DRX). During this state, the UE 1100 may power down for short intervals, thus saving power. If there is no data traffic activity for an extended period, the UE 1100 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1100 enters a very low power state and performs paging, in which the device wakes up periodically again to listen for the network and then powers down again. The UE 1100 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes may cause the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and may be completely powered down. Any data sent during this period will incur a significant delay, and it is assumed that the delay is acceptable.

[0133] 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.

[0134] Figure 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.

[0135] 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.

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

[0137] 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 Figure 11 Like-named elements are shown and described.

[0138] 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.

[0139] 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.

[0140] 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 example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples set forth below. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples shown in the example section below.

[0141] Embodiment

[0142] In the following section, additional exemplary embodiments are provided.

[0143] Example 1 includes a method of operating a UE, the method comprising: receiving, from a plurality of transmit and receive points (TRPs), a plurality of downlink control information (DCI) to schedule a plurality of physical downlink shared channel (PDSCH) transmissions; 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 plurality of PDSCH transmissions based on a first control resource set (CORESET) and a second CORESET associated with the plurality of DCI; detecting a physical downlink control channel (PDCCH) associated with a third CORESET that overlaps at least one of the PDSCH transmissions; and reconfiguring the first antenna panel to have a third default beam to receive at least a portion of the plurality of PDSCH transmissions based on the third CORESET.

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

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

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

[0147] Example 5 includes the method according to Example 1 or some other example herein, wherein the plurality of PDSCH transmissions are scheduled in a first component carrier, and the PDCCH is detected in a second component carrier.

[0148] Example 6 includes the method according to Example 5 or some other example herein, wherein the first component carrier and the second component carrier are in a common frequency band or frequency band group.

[0149] Example 7 includes the method according to Example 1 or some other example herein, wherein the PDCCH is a first PDCCH, a 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 a first antenna panel to have a third default beam based on the first PDCCH having the higher priority.

[0150] Example 8 includes the method according to Example 7 or some other example herein, wherein determining that the first PDCCH has a higher priority includes: comparing the search spaces of the third CORESET and the fourth CORESET.

[0151] Example 9 includes the method according to Example 8 or some other example 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.

[0152] Example 10 includes the method according to an example in one or some other examples herein, further including generating a report based on a synchronization signal block or channel state information - reference signal, wherein a measurement process identifier is taken from a transmission configuration indicator (TCI) of the PDCCH.

[0153] Example 11 includes a method of operating a UE, the method including: receiving downlink control information (DCI) from a first transmit and receive point (TRP) to schedule a plurality of physical downlink shared channel (PDSCH) transmissions from corresponding plural 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 of resource elements that will use a control resource set (CORESET); and reconfiguring the antenna panel to use a second default beam based on the CORESET.

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

[0155] Embodiment 13 includes the 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 plurality of PDSCH transmissions using the first antenna panel using the second default beam and the second antenna panel using the third default beam.

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

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

[0158] Embodiment 16 includes the method according to Embodiment 11 or some other embodiment herein, further including: transmitting a UE capability report to the 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 PDSCH transmissions when there are one or more overlapping PDCCH transmissions.

[0159] Embodiment 17 includes the method according to Embodiment 11 or some other embodiment herein, wherein the overlapping PDCCH transmissions are first overlapping PDCCH transmissions, the CORESET is the first CORESET, and the method further includes: identifying second overlapping PDCCH transmissions 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 the second default beam based on the first CORESET having the higher priority.

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

[0161] Embodiment 19 includes a method of 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 receiving physical downlink shared channel (PDSCH) transmissions using one or two default beams 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 for enabling 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.

[0162] Embodiment 20 includes the method according to Embodiment 19 or some other embodiment herein, further comprising: transmitting one or more downlink control information (DCI) to schedule a plurality of PDSCH transmission opportunities, wherein the plurality of PDSCH opportunities are scheduled with a scheduling offset less than a predetermined threshold, and the control indication is for indicating that the UE will use one default beam to receive PDSCH transmissions in all of the plurality of PDSCH transmission opportunities.

[0163] Embodiment 21 may include an apparatus, the apparatus including means for performing one or more elements of the method according to any one of Embodiments 1 to 20 or related thereto, or any other method or process described herein.

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

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

[0166] Embodiment 24 may include the method, technique or process according to any one of Embodiments 1 to 20 or related thereto, or a part or component thereof.

[0167] Embodiment 25 may include an apparatus, the apparatus including: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, technique or process according to any one of Embodiments 1 to 20 or related thereto, or a part thereof.

[0168] Example 26 may include a signal as described in or related to any one of Examples 1 to 20, or a part or component thereof.

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

[0170] Example 28 may include a signal encoded with data as described in or related to any one of Examples 1 to 20, or a part or component thereof, or otherwise described in the present disclosure.

[0171] Example 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any one of the above Examples 1 to 64, or a part or component thereof, or otherwise described in the present disclosure.

[0172] Example 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 as described in or related to any one of Examples 1 to 20, or a part thereof.

[0173] Example 31 may include a computer program, the computer program including instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described in or related to any one of Examples 1 to 20, or a part thereof.

[0174] Example 32 may include a signal in a wireless network as shown and described herein.

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

[0176] Example 34 may include a system for providing wireless communication as shown and described herein.

[0177] Example 35 may include a device for providing wireless communication as shown and described herein.

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

[0179] While the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. This disclosure is intended that the following claims be interpreted to cover all such variations and modifications.

Claims

1. A method, comprising: detecting radio resource control (RRC) parameters to enable default transmission control indicator (TCI) state operation; determining that a physical downlink shared channel (PDSCH) transmission overlaps with a physical downlink control channel (PDCCH) transmission; and prioritizing reception of the PDCCH transmission based on the detected RRC parameters.

2. The method according to claim 1, wherein the RRC parameters are used to enable the default TCI state for each control resource set (CORESET) pool index, and the method further comprises: determining that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index; and prioritizing reception of the PDCCH transmission based on determining that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index.

3. The method according to claim 2, wherein the RRC parameters are used to configure multiple downlink control information (DCI) modes.

4. The method according to claim 1, wherein the RRC parameters are used to enable two default transmission control indicator (TCI) states, and the method further comprises: determining two default PDSCH beams based on the lowest TCI code point in a TCI code point including two TCI states, wherein the two default PDSCH beams are associated with two PDSCH transmissions, and the two PDSCH transmissions include the PDSCH transmission; determining that the two default PDSCH beams are different from the beam associated with the PDCCH transmission; and configuring the beam associated with the PDCCH transmission for reception based on determining that the two PDSCH beams are different from the beam associated with the PDCCH transmission.

5. The method according to claim 4, wherein the RRC parameters are used to configure a single downlink control information (DCI) mode.

6. The method according to claim 1, wherein the PDSCH transmission is associated with a first component carrier of a frequency band, and the PDCCH transmission is associated with a second component carrier of the frequency band.

7. One or more non-transitory computer-readable storage media having instructions that, when executed, cause a processing circuitry to perform the following operations: detecting radio resource control (RRC) parameters to enable default transmission control indicator (TCI) state operation; determining that a physical downlink shared channel (PDSCH) transmission overlaps with a physical downlink control channel (PDCCH) transmission; and configuring the beam associated with the PDCCH transmission for reception based on the detection of the RRC parameters.

8. The one or more non-transitory computer-readable storage media according to claim 7, wherein the RRC parameters are used to enable the default transmission control indicator (TCI) state for each control resource set (CORESET) pool index, and the instructions, when executed, further cause the processing circuitry to: determine that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index; and Further configure the beam associated with the PDCCH transmission for reception based on determining that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index.

9. The one or more non-transitory computer-readable storage media according to claim 8, wherein the RRC parameter is used to configure a multi-downlink control information DCI mode.

10. The one or more non-transitory computer-readable storage media according to claim 7, wherein the RRC parameter is used to enable two default transmission control indicator (TCI) states, and the instructions, when executed, further cause the processing circuitry: Determine two default PDSCH beams based on the lowest TCI code point in a TCI code point including two TCI states, wherein the two default PDSCH beams are associated with two PDSCH transmissions, and the two PDSCH transmissions include the PDSCH transmission; Determine that the two default PDSCH beams are different from the beam associated with the PDCCH transmission; and Further configure the beam associated with the PDCCH transmission for reception based on determining that the two PDSCH beams are different from the beam associated with the PDCCH transmission.

11. The one or more non-transitory computer-readable storage media according to claim 10, wherein the RRC parameter is used to configure a single downlink control information DCI mode.

12. The one or more non-transitory computer-readable media according to claim 7, wherein the processing circuitry is used to configure an antenna panel with the beam.

13. The one or more non-transitory computer-readable media according to claim 7, wherein the PDSCH transmission is associated with a first component carrier of a frequency band, and the PDCCH transmission is associated with a second component carrier of the frequency band.

14. An apparatus, comprising: processing circuitry, configured to: detect a radio resource control (RRC) parameter to enable default transmission control indicator (TCI) state operation; determine that a physical downlink shared channel (PDSCH) transmission overlaps with a physical downlink control channel (PDCCH) transmission; and configure reception parameters to prioritize reception of the PDCCH transmission based on the detection of the RRC parameter; and interface circuitry coupled to the processing circuitry to enable communication.

15. The apparatus according to claim 14, wherein the RRC parameter is used to enable a default TCI state for each control resource set (CORESET) pool index, and the processing circuitry is further configured to: determine that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index, wherein, to configure the reception parameters, the processing circuitry further configures the beam associated with the PDCCH transmission for reception based on determining that both the PDSCH transmission and the PDCCH transmission are associated with the same CORESET pool index.

16. The apparatus according to claim 15, wherein the RRC parameter is used to configure a multi-downlink control information DCI mode.

17. The apparatus according to claim 14, wherein the RRC parameter is used to enable two default transmission control indicator (TCI) states, and the processing circuitry is further configured to: determine two default PDSCH beams based on a lowest TCI code point among TCI code points including the two TCI states, wherein the two default PDSCH beams are associated with two PDSCH transmissions, and the two PDSCH transmissions include the PDSCH transmission; determine that the two default PDSCH beams are different from a beam associated with the PDCCH transmission; and further configure the reception parameter based on determining that the two PDSCH beams are different from the beam associated with the PDCCH transmission.

18. The apparatus according to claim 17, wherein the RRC parameter is used to configure a single-downlink control information DCI mode.

19. The apparatus according to claim 14, wherein in order to configure the reception parameter, the processing circuitry configures an antenna panel by using a reception beam associated with the PDCCH transmission.

20. The apparatus according to claim 14, wherein the PDSCH transmission is associated with a first component carrier of a frequency band, and the PDCCH transmission is associated with a second component carrier of the frequency band.

Images