Systems, methods, and apparatus for UL-configured, UE-initiated beam indication

By implementing UE-initiated beam reports in uplink configuration granting, utilizing PUSCH resources to transmit beam measurement information and receive downlink feedback, the problem of low beam management resource utilization efficiency in existing technologies is solved, and communication quality and adaptability are improved.

CN123125799APending Publication Date: 2026-11-17APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580025833.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-05
Filing Date
2025-04-04
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies fail to effectively utilize time and frequency resources to achieve active beam reporting by the UE, resulting in low beam management efficiency.

Method used

By using the permission (CG) configured in the uplink, the UE initiates a beam report or indication, and uses PUSCH resources to transmit beam measurement information at a specified time. The base station receives and generates downlink feedback.

Benefits of technology

It improves the efficiency and accuracy of beam management, ensures the communication quality between the UE and the base station, and adapts to dynamic wireless environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125799A_ABST
    Figure CN123125799A_ABST
Patent Text Reader

Abstract

This paper presents a solution for beam reporting or indication initiated by a User Equipment (UE) based on an authorization (CG) configured in the uplink (UL). A base station can transmit a UL CG to the UE for beam reporting or indication. The UL CG may correspond to the time and frequency resources of a Physical UL Shared Channel (PUSCH) with a transmission timing. The UE can detect a preselected event for beam reporting or indication for one or more beams, and in response to the preselected event, can generate a beam report. The UE can communicate the beam report to the base station using the PUSCH during the transmission timing. The beam report may include UL control information (UCI) with measurement information for one or more beams. The base station can receive the beam report, generate downlink (DL) feedback based on the beam report, and communicate the DL feedback to the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 575,580, filed April 5, 2024, the entire disclosure of which is incorporated herein by reference for all purposes. Technical Field

[0003] This disclosure relates to wireless communication networks and mobile device capabilities. Background Technology

[0004] Wireless communication networks and services are becoming increasingly dynamic, complex, and ubiquitous. For example, wireless communication networks can be developed to implement fourth-generation (4G), fifth-generation (5G), or new radio (NR) technologies. Such technologies can include solutions for enabling user equipment (UE) and network devices, such as base stations, to communicate with each other. One aspect of developing such technologies involves managing beams, channels, and signals between the UE and the base station. Attached Figure Description

[0005] This disclosure will be readily understood and implemented through the detailed description and accompanying drawings. The same reference numerals may designate the same features and structural elements. The drawings and corresponding descriptions are provided as non-limiting examples of aspects, embodiments, etc., of this disclosure, and references to “a” or “an” aspect, embodiment, etc., may not necessarily refer to the same aspect, embodiment, etc., and may mean at least one, one, or more, etc.

[0006] Figure 1 This is an example illustration of an overview of one or more specific implementations described herein.

[0007] Figure 2 This is a diagram of an example network based on one or more specific implementations described in this document.

[0008] Figure 3 This is a diagram illustrating an example procedure for beam indication initiated by a UE for uplink (UL) configuration-based authorization (CG) according to one or more specific implementations described herein.

[0009] Figure 4 This is a diagram illustrating an example of beam indication and downlink (DL) feedback initiated by a UE according to one or more specific implementations described herein.

[0010] Figure 5 This is a diagram illustrating an example of a Transmission Configuration Indicator (TCI) with Quasi-Co-address (QCL) information according to one or more specific implementations described herein.

[0011] Figure 6This is a diagram illustrating an example of beam management (BM) UL control information (UCI) according to one or more specific implementations described herein.

[0012] Figure 7 This is a diagram illustrating an example of DL feedback relative to the timing of UL CG transmission, based on one or more specific implementations described herein.

[0013] Figure 8 This is a diagram illustrating an example of DL feedback relative to the timing of UL CG transmission, based on one or more specific implementations described herein.

[0014] Figure 9 This is a diagram illustrating an example procedure for beam indication initiated by a UE based on a UL CG, according to one or more specific implementations described herein.

[0015] Figure 10 This is a diagram illustrating an example procedure for beam indication initiated by a UE based on a UL CG, according to one or more specific implementations described herein.

[0016] Figure 11 This is an illustration of an example of a component of a device according to one or more specific implementations described herein.

[0017] Figure 12 This is a block diagram illustrating components according to one or more specific embodiments described herein that are capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. Detailed Implementation

[0018] The following detailed description refers to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar features, elements, operations, etc. Additionally, this disclosure is not limited to the following description, as other specific embodiments and structural or logical changes may be made without departing from the scope of this disclosure.

[0019] Telecommunication networks may include user equipment (UEs) capable of communicating with base stations and / or other network access nodes. UEs and base stations may implement various technologies and communication standards that enable UEs and base stations to discover each other, establish and maintain connectivity, and exchange information in an ongoing manner. The objectives of such technologies may include processes, operations, configurations, and information for beam management.

[0020] Beam management can include beam measurement and reporting, beam indication, and beam fault and recovery. Beam measurement and reporting may involve the UE measuring characteristics related to the state or quality of a beam and reporting the measured characteristics to the base station. Beam indication may involve the base station indicating one or more downlink (DL) or uplink (UL) channels or signals to the UE. Beam fault recovery may involve the base station and the UE operating when a channel or signal fails to function as a reliable transmission medium and operating to restore the same or different channel or signal. A beam can refer to a channel, signal, or another type of wireless resource that enables wireless communication.

[0021] Beam management can involve a Transmission Configuration Indicator (TCI) signaling framework, where the beam for a target channel (e.g., Physical DL Shared Channel (PDSCH), Physical DL Control Channel (PDCCH), Channel State Information (CSI) Reference Signal (CSI-RS), etc.) can be indicated by the TCI. The TCI can include a signaling mechanism for informing the UE of the current configuration of DL transmission parameters. The TCI can include the source reference signal (RS) and the expected quasi-co-address (QCL) type to be applied. For example, a base station can schedule the PDSCH for the UE by transmitting UE DL Control Information (DCI) that includes the TCI of the PDSCH. The UE can self-configure simulated beamforming coefficients based on the TCI. For the PDCCH or CSI-RS, different signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Element (MAC-CE) signaling, etc.) can be used for beam indication. A unified TCI can also be applied to UL channels / signals.

[0022] A beam indication technique involving the use of a single TCI to schedule a single DL or UL channel or signal can be referred to as a standalone TCI framework. A beam indication technique involving the use of a set of TCIs (also known as a unified TCI (uTCI)) to schedule multiple DL or UL channels or signals can be referred to as a uTCI framework. The uTCI framework can be implemented in either Mode 1 or Mode 2. Mode 1 can be referred to as joint TCI and can involve applying a single TCI to both DL channels or signals and UL channels or signals. Mode 2 can be referred to as standalone TCI, where a DL TCI can be used to indicate multiple DL beams, and a UL TCI can be used to indicate multiple UL beams.

[0023] TCI status indication can include a first TCI status indication scheme (Scheme 1) or a second TCI status indication scheme (Scheme 2). Scheme 1 can include a common TCI indication for multiple UL or DL ​​channels or signals. The common TCI can be applied to dedicated PDCCH, PDSCH, PUCCH, and PUSCH. The common TCI can optionally be applied to aperiodic CSI-RS for beam management CSI, and sounding reference signals (SRS) for cellular band beam management, non-cellular band beam management, and access layer (AS) beam management. Whether the common TCI is applied to a channel or signal can be configured by RRC. Scheme 2 can include a dedicated TCI indication for a single channel or reference signal. For example, Scheme 2 can be applied to signals that are not subject to a common TCI indication (e.g., Scheme 1).

[0024] In summary, Scheme 1 can be applied to dedicated PDSCH, PDCCH, PUSCH, and PUCCH. Scheme 1 or Scheme 2 can be applied to a common PDSCH for intra-cell beam management, a common PDCCH for intra-cell beam management, or a non-periodic CSI-RS for beam management CSI. Scheme 2 can be applied to periodic CSI-RS, semi-persistent CSI-RS, a non-periodic CSI-RS for tracking, a common PDSCH for inter-cell beam management, or a common PDSCH for inter-cell beam management.

[0025] The base station can allocate time and frequency resources for downlink (DL) and uplink (UL) communication via configured grant (CG) or dynamic grant (DG). The base station can provide a DG for UL resources to the UE in response to a request from the UE. The base station can also provide a CG for UL resources to the UE without a request from the UE. The time and frequency resources, periodicity, etc., of the CG can be based on the corresponding type of service or signaling. The UL CG can be a Type 1 CG or a Type 2 CG. Type 1 CGs can be activated or deactivated using RRC signaling. Type 2 CGs can be activated or deactivated using DCI signaling.

[0026] Current available technologies fail to provide any or appropriate solutions for beam management because they do not enable UEs to actively participate in beam reporting in a way that allows for efficient use of time and frequency resources. Beam reporting (or beam indication) may include one or more types of information provided by the UE to a base station relating to the status, condition, or quality of a beam, channel, or signal. This information may include measurements performed by the UE, and the reported beam, channel, or signal may be associated with a base station serving the UE, another base station, another type of network access point, or another UE. One or more of the technologies described herein can achieve beam reporting or indication via a UL CG that includes PUSCH resources with transmission timing.

[0027] Figure 1 This is an example illustration of an overview 100 according to one or more specific embodiments described herein. As shown, overview 100 may include a UE 110 and a base station 120. Base station 120 may transmit a UL CG to UE 120 for beam reporting / indication (at 1). The UL CG may include time and frequency resources of a PUSCH with transmission timing. In some embodiments, base station 120 may also transmit configuration information to UE 120 for monitoring or measuring one or more beams associated with base station 120 or another device, such as beams of neighboring base stations (not shown). UE 120 may detect preselected events for beam reporting or indication, and in response to the preselected events, may generate a beam report (at 2). The beam report may include UL control information (UCI) with measurement information for one or more beams. UE 210 can use PUSCH to communicate a beam report to base station 222 during the transmission period, and base station 222 can receive the beam report, generate DL feedback based on the beam report, and communicate the DL feedback to UE 210 (at point 3). The DL feedback can serve as confirmation of whether the base station acknowledges the beam report. These and other features are described in more detail with reference to the remaining figures.

[0028] Figure 2 Example network 200 is an example network according to one or more specific implementations described herein. Example network 200 may include UE 210, 210-2, etc. (collectively referred to as "UE 210" and individually referred to as "UE 210"), radio access network (RAN) 220, core network (CN) 230, application server 240 and external network 250.

[0029] The systems and devices of Example Network 200 may operate according to one or more communication standards, such as 2G, 3G, 4G (e.g., LTE), and / or 5G (e.g., NR) communication standards of the 3rd Generation Partnership Project (3GPP). Additionally or alternatively, one or more of the systems and devices of Example Network 200 may operate according to other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., 6G, 7G, etc.), IEEE standards (e.g., Wireless Metropolitan Area Network (WMAN), Global Microwave Access Interoperability (WiMAX), etc.), and more.

[0030] As shown in the figure, UE 210 may include a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more wireless communication networks). Additionally or alternatively, UE 210 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as personal data assistants (PDAs), pagers, laptops, desktop computers, cordless phones, etc. In some implementations, UE 210 may include an Internet of Things (IoT) device (or IoT UE) that may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. Additionally or alternatively, the IoT UE may utilize one or more types of technologies such as machine-to-machine (M2M) communication or machine-type communication (MTC) (e.g., to exchange data with an MTC server or other device via a Public Land Mobile Network (PLMN), Proximity Services (ProSe) or Device-to-Device (D2D) communication, sensor networks, IoT networks, etc. Depending on the scenario, the M2M or MTC exchange of data may be machine-initiated, and the IoT network may include IoT UEs interconnected with short-lived connections (which may include uniquely identifiable embedded computing devices within an internet infrastructure). In some scenarios, IoT UEs can execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity in IoT networks.

[0031] UE 210 can communicate with and establish connections with one or more other UEs 210 via one or more radio channels 212, each of which may include a physical communication interface / layer. Connections may include M2M connections, MTC connections, D2D connections, SL connections, etc. Connections may involve a PC5 interface. In some implementations, UE 210 can be configured to discover each other, negotiate radio resources with each other, and establish connections with each other without the intervention or communication of RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., may involve communication with RAN node 222 or another type of network node.

[0032] UE 210 may communicate with each other using one or more radio channels 212. As described herein, UE 210 may communicate with RAN node 222 to request SL resources. RAN node 222 may respond to the request by providing UE 210 with a dynamic grant (DG) or a configured grant (CG) regarding SL resources. A DG may include grant based on a grant request from UE 210. A CG may involve granting resources without a grant request and may be based on the type of service offered (e.g., a service with strict timing or latency requirements). UE 210 may perform an idle channel assessment (CCA) procedure based on a DG or CG, select SL resources based on the CCA procedure and a DG or CG, and communicate with another UE 210 based on SL resources. UE 210 may communicate with RAN node 222 using licensed frequency bands and with another UE 210 using unlicensed frequency bands.

[0033] UE 210 can communicate with and establish a connection with RAN 220, which may involve one or more radio channels 214-1 and 214-2, each of which may include a physical communication interface / layer. In some implementations, the UE may be configured with dual connectivity (DC) as multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a UE capable of multiple receive and transmit (Rx / Tx) can use resources provided by different network nodes (e.g., 222-1 and 222-2) that may be connected via non-ideal backhaul (e.g., one network node provides NR access and another provides E-UTRA for LTE or NR access for 5G). In such scenarios, one network node may act as a primary node (MN) and the other as a secondary node (SN). MN and SN may be connected via a network interface, and at least MN may be connected to CN 230. Additionally, at least one of the MN or SN can operate via a shared spectrum channel access, and the functionality specified for UE 210 can be used for Integrated Access and Backhaul Mobile Terminal (IAB-MT). Similar to UE 210, the IAB-MT can access the network using one network node or two different nodes with an Enhanced Dual Connectivity (EN-DC) architecture or a New Radio Dual Connectivity (NR-DC) architecture, etc. In some specific implementations, the base station (as described herein) can be an example of network node 222.

[0034] As described herein, UE 210 may receive and store one or more configurations, instructions, and / or other information for implementing SL-U communication with quality and priority standards. PQI can be determined and used to indicate the QoS associated with SL-U communication (e.g., channels, data streams, etc.). Similarly, L1 priority values ​​can be determined and used to indicate the priority of SL-U transmissions, SL-U channels, SL-U data, etc. PQI and / or L1 priority values ​​can be mapped to CAPC values, and PQI, L1 priority, and / or CAPC can indicate SL Channel Occupancy Time (COT) sharing, Maximum Channel Occupancy Time (MCOT), time intervals for COT sharing, LBT configuration, traffic, and channel priority, etc.

[0035] As shown in the figure, UE 210 may also or alternatively connect to access point (AP) 216 via connection interface 218, which may include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 may include a wireless local area network (WLAN), a WLAN node, a WLAN endpoint, etc. Connection 216 may include a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 may include Wi-Fi. ® Router or other access point. Although in Figure 2 While not explicitly described, AP 216 can connect to another network (e.g., the Internet) without needing to connect to RAN 220 or CN230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE / WLAN radio-level technology with integrated IPsec tunneling (LWIP). LWA may involve RAN 220 configuring UE 210 in RRC_CONNECTED state to utilize LTE and WLAN radio resources. LWIP may involve UE 210 using WLAN radio resources (e.g., connection interface 218) to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) transmitted via connection interface 218 via IPsec protocol tunneling. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original IP packet header.

[0036] RAN 220 may include one or more RAN nodes 222-1 and RAN nodes 222-2 (collectively referred to as RAN node 222, and individually referred to as RAN node 222) that enable the establishment of channels 214-1 and 214-2 between UE 210 and RAN 220. RAN node 222 may include network access points configured to provide radio baseband functionality for data and / or voice connectivity between users and the network based on one or more communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, as an example, a RAN node may be an E-UT RAN node B (e.g., enhanced node B, eNodeB, eNB, 4G base station, etc.), a next-generation base station (e.g., 5G base station, NR base station, next-generation eNB (gNB), etc.). RAN node 222 may include roadside units (RSUs), transmit / receive points (TRxPs or TRPs), and one or more other types of ground stations (e.g., ground access points). In some scenarios, RAN node 222 can be dedicated physical equipment such as macro cell base stations and / or low-power (LP) base stations used to provide smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0037] Some or all of the RAN nodes or portions thereof may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a Centralized RAN (CRAN) and / or a Virtual Baseband Unit Pool (vBBUP). In these specific implementations, the CRAN or vBBUP may be implemented as follows: RAN function splitting, such as Packet Data Convergence Protocol (PDCP) splitting, where the Radio Resource Control (RRC) and PDCP layers can be operated by CRAN / vBBUP, and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; Medium Access Control (MAC) / Physical (PHY) layer splitting, where the RRC, PDCP, Radio Link Control (RLC), and MAC layers can be operated by CRAN / vBBUP, and the PHY layer can be operated by individual RAN nodes 222; or “lower PHY” splitting, where the upper portions of the RRC, PDCP, RLC, MAC, and PHY layers can be operated by CRAN / vBBUP, and the lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualization framework allows the idle processor cores of RAN node 222 to perform or execute other virtualization applications.

[0038] In some implementations, a single RAN node 222 may represent a single gNB distributed unit (DU) connected to the gNB control unit (CU) via a single F1 or other interface. In such implementations, the gNB-DU may include one or more remote radio headends or radio frequency (RF) front-end modules (RFEMs), and the gNB-CU may operate in a manner similar to CRAN / vBBUP by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources). Additionally or alternatively, one or more RAN nodes in RAN node 222 may be next-generation eNBs (i.e., gNBs) that provide Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE 210 and can be connected to the 5G core network (5GC) 230 via an NG interface.

[0039] Any RAN node in RAN 222 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 210. In some implementations, any RAN node in RAN 222 can perform various logical functions of RAN 220, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management. UE 210 can be configured to communicate with each other or with any of RAN nodes 222 on a multi-carrier communication channel using Orthogonal Frequency Division Multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, OFDMA communication technologies (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technologies (e.g., for uplink and ProSe or sidelink (SL) communication), but the scope of such implementations is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0040] In some implementations, the downlink resource grid can be used for downlink transmission from any of the RAN nodes in RAN node 222 to UE 210, and uplink transmission can utilize similar techniques. This grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid), representing the physical resources of the downlink in each time slot. Such time-frequency representations are common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises resource blocks that describe the mapping of certain physical channels to resource elements (REs). Each resource block may include a set of resource elements; in the frequency domain, this may represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0041] Furthermore, RAN node 222 can be configured to wirelessly communicate with UE 210 and / or with each other via licensed media (also referred to as “licensed spectrum” and / or “licensed band”), unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”), or a combination thereof. Licensed spectrum may correspond to channels or bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunications network activity), while unlicensed spectrum may correspond to one or more bands that are unrestricted for certain types of wireless activity. Whether a particular band corresponds to licensed or unlicensed media may depend on one or more factors, such as frequency allocations determined by public sector organizations (e.g., government agencies, regulatory bodies, etc.) or frequency allocations determined by private sector organizations involved in developing wireless communication standards and protocols.

[0042] To operate in unlicensed spectrum, UE 210 and RAN node 222 may use standalone unlicensed operation, licensed assisted access (LAA), eLAA, and / or feLAA mechanisms. In these specific implementations, UE 210 and RAN node 222 may perform one or more known medium sensing or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-Before-Speak (LBT) protocol.

[0043] The PDSCH can carry user data and higher-layer signaling to UE 210. The Physical Downlink Control Channel (PDCCH) can carry information such as transmission formats and resource allocations related to the PDSCH channel. The PDCCH can also inform UE 210 about transmission formats, resource allocations, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UE 210 within the cell) can be performed on any RAN node in RAN node 222 based on channel quality information fed back from any UE in UE 210. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., assigned to) each UE in UE 210.

[0044] One or more of the techniques described herein can use a UL CG to implement a UE-initiated beam reporting or indication. Base station 222 can transmit the UL CG to UE 210 for beam reporting / indication. The UL CG can correspond to the time and frequency resources of a PUSCH with a transmission timing. UE 210 can detect a preselected event for beam reporting or indication, and in response to the preselected event, can generate a beam report. UE 210 can communicate the beam report to base station 222 using a PUSCH during the transmission timing. The beam report may include a UCI with measurement information for one or more beams. Base station 222 can receive the beam report, generate DL feedback based on the beam report, and communicate the DL feedback to UE 210. Many other aspects and examples are also described herein.

[0045] RAN nodes 222 can be configured to communicate with each other via interface 223. In a specific implementation where the system is an LTE system, interface 223 may be an X2 interface. In an NR system, interface 223 may be an Xn interface. The X2 interface may be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or combinations thereof) connected to the Evolved Packet Core (EPC) or CN 230, or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U may provide flow control mechanisms for user data packets transmitted through the X2 interface and may be used to convey information about the delivery of user data between eNBs or gNBs. For example, X2-U can provide specific sequence number information for user data transmitted from the primary eNB (MeNB) to the secondary eNB (SeNB); information about the successful in-order delivery of PDCP Packet Data Units (PDUs) from the SeNB to the UE 210 for user data; information about PDCP PDUs not delivered to the UE 210; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; etc. X2-C can provide LTE in-network access mobility functions (e.g., including context passing from the source eNB to the target eNB, user plane transmission control, etc.), load management functions, and inter-cell interference coordination functions.

[0046] As shown in the figure, RAN 220 may be connected (e.g., communicatively coupled) to CN 230. CN 230 may include multiple network elements 232 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE210) connected to CN 230 via RAN 220. In some implementations, CN 230 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. Components of CN 230 may be implemented in a physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some implementations, network function virtualization (NFV) may be used to virtualize any or all of the aforementioned network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 230 may be referred to as a network slice, and a logical instance of a portion of CN 230 may be referred to as a network subslice. Network Functions Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions onto physical resources, including a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, proprietary hardware). In other words, NFV systems can be used to perform virtual or reconfigurable concrete implementations of one or more EPC components / functions.

[0047] As shown in the figure, CN 230, application server 240, and external network 250 can be interconnected via interfaces 234, 236, and 238, which may include IP network interfaces. Application server 240 may include one or more server devices or network elements (e.g., Virtual Network Functions (VNFs) that provide applications with access to IP bearer resources via CM 230 (e.g., Universal Mobile Telecommunications System Packet Service (UMTSPS) domain, LTE PS Data Service, etc.). Application server 240 may also or alternatively be configured to support one or more communication services for UE 210 via CN 230 (e.g., Voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.). Similarly, external network 250 may include one or more networks from various networks, including the Internet, thereby providing network access to various additional services, information, interconnectivity, and other network features to the mobile communication network and UE 210.

[0048] Figure 3This is a diagram illustrating an example procedure 300 for beam indication initiated by a UE based on a UL CG, according to one or more specific implementations described herein. Procedure 300 may be implemented by a UE 210 and one or more base stations 222. In some implementations, some or all of procedure 300 may be implemented by one or more other systems or devices (including...). Figure 2 The process is performed by one or more devices in the device. Additionally, process 300 may include... Figure 3 The operations shown are fewer, additional, in a different order, and / or arranged than those of other operations. In some specific implementations, some or all of the operations of process 300 may be performed independently, sequentially, simultaneously, etc., with respect to other operations of process 300. Therefore, the techniques described herein are not limited to those of other operations. Figure 3 The number, sequence, arrangement, timing, etc. of the operations or processes described.

[0049] As shown in the figure, UE 210 can communicate UE capability information (at 310) to base station 222. UE capability information can indicate UE 210's ability to participate in beam management. Examples of such capabilities may include beam monitoring and measurement capabilities, beam reporting capabilities, transmit and receive capabilities, TCI states and / or TCI state frameworks supported by UE 210, etc.

[0050] Base station 222 can communicate a ULCG (at 320) to UE 210. Base station 222 can generate a ULCG for resource allocation and can transmit the ULCG to UE 210. The ULCG may include time and frequency resources for PUSCH. The ULCG may include the number, periodicity, and duration of PUSCH resource transmission opportunities. Base station 222 can also communicate UE configuration information to UE 210. The UE configuration information may indicate one or more beams, channels, or signals to be monitored or measured by UE 210. The UE configuration information may also indicate one or more events, triggers, or conditions to be monitored by UE 210. The UE configuration information may also include one or more parameters, thresholds, or other types of information or instructions for operation according to the techniques described herein. Examples of such information may include unified TCI status, joint TCI status, DL unified TCI, UL unified TCI, etc. The ULCG and UE configuration information may be communicated together or separately and may involve RRC signaling, DCI signaling, MAC-CE, or another type of signaling.

[0051] In some implementations, as described herein, the UL CG used for UE-initiated beam indication can be a Type 1 UL CG, a Type 2 UL CG, or either Type 1 or Type 2 UL CG. For example, in some implementations, the UL CG used for UE-initiated beam indication can be activated and deactivated by RRC signaling. In other implementations, the UL CG used for UE-initiated beam indication can be activated and deactivated by DCI signaling. In still other implementations, both RRC signaling and DCI signaling can be used for CG activation or CG deactivation.

[0052] UE 210 can detect beam reporting events and generate beam reports (box 330). Beam reporting events can be pre-selected events. Pre-selected events can include events or conditions (based on existing communication standards) provided by base station 210 or indicated by configuration information locally stored by UE 210. Pre-selected events can include the occurrence of one or more conditions related to beams, channels, or signals (e.g., RSRP, SINR, etc.). These conditions may involve beam characteristics that have decreased to below, equal to, or exceeded a corresponding threshold, as measured or detected by UE 210. UE 210 can generate a beam report in response to detecting a pre-selected event. The beam report can identify or indicate the status or one or more characteristics of one or more beams and / or beams.

[0053] UE 210 can use the UL CG to communicate beam reports to base station 222 (box 340). Beam reports can be communicated using the time and frequency resources of PUSCH during the transmission period defined by the UL CG. The beam report may include a UCI. The UCI used for beam management may be referred to as the Beam Management (BM) UCI ​​(BM-UCI). The UCI may include a beam indicator, HARQ process number, Redundancy Version (RV) value, beam quality indicator, capability index value, etc. The beam report may also indicate the beam, beam type, and / or pre-selected event corresponding to the beam report. UE 210 may communicate the entire beam report during a single transmission period or over multiple transmission periods. UE 210 may retransmit the beam report until DL feedback is received. In some implementations, UE 210 may retransmit the beam report as long as DL feedback is not received, until the maximum number of beam report retransmissions has been reached.

[0054] Base station 222 can determine DL feedback based on beam reports (box 350). Base station 222 can also communicate DL feedback to UE 210 (box 360). For example, in response to receiving a beam report from UE 210, the base station can generate DL feedback. DL feedback may include an acknowledgment or confirmation that base station 222 has received the beam report. DL feedback may include an indication (e.g., timing) of the transmission of the beam report or a UL associated with the beam report, enabling UE 210 to determine the beam report corresponding to the DL feedback.

[0055] In some specific implementations, DL feedback may include additional information, such as instructions or configuration information that enable UE 210 to participate in beam fault recovery, switch to another beam, channel, or signal, etc. DL feedback may also or alternatively include acknowledgment of receipt of a UE-triggered / event-driven beam report or configuration of measurement resources and events for the UE to perform beam refinement. Since DL feedback can be used as acknowledgment that base station 222 has received a beam report, UE 210 can respond to receiving DL feedback by canceling subsequent retransmissions of the beam report. Additionally or alternatively, UE 210 can respond to DL feedback by changing the active beam used for communication or performing additional beam measurements. Example procedure 300 may also include one or more of the additional features, operations, or alternatives, or any combination thereof, described with reference to the accompanying figures and examples.

[0056] Figure 4 This is a diagram illustrating example 400 of beam indication and DL feedback initiated by a UE according to one or more specific implementations described herein. As shown, example 400 may include time represented along the horizontal axis, PUSCH transmission timings N to N+3, a preselected event between PUSCH N and PUSCH N+1, and DL feedback between PUSCH N+2 and PUSCH N+3. PUSCH transmission timings N to N+3 may be spaced according to UL CG periodicity. The PUSCH transmission timings N to N+3 and the ULCG periodicity between them may represent the UL CG provided to UE 210 by base station 222.

[0057] For the purpose of explaining Example 400, assume that base station 222 provides the depicted UL CG to UE 210. UE 210 detects a preselected event between transmission time N and transmission time N+1. Examples of preselected events may be changes in signal quality, RSRP, SINR, etc., exceeding a preselected threshold. UE 210 can respond to the event by generating a beam report corresponding to the detected preselected event and transmitting the beam report to the base station during UL CG transmission time N+1. The beam report may include a UCI. Base station 222 can receive the beam report and prepare DL feedback in response to the report.

[0058] Base station 222 can communicate DL feedback to UE 210. As shown, DL feedback can confirm the reception of a beam report transmitted during transmission timing N+1. DL feedback can confirm reception by, for example, including an indication of a detected pre-selected event, the transmission timing for transmitting the beam report, the PUSCH resource for transmitting the beam report, and / or by including one or more other types of information. In some implementations, DL feedback can confirm the reception of the beam report using DL resources associated with transmission timing N+1. Therefore, UE 210 can determine that the beam report was received by base station 222 based on the DL feedback.

[0059] In some implementations, UE 210 may generate a beam report and communicate it to base station 222 in response to the detection of a preselected event. In other implementations, UE 210 may generate a beam report and communicate it to the base station during each transmission period of the UL CG (e.g., regardless of whether a preselected event has been detected). Additionally or alternatively, UE 210 may communicate a beam report (e.g., UCI) regardless of whether UE 210 has UL data (e.g., transport block (TB), UL shared channel (UL-SCH) information, etc.) to be transmitted during the same UL CG transmission period. In other implementations, when UE 210 has UL data to be transmitted during the same UL CG transmission period, UE 210 may only communicate a beam report (e.g., UCI).

[0060] In some implementations, UE 210 can generate a UCI for beam reporting and a UCI for UL CG, and UE 210 can communicate both the beam reporting UCI and the CG-UCI to base station 222 during the UL CG transmission period. In some implementations, UE 210 can be configured to always report the beam reporting UCI and the CG-UCI together. In other implementations, UE 210 can be configured to report the beam reporting UCI with or without the CG-UCI.

[0061] In some implementations, UE 210 may generate a UCI for beam reporting and a UCI for unused transmission opportunities (UTO) (UTO-UCI). The UTO-UCI may indicate one or more unused CG UL transmission opportunities and / or portions (or resources) of one or more unused CG UL transmission opportunities. In some implementations, UE 210 may be configured to always report the beam reporting UCI and UTO-UCI together (e.g., even when there are no unused transmission opportunities). In other implementations, UE 210 may be configured to report the beam reporting UCI with or without a UTO-UCI.

[0062] Base station 222 can configure UE 210 using a unified TCI state list for measurement. This can be included in the ULCG or UE configuration information. For joint TCI modes or scenarios, the unified TCI state list can be selected from the dl-OrJointTCI-StateList-r17 data structure of the PDSCH-Config information element (IE). For individual TCI modes or scenarios, the unified TCI state list can be selected only from the DL unified TCI (e.g., from the TCI in the dl-OrJointTCI-StateList-r17 data structure of the PDSCH-Config IE). In other embodiments, the unified TCI state list for individual TCI modes can be selected from either the DL unified TCI or the UL TCI (both but not both simultaneously) (e.g., from the ul-TCI-StateList-r17 data structure of the BWP-UplinkDedicated IE). In still other embodiments, the unified TCI state list for individual TCI modes can be selected from a mixture of DL unified TCI and UL unified TCI.

[0063] Alternatively, base station 222 may not explicitly configure UE 210 to measure specific resources (e.g., unified TCI states). In such implementations, UE 210 may determine the list of unified TCI states to monitor and measure based on which unified TCI states are configured by RRC signaling or activated by MAC-CE. In some implementations, the list of unified TCI states to monitor and measure may be limited to those configured by RRC signaling. In other implementations, the list of unified TCI states to monitor and measure may be limited to those activated by MAC-CE.

[0064] Figure 5This is a diagram of example 500 of transmitting a TCI with QCL information according to one or more specific implementations described herein. As shown, example 500 may include a TCI status IE, which includes one or more QCL information IEs.

[0065] The TCI status IE can indicate a unified TCI status, which includes the TCI status ID and the signal associated with the unified TCI status. The QCL information IE can correspond to the signal that the UE 210 monitors and measures for beam management purposes. The QCL information IE includes characteristics of the signal source, such as serving cell index, bandwidth portion (BWP) ID, reference signal type (e.g., CSI-RS), reference signal ID, and QCL type (e.g., type A, type B, type C, and type D).

[0066] Base station 222 can provide UE configuration information (e.g., TCI state IE) to UE 210, which includes one or more unified TCI states for beam management purposes. In some implementations, when the TCI state IE includes two or more QCL sources, UE 210 can be configured to monitor, measure, and report only signals of QCL type D. In other implementations, UE 210 can be configured to monitor, measure, and report signals of different QCL types (e.g., any combination of QCL types AD). In some implementations, base station 222 can change which beams or signals are measured and reported by UE 210 via RRC signaling, DCI, MAC-CE, or another type of UE configuration information.

[0067] As described herein, a preselected event can be used as a trigger for UE 210 to generate a beam report and communicate the beam report to base station 222. The preselected event can correspond to a change in one or more signals of the unified TCI state. In some implementations, the preselected event may include UE 210 detecting that the unified TCI state has a measured quality superior to the active TCI state. In some implementations, the preselected event includes a measured quality difference that corresponds to a preselected event when the quality difference exceeds a quality threshold.

[0068] In some implementations, the preselected event may include UE 210 detecting that the quality of the active TCI state is below a threshold. Additionally or alternatively, the preselected event may include a quality difference that persists for more than a predetermined time threshold. In some implementations, one or more of the following—the quality threshold, the quality threshold difference, the time threshold, or another type of threshold—may be configured by base station 222 via RRC, DCI, or MAC-CE. One or more thresholds may also be defined according to communication standards. Examples of the measured signal and / or channel or signal quality may involve RSRP and / or SINR.

[0069] Figure 6 This is a diagram of Example 600 of a UCI according to one or more specific implementations described herein. As shown, Example 600 may include fields representing information that can be included in a UCI (also known as BM-UCI) and corresponding tables describing them. Beam reporting may include a UCI, and a UCI may include one or more of the fields and information represented in Example 600.

[0070] The beam indicator may indicate the preferred beam of UE 210 and may be the beam of the unified TCI monitored by UE 210. The beam quality indicator may include an indication of the quality of the preferred beam of UE 210. Beam quality may relate to RSRP, SINR, and / or another type of measured characteristic. In some implementations, beam quality may be reported along with each reported beam. In other implementations, beam quality may not be reported along with each reported beam. Additionally or alternatively, the beam quality indicator may include a capability index for each reported beam. The capability index (e.g., CapabilityIndex) may indicate the maximum number of SRS ports. The HARQ process number may include an indication of the HARQ process ID for the corresponding PUSCH. The redundancy version (RV) may include an indication of the RV for the corresponding PUSCH. The new data indicator may include an indication of whether the corresponding PUSCH is a new transmission or a retransmission.

[0071] In some implementations, beam pairs or multiple beams may be reported (e.g., unified TCI status). In such implementations, UE 210 may use two beams for receiving and / or transmitting. In other implementations, beam pairs or multiple beams may not be reported. In other implementations, UE 210 may measure and report the number (N) of beams or beam pairs. In such scenarios, N may be configured by the base station and / or by the communication standard implemented by UE 210.

[0072] The β offset factor can be used to determine the amount of resources used to reuse different types of UCI in the PUSCH. Base station 222 can configure UE 210 to use one or more types of β offsets via control information or another type of information. In some specific implementations, a common β offset can be used for BM-UCI. For example, a β offset used for another scenario (e.g., a β offset typically applied to CG, a β offset applied to UTO, etc.) can be applied to UCI used for beam reporting. An example of a common β offset can be represented as follows.

[0073] or

[0074] In other specific implementations, a β offset specifically designed for BM-UCI can be used. An example of such a β offset can be represented as follows.

[0075]

[0076] Base station 222 can configure UE 210 to use a UCI specifically for beam management and reporting (e.g., BM-UCI). In such a specific implementation, base station 222 can configure a β offset for BM-UCI compared to the case for other types of UCI.

[0077] Alternatively or additionally, BM-UCI may be carried solely by the UL CG of the PUSCH resource. In some implementations, BM-UCI may be co-coded with HARQ ACK. In such implementations, base station 222 may configure UE 210 regarding whether UE 210 should co-code BM-UCI with HARQ-ACK. Alternatively or additionally, when BM-UCI is co-coded or multiplexed with HARQ-ACK, UE 210 may use a β offset configured for HARQ-ACK (e.g., instead of a β offset configured for BM-UCI or for CG-UCI, UTO-UCI, etc.). In other implementations, UE 210 is not configured to co-code HARQ-ACK with BM-UCI.

[0078] In scenarios where BM-UCI and HARQ-ACK conflict or contradict each other, and UE 210 is not configured to multiplex BM-UCI and HARQ-ACK, UE 210 can determine whether to discard (e.g., abandon transmission) BM-UCI or HARQ-ACK. In some implementations, UE 210 can determine the priority associated with BM-UCI (e.g., the PUSCH resource authorized to carry BM-UCI) and the priority associated with HARQ-ACK. In some implementations, UE 210 can discard or abandon transmission of BM-UCI or HARQ-ACK based on which has the lower priority. Additionally or alternatively, UE 210 can use PUSCH resources to transmit either one with the higher priority. In other specific implementations, when HARQ-ACK has the same (or higher) priority as the PUSCH used to send BM-UCI, UE 210 may abandon sending BM-UCI via PUSCH resources and use PUSCH resources to send HARQ-ACK or use PUSCH resources other than those associated with BM-UCI to send HARQ-ACK.

[0079] Figure 7 This is a diagram illustrating example 700 of DL feedback relative to the timing of UL CG transmission according to one or more specific embodiments described herein. As shown, example 700 may include time represented along a horizontal axis, PUSCH transmission times N to N+3, a preselected event between PUSCH N and PUSCH N+1, and DL feedback between subsequent PUSCH N+3. PUSCH transmission times N to N+3 may be spaced out according to the periodicity of UL CG. For the purpose of explaining example 700, it is assumed that base station 222 provides the depicted UL CG to UE 210. It is also assumed that UE 210 detects the preselected event and transmits a beam report to base station 222, and that base station 222 responds by transmitting DL feedback to UE 210 at some point after PUSCH transmission time N+3. In some embodiments, DL feedback may be applied to PUSCH transmission times prior to the transmission of DL feedback, in addition to PUSCH transmission times within a minimum time duration (D) (e.g., PUSCH transmission time N+3). The minimum time duration can be configured by base station 222 and can be measured starting from the transmission of DL feedback.

[0080] In some implementations, base station 222 may provide configuration information to UE 210 indicating whether DL feedback is part of the beam management, beam reporting, and beam indication processes discussed herein. This may be provided via UE configuration information or another type of configuration information. DL feedback may be transmitted as DCI (e.g., using DCI format 0_1). DCI may involve Cyclic Redundancy Check (CRC) scrambling using a special Radio Network Temporary Identifier (RNTI) designated for beam management (e.g., BM-RNTI). In other implementations, a configured Scheduled (CS) RNTI (CS-RNTI) may be used for CRC scrambling. In this scenario, a 1-bit field may be used in DCI format 0_1 ​​to indicate whether CRC scrambling is applied to DL feedback. In other implementations, a DL Feedback Information (DFI) flag may be used in DCI format 0_1. In cases of size differences, the size of the DCI can be aligned with other or existing DCI formats 0_1 by setting the remaining bits to 0.

[0081] Figure 8 This is a diagram illustrating example 800 of DL feedback relative to the timing of UL CG transmission according to one or more specific embodiments described herein. As shown, example 800 may include time represented along a horizontal axis, PUSCH transmission times N through N+3, a preselected event between PUSCH N and PUSCH N+1, and DL feedback between subsequent PUSCH N+3. PUSCH transmission times N through N+3 may be spaced out according to the periodicity of UL CG. For the purpose of explaining example 800, it is assumed that base station 222 provides the depicted UL CG to UE 210. It is also assumed that UE 210 detects the preselected event and transmits a beam report to base station 222, and that base station 222 responds by transmitting DL feedback to UE 210 at some point after PUSCH transmission time N+3. In some specific embodiments, DL feedback may be applied to the most recent PUSCH transmission time prior to the minimum time duration (D) measured backward from the transmission from the DL feedback. In other words, DL feedback may not apply to previous PUSCH transmissions within the minimum time duration, or to PUSCH transmissions prior to other most recent PUSCH transmissions. The minimum time duration can be configured by base station 222 and can be measured from the start of DL feedback transmission.

[0082] In some implementations, DL feedback can be carried by a DCI (e.g., by DCI format 0_1). In such implementations, the DCI may include an indication of the joint unified TCI status corresponding to beam reporting and BM-UCI. The DCI may also, or alternatively, include one or more of the following: an indicator of the UL unified TCI status; a transmit power control (TPC) command for the PUSCH of the UL CG; and a bitmap of different HARQ processes. The bitmap may include 16 bits, and each bit may be mapped to a different HARQ process. A "1" may indicate that the corresponding HARQ process has been received, while a "0" may indicate that the corresponding HARQ process has not yet been received.

[0083] In some implementations, DCI may include an indicator of a unified TCI status. The indicated TCI status may be active after a certain or specified time period. This time period can be measured from the transmission time of DL feedback. Base station 222 may use RRC signaling, DCI signaling, or MAC-CE to configure a specified time period for UE 210. Alternatively, the specified time period may be based on a communication standard implemented by UE 210. In some implementations, the specified time period may be based on or equal to the minimum time duration provided to base station 222 via UE capability information.

[0084] Figure 9 This is a diagram illustrating an example procedure 900 for beam indication initiated by a UL CG-based UE according to one or more specific implementations described herein. Procedure 900 may be implemented by one or more baseband processors and / or UE 210. In some implementations, some or all of procedure 900 may be implemented by one or more other systems or devices (including...). Figure 2 The process is performed by one or more devices in the device. Additionally, process 900 may include... Figure 9 The operations shown are fewer, additional, in a different order, and / or arranged than those of other operations. In some specific implementations, some or all of the operations of process 900 may be performed independently, sequentially, simultaneously, etc., with respect to other operations of process 900. Therefore, the techniques described herein are not limited to those of other operations. Figure 9 The number, sequence, arrangement, timing, etc. of the operations or processes described.

[0085] As shown in the figure, process 900 may include receiving a UL CG (block 910) including a PUSCH with UL transmission timing. For example, UE 210 may provide UE capability information to base station 210. Base station 222 may respond by transmitting UE configuration information and / or a UL CG for beam management purposes. The UE configuration information may indicate one or more channels, signals, or beams to be monitored and measured by UE 210. The UE configuration information may also, or alternatively, include information and instructions for configuring UE 210 to generate beam reports for one or more beams, channels, or beams in response to one or more triggers, thresholds, and / or events.

[0086] Process 900 may further include: detecting a preselected event and generating a beam report (block 920). The preselected event may include an event or condition (based on existing communication standards) provided by base station 210 or indicated by configuration information locally stored by UE 210. The preselected event may include the occurrence of one or more conditions related to a beam, channel, or signal (e.g., SRS, SINR, etc.). This condition may relate to a beam characteristic measured or detected by UE 210 that has dropped to below, equal to, or above a corresponding threshold. UE 210 may generate a beam report in response to detecting a preselected event. The beam report may identify the status of one or more beams and / or one or more beam characteristics.

[0087] Process 900 may include: transmitting a beam report via UL CG resources (block 930). For example, UE 210 may transmit a beam report to base station 210 using time and frequency PUSCH resources during a transmission period of the UL CG provided by base station 222. The transmission period may be immediately following the detection of a preselected event and / or the generation of a beam report. In some implementations, UE 210 may generate and provide a beam report in response to the detection of a preselected event. In other implementations, UE 210 may generate and provide a beam report during each transmission period (regardless of whether a preselected event has been detected).

[0088] Process 900 may include receiving DL feedback (block 940). For example, UE 210 may receive DL feedback from base station 222. DL feedback may include confirmation that base station 222 has received the beam report. In some implementations, UE 210 may retransmit the beam report until DL feedback is received. In some implementations, UE 210 may retransmit the beam report as long as DL feedback is not received, until the maximum number of retransmissions has been reached. Example process 900 may also include one or more additional operations or any combination thereof, which may be described as aspects, features, or examples of the techniques described herein.

[0089] Figure 10 This is a diagram illustrating an example procedure 1000 for beam indication initiated by a UE based on a UL CG, according to one or more specific implementations described herein. Procedure 1000 may be implemented by base station 222. In some implementations, some or all of procedure 1000 may be implemented by one or more other systems or devices (including...). Figure 2 The process is performed by one or more devices in the device. Additionally, process 1000 may include... Figure 10 The operations shown are fewer, additional, in a different order, and / or arranged than those of other operations. In some specific implementations, some or all of the operations of process 1000 may be performed independently, sequentially, simultaneously, etc., with respect to other operations of process 1000. Therefore, the techniques described herein are not limited to those of other operations. Figure 10 The quantity, sequence, arrangement, timing, etc. of the operations or processes described herein.

[0090] As shown in the figure, process 1000 may include: communicating a UL CG (box 1010) that includes PUSCH resources with UL transmission timings. For example, in addition to the periodicity and / or number of corresponding transmission timings, base station 222 may also determine the time and frequency resources of the PUSCH to be allocated to UE 210. Base station 222 may generate a UL CG for resource allocation and may transmit the UL CG to UE 210.

[0091] Process 1000 may include receiving a beam report, including a UCI, via PUSCH and during UL transmission (block 1020). For example, base station 222 may receive the beam report from UE 210 via resources of the UL CG. The beam report may include a UCI associated with one or more beams, channels, or signals, and corresponding status or measurement information. The UCI may be associated with a beam from base station 222 and / or a beam from another base station 222.

[0092] Process 1000 may include generating DL feedback based on a beam report (block 1030). For example, base station 222 may generate DL feedback in response to a beam report from UE 210. DL feedback may include an acknowledgement or confirmation that base station 222 has received the beam report. In some implementations, DL feedback may include additional information, such as instructions or configuration information that enable UE 210 to participate in beam failure recovery, switch to another beam, channel, or signal. Process 1000 may also include communicating DL feedback in response to a beam report (block 1040). For example, base station 222 may communicate DL feedback to UE 210. Example process 1000 may also include one or more additional operations or any combination thereof, which may be described as aspects, features, or examples of the techniques described herein.

[0093] Figure 11 This is an illustration of examples of components of device 1100 according to one or more embodiments described herein. In some embodiments, device 1100 may include at least application circuitry 1102, baseband circuitry 1104, RF circuitry 1106, front-end module (FEM) circuitry 1108, one or more antennas 1110, and power management circuitry (PMC) 1112 coupled together as shown. The components of the illustrated device 1100 may be included in a UE or RAN node. In some embodiments, device 1100 may include fewer components (e.g., the RAN node may not utilize application circuitry 1102, but instead include a processor / controller to process IP data received from the CN or Evolved Packet Core (EPC). In some embodiments, device 1100 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in device 1100, etc.), or input / output (I / O) interfaces. In other implementations, the components described below may be included in more than one device (e.g., the circuitry may be included separately in more than one device for a cloud-RAN (C-RAN) implementation).

[0094] Application circuitry 1102 may include one or more application processors. For example, application circuitry 1102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include such memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 1100. In some specific implementations, the processor of application circuitry 1102 may process IP data packets received from the EPC.

[0095] Baseband circuit 1104 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1104 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 1106 and generate baseband signals for the transmit signal path of RF circuit 1106. Baseband circuit 1104 may interface with application circuitry 1102 to generate and process baseband signals and control the operation of RF circuit 1106. For example, in some implementations, baseband circuit 1104 may include a 3G baseband processor 1104A, a 4G baseband processor 1104B, a 5G baseband processor 1104C, or other existing, developing, or future generations of baseband processors 1104D (e.g., 5G, 6G, etc.). Baseband circuit 1104 (e.g., one or more baseband processors 1104A-1104D) may handle various radio control functions that enable communication with one or more radio networks via RF circuit 1106. In other embodiments, some or all of the functionality of the baseband processors 1104A-1104D may be included in a module stored in memory 1104G and executed via a central processing unit (CPU) 1104E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1104 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1104 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functionality. Specific implementations of the modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionalities in other respects.

[0096] In some implementations, memory 1104G may receive and / or store information and instructions for using UL CG to implement UE-initiated beam reporting or indication. Base station 222 may transmit UL CG to UE 210 for beam reporting / indication. UL CG may correspond to the time and frequency resources of PUSCH with a transmission timing. UE 210 may detect a preselected event for beam reporting or indication, and in response to the preselected event, may generate a beam report. UE 210 may communicate the beam report to base station 222 using PUSCH during the transmission timing. The beam report may include UCI with measurement information for one or more beams. Base station 222 may receive the beam report, generate DL feedback based on the beam report, and communicate the DL feedback to UE 210. Many other aspects and examples are also described herein.

[0097] In some embodiments, the baseband circuit 1104 may include one or more audio digital signal processors (DSPs) 1104F. The audio DSP 1104F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuit may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1104 and the application circuit 1102 may be implemented together, such as, for example, on a system-on-a-chip (SoC).

[0098] In some implementations, baseband circuit 1104 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1104 can support communication with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN), etc. Implementations of baseband circuit 1104 configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0099] RF circuit 1106 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuit 1106 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1106 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 1108 and providing a baseband signal to baseband circuit 1104. RF circuit 1106 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1104 and providing an RF output signal to FEM circuit 1108 for transmission.

[0100] In some embodiments, the receive signal path of RF circuit 1106 may include mixer circuit 1106A, amplifier circuit 1106B, and filter circuit 1106C. In some embodiments, the transmit signal path of RF circuit 1106 may include filter circuit 1106C and mixer circuit 1106A. RF circuit 1106 may also include synthesizer circuit 1106D for synthesizing frequencies used by mixer circuit 1106A in both the receive and transmit signal paths. In some embodiments, mixer circuit 1106A in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1108 based on the synthesized frequency provided by synthesizer circuit 1106D. Amplifier circuit 1106B may be configured to amplify the down-converted signal, and filter circuit 1106C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal can be provided to the baseband circuit 1104 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 1106A for the received signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0101] In some embodiments, the mixer circuit 1106A of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1106D to generate an RF output signal for the FEM circuit 1108. The baseband signal can be provided by the baseband circuit 1104 and can be filtered by the filter circuit 1106C. In some embodiments, the mixer circuit 1106A of the receive signal path and the mixer circuit 1106A of the transmit signal path can include two or more mixers and can be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1106A of the receive signal path and the mixer circuit 1106A of the transmit signal path can include two or more mixers and can be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1106A of the receive signal path and the mixer circuit 1106A of the transmit signal path can be arranged for direct down-conversion and direct up-conversion, respectively. In some specific implementations, the mixer circuit 1106A for the receive signal path and the mixer circuit 1106A for the transmit signal path can be configured for superheterodyne operation.

[0102] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1106 may include analog-to-digital converter (ADC) circuitry and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1104 may include a digital baseband interface for communication with the RF circuit 1106.

[0103] In some dual-mode implementations, separate radio IC circuitry may be provided to process the signal for each spectrum, but the scope of implementation is not limited in this respect. In some implementations, the synthesizer circuit 1106D may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, the synthesizer circuit 1106D may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0104] Synthesizer circuit 1106D can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1106A of RF circuit 1106. In some specific implementations, synthesizer circuit 1106D can be a fractional N / N+1 synthesizer.

[0105] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1104 or the application circuit 1102 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1102.

[0106] The synthesizer circuit 1106D of the RF circuit 1106 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include cascaded, tunable, delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0107] In some embodiments, the synthesizer circuit 1106D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 1106 may include an IQ / polarity converter.

[0108] FEM circuit 1108 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1110, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1106 for further processing. FEM circuit 1108 may also include a transmit signal path, which may include circuitry configured to amplify the signal provided by RF circuit 1106 for transmission via one or more of the one or more antennas 1110. In various specific implementations, amplification via the transmit signal path or the receive signal path may be performed only in RF circuit 1106, only in FEM circuit 1108, or in both RF circuit 1106 and FEM circuit 1108.

[0109] In some implementations, FEM circuit 1108 may include a TX / RX switch to switch between transmit mode operation and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 1106). The transmit signal path of FEM circuit 1108 may include: a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 1106); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more antennas in one or more antennas 1110).

[0110] In some implementations, the PMC 1112 manages the power supplied to the baseband circuitry 1104. Specifically, the PMC 1112 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1112 is typically included when the device 1100 can be battery powered, for example, when the device is included in a UE. The PMC 1112 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0111] Although Figure 11PMC 1112 is shown coupled only to baseband circuit 1104. However, in other specific implementations, PMC 1112 may be additionally or alternatively coupled to other components, such as, but not limited to, application circuit 1102, RF circuit 1106, or FEM 1108, and perform similar power management operations.

[0112] In some implementations, PMC 1112 can control or otherwise become part of various power-saving mechanisms of device 1100. For example, if device 1100 is in the RRC_Connected state, in which the device is still connected to the RAN node because it expects to receive traffic soon, the device can enter a state called Discontinuous Receive Mode (DRX) after the inactive period. During this state, device 1100 can be powered down for short intervals, thereby saving power.

[0113] If no data traffic activity persists for an extended period, device 1100 may transition to the RRC_Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1100 enters a very low power state and performs paging, during which the device periodically wakes up again to listen to the network and then powers off again. Device 1100 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0114] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device cannot connect to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

[0115] The processor of application circuit 1102 and the processor of baseband circuit 1104 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 1104 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functionality, while the processor of baseband circuit 1104 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functionality (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0116] Figure 12This is a block diagram illustrating components, according to some examples, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any or more methods discussed herein. Specifically, Figure 12 A schematic diagram of hardware resource 1200 is shown, including one or more processors (or processor cores) 1210, one or more memory / storage devices 1220, and one or more communication resources 1230, each of which is communicatively coupled via bus 1240. For a specific implementation utilizing node virtualization (e.g., NFV), an executable hypervisor can provide an execution environment for one or more network slices / subslices to utilize hardware resource 1200.

[0117] Processor 1210 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1212 and processor 1214.

[0118] The memory / storage device 1220 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1220 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0119] In some implementations, memory / storage device 1220 receives and / or stores information and instructions 1255 for using UL CG to implement UE-initiated beam reporting or indication. Base station 222 can transmit UL CG to UE 210 for beam reporting / indication. UL CG may correspond to the time and frequency resources of PUSCH with a transmission timing. UE 210 can detect a preselected event for beam reporting or indication, and in response to the preselected event, can generate a beam report. UE 210 can communicate the beam report to base station 222 using PUSCH during the transmission timing. The beam report may include UCI with measurement information for one or more beams. Base station 222 can receive the beam report, generate DL feedback based on the beam report, and communicate the DL feedback to UE 210. Many other aspects and examples are also described herein.

[0120] Communication resource 1230 may include interconnect components or network interface components or other suitable devices for communicating with one or more peripheral devices 1204 or one or more databases 1206 via network 1208. For example, communication resource 1230 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, Bluetooth, etc. ® Components (such as Bluetooth) ® Low power consumption, Wi-Fi ® Components and other communication components.

[0121] Instructions 1250 may include software, programs, applications, applets, or other executable code for causing at least one processor in processor 1210 to execute any or more of the methods discussed herein. Instructions 1250 may reside wholly or partially within at least one processor in processor 1210 (e.g., within the processor's cache memory), memory / storage device 1220, or any suitable combination thereof. Furthermore, any portion of instructions 1250 may be transferred to hardware resource 1200 from any combination of peripheral device 1204 or database 1206. Thus, the memory of processor 1210, memory / storage device 1220, peripheral device 1204, and database 1206 are examples of computer-readable and machine-readable media.

[0122] The embodiments and / or specific implementations herein may include subjects such as methods, components for performing actions or blocks of the method, at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform actions of a method, apparatus, or system for concurrent communication using various communication technologies according to the described specific implementations and embodiments.

[0123] In Embodiment 1, which may also include one or more embodiments described herein, a baseband circuit may include: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the one or more processors to: receive an uplink (UL) configuration grant (CG) from a base station via radio frequency (RF) circuitry, the UL CG including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; generate UL control information (UCI) including beam reports for downlink (DL) and / or uplink (UL) beams in response to the detection of a preselection event; and communicate the UCI to the base station via the RF circuitry during one of the multiple UL transmission opportunities.

[0124] In Embodiment 2, which may also include one or more embodiments described herein, the baseband processor is part of the user equipment (UE).

[0125] In Embodiment 3, which may also include one or more embodiments described herein, the one or more processors are configured to: receive the UL CG only via Radio Resource Control (RRC) signaling; receive the UL CG only via Downlink (DL) Control Information (DCI) signaling; or receive the UL CG via RRC signaling or DCI signaling.

[0126] In Embodiment 4, which may also include one or more embodiments described herein, the preselected event includes: detecting that the quality of a beam that meets the event triggering condition exceeds a quality threshold relative to the quality of another beam.

[0127] In Embodiment 5, which may also include one or more embodiments described herein, the preselected event includes the UL transmission timing among the plurality of UL transmission timings.

[0128] In Embodiment 6, which may also include one or more embodiments described herein, the one or more processors are further configured to: transmit the UCI via the RF circuit during the UL transmission timing, regardless of whether there is other UL data to be transmitted to the base station.

[0129] In embodiment 7, which may also include one or more embodiments described herein, the one or more processors are further configured to: transmit the UCI via the RF circuit during the UL transmission timing, provided that there is additional UL data to be transmitted to the base station.

[0130] In embodiment 8, which may also include one or more embodiments described herein, the preselected event includes a CG-UCI to be reported to the base station in conjunction with the UCI.

[0131] In embodiment 9, which may also include one or more embodiments described herein, the one or more processors are further configured to: transmit the UCI via the RF circuit during the UL transmission timing, regardless of whether there is a CG-UCI to be transmitted to the base station.

[0132] In embodiment 10, which may also include one or more embodiments described herein, the one or more processors are further configured to: transmit the UCI including the beam report via the RF circuitry along with CG Unused Transmission Occasion (UTO) information.

[0133] In embodiment 11, which may also include one or more embodiments described herein, the one or more processors are further configured to: convey the UCI including the beam report via the RF circuitry, regardless of whether there is CG Unused Transmission Occasion (UTO) information to be conveyed to the base station.

[0134] In embodiment 12, which may also include one or more embodiments described herein, the one or more processors are further configured to: receive instructions from the base station via the RF circuit for measuring one or more TCI states; and perform measurements on the one or more TCI states, wherein the UCI includes the measurements on the one or more TCI states.

[0135] In embodiment 13, which may also include one or more embodiments described herein, the one or more processors are further configured to: determine a unified TCI state list based on one or more TCI states activated by Radio Resource Control (RRC) signaling or Media Access Control (MAC) Control Element (MAC-CE) signaling; and perform measurements on the unified TCI state list, wherein the UCI includes the measurements associated with the unified TCI state list.

[0136] In embodiment 14, which may also include one or more embodiments described herein, the ULCG is associated with a unified TCI state having two quasi-co-located (QCL) information sources.

[0137] In embodiment 15, which may also include one or more embodiments described herein, the preselected event includes at least one of the following: the inactive unified TCI state has a better measurement than the active TCI state, or the quality level of the active TCI state fails to meet the corresponding threshold.

[0138] In embodiment 16, which may also include one or more embodiments described herein, the quality level is based on at least one of the following: a reference signal received power (RSRP) measurement; or a signal-to-interference plus noise ratio (SINR), and the corresponding threshold is configured by at least one of the following: RRC signaling, MAC-CE signaling, or DCI signaling.

[0139] In embodiment 17, which may also include one or more embodiments described herein, the UCI includes at least one of the following: a beam indicator, a beam quality indicator, a hybrid automatic repeat request (HARQ) number, a redundancy version, or an indication of whether the UCI corresponds to a new PUSCH transmission or a PUSCH retransmission.

[0140] In embodiment 18, which may also include one or more embodiments described herein, the UCI is configured to include reporting information for a single beam.

[0141] In embodiment 19, which may also include one or more embodiments described herein, the UCI includes a reported capability index for each beam, the capability index indicating the maximum number of probe reference signal (SRS) ports.

[0142] In embodiment 20, which may also include one or more embodiments described herein, the UCI includes an indication of the reported beam and the beam quality of the reported beam, the beam quality including at least one of the following: RSRP associated with the reported beam; or SINR associated with the reported beam.

[0143] In embodiment 21, which may also include one or more embodiments described herein, the base station is configured with a separate β offset to determine the amount of resources used to encode the UCI.

[0144] In embodiment 22, which may also include one or more embodiments described herein, the amount of resources used for encoding the UCI is determined using an existing β offset configured by the base station.

[0145] In embodiment 23, which may also include one or more embodiments described herein, the UCI is jointly encoded together with Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK).

[0146] In embodiment 24, which may also include one or more embodiments described herein, when a UL transmission of the UCI via the PUSCH conflicts with a UL transmission of a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) signal, if the PUSCH has the same priority as the HARQ-ACK signal, the PUSCH is not transmitted, and the HARQ-ACK signal is transmitted via the Physical UL Control Channel (PUCCH) or a different PUSCH; if the PUSCH has a different priority than the HARQ-ACK signal, the PUSCH or the HARQ-ACK signal with the lower priority is discarded.

[0147] In embodiment 25, which may also include one or more embodiments described herein, the one or more processors are further configured to receive downlink (DL) feedback from the base station via the RF circuit and in response to the UCI.

[0148] In embodiment 26, which may also include one or more embodiments described herein, the DL feedback includes a DCI with a cyclic redundancy check (CRC) scrambled by a beam-managed (BM) radio network temporary identifier (RNTI) (BM-RNTI).

[0149] In embodiment 27, which may also include one or more embodiments described herein, the DL feedback includes a DCI with a CRC scrambled by a configured scheduler (CS) RNTI (CS-RNTI).

[0150] In embodiment 28, which may also include one or more embodiments described herein, the DL feedback includes a DCI, the DCI including at least one of the following: an indication of a unified TCI status; an indication of a UL unified TCI status; a bitmap configured to indicate one or more successful HARQ processes and one or more unsuccessful HARQ processes; or a transmit power control (TPC) command for the PUSCH of the UL CG.

[0151] In embodiment 29, which may also include one or more embodiments described herein, the DL feedback includes a DCI, the DCI including a unified TCI status indicator associated with at least one TCI status, and the at least one TCI status becomes active when a duration measured from the transmission or reception time of the DCI expires, the duration including at least one of the following: a time amount defined by a communication standard, a time amount configured by RRC signaling, or a minimum time duration reported as UE capability information.

[0152] In embodiment 30, which may also include one or more embodiments described herein, the DL feedback includes DCIs that are applicable to all UL CGs transmitted prior to a configured duration (D) as measured from the transmission or reception time of the DCI.

[0153] In embodiment 31, which may also include one or more embodiments described herein, the DL feedback includes only the most recent UL CG transmitted prior to a configured duration (D) as measured from the transmission or reception time of the DCI.

[0154] In embodiment 32, which may also include one or more embodiments described herein, a user equipment (UE) includes: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the one or more processors to: receive an uplink (UL) configuration grant (CG) from a base station, the UL CG including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; generate UL control information (UCI) including beam reports for downlink (DL) beams and / or uplink (UL) beams in response to detecting a preselection event; and communicate the UCI to the base station during one of the multiple UL transmission opportunities.

[0155] In embodiment 33, which may also include one or more embodiments described herein, a method performed by a user equipment (UE) may include: receiving an uplink (UL) configuration grant (CG) from a base station, the UL CG including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; generating UL control information (UCI) including beam reports for downlink (DL) beams and / or uplink (UL) beams in response to detecting a preselected event; and communicating the UCI to the base station during one of the multiple UL transmission opportunities.

[0156] In embodiment 34, which may also include one or more embodiments described herein, a base station includes: radio frequency (RF) circuitry; a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to: communicate uplink (UL) configuration grant (CG) to a user equipment (UE), the uplink (UL) configuration grant (CG) including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; receive from the UE and during a UL transmission opportunity of the multiple UL transmission opportunities UL control information (UCI) including beam reports for downlink (DL) beams and / or uplink (UL) beams; generate downlink (DL) feedback based on the UCI; and communicate the DL feedback to the UE.

[0157] In embodiment 35, which may also include one or more embodiments described herein, a method performed by a base station may include: communicating an uplink (UL) configuration grant (CG) to a user equipment (UE), the uplink (UL) configuration grant (CG) including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; receiving from the UE and during a UL transmission opportunity of the multiple UL transmission opportunities UL control information (UCI) including beam reports for downlink (DL) beams and / or uplink (UL) beams; generating downlink (DL) feedback based on the UCI; and communicating the DL feedback to the UE.

[0158] The embodiments discussed above are also extended to methods, computer-readable media, and components plus functional claims and specific implementations, which may include one or more of the features or operations of any embodiment or combination of the embodiments mentioned above.

[0159] The foregoing description of exemplary examples, embodiments, aspects, etc., of the subject matter of this disclosure, including those described in the specification summary, is not intended to be exhaustive or to limit the disclosed aspects to their precise forms. While specific examples, embodiments, aspects, etc., have been described herein for illustrative purposes, various modifications may be contemplated within the scope of such examples, embodiments, aspects, etc., as will be appreciated by those skilled in the art.

[0160] In this regard, although the subject matter of this disclosure has been described in conjunction with various examples, embodiments, aspects, and corresponding drawings, it should be understood, where applicable, that other similar aspects may be used or that modifications and additions may be made to the disclosed subject matter to perform the same, similar, alternative, or substitute functions of the described subject matter without departing from the subject matter. Therefore, the disclosed subject matter should not be limited to any single example, embodiment, or aspect described herein, but should be interpreted in accordance with the breadth and scope of the appended claims.

[0161] In particular, regarding the various functions performed by the aforementioned components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise stated, the terminology used to describe such components (including references to "part") is intended to correspond to any component or structure that performs the specified functions of the described component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs the functions in the exemplary embodiments illustrated herein. Furthermore, although certain features have been disclosed with respect to only one of several embodiments, it may be desirable and advantageous for any given application to combine such features with one or more other features of other embodiments.

[0162] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise stated or clearly apparent from the context, “X adopts A or B” is intended to mean any natural inclusive arrangement of natural inclusive arrangements. That is, if X adopts A; X adopts B; or X adopts both A and B, then “X adopts A or B” is satisfied in any of the foregoing cases. Additionally, the articles “a” and “an” used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise stated or clearly apparent from the context to refer to the singular form. Furthermore, to the extent that the terms “comprising,” “including,” “having,” “having,” “with,” or variations thereof are used in the detailed description or claims, such terms are intended to be included in a manner similar to the term “including.” Additionally, in the case of discussing one or more numbered items (e.g., “first X,” “second X,” etc.), generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0163] As is widely recognized, the use of personally identifiable information should comply with privacy policies and measures that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. In particular, personally identifiable information data should be managed and disposed of to minimize the risk of unintentional or unauthorized access or use, and users should be clearly informed of the nature of authorized use.

Claims

1. A baseband circuit, the baseband circuit comprising: Memory; and One or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the one or more processors to: The uplink (UL) configuration permission (CG) is received from the base station via radio frequency (RF) circuitry, the UL CG indicating physical UL shared channel (PUSCH) resources and multiple UL transmission timings; In response to the detection of a preselected event, UL control information (UCI) is generated, including beam reports for the downlink (DL) and / or uplink (UL) beams; and The UCI is transmitted to the base station via the RF circuit and the PUSCH during the UL transmission timing of the plurality of UL transmission timings.

2. The baseband circuit of claim 1, wherein the baseband processor is part of a user equipment (UE).

3. The baseband circuit of claim 1, wherein the one or more processors are configured to: The UL CG is received only via Radio Resource Control (RRC) signaling; The UL CG is received only via downlink (DL) control information (DCI) signaling; The UL CG is received via RRC signaling or DCI signaling.

4. The baseband circuit according to claim 1, wherein the preselected event includes: The quality of a beam that meets the event triggering conditions is detected to exceed a quality threshold relative to the quality of another beam.

5. The baseband circuit according to claim 1, wherein the preselected event includes the UL transmission timing among the plurality of UL transmission timings.

6. The baseband circuit of claim 1, wherein the one or more processors are further configured to: The UCI is transmitted via the RF circuit during the UL transmission period, regardless of whether there is other UL data to be transmitted to the base station.

7. The baseband circuit of claim 1, wherein the one or more processors are further configured to: The UCI is transmitted via the RF circuit during the UL transmission period, provided that there is other UL data to be transmitted to the base station.

8. The baseband circuit of claim 1, wherein the preselected event includes a CG-UCI to be reported to the base station in conjunction with the UCI.

9. The baseband circuit of claim 1, wherein the one or more processors are further configured to: The UCI is transmitted via the RF circuit during the UL transmission period, regardless of whether there is a CG-UCI to be transmitted to the base station.

10. The baseband circuit of claim 1, wherein the one or more processors are further configured to: The UCI, including the beam report, is transmitted via the RF circuit along with the CG Unused Transmission Occasion (UTO) information.

11. The baseband circuit of claim 1, wherein the one or more processors are further configured to: The UCI, including the beam report, is transmitted via the RF circuit, regardless of whether there is CG Unused Transmission Occasion (UTO) information to be transmitted to the base station.

12. The baseband circuit according to claim 1, wherein: The one or more processors are further configured to: Receive instructions from the base station via the RF circuit for measuring one or more TCI states; and Perform measurements on one or more of the TCI states, and The UCI includes the measurement of one or more TCI states.

13. The baseband circuit according to claim 1, wherein: The one or more processors are further configured to: A unified TCI state list is determined based on one or more TCI states activated by Radio Resource Control (RRC) signaling or Media Access Control (MAC) Control Element (MAC-CE) signaling; and Measurements are performed on the unified TCI state list, and The UCI includes the measurement associated with the unified TCI status list.

14. The baseband circuit of claim 1, wherein the UL CG is associated with a unified TCI state having two quasi-co-located (QCL) information sources.

15. The baseband circuit of claim 1, wherein the preselected event includes at least one of the following: Inactive unified TCI states have superior measurement performance compared to active TCI states, or The quality level of the active TCI state failed to meet the corresponding threshold.

16. The baseband circuit according to claim 1, wherein: The quality level is based on at least one of the following: Reference signal received power (RSRP) measurement; or Signal-to-interference-plus-noise ratio (SINR), and The corresponding threshold is configured by at least one of the following: RRC signaling, MAC-CE signaling, or DCI signaling.

17. A user equipment (UE), the user equipment (UE) comprising: Memory; and One or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the one or more processors to: The system receives an authorization (CG) for uplink (UL) configuration from the base station, the UL CG including physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; In response to the detection of a preselected event, UL control information (UCI) is generated, including beam reports for the downlink (DL) beam and / or uplink (UL) beam; and The UCI is transmitted to the base station via the PUSCH during the UL transmission period of the plurality of UL transmission periods.

18. The UE of claim 17, wherein the UL CG is associated with a unified TCI state having two quasi-co-located (QCL) information sources.

19. A base station, the base station comprising: Radio frequency (RF) circuits; Memory; and One or more processors, the one or more processors being configured to, when executing instructions stored in the memory, cause the one or more processors to: The user equipment (UE) is informed of the uplink (UL) configuration grant (CG), which includes physical UL shared channel (PUSCH) resources and multiple UL transmission opportunities; UL control information (UCI) including beam reports for downlink (DL) beams and / or uplink (UL) beams is received from the UE via the PUSCH and during the UL transmission period of the plurality of UL transmission periods. The downlink (DL) feedback is generated based on the UCI. as well as The DL feedback is communicated to the UE.

20. The base station of claim 19, wherein the preselected event includes a CG-UCI reported to the base station in conjunction with the UCI.