Techniques for reporting dynamic downlink and uplink pseudo-collocation relationships

Abstract

Techniques for dynamic downlink and uplink quasi-co-location (QCL) relationship reporting are disclosed. In one example, a base station may determine to change a QCL reporting state for a user equipment (UE), where the QCL reporting state is one of an active QCL reporting state or a limited QCL reporting state. The base station may also generate an indication to indicate the change in the QCL reporting state to the UE in response to determining the change in the QCL reporting state. The base station may also transmit the indication to the UE in response to generating the indication.

Description

Technical Field

[0001] Cross - reference to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 037,249, titled "TECHNIQUES FOR DYNAMIC DOWNLINK AND UPLINK QUASI CO - LOCATION RELATIONSHIP REPORTING," filed on June 10, 2020, and U.S. Patent Application No. 17 / 339,292, titled "TECHNIQUES FOR DYNAMIC DOWNLINK AND UPLINK QUASI CO - LOCATION RELATIONSHIP REPORTING," filed on June 4, 2021, which are hereby incorporated by reference in their entirety.

[0002]

[0002] Aspects of the present disclosure generally relate to communication systems, and more particularly, to techniques for dynamic downlink and uplink quasi co - location (QCL) relationship reporting.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technology that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, and time division synchronous code division multiple access (TD - SCDMA) systems.

[0004]

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An exemplary telecommunications standard is fifth-generation (5G) new radio (NR) technology. 5G NR technology is part of the ongoing mobile broadband development issued by the Third Generation Partnership Project (3GPP®) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR technology includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-high reliability low-latency communications (URLLC). [Overview of the Initiative]

[0005]

[0005] Below, a simplified overview of one or more embodiments is provided to give a basic understanding of such embodiments. This overview is not a comprehensive overview of all intended embodiments, nor does it identify the main or important elements of all embodiments, nor does it define the scope of any or all embodiments. The sole purpose of this overview is to present some concepts of one or more embodiments in a simplified form as an introduction to the more detailed explanations that will be presented later.

[0006]

[0006] As a result of using high-frequency communications, slot durations may be shorter. Shorter slot durations can lead to more frequent pseudo-collocation (QCL) relationship changes, which can result in additional overhead in communications. This disclosure provides systems, apparatus, and methods for reducing overhead in these situations by enabling a base station to limit QCL reporting by user equipment (UE).

[0007]

[0007] In one embodiment, a method for wireless communication by a base station is provided. The method may include deciding to change the pseudo-collocation (QCL) reporting state of a user device (UE), the QCL reporting state being either an active QCL reporting state or a restricted QCL reporting state. The method may also include generating an indication to show the UE the change in the QCL reporting state in response to the decision to change the QCL reporting state. The method may also include transmitting the indication to the UE in response to generating the indication.

[0008]

[0008] In another embodiment, a method for wireless communication by a user device (UE) is provided. This method may include receiving an indication from a base station to change the pseudo-collocation (QCL) reporting state of the UE. This method may also include setting the QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on the indication. This method may also include transmitting a QCL report to the base station in response to setting the QCL reporting state to an active QCL reporting state. This method may also include restricting the transmission of a QCL report to the base station in response to setting the QCL reporting state to a restricted QCL reporting state.

[0009]

[0009] In another embodiment, an apparatus and a computer-readable medium for carrying out the operation of the method are also disclosed.

[0010]

[0010] To achieve the above-mentioned and related objectives, one or more embodiments shall have features that are fully described below and, in particular, pointed out in the claims. The following description and accompanying drawings shall describe in detail some exemplary features of one or more embodiments. However, these features shall represent only a few of the various ways in which the principles of various embodiments may be employed, and this description shall include all such embodiments and their equivalents.

[0011]

[0011] The disclosed aspects are described below with reference to the accompanying drawings provided to illustrate, not limit, the disclosed aspects, where similar names refer to similar elements. [Brief explanation of the drawing]

[0012] [Figure 1]

[0012] A schematic diagram of an exemplary wireless communication system and access network according to an aspect of the present disclosure. [Figure 2]

[0013] A flowchart illustrating an exemplary method of wireless communication using the base station shown in Figure 1, according to an aspect of this disclosure. [Figure 3]

[0014] A schematic diagram of an example of a base station shown in Figure 1, according to the embodiments of this disclosure. [Figure 4]

[0015] A flowchart illustrating an exemplary method of wireless communication using the user equipment (UE) shown in Figure 1, according to an aspect of this disclosure. [Figure 5]

[0016] A schematic diagram of an example of the UE in Figure 1 according to the aspects of this disclosure. [Modes for carrying out the invention]

[0013]

[0017] The detailed descriptions provided below, along with the accompanying drawings, are intended to describe various configurations and are not intended to represent only the configurations in which the concepts described herein can be put into practice. The detailed descriptions include specific details to provide a complete understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be put into practice without these specific details. In some cases, well-known structures and components are shown in block diagrams to avoid obscuring such concepts.

[0014]

[0018] Next, several embodiments of telecommunications systems will be presented with respect to various devices and methods. These devices and methods will be described in the following detailed descriptions and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented by hardware or software depends on the specific applications and design constraints imposed on the system as a whole.

[0015]

[0019] For example, an element, or any part of an element, or any combination of elements, may be implemented as a “processing system” comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other appropriate hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of the names such as software, firmware, middleware, microcode, hardware description language, etc.

[0016]

[0020] Accordingly, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, these functions may be stored on one or more instructions or codes on a computer-readable medium, or may be encoded as such instructions or codes. The computer-readable medium includes computer storage media. The storage medium may be any available medium that can be accessed by a computer. Such computer-readable media may include, but not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM®), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the computer-readable media of the types described above, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0017]

[0021] As carrier frequencies increase for fifth-generation (5G) new radio (NR) technology (for example, frequency range 4 (FR4) covers 52.6–114.25 GHz), larger antenna arrays may be used on the user equipment (UE) side. However, these large arrays need to be controlled by multiple radio frequency integrated circuits (RFICs) and consume a lot of power, which can lead to high thermal overhead. Therefore, it is desirable to view antenna elements as degrees of freedom that can be dynamically operated over time.

[0018]

[0022] In 5G-NR, a pseudo-collocation (QCL) relationship (or configuration) may exist between one or more signals. In a QCL relationship, the properties of a first channel when a symbol on one antenna port is communicated can be inferred from a second channel when a symbol on another antenna port is communicated. This means that in a QCL relationship, there is a relationship between the antenna ports (and corresponding signaling beams) of each transmit. For example, in a QCL relationship, transmits sharing the same antenna port experience the same channel. Sometimes, transmits from different antenna ports experience a radio channel that shares some common characteristics (this is captured by the QCL relationship). As another example, a physical downlink shared channel (PDSCH) and a DL reference signal (RS) may have a QCL relationship in the sense that the beam properties of one channel can be derived from the other channel. However, this means that the beam weights used for the PDSCH do not need to be directly derived from DL RS measurements, but simply need to be based on or derived from DL RS measurements.

[0019]

[0023] In 3GPP 5G-NR DL transmission, there are typically four QCL type relationships: QCL-Type A, QCL-Type B, QCL-Type C, and QCL-Type D. In a QCL-Type A relationship, two or more ports (or channels) share the same settings related to Doppler shift, Doppler spread, mean delay, and delay spread. In a QCL-Type B relationship, two or more ports (or channels) share the same settings related to Doppler shift and Doppler spread. In a QCL-Type C relationship, two or more ports (or channels) share the same settings related to Doppler shift and mean delay. In a QCL-Type D relationship, two or more ports (or channels) share the same settings related to spatial receiver parameters.

[0020]

[0024] Typically, four QCL type relationships may potentially be used for DL transmission. However, QCL-Type A, B, and C are typically for Frequency Range 1 (FR1), and QCL-Type A, QCL-Type C, and QCL-Type D are typically for Frequency Range 2 (FR2). Furthermore, the QCL relationship is typically restricted to QCL-Type D for uplink (UL) transmission.

[0021]

[0025] In Frequency Range 4 (FR4), the bandwidth (BW) and subcarrier spacing (e.g., subcarrier spacing (SCS) of 240 - 960 kHz and occupied BW of 400 - 1600 MHz) can be significantly higher than those in FR2 (e.g., 120 kHz and 200 MHz / component carrier (CC) occupied BW at 28 GHz), which can lead to shorter slot durations. In FR4, since the subarray used on the UE side can change dynamically (e.g., symbol-by-symbol or over multiple slots), the QCL-Type A, B, and C relationships based on delay and Doppler settings may change more frequently than the QCL-Type D relationship because the beamforming delay / Doppler spread may change with the subarray change. As shown, the QCL-Type D relationship corresponds to "spatial receiver parameters", which means that only the spatial relationships corresponding to BW changes or beam weights (e.g., wide beam and narrow beam in the Physical X Control Channel (PXCCH) and Physical X Shared Channel (PXSCH), where X indicates UL or DL) can be considered.

[0022]

[0026] Furthermore, more frequent QCL relationship changes (e.g., QCL Type A, B, or C) can result in higher overhead. QCL relationships, if configured, are established between one or two DL RSs and the demodulated RS (DM-RS) port of the PDSCH using the higher-layer parameters qclType-1 and qclType-2. The QCL types of two DL RSs are not the same, regardless of whether the QCL mapping is to the same DL RS or to different DL RSs. Therefore, a UE may be provided with two different RSs: one for QCL-Type A, B, or C, and another for QCL-Type D. When a beam change occurs at the base station (e.g., a beam weight change due to switching symbols to point from one direction to another) (e.g., a P2 beam sweep), delay or Doppler spread may change (from the UE's perspective), so a fixed RS provided for QCL-Type A may not be sufficient to associate with the DM-RS on the PDSCH. In other words, in some frequency ranges (e.g., FR4), summaries (e.g., QCL reports) or additional reports (e.g., QCL reports) may be required by the UE due to shorter symbol durations and dynamically changing antenna elements, or because the antenna elements change frequently.

[0023]

[0027] Therefore, aspects of the present disclosure provide a more dynamic update of the QCL relationship for both DL and UL. In one example, the base station removes or reduces the RSs associated with QCL-Type A, B, or C, or restricts these RSs to certain situations. In one example, the DM-RS of PXCCH or PXSCH can be removed or reduced. In another example, the base station can signal to the UE which (or both) of the DM-RS of PXCCH or the DM-RS of PXSCH is removed. In other words, the base station can dynamically reduce the overhead from the QCL mapping report due to symbol changes. For example, the base station may determine that the QCL report is burdensome to the UE, or the UE may indicate to the base station that the QCL report is burdensome. Therefore, the base station can limit the use of the QCL report over several slots or over certain slots.

[0024]

[0028] In one aspect, the base station can control the reporting for each symbol, each slot, or multiple slots. Further, the control of the reporting by the base station can be configured by higher layer parameters related to the periodicity and degree of beam reporting.

[0025]

[0029] In one aspect, the base station can indicate to the UE whether to perform the QCL reporting or restrict the QCL reporting. The UE can monitor the message from the base station and, upon receiving an indication from the base station, can perform the QCL reporting until an indication for restricting the QCL reporting is received, or can restrict the QCL reporting until an indication for performing the QCL reporting is received. When the UE is not performing the QCL reporting, the base station can continue to use the QCL relationship setting, such as the delay / Doppler setting, received from the previous QCL report from the UE.

[0026]

[0030] In one embodiment, a QCL-type toggle bit (or toggler bit) may be used to signal the removal or reduction of RS. In one example, the QCL toggle bit may be transmitted through a PDCCH such as DL control information (DCI). In one example, when the beam changes and the QCL-Type D relationship does not change, the QCL-type toggle bit may be toggled (for example, the bit's current value is changed from the previous value), thereby letting the UE know that the QCL-Type A property has changed. In this case, the UE may reset the filtering for delay / Doppler-related parameters due to this change. In another example, when there is no beam change and the QCL-Type D relationship does not change, the QCL-type toggle bit is not toggled (for example, the bit's current value is the same as the previous value). In this example, the UE may still be provided with a DL RS (e.g., tracking RS (TRS)) of QCL-Type A, B, or C, but the DL RS may provide broad (or coarse) information, while the DM-RS of PXCCH or PXSCH may provide more detailed (or refined) information regarding QCL-Type A, B, or C. In addition, a separate RS (similar to a phase tracking RS (PT-RS)) may be used, which may be transmitted along with the data. Thus, according to this disclosure, beam toggling can be used to signal more detailed (or fine) changes in the beam through the use of QCL-type toggle bits.

[0027]

[0031] Next, looking at the figure, it illustrates an example of a technique for dynamic DL and UL QCL relationship reporting. Please note that the figures may not be drawn to a fixed scale, but rather for illustrative purposes.

[0028]

[0032] Referring to Figure 1, a diagram is provided showing an example of a wireless communication system and access network 100. The wireless communication system (also called a wireless wide area network (WWAN)) includes a base station 102, an UE 104, an advanced packet core (EPC) 160, and a 5G core (5GC) 190.

[0029]

[0033] The base station 102 may include a modem 140 having a QCL toggle component 142, which is configured to signal the change in the QCL reporting state to the UE 104 by determining whether to change the QCL reporting state of the UE 104 from a restricted reporting state to an active reporting state, or vice versa.

[0030]

[0034] The UE 104 may include a modem 144 having a QCL reporting component 146, which is configured to receive an indication from the base station 102 and to restrict or perform QCL reporting in response to the indication.

[0031]

[0035] In one embodiment, the base station 102 may include a macrocell (high-power cellular base station) and / or a small cell (low-power cellular base station). A macrocell includes a base station. A small cell includes a femtocell, a picocell, and a microcell.

[0032]

[0036] Base station 102 configured for 4G LTE (registered trademark), collectively referred to as the Advanced Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), may interface with EPC 160 via backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)), may interface with 5GC 190 via backhaul link 184. In addition to other functions, base station 102 may perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, delivery for non-access layer (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and warning message delivery. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC160 or 5GC190) via backhaul link 134 (e.g., X2 interface). Each of backhaul links 132, 134, and 184 may be wired or wireless.

[0033]

[0037] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage to its respective geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network containing both small cells and macro cells is sometimes known as a heterogeneous network. A heterogeneous network may also include home-evolved node B (eNB) (HeNB) that can serve a limited group known as a limited subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) transmissions from UE 104 to base station 102 (also called a reverse link) and / or downlink (DL) transmissions from base station 102 to UE 104 (also called a forward link). Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) for each carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. Carriers may be adjacent to each other or not. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. Primary component carriers may be called primary cells (PCells), and secondary component carriers may be called secondary cells (SCells).

[0034]

[0038] Several UE104s may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication may be via various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth®, ZigBee®, Wi-Fi® based on the IEEE 802.11 standard, LTE, or NR.

[0035]

[0039] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154 within the 5 GHz unlicensed frequency spectrum. When communicating within the unlicensed frequency spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0036]

[0040] Small cell 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in an unlicensed frequency spectrum, small cell 102' may employ NR and use the same 5GHz unlicensed frequency spectrum used by Wi-Fi AP150. Small cell 102' employing NR in an unlicensed frequency spectrum may enhance coverage to the access network and / or increase the capacity of the access network.

[0037]

[0041] Base station 102 may be a small cell 102' or a large cell (e.g., a macro base station), and may include eNBs, gNodeBs (gNBs), or other types of base stations. Some base stations, such as gNB180, may operate in communication with UE104 in the conventional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near-mmW frequencies. When gNB180 operates at mmW or near-mmW frequencies, gNB180 is sometimes referred to as an mmW base station. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 millimeter and 10 millimeters. Radio waves in that band are sometimes called millimeter waves. Near-mmW can extend down to frequencies up to 3 GHz with wavelengths of 100 millimeters. The very high frequency (SHF) band extends between 3 GHz and 30 GHz and is also called centimeter waves. Communication using the mmW / near-mmW radio frequency band has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range.

[0038]

[0042] EPC160 may include a Mobility Management Entity (MME) 162, another MME 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connectivity management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which itself connects to the PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for UEs and other functions. The PDN Gateway 172 and the BM-SC 170 connect to the IP Service 176. IP service 176 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming service, and / or other IP services. BM-SC170 may provide functionality for MBMS user service provisioning and distribution. BM-SC170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting specific services, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0039]

[0043] 5GC190 may include Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Integrated Data Management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and 5GC190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0040]

[0044] Base station 102 may also be called gNB, Node B, Advanced Node B (eNB), Access point, Base transceiver station, Radio base station, Radio transceiver, Transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmit / Receive Point (TRP), or any other appropriate term. Base station 102 provides UE104 with access to EPC160 or 5GC190. Examples of UE104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, Global Positioning Systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of UE104 may be called IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, cardiac monitors, etc.). The UE104 may also be referred to as station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or any other appropriate term.

[0041]

[0045] Referring to Figure 2, an exemplary method of wireless communication is disclosed. Method 200 may be implemented by base station 102 in conjunction with any of the base station 102's components (see, for example, Figure 3). For example, Method 200 may be implemented by one or more of the base station 102's processor 312, transceiver 302, modem 140, QCL toggle component 142, and / or one or more additional components / subcomponents.

[0042]

[0046] Turning to Figure 2, in 202, method 200 may include deciding to change the QCL reporting state for the UE. For example, one or more of the processor 312, modem 140, QCL toggling component 142, and / or one or more components / subcomponents of base station 102 may be configured to decide to change the QCL reporting state for UE 104. Thus, the processor 312, modem 140, QCL toggling component 142, and / or one or more components / subcomponents of base station 102 may define means for deciding to change the QCL reporting state for UE 104. In one example, the QCL reporting state is either an active QCL reporting state or a restricted QCL reporting state. In one example, base station 102 may decide to change the QCL reporting state in response to receiving a request from UE 104 to restrict QCL reporting. In another example, base station 102 may decide to change the QCL reporting state in response to determining that a beam change has occurred. In another example, base station 102 may decide to change the QCL reporting state in response to a beam change, and further, in response to the current beam having the same QCL type as the previous beam. In yet another example, base station 102 may decide that the QCL reporting would result in a power saving issue for UE 104, and in response to this power saving issue, may decide to change the QCL reporting state for UE 104. In one example, base station 102 may decide to change the QCL reporting state on a symbol-to-symbol basis, a slot-to-slot basis, or a multiple slot-to-multiple slot basis.

[0043]

[0047] In 204, method 200 may also include generating an indication to show the UE a change in the QCL reporting state in response to a decision to change the QCL reporting state. For example, one or more of the processor 312, modem 140, QCL toggling component 142, and / or one or more components / subcomponents of base station 102 may be configured to generate an indication to show the UE 104 a change in the QCL reporting state in response to a decision to change the QCL reporting state. Thus, the processor 312, modem 140, QCL toggling component 142, and / or one or more components / subcomponents of base station 102 may define means for generating an indication to show the UE 104 a change in the QCL reporting state in response to a decision to change the QCL reporting state. In one example, generating an indication might involve setting the current value of a QCL type toggle bit (e.g., 1) to a value different from its previous value (e.g., 0), or vice versa (e.g., from 0 to 1). In another example, the indication might further indicate a change to a first QCL type, a second QCL type, or both QCL types. In yet another example, the indication could be a message sent to UE104 via DCI.

[0044]

[0048] In 206, method 200 may include transmitting an indication to the UE in response to generating an indication. For example, one or more of the processor 312, transceiver 302, modem 140, QCL toggle component 142, and / or one or more components / subcomponents of base station 102 may be configured to transmit an indication to UE 104 in response to generating an indication. Thus, the processor 312, transceiver 302, modem 140, QCL toggle component 142, and / or one or more components / subcomponents of base station 102 may define means for transmitting an indication to UE 104 in response to generating an indication. In one example, the indication may be transmitted through a PDCCH such as DCI.

[0045]

[0049] In some examples, Method 200 may optionally include storing QCL relationship settings received from a previous QCL report and communicating with the UE based on the QCL relationship settings in response to the QCL report state being a restricted QCL report state. For example, one or more of the base station 102's processor 312, transceiver 32, modem 140, QCL toggle component 142, and / or one or more components / subcomponents may be configured to store QCL relationship settings received from a previous QCL report and communicate with the UE based on the QCL relationship settings in response to the QCL report state being a restricted QCL report state. Thus, the base station 102's processor 312, transceiver 302, modem 140, QCL toggle component 142, and / or one or more components / subcomponents may define means for storing QCL relationship settings received from a previous QCL report and communicating with the UE based on the QCL relationship settings in response to the QCL report state being a restricted QCL report state.

[0046]

[0050] Referring to Figure 3, an example of an implementation of the base station 102 may include various components. Some of these have already been described above, but include components such as one or more processors 312, memory 316, and transceivers 302 that communicate over one or more buses 344, which may work together with the modem 140 to enable one or more of the functions of method 200 described herein. One or more processors 312, modem 144, memory 316, transceivers 302, RF front end 388, and one or more antennas 365 may be configured to support voice and / or data calls (simultaneously or asynchronously) in one or more radio access technologies.

[0047]

[0051] In one embodiment, one or more processors 312 may include a modem 140 that uses one or more modem processors. Various functions related to the QCL toggle component 142 may be included in the modem 140 and / or processors 312, and in one embodiment, they may be performed by a single processor, while in other embodiments, different functions of these functions may be performed by a combination of two or more different processors. For example, in one embodiment, one or more processors 312 may include one or any combination of a modem processor associated with a transceiver 302, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor. In other embodiments, some of the functions of one or more processors 312 and / or modem 140 may be performed by the transceiver 302.

[0048]

[0052] Furthermore, memory 316 may be configured to store data used herein and / or a local version of application 375, or one or more of the QCL toggling components 142 and / or their subcomponents being executed by at least one processor 312. Memory 316 may include any type of computer-readable medium available to the computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one embodiment, for example, memory 316 may be a non-temporary computer-readable storage medium that stores one or more computer-executable codes that define the QCL toggling components 142 and / or their subcomponents, and / or related data, when the base station 102 is operating at least one processor 312 to execute one or more of the QCL toggling components 142 and / or their subcomponents.

[0049]

[0053] The transceiver 302 may include at least one receiver 306 and at least one transmitter 308. The receiver 306 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). The receiver 306 may be, for example, a radio frequency (RF) receiver. In one embodiment, the receiver 306 may receive signals transmitted by at least one of the UE 104. In addition, the receiver 306 may process such received signals and may obtain measurements of the signals such as Ec / Io, SNR, RSRP, RSSI, etc. The transmitter 308 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). A suitable example of the transmitter 308 may include, but is not limited to, an RF transmitter. The transceiver 302, receiver 306, and / or transmitter 308 may be configured to operate at mmW frequencies and / or near-mmW frequencies.

[0050]

[0054] Furthermore, in one embodiment, the base station 102 may include an RF front end 388 which may communicate with one or more antennas 365 and transceivers 302 to receive and transmit wireless transmissions, for example, wireless communications received by the base station 102 or wireless transmissions transmitted by the base station 102. The RF front end 388 may be connected to one or more antennas 365 and may include one or more low-noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 to transmit and receive RF signals.

[0051]

[0055] In one embodiment, the LNA 390 can amplify the received signal to a desired output level. In one embodiment, each of the LNA 390 may have a specified minimum and maximum gain value. In one embodiment, the RF front-end 388 may use one or more switches 392 to select a particular LNA 390 and its specified gain value based on a desired gain value for a particular application.

[0052]

[0056] One or more PA398s may be used by the RF front-end 388 to amplify the RF output signal at a desired output power level. In one embodiment, each of the PA398s may have a specified minimum and maximum gain value. In one embodiment, the RF front-end 388 may use one or more switches 392 to select a particular PA398 and its specified gain value based on a desired gain value for a particular application.

[0053]

[0057] Furthermore, for example, one or more filters 396 may be used by the RF front-end 388 to filter the received signal to obtain an input RF signal. Similarly, in one embodiment, for example, each filter 396 may be used to filter the output from each PA 398 to generate an output signal for transmission. In one embodiment, each of the filters 396 may be connected to a specific LNA 390 and / or PA 398. In one embodiment, the RF front-end 388 may use one or more switches 392 to select a transmit or receive path that uses a specified filter 396, LNA 390, and / or PA 398, based on a configuration such as that specified by the transceiver 302 and / or processor 312.

[0054]

[0058] Therefore, the transceiver 302 may be configured to transmit and receive wireless signals through one or more antennas 365 via the RF front end 388. In one embodiment, the transceiver 302 may be tuned to operate at a specified frequency such that the base station 102 can communicate with, for example, one or more of the UEs 104. In one embodiment, for example, the modem 140 may configure the transceiver 302 to operate at a specified frequency and power level based on the base station 102 configuration and the communication protocol used by the modem 140.

[0055]

[0059] In one embodiment, modem 140 may be a multiband, multimode modem capable of processing digital data and communicating with transceiver 302 so that digital data is sent and received using transceiver 302. In one embodiment, modem 144 may be multiband and configured to support multiple frequency bands for a particular communication protocol. In one embodiment, modem 140 may be multimode and configured to support multiple operating networks and communication protocols. In one embodiment, modem 140 may control one or more components of base station 102 (e.g., RF front end 388, transceiver 302) to enable transmission and / or reception of signals from the network based on a specified modem configuration. In one embodiment, the modem configuration may be based on the mode of modem 140 and the frequency band in use. In another embodiment, the modem configuration may be based on base station configuration information related to base station 102 provided by the network during cell selection and / or cell reselection.

[0056]

[0060] Referring to Figure 4, an exemplary method of wireless communication is disclosed. Method 400 may be implemented by UE104 in conjunction with any of the components of UE104 (see, for example, Figure 5). For example, Method 400 may be implemented by one or more of the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more additional components / subcomponents of UE104.

[0057]

[0061] Turning to Figure 4, in 402, method 400 may include receiving an indication from a base station to change the QCL reporting state of the UE. For example, one or more of the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of the UE 104 may be configured to receive an indication from base station 102 to change the QCL reporting state of the UE 104. Thus, the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of the UE 104 may define means for receiving an indication from base station 102 to change the QCL reporting state of the UE 104. In one example, the indication may be received in response to a request to restrict QCL reporting being sent from the UE 104 to base station 102.

[0058]

[0062] In 404, method 400 may also include setting a QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on an indication. For example, one or more of the processor 512, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of the UE 104 may be configured to set a QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on an indication. Thus, the processor 512, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of the UE 104 may define means for setting a QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on an indication.

[0059]

[0063] In 406, method 400 may include transmitting a QCL report to a base station in response to setting the QCL reporting state to an active QCL reporting state. For example, one or more of the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of UE 104 may be configured to transmit a QCL report to base station 102 in response to setting the QCL reporting state to an active QCL reporting state. Thus, the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of UE 104 may define means for transmitting a QCL report to base station 102 in response to setting the QCL reporting state to an active QCL reporting state. In one example, the QCL report may be transmitted to base station 102 until a subsequent indication is received by UE 104.

[0060]

[0064] In 408, method 400 may include restricting the transmission of QCL reports to a base station in response to setting the QCL reporting state to a restricted QCL reporting state. For example, one or more of the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of UE 104 may be configured to restrict the transmission of QCL reports to base station 102 in response to setting the QCL reporting state to a restricted QCL reporting state. Thus, the processor 512, transceiver 502, modem 144, QCL reporting component 146, and / or one or more components / subcomponents of UE 104 may define means for restricting the transmission of QCL reports to base station 102 in response to setting the QCL reporting state to a restricted QCL reporting state.

[0061]

[0065] Referring to Figure 5, an example of an implementation of UE104 may include various components. Some of these have already been described above, but include components such as one or more processors 512, memory 516, and transceivers 502 that communicate over one or more buses 544, which may work together with the modem 144 and QCL reporting component 146 to enable one or more of the functions of method 400 described herein.

[0062]

[0066] The transceiver 502, receiver 506, transmitter 508, one or more processors 512, memory 516, application 575, bus 544, RF front end 588, LNA 590, switch 592, filter 596, PA 598, and one or more antennas 565 may be the same as or similar to the corresponding components of base station 102 as described above, but may be configured or otherwise programmed for UE operation as opposed to base station operation. Some further examples

[0067] An exemplary method of wireless communication by a base station, comprising: deciding to change the QCL reporting state for a UE, wherein the QCL reporting state is either an active QCL reporting state or a restricted QCL reporting state; generating an indication to show the UE the change in the QCL reporting state in response to the decision to change the QCL reporting state; and transmitting the indication to the UE in response to generating the indication.

[0063]

[0068] The above exemplary method comprises generating an indication by setting the current value of the QCL type toggle bit to be different from the previous value of the QCL type toggle bit.

[0064]

[0069] Further, receiving a request from the UE to restrict QCL reporting and deciding to change the QCL reporting status is one or more of the exemplary methods described above in response to receiving the request.

[0065]

[0070] One or more of the exemplary methods described above, further comprising determining that a beam change has occurred and determining that the QCL reporting status is changed in response to determining the beam change.

[0066]

[0071] Further comprising determining that the QCL type for the current beam is the same as the previous beam, and further determining to change the QCL reporting status, one or more of the exemplary methods described above, which further respond to determining that the QCL type for the current beam is the same as the previous beam.

[0067]

[0072] Further, one or more of the exemplary methods described above are in response to the decision that QCL reporting would result in energy saving issues for the UE, and that the decision to change the QCL reporting status for the UE would result in energy saving issues for the UE.

[0068]

[0073] The decision to change the QCL reporting status is made in one or more of the exemplary methods described above, whether per symbol, per slot, or per set of slots.

[0069]

[0074] One or more of the exemplary methods described above further indicate that the indication changes to the first QCL type, the second QCL type, or both QCL types.

[0070]

[0075] One or more of the exemplary methods described above, further comprising: remembering the QCL relationship settings received from a previous QCL report; and communicating with the UE based on the QCL relationship settings in response to the QCL report state being a restricted QCL report state.

[0071]

[0076] An exemplary base station comprising memory storing instructions and one or more processors coupled to the memory, wherein one or more processors are configured to: determine to change a pseudo-collocation (QCL) reporting state for a user device (UE), wherein the QCL reporting state is either an active QCL reporting state or a restricted QCL reporting state; generate an indication to show the UE the change in the QCL reporting state in response to the decision to change the QCL reporting state; and transmit the indication to the UE in response to generating the indication.

[0072]

[0077] The above-described example base station, further configured to set the current value of the QCL type toggle bit to be different from the previous value of the QCL type toggle bit.

[0073]

[0078] One or more of the above exemplary base stations are further configured to receive a request from the UE to restrict QCL reporting, and one or more processors decide to change the QCL reporting state in response to receiving the request.

[0074]

[0079] One or more of the exemplary base stations described above, each further configured with one or more processors to determine that a beam change has occurred, and with one or more processors to determine that the QCL reporting state has been changed in response to determining the beam change.

[0075]

[0080] One or more of the exemplary base stations described above are further configured to determine that the QCL type for the current beam is the same as the QCL type for the previous beam, and one or more processors decide to change the QCL reporting state in response to determining that the QCL type for the current beam is the same as the QCL type for the previous beam.

[0076]

[0081] One or more of the exemplary base stations described above are further configured to determine that QCL reporting would result in a power saving issue for the UE, and one or more processors determine to change the QCL reporting state in response to the determination that QCL reporting would result in a power saving issue for the UE.

[0077]

[0082] One or more of the above-described example base stations, where one or more processors decide to change the QCL reporting state on a per-symbol, per-slot, or per-slot basis.

[0078]

[0083] One or more of the example base stations above, where the indication further indicates a change to the first QCL type, the second QCL type, or both QCL types.

[0079]

[0084] One or more of the exemplary base stations described above, each further configured to store QCL relationship settings received from a previous QCL report and to communicate with the UE based on the QCL relationship settings in response to the QCL report state being a restricted QCL report state.

[0080]

[0085] An exemplary apparatus for use in a device (for example, a base station), comprising means for wireless communication, means for storing instructions and data, and means for carrying out one or more of the exemplary methods described above, in whole or in part.

[0081]

[0086] An exemplary computer-readable medium storing computer-executable code for use in a device (e.g., a base station), comprising code for performing one or more of the exemplary methods described above, in whole or in part.

[0082]

[0087] A second exemplary method of wireless communication by a UE, comprising: receiving an indication from a base station for changing the QCL reporting state of the UE; setting the QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on the indication; transmitting a QCL report to the base station in response to setting the QCL reporting state to an active QCL reporting state; and restricting the transmission of the QCL report to the base station in response to setting the QCL reporting state to a restricted QCL reporting state.

[0083]

[0088] A second exemplary method of the above, further comprising storing the previous value of the QCL type toggle bit, and receiving an indication to change the QCL reporting state, comprising comparing the current value of the QCL type toggle bit received from the base station with the previous value of the QCL type toggle bit, wherein the indication to change the QCL reporting state is based on the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit.

[0084]

[0089] One or more of the exemplary second methods described above, further comprising remembering the previous QCL reporting state of the UE, and setting the QCL reporting state to one of the active QCL reporting state or restricted QCL reporting state in response to the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit, wherein the QCL reporting state is changed to one of the active QCL reporting state or restricted QCL reporting state which is different from the previous QCL reporting state.

[0085]

[0090] The UE further comprises sending a request to the base station to restrict QCL reporting, and the receipt of the indication is in response to sending the request, one or more of the exemplary second methods described above. The QCL report is sent or the transmission of the QCL report is restricted until a subsequent indication is received, one or more of the exemplary second methods described above.

[0086]

[0091] An exemplary user device (UE) comprising memory storing instructions and one or more processors coupled to the memory, wherein one or more processors are configured to receive an indication from a base station for changing the pseudo-collocation (QCL) reporting state of the UE; to set the QCL reporting state to either an active QCL reporting state or a restricted QCL reporting state based on the indication; to transmit a QCL report to the base station in response to setting the QCL reporting state to an active QCL reporting state; and to restrict the transmission of a QCL report to the base station in response to setting the QCL reporting state to a restricted QCL reporting state.

[0087]

[0092] One or more processors are further configured to store the previous value of the QCL type toggle bit and to compare the current value of the QCL type toggle bit received from the base station with the previous value of the QCL type toggle bit, such that an indication for changing the QCL reporting state is based on the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit, as described in the exemplary UE above.

[0088]

[0093] One or more of the exemplary UEs described above, each further configured to store the previous QCL reporting state of the UE and, in response to the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit, change the QCL reporting state to one of either an active QCL reporting state or a restricted QCL reporting state that is different from the previous QCL reporting state.

[0089]

[0094] One or more of the exemplary UEs described above, each having one or more processors further configured to send a request from the UE to the base station to limit QCL reporting, and each having one or more processors configured to receive an indication in response to sending the request.

[0090]

[0095] One or more of the above exemplary UEs where QCL reports are sent or the sending of QCL reports is restricted until a subsequent indication is received.

[0091]

[0096] An exemplary apparatus for use in a device (for example, a base station), comprising means for wireless communication, means for storing instructions and data, and means for carrying out one or more of the exemplary second methods described above, in whole or in part.

[0092]

[0097] An exemplary computer-readable medium storing computer-executable code for use in a device (e.g., a base station), comprising code for implementing one or more of the exemplary second methods described above, in whole or in part.

[0093]

[0098] The modes for carrying out the above-described inventions with respect to the attached drawings are illustrative and do not necessarily represent only examples that can be implemented or fall within the scope of the claims. The term “example,” as used in this description, means “to serve as an example, case, or illustration,” and does not mean “preferred” or “advantageous over other examples.” The modes for carrying out the inventions include specific details for the purpose of giving an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0094]

[0099] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips which may be referenced throughout the above description may be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, computer executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0095]

[0100] The various exemplary blocks and components described in this disclosure may be implemented or carried out using specially programmed devices, but are not limited to, processors, digital signal processors (DSPs), ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The specially programmed processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration.

[0096]

[0101] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes in a non-temporary computer-readable medium, or transmitted via a non-temporary computer-readable medium. Other examples and implementations fall within the scope and spirit of this disclosure and the accompanying claims. For example, due to the nature of the software, the functions described above may be implemented using software executed by a specially programmed processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations. Furthermore, when used herein, including within the claims, "or" in an enumeration of items ending in "at least one of" indicates a disjunctive enumeration, such as "at least one of A, B, or C" meaning A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0097]

[0102] Computer-readable media include both computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Storage media can be any available media that can be accessed by a general-purpose or dedicated computer. By example, and not by limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to carry or store desired program code means in the form of instructions or data structures, and can be accessed by a general-purpose or dedicated computer or general-purpose or dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. The terms "disk" and "disc" as used herein include Compact Disc (CD), LaserDisc® (disc), Optical Disc (disc), Digital Multipurpose Disc (disc) (DVD), Floppy Disk (disk), and Blu-ray® Disc (disc), where a disk typically reproduces data magnetically, and a disc reproduces data optically using a laser. Combinations of the above are also included within the scope of computer-readable media.

[0098]

[0103] The foregoing descriptions in this disclosure are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this disclosure will be readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Furthermore, elements of the described aspects and / or embodiments may be described or claimed in the singular, but unless a limitation to the singular is expressly stated, the plural is intended. In addition, any aspect and / or embodiment in whole or in part may be used in conjunction with any other aspect and / or embodiment in whole or in part unless otherwise stated. Accordingly, this disclosure should not be limited to the examples and designs described herein, but should be given the broadest scope that corresponds to the principles and novel features disclosed herein. The invention described in the original claims of this application is listed below. [C1] A method of wireless communication using a base station, A decision to change the pseudo-collocation (QCL) reporting status for a user device (UE), wherein the QCL reporting status is either an active QCL reporting status or a restricted QCL reporting status. In response to the decision to change the QCL reporting status, an indication is generated to show the change in the QCL reporting status to the UE. To transmit the indication to the UE in response to generating the indication. A method that includes [a certain feature]. [C2] The generation of the indication is The method according to C1, comprising setting the current value of a QCL type toggle bit to be different from the previous value of the QCL type toggle bit. [C3] The method of C1, further comprising receiving a request from the UE to restrict QCL reporting, and determining to change the QCL reporting status in response to receiving the request. [C4] The method of C1, further comprising determining that a beam change has occurred, and determining that the QCL reporting state is changed in response to determining the beam change. [C5] The method of C1, further comprising determining that the QCL type for the current beam is the same as the QCL type for the previous beam, and changing the QCL reporting status, wherein the determination further responds to the determination that the QCL type for the current beam is the same as the QCL type for the previous beam. [C6] The method of C1, further comprising determining that the QCL report would result in a power saving problem for the UE, wherein the determination to change the QCL report status for the UE is in response to the determination that the QCL report would result in a power saving problem for the UE. [C7] The method according to C1, wherein changing the QCL reporting status is determined on a per-symbol, per-slot, or per-multiple-slot basis. [C8] The method according to C1, wherein the indication further indicates a change to a first QCL type, a second QCL type, or both QCL types. [C9] Remember the QCL relationship settings received from the previous QCL report, In response to the QCL reporting state being the restricted QCL reporting state, communicate with the UE based on the QCL relationship settings. A method of C1 that further includes the following: [C10] A method of wireless communication using user equipment (UE), Receiving an indication from the base station to change the pseudo-collocation (QCL) reporting status of the aforementioned UE, Based on the indication, the QCL reporting state is set to either an active QCL reporting state or a restricted QCL reporting state. In response to setting the QCL reporting state to the active QCL reporting state, the QCL report is transmitted to the base station. In response to setting the QCL reporting state to the restricted QCL reporting state, the transmission of the QCL report to the base station is restricted. A method that includes [a certain feature]. [C11] The system further includes storing the previous value of the QCL type toggle bit, and receiving the indication for changing the QCL reporting state, The method of C10, comprising comparing the current value of the QCL type toggle bit received from the base station with the previous value of the QCL type toggle bit, wherein the indication for changing the QCL reporting state is based on the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit. [C12] The system further includes storing the previous QCL reporting state of the UE, and setting the QCL reporting state to either the active QCL reporting state or the restricted QCL reporting state. The method of C10, comprising changing the QCL reporting state to one of the active QCL reporting state or the restricted QCL reporting state, which is different from the previous QCL reporting state, in response to the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit. [C13] The method of C10, further comprising transmitting a request from the UE to restrict QCL reporting to the base station, wherein the reception of the indication is in response to the transmission of the request. [C14] The method of C10, wherein the QCL report is transmitted or the transmission of the QCL report is restricted until a subsequent indication is received. [C15] The memory that stores the instructions, A base station comprising one or more processors coupled to the memory, wherein the one or more processors A decision to change the pseudo-collocation (QCL) reporting status for a user device (UE), wherein the QCL reporting status is either an active QCL reporting status or a restricted QCL reporting status. In response to a decision to change the QCL reporting status, an indication is generated to show the change in the QCL reporting status to the UE, Sending the indication to the UE in response to generating the indication. A base station configured to perform the following actions. [C16] The one or more processors described above The base station according to C15, further configured to set the current value of the QCL type toggle bit to be different from the previous value of the QCL type toggle bit. [C17] The one or more processors described above The base station according to C15, further configured to receive a request from the UE to restrict QCL reporting, and the one or more processors decide to change the QCL reporting state in response to receiving the request. [C18] The one or more processors described above The base station according to C15, further configured to determine that a beam change has occurred, and the one or more processors determine to change the QCL reporting state in response to determining the beam change. [C19] The one or more processors described above The base station according to C15, further configured to determine that the QCL type for the current beam is the same as the QCL type for the previous beam, and the one or more processors determine to change the QCL reporting state in response to determining that the QCL type for the current beam is the same as the QCL type for the previous beam. [C20] The one or more processors described above The base station according to C15, further configured to determine that a QCL report would result in a power saving problem for the UE, and the one or more processors determine to change the QCL report state in response to the determination that the QCL report would result in the power saving problem for the UE. [C21] The base station according to C15, wherein one or more processors decide to change the QCL reporting state for each symbol, each slot, or each set of slots. [C22] A base station as described in C15, wherein the indication further indicates a change to a first QCL type, a second QCL type, or both QCL types. [C23] The one or more processors described above Remember the QCL relationship settings received from the previous QCL report, In response to the QCL reporting state being the restricted QCL reporting state, communication with the UE is performed based on the QCL relationship setting. A base station as described in C15, further configured to perform the following actions. [C24] The memory that stores the instructions, A user device (UE) comprising one or more processors coupled to the memory, wherein the one or more processors Receiving an indication from the base station to change the pseudo-collocation (QCL) reporting status of the aforementioned UE, Based on the indication, the QCL reporting state is set to either an active QCL reporting state or a restricted QCL reporting state. In response to setting the QCL reporting state to the active QCL reporting state, the QCL report is transmitted to the base station. In response to setting the QCL reporting state to the restricted QCL reporting state, the transmission of the QCL report to the base station is restricted. A UE configured to perform the following actions. [C25] The one or more processors described above The QCL type toggle bit remembers the previous value, The current value of the QCL type toggle bit received from the base station is compared with the previous value of the QCL type toggle bit. The UE described in C24 is further configured to perform such an indication for changing the QCL reporting state, where the current value of the QCL type toggle bit is different from the previous value of the QCL type toggle bit. [C26] The one or more processors described above The QCL reporting status prior to the aforementioned UE is to be stored, In response to the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit, the QCL reporting state is changed to one of the active QCL reporting state or the restricted QCL reporting state, which is different from the previous QCL reporting state. The UE described in C24 is further configured to perform the following actions. [C27] The one or more processors described above The UE according to C24, further configured to transmit a request from the UE to restrict QCL reporting to the base station, and one or more processors configured to receive the indication in response to transmitting the request. [C28] The UE described in C24, wherein the QCL report is transmitted or the transmission of the QCL report is restricted until a subsequent indication is received.

Claims

1. A method of wireless communication using a base station, wherein the method is Deciding to change the pseudo-collocation (QCL) reporting state for a user device (UE), wherein the QCL reporting state is either an active QCL reporting state in which the UE transmits one or more QCL reports to the base station, or a restricted QCL reporting state in which the UE is restricted from transmitting one or more QCL reports to the base station. In response to the decision to change the QCL reporting state, an indication is generated to show the UE that the QCL reporting state has been changed from the active QCL reporting state to the restricted QCL reporting state, or from the restricted QCL reporting state to the active QCL reporting state. To transmit the indication to the UE in response to generating the indication. A method that includes [a certain feature].

2. The generation of the indication is The method according to claim 1, further comprising setting the current value of a QCL type toggle bit to be different from the previous value of the QCL type toggle bit.

3. The method according to claim 1, further comprising receiving a request from the UE to restrict QCL reporting, wherein the decision to change the QCL reporting status is in response to receiving the request.

4. The method according to claim 1, further comprising determining that a beam change has occurred, wherein the determination to change the QCL reporting state is in response to the determination of the beam change.

5. The method according to claim 1, further comprising determining that the QCL type for the current beam is the same as the QCL type for the previous beam, wherein the determination to change the QCL reporting state is a further response to determining that the QCL type for the current beam is the same as the QCL type for the previous beam.

6. The method according to claim 1, further comprising determining that the QCL report would result in a power saving problem for the UE, wherein the determination to change the QCL report status for the UE is in response to the determination that the QCL report would result in a power saving problem for the UE.

7. The method according to claim 1, wherein the determination to change the QCL reporting status is made per symbol, per slot, or per set of slots.

8. The method according to claim 1, wherein the indication further indicates a change to a first QCL type, a second QCL type, or both QCL types.

9. Remember the QCL relationship settings received from the previous QCL report, In response to the QCL reporting state being the restricted QCL reporting state, communication with the UE is performed based on the QCL relationship settings. The method according to claim 1, further comprising:

10. A method of wireless communication using user equipment (UE), wherein the method is: Receiving an indication from a base station to change the pseudo-collocation (QCL) reporting state of the UE, wherein the QCL reporting state is either an active QCL reporting state in which the UE transmits one or more QCL reports to the base station, or a restricted QCL reporting state in which the UE is restricted from transmitting one or more QCL reports to the base station. Based on the indication, the QCL reporting state is changed from the active QCL reporting state to the restricted QCL state, or from the restricted QCL reporting state to the active QCL state. A method that includes [a certain feature].

11. The system further includes storing the previous value of the QCL type toggle bit, and receiving the indication for changing the QCL reporting state. The method according to claim 10, comprising comparing the current value of the QCL type toggle bit received from the base station with the previous value of the QCL type toggle bit, wherein the indication for changing the QCL reporting state is based on the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit.

12. The system further includes storing the QCL reporting state prior to the UE, and setting the QCL reporting state to either the active QCL reporting state or the restricted QCL reporting state. The method according to claim 10, comprising changing the QCL reporting state to one of the active QCL reporting state or the restricted QCL reporting state which is different from the previous QCL reporting state, in response to the current value of the QCL type toggle bit being different from the previous value of the QCL type toggle bit.

13. The method according to claim 10, further comprising transmitting a request from the UE to restrict QCL reporting to the base station, wherein the reception of the indication is in response to the transmission of the request.

14. The memory that stores the instructions, A base station comprising one or more processors coupled to the memory, wherein the one or more processors Deciding to change the pseudo-collocation (QCL) reporting state for a user device (UE), wherein the QCL reporting state is either an active QCL reporting state in which the UE transmits one or more QCL reports to the base station, or a restricted QCL reporting state in which the UE is restricted from transmitting one or more QCL reports to the base station. In response to a decision to change the QCL reporting state, an indication is generated to show the UE that the QCL reporting state has been changed from the active QCL reporting state to the restricted QCL reporting state, or from the restricted QCL reporting state to the active QCL reporting state. Sending the indication to the UE in response to generating the indication. A base station configured to perform the following actions.

15. The memory that stores the instructions, A user device (UE) comprising one or more processors coupled to the memory, wherein the one or more processors Receiving an indication from a base station to change the pseudo-collocation (QCL) reporting state of the UE, wherein the QCL reporting state is either an active QCL reporting state in which the UE transmits one or more QCL reports to the base station, or a restricted QCL reporting state in which the UE is restricted from transmitting one or more QCL reports to the base station. Based on the indication, the QCL reporting state is changed from the active QCL reporting state to the restricted QCL state, or from the restricted QCL reporting state to the active QCL state. A UE configured to perform the following actions.

Images