EP3871357A1 - Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch) - Google Patents
Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch)Info
- Publication number
- EP3871357A1 EP3871357A1 EP19876208.0A EP19876208A EP3871357A1 EP 3871357 A1 EP3871357 A1 EP 3871357A1 EP 19876208 A EP19876208 A EP 19876208A EP 3871357 A1 EP3871357 A1 EP 3871357A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- coreset
- pdsch
- qcl
- reception
- coresets
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
- H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
Definitions
- 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.
- 3 GPP Third Generation Partnership Project
- 3GPP LTE Long Term Evolution
- 5G Fifth Generation
- NR New Radio
- 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.
- PDCCHs physical downlink control channels
- PDSCHs physical downlink shared channels
- QCL quasi -colocation
- 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.
- FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments
- FIG. 3 illustrates an exemplary communication circuitry according to some aspects
- FIG. 4 illustrates the operation of a method of communication in accordance with some embodiments
- FIG. 5 illustrates examples of quasi-colocation (QCL) in accordance with some embodiments.
- FIG. 6 illustrates example operations in accordance with some embodiments.
- 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.
- the network 100 may be a Third Generation Partnership Project (3 GPP) network.
- the network 150 may be a 3GPP network, a new radio (NR) network and/or Fifth Generation (5G) network.
- NR new radio
- 5G Fifth Generation
- 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.
- the network 100 may comprise a radio access network (RAN)
- RAN radio access network
- 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.
- E- ETTRAN evolved universal terrestrial radio access network
- the core network 120 may include a mobility management entity
- 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.
- UE User Equipment
- 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.
- references herein to an eNB 104 or to a gNB 105 are not limiting.
- one or more operations, methods and/or techniques 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.
- 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.
- 5G Fifth Generation
- 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.
- EIEs 102, the eNB 104 and/or gNB 105 may be configured to communicate Orthogonal Frequency Division
- OFDM Orthogonal Frequency Division Multiplexing
- OFDMA Orthogonal Frequency Division Multiple Access
- 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.
- NG-RAN next generation RAN
- 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.
- the network 150 may include the MME
- 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.
- Embodiments are not limited to the number or type of
- Embodiments are also not limited to the connectivity of components shown in FIG. 1B.
- 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.
- ASIC Application Specific Integrated Circuit
- the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
- 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.
- 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.
- AP access point
- STA station
- 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.
- cloud computing software as a service
- SaaS software as a service
- the machine 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.
- the storage device 216 may include a machine readable medium
- 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.
- 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.
- the machine readable medium may be or may include a non-transitory computer-readable storage medium.
- the machine readable medium may be or may include a computer-readable storage medium.
- 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
- machine readable media may include non-transitory machine readable media.
- machine readable media may include machine readable media that is not a transitory propagating signal.
- 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.
- 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.
- SIMO single-input multiple-output
- MIMO multiple-input multiple-output
- MISO multiple-input single-output
- 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.
- FIG. 3 illustrates an exemplary communication circuitry according to some aspects.
- 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.
- PHY physical layer
- 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.
- 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.
- processing circuitry may perform one or more operations described herein and/or other operation(s).
- 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).
- 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).
- 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).
- 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.
- the functional elements may refer to one or more processes operating on one or more processing elements.
- 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).
- 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.
- 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.
- 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.
- CORESET- ID CORESET identifier
- 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.
- 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.
- 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.
- 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.
- Discussion of various operations, techniques and/or concepts regarding one method described herein 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.
- AP Wi-Fi access point
- STA station
- an apparatus of a device 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.
- such an element may be generated, encoded or otherwise processed by processing circuitry for transmission by a transceiver or other component cases.
- such an element may be received by a transceiver or other component, and may be decoded, detected or otherwise processed by processing circuitry.
- the processing circuitry and the transceiver may be included in a same apparatus.
- the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.
- 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
- 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.
- 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.
- 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.
- the control signaling may include multiple messages, multiple instances of signaling, multiple types of signaling, multiple elements and/or other.
- the UE 102 may receive, from the gNB
- control signaling that configures one or more control resource sets (CORESETs).
- the control signaling may include one or more additional elements, 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.
- 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.
- 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.
- 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.
- the UE 102 may receive one or more PDCCHs.
- the UE 102 may determine quasi-colocation (QCL) for a physical downlink shared channel (PDSCH).
- the UE 102 may receive the PDSCH.
- QCL quasi-colocation
- the UE 102 may receive one or more
- the UE 102 may receive one or more
- a PDCCH may schedule a PDSCH.
- one or more of the received PDCCHs may schedule one or more PDSCHs.
- the UE 102 may receive the PDSCH in accordance with the determined QCL.
- 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.
- 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.
- 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.
- 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
- 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.
- RSs reference signals
- TCI Transmission Configuration Indication
- DMRSs demodulation reference signals
- 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
- 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.
- SSB Synchronization Signal Block
- 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.
- 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).
- CSI-RSs channel state information reference signals
- SSB Synchronization Signal Block
- 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.
- BWP active bandwidth part
- 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.
- SSB Synchronization Signal Block
- 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.
- 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.
- 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).
- RNTI radio network temporary identifier
- 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.
- 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.
- BWP active bandwidth part
- the EE 102 may receive (from the gNB
- each of the CORESETs may be allocated for reception of one or more PDCCHs.
- each of the CORESETs may be associated with a CORESET -ID.
- the UE 102 may decode one or more PDCCHs received from the gNB 105.
- 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.
- the RSs may be included in CORESET 0 if the control signaling configures CORESET 0.
- the UE 102 may receive and/or decode the PDSCH in accordance with the determined QCL.
- FIG. 5 illustrates examples of quasi-colocation (QCL) in accordance with some embodiments.
- FIG. 6 illustrates example operations in accordance with some embodiments.
- 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.
- elements described below 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.
- Some embodiments may be related to a QCL assumption for
- 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).
- SS0 Search Space
- SSB Synchronization Signal Block
- 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.
- DCI Downlink Control Information
- 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).
- the signals 510, 512, 514 may be QCLed.
- the signals 520, 522, 524 may be QCLed.
- UE 102 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).
- TCI Transmission Configuration Indication
- BWP active Bandwidth Part
- 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.
- Some embodiments may be related to QCL assumption for
- 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 ⁇ .
- 'QCL- TypeA' Doppler shift, Doppler spread, average delay, delay spread ⁇
- QL-TypeB' Doppler shift, Doppler spread ⁇
- 'QCL-TypeC Doppler shift, average delay ⁇
- 'QCL-TypeD' spatial Rx parameter ⁇ .
- CORESET 0 may should be taken into account to decide UE’s default PDSCH beam.
- 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).
- SS Monitoring Search Space
- 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.
- 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.
- 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.
- all instances of SS/CORESET 0 should be taken into account to determine the default QCL assumption 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.
- 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.
- 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.
- the decision diamond 650 asks if active TCI is configured for
- 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.
- the method 600 continues to 680 after either of 662 or 672. At
- 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.
- the DMRS of PDSCH when scheduling offset for PDSCH is below a threshold, 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.
- UE 102 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.
- 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.
- the UE 102 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.
- 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.
- 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.
- 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.
- the CORESETs may be used to determine PDSCH QCL be tied to a Search Space (SS) that the EE 102 is monitoring.
- SS Search Space
- the random access procedure can at least indicate the initial access procedure and/or handover procedure.
- the random access procedure may include beam failure recovery procedure.
- the random access procedure may include PDCCH ordered PRACH procedure.
- 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.
- TCI state for CORESET 0 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.
- the UE 102 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.
- the DMRS of PDSCH when scheduling offset for PDSCH is below a threshold, 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.
- the UE 102 shall assume DMRS of PDSCH should be QCLed with the SSB it identified during initial access.
- the UE 102 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.
- the UE 102 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.
- the UE 102 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.
- the CSI-RS configured in CORESETO can be QCLed with SSB with QCL-typeA and/or QCL-typeD.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862749959P | 2018-10-24 | 2018-10-24 | |
PCT/US2019/057426 WO2020086572A1 (en) | 2018-10-24 | 2019-10-22 | Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch) |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3871357A1 true EP3871357A1 (en) | 2021-09-01 |
EP3871357A4 EP3871357A4 (en) | 2022-07-13 |
Family
ID=70330531
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19876208.0A Withdrawn EP3871357A4 (en) | 2018-10-24 | 2019-10-22 | Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch) |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3871357A4 (en) |
WO (1) | WO2020086572A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114070527B (en) * | 2020-08-07 | 2023-07-14 | 大唐移动通信设备有限公司 | Information transmission method, network side equipment, terminal and storage medium |
KR20230027096A (en) * | 2020-09-30 | 2023-02-27 | 지티이 코포레이션 | Acquisition of pseudo colocation information using transport configuration indicators |
CN114726409A (en) * | 2021-01-04 | 2022-07-08 | 中国移动通信有限公司研究院 | Configuration method, base station, terminal and medium for multi-beam transmission |
WO2024073945A1 (en) * | 2022-12-15 | 2024-04-11 | Lenovo (Beijing) Limited | Method and apparatus of beam determination |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9197387B2 (en) * | 2011-08-15 | 2015-11-24 | Google Technology Holdings LLC | Method and apparatus for control channel transmission and reception |
WO2017052284A1 (en) * | 2015-09-24 | 2017-03-30 | Lg Electronics Inc. | Method and apparatus for performing a discontinuous reception |
US10652876B2 (en) * | 2016-03-16 | 2020-05-12 | Lg Electronics Inc. | Method for transmitting and receiving control information in wireless communication system, and apparatus therefor |
-
2019
- 2019-10-22 EP EP19876208.0A patent/EP3871357A4/en not_active Withdrawn
- 2019-10-22 WO PCT/US2019/057426 patent/WO2020086572A1/en unknown
Also Published As
Publication number | Publication date |
---|---|
WO2020086572A1 (en) | 2020-04-30 |
EP3871357A4 (en) | 2022-07-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11818672B2 (en) | In-device coordination of sidelink over LTE and NR PC5 interfaces | |
US12028822B2 (en) | Signaling of timing advance (TA) offsets in IAB networks | |
US11825525B2 (en) | Allocation of resources for preamble and payload of messages in a 2-step random access (RA) procedure in new radio (NR) systems | |
EP3861668A1 (en) | Pdcch monitoring span and dci format set determination | |
US11533695B2 (en) | Synchronization for sidelink based on prioritization of synchronization signals | |
US12041587B2 (en) | Signaling of not available resources for central coordination in IAB networks | |
WO2020086572A1 (en) | Determination of quasi-colocation (qcl) for reception of a physical downlink shared channel (pdsch) | |
US12108312B2 (en) | Sidelink communication under control of LTE UU interface or NR interface | |
US9706578B2 (en) | Scheduling signaling transmission method and device | |
KR20230110629A (en) | Method and apparatus for identification of RedCap UEs | |
EP3166354B1 (en) | Coverage enhancement mode change for enhanced coverage user equipment | |
KR102493285B1 (en) | Configuration of Measurement Gaps in Novel Radio (NR)-NR Dual Access (NR-NR DC) Arrangements | |
EP3834357B1 (en) | Generation of dm-rs for sidelink based on location of ue | |
US11950182B2 (en) | Negotiation of a PC5 rat for a V2X service | |
WO2020028774A1 (en) | Adaptive allocation of csi-rs for rlm | |
WO2024149553A1 (en) | Resource release enhancement in network conditional handover |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20201223 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20220615 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 72/12 20090101ALI20220610BHEP Ipc: H04B 17/373 20150101ALI20220610BHEP Ipc: H04L 5/00 20060101AFI20220610BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20230117 |