Dci for public tci state update

Abstract

Apparatuses, methods, and computer program products for beam updates are provided. An example method includes receiving DCI. The method also includes determining, based on the DCI, whether the DCI is associated with a beam update for uplink, downlink, or a combination of uplink and downlink. The method also includes determining, from the DCI, a TCI state indicating a beam for the uplink, the downlink, or the combination of uplink and downlink.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 150,887, filed January 15, 2021, entitled “DCI FOR COMMONTCI STATE UPDATE”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically, to wireless communication systems with beam updates. Background Technology

[0004] Wireless communication systems are widely deployed to provide various communication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies, which enable communication with multiple users by sharing available system resources. Such multiple access technologies include 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 Time Division Synchronous Code Division Multiple Access (TD-SCDMA).

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology requires further improvements. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] Below is a simplified overview of one or more aspects to provide a basic understanding of them. This overview is not a comprehensive overview of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some ideas of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, a computer-readable medium, and apparatus at a user equipment (UE) are provided. An example UE may receive downlink control information (DCI). The example UE may determine a transmission configuration indicator (TCI) state based on the DCI, indicating a beam for uplink, downlink, or a combination of uplink and downlink.

[0008] 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 indicate only a few of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is a diagram illustrating an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0015] Figure 4 This is a diagram showing the base station communicating with the UE.

[0016] Figure 5A This is a call flow diagram of signaling between a UE and a base station according to certain aspects of this disclosure.

[0017] Figure 5B Examples of DCIs with different purposes are shown.

[0018] Figure 6 This is a flowchart of a wireless communication method.

[0019] Figure 7This is a flowchart of a wireless communication method.

[0020] Figure 8 This is a diagram illustrating an example of how the hardware implementation of the example device is performed.

[0021] Figure 9 This is a diagram illustrating an example of how the hardware implementation of the example device is performed. Detailed Implementation

[0022] The detailed description set forth below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0023] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in the detailed embodiments below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints of the overall system.

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

[0025] Therefore, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, these functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible to a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0026] In some wireless communication systems, the TCI may include a TCI state comprising at least one source reference signal (RS) to provide a reference (e.g., a basis for UE assumptions) to determine quasi-co-location (QCL) relationships or spatial filters (e.g., beams) for wireless communication. The base station may use the TCI state to indicate beam changes to the UE. Various types of TCI states can be used. For example, a TCI state may indicate a joint downlink (DL) / uplink (UL) common TCI state to indicate a common beam for at least one DL channel or DL ​​RS plus at least one UL channel or UL RS. Another example TCI state may indicate a separate DL common TCI state to indicate a common beam for more than one DL channel or DL ​​RS, e.g., but not for a common beam for a UL channel or UL RS. Yet another example TCI state may indicate a separate UL common TCI state to indicate a common beam for more than one UL channel or UL RS, e.g., but not for a common beam for a DL channel or DL ​​RS. Furthermore, in some aspects, separate TCI states may be used, one for DL ​​and one for UL. For a single DL TCI state, multiple source reference signals from multiple TCIs (e.g., M TCIs, where M is an integer) provide QCL information for UE-dedicated reception on the Physical Downlink Shared Channel (PDSCH) and for all or a subset of the Control Resource Set (CORESET) in the CC. For a single UL TCI, multiple source reference signals from N TCIs (e.g., N is an integer) can provide a reference for determining a common UL TX spatial filter (i.e., beam) for at least all or a subset of the Physical Uplink Shared Channel (PUSCH) and Dedicated Physical Uplink Control Channel (PUCCH) resources in the CC based on Dynamic License / Configuration License. Furthermore, the UL TX spatial filter can also be applied to all SRS resources in the resource set configured for antenna switching / codebook-based / non-codebook-based UL transmissions.

[0027] In some wireless communication systems, under this TCI framework, the DCI can be used to update the beam indication. The DCI indicating the beam update can then be used to further schedule transmissions, such as PDSCH or PUSCH. The aspects provided in this paper enable the DCI to perform beam updates, which can flexibly schedule transmissions or not.

[0028] Figure 1 This diagram illustrates an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0029] Base station 102 configured for 4G LTE (collectively referred to as Evolved Public Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), user and equipment tracking, RAN Information Management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate directly or indirectly with each other via a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0030] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include Home Evolution Node B (eNB) (HeNB), which can provide services to restricted groups referred to as Closed Subscriber Groups (CSGs). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 may use a spectrum bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.), which is allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. Carriers may be adjacent to each other or not. Carrier allocation may be asymmetrical relative to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0031] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0032] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in an unlicensed spectrum, for example, 5 GHz. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0033] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can use NR and uses the same unlicensed spectrum (e.g., 5 GHz) as the Wi-Fi AP 150. Using NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0034] Based on frequency / wavelength, the electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. In 5G NR, two initial operating frequency bands were designated as frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 exceeds 6GHz, FR1 is frequently referred to (interchangeably) as the “Sb-6 GHz” band in various documents and articles. FR2 sometimes faces similar naming issues; although it differs from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally referred to (interchangeably) as the millimeter wave band in documents and articles.

[0035] In light of the foregoing, unless otherwise stated, it should be understood that the terms "sb-6GHz" and the like, if used herein, can broadly refer to frequencies below 6GHz, within FR1, or may include mid-band frequencies. Furthermore, unless otherwise stated, it should be understood that the terms "millimeter wave" and the like, if used herein, can broadly refer to frequencies that may include mid-band frequencies, within FR2, or may include EHF band frequencies.

[0036] Base station 102, whether a small cell 102' or a large-scale (e.g., macro base station), may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the conventional sb-6GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies communicating with UE 104. When gNB 180 operates at millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0037] Base station 180 can transmit beamforming signals to UE 104 in one or more transmit directions 182'. UE 104 can receive beamforming signals from base station 180 in one or more receive directions 182'. UE 104 can also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 can receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 can perform beamforming training to determine the optimal receive and transmit directions for each base station 180 / UE 104. The transmit and receive directions of base station 180 can be the same or different. The transmit and receive directions of UE 104 can be the same or different.

[0038] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), streaming services, and / or other IP services. BM-SC 170 provides functions for MBMS user service provision and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 within broadcast-specific service multicast-broadcast-single-frequency (MBSFN) areas, and is responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0039] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming Media Service (PSS), and / or other IP services.

[0040] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0041] Refer again Figure 1In some aspects, UE 104 may include DCI component 198. In some aspects, DCI component 198 may be configured to receive DCI. In some aspects, DCI component 198 may also be configured to determine, based on DCI, whether DCI is associated with a beam update for the uplink, downlink, or a combination of uplink and downlink. In some aspects, DCI component 198 may also be configured to determine a TCI state based on DCI, indicating the beam used for the uplink, downlink, or a combination of uplink and downlink. Although the following description may be directed to 5G NR, the concepts described herein are applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0042] Figure 2A Figure 200 shows an example of the first subframe within a 5G / NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL, or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2C In the provided example, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE configures the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-static / static configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G / NR frame structure, i.e., TDD.

[0043] Other wireless communication technologies can have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe can include one or more time slots. Subframes can also include smaller time slots, which can contain 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot can contain 7 or 14 symbols. For time slot configuration 0, each time slot can contain 14 symbols, and for time slot configuration 1, each time slot can contain 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set. For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of a parameter set. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the parameter set from 0 to 4. Thus, parameter set μ = 0 has a subcarrier spacing of 15kHz, and parameter set μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 is provided, with 14 symbols per slot, parameter set μ=2, and 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see [link to example]). Figure 2B Each BWP may have a specific set of parameters.

[0044] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0045] like Figure 2AAs shown, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) (denoted as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0046] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., a public search space, a UE-specific search space) during the PDCCH monitoring timing of the CORESET, where PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can reside at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. UE 104 uses the PSS to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the physical layer cell identifier group number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), which carries the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides several RBs and a System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) that is not transmitted through the PBCH, and paging messages.

[0047] like Figure 2CAs shown, some REs carry DM-RS for channel estimation at the base station (denoted as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first one or two symbols preceding the PUSCH. Depending on whether a short or long PUCCH is transmitted, and the specific PUCCH format used, PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of these comb structures. The base station can use SRS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0048] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned according to an indication in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK (NACK)) feedback. The PUCCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0049] Figure 3This is a block diagram of base station 310 communicating with UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via ARQ, connection, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing MAC SDUs to transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0050] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier with its respective spatial stream for transmission.

[0051] At UE 350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are assigned to UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0052] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. At UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0053] Similar to the functions described in the DL transmission description of the base station 310, the controller / processor 359 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to the transmission of upper-layer PDUs, error correction via ARQ, connection, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing MAC SDUs to TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0054] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted from the base station 310 by the channel estimator 358 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use its own spatial stream to modulate an RF carrier for transmission.

[0055] Base station 310 processes UL transmissions in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0056] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0057] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 The aspects related to DCI component 198.

[0058] Figure 4 Figure 400 shows a base station 402 communicating with UE 404. (Reference) Figure 4 Base station 402 can transmit beamforming signals to UE 404 in one or more of the following directions: 402a, 402b, 402c, 402d, 402e, 402f, 402g, and 402h. UE 404 can receive beamforming signals from base station 402 in one or more receiving directions: 404a, 404b, 404c, and 404d. UE 404 can also transmit beamforming signals to base station 402 in one or more of the following directions: 404a-404d. Base station 402 can receive beamforming signals from UE 404 in one or more receiving directions: 402a-402h. Base station 402 / UE 404 can perform beamforming training to determine the optimal receiving and transmitting directions for each base station 402 / UE 404. The transmitting and receiving directions of base station 402 can be the same or different. The transmitting and receiving directions of UE 404 can be the same or different.

[0059] In response to various conditions, such as the DCI for beam updates provided herein, UE 404 may determine, for example, to switch beams between beams 402a-402h, or may determine that the base station will switch between beams. The beam at UE 404 can be used for receiving downlink communications and / or transmitting uplink communications. The beam at base station 402 can be used for uplink receiving and / or downlink transmitting. In some examples, base station 402 may send a transmission that triggers UE 404 to perform a beam switch. For example, base station 402 may indicate a TCI state change, and in response, UE 404 may switch to a new beam for the new TCI state of base station 402. In some instances, the UE may receive a signal from the base station configured to trigger a Transmission Configuration Indication (TCI) state change via, for example, a MAC control element (CE) command. The TCI state change may cause the UE to find the optimal UE receive beam corresponding to the TCI state from the base station and switch to that beam. By ensuring that the transmitter and receiver communicate using appropriately configured beam sets, and by taking into account changing conditions between the base station and the UE and / or movement of the UE or base station, beam switching can improve connectivity between the UE and the base station. In some respects, as provided herein, the base station can send DCI to trigger a change in the UE's TCI state.

[0060] UE 404 can operate using carrier aggregation (CA) and can be configured to communicate with the network via base station 402 using multiple component carriers (CCs). For example, UE 404 can communicate with base station 402 using a primary cell (PCell) and a secondary cell (SCell). Carrier aggregation allows UE 404 to simultaneously transmit and / or receive data from a single base station 402 on multiple CCs. Each aggregated carrier can be referred to as a CC. Carrier aggregation also allows UE 404 to communicate on one or more concurrent beams. The UE can divide CCs into different groups under carrier aggregation. For example, CCs in the same group can use the same beam, while CCs in different groups can use different beams or independent beams. For example, a UE supporting three carriers and two beams can group the first and second CCs into one group using the first beam, and the third CC can use the second beam.

[0061] In some wireless communication systems, the TCI may include a TCI state that includes at least one source RS to provide a reference (e.g., the basis for UE assumptions) to determine the QCL relationship or spatial filter (e.g., beam) used for wireless communication. The base station can use the TCI state to indicate beam changes to the UE. Various types of TCI states can be used. For example, a TCI state (Type 1) may indicate a combined DL or UL common TCI state to indicate a common beam for at least one DL channel or DL ​​RS plus at least one UL channel or UL RS. Another example TCI state (Type 2) may indicate a separate DL common TCI state to indicate a common beam for more than one DL channel or DL ​​RS, e.g., but not for a common beam for a UL channel or UL RS. Yet another example TCI state (Type 3) may indicate a separate UL common TCI state to indicate a common beam for more than one UL channel or UL RS, e.g., but not for a common beam for a UL channel or UL RS. Furthermore, in some aspects, separate TCI states may be used, one for DL ​​and one for UL. For a single DL TCI state, multiple source reference signals from multiple TCIs (e.g., M TCIs, where M is an integer) provide QCL information for at least all or a subset of UE-specific reception on the PDSCH and the CORESET in the CC. For a single UL TCI state, multiple source reference signals from N TCIs (e.g., N is an integer) can provide a reference for determining a common UL TX spatial filter (i.e., beam) for at least all or a subset of dedicated PUCCH resources in the CC, based on dynamic licensing / configuration licensing. Furthermore, the UL TX spatial filter can also be applied to all SRS resources in the resource set configured for antenna switching / codebook-based / non-codebook-based UL transmissions.

[0062] In some wireless communication systems, base stations can transmit DCI to update beam indications within a TCI framework, such as a unified TCI framework that includes a common beam indication. DCI can also schedule transmissions such as PDSCH or PUSCH. The aspects provided herein enable DCI to perform beam updates that can flexibly schedule or not schedule transmissions. For example, in some aspects, base stations can use DCI formats 1_1 and 1_2 to include UL-only TCI status update beam indications (e.g., for separate UL / DL TCI status indications). In other aspects, other DCI formats can be used, such as newly defined DCI formats.

[0063] Example TCI status types include types 1, 2, 3, 4, 5, and 6. In addition to types 1-3 mentioned above, type 4 TCI status can include a separate DL single-channel / RS TCI status to indicate the beam used for a single DL channel / DL RS. Type 5 TCI status can include a separate UL single-channel / RS TCI status to indicate the beam used for a single UL channel / UL RS. Type 6 TCI status can include UL spatial relation information (SRI) to indicate the beam used for a single UL channel / UL RS. In DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2, DCI formats 1_1 and 1_2 can include a TCI field indicating the TCI status, while DCI formats 0_1 and 0_2 can include an SRI field for spatial relation information.

[0064] A Cyclic Redundancy Check (CRC) bit set can be associated with the DCI and can be scrambled with a Network Temporary Identifier (RNTI). For example, a base station can use a DCI with a CRC scrambled with a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) to schedule resources for Semi-Persistent Scheduling (SPS) PDSCH or configured Granted (CG) PUSCH, or to activate / release / reactivate SPS PDSCH or CG PUSCH. For example, if the DCI's New Data Indicator (NDI) field is set to 0, and if the CRC associated with the DCI is scrambled with CS-RNTI, the UE can determine the configuration by which the DCI activates / releases SPS PDSCH or CG PUSCH. If the DCI's NDI field is set to 1, and if the CRC associated with the DCI is scrambled with CS-RNTI, the UE can determine that the DCI schedules retransmissions of SPS PDSCH or CG PUSCH. The UE can also confirm the use of the DCI for scheduling / activating / releasing SPS PDSCH or CG PUSCH based on a set of one or more fields. For example, if a DCI has a CRC scrambled with the corresponding CS-RNTI (which instructs the UE that the DCI will schedule a retransmission / activate / release an SPS or CG resource), and the NDI field is set to 0 (e.g., indicating an initial transmission), the UE can determine that the DCI is not used for retransmission. An NDI set to "1" is associated with retransmission. If fields such as RV, MCS, FDRA (which may be referred to as special fields or subsets of fields) match reserved values, the UE can determine the purpose of the DCI. If these fields do not match a specific set of values, the UE can discard the DCI. For example, for a single DL SPS or a single UL license type 2 scheduling activation PDCCH verification, when multiple DL SPS or UL license type 2 configurations are provided to the UE, the UE can check whether the RV field is set to all zeros for the DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_2 or 1_1 (e.g., for an enabled TB). For multiple DL SPS and UL license type 2 scheduling release PDCCH verifications, the UE can check whether RV is set to all zeros, MCS is set to all 1s, and FDRA is set to all 1s for DCI formats 0_0, 0_1, or 0_2. For DCI formats 1_0, 1_1, or 1_2, the UE can check whether the RV field is set to all zeros, the MCS field is set to all 1s, and FDRA is set to all zeros for FDRA type 0 or all 1s for FDRA type 1. If the fields do not match the indicated values, the DCI fails verification, and the UE can discard the DCI. If more than one SPS configuration is provided to the UE, the HARQ process number field of the DCI can indicate the corresponding ID to be released / activated.When configuring a single SPS configuration for a UE, the HARQ process number field in the DCI can be set to all zeros.

[0065] Figure 5A This is a communication flowchart 500 illustrating an example aspect of signaling between UE 502 and base station 504, including indicating the TCI status from the base station to the UE in the DCI. Figure 5A As shown, UE 502 can receive beam update DCI 508 from base station 504 and determine the TCI state 509 of one or more of the UL channel, UL RS, DL channel, or DL ​​RS based on the DCI. The beam update DCI 508 can be one of different DCI formats. In some aspects, the format of the beam update DCI 508 can be one of DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2. The beam update DCI 508 can include a sequence that can indicate the beam update purpose of the DCI (i.e., beam indication). The CRC associated with the beam update DCI 508 can be scrambled with an RNTI not dedicated to beam updates (such as CS-RNTI, Cellular Radio RNTI (C-RNTI), etc.). When UE 502 detects this sequence, UE 502 can determine that the beam update DCI 508 is used for beam updates. Beam indication information (e.g., the new beam TCI status identifier (ID)) can be transmitted in a separate field of the DCI. In some respects, beam information can be indicated separately from the indication used by the DCI for beam updates. Therefore, the UE can determine the TCI status based on additional information in the DCI. For example, beam indication information can be included in the TCI status ID field of DCI formats 1_1 and 1_2; in the Hybrid Automatic Repeat Request (HARQ) process number field of the fallback DCI format, etc.

[0066] In some aspects, the sequence may include reserved values ​​from specific fields of the DCI to indicate to the UE the purpose of beam update. In other aspects, the sequence may include a combination of values ​​from specific fields of the DCI to indicate to the UE the purpose of beam update. When the DCI is used for purposes other than beam update, the sequence of values ​​in one or more fields may be an unused or infeasible sequence. The UE may use the values ​​of these fields at least in part to determine that the DCI is a beam update DCI. The sequence may indicate to the UE the purpose of beam update, and the base station may not use the sequence in the DCI for other purposes, such as transmission, activation / release, etc. In some examples, the sequence may be a defined sequence associated with beam update, or it may be a sequence unrelated to another DCI purpose. In some examples, the sequence in the DCI may not be applicable to purposes other than beam update DCI.

[0067] In some aspects, the CRC associated with beam update DCI 508 can be scrambled using one or more combinations of a CS-RNTI and a verification sequence and special fields indicating the beam update purpose of the DCI (excluding fields used for SPS PDSCH activation / release). In some aspects, a verification sequence and / or fields can be defined for the beam update DCI. In some aspects, the CRC associated with beam update DCI 508 can be scrambled using a C-RNTI, and this sequence can be based on one or more of the following: Redundancy Version (RV) field, Frequency Domain Resource Allocation (FDRA) field, Time Domain Resource Allocation (TDRA) field, Hybrid Automatic Repeat Request (HARQ) process number field, or Modulation and Coding Scheme (MCS) field. As a non-limiting example, the base station can indicate to the UE that the DCI is for beam update by including the same value in each of the RV field, FDRA field, TDRA field, HARQ process number field, and MCS field. For example, if each of the subsets of DCI fields (e.g., RV field, FDRA field, TDRA field, HARQ process number field, and MCS field) has a value of 1, the UE can determine that the DCI is used for beam updates. The combination of the RV field, FDRA field, TDRA field, HARQ process number field, and MCS field is used to illustrate this concept. In other respects, subsets of fields can include different subsets of DCI fields.

[0068] In some respects, a base station can indicate that a DCI is a beam update DCI 508 by scrambling a CRC associated with the beam update DCI 508 using C-RNTI, and by any combination of an NDI field indicating a new transmission, an MCS field indicating a reserved MCS value for retransmission, and a sequence in additional specific fields (e.g., all '1's or '0's in the HARQ ID, RV field, and FDRA). A UE can use one or more indications to determine that a DCI is a beam update DCI. In these respects, the sequence may not be a sequence used for scheduling retransmissions. Therefore, by indicating parameters that are generally unrelated, such as the MCS for retransmissions and the NDI for new transmissions, or the MCS for retransmissions and a sequence not used for retransmissions, the base station can indicate to the UE that the DCI is for beam updates, for example, rather than retransmissions or initial transmissions. The sequence may be a sequence not used for scheduling retransmissions. The sequence is unique for indicating that the DCI is for beam updates. Having a specific sequence helps the UE avoid misunderstanding the DCI for another purpose. Figure 5BExamples of various types of DCIs are shown. First DCI 520 includes a DL license for initial transmission (e.g., NDI = 0 for initial transmission). Second DCI 522 includes a DL license for retransmission (e.g., NDI = 1 for retransmission). Beam update DCI 524 includes beam update information. A beam update DCI may include an NDI field for initial transmission and an MCS associated with retransmission as a way to indicate to the UE that the DCI is for beam update rather than DL license. Without sequence verification, if the DL license for retransmission (e.g., DCI 522) is missed by the UE, the UE may mistakenly identify beam update DCI 524 as a DL license for retransmission. In some examples, this sequence may be a sequence not used for retransmission DCIs, allowing the UE to distinguish between DCI 522 with a DL license for retransmission and beam update DCI 524. Therefore, the UE can determine that the DCI is a beam scheduling DCI, at least in part, based on this sequence. The base station can indicate different DCI formats to indicate beam updates for specific types of TCI states. Therefore, the UE can determine whether the DCI is a beam-scheduling DCI based on this sequence, and can determine the type of TCI state indicated in the DCI based on the DCI format. For example, a DL DCI format can be used to indicate the TCI state of a DL channel. In some aspects, beam update DCIs can, for example, provide beam updates without scheduling transmissions.

[0069] In some respects, such a beam update DCI 508 of DCI format 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2 may include a sequence indicating the beam update purpose of the DCI (e.g., a DCI for beam indication), the DCI may have a CRC scrambled with an RNTI not dedicated to beam update (such as CS-RNTI, C-RNTI, etc.), and the DCI may not schedule transmissions (e.g., communication 512).

[0070] In some respects, the CRC associated with the beam update DCI 508 can be scrambled using a type of RNTI dedicated to beam update DCIs. The UE receiving the DCI can determine that the DCI is a beam update DCI based at least in part on the RNTI used to scramble the CRC. In some respects, the RNTI can be referred to as the beam update RNTI (BU-RNTI). In other respects, the RNTI can be referred to by another name. In some respects, the beam update DCI 508 can be a DCI format 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2. In some respects, the BU-RNTI can include a common RNTI for all types of TCIs that can be updated by the DCI, and fields within the beam update DCI 508 can be used to indicate the specific TCI type being updated by the beam update DCI 508. In some respects, the BU-RNTI can include a dedicated RNTI for a specific type of TCI state; for example, each type of TCI state update is associated with a different dedicated RNTI. In some respects, some fields of the DCI can be reused to indicate information related to TCI updates. For example, the HARQ ID field (in beam update DCI 508) can indicate the TCI status ID in the fallback DCI. As another example, the TCI status ID field in DCI format 1_1 or DCI format 1_2 in beam update DCI 508 can indicate the new TCI status ID. In some aspects, after receiving a DCI with a CRC scrambled with BU-RNTI, UE 502 can verify that the DCI is a beam update DCI by checking whether one or more fields use a reserved index for beam updates. If these fields do not include an index associated with beam updates, UE 502 can discard the DCI. In some examples, BU-RNTI can be used to indicate that an existing DCI format is used to indicate beam updates; for example, a DCI format specifically for beam updates is not used.

[0071] In some respects, the beam update DCI 508 with a CRC scrambled with BU-RNTI can indicate beam updates without scheduling transmissions. For example, the DCI can be based on a backoff DCI format that does not include the TCI field.

[0072] In some respects, when a base station updates the beam of a channel or RS that is different from the scheduled channel / RS, the target channel / RS (e.g., associated with beam change / TCI state update) and the scheduled channel / RS may not share a common TCI state. For example, in the absence of a common TCI configured for DL ​​channels (e.g., PDSCH) and UL channels (e.g., PUSCH), the base station may send DCIs to schedule PDSCH and change the PUSCH beam.

[0073] In some respects, this beam update DCI 508 with a CRC scrambled with a BU-RNTI can be used to schedule transmissions, such as communication 512. For example, when the beam update DCI 508 is a DCI format with a TCI ID field (e.g., DCI format 1_1 or DCI format 1_2), and if (1) the scheduling channel / RS and the target channel / RS of the beam update are the same channel, or (2) the beam of the scheduling channel / RS and the update beam are defined in a certain common TCI state, then the beam update DCI 508 can be used for beam update and simultaneously schedule communication 512. In another example, if UL beam 0 and DL beam 1 are defined in common TCI state 0, then the beam update DCI 508 of format 1_1 schedules PDSCH by using a C-RNTI and indicating common TCI state 0, and then the PDSCH beam can be updated to DL beam 1. If the DCI 508 beam update of DCI format 1_1 schedules PDSCH by using BU-RNTI and indicating common TCI state 0, then both PDSCH and PUSCH beams are updated to UL beam 0 and DL beam 1.

[0074] In some aspects, the beam update DCI 508 can be based on an existing DCI format and can include fields indicating the beam update purpose of the DCI. For example, the base station can use new fields associated with an existing DCI to indicate a beam update. The DCI format can include one or more additional fields indicating a TCI status update, for example, having DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, or DCI format 1_2. These one or more fields can include a TCI status field to indicate the updated beam. In some aspects, the payload of the DCI format can be dynamically configured by the base station. In some aspects, the base station can configure the size of the DCI format via Radio Resource Control (RRC). For example, when a higher layer indicates that DCI-based beam updates are allowed and a TCI pool is configured, the field can contain X bits, where X can be equal to the size of the TCI pool. If DCI-based beam updates are not allowed, or if no TCI pool is configured at the UE, the field can have 0 bits. In some aspects, a base station may use reserved bits or reserved indices in a field to indicate when there is no beam update. In some aspects, such a beam update DCI 508 with a DCI format having one or more fields indicating the TCI status can be added to any of the DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2 for scheduling transmissions, such as communication 512. In some aspects, a base station may indicate a beam update and schedule transmissions in the DCI based on rules indicating whether transmission is permitted. In some aspects, a base station may indicate a beam update and schedule transmissions in the DCI based on signaling indicating whether combined beam update / transmission scheduling is permitted or supported. If permitted, supported, or enabled, the indication in the beam update DCI 508 may indicate whether the beam update DCI 508 is also used to schedule transmissions other than beam updates. For example, one or more additional bits or a specific set of fields may be used for indication. In some aspects, these bits or fields may be reserved indices when the DCI does not include scheduling permission.

[0075] In some aspects, base station 504 may send a first-level DCI 506 before sending a beam update DCI 508. The first-level DCI 506 may be one of DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2. The first-level DCI may schedule a second-level message (such as beam update DCI 508) containing beam indication information. The first-level DCI may use reserved bits, sequences in some fields, or new / reserved fields to indicate that the second-level message is for beam indication or beam update. In some aspects, the second-level message may be a Media Access Control (MAC) Control Element (CE) (MAC-CE) instead of a second DCI. In some aspects, a PDSCH carrying a MAC-CE may be scheduled by the first-level DCI 506 or using configured resources. In some aspects, the second-level message may be carried by a PDSCH (e.g., scheduled by the first-level DCI 506) or a PDCCH. In some respects, PDSCH or PDCCH can be transmitted via rule-based identified resources (such as a defined number of time slots after Level 1 DCI 506). In other respects, PDSCH or PDCCH can be transmitted in configured resources, for example, in a configured number of time slots after Level 1 DCI.

[0076] In some aspects, the beam update DCI 508 can use a DCI format different from one of the DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2. In these aspects, the beam update DCI 508 can be a format used to update TCI indications, for example, specifically for updating TCI status, such as beam updates. The base station can indicate the updated TCI ID and the applicable channel / RS for beam updates in the beam update DCI 508. In some aspects, the beam update DCI 508 can indicate the CC, partial bandwidth (BWP), or CC group used for beam updates. If the CC indication is not present, the UE 502 can use implicit rules to determine the applicable CC, such as the CC of the received DCI. In these aspects, the beam update DCI 508 can also be a format used to update TCI status content. In some aspects, one or more search spaces (SS) can be configured for the UE 502. In these respects, the beam update DCI 508 can be used to update the format of the TCI indication, and the beam update DCI 508 can be used to schedule transmissions (e.g., communication 512) simultaneously.

[0077] In some aspects, when beam update DCI 508 also schedules DL or UL transmissions (e.g., communication 512), an acknowledgment (ACK) for a DL or UL transmission can be considered an ACK for the DCI, and a dedicated ACK 510 for the beam update DCI may not be required; for example, the UE may not send a dedicated ACK for the beam update DCI. In some aspects where beam update DCI 508 does not schedule communication 512, the UE may send a dedicated ACK 510 for the beam update DCI. In some aspects, the UE may send ACK 510 in the uplink control information (UCI) within the PUSCH or PUCCH. In some aspects, the UE may send ACK 510 after a time period X following the receipt of the last PDCCH symbol containing beam update DCI 508. In some aspects, the time period X may be determined by the frequency modulation interval of the CC receiving the DCI and the frequency modulation interval of the CC applying beam indication, and may also be determined based on the UE capabilities of UE 502. In some respects, the application of the new beam indicated in the DCI can occur after a time period Y following the UE sending the ACK 510 (the last symbol) indicating the beam update. The time period Y can be based on the UE capabilities of UE 502. In some respects, Y can also be based on the frequency modulation interval of at least one of the CCs that send the ACK, the CC that receives the ACK, or the CC that applies the beam update. If the beam update occurs in multiple CCs, one of the CCs, such as the CC with the smallest frequency modulation interval, can be used to determine X and / or Y.

[0078] Figure 6 This is a flowchart 600 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 404, UE 502, device 802). Optional steps are indicated by dashed lines. These steps are not necessarily shown in chronological order. This method can enable DCI, which indicates a TCI state update of one of various types.

[0079] In position 602, the UE receives DCI. In some respects, position 602 can be... Figure 8 The DCI receiving component 842 in the middle is used to perform this. Figure 5AAn example of UE 502 receiving DCI 508 from base station 504 is shown. In some aspects, the DCI also includes beam indication information, which includes a TCI state ID indicating the TCI state of the beam. In some aspects, the DCI includes a HARQ ID field indicating the TCI state ID of the beam, which indicates the beam. In some aspects, the DCI includes a TCI state ID field indicating the TCI state of the beam. In some aspects, the DCI is used to schedule beams when the channel used for beam updates, the reference signal, and the target channel, as well as the scheduled channel, are the same channel, or when the beam for the scheduled channel and the beam for beam updates are defined in a common TCI state. In some aspects, the DCI includes a dedicated field indicating whether the beam update is for uplink, downlink, or a combination of uplink and downlink. In some aspects, the payload of the DCI is configured via RRC signaling. In some aspects, the DCI schedules uplink or downlink transmissions. In some aspects, the DCI is in a format for beam updates. In some cases, a dedicated SS is configured at the UE to monitor the DCI. In other cases, the DCI does not schedule transmissions.

[0080] In section 604, the UE can determine whether the DCI is associated with a beam update for uplink, downlink, or a combination of uplink and downlink based on the DCI. In some aspects, section 604 can be determined by... Figure 8 The DCI determination component 844 in the DCI is used to perform this determination. This determination may include combining... Figure 5A The determination at point 509 describes any of the aspects. In some aspects, the DCI includes a sequence associated with beam updates, and the UE uses this sequence to determine whether the beam update is for uplink, downlink, or a combination of uplink and downlink. In some aspects, this sequence differs from the sequence used for scheduling transmissions. In some aspects, the CRC associated with the DCI is scrambled with a CS-RNTI, and this sequence differs from the sequence used for SPS PDSCH activation or release. In some aspects, the CRC associated with the DCI is scrambled with a C-RNTI, and where this sequence is a combination of one or more of the RV field, FDRA field, TDRA field, HARQ process number field, or MCS field. In some aspects, the CRC associated with the DCI is scrambled with a BU-RNTI dedicated to beam updates, and the UE determines based on the BU-RNTI that the DCI indicates a beam update for uplink, downlink, or a combination of uplink and downlink. In some respects, before determining that the DCI is associated with a beam update, the UE receives a second-level message in the PDCCH or the PDSCH scheduled by the DCI, which includes a second DCI or MAC-CE.

[0081] In 606, the UE can determine the TCI state based on the DCI, which indicates the beam used for the uplink, downlink, or a combination of uplink and downlink. In some aspects, 606 can be... Figure 8 The TCI status determination component 846 in the system is used to perform this.

[0082] In 608, the UE can send an acknowledgment. In some respects, 608 can be... Figure 8 The determination is performed using the ACK component 848 in the code. Figure 5A The determination at point 509 describes any of the aspects. In some aspects, when the DCI schedules downlink or uplink transmissions, the UE sends a non-dedicated acknowledgment, such as an acknowledgment of uplink or downlink transmission, to acknowledge the reception of the DCI. In some aspects, when the DCI does not schedule downlink or uplink transmissions, the UE sends a dedicated acknowledgment to acknowledge the reception of the DCI. In some aspects, the UE may send an acknowledgment of the UCI received by the DCI. In some aspects, the UE receives a new beam indication after a period of time following the sending of the acknowledgment. In some aspects, the period of time is determined based on a set of UE capability metrics. In some aspects, the period of time is determined based on the frequency modulation interval of the CC receiving the DCI and the frequency modulation interval of the CC sending the acknowledgment.

[0083] In 610, the UE can send uplink transmissions. In some aspects, 610 can be... Figure 8 The uplink component 850 in the UE performs this action. In some aspects, the UE determines that the beam update is for the uplink, and the UE can use a beam based on the TCI state to transmit uplink transmissions. In some aspects, the TCI state indicates at least two uplink channels. In some aspects, the UE determines that the beam update is for both the uplink and downlink, and the UE can transmit uplink transmissions and receive downlink transmissions based on the beam update.

[0084] In 612, the UE can receive downlink transmissions. In some aspects, 612 can be... Figure 8 The downlink component 852 in the UE performs this operation. In some aspects, the UE determines that the beam update is for a downlink transmission, and the UE can use a beam based on the TCI state to receive the downlink transmission. In some aspects, the TCI state indicates at least two downlink channels.

[0085] Figure 7This is a flowchart 700 of a wireless communication method. This method can be performed by a base station (e.g., base station 102 / 180, base station 402, base station 504, device 902). Optional steps are indicated by dashed lines. These steps are not necessarily shown in chronological order. This method enables the base station to send a DCI to the UE, indicating a TCI state update of one of various types.

[0086] In 702, the base station can transmit a DCI indicating beam updates for uplink, downlink, or a combination of uplink and downlink. In some aspects, 602 can be... Figure 9 The DCI component 942 in the DCI module is used to execute this. Figure 5A An example is shown where base station 504 sends beam update DCI 508 to UE 502. In some aspects, the DCI also includes beam indication information, which includes a TCI state ID indicating the TCI state of the beam. In some aspects, the DCI includes a HARQ ID field indicating the TCI state ID, which indicates the beam. In some aspects, the DCI includes a TCI state ID field indicating the TCI state, which indicates the beam.

[0087] In 703, the base station indicates in the DCI that the DCI is used for beam updates. This indication can be provided by... Figure 9 The instruction is executed using the DCI component 942 within the DCI module. This instruction can be based on the combination of... Figure 5AThe beam update DCI 508 describes any aspect of this. In some aspects, the DCI is used to schedule beams when the channel used for beam update, the reference signal, and the target channel, as well as the scheduled channel, are the same channel, or when the beam for the scheduled channel and the beam for beam update are defined in a common TCI state. In some aspects, the DCI includes a dedicated field indicating whether the beam update is for uplink, downlink, or a combination of uplink and downlink. In some aspects, the payload of the DCI is configured via RRC signaling. In some aspects, the DCI schedules uplink or downlink transmissions. In some aspects, the DCI is a format used for beam updates. In some aspects, a dedicated SS is configured at the UE to monitor the DCI. In some aspects, the DCI does not schedule transmissions. In some aspects, the DCI includes a sequence associated with the beam update, and the UE uses this sequence to determine whether the beam update is for uplink, downlink, or a combination of uplink and downlink. In some aspects, this sequence differs from the sequence used to schedule transmissions. In some aspects, the CRC associated with the DCI is scrambled with CS-RNTI, and this sequence is different from the sequence used for SPS PDSCH activation or release. In some aspects, the CRC associated with the DCI is scrambled with C-RNTI, and the sequence is a combination of one or more of the RV field, FDRA field, TDRA field, HARQ process number field, or MCS field. In some aspects, the CRC associated with the DCI is scrambled with BU-RNTI dedicated to beam updates, and the UE determines the DCI indication for beam updates for uplink, downlink, or a combination of uplink and downlink based on the BU-RNTI. In some aspects, before determining that the DCI is associated with a beam update, the UE receives a second-level message in the PDCCH or a PDSCH scheduled by the DCI, which includes a second DCI or MAC-CE.

[0088] In 704, the base station can receive confirmation. In some respects, 608 can be... Figure 9 The ACK processing component 944 in the system performs this operation. In some aspects, the base station receives non-dedicated acknowledgments, such as acknowledgments for uplink or downlink transmissions, which can be used as acknowledgments of DCI reception when DCI schedules downlink or uplink transmissions without receiving dedicated acknowledgments. In some aspects, the base station receives dedicated acknowledgments of DCI reception when DCI does not schedule downlink or uplink transmissions. In some aspects, the acknowledgment can be in the form of a UCI. In some aspects, the base station sends a new beam indication after a period of time following the receipt of the acknowledgment. In some aspects, this period of time is determined based on a set of UE capability metrics of the UE. In some aspects, this period of time is determined based on the frequency modulation interval of the CC receiving the DCI and the frequency modulation interval of the CC sending the acknowledgment.

[0089] In the 706, the base station can receive uplink transmissions. In some aspects, the 610 can be... Figure 9 The uplink component 946 in the middle performs this function. In some aspects, the TCI status indicates at least two uplink channels. In some aspects, beam updates are used for both uplink and downlink.

[0090] In 708, the base station can send downlink transmissions. In some aspects, 708 can be... Figure 9 The downlink component 948 in the UE performs this action. In some aspects, the UE determines that the beam update is for a downlink transmission, and the UE can use a beam based on the TCI state to receive the downlink transmission. In some aspects, the TCI state indicates at least two downlink channels.

[0091] Figure 8 Figure 800 illustrates an example of a hardware implementation of device 802. Device 802 is a UE and includes a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822, one or more Subscriber Identity Module (SIM) cards 820, an application processor 806 coupled to a Secure Digital Card (SD) card 808 and a screen 810, a Bluetooth module 812, a Wireless Local Area Network (WLAN) module 814, a Global Positioning System (GPS) module 816, and a power supply 818. The cellular baseband processor 804 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 822. The cellular baseband processor 804 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 804 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 804, the software causes the cellular baseband processor 804 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 804 during software execution. The cellular baseband processor 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. The communication manager 832 includes one or more of the components shown. The components within the communication manager 832 can be stored in the computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 804. The cellular baseband processor 804 can be a component of the UE 350 and can include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 802 can be a modem chip and includes only the baseband processor 804, while in another configuration, the device 802 can be the entire UE (e.g., see...). Figure 3 (350), and includes the aforementioned additional module of device 802.

[0092] Communication manager 832 includes DCI receiving component 842, which is configured to receive DCI, for example, as in combination with Figure 6 As described in 602. The communication manager 832 may also include a DCI determination component 844 configured to determine, based on the DCI, whether the DCI is associated with a beam update for uplink, downlink, or a combination of uplink and downlink, for example, as in combination with... Figure 6 As described in section 604. The communication manager 832 may also include a TCI status determination component 846 configured to determine a TCI status based on the DCI, the TCI status indicating the beam used for the uplink, downlink, or a combination of uplink and downlink, for example, as combined with Figure 6 As described in 606. The communication manager 832 may also include an ACK component 848, which is configured to send an acknowledgment, for example, as in combination with Figure 6 As described in 608. The communication manager 832 may also include an uplink component 850 configured to send uplink transmissions, for example, as in conjunction with Figure 6 As described in 610. The communication manager 832 may also include a downlink component 852, which is configured to receive downlink transmissions, for example, as in combination with Figure 6 As described in 612.

[0093] The device may include the ability to perform the above-described actions. Figure 6 The additional components of each box in the flowchart of the algorithm. Thus, the above... Figure 6 Each block in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0094] In one configuration, device 802, particularly cellular baseband processor 804, includes components for receiving a Direct Current Interface (DCI). Cellular baseband processor 804 may further include components for determining, based on the DCI, whether the DCI is associated with a beam update for an uplink, downlink, or a combination of uplink and downlink. Cellular baseband processor 804 may also include components for determining a Transmission Control Interchange (TCI) state based on the DCI, the TCI state indicating a beam for an uplink, downlink, or a combination of uplink and downlink. Cellular baseband processor 804 may further include components for transmitting uplink transmissions using the TCI-based beam. Cellular baseband processor 804 may also include components for receiving downlink transmissions using the TCI-based beam. Cellular baseband processor 804 may further include components for transmitting uplink transmissions based on beam updates. Cellular baseband processor 804 may also include components for receiving downlink transmissions based on beam updates. The cellular baseband processor 804 may further include components for receiving a second-level message, including a second DCI or MAC-CE, in a PDCCH or a PDSCH scheduled by the DCI before determining that the DCI is associated with a beam update. The cellular baseband processor 804 may also include components for sending a UCI acknowledging receipt of the DCI, wherein the DCI schedules downlink or uplink transmissions. The cellular baseband processor 804 may further include components for sending a dedicated acknowledgment confirming receipt of the DCI. The cellular baseband processor 804 may further include components for receiving a new beam indication after a time period following the transmission of the acknowledgment.

[0095] The aforementioned components may be one or more of the aforementioned components of device 802, configured to perform the functions listed above. As described above, device 802 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned components may be TX processor 368, RX processor 356, and controller / processor 359, configured to perform the functions listed above.

[0096] Figure 9Figure 900 illustrates an example of a hardware implementation of device 902. Device 902 is a baseband unit (BS) and includes a baseband unit 904. Baseband unit 904 can communicate with UE 104 via a cellular RF transceiver 922. Baseband unit 904 may include computer-readable media / memory. Baseband unit 904 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by baseband unit 904, the software causes baseband unit 904 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by baseband unit 904 during software execution. Baseband unit 904 also includes a receiving component 930, a communication manager 932, and a transmitting component 934. Communication manager 932 includes one or more of the components shown. Components within communication manager 932 may be stored in computer-readable media / memory and / or configured as hardware within baseband unit 904. The baseband unit 904 may be a component of the BS 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0097] Communication manager 932 includes DCI component 942 for receiving DCI, for example, as combined with Figure 7 As described in 702. The communication manager 932 also includes an ACK processing component 944 for receiving acknowledgments, for example, as in combination with Figure 7 As described in 704. The communication manager 932 also includes an uplink component 946 for receiving uplink transmissions, for example, as in combination with Figure 7 As described in 706. The communication manager 932 also includes a downlink component 948 for transmitting downlink transmissions, for example, as in combination with Figure 7 As described in 708.

[0098] The device may include the ability to perform the above-described actions. Figure 7 The additional components of each box in the flowchart of the algorithm. Thus, the above... Figure 7 Each block in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0099] In one configuration, device 902, particularly baseband unit 904, includes components for transmitting DCI. Baseband unit 904 may also include components for transmitting downlink transmissions using beamforming based on TCI states. Baseband unit 904 may also include components for receiving uplink transmissions. Baseband unit 904 may also include components for transmitting downlink transmissions. Baseband unit 904 may also include components for transmitting a second-level message, including a second DCI or MAC-CE, in a PDCCH or a PDSCH scheduled by the DCI. Baseband unit 904 may also include components for receiving a UCI acknowledging receipt of the DCI, wherein the DCI schedules downlink or uplink transmissions. Baseband unit 904 may also include components for receiving a dedicated acknowledgment confirming receipt of the DCI. Baseband unit 904 may also include components for transmitting a new beam indication after a time period following the receipt of the acknowledgment.

[0100] The aforementioned components may be one or more of the aforementioned components of device 902, configured to perform the functions listed above. As described above, device 902 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the aforementioned components may be TX processor 316, RX processor 370, and controller / processor 375, configured to perform the functions listed above.

[0101] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative of the exemplary method. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged. Furthermore, some blocks can be combined or omitted. The appended method claims present the elements of various blocks in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0102] 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 can be applied to other aspects. Therefore, the claims are not intended to limit themselves to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein, unless specifically stated otherwise, the singular element does not mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” should be interpreted as indicating “under the condition,” rather than referring to an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only that the action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known to or will be known thereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, nothing disclosed herein is intended to be exclusive to the public, whether or not such disclosure is expressly stated in the claims. The terms "module", "mechanism", "element", "device", etc., cannot replace the term "part". Therefore, unless a claim element is explicitly stated using the phrase "for a component," no claim element is interpreted as a component plus a function.

[0103] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0104] Aspect 1 is a method for wireless communication at a UE, comprising: receiving a DCI; determining, based on the DCI, whether the DCI is associated with a beam update for an uplink, downlink, or a combination of uplink and downlink; and determining, based on the DCI, a TCI state indicating a beam for an uplink, downlink, or a combination of uplink and downlink.

[0105] Aspect 2 is the method according to aspect 1, wherein the UE determines that the beam update is for the uplink, and the method further includes: using a beam based on TCI state to transmit uplink transmissions.

[0106] Aspect 3 is the method according to any one of Aspects 1-2, wherein the TCI status indicates at least two uplink channels.

[0107] Aspect 4 is a method according to any one of Aspects 1-3, wherein the UE determines that the beam update is for downlink transmission, and the method further includes: using a beam based on TCI state to receive the downlink transmission.

[0108] Aspect 5 is the method according to any one of Aspects 1-4, wherein the TCI status indicates at least two downlink channels.

[0109] Aspect 6 is a method according to any one of Aspects 1-5, wherein the UE determines that the beam update is for both uplink and downlink, and the method further includes: transmitting uplink transmissions based on the beam update; and receiving downlink transmissions based on the beam update.

[0110] Aspect 7 is the method according to any one of Aspects 1-6, wherein the DCI includes a sequence associated with beam updates, and the UE uses the sequence to determine whether the beam update is for the uplink, downlink, or a combination of uplink and downlink.

[0111] Aspect 8 is the method according to any one of Aspects 1-7, wherein the DCI further includes beam indication information, which includes a TCI state ID indicating the TCI state of the beam.

[0112] Aspect 9 is the method according to any one of aspects 1-8, wherein the sequence is different from the sequence used for scheduling transmissions.

[0113] Aspect 10 is the method according to any one of aspects 1-9, wherein the CRC associated with the DCI is scrambled with CS-RNTI, and wherein the sequence is different from the sequence used for SPS PDSCH activation or deactivation.

[0114] Aspect 11 is the method according to any one of Aspects 1-9, wherein the CRC associated with the DCI is scrambled with C-RNTI, and wherein the sequence is a combination of one or more of the RV field, FDRA field, TDRA field, HARQ process number field or MCS field.

[0115] Aspect 12 is the method according to any one of Aspects 1-9, wherein the CRC associated with the DCI is scrambled with C-RNTI, and wherein the sequence is a combination of one or more of the RV field, NDI field, FDRA field, HARQ process number field or MCS field.

[0116] Aspect 13 is the method according to any one of aspects 1-12, wherein DCI does not schedule transmissions.

[0117] Aspect 14 is the method according to any one of Aspects 1-9, wherein the CRC associated with the DCI is scrambled using a BU-RNTI dedicated to beam updates, and the UE determines the DCI indication for beam updates for uplink, downlink, or a combination of uplink and downlink based on the BU-RNTI.

[0118] Aspect 15 is the method according to any one of aspects 1-14, wherein the DCI includes a HARQ ID field indicating a TCI state ID, which indicates a beam.

[0119] Aspect 16 is the method according to any one of Aspects 1-15, wherein the DCI includes a TCI state ID field indicating a TCI state indicating a beam, and wherein the DCI is used to schedule the beam when the channel used for beam update, the reference signal and the target channel and the scheduled channel are the same channel or the beam used for the scheduled channel and the beam used for beam update are defined in a common TCI state.

[0120] Aspect 17 is the method according to any one of Aspects 1-16, wherein the DCI includes a dedicated field indicating that the beam update is for uplink, downlink, or a combination of uplink and downlink.

[0121] Aspect 18 is the method according to any one of aspects 1-17, wherein the payload of the DCI is configured via RRC signaling.

[0122] Aspect 19 is the method according to any one of Aspects 1-8 and 16-18, wherein DCI schedules uplink transmissions or downlink transmissions.

[0123] Aspect 20 is the method according to any one of aspects 1-19, further comprising: receiving a second-level message, the second-level message including a second DCI or Media Access Control MAC-CE in a PDCCH or a PDSCH scheduled by the DCI, before determining that the DCI is associated with a beam update.

[0124] Aspect 21 is the method according to any one of aspects 1-20, wherein DCI is a format for beam updating.

[0125] Aspect 22 is the method according to any one of aspects 1-21, wherein a dedicated SS is configured at the UE for monitoring the DCI.

[0126] Aspect 23 is the method according to any one of aspects 1-22, further comprising sending a non-dedicated acknowledgment upon acknowledgment of receipt of the DCI, wherein the DCI schedules downlink transmission or uplink transmission.

[0127] Aspect 24 is the method according to any one of aspects 1-23, further comprising sending an acknowledgment of receiving a dedicated acknowledgment from the DCI, wherein the DCI does not schedule downlink or uplink transmissions.

[0128] Aspect 25 is the method according to any one of aspects 1-24, further comprising receiving a new beam indication after a time period following the transmission of confirmation.

[0129] Aspect 26 is the method according to any one of Aspects 1-25, wherein the time period is determined based on a set of UE capability metrics of the UE.

[0130] Aspect 27 is the method according to any one of aspects 1-26, wherein the time period is determined based on the frequency modulation interval of the CC receiving the DCI and the frequency modulation interval of the CC sending the acknowledgment.

[0131] Aspect 28 is a method for wireless communication at a base station, comprising: transmitting a DCI indicating a beam update for an uplink, a downlink, or a combination of uplink and downlink; and indicating in the DCI that the DCI is used for beam update.

[0132] Aspect 29 is the method according to aspect 28, wherein the TCI status indicates at least two uplink channels.

[0133] Aspect 30 is the method according to any one of aspects 28-29, further comprising: transmitting downlink transmissions using a beam based on TCI state.

[0134] Aspect 31 is the method according to any one of aspects 28-30, wherein the TCI status indicates at least two downlink channels.

[0135] Aspect 32 is the method according to any one of aspects 28-31, further comprising: receiving uplink transmissions based on beam updates; and transmitting downlink transmissions based on beam updates.

[0136] Aspect 33 is the method of any one of Aspects 28-32, wherein the DCI includes a sequence associated with beam updates.

[0137] Aspect 34 is the method according to any one of aspects 28-33, wherein the DCI further includes beam indication information, which includes a TCI state ID indicating the TCI state of the beam.

[0138] Aspect 35 is the method according to any one of aspects 28-34, wherein the sequence is different from the sequence used for scheduling transmissions.

[0139] Aspect 36 is the method according to any one of aspects 28-35, wherein the CRC associated with the DCI is scrambled with CS-RNTI, and wherein the sequence is different from the sequence used for SPS PDSCH activation or release.

[0140] Aspect 37 is the method according to any one of Aspects 28-35, wherein the CRC associated with the DCI is scrambled with C-RNTI, and wherein the sequence is a combination of one or more of the RV field, FDRA field, TDRA field, HARQ process number field or MCS field.

[0141] Aspect 38 is the method according to any one of aspects 28-35, wherein the CRC associated with the DCI is scrambled with C-RNTI, and wherein the sequence is a combination of one or more of the RV field, NDI field, FDRA field, HARQ process number field or MCS field.

[0142] Aspect 39 is the method according to any one of aspects 28-38, wherein DCI does not schedule transmissions.

[0143] Aspect 40 is the method according to any one of Aspects 28-35, wherein the CRC associated with the DCI is scrambled using a BU-RNTI dedicated to beam updates, and the UE determines the DCI indication for beam updates for uplink, downlink, or a combination of uplink and downlink based on the BU-RNTI.

[0144] Aspect 41 is the method according to any one of aspects 28-40, wherein the DCI includes a HARQ ID field indicating a TCI state ID, which indicates a beam.

[0145] Aspect 42 is the method according to any one of aspects 28-41, wherein the DCI includes a TCI state ID field indicating a TCI state indicating a beam, and wherein the DCI is used to schedule the beam when the channel used for beam update, the reference signal and the target channel and the scheduled channel are the same channel or the beam used for the scheduled channel and the beam used for beam update are defined in a common TCI state.

[0146] Aspect 43 is the method according to any one of Aspects 28-42, wherein the DCI includes a dedicated field indicating that the beam update is for uplink, downlink, or a combination of uplink and downlink.

[0147] Aspect 44 is the method according to any one of aspects 28-43, wherein the payload of the DCI is configured via RRC signaling.

[0148] Aspect 45 is the method according to any one of Aspects 28-34 and 42-44, wherein DCI schedules uplink transmissions or downlink transmissions.

[0149] Aspect 46 is the method according to any one of aspects 28-45, further comprising: receiving a second-level message, the second-level message including a second DCI or Media Access Control MAC-CE in a PDCCH or a PDSCH scheduled by the DCI, before determining that the DCI is associated with a beam update.

[0150] Aspect 47 is the method according to any one of aspects 28-46, wherein DCI is a format for beam updating.

[0151] Aspect 48 is the method according to any one of aspects 28-47, wherein a dedicated SS is configured at the UE for monitoring the DCI.

[0152] Aspect 49 is the method according to any one of aspects 28-48, further comprising sending a non-dedicated acknowledgment upon acknowledgment of receipt of the DCI, wherein the DCI schedules downlink or uplink transmissions.

[0153] Aspect 50 is the method according to any one of aspects 28-49, further comprising receiving an acknowledgment of receiving a dedicated acknowledgment of the DCI, wherein the DCI does not schedule downlink or uplink transmissions.

[0154] Aspect 51 is the method according to any one of aspects 28-50, further comprising sending a new beam indication after a time period following the transmission of confirmation.

[0155] Aspect 52 is the method according to any one of aspects 28-51, wherein the time period is determined based on a set of UE capability metrics of the UE.

[0156] Aspect 53 is the method according to any one of aspects 28-52, wherein the time period is determined based on the frequency modulation interval of the CC receiving the DCI and the frequency modulation interval of the CC transmitting the acknowledgment.

[0157] Aspect 54 is an apparatus for wireless communication, including at least one processor coupled to a memory, the at least one processor being configured to implement the method according to any one of aspects 1 to 27.

[0158] Aspect 55 is an apparatus for wireless communication, including at least one processor coupled to a memory, the at least one processor being configured to implement the method according to any one of aspects 28 to 53.

[0159] Aspect 56 is an apparatus for wireless communication, comprising components for implementing the method according to any one of aspects 1 to 27.

[0160] Aspect 57 is an apparatus for wireless communication, including components for implementing the method according to any one of aspects 28 to 53.

[0161] Aspect 58 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to implement the method of any one of aspects 1 to 27.

[0162] Aspect 59 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to implement the method of any one of aspects 28 to 53.

Claims

1. A method for performing wireless communication at a user equipment (UE), comprising: Receive downlink control information (DCI); Based on the DCI, determine whether the DCI is associated with a beam update for the uplink, downlink, or a combination of the uplink and downlink; as well as The UE determines a Transmission Configuration Indicator (TCI) state for the beam indicating the uplink, downlink, or combination of the uplink and downlink based on the DCI, wherein the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled with a Beam Update Network Temporary Identifier (RNTI) dedicated to beam updates, BU-RNTI, and the UE determines the DCI indicating the beam update for the uplink, downlink, or combination of the uplink and downlink based on the BU-RNTI.

2. The method of claim 1, wherein the UE determines that the beam update is for the uplink, the method further comprising: Uplink transmissions are sent using the beam based on the TCI state.

3. The method of claim 2, wherein the TCI status indicates at least two uplink channels.

4. The method of claim 1, wherein the UE determines that the beam update is for the downlink transmission, the method further comprising: The beam based on the TCI state is used to receive downlink transmissions.

5. The method of claim 4, wherein the TCI status indicates at least two downlink channels.

6. The method of claim 1, wherein the UE determines that the beam update is for the uplink and the downlink, the method further comprising: Uplink transmission is sent based on the beam update; as well as The downlink transmission is received based on the beam update.

7. The method of claim 1, wherein the DCI does not schedule transmissions.

8. The method of claim 1, wherein the DCI includes a Hybrid Automatic Repeat Request (HARQ) identifier ID field indicating the TCI status, the TCI status indicating the beam.

9. The method of claim 1, wherein the DCI includes a TCI state identifier ID field indicating the TCI state, the TCI state indicating the beam, and wherein: When the channel used for beam update, the reference signal, the target channel, and the channel being scheduled are the same; or The DCI is used to schedule the beam when the beam for the scheduled channel and the beam for the beam update are defined in a common TCI state.

10. The method of claim 1, wherein the DCI includes a dedicated field indicating that the beam update is for the uplink, the downlink, or the combination of the uplink and the downlink.

11. The method of claim 10, wherein the payload of the DCI is configured via Radio Resource Control (RRC) signaling.

12. The method according to claim 1, wherein the DCI schedules uplink transmission or downlink transmission.

13. The method according to claim 1, further comprising: Before determining that the DCI is associated with beam update, a second-level message including the second DCI or Media Access Control (MAC) control element CE, MAC-CE, is received in the Physical Downlink Control Channel (PDCCH) or the Physical Downlink Shared Channel (PDSCH) scheduled by the DCI.

14. The method of claim 1, wherein the DCI is a format for beam updating.

15. The method of claim 1, wherein a dedicated search space SS is configured at the UE for monitoring the DCI.

16. The method of claim 1, further comprising sending a non-dedicated acknowledgment upon confirmation of receipt of the DCI, wherein the DCI schedules downlink or uplink transmissions.

17. The method of claim 1, further comprising sending a dedicated acknowledgment of receipt of the DCI, wherein the DCI does not schedule downlink or uplink transmissions.

18. The method of claim 17, further comprising receiving a new beam indication after a time period following the transmission of the acknowledgment.

19. The method of claim 18, wherein the time period is determined based on a set of UE capability metrics of the UE.

20. The method of claim 18, wherein the time period is determined based on the frequency modulation interval of the component carrier CC of the received DCI and the frequency modulation interval of the CC of the transmitted acknowledgment.

21. A method for performing wireless communication at a user equipment (UE), comprising: Receive downlink control information (DCI); Based on the DCI, determine whether the DCI is associated with a beam update for the uplink, downlink, or a combination of the uplink and downlink; as well as The DCI determines a Transmission Configuration Indicator (TCI) state for a beam used for the uplink, the downlink, or the combination of the uplink and the downlink, wherein the DCI includes a sequence associated with the beam update, and the UE uses the sequence to determine whether the beam update is for the uplink, the downlink, or the combination of the uplink and the downlink.

22. The method of claim 21, wherein the DCI further comprises beam indication information, the beam indication information including a TCI state identifier ID indicating the TCI state of the beam.

23. The method of claim 21, wherein the sequence is different from the sequence used for scheduling transmissions.

24. The method of claim 21, wherein the CRC associated with the DCI is scrambled with a configured scheduled radio network temporary identifier RNTI, CS-RNTI, and wherein the sequence is different from the sequence used for activation or release of the semi-persistent scheduling SPS physical downlink shared channel PDSCH.

25. The method of claim 21, wherein the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled with a Cell Radio Network Temporary Identifier (RNTI), C-RNTI, and wherein the sequence is a combination of one or more of the following: Redundancy Version (RV) field, Frequency Domain Resource Allocation (FDRA) field, Time Domain Resource Allocation (TDRA) field, Hybrid Automatic Repeat Request (HARQ) Process Number field, or Modulation and Coding Scheme (MCS) field.

26. The method of claim 21, wherein the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled with a Cell Radio Network Temporary Identifier (RNTI) or a C-RNTI, and wherein the sequence is a combination of one or more of the following: a Redundancy Version (RV) field, a New Data Indicator (NDI) field, a Frequency Domain Resource Allocation (FDRA) field, a Hybrid Automatic Repeat Request (HARQ) process number field, or a Modulation and Coding Scheme (MCS) field.

27. The method of claim 21, wherein the UE determines that the beam update is for the uplink, the method further comprising: Uplink transmissions are sent using the beam based on the TCI state.

28. The method of claim 27, wherein the TCI status indicates at least two uplink channels.

29. The method of claim 21, wherein the UE determines that the beam update is for the downlink transmission, the method further comprising: The beam based on the TCI state is used to receive downlink transmissions.

30. The method of claim 29, wherein the TCI state indicates at least two downlink channels.

31. The method of claim 21, wherein the UE determines that the beam update is for the uplink and the downlink, the method further comprising: Uplink transmission is sent based on the beam update; as well as The downlink transmission is received based on the beam update.

32. The method of claim 21, wherein the DCI does not schedule transmissions.

33. The method of claim 21, wherein the DCI includes a dedicated field indicating that the beam update is for the uplink, the downlink, or the combination of the uplink and the downlink.

34. The method of claim 33, wherein the payload of the DCI is configured via Radio Resource Control (RRC) signaling.

35. The method of claim 21, wherein the DCI schedules uplink transmission or downlink transmission.

36. The method of claim 21, further comprising: Before determining that the DCI is associated with beam update, a second-level message including the second DCI or Media Access Control (MAC) control element CE, MAC-CE, is received in the Physical Downlink Control Channel (PDCCH) or the Physical Downlink Shared Channel (PDSCH) scheduled by the DCI.

37. The method of claim 21, wherein the DCI is a format for beam updating.

38. The method of claim 21, wherein a dedicated search space SS is configured at the UE for monitoring the DCI.

39. The method of claim 21, further comprising sending a non-dedicated acknowledgment upon confirmation of receipt of the DCI, wherein the DCI schedules downlink or uplink transmissions.

40. The method of claim 21, further comprising sending a dedicated acknowledgment of receipt of the DCI, wherein the DCI does not schedule downlink or uplink transmissions.

41. The method of claim 40, further comprising receiving a new beam indication after a time period following the transmission of the acknowledgment.

42. The method of claim 41, wherein the time period is determined based on a set of UE capability metrics of the UE.

43. The method of claim 41, wherein the time period is determined based on the frequency modulation interval of the component carrier (CC) of the received DCI and the frequency modulation interval of the CC of the transmitted acknowledgment.

44. An apparatus for performing wireless communication at a user equipment (UE), comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the apparatus to perform the method of any one of claims 1-43.

45. A method for conducting wireless communication at a base station, comprising: Send downlink control information (DCI) indicating beam updates for the uplink, downlink, or a combination of the uplink and downlink; as well as The DCI is indicated to be used for the beam update, wherein the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled with a dedicated beam update network temporary identifier RNTI, BU-RNTI.

46. ​​A method for conducting wireless communication at a base station, comprising: Send downlink control information (DCI) indicating beam updates for the uplink, downlink, or a combination of the uplink and downlink; as well as The DCI indicates that the DCI is used for the beam update, wherein the DCI includes a sequence associated with the beam update, and the UE uses the sequence to determine whether the beam update is for the uplink, the downlink, or the combination of the uplink and the downlink.

47. An apparatus for wireless communication at a base station, comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the apparatus to perform the method of any one of claims 45-46.

48. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising components for performing the method according to any one of claims 1 to 43.

49. An apparatus for wireless communication at a base station, the apparatus comprising components for performing the method according to any one of claims 45 to 46.

50. A computer-readable medium storing computer-executable code, including code for causing a user equipment (UE) to perform the method of any one of claims 1-43.

51. A computer-readable medium storing computer-executable code, including code for causing a base station to perform the method of any one of claims 45-46.

Images