WO2020086572A1 - Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch) - Google Patents

Abstract

Embodiments of a User Equipment (UE) and methods of communication are generally described herein. The UE may receive control signaling that configures one or more control resource sets (CORESETs). Each of the CORESETs may be allocated for reception of one or more physical downlink control channels (PDCCHs). Each of the CORESETs may be associated with a CORESET identifier (CORESET-ID). The UE may determine that reception of a physical downlink shared channel (PDSCH) scheduled by one of the PDCCHs is to be performed based on quasi-colocation (QCL). The UE 102 may determine the QCL based on Transmission Configuration Indication (TCI), CORESET-ID and/or other factors. The UE may receive the PDSCH in accordance with the determined QCL.

Description

DETERMINATION OF QUASI-COLOCATION (QCL) FOR RECEPTION OF A PHYSICAL DOWNLINK SHARED CHANNEL (PDSCH)

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 62/749,959, filed October 24, 2018, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, and 3GPP LTE (Long Term Evolution) networks, Fifth Generation (5G) networks, and/or New Radio (NR) networks. Some embodiments relate to physical downlink control channels (PDCCHs). Some embodiments relate to physical downlink shared channels (PDSCHs). Some embodiments relate to quasi -colocation (QCL). Some embodiments relate to determine of QCL for reception of PDSCH.

BACKGROUND

[0003] Efficient use of the resources of a wireless network is important to provide bandwidth and acceptable response times to the users of the wireless network. However, often there are many devices trying to share the same resources and some devices may be limited by the communication protocol they use or by their hardware bandwidth. Moreover, wireless devices may need to operate with both newer protocols and with legacy device protocols. BRIEF DESCRIPTION OF THE DRAWINGS [0004] FIG. 1 A is a functional diagram of an example network in accordance with some embodiments;

[0005] FIG. 1B is a functional diagram of another example network in accordance with some embodiments;

[0006] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments;

[0007] FIG. 3 illustrates an exemplary communication circuitry according to some aspects;

[0008] FIG. 4 illustrates the operation of a method of communication in accordance with some embodiments;

[0009] FIG. 5 illustrates examples of quasi-colocation (QCL) in accordance with some embodiments; and

[0010] FIG. 6 illustrates example operations in accordance with some embodiments.

DETAILED DESCRIPTION

[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] FIG. 1 A is a functional diagram of an example network in accordance with some embodiments. FIG. 1B is a functional diagram of another example network in accordance with some embodiments. In references herein, “FIG. 1” may include FIG. 1 A and FIG. 1B. In some embodiments, the network 100 may be a Third Generation Partnership Project (3 GPP) network. In some embodiments, the network 150 may be a 3GPP network, a new radio (NR) network and/or Fifth Generation (5G) network. Other networks may be used in some embodiments. In some embodiments, a network may include one or more of: one or more components shown in FIG. 1 A; one or more components shown in FIG. 1B; and one or more additional components. Some embodiments may not necessarily include all components shown in FIG. 1 A and FIG. 1B.

[0013] The network 100 may comprise a radio access network (RAN)

101 and the core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an Sl interface 115. For convenience and brevity sake, only a portion of the core network 120, as well as the RAN 101, is shown. In some embodiments, the RAN 101 may include one or more of: one or more components of an evolved universal terrestrial radio access network (E- ETTRAN), one or more components of an NR network, and/or one or more other components.

[0014] The core network 120 may include a mobility management entity

(MME) 122, a serving gateway (serving GW) 124, and packet data network gateway (PDN GW) 126. In some embodiments, the networks 100, 150 may include (and/or support) one or more Evolved Node-B’s (eNBs) 104 and/or one or more Next Generation Node-B’s (gNBs) 105. The eNBs 104 and/or gNBs 105 may operate as base stations for communicating with User Equipment (UE) 102. In some embodiments, one or more eNBs 104 may be configured to operate as gNBs 105. Embodiments are not limited to the number of eNBs 104 shown in FIG. 1 A or to the number of gNBs 105 shown in FIG. 1B.

Embodiments are also not limited to the connectivity of components shown in FIG. 1A.

[0015] It should be noted that references herein to an eNB 104 or to a gNB 105 are not limiting. In some embodiments, one or more operations, methods and/or techniques (such as those described herein) may be practiced by a base station component (and/or other component), including but not limited to a gNB 105, an eNB 104, a serving cell, a transmit receive point (TRP) and/or other. In some embodiments, the base station component may be configured to operate in accordance with one or more of: a 3 GPP LTE protocol/standard, an NR protocol/standard, a Fifth Generation (5G) protocol/standard; and/or other protocol/standard, although the scope of embodiments is not limited in this respect.

[0016] Descriptions herein of one or more operations, techniques and/or methods practiced by a component (such as the UE 102, eNB 104, gNB 105 and/or other) are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by another component.

[0017] The MME 122 manages mobility aspects in access such as gateway selection and tracking area list management. The serving GW 124 terminates the interface toward the RAN 101, and routes data packets between the RAN 101 and the core network 120. In addition, it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter- 3GPP mobility. The serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.

[0018] In some embodiments, EIEs 102, the eNB 104 and/or gNB 105 may be configured to communicate Orthogonal Frequency Division

Multiplexing (OFDM) communication signals over a multicarrier

communication channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique.

[0019] In some embodiments, the network 150 may include one or more components configured to operate in accordance with one or more 3 GPP standards, including but not limited to an NR standard. The network 150 shown in FIG. 1B may include a next generation RAN (NG-RAN) 155, which may include one or more gNBs 105. In some embodiments, the network 150 may include the E-UTRAN 160, which may include one or more eNBs. The E- ETTRAN 160 may be similar to the RAN 101 described herein, although the scope of embodiments is not limited in this respect.

[0020] In some embodiments, the network 150 may include the MME

165, which may be similar to the MME 122 described herein, although the scope of embodiments is not limited in this respect. In some embodiments, the network 150 may include the SGW 170, which may be similar to the SGW 124 described herein, although the scope of embodiments is not limited in this respect.

[0021] Embodiments are not limited to the number or type of

components shown in FIG. 1B. Embodiments are also not limited to the connectivity of components shown in FIG. 1B.

[0022] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

[0023] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments. The machine 200 is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed. In alternative embodiments, the machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines. The machine 200 may be a EE 102, eNB 104, gNB 105, access point (AP), station (STA), user, device, mobile device, base station, another device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0024] Examples as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. [0025] The machine (e.g., computer system) 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The machine 200 may further include one or more of 210-228.

[0026] The storage device 216 may include a machine readable medium

222 on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine 200. In an example, one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute machine readable media. In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine readable medium may be or may include a computer-readable storage medium.

[0027] While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224. The term“machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable

Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine readable media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0028] The instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols. In an example, the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0029] FIG. 3 illustrates an exemplary communication circuitry according to some aspects. It should be noted that a device, such as a UE 102, eNB 104, gNB 105, the machine 200 and/or other device may include one or more components of the communication circuitry 300, in some aspects. The communication circuitry 300 may include protocol processing circuitry 305, which may implement one or more of: medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS) functions. The communication circuitry 300 may further include digital baseband circuitry 310, which may implement one or more physical layer (PHY) functions. The communication circuitry 300 may further include transmit circuitry 315, receive circuitry 320 and/or antenna array circuitry 330. The communication circuitry 300 may further include radio frequency (RF) circuitry 325. In an aspect of the disclosure, RF circuitry 325 may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array 330. [0030] In some embodiments, processing circuitry may perform one or more operations described herein and/or other operation(s). In a non-limiting example, the processing circuitry may include one or more components such as the processor 202, protocol processing circuitry 305, digital baseband circuitry 310, similar component(s) and/or other component(s).

[0031] In some embodiments, a transceiver may transmit one or more elements (including but not limited to those described herein) and/or receive one or more elements (including but not limited to those described herein). In a non limiting example, the transceiver may include one or more components such as transmit circuitry 315, receive circuitry 320, radio frequency circuitry 325, similar component(s) and/or other component(s).

[0032] Although the UE 102, eNB 104, gNB 105, machine 200 and/or other device described herein may each be illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), one or more microprocessors, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0033] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0034] It should be noted that in some embodiments, an apparatus of the

UE 102, eNB 104, gNB 105, machine 200, and/or other device may include various components shown in FIGs. 2-3 and/or other components. Accordingly, techniques and operations described herein that are performed by a device may be performed by an apparatus of the device, in some embodiments.

[0035] In accordance with some embodiments, the UE 102 may receive, from the gNB 105, control signaling that configures one or more control resource sets (CORESETs). Each of the CORESETs may be allocated for reception of one or more physical downlink control channels (PDCCHs). Each of the CORESETs may be associated with a CORESET identifier (CORESET- ID). The UE 102 may receive one or more PDCCHs from the gNB 105. For a physical downlink shared channel (PDSCH) scheduled by one of the PDCCHs, when a scheduling offset between the PDSCH and the corresponding PDCCH is less than a threshold, the UE 102 may determine that reception of the PDSCH is to be performed based on quasi-colocation (QCL) between the PDSCH and: one or more reference signals (RSs) configured by a Transmission Configuration Indication (TCI) state in the control signaling; or demodulation reference signals (DMRSs) of the PDCCH, from the one or more decoded PDCCHs, that is associated with the CORESET of lowest CORESET-ID. The UE 102 may receive the PDSCH in accordance with the determined QCL. These

embodiments are described in more detail below.

[0036] FIG. 4 illustrates the operation of a method of communication in accordance with some embodiments. Embodiments of the method 400 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 4. Embodiments of the method 400 are not necessarily limited to the chronological order that is shown in FIG. 4.

[0037] In some embodiments, a UE 102 may perform one or more operations of the method 400, but embodiments are not limited to performance of the method 400 and/or operations of it by the UE 102. In some embodiments, a device and/or component (including but not limited to the UE 102, gNB 105 and/or eNB 104) may perform one or more operations that may be the same as, similar to, reciprocal to and/or related to an operation of the method 400.

[0038] Discussion of various operations, techniques and/or concepts regarding one method described herein (such as the method 400 and/or other) may be applicable to other operations described herein and/or other methods described herein. One or more of the techniques, operations and/or methods described herein may be performed by a device other than an eNB 104, gNB 105, and UE 102, including but not limited to a Wi-Fi access point (AP), station (STA) and/or other.

[0039] In some embodiments, an apparatus of a device (including but not limited to the UE 102, eNB 104, gNB 105 and/or other) may comprise memory that is configurable to store one or more elements, and the apparatus may use them for performance of one or more operations. The apparatus may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method 400 and/or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and/or the processing circuitry may perform one or more operations described herein. The apparatus may include a transceiver to transmit and/or receive one or more blocks, messages and/or other elements.

[0040] Embodiments are not limited by references herein to

transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such an element may be generated, encoded or otherwise processed by processing circuitry for transmission by a transceiver or other component cases. In some embodiments, such an element may be received by a transceiver or other component, and may be decoded, detected or otherwise processed by processing circuitry. In some embodiments, the processing circuitry and the transceiver may be included in a same apparatus. In some embodiments, the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.

[0041] One or more of the elements (such as messages, operations and/or other) described herein may be included in a 3 GPP protocol, 3 GPP LTE protocol, 4G protocol, 5G protocol, NR protocol and/or other protocol, but embodiments are not limited to usage of those elements. In some embodiments, other elements may be used, including other element(s) in a same

standard/protocol, other element(s) in another standard/protocol and/or other. In addition, the scope of embodiments is not limited to usage of elements that are included in standards.

[0042] In some embodiments, the UE 102, eNB 104 and/or gNB 105 may be arranged to operate in accordance with a 3 GPP protocol, NR protocol, and/or other protocol.

[0043] At operation 405, the UE 102 may exchange control signaling with a gNB 105. It should be noted that multiple instances of control signaling may be exchanged, in some embodiments. In some embodiments, the exchange of control signaling may include one or more of: transmission of one or more elements by the UE 102, transmission of one or more elements by the UE 102 to the gNB 105, reception of one or more elements by the UE 102, reception of one or more elements from the gNB 105 by the UE 102, and/or other. The above elements may include signaling, messages and/or other. In some embodiments, the control signaling may include multiple messages, multiple instances of signaling, multiple types of signaling, multiple elements and/or other.

[0044] In some embodiments, the UE 102 may receive, from the gNB

105 and/or other component, control signaling that configures one or more control resource sets (CORESETs). The control signaling may include one or more additional elements, in some embodiments.

[0045] In some embodiments, each of the CORESETs may be allocated for one or more physical downlink control channels (PDCCHs), although the scope of embodiments is not limited in this respect. In some embodiments, each of the CORESETs may be allocated for reception of one or more PDCCHs, although the scope of embodiments is not limited in this respect.

[0046] In some embodiments, each of the CORESETs may be mapped to a search space (SS) of time resources and frequency resources. The SSs may be searched by the UE 102 as part of detection of one or more PDCCHs, in some embodiments.

[0047] In some embodiments, each of the CORESETs may be associated with a CORESET identifier (CORESET-ID). In some embodiments, one or more of the CORESETs may be associated with a CORESET-ID.

[0048]

[0049] At operation 410, the UE 102 may receive one or more PDCCHs.

At operation 415, the UE 102 may determine quasi-colocation (QCL) for a physical downlink shared channel (PDSCH). At operation 420, the UE 102 may receive the PDSCH.

[0050] In some embodiments, the UE 102 may receive one or more

PDCCHs. In some embodiments, the UE 102 may receive one or more

PDCCHs from the gNB 105, although the scope of embodiments is not limited in this respect. In some embodiments, a PDCCH may schedule a PDSCH. In some embodiments, one or more of the received PDCCHs may schedule one or more PDSCHs.

[0051] In some embodiments, the UE 102 may receive the PDSCH in accordance with the determined QCL. In some embodiments, the QCL may be based on one or more of: a Doppler shift, a Doppler spread, an average delay, a delay spread, a spatial receive (Rx) parameter, and/or one or more other parameters. In some embodiments, the QCL may be based on one or more of: 1) Type A QCL based on one or more of: a Doppler shift, a Doppler spread, an average delay, and a delay spread, 2) Type D QCL based on a spatial receive (Rx) parameter, 3) one or more other types (such as Type B, Type C and/or other) of QCL, and 4) other.

[0052] In a non-limiting example, the UE 102 may determine one or more parameters (such as Doppler shift, a Doppler spread, an average delay, a delay spread, a spatial receive (Rx) parameter and/or other) related to reception of a signal (such as the RSs, the DMRSs and/or other), and may decode/receive the PDSCH based at least partly on the determined one or more parameters.

[0053] In some embodiments, the UE 102 may receive and/or decode one or more PDCCHs. For a PDSCH scheduled by one of the PDCCHs, when a scheduling offset between the PDSCH and the corresponding PDCCH is less than a threshold, the UE 102 may determine that reception of the PDSCH is to be performed based on QCL between the PDSCH and: 1) one or more reference signals (RSs) configured by a Transmission Configuration Indication (TCI) state in the control signaling, or 2) demodulation reference signals (DMRSs) of the PDCCH, from the one or more decoded PDCCHs, that is associated with the CORESET of lowest CORESET-ID. In some embodiments, the one or more PDCCHs may be received in a latest slot in which multiple CORESETs are configured in an active bandwidth part (BWP). The multiple CORESETs may be configurable to include a CORESET of CORESET-ID equal to zero

(CORESET 0).

[0054] In some embodiments, when an active TCI state is not configured for a CORESET of CORESET-ID equal to zero (CORESET 0), or when the active TCI state for the CORESET 0 is reset, the UE 102 may determine that the reception of the PDSCH is to be performed based on QCL between the PDSCH and one or more of: a Synchronization Signal Block (SSB) of a random access procedure, and a CORESET 0 instance of the random access procedure. In some embodiments, the random access procedure may be related to one or more of: initial access, a handover, beam failure recovery, an ordered physical random access (PRACH) procedure, and/or other.

[0055] In some embodiments, when a TCI state is configured for

CORESET 0, the UE 102 may determine that the reception of the PDSCH is to be performed based on QCL between the PDSCH and channel state information reference signals (CSI-RSs) of a received Synchronization Signal Block (SSB).

[0056] In some embodiments, the UE 102 may determine that DMRSs of the PDSCH are to be QCLed with RS of a TCI state corresponding to a lowest CORESET-ID of the CORESETs configured for a latest slot when multiple CORESETs are configured in an active bandwidth part (BWP) after reception of a TCI indication for a CORESET configured for the active BWP.

[0057] In some embodiments, before reception of a TCI indication for a

CORESET, the UE 102 may determine that the reception of the PDSCH is to be performed based on QCL between DMRSs of the PDSCH and a Synchronization Signal Block (SSB) detected by the UE 102 during an initial access.

[0058] In some embodiments, the UE 102 may perform one or more of: refrain from performance of beam failure detection for CORESET 0 if a TCI state is not configured for CORESET 0; perform beam failure detection for CORESET 0 if the TCI state is configured for CORESET 0, wherein the beam failure detection is performed in accordance with QCL configured by the TCI state configured for CORESET 0; and/or other.

[0059] In some embodiments, after reception of a beam failure recovery response as part of a beam failure detection, the EE 102 may determine that PDSCHs scheduled by PDCCHs of any CORESET except CORESET 0 are to be received in accordance with QCL between the PDSCHs and a beam that is identified by the beam failure recovery response.

[0060] In some embodiments, after reception of a beam failure recovery response as part of a beam failure detection, the EE 102 may determine that one or more PDSCHs are to be received in accordance with QCL between the PDSCHs and beam that is identified by the beam failure recovery response if: 1) the scheduling offset is above the threshold, and 2) the PDSCHs are scheduled by PDCCHs with a radio network temporary identifier (RNTI) that is one of: a cell RNTI (C-RNTI), a modulation and coding scheme (MCS) cell RNTI (MCS- C-RNTI), a configured scheduling (CS) RNTI (CS-RNTI).

[0061] In some embodiments, the EE 102 may receive control signaling.

The EE 102 may receive and/or decode a PDCCH that schedules a PDSCH. If a scheduling offset between the PDSCH and the PDCCH is greater than or equal to a threshold, the EE 102 may determine that reception of the PDSCH is to be performed based on QCL that is: indicated in a TCI state in the control signaling, or DMRS of the PDCCH. If the scheduling offset between the PDSCH and the PDCCH is less than the threshold, and if CORESET 0 is within an active bandwidth part (BWP) and is configured for the EE 102 in a latest slot, the EE 102 may determine that reception of the PDSCH is to be performed based on QCL between the PDSCH and: 1) one or more RSs configured by a TCI state in the control signaling, or 2) DMRSs of the PDCCH, from the one or more decoded PDCCHs, that is associated with the CORESET of lowest CORESET- ID.

[0062] In some embodiments, the EE 102 may receive (from the gNB

105 and/or other component) control signaling that configures one or more CORESETs. In some embodiments, each of the CORESETs may be allocated for reception of one or more PDCCHs. In some embodiments, each of the CORESETs may be associated with a CORESET -ID. In some embodiments, the UE 102 may decode one or more PDCCHs received from the gNB 105. In some embodiments, for a PDSCH scheduled by one of the PDCCHs, the UE 102 may determine that reception of the PDSCH is to be performed based on QCL between the PDSCH and one or more RSs. In some embodiments, the RSs may be included in CORESET 0 if the control signaling configures CORESET 0. In some embodiments, the UE 102 may receive and/or decode the PDSCH in accordance with the determined QCL.

[0063] FIG. 5 illustrates examples of quasi-colocation (QCL) in accordance with some embodiments. FIG. 6 illustrates example operations in accordance with some embodiments. It should be noted that FIGs. 5-6 may illustrate some or all of the concepts and techniques described herein, in some cases. The scope of embodiments is not limited by FIGs. 5-6, however. For instance, embodiments are not limited by the name, number, type, size, ordering, arrangement or other aspect(s) of elements (such as devices, operations, time resources, frequency resources, messages and/or other elements) shown in FIGs. 5-6. Although some of the elements described below (and elsewhere herein) may be included in a 3GPP standard, NR standard, 5G standard and/or other standard, embodiments are not limited to usage of such elements that are included in standards.

[0064] Some embodiments may be related to a QCL assumption for

PDSCH reception. Some embodiments may be related to 3GPP standards and/or NR standards, such as Rel-l5, Rel-l6 WI and/or other. In 3GPP NR Rel-l5, it has been specified that the PDCCH used to schedule broadcast PDSCH, which we call it as broadcast PDCCH for short for the following section, can be transmitted in Search Space (SS) #0, which is connected to Control Resource Set (CORESET) #0. Each instance of SS0 is tied to a Synchronization Signal Block (SSB). The PDCCH in SS0 can be used to schedule PDSCH for broadcast transmission, where the Downlink Control Information (DCI) is associated with RA-RNTI, SI-RNTI or P-RNTI. The scheduling offset between the PDSCH and PDCCH could be 0 or 1 slot. The Demodulation Reference Signal (DMRS) of each instance of PDCCH and its scheduled PDSCH should be quasi-co-located (QCLed) with corresponding SSB. FIG. 5 illustrates a non-limiting example 500 for broadcast PDCCH transmission (embodiments are not limited to broadcast transmissions). In a non-limiting example, the signals 510, 512, 514 may be QCLed. In another non-limiting example, the signals 520, 522, 524 may be QCLed.

[0065] Further, it has been specified that when scheduling offset is below a threshold reported by UE capability, which could be 1 or 2 slots, UE 102 shall use a default beam to receive the PDSCH. The default beam is based on the reference signal in Transmission Configuration Indication (TCI) for a CORESET with lowest CORESET ID in latest slot when multiple CORESETs are configured in active Bandwidth Part (BWP). Then one issue is that UE 102 cannot receive broadcast PDSCH, if TCI is not configured for CORESET 0, since the scheduling offset for broadcast PDSCH could be smaller than UE reported threshold. Some embodiments may be related to methods for UE QCL assumption for PDSCH including: PDSCH QCL assumption when TCI is not configured for CORESET 0, PDSCH QCL assumption when TCI is configured for CORESET 0, and/or other.

[0066] Some embodiments may be related to QCL assumption for

PDSCH when scheduling offset is below a threshold, which can also be applied to aperiodic Channel State Information Reference Signal (CSI-RS). Note that the TCI indication for CORESET 0 indicates that UE 102 receives a MAC CE for CORESET 0 TCI indication, where the TCI-statelD field could be a TCI state ID or an SSB index. The QCL in this IDF denotes QCL with all parameters defined, which means QCL typeA+D. The QCL types may be assumed as follows (although the scope of embodiments is not limited in this respect): 'QCL- TypeA': (Doppler shift, Doppler spread, average delay, delay spread};‘QCL- TypeB': (Doppler shift, Doppler spread}; 'QCL-TypeC: (Doppler shift, average delay}; 'QCL-TypeD': (Spatial Rx parameter}. In some embodiments,

CORESET 0 may should be taken into account to decide UE’s default PDSCH beam. When scheduling offset for PDSCH is less than a threshold, PDSCH should be QCLed with reference signal in TCI state or DMRS of PDCCH for the CORESET with lowest CORESET-ID in latest slot when multiple CORESETS are configured in active BWP including CORESET 0, where all the CORESTs should be the CORESET with a monitoring Search Space (SS).

[0067] In some embodiments, when active TCI state for CORESET 0 is not configured or is reset, only the SSB and the SS/CORESET 0 instance that UE 102 identified during the latest random access procedure can be considered to determine the PDSCH QCL, where the random access procedure can indicate the initial access procedure and/or handover procedure, and random access procedure may or may not include beam failure recovery procedure or PDCCH ordered PRACH procedure.

[0068] In some embodiments, when an active TCI state for CORESET 0 is configured, the instance of the SS/CORESET 0 to determine the default PDSCH QCL can be determined by the SSB which is QCLed with CSI-RS. Thus UE 102 shall monitor the SS0/CORESET0 that is tied to the SSB, and the corresponding instance for SS0/CORESET0 should be included to determine PDSCH default QCL information.

[0069] In some embodiments, when TCI state for CORESET 0 is configured, all instances of SS/CORESET 0 should be taken into account to determine the default QCL assumption for PDSCH. When determining the default beam for PDSCH, UE shall assume all instances of SS0/CORESET0 is QCLed with RS in the indicated TCI state or the SSB identified in latest random access procedure.

[0070] FIG. 6 illustrates a non-limiting example 600 for PDSCH QCL assumption with regard to CORESET 0. The method 600 begins with the decision diamond 605, which asks if a scheduling offset for PDSCH is less than a threshold that the UE 102 reported. If the answer to 605 is“no” (as indicated by 610), then the method 600 continues to 612, wherein the PDSCH is QCLed with the indicated TCI state in DCI or DMRS of scheduling PDDCH. If the answer to 605 is“yes” (as indicated by 620), then the method 600 continues to the decision diamond 622. The decision diamond 622 asks if CORESET 0 is within active BWP and one of the CORESETs in the latest slot in which one or more CORESETs within the active BWP of the serving cell are configured for the UE 102.

[0071] If the answer to the decision diamond 622 is“no” (as indicated by

630), the method 600 continues to 632, wherein the PDSCH is QCLed with RS in TCI state for a CORESET with lowest CORESET-ID in latest slot when multiple CORESETs are configured in active BWP. If the answer to the decision diamond 622 is“yes” (as indicated by 640), the method 600 continues to the decision diamond 650.

[0072] The decision diamond 650 asks if active TCI is configured for

CORESET 0. If the answer to the decision diamond 650 is“no” (as indicated by 660), the method 600 continues to 662, wherein a CORESET 0 instance is based on SSB that is identified in latest random access procedure. If the answer to the decision diamond 650 is“yes” (as indicated by 670), the method 600 continues to 672, wherein the CORESET 0 instance is based on SSB that is QCLed with CSI-RS in TCI state for CORESET 0.

[0073] The method 600 continues to 680 after either of 662 or 672. At

680, the PDSCH is QCLed with RS in TCI state or DMRS of PDCCH for a CORESET with lowest CORESET-ID in latest slot when multiple CORESETs are configured in active BWP including CORESET 0 instance.

[0074] In some embodiments, when scheduling offset for PDSCH is below a threshold, the DMRS of PDSCH should be QCLed with RS in TCI state in lowest CORESET ID in latest slot when multiple CORESETs are configured in active BWP after TCI indication for a CORESET in active BWP. Before TCI state indication of a CORESET, UE 102 shall assume DMRS of PDSCH should be QCLed with the SSB it identified during initial access.

[0075] In some embodiments, the UE 102 shall expect the gNB 105 to indicate the TCI state for CORESET 0 after RRC connection. Then after RRC connection, the default PDSCH beam could be based on the TCI state in lowest CORESET ID in latest slot, and before RRC connection, PDSCH is QCLed with the SSB it identified during initial access.

[0076] In some embodiments, if TCI state for CORESET 0 is not configured, the UE 102 shall not perform beam failure detection for CORESET 0; otherwise, UE shall perform beam failure detection for CORESET 0 based on the QCL assumption configured in the TCI state. Further after receiving the beam failure recovery response, EE shall assume the PDSCH scheduled by all CORESETs except CORESET 0 should be QCLed with the newly identified beam during beam failure recovery procedure. Alternatively, after receiving beam failure recovery response, EE shall assume that PDSCH scheduled by PDCCH with C-RNTI or MCS-C-RNTI or CS-RNTI should be QCLed with the newly identified beam when scheduling offset is above threshold.

[0077] In some embodiments, the CSI-RS configured in CORESETO can be QCLed with SSB with QCL-typeA and/or QCL-typeD. The other CSI-RS and SSB can be QCLed with QCL typeC and/or QCL-typeD.

[0078] In some embodiments, the EE 102 may perform one or more of: determine QCL for a PDSCH when CORESET 0 is configured in active BWP; determine the CORESET(s) for beam failure detection; determine the QCL for CSI-RS configured for CORESET 0. In some embodiments, when scheduling offset for PDSCH is less than a threshold, PDSCH should be QCLed with reference signal in TCI state or DMRS of PDCCH for the CORESET with lowest CORESET-ID in latest slot when multiple CORESETS are configured in active BWP including CORESET 0. In some embodiments, the CORESETs may be used to determine PDSCH QCL be tied to a Search Space (SS) that the EE 102 is monitoring. In some embodiments, when active TCI state for CORESET 0 is not configured or is reset, only the Synchronization Signal Block (SSB) and the SSO/CORESET 0 instance that EE 102 identified during the latest random access procedure can be considered to determine the PDSCH QCL.

[0079] In some embodiments, the random access procedure can at least indicate the initial access procedure and/or handover procedure. In some embodiments, the random access procedure may include beam failure recovery procedure. In some embodiments, the random access procedure may include PDCCH ordered PRACH procedure.

[0080] In some embodiments, when an active TCI state for CORESET 0 is configured, the instance of the SSO/CORESET 0 to determine the default PDSCH QCL can be determined by the SSB which is QCLed with CSI-RS. In some embodiments, when TCI state for CORESET 0 is configured, all instances of S S/CORESET 0 should be taken into account to determine the default QCL assumption for PDSCH. In some embodiments, when determining the default beam for PDSCH, the UE 102 shall assume all instances of SS0/CORESET0 is QCLed with RS in the indicated TCI state or the SSB identified in latest random access procedure. In some embodiments, when scheduling offset for PDSCH is below a threshold, the DMRS of PDSCH should be QCLed with RS in TCI state in lowest CORESET ID in latest slot when multiple CORESETs are configured in active BWP after TCI indication for a CORESET in active BWP.

[0081] In some embodiments, before TCI state indication of a

CORESET, the UE 102 shall assume DMRS of PDSCH should be QCLed with the SSB it identified during initial access. In some embodiments, if TCI state for CORESET 0 is not configured, the UE 102 shall not perform beam failure detection for CORESET 0; otherwise, the UE 102 shall perform beam failure detection for CORESET 0 based on the QCL assumption configured in the TCI state. In some embodiments, after receiving the beam failure recovery response, the UE 102 shall assume the PDSCH scheduled by all CORESETs except CORESET 0 should be QCLed with the newly identified beam during beam failure recovery procedure. In some embodiments, after receiving beam failure recovery response, the UE 102 shall assume that PDSCH scheduled by PDCCH with C-RNTI or MCS-C-RNTI or CS-RNTI should be QCLed with the newly identified beam when scheduling offset is above threshold. In some

embodiments, the CSI-RS configured in CORESETO can be QCLed with SSB with QCL-typeA and/or QCL-typeD.

[0082] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to:

decode, from a Next Generation Node-B (gNB), control signaling that configures one or more control resource sets (CORESETs), wherein each of the CORESETs is allocated for reception of one or more physical downlink control channels (PDCCHs), wherein each of the CORESETs is associated with a CORESET identifier (CORESET-ID);

decode one or more PDCCHs received from the gNB;

for a physical downlink shared channel (PDSCH) scheduled by one of the PDCCHs, when a scheduling offset between the PDSCH and the

corresponding PDCCH is less than a threshold, determine that reception of the PDSCH is to be performed based on quasi-colocation (QCL) between the PDSCH and:

one or more reference signals (RSs) configured by a Transmission Configuration Indication (TCI) state in the control signaling, or

demodulation reference signals (DMRSs) of the PDCCH, from the one or more decoded PDCCHs, that is associated with the CORESET of lowest CORESET-ID; and

decode the PDSCH in accordance with the determined QCL,

wherein the memory is configured to store at least a portion of the control signaling.

2. The apparatus according to claim 1, wherein the one or more PDCCHs are received in a latest slot in which multiple CORESETs are configured in an active bandwidth part (BWP), the multiple CORESETs configurable to include a CORESET of CORESET-ID equal to zero (CORESET 0).

3. The apparatus according to claim 1, wherein the QCL is based on one or more of:

a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial receive (Rx) parameter.

4. The apparatus according to claim 1, the processing circuitry further configured to:

determine one or more parameters related to reception of the RSs or the DMRSs, wherein the one or more parameters are included in: a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial receive (Rx) parameter; and

decode the PDSCH based at least partly on the determined one or more parameters.

5. The apparatus according to claim 1, the processing circuitry further configured to:

when an active TCI state is not configured for a CORESET of

CORESET-ID equal to zero (CORESET 0), or when the active TCI state for the CORESET 0 is reset:

determine that the reception of the PDSCH is to be performed based on quasi-colocation (QCL) between the PDSCH and one or more of:

a Synchronization Signal Block (SSB) of a random access procedure, and

a CORESET 0 instance of the random access procedure.

6. The apparatus according to claim 1, wherein the random access procedure is related to one or more of:

initial access,

a handover,

beam failure recovery, and

an ordered physical random access (PRACH) procedure.

7. The apparatus according to claim 1, the processing circuitry further configured to:

when a TCI state is configured for a CORESET of CORESET-ID equal to zero (CORESET 0):

determine that the reception of the PDSCH is to be performed based on QCL between the PDSCH and channel state information reference signals (CSI-RSs) of a received Synchronization Signal Block (SSB).

8. The apparatus according to claim 1, the processing circuitry further configured to:

determine that DMRSs of the PDSCH are to be QCLed with RS of a TCI state corresponding to a lowest CORESET-ID of the CORESETs configured for a latest slot when multiple CORESETs are configured in an active bandwidth part (BWP) after reception of a TCI indication for a CORESET configured for the active BWP.

9. The apparatus according to claim 1, the processing circuitry further configured to:

before reception of a TCI indication for a CORESET, determine that the reception of the PDSCH is to be performed based on QCL between DMRSs of the PDSCH and a Synchronization Signal Block (SSB) detected by the UE during an initial access.

10. The apparatus according to claim 1, the processing circuitry further configured to:

refrain from performance of beam failure detection for a CORESET of CORESET-ID equal to zero (CORESET 0) if a TCI state is not configured for CORESET 0; and

perform beam failure detection for CORESET 0 if the TCI state is configured for CORESET 0, wherein the beam failure detection is performed in accordance with QCL configured by the TCI state configured for CORESET 0.

11. The apparatus according to claim 1, the processing circuitry further configured to:

after reception of a beam failure recovery response as part of a beam failure detection, determine that PDSCHs scheduled by PDCCHs of any CORESET except CORESET 0 are to be received in accordance with QCL between the PDSCHs and a beam that is identified by the beam failure recovery response.

12. The apparatus according to claim 1, the processing circuitry further configured to:

after reception of a beam failure recovery response as part of a beam failure detection, determine that one or more PDSCHs are to be received in accordance with QCL between the PDSCHs and beam that is identified by the beam failure recovery response if:

the scheduling offset is above the threshold, and the PDSCHs are scheduled by PDCCHs with a radio network temporary identifier (RNTI) that is one of: a cell RNTI (C-RNTI), a modulation and coding scheme (MCS) cell RNTI (MCS-C-RNTI), a configured scheduling (CS) RNTI (CS-RNTI).

13. The apparatus according to claim 1, wherein each of the CORESETs is mapped to a search space (SS) of time resources and frequency resources.

14. The apparatus of claim 1, wherein:

the processing circuitry includes a baseband processor to decode the control signaling, and

the apparatus further comprises a transceiver to receive the control signaling.

15. A computer-readable storage medium that stores instructions for execution of operations by processing circuitry of a User Equipment (UE), the operations to configure the processing circuitry to:

decode control signaling; decode a physical downlink control channel (PDCCH) that schedules a physical downlink shared channel (PDSCH);

if a scheduling offset between the PDSCH and the PDCCH is greater than or equal to a threshold, determine that reception of the PDSCH is to be performed based on quasi-colocation (QCL) that is:

indicated in a Transmission Configuration Indication (TCI) state in the control signaling, or

demodulation reference signals (DMRSs) of the PDCCH.

16. The computer-readable storage medium according to claim 15, the operations to further configure the processing circuitry to:

if the scheduling offset between the PDSCH and the PDCCH is less than the threshold,

if a control resource set (CORESET) of CORESET identifier (CORESET ID) equal to zero (CORESET 0) is within an active bandwidth part (BWP) and is configured for the UE in a latest slot:

determine that reception of the PDSCH is to be performed based on QCL between the PDSCH and:

one or more reference signals (RSs) configured by a TCI state in the control signaling, or

DMRSs of the PDCCH, from the one or more decoded PDCCHs, that is associated with the CORESET of lowest CORESET-ID.

17. An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to:

decode, from a Next Generation Node-B (gNB), control signaling that configures one or more control resource sets (CORESETs), wherein each of the CORESETs is allocated for reception of one or more physical downlink control channels (PDCCHs), wherein each of the CORESETs is associated with a CORESET identifier (CORESET-ID);

decode one or more PDCCHs received from the gNB;

for a physical downlink shared channel (PDSCH) scheduled by one of the PDCCHs, determine that reception of the PDSCH is to be performed based on quasi-colocation (QCL) between the PDSCH and one or more reference signals (RSs),

wherein the RSs are included in a CORESET of CORESET ID equal to zero (CORESET 0) if the control signaling configures CORESET 0; and

decode the PDSCH in accordance with the determined QCL,

wherein the memory is configured to store at least a portion of the control signaling.

18. The apparatus according to claim 17, wherein the QCL is based on one or more of:

Type A QCL based on one or more of: a Doppler shift, a Doppler spread, an average delay, and a delay spread, and

Type D QCL based on a spatial receive (Rx) parameter.