The updated beam is applied before the triggered transmission time.

Abstract

Certain aspects of this disclosure relate to wireless communication, and more specifically, to techniques for determining when to apply beam updates. A method executable by a user equipment (UE) includes: receiving signaling indicating a beam update, determining that the application time of the beam update occurs between downlink control information (DCI) of a scheduled transmission and the scheduled transmission, and deciding whether to apply the beam update to the scheduled transmission.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Application No. 17 / 169,034, filed February 5, 2021, which claims the benefits and priority of U.S. Provisional Application No. 62 / 981,015, filed February 24, 2020, and U.S. Provisional Application No. 62 / 982,695, filed February 27, 2020, both of which are hereby assigned to the assignee in their entirety and are expressly incorporated herein by reference, as fully set forth below and used for all applicable purposes. Technical Field

[0003] This disclosure relates to wireless communication, and more specifically to techniques for beam updating. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3GPP Long Term Evolution (LTE) systems, LTE-A Advanced systems, 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.

[0005] In some examples, a radio multiple access communication system may include multiple base stations (BSs), each capable of simultaneously supporting communication from multiple communication devices (also known as user equipment (UEs)). In LTE or LTE-A networks, a group of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR) or 5G networks), a radio multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit-receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a group of one or more DUs communicating with the CUs may define access nodes (e.g., which may be referred to as BSs, 5G NBs, next-generation node Bs (gNBs or gNodeBs), TRPs, etc.). A BS or DU may communicate with a group of UEs on downlink (DL) channels (e.g., for transmissions from the BS to the UE) and uplink (UL) channels (e.g., for transmissions from the UE to the BS or DU).

[0006] These multiple access technologies have been adopted by various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the municipal, national, regional, and even global levels. New Radio (NR) (such as 5G) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard issued by 3GPP. It aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards that use OFDMA with a cyclic prefix (CP) on DL and UL. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, with the increasing demand for mobile broadband access, NR and LTE technologies need further improvement. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0008] The systems, methods, and apparatuses of this disclosure each have multiple aspects, none of which are solely responsible for their desired properties. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled “Detailed Description,” one will understand how the features of this disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0009] One or more aspects of the subject matter described in this disclosure can be implemented in a method for wireless communication by a user equipment (UE). The method typically includes receiving signaling indicating a beam update. The method typically includes determining that the beam update application occurs between downlink control information (DCI) for a scheduled transmission and the scheduled transmission. The method typically includes deciding whether to apply the beam update to the scheduled transmission.

[0010] One or more aspects of the subject matter described in this disclosure can be implemented in a method for wireless communication by a network entity. The method typically includes signaling an indication of a beam update to the UE. The method typically includes determining that the application time of the beam update occurs between the DCI of a scheduled transmission and the scheduled transmission. The method typically includes deciding whether to apply the beam update to the scheduled transmission.

[0011] One or more aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication by a UE. The apparatus typically includes a memory and at least one processor coupled to the memory. The at least one processor coupled to the memory is typically configured to receive signaling indicating a beam update. The at least one processor coupled to the memory is typically configured to determine when the beam update application occurs between the DCI of a scheduled transmission and the scheduled transmission. The at least one processor coupled to the memory is typically configured to decide whether to apply the beam update to the scheduled transmission.

[0012] One or more aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication by a network entity. The apparatus typically includes a memory and at least one processor coupled to the memory. The at least one processor coupled to the memory is typically configured to signal an indication of a beam update to the UE. The at least one processor coupled to the memory is typically configured to determine that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission. The at least one processor coupled to the memory is typically configured to decide whether to apply the beam update to the scheduled transmission.

[0013] One or more aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus typically includes components for receiving signaling indicative of beam updates. The apparatus typically includes components for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission. The apparatus typically includes components for determining whether to apply the beam update to the scheduled transmission.

[0014] One or more aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus typically includes components for signaling an indication of beam update to the UE. The apparatus typically includes components for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission. The apparatus typically includes components for determining whether to apply the beam update to the scheduled transmission.

[0015] One or more aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium having computer-executable code stored thereon. The computer-readable medium having computer-executable code stored thereon typically includes code for receiving signaling indicating beam updates. The computer-readable medium having computer-executable code stored thereon typically includes code for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission. The computer-readable medium having computer-executable code stored thereon typically includes code for deciding whether to apply the beam update to the scheduled transmission.

[0016] One or more aspects of the subject matter described in this disclosure may be implemented in a computer-readable medium having computer-executable code stored thereon. The computer-readable medium having computer-executable code stored thereon typically includes code for signaling an indication of beam update to the UE. The computer-readable medium having computer-executable code stored thereon typically includes code for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission. The computer-readable medium having computer-executable code stored thereon typically includes code for deciding whether to apply the beam update to the scheduled transmission.

[0017] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features represent only a few of the many ways in which the principles of each aspect can be employed. Attached Figure Description

[0018] To gain a more detailed understanding of the foregoing features of this disclosure, reference can be made to several aspects for which a more specific description has been briefly summarized above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain aspects of this disclosure, and that this description can accommodate other equally valid aspects.

[0019] Figure 1 This is a block diagram conceptually illustrating an example telecommunications system according to certain aspects of this disclosure.

[0020] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to certain aspects of this disclosure.

[0021] Figure 3 This is a diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure.

[0022] Figure 4 This is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0023] Figure 5 This is a diagram illustrating an example of implementing a communication protocol stack according to certain aspects of this disclosure.

[0024] Figure 6 Examples of frame formats for new radio (NR) systems are shown in accordance with certain aspects of this disclosure.

[0025] Figure 7 This illustrates how different beams can be used to transmit different synchronization signal blocks (SSBs) according to certain aspects of this disclosure.

[0026] Figure 8 An exemplary transport resource mapping is shown in accordance with certain aspects of this disclosure.

[0027] Figure 9 Examples of quasi-colocational (QCL) relationships are shown according to certain aspects of this disclosure.

[0028] Figure 10 This is a flowchart illustrating an example operation of wireless communication performed by a UE according to certain aspects of this disclosure.

[0029] Figure 11 This is a flowchart illustrating an example operation of wireless communication by a network entity according to certain aspects of this disclosure.

[0030] Figure 12 It is a timing diagram used to determine whether to apply beam updates, based on certain aspects of this disclosure.

[0031] Figure 13 A communication device, shown according to aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0032] Figure 14 Communication devices, as shown in aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0033] For ease of understanding, the same reference numerals are used where possible to denote common elements in the figures. Elements disclosed in one aspect are intended to be usefully applied in other aspects without specific description. Detailed Implementation

[0034] This disclosure relates to wireless communication, and more specifically to techniques for beam updating.

[0035] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various procedures or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or method. Moreover, the scope of this disclosure is intended to cover apparatus or methods practiced using structures, functions, or structures and functions other than those set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims. The word “exemplary” is used herein to mean “as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or advanced over other aspects.

[0036] The techniques described in this article can be used in various wireless communication technologies, such as Long Term Evolution (LTE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as New Radio (NR) (e.g., 5GRA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

[0037] NR is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP LTE and LTE-Advanced (LTE-A) are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used with the aforementioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used to describe aspects herein, aspects of this disclosure can be applied to other generation-based communication systems, including NR technology, such as 5G and later.

[0038] NR access (such as 5G technology) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., 80MHz or higher), massive machine-type communication (mMTC) for high carrier frequencies (e.g., 25GHz or higher), and / or mission-critical ultra-reliable low-latency communication (URLLC) for non-backward-compatible MTC technologies. These services may have latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. Furthermore, these services can coexist in the same subframe.

[0039] Example wireless communication system

[0040] Figure 1 An example wireless communication network 100 (e.g., a New Radio (NR) / 5G network) is shown, in which aspects of this disclosure can be implemented. For example, wireless network 100 may include components configured to perform... Figure 10 Operation 1000 is used to process data from network entities (executing...) Figure 11 The user equipment (UE) 120 sends a beam update (operation 1100) to perform beam refinement.

[0041] like Figure 1As shown, the wireless network 100 may include multiple base stations (BSs) 110 and other network entities. A BS may be a station communicating with a UE. Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B (NB) and / or the Node B subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is interchangeable with Next Generation Node B (gNB), NR BS, 5G NB, Access Point (AP), or Transmit / Receive Point (TRP). In some examples, a cell may not necessarily be static, and the geographic area of ​​the cell may move depending on the location of a mobile BS. In some examples, base stations may be interconnected to another and / or one or more other base stations or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces, such as direct physical connections, wireless connections, virtual networks, or similar interfaces using any suitable transport network.

[0042] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0043] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other cell types. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow unrestricted access for UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the example shown, BS110a, 110b, and 110c can be macroBSs for macrocells 102a, 102b, and 102c, respectively. BS110x can be a picoBS for picocell 102x. BS110y and 110z can be femtoBSs for femtocells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.

[0044] The wireless communication network 100 may also include relay stations. A relay station is a station that receives data and / or other information transmissions from an upstream station (e.g., a BS or a UE) and transmits these transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE relaying transmissions for other UEs. Figure 1 In the example shown, relay station 110r can communicate with BS110a and UE 120r to facilitate communication between BS110a and UE 120r. A relay station can also be called a relay BS, relay, etc.

[0045] Wireless network 100 can be a heterogeneous network comprising different types of BSs (e.g., macro BS, pico BS, femto BS, repeaters, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, femto BS, and repeater may have a lower transmit power level (e.g., 1 watt).

[0046] Wireless communication network 100 can support synchronous or asynchronous operation. For synchronous operation, BSs may have similar frame timings, and transmissions from different BSs may be roughly time-aligned. For asynchronous operation, BSs may have different frame timings, and transmissions from different BSs may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0047] Network controller 130 can be coupled to a group of BSs and provide coordination and control for these BSs. Network controller 130 can communicate with BS 110 via backhaul. BS 110 can also communicate with each other (e.g., directly or indirectly) via wireless or wired backhaul.

[0048] UE 120 (e.g., 120x, 120y, etc.) may be distributed throughout the wireless network 100, and each UE may be static or mobile. UE may also be referred to as a mobile station, terminal, access terminal, user unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biometric sensor / device, wearable device such as smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, gaming device, augmented reality device (augmented reality (AR), extended reality (XR), or virtual reality (VR)) or any other suitable device configured to communicate via wireless or wired media.

[0049] Some UEs can be considered Machine-Type Communication (MTC) devices or Evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or other entities. For example, a wireless node can provide connectivity to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices; they can be Narrowband Internet of Things (NB-IoT) devices.

[0050] Some wireless networks (e.g., LTE) use Orthogonal Frequency Division Multiplexing (OFDM) on the downlink (DL) and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink (UL). OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often also called tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transmission (FFT) size could be 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into multiple subbands. For example, a subband may cover 1.08MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, respectively.

[0051] While the aspects of the examples described herein may be associated with LTE technology, the aspects of this disclosure are applicable to other wireless communication systems, such as NR. NR can use OFDM with a cyclic prefix (CP) on both UL and DL and includes support for half-duplex operation using Time Division Duplex (TDD). Beamforming can be supported and beam direction can be dynamically configured. Precoded Multiple-Input Multiple-Output (MIMO) transmission can also be supported. MIMO configuration in DL can support up to eight transmit antennas, with up to eight streams transmitted across multiple DL layers, and up to two streams per UE. Multilayer transmission with up to two streams per UE can be supported. Aggregation of multiple cells with up to eight serving cells can be supported.

[0052] In certain situations, air interface access can be scheduled. For example, a scheduling entity (e.g., BS, Node B, eNB, gNB, etc.) can allocate resources for communication between some or all devices and apparatuses within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities can utilize resources allocated by one or more scheduling entities.

[0053] A BS is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by the UE for wireless communication. In some examples, a UE can be used as a scheduling entity in peer-to-peer (P2P) networks and / or mesh networks. In mesh network examples, in addition to communicating with scheduling entities, UEs can also communicate directly with each other.

[0054] Back Figure 1 This diagram illustrates various potential deployments across different deployment scenarios. For example, in... Figure 1 In the diagram, a solid line with a double arrowhead represents the desired transmission between the UE and the serving BS, which is the BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with a double arrowhead represents interference transmission between the UE and the BS. Other lines indicate component-to-component (e.g., UE-to-UE) communication options.

[0055] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to certain aspects of this disclosure. The logical architecture of the distributed RAN 200 can be... Figure 1 This is implemented in the wireless communication network 100 shown. The 5G access node (AN) 206 may include an access node controller (ANC) 202. The ANC 202 may be the central unit (CU) of a distributed RAN 200. The backhaul interface to the next-generation core network (NG-CN) 204 may terminate at the ANC 202. The backhaul interface to the adjacent next-generation access node (NG AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more transmit / receive points (TRPs) 208 (e.g., cell, BS, gNB, etc.).

[0056] TRP 208 can be a distributed unit (DU). TRP 208 can be connected to a single ANC (e.g., ANC 202) or more ANCs (not shown). For example, for RAN-shared, Radio-as-a-Service (RaaS), and service-specific ANC deployments, TRP 208 can be connected to more than one ANC. TRP 208 can each include one or more antenna ports. TRP 208 can be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0057] The logical architecture of the distributed RAN 200 can support a variety of backhaul and fronthauling solutions. This support can occur across and across different deployment types. For example, the logical architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter).

[0058] The logical architecture of the distributed RAN 200 can share features and / or components with LTE. For example, the next-generation access node (NG-AN) 210 can support dual connectivity with NR and can share common fronthaul for LTE and NR.

[0059] The logical architecture of the distributed RAN 200 enables cooperation between TRPs 208, for example, cooperation within a TRP and / or across TRPs via ANC 202. Inter-TRP interfaces can be omitted.

[0060] Logical functions can be dynamically distributed across the distributed RAN 200 logical architecture. (See reference...) Figure 5 As described in more detail, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer can be adapted to be placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

[0061] Figure 3 This is a diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU 302 can be deployed centrally. C-CU 302 functions can be offloaded (e.g., to Advanced Radio Services (AWS)) to handle peak capacity.

[0062] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU 304 can host core network functions locally. The C-RU 304 can be deployed in a distributed manner. The C-RU 304 may be located near the network edge.

[0063] The DU 306 can host one or more TRPs (Edge Nodes (EN), Edge Units (EU), Radio Headers (RH), Smart Radio Headers (SRH), etc.). The DU can be located at the network edge with radio frequency (RF) capabilities.

[0064] Figure 4 The BS110 and UE 120 shown are examples of aspects that can be used to implement this disclosure. Figure 1Example components (as depicted in the text). For example, antenna 452, processors 466, 458, 464 and / or controller / processor 480 of UE 120 can be used to perform... Figure 10 Operation 1000, and the antenna 434, processors 420, 460, 438 and / or controller / processor 440 of the BS110 can be used to perform Figure 11 Operation 1100.

[0065] At BS110, the transmit processor 420 can receive data from data source 412 and control information from controller / processor 440. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. The processor 420 can process (e.g., encode and symbol map) the data and control information separately to obtain data symbols and control symbols. The processor 420 can also generate reference symbols such as the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). The transmit (TX) MIMO processor 430 can perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, and, where applicable, can provide an output symbol stream to the modulator (MOD) in transceivers 432a-432t. Each modulator in transceivers 432a-432t can process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The DL signal from the modulators in transceivers 432a-432t can be transmitted via antennas 434a-434t respectively.

[0066] At UE 120, antennas 452a-452r can receive DL signals from BS 110 and can provide the received signals to demodulators (DEMODs) in transceivers 454a-454r respectively. Each demodulator in transceivers 454a-454r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM, etc.) to obtain a received symbol. MIMO detector 456 can obtain the received symbol from all demodulators in transceivers 454a-454r, perform MIMO detection on the received symbol if applicable, and provide the detected symbol. Receiver processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbol, provide the decoded data for UE 120 to data sink 460, and provide the decoded control information to controller / processor 480.

[0067] At UL, at UE 120, the transmit processor 464 can receive and process data from data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). The transmit processor 464 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signals (SRS)). If applicable, symbols from the transmit processor 464 can be pre-encoded by the TX MIMO processor 466, further processed by demodulators in transceivers 454a-454r (e.g., for SC-FDM, etc.), and transmitted to BS110. At BS110, the UL signal from UE 120 can be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 if applicable, and further processed by receive processor 438 to obtain decoded data and control information transmitted by UE 120. The receiver processor 438 can provide the decoded data to the data receiver 439 and the decoded control information to the controller / processor 440.

[0068] Controllers / processors 440 and 480 can direct operations at BS110 and UE 120, respectively. Processor 440 and / or other processors and modules at BS110 can execute or direct processes performed using the techniques described herein. Memory 442 and 482 can store data and program code for BS110 and UE 120, respectively. Scheduler 444 can schedule data transfers by the UE for DL ​​and / or UL.

[0069] Figure 5This is a diagram illustrating an example of a communication protocol stack according to certain aspects of this disclosure. The communication protocol stack shown can be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting UL-based mobility). Figure 500 illustrates a communication protocol stack including an RRC layer 510, a PDCP layer 515, an RLC layer 520, a MAC layer 525, and a PHY layer 530. In various examples, the layers of the protocol stack can be implemented as separate software modules, portions of a processor or application-specific integrated circuit (ASIC), portions of non-collocated devices connected via a communication link, or various combinations thereof. For example, both collocation and non-collocation implementations can be used in the protocol stack for network access devices (e.g., AN, CU, and / or DU) or UEs.

[0070] Option 505-a illustrates a split implementation of the protocol stack, where the protocol stack implementation is in a centralized network access device (e.g., Figure 2 ANC 202) and distributed network access devices (e.g., Figure 2 The DU (208) is split. In option 505-a, the RRC layer 510 and PDCP layer 515 can be implemented through the CU, and the RLC layer 520, MAC layer 525, and PHY layer 530 can be implemented through the DU. In various examples, the CU and DU can be co-located or non-co-located. Option 505-a may be useful in macrocell, microcell, or picocell deployments.

[0071] Option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device. In this option, each of the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 can be implemented via AN. Option 505-b may be useful in, for example, femtocell deployments.

[0072] Regardless of whether the network access device implements part or all of the protocol stack, the UE can implement the entire protocol stack, as shown in 505-c (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530).

[0073] The embodiments discussed here can include various interval and timing deployments. For example, in LTE, the basic transmission time interval (TTI), or data packet duration, is a 1ms subframe. In NR, a subframe is still 1ms, but the basic TTI is referred to as a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16 time slots), depending specifically on the subcarrier spacing. An NR resource block (RB) consists of 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing (SCS) of 15kHz and can define other SCSs relative to the basic SCS, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. Symbol and time slot lengths are proportional to the SCS. The CP length also depends on the SCS.

[0074] Figure 6 An example of a frame format 600 for a New Radio (NR) system according to certain aspects of this disclosure is shown. The transmission timeline of each of the DL and UL can be divided into radio frame units. Each radio frame can have a predetermined duration (e.g., 10 ms) and can be divided into 10 subframes, each 1 ms in number, indexed from 0 to 9. Depending on the subcarrier spacing, each subframe can include a variable number of time slots. Depending on the subcarrier spacing, each time slot can include a variable number of symbol time periods (e.g., 7 or 14 symbols). The symbol time periods within each time slot can be assigned an index. A mini-time slot is a sub-time slot structure (e.g., 2, 3, or 4 symbols).

[0075] Each symbol in a time slot can indicate the link direction used for data transmission (e.g., DL, UL, or a flexible direction), and the link direction can be dynamically switched for each subframe. The link direction can be based on the time slot format. Each time slot can include DL / UL data as well as DL / UL control information.

[0076] In NR, synchronization signal blocks (SSBs) are transmitted. In some respects, SSBs can be transmitted in bursts, where each SSB in the burst corresponds to a different beam direction used for UE-side beam management (e.g., including beam selection and / or beam optimization). SSBs include PSS, SSS, and dual-symbol PBCH. SSBs can be transmitted at fixed time slot locations, such as... Figure 6The symbols 0-3 are shown. The UE can use PSS and SSS for cell search and acquisition. PSS provides half-frame timing, and SS provides CP length and frame timing. PSS and SSS can provide cell identification. PBCH carries basic system information such as DL system bandwidth, intra-radio frame timing information, SS burst set period, and system frame number. SSB can be organized into SS bursts to support beam scanning. Other system information, such as Residual Minimum System Information (RMSI), System Information Block (SIB), and Other System Information (OSI), can be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes. An SSB can be transmitted up to 64 times; for example, for mmWave, there can be up to 64 different beam directions. Multiple transmissions of an SSB are called SS burst sets. SSBs in an SS burst set can be transmitted in the same frequency region, while SSBs in different SS burst sets can be transmitted in different frequency regions.

[0077] like Figure 7 As shown, SSBs can be organized into SS burst sets to support beam scanning. Different beams can be used to transmit each SSB in the burst set, which helps the UE quickly acquire the transmit (TX) and receive (RX) beams (especially for mmW applications). The Physical Cell Identifier (PCI) can be decoded from the PSS and SSS of the SSB.

[0078] Some deployment scenarios may include one or two NR deployment options. Some may be configured as non-standalone (NSA) and / or standalone (SA) options. A standalone cell may need to broadcast both the SSB and RMSI simultaneously, for example, using two SIBs (e.g., SIB1 and SIB2). A non-standalone cell may only need to broadcast the SSB without broadcasting the RMSI. In a single NR carrier, multiple SSBs can be transmitted on different frequencies and can include different types of SSBs.

[0079] Control resource set (CORESET)

[0080] A control resource set (CORESET) for an Orthogonal Frequency Division Multiple Access (OFDMA) system (e.g., a communication system that uses OFDMA waveforms to transmit the Physical Downlink Control Channel (PDCCH)) may include one or more sets of control resources (e.g., time and frequency resources) configured to transmit the PDCCH within the system bandwidth. Within each CORESET, one or more search spaces (e.g., a common search space (CSS), a UE-specific search space (USS), etc.) may be defined for a given user equipment (UE). A search space can be an area or portion in which a communication device (e.g., a UE) can search for control information.

[0081] According to aspects of this disclosure, a CORESET is a collection of time-domain and frequency-domain resources, defined in units of Resource Element Groups (REGs). Each REG may include a fixed number (e.g., twelve) of tones within a symbol time period (e.g., a symbol time period of a time slot), where one tone within a symbol time period is referred to as a Resource Element (RE). The fixed number of REGs may be included in Control Channel Elements (CCEs). A set of CCEs may be used to transmit New Radio PDCCH (New Radio (NR) PDCCH (NR-PDCCH)), using different aggregation levels, with different numbers of CCEs in the set used for transmitting NR-PDCCH. A multi-set CCE may be defined as the UE's search space, so that a Node B or other base station (BS) can transmit NR-PDCCH to the UE by transmitting NR-PDCCH within a CCE set, which may be defined as decoding candidates within the UE's search space, and the UE can receive NR-PDCCH by searching within the UE's search space and decoding the NR-PDCCH transmitted by the Node B (or other BS).

[0082] The operational characteristics of a Node B or other Base Station (BS) in an NR communication system may depend on the frequency range (FR) in which the system operates. The FR may include one or more operating frequency bands (e.g., the “n1” band, “n2” band, “n7” band, and “n41” band), and the communication system (e.g., one or more BSs / Node Bs and UEs) may operate within one or more operating frequency bands. Frequency ranges and operating frequency bands are described in more detail in the Technical Specification (TS) 38.104 (Revision 15) for Radio Transmission and Reception of Base Stations (BSs), which is available from the 3GPP website.

[0083] As described above, a CORESET can be a collection of time-domain and frequency-domain resources. A CORESET can be configured to transmit PDCCH within the system bandwidth. The UE can determine and monitor the CORESET used for the control channel. During initial access, the UE can identify the initial CORESET (CORESET#0) configuration from a field in the Master Information Block (MIB) (e.g., pdcchConfigSIB1). This initial CORESET can then be used to configure the UE (e.g., via dedicated (UE-specific) signaling along with other CORESETs and / or Bandwidth Parts (BWPs)). When the UE detects a control channel in a CORESET, the UE can attempt to decode the control channel and communicate with the transmitting base station (e.g., the transmitting cell) based on the control data provided in the control channel (e.g., transmitted via the CORESET).

[0084] According to aspects of this disclosure, when a UE connects to a cell (or BS), the UE can receive a Media Injection Block (MIB). The MIB can reside in a synchronization signal and physical broadcast channel (SS / PBCH) block on a synchronization raster (e.g., within the PBCH of the SS / PBCH block). In some cases, the synchronization raster may correspond to an SSB. Based on the frequency of the synchronization raster, the UE can determine the operating frequency band of the cell. Based on the operating frequency band of the cell, the UE can determine the minimum channel bandwidth and the channel subcarrier spacing (SCS). The UE can then determine an index from the MIB (e.g., a four-bit index in the MIB representing an index in the range of 0-15).

[0085] Given this index, the UE can look up or locate a CORESET configuration (this initial CORESET configured via the MIB is typically referred to as CORESET#0). This can be done from one or more CORESET configuration tables. These configurations (including scenarios with a single table) may comprise multiple subsets of the index, which indicate valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of the index in the table.

[0086] Alternatively or additionally, the UE can select a search space CORESET configuration table from several CORESET configuration tables. These configurations can be based on minimum channel bandwidth and SCS. The UE can then look up the CORESET configuration from the selected table based on an index (e.g., Type 0-PDCCH search space CORESET configuration). After determining the CORESET configuration (e.g., from a single table or a selected table), the UE can determine the CORESET to monitor based on the location (in time and frequency) of the SS / PBCH block and the CORESET configuration (as described above).

[0087] Figure 8 An exemplary transport resource mapping 800 according to certain aspects of this disclosure is shown. In the exemplary transport resource mapping 800, the BS (e.g., Figure 1 The BS110a) shown in the wireless communication network 100 transmits SS / PBCH block 802. SS / PBCH block 802 may include a MIB that indexes a table that associates the time and frequency resources of CORESET 804 with the time and frequency resources of SS / PBCH block 802.

[0088] The BS can also send control signaling. In some scenarios, the BS can send control signaling to the UE (e.g., within the CORESET (time / frequency resources)). Figure 1In the wireless communication network 100, the UE 120a) transmits a PDCCH. The PDCCH can schedule PDSCH 806. The BS can then transmit the PDSCH to the UE. The UE can receive the MIB, determine the index, look up the CORESET configuration based on the index in the SS / PBCH block 802, and determine the CORESET according to the CORESET configuration and the SS / PBCH block 802. The UE can then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH 806 allocated via the PDCCH.

[0089] Different CORESET configurations may have different parameters that define the corresponding CORESET. For example, each configuration may indicate the number of resource blocks (RBs) (e.g., 24, 48, or 96), the number of symbols (e.g., 1–3), and may indicate the offset of the position in the frequency (e.g., 0–38 RBs).

[0090] Quasi-Cooperative Positioning (QCL) Port and Transport Configuration Indicator (TCI) Status

[0091] In many cases, it may be important for the User Equipment (UE) to understand what assumptions it can make on channels corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode transmitted signals (e.g., Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH)). It may also be important for the UE to be able to report relevant Channel State Information (CSI) to the Base Station (BS) (or gNB) for scheduling, link adaptation, and / or beam management purposes. In New Radio (NR), the concepts of Quasi-Cooperative Positioning (QCL) and Transmission Configuration Indicator (TCI) states can be used to convey information about these assumptions.

[0092] The QCL assumption can be defined based on channel attributes. According to 3GPP Technical Specification (TS) 38.214, “If the attributes of a channel on which symbols are transmitted on one of two antenna ports can be inferred from the attributes of a channel on which symbols are transmitted on the other of two antenna ports, then the two antenna ports can be said to be quasi-co-located.” If the receiver (e.g., the UE) can apply the channel attributes determined by detecting a first reference signal (RS) to help detect a second RS, then the different reference signals can be considered quasi-co-located (“QCL”). TCI states typically include configurations such as, for example, the QCL relationship between downlink (DL) RSs and PDSCH demodulation reference signal (DMRS) ports in a CSI-RS set.

[0093] In some cases, a UE can be configured with up to M TCI states. The configuration of the M TCI states can be achieved via higher-layer signaling, and the UE can be signaled to decode the PDSCH based on the detected PDCCH containing downlink control information (DCI) indicating one of the TCI states. Each configured TCI state can include a TCIRS-SetConfig of an RS set, which indicates different QCL assumptions between specific source and target signals.

[0094] Figure 9 Example QCL relationships are shown according to certain aspects of this disclosure. More specifically, Figure 9 An example of the association between DL RS and the corresponding QCL type that can be indicated by TCI-RS-SetConfig is shown.

[0095] exist Figure 9 In the example, the source RS can be indicated in the top block and can be associated with the target signal indicated in the bottom block. In this context, the target signal can refer to a signal whose channel properties can be inferred by measuring those channel properties associated with the source signal. As mentioned above, the UE can use the source RS to determine various channel parameters, depending on the associated QCL type. Furthermore, the UE can use those different channel parameters (determined based on the source RS) to process the target signal. The target RS does not necessarily need to be the DMRS of the PDSCH, but can be any other RS: Physical Uplink Shared Channel (PUSCH) DMRS, CSI-RS, Tracking Reference Signal (TRS), and Sounding Reference Signal (SRS).

[0096] As shown in the figure, each TCI-RS-SetConfig can contain parameters. For example, these parameters can configure the QCL relationship between the RSs in the RS set and the DMRS port group of the PDSCH. The RS set can contain references to one or two DL RSs and the associated QCL-Type (QCL type) of each configured by the higher-level parameter QCL-Type.

[0097] like Figure 9 As shown, the QCL type can be arranged in several ways for the case of two DL RSs. For example, the QCL types may be different regardless of whether the reference is for the same DL RS or different DL RSs. In the example shown, the SSB can be associated with a type C QCL for the phase tracking reference signal (P-TRS), while the CSI-RS (CSIRS-BM) for beam management can be associated with a type D QCL.

[0098] In some cases, QCL information and / or type may depend on other information or a function of other information. For example, the QCL type indicated to the UE may be based on a higher-level parameter QCL-Type and may take one or a combination of the following types:

[0099] QCL-Type A (Type A QCL): {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0100] QCL-Type B (Type B QCL): {Doppler frequency shift, Doppler spread}

[0101] QCL-Type C (C-type QCL): {Average delay, Doppler shift}, and

[0102] QCL-TypeD (D-type QCL): {Spatial reception parameters}

[0103] Spatial QCL assumption (QCL-TypeD) can be used to help the UE select the analog receive (RX) beam (e.g., during beam management procedures). For example, an SSB resource indicator can indicate that the same beam from a previous RS should be used for subsequent transmissions.

[0104] The initial CORESET in the NR (e.g., CORESET ID 0 or simply CORESET#0) can be identified during the UE's initial access (e.g., via a field in the MIB). The ControlResourceSet Information Element (CORESET IE), transmitted via Radio Resource Control (RRC) signaling, can convey information about the CORESET configured for the UE. The CORESET IE may include the CORESET ID, an indication of the frequency domain resources (e.g., the number of RBs) allocated to the CORESET, the consecutive duration of the CORESET across multiple symbols, and the TCI status.

[0105] As described above, a subset of TCI states provides a QCL relationship between the DL RS and the PDCCHDMRS ports in a set of RSs (e.g., TCI-Set). A specific TCI state for a given UE (e.g., unicast PDCCH) can be transmitted to the UE via a Media Access Control (MAC) control element (MAC CE). A specific TCI state can be selected from a set of TCI states transmitted via the CORESET IE, with the initial CORESET (CORESET#0) typically configured via the MIB.

[0106] Search space information can also be provided via RRC signaling. For example, a search space IE can be another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space may be associated with a CORESET. The search space IE can be identified by the search space ID configured for the CORESET. In one aspect, the search space ID associated with CORESET#0 could be search space ID#0. Search spaces can be configured via PBCH (MIB).

[0107] Application beaming example updated before transmission time is triggered.

[0108] Certain aspects of this disclosure provide techniques for determining when to apply beam updates.

[0109] Various timings can be defined for application beams that are updated before the triggered transmission time. For example, Figure 12 This is a timing diagram used to determine whether to apply beam updates, based on certain aspects of this disclosure. For example... Figure 12 As shown, T1 can refer to the end of the downlink control information (DCI) for scheduling downlink (DL) or uplink (UL) transmissions (e.g., Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Aperiodic Channel State Information Reference Signal (AP CSI-RS), Aperiodic Sounding Reference Signal (AP SRS)). T2 can refer to the start time of the DL or UL transmission scheduled by the DCI (which ends at T1). Typically, in some respects, T2 must be greater than T1. T3 can refer to the application time of the beam update for the scheduled transmission, which can be updated by a previously transmitted Medium Access Control (MAC) control element (CE). For example, T3 can be 3 milliseconds (ms) after the user equipment (UE) finishes acknowledging (ACK) the PDSCH carrying the updated beam to the MAC-CE.

[0110] In some cases, the beam can be indicated via the Transmission Configuration Indicator (TCI) status, spatial relationship, or UL TCI status.

[0111] In some cases, if the application time (T3) of the beam update for the scheduled transmission is between the scheduled DCI (T1) and the scheduled transmission (T2) (e.g., if T3 occurs between T1 and T2, such as...), Figure 12 If the time between T3 and T2 is too short, the UE may not have enough time to apply the updated beam to the scheduled transmission.

[0112] This disclosure provides various techniques to illustrate when beam updates can be applied in this situation.

[0113] Figure 10 This is a flowchart illustrating an example operation 1000 of a UE performing wireless communication according to certain aspects of this disclosure. Operation 1000 can be performed, for example, by a UE 120a in a wireless communication network 100. Operation 1000 can be implemented in one or more processors (e.g., Figure 2 The software components that execute and operate on the controller / processor 280. Furthermore, they can be accessed via, for example, one or more antennas (e.g., Figure 2 The antenna 252) enables the UE to transmit and receive signals during operation 1000. In some respects, the UE's transmission and / or reception of signals may be achieved via a bus interface that acquires and / or outputs signals from one or more processors (e.g., controller / processor 280).

[0114] Operation 1000 can begin in box 1002 when the UE receives signaling indicating a beam update.

[0115] In box 1004, the UE determines that the beam update application time occurs between the scheduled transmission's DCI and the scheduled transmission.

[0116] In box 1006, the UE decides whether to apply beam updates to scheduled transmissions.

[0117] Figure 11 This is a flowchart illustrating an example operation 1100 of wireless communication performed by a network entity according to certain aspects of this disclosure. For example, operation 1100 may be performed by a base station (BS) (e.g., BS110a, such as in wireless communication network 100). Operation 1100 may supplement operation 1000 performed by a UE. Operation 1100 may be implemented in one or more processors (e.g., Figure 2 The software components that execute and operate on the controller / processor 240. Furthermore, they can be accessed via, for example, one or more antennas (e.g., Figure 2 The antenna 234 enables the BS to transmit and receive signals in operation 1100. In some respects, the BS can transmit and / or receive signals via a bus interface of the acquire and / or output signals of one or more processors (e.g., controller / processor 240).

[0118] Operation 1100 can begin in box 1102 by signaling the UE with an indication of beam update.

[0119] In box 1104, the network entity determines that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission.

[0120] In box 1106, the network entity decides whether to apply beam updates to scheduled transmissions.

[0121] According to certain aspects, when the application time of beam update occurs after the scheduled DCI (e.g., T1) and before the DL / UL transmission scheduled by the DCI (e.g., T2), the updated beam may not be applied to the scheduled transmission at which the updated beam is applied (e.g., T1). Figure 12 The scenario shown, where T3 occurs between T1 and T2, can be considered invalid.

[0122] In some cases, beam updates can be indicated via TCI status, spatial relation, or UL TCI status.

[0123] In some cases, beam updates can be indicated via MAC-CE. For MAC-CE-based beam updates, the application time for the updated beam can be 3ms after the ACK feedback of the PDSCH of the MAC-CE carrying the updated beam ends.

[0124] According to some aspects, when the beam update is applied after the scheduled DCI (e.g., T1) and in the DCI where the updated beam is applied (e.g., Figure 12 The scenario shown in T3 between T1 and T2 can be considered valid) before the scheduled DL / UL transmission (e.g., T2), when an updated beam can be applied.

[0125] In some cases, if the duration between the application time of the updated beam and the start of the scheduled transmission (e.g., the duration between T2 and T3) exceeds a minimum duration, the updated beam may be applied to the scheduled transmission. Otherwise, the beam initially configured before the beam update may continue to be applied to the scheduled transmission.

[0126] In some cases, the minimum duration can be a fixed value. For example, the minimum duration can be a fixed value of zero.

[0127] In some cases, the minimum duration can be at least partially based on UE capabilities.

[0128] In some cases, the minimum duration may further depend on the scheduled component carrier (CC) and the subcarrier spacing (SCS) of the scheduled CC. For example, the minimum duration may depend at least in part on the SCS of the first CC of the DCI and the second CC of the scheduled transmission. In some examples, the minimum duration may be based on the minimum SCS of the first and second CCs. For example, if the minimum SCS of the scheduled CC and the scheduled CC is 120 kHz, then the minimum duration based on the minimum SCS could be 28 symbols.

[0129] Depending on the aspect, DCI can schedule multiple DL / UL transmissions in each transmission using the same or different beams (e.g., each SRS resource uses the same or different beams, and DCI triggers transmissions of multiple aperiodic (AP) probe reference signal (SRS) resources).

[0130] In some cases, the indicated beam for each transmission in the DCI can be based on the updated beam from each transmission prior to the start of the first transmission. For example, in the case of multiple transmissions scheduled by the DCI, if a previous MAC-CE update of the beam for the third SRS resource of the third transmission scheduled by the DCI and the corresponding application time of the new beam (e.g., T3 of the third SRS resource) is after the start of the first transmission scheduled by the DCI (e.g., after T2 of the first SRS resource), the UE can continue to use the beam applied before the update for the third transmission of the third SRS resource.

[0131] In some cases, the indicated beam for each transmission in the DCI can be based on an updated beam for each transmission prior to the first transmission or before the start of the corresponding transmission. For example, in the case of multiple transmissions scheduled by the DCI, if a previous MAC-CE update is used for the beam of the third SRS resource of the third transmission scheduled by the DCI, and the corresponding application time of the new beam (e.g., T3 of the third SRS resource) is after the start of the first transmission scheduled by the DCI (e.g., after T2 of the first SRS resource) but before the start of the third transmission (e.g., before T2 of the third SRS resource), the UE can use the updated beam for the third transmission of the third SRS resource.

[0132] According to some aspects, when the spatial relationship of AP SRS is updated via MAC-CE and the HARQ-ACK corresponding to MAC-CE is sent in slot n, the updated spatial relationship can be effective from slot n+3ms.

[0133] In some cases, the activity space relationship at the start of an AP SRS transmission or at the start of a time slot in an AP SRS transmission can be applied to the scheduled AP SRS transmission.

[0134] In some cases, the active space relation at the beginning of the PDCCH that triggers the AP SRS transmission or at the beginning of the time slot of the PDCCH that triggers the AP SRS transmission can be applied to the AP SRS transmission.

[0135] In some respects, the decision to apply the active space relation at the start of the AP SRS transmission (or at the start of the AP SRS transmission time slot) or at the start of the PDCCH that triggers the AP SRS transmission (or at the start of the PDCCH time slot that triggers the AP SRS transmission) can be based on the UE's capabilities.

[0136] In some cases where the UE is capable of deciding whether to apply beam updates to scheduled transmissions, the UE or network entity may decide to apply beam updates to scheduled transmissions or to apply previous beams to scheduled transmissions, wherein the previous beams have an application time that occurred at or before the start of the DCI or DCI time slot of the scheduled transmission.

[0137] For example, a first UE may have the capability to use the active spatial relationship when the PDCCH triggers the AP SRS transmission (at the beginning of the PDCCH or at the beginning of the PDCCH time slot), while a second UE may have the capability to allow the use of the active spatial relationship when the AP SRS transmission begins (at the beginning of the AP SRS transmission or at the beginning of the AP SRS transmission time slot).

[0138] Figure 13 The illustration may include operations configured to perform the techniques disclosed herein (such as...) Figure 13 The communication device 1300 comprises various components (e.g., corresponding to device plus functional components) of the operation shown herein. The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or receiver). The transceiver 1308 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1300 via an antenna 1310. The processing system 1302 may be configured to perform processing functions of the communication device 1300, including processing the signals received and / or transmitted by the communication device 1300.

[0139] Processing system 1302 includes processor 1304 coupled to computer-readable medium / memory 1312 via bus 1306. In some aspects, computer-readable medium / memory 1312 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1304, cause processor 1304 to perform... Figure 10The operations shown may be other operations used to perform the various techniques for beam updating discussed herein. In some aspects, the computer-readable medium / memory 1312 stores code 1314 for receiving (e.g., for receiving signaling indicating a beam update), code 1316 for determining (e.g., for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission), and code 1318 for deciding (e.g., for deciding whether to apply the beam update to the scheduled transmission), etc. In some aspects, the processor 1304 has circuitry configured to execute the code stored in the computer-readable medium / memory 1312. The processor 1304 includes circuitry 1324 for receiving (e.g., for receiving signaling indicating a beam update); circuitry 1326 for determining (e.g., for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission); and circuitry 1328 for deciding (e.g., for deciding whether to apply the beam update to the scheduled transmission), etc.

[0140] Figure 14 The illustration may include operations configured to perform the techniques disclosed herein (such as...) Figure 11 The communication device 1400 comprises various components (e.g., corresponding to device plus functional components) of the operation shown herein. The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or receiver). The transceiver 1408 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1400 via an antenna 1410. The processing system 1402 may be configured to perform processing functions of the communication device 1400, including processing the signals received and / or transmitted by the communication device 1400.

[0141] Processing system 1402 includes processor 1304 coupled to computer-readable medium / memory 1412 via bus 1406. In some aspects, computer-readable medium / memory 1412 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1404, cause processor 1404 to perform... Figure 11The operations shown may be other operations used to perform the various techniques for beam updates discussed herein. In some aspects, the computer-readable medium / memory 1412 stores code 1414 for signaling notification (e.g., for signaling an indication of beam update to the UE); code 1416 for determining (e.g., for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission); and code 1418 for deciding (e.g., for deciding whether to apply the beam update to the scheduled transmission). In some aspects, the processor 1404 has circuitry configured to execute the code stored in the computer-readable medium / memory 1412. The processor 1404 includes circuitry 1424 for signaling notification (e.g., for signaling an indication of beam update to the UE); circuitry 1426 for determining (e.g., for determining that the application time of the beam update occurs between the DCI of the scheduled transmission and the scheduled transmission); and circuitry 1428 for deciding (e.g., for deciding whether to apply the beam update to the scheduled transmission), etc.

[0142] Example

[0143] Aspect 1: A method for wireless communication by a user equipment (UE), comprising: receiving signaling indicating a beam update; determining that the application time of the beam update occurs between downlink control information (DCI) of a scheduled transmission and the scheduled transmission; and deciding whether to apply the beam update to the scheduled transmission.

[0144] Aspect 2: According to the method of aspect 1, wherein if one or more conditions are met, the UE decides to apply beam updates to the scheduled transmission.

[0145] Aspect 3: According to the method of aspect 2, one or more conditions include that the time between the application time of the beam update and the start of the scheduled transmission is at least a minimum duration.

[0146] Aspect 4: According to the method of aspect 3, the minimum duration includes a fixed value.

[0147] Aspect 5: The method according to aspect 3 or 4, wherein the minimum duration includes a value based on UE capabilities.

[0148] Aspect 6: The method according to any one of Aspects 3-5, wherein the minimum duration depends at least in part on the subcarrier spacing (SCS) of at least one of the following: the first component carrier (CC) of the DCI or the second CC of the scheduled transmission.

[0149] Aspect 7: The method according to aspect 6, wherein the minimum duration is based on the minimum SCS in the first and second CCs.

[0150] Aspect 8: The method according to any one of Aspects 1-7, wherein the UE decides not to apply beam updates to the scheduled transmission.

[0151] Aspect 9: The method according to any one of Aspects 1-8, wherein beam updates are indicated via Transmission Configuration Indicator (TCI) status.

[0152] Aspect 10: The method according to any one of aspects 1-9, wherein beam updates are indicated via spatial relations.

[0153] Aspect 11: The method according to any one of Aspects 1-10, wherein beam updates are indicated via the uplink (UL) transmission configuration indicator (TCI) status.

[0154] Aspect 12: The method according to any one of Aspects 1-11, wherein the beam update is indicated via a Medium Access Control (MAC) Control Element (CE) (MAC-CE); and the application time of the beam update is a fixed duration after the acknowledgment of the Physical Downlink Shared Channel (PDSCH) carrying the MAC-CE has ended.

[0155] Aspect 13: The method according to any one of Aspects 1-12, wherein: DCI schedules multiple transmissions; and the decision to apply beam updates to the first scheduled transmission among the multiple scheduled transmissions is also applied to the other scheduled transmissions among the multiple scheduled transmissions.

[0156] Aspect 14: The method according to any one of Aspects 1-13, wherein: DCI schedules multiple transmissions; and the UE decides individually for each scheduled transmission whether to apply beam updates to each scheduled transmission.

[0157] Aspect 15: The method according to aspect 14, wherein the decision on whether to apply beam updates to each scheduled transmission is based on at least one of the following: whether the application time of beam updates for each scheduled transmission is after the start of the scheduled transmission of the first transmission among a plurality of scheduled transmissions, wherein the first transmission is the first scheduled transmission among a plurality of scheduled transmissions; and whether the application time of beam updates for each scheduled transmission is before each corresponding scheduled transmission.

[0158] Aspect 16: The method according to any one of Aspects 1-15, wherein a decision is made based on the capabilities of the UE to apply a beam update to the scheduled transmission; the UE decides to apply a beam update to the scheduled transmission or to apply a previous beam to the scheduled transmission, wherein the previous beam has an application time that occurred at or before the start of the DCI or the time slot of the scheduled transmission.

[0159] Aspect 17: The method according to any one of aspects 1-16 further includes: transmitting an indication of the capabilities of the UE.

[0160] Aspect 18: A method for wireless communication by a network entity, comprising: signaling a user equipment (UE) to notify of an indication of a beam update; determining that the application time of the beam update occurs between downlink control information (DCI) of a scheduled transmission and the scheduled transmission; and deciding whether to apply the beam update to the scheduled transmission.

[0161] Aspect 19: According to the method of aspect 18, wherein if one or more conditions are met, the network entity decides to apply beam updates to the scheduled transmissions.

[0162] Aspect 20: The method according to aspect 19, wherein one or more conditions include the time between the application time of beam update and the start of scheduled transmission being at least a minimum duration.

[0163] Aspect 21: The method according to aspect 20, wherein the minimum duration includes a fixed value.

[0164] Aspect 22: The method according to aspect 20 or 21, wherein the minimum duration includes a value based on UE capabilities.

[0165] Aspect 23: The method according to any one of Aspects 20-22, wherein the minimum duration depends at least in part on the subcarrier spacing (SCS) of at least one of the following: the first component carrier (CC) of the DCI or the second CC of the scheduled transmission.

[0166] Aspect 24: According to the method of aspect 23, wherein the minimum duration is based on the minimum SCS in the first and second CCs.

[0167] Aspect 25: The method according to any one of Aspects 18-24, wherein: DCI schedules multiple transmissions; and the decision to apply beam updates to the first scheduled transmission among the multiple scheduled transmissions is also applied to the other scheduled transmissions among the multiple scheduled transmissions.

[0168] Aspect 26: The method according to any one of Aspects 18-25, wherein: DCI schedules multiple transmissions; and the network entity decides individually for each scheduled transmission whether to apply beam updates to each scheduled transmission.

[0169] Aspect 27: According to the method of aspect 26, the decision on whether to apply beam updates to each scheduled transmission is based on at least one of the following: whether the application time of the beam update for each scheduled transmission is after the start of the scheduled transmission of the first transmission in a plurality of scheduled transmissions, wherein the first transmission is the first scheduled transmission in a plurality of scheduled transmissions; and whether the application time of the beam update for each scheduled transmission is before each corresponding scheduled transmission.

[0170] Aspect 28: The method according to any one of Aspects 18-27 further includes: receiving an indication of the capability of the UE, wherein a decision is made based on the capability of the UE to apply a beam update to the scheduled transmission; and the network entity decides to apply a beam update to the scheduled transmission or to apply a previous beam to the scheduled transmission, wherein the previous beam has an application time that occurs at or before the start of the DCI or the time slot of the DCI of the scheduled transmission.

[0171] Aspect 29: An apparatus for wireless communication by a user equipment (UE), comprising: a memory; at least one processor coupled to the memory and configured to: receive signaling indicating a beam update; determine that the application time of the beam update occurs between downlink control information (DCI) of a scheduled transmission and the scheduled transmission; and decide whether to apply the beam update to the scheduled transmission.

[0172] Aspect 30: An apparatus for wireless communication by a network entity, comprising: a memory; at least one processor coupled to the memory and configured to: signal a beam update indication to a user equipment (UE); determine that the beam update application occurs between downlink control information (DCI) of a scheduled transmission and the scheduled transmission; and decide whether to apply the beam update to the scheduled transmission.

[0173] Other considerations

[0174] The methods disclosed herein include one or more steps or actions for implementing the method. The method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0175] As used herein, the phrase “at least one” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a and b, a and c, b and c, and a and b and c, as well as any combination with multiple identical elements (e.g., a and a, a and a and a, a and a and b, a and a and c, a and b and b, a and c and c, b and b, b and b and b, b and b and c, c and c, and c and c and c or any other ordering of a, b and c).

[0176] As used herein, the term "determine" encompasses a variety of actions. For example, "determine" can include calculation, processing, derivation, investigation, searching (e.g., looking in a table, database, or other data structure), assertion, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determine" can include solving, selecting, picking, building, etc.

[0177] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language of the claims, wherein an element referred to in the singular is not intended to mean “one and only one,” but rather “one or more” unless otherwise expressly stated. Unless otherwise expressly stated, the term “some” means one or more. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or will be known hereafter to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. According to 35 U.SC §112(f), unless the element is expressly stated using the phrase “component for…” or, in the case of a method claim, referred to using the phrase “step for…”, the element is considered.

[0178] The various operations described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, in the case of operations as shown in the figures, these operations may have corresponding components with similar numbering, plus functional components.

[0179] The various illustrative logic blocks, modules, and circuits described in this disclosure can be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination of the foregoing components designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0180] If implemented in hardware, the example hardware configuration could include a processing system in a wireless node. The processing system can be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus can include any number of interconnect buses and bridges. The bus can link various circuits together, including processors, machine-readable media, and bus interfaces. The bus interface can be used to connect network adapters, etc., to the processing system via the bus. The network adapter can be used to implement signal processing functions at the PHY layer. In user terminal 120 (see...) Figure 1 In this case, the user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. The bus can also link various other circuits known in the art (such as timing sources, peripherals, voltage regulators, power management circuits, etc.), and therefore will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how best to implement the described functions for the processing system, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0181] If implemented in software, the functionality can be stored or transmitted as one or more instructions or code on a computer-readable medium. Software should be interpreted broadly as instructions, data, or any combination thereof, whether referring to software, firmware, middleware, microcode, hardware description languages, or others. Computer-readable media includes computer storage media and communication media, with communication media including any medium that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. As an example, machine-readable media may include transmission lines, data-modulated carrier waves, and / or computer-readable storage media (on which instructions are stored separately from the wireless node), all of which can be accessed by the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as in cases where it may have a cache and / or a general-purpose register file. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media or any combination thereof. Machine-readable media may be embedded in computer program products.

[0182] Software modules can comprise a single instruction or a number of instructions, and can be distributed across several different code segments, different programs, and multiple storage media. Computer-readable media can include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules can include sending modules and receiving modules. Each software module can reside in a single storage device or be distributed across multiple storage devices. For example, a software module can be loaded from a hard disk drive into RAM when a triggering event occurs. During the execution of a software module, the processor can load some instructions into a cache to improve access speed. One or more cache lines can then be loaded into a general-purpose register file for the processor to execute. When the functionality of a software module is referred to below, it should be understood that this functionality is implemented by the processor when executing instructions from that software module.

[0183] Furthermore, any connection is properly referred to as computer-readable medium. 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 (IR), radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of medium. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and... Disks, where magnetic disks typically reproduce data magnetically, and optical disks optically reproduce data using lasers. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include temporary computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0184] Therefore, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium on which instructions are stored (and / or encoded) that can be executed by one or more processors to perform the operations described herein. Figure 10 and 11 The instructions for the operation are shown in the image.

[0185] Furthermore, it should be understood that modules and / or other suitable components for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by the user terminal and / or base station, if applicable. For example, such a device may be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein may be provided via storage devices (e.g., RAM, ROM, physical storage media such as CDs or floppy disks), such that the user terminal and / or base station can obtain the various methods when the storage device is coupled or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device may be used.

[0186] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the above-described methods and apparatus without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Receive signaling indicating beam update; Determine whether the application time of the beam update occurs between the downlink control information (DCI) of the scheduled transmission and the scheduled transmission; and In response to the determination that the application time of the beam update occurs between the DCI that schedules the transmission and the scheduled transmission, a decision is made on whether to apply the beam update to the scheduled transmission based on the time between the application time of the beam update and the start of the scheduled transmission.

2. The method according to claim 1, wherein, The time between the application time of the beam update and the start of the scheduled transmission is at least the minimum duration.

3. The method according to claim 2, wherein, The minimum duration includes a fixed value.

4. The method of claim 3, wherein the fixed value is zero.

5. The method according to claim 2, wherein, The minimum duration includes a value based on UE capabilities.

6. The method according to claim 2, wherein, The minimum duration depends at least in part on the subcarrier spacing SCS of at least one of the following: the first component carrier CC of the DCI or the second CC of the scheduled transmission.

7. The method according to claim 6, wherein, The minimum duration is based on the minimum SCS in the first and second CCs.

8. The method according to claim 1, wherein, The UE decides not to apply the beam update to the scheduled transmission.

9. The method according to claim 1, wherein, The beam update is indicated via the Transmission Configuration Indicator (TCI) status.

10. The method according to claim 1, wherein, The beam update is indicated via spatial relationships.

11. The method according to claim 1, wherein, The beam update is indicated via the uplink UL transport configuration indicator (TCI) status.

12. The method according to claim 1, wherein, The beam update is indicated via the Medium Access Control (MAC) control element CE, MAC-CE; and The application time of the beam update is a fixed duration after the acknowledgment of the Physical Downlink Shared Channel (PDSCH) carrying the MAC-CE ends.

13. The method according to claim 1, wherein: The DCI schedules multiple transmissions; and The decision to apply the beam update to the transmission of the first scheduled transmission among the plurality of scheduled transmissions is also applied to the transmissions of the other scheduled transmissions among the plurality of scheduled transmissions.

14. The method according to claim 1, wherein: The DCI schedules multiple transmissions; and The UE determines whether to apply the beam update to each scheduled transmission.

15. The method according to claim 14, wherein, The decision to apply the beam update to each scheduled transmission is based on at least one of the following: Whether the application time of the beam update for each scheduled transmission is after the start of the scheduled transmission of the first transmission among the plurality of scheduled transmissions; and Whether the beam update is applied before each corresponding scheduled transmission.

16. The method according to claim 1, wherein, The decision to apply the beam update to the scheduled transmission is based on the UE's capabilities; and The UE decides to apply the beam update to the scheduled transmission or to apply the previous beam to the scheduled transmission, wherein the previous beam has an application time that occurred at or before the start of the DCI or the time slot of the DCI that schedules the transmission.

17. The method according to claim 1, further comprising: Send an indication of the capabilities of the UE.

18. A method for wireless communication by a network entity, comprising: Signal to the User Equipment (UE) to notify of the beam update instruction; Determine whether the application time of the beam update occurs between the downlink control information (DCI) of the scheduled transmission and the scheduled transmission; and In response to the determination that the application time of the beam update occurs between the DCI that schedules the transmission and the scheduled transmission, a decision is made on whether to apply the beam update to the scheduled transmission based on the time between the application time of the beam update and the start of the scheduled transmission.

19. The method according to claim 18, wherein, The time between the application time of the beam update and the start of the scheduled transmission is at least the minimum duration.

20. The method according to claim 19, wherein, The minimum duration includes a fixed value.

21. The method according to claim 19, wherein, The minimum duration includes a value based on UE capabilities.

22. The method according to claim 19, wherein, The minimum duration depends at least in part on the subcarrier spacing SCS of at least one of the following: the first component carrier CC of the DCI or the second CC of the scheduled transmission.

23. The method according to claim 22, wherein, The minimum duration is based on the minimum SCS in the first and second CCs.

24. The method of claim 18, wherein: The DCI schedules multiple transmissions; and The decision to apply the beam update to the transmission of the first schedule among the multiple schedules is also applied to the transmissions of the other schedules among the multiple schedules.

25. The method according to claim 18, wherein: The DCI schedules multiple transmissions; and The network entity decides individually for each scheduled transmission whether to apply the beam update to each scheduled transmission.

26. The method of claim 25, wherein, The decision to apply the beam update to each scheduled transmission is based on at least one of the following: Whether the application time of beam update for each scheduled transmission is after the start of the scheduled transmission of the first transmission among the plurality of scheduled transmissions; and Whether the beam update is applied before each corresponding scheduled transmission.

27. The method of claim 18, further comprising: Receive an indication of the UE's capabilities, wherein whether to apply the beam update to the scheduled transmission is determined based on the UE's capabilities; and The network entity decides to apply the beam update to the scheduled transmission or to apply a previous beam to the scheduled transmission, wherein the previous beam has an application time that occurred at or before the start of the DCI or the time slot of the DCI that schedules the transmission.

28. An apparatus for wireless communication by a user equipment (UE), comprising: Memory; and At least one processor, coupled to the memory and configured to: Receive signaling indicating beam update; Determine whether the application time of the beam update occurs between the downlink control information (DCI) of the scheduled transmission and the scheduled transmission; and In response to the determination that the application time of the beam update occurs between the DCI that schedules the transmission and the scheduled transmission, a decision is made on whether to apply the beam update to the scheduled transmission based on the time between the application time of the beam update and the start of the scheduled transmission.

29. An apparatus for wireless communication by a network entity, comprising: Memory; and At least one processor, coupled to the memory and configured to: Send a signal to the user equipment (UE) to notify it of the beam update instruction; Determine whether the application time of the beam update occurs between the scheduled transmission of downlink control information (DCI) and the scheduled transmission; and In response to the determination that the application time of the beam update occurs between the DCI that schedules the transmission and the scheduled transmission, a decision is made on whether to apply the beam update to the scheduled transmission based on the time between the application time of the beam update and the start of the scheduled transmission.

30. A computer-readable medium storing code for wireless communication by a user equipment, wherein the code is executable by one or more processors of the user equipment to cause the processors to perform the method of any one of claims 1-17.

31. A non-transitory computer-readable medium storing code for wireless communication by a network entity, wherein the code is executable by one or more processors of the network entity. So that the processor performs the method of any one of claims 18-27.

Images