Acknowledgement of beam report

Abstract

A user equipment (UE), baseband processor, or other network device (e.g., base station, next generation Node B, etc.) can operate to process or generate an acknowledgement (ACK) or non-acknowledgement (NACK) of a beam report to indicate an autonomous transmission configuration indicator (TCI) state update, which can be a TCI update without a corresponding TCI indication / trigger. The UE can determine the ACK / NACK in response to providing the beam report in the autonomous TCI state update. The UE can then activate the TCI state of the autonomous TCI state update in response to identifying the ACK, or retransmit the beam report for the autonomous TCI state update when a NACK is identified.

Description

Technical Field

[0001] This disclosure relates to wireless technologies including beam reporting and confirmation for beam reporting operations. Background Technology

[0002] Next-generation wireless communication systems, such as 5G or New Radio (NR) networks, will provide ubiquitous connectivity and access to information and the ability to share data globally. 5G networks and network slicing will be a unified, service-based framework that aims to meet common and sometimes conflicting performance standards and serve an extremely diverse range of application domains, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and others. Generally, NR will evolve based on 3GPP Long Term Evolution (LTE) Advanced technologies and additional Enhanced Radio Access Technologies (RATs) to achieve seamless and faster wireless connectivity solutions.

[0003] In New Radio (NR) 5G networks, load balancing is achieved through handover operations, redirection mechanisms during Radio Resource Control (RRC) signaling release, and the use of inter-frequency and Radio Access Technology (RAT) priority and offset parameters. However, network layer signaling, such as RRC signaling, involves long handover delays, long interruptions during handover, and high signaling overhead. Therefore, handover mechanisms do not always meet the goal of high-frequency, rapid cell changes in 5G networks. Thus, it is necessary to enhance the signaling mechanisms used for handover to improve handover latency and efficiency by increasing the use of dynamic control signaling. Attached Figure Description

[0004] Figure 1 An exemplary block diagram is shown illustrating an example of a user equipment (UE) that can be used in conjunction with the various embodiments (aspects) described herein, the UE being communicatively coupled via a network to a network component as a peer device.

[0005] Figure 2 A diagram is shown illustrating exemplary components of a device that may be employed according to the various aspects discussed herein.

[0006] Figure 3 An exemplary simplified block diagram of a user equipment (UE) wireless communication device or other network device / component (e.g., eNB, gNB) is shown according to various aspects.

[0007] Figure 4 Exemplary signaling for autonomous TCI status updates or beam-based TCI indications is shown, depending on various aspects.

[0008] Figure 5An exemplary processing flow for autonomous TCI status updates or beam-based TCI indications is shown, depending on various aspects.

[0009] Figure 6 Another exemplary processing flow for autonomous TCI status updates or beam-based TCI indications is shown, depending on various aspects.

[0010] Figure 7 An exemplary ACK / NACK configuration for autonomous TCI status updates or beam-based TCI indications is shown, depending on various aspects.

[0011] Figure 8 Exemplary ACK / NACK signaling for autonomous TCI status updates or beam-based TCI indications are shown, depending on various aspects.

[0012] Figure 9 Exemplary ACK / NACK signaling for autonomous TCI status updates or beam-based TCI indications are shown, depending on various aspects.

[0013] Figure 10 Exemplary ACK / NACK signaling for autonomous TCI status updates or beam-based TCI indications are shown, depending on various aspects.

[0014] Figure 11 Exemplary ACK / NACK signaling for autonomous TCI status updates or beam-based TCI indications are shown, depending on various aspects. Detailed Implementation

[0015] In light of various concerns regarding enhancements to the acknowledgment and non-acknowledgment signaling mechanisms for beam reports based on Autonomous Transport Configuration Indicator (TCI) state updates, TCI updates without beam indication can lead to potential mismatches where other network devices originating from the base station (e.g., gNodeB (gNB)) or the serving cell incorrectly decode beam report transmissions used in the autonomous TCI state update process. To remedy or prevent such mismatches, acknowledgment and non-acknowledgment signaling aspects for configuring autonomous TCI state updates via beam reports are disclosed.

[0016] Beam reports (e.g., Layer 1 (L1) L1-Reference Received Power (RSRP) / L1-Signal-to-Interference-plus-Noise Ratio (SINR) reports) can be transmitted via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH) in various schemes. For example, beam reports can be transmitted via PUCCH in a first scheme or via uplink control information (UCI) in a second scheme and multiplexed with PUSCH.

[0017] The action delay for updating the Transmission Configuration Indicator (TCI) state can depend on whether the beam has a known / unknown TCI state. A beam or TCI state can be known if certain conditions are met. When the TCI is known, the beam is measured or reported using a beam time window. At least one beam with a TCI state and an SNR higher than -3dB for that TCI state will be reported. These constitute the three conditions under which the TCI is considered known; otherwise, the beam is considered unknown. The action delay for an unknown TCI state can be quite long to account for the time it takes for the UE to track an unknown beam.

[0018] In autonomous TCI state updates or TCI indication based on beam reports, the TCI state can be updated without signaling a TCI indication or identifier to trigger a TCI state switch or update. The UE can update its TCI state autonomously by providing a beam report to the network or base station, rather than configuring the TCI state update through a signaling identifier or trigger that enables the beam to switch to the associated TCI state. After the UE reports a beam with a TCI state in its beam report, both the UE and the gNB ideally change the beam without using any additional TCI indication / identifier signaling. However, there may be a lack of ACK / NACK mechanisms or configurations for beam reports used in autonomous TCI state updates. Specifically, beam mismatch may occur even if the UE reports a beam, if the base station (gNB) does not correctly receive or decode the beam report. If a mismatch occurs, the gNB may not change / switch the beam to match the target beam that the UE has updated to. Therefore, effective and dynamic signaling is configured to prevent unknown mismatches using ACK / NACK indications from the base station, action delays and UE behavior for TCI updates without TCI indications or triggers, and a new mechanism for beam reporting is provided.

[0019] On one hand, the ACK / NACK mechanism is configured for autonomous TCI state updates via beam reports from the UE. Alternatively, UE behavior and action delays for TCI state updates can be configured based on the ACK / NACK signaling mechanism without signaling the TCI indicator / identifier or autonomous TCI state update to the UE. In response to identifying ACK / NACK from the signaling in response to the beam reported in the beam report, the UE can determine whether the beam report has been received and decoded. The UE can then activate the updated TCI state for autonomous TCI state updates based on ACK, or retransmit the beam report based on NACK.

[0020] ACKs can be transmitted based on a specific Radio Network Temporary Identifier (RNTI) that can be predefined and configured via Radio Resource Control (RRC) signaling or higher-layer signaling. For example, a gNB can generate an ACK based on an acknowledgment RNTI (ACK-RNTI). For example, based on a predefined configuration or RRC signaling, a UE can decode the transmission after beam reporting to identify ACK or NACK using the ACK-RNTI.

[0021] Alternatively or otherwise, ACK / NACK can be transmitted based on traditional downlink control information (DCI) formats, such as DCI used for scheduling the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH).

[0022] Alternatively or otherwise, ACK / NACK can be transmitted via the Dedicated Search Space (SS) or the Control Resource Set (CORESET) PDCCH.

[0023] Alternatively or otherwise, ACK / NACK can be transmitted via a Media Access Control (MAC) control element (MAC CE).

[0024] Alternatively, or otherwise, ACK / NACK can be determined based on timer operations.

[0025] Alternatively or otherwise, the UE may transmit beam reports via MAC CE.

[0026] Alternatively or otherwise, the action delay of UE behavior can be configured to activate the TCI state associated with beam reporting after ACK recognition.

[0027] Alternatively or otherwise, beam reports can be generated based on measurements of the Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS).

[0028] Alternatively or otherwise, the gNB or UE can configure beam reporting specifically for downlink (DL) TCI updates, uplink (UL) TCI updates, or both.

[0029] Other aspects and details of this disclosure are further described below with respect to the accompanying drawings.

[0030] Figure 1An exemplary architecture of system 100 for a network according to various implementations (various aspects) is illustrated. The following description is provided for an exemplary system 100 that can combine LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementation is not limited in this respect, and the implementation can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0031] like Figure 1 As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may include any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, etc.

[0032] In some implementations, any of UEs 101 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity Service (ProSe), or Device-to-Device (D2D) communication, sensor network, or IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0033] UE 101 can be configured to connect to (e.g., communicatively coupled to) a radio access network (RAN) 110. In implementations, RAN 110 can be a next-generation (NG) RAN or a 5G RAN, an evolved-UMTS terrestrial RAN (E-UTRAN), or a legacy RAN such as a UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN," etc., can refer to RAN 110 operating in an LTE or 4G system 100. UE 101 utilizes connections (or channels) 102 and 104, each connection (or channel) including a physical communication interface / layer.

[0034] Alternatively or otherwise, each UE in UE 101 may be configured with dual connectivity (DC) as multiple RATs or multiple radio dual connectivity (MR-DC), wherein a UE with multiple Rx / Tx capabilities may be configured to utilize resources provided by two different nodes (e.g., 111, 112, or other network nodes) capable of connecting via non-ideal backhaul connections, for example, one node providing NR access and the other providing E-UTRA for LTE or NR access for 5G. One node may act as a primary node (MN), and the other node may act as a secondary node (SN). The MN and SN may be connected via a network interface, and at least the MN may be connected to the core network 120. At least one of the MN and / or SN may operate using shared spectrum channel access. All functions specified for the UE may be available for Integrated Access and Backhaul Mobile Terminal (IAB-MT). Similar to UE 101, the IAB-MT may use one network node or two different nodes with EN-DC architecture, NR-DC architecture, etc., to access the network.

[0035] In MR-DC, a group of serving cells associated with a primary node can be configured as a primary cell group (MCG), including a special cell (SpCell) acting as the primary cell (PCell), and optionally one or more secondary cells (SCells). The MCG can be a radio access node providing control plane connectivity to the core network (CN) 120; for example, it can be a primary eNB (in EN-DC), a primary ng-eNB (in NGEN-DC), or a primary gNB (in NR-DC and NE-DC). A SpCell can refer to the PCell of an MCG or the primary / secondary cell (PSCell) of a secondary cell group (SCG), depending on the MAC entity associated with the MCG or SCG, respectively. In MR-DC, an SCG can be a group of serving cells associated with a SN, including SpCells acting as PSCells, and optionally one or more SCells.

[0036] In this example, connections 102 and 104 are shown as air interfaces for communication coupling and can be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, Cellular PTT (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP LTE protocols, 5G protocols, NR protocols, and / or any other communication protocols discussed herein. In an implementation, UE 101 can directly exchange communication data via ProSe interface 105. ProSe interface 105 may alternatively be referred to as SL interface 105 and may include one or more logical channels, including but not limited to the Physical Side Link Control Channel (PSCCH), Physical Side Link Shared Channel (PSSCH), Physical Side Link Discovery Channel (PSDCH), and Physical Side Link Broadcast Channel (PSBCH).

[0037] The diagram shows UE 101b configured to access AP 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN terminal 106", "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 106 will include Wireless Fibre. Router. In this example, AP106 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 101b, RAN 110, and AP 106 can be configured to utilize LTE-WLAN aggregation (LWA) operation and / or LTE / WLAN radio-level operation integrated with IPsec tunneling (LWIP). LWA operation may involve RAN nodes 111a-111b configuring UE 101b, which is in the Radio Resource Control (RRC_CONNECTED) state, to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0038] RAN 110 includes one or more access nodes (ANs) or RAN nodes 111a and 111b (collectively referred to as "multiple RAN nodes 111" or "RAN node 111") that enable connections between 102 and 104. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, Node B, RSU, Transmit-Receive Point (TRxP), or TRP, etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 111 (e.g., gNB) operating in NR or 5G system 100, and the terms "E-UT RAN node," etc., can refer to RAN node 111 (e.g., next-generation node B (gNB)) operating in LTE or 5G system 100. According to various implementation schemes, RAN node 111 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations, which are used to provide femtocell base stations, picocell base stations or other similar cells with smaller coverage area, smaller user capacity or higher bandwidth compared to macro cells.

[0039] In some implementations, all or part of RAN node 111 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a Centralized RAN (CRAN) and / or a Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning such as Packet Data Convergence Protocol (PDCP) partitioning, where the Radio Resource Control (RRC) and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 111; Media Access Control (MAC) / Physical (PHY) layer partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a “lower PHY” partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of multiple RAN nodes 111 to execute other virtualized applications.

[0040] In some implementations, a single RAN node 111 may represent a gNB distributed unit (DU) connected to the gNB central unit (CU) via a respective F1 interface. In these implementations, the gNB-DU may include one or more remote radio headers or RF front-end modules (RFEMs) (not shown), and the gNB-CU may be operated by a server (not shown) located in RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more of the plurality of RAN nodes 111 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to UE 101 and is connected to 5GC via an NG interface.

[0041] Any node in RAN 111 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 101. In some implementations, any node in RAN 111 can perform various logical functions of RAN 110, 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 and data packet scheduling, and mobility management.

[0042] In the implementation, UE 101 may be configured to communicate with each other or with any of the RAN nodes 111 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 technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0043] In some implementations, the downlink resource grid can be used for downlink transmissions from any node in RAN 111 to UE 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is 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 multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0044] According to various implementations, UE 101 and RAN node 111 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0045] The PDSCH carries user data and higher-layer signaling to multiple UEs 101. The Physical Downlink Control Channel (PDCCH) carries information such as transmission format and resource allocation related to the PDSCH channel. It also informs UEs 101 about transmission format, resource allocation, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UEs 101b within the cell) can be performed at any RAN node of RAN node 111 based on channel quality information fed back from any of the UEs in UE 101. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UE 101.

[0046] PDCCH uses Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, 8, 16) can be defined.

[0047] In all aspects of system 100 being a 5G or NR system, interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to 5GC 120, between a RAN node 111 (e.g., a gNB) connected to 5GC 120 and an eNB, and / or between two eNBs connected to 5GC 120. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 101 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more RAN nodes 111. This mobility support may include context transfer from the old (source) serving RAN node 111 to the new (destination) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (destination) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer and a user plane GPRS Tunneling Protocol (GTP-U) layer on top of the User Datagram Protocol (UDP) and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of the Flow Control Transport Protocol (SCTP). SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0048] RAN 110 is shown communicatively coupled to the core network—in this embodiment, communicatively coupled to the core network (CN) 120. CN 120 may include a plurality of network elements 122 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. Components of CN 120 may be implemented in a single 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 embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network subslice. Network Function Virtualization (NFV) architectures and infrastructure may be used to virtualize one or more network functions onto a physical resource comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally performed by proprietary hardware). In other words, NFV systems can be used to execute virtual or reconfigurable concrete implementations of one or more Evolution Packet Core (EPC) components / functions.

[0049] Generally, application server 130 may be an element that provides IP bearer resources for use with the core network (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services for UE 101 via EPC 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0050] In various respects, CN 120 may be a 5GC (referred to as "5GC 120", etc.), and RAN 110 may be connected to CN 120 via NG interface 112. In an implementation, NG interface 112 may be divided into two parts: a Next Generation (NG) User Plane (NG-U) interface 114, which carries traffic data between RAN node 111 and the User Plane Function (UPF); and an S1 Control Plane (NG-C) interface 115, which is the signaling interface between RAN node 111 and the Access and Mobility Management Function (AMF).

[0051] In all respects, when CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 can be connected to CN 120 via S1 interface 112. In the implementation, S1 interface 112 can be divided into two parts: S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and S-GW; and S1-MME interface 115, which is the signaling interface between RAN node 111 and MME.

[0052] The core NW element / component 122 may include one or more of the following functions and network components: Authentication Server Function (AUSF); Access and Mobility Management Function (AMF); Session Management Function (SMF); Network Exposure Function (NEF); Policy Control Function (PCF); Network Repository Function (NRF); Unified Data Management (UDM); Application Function (AF); User Plane (UP) Function (UPF); and Network Slice Selection Function (NSSF).

[0053] UPF can, for example, act as an anchor point for mobility within and between RATs, an external Protocol Data Unit (PDU) session point interconnecting with a data network (DN), and a branch point supporting multihomed PDU sessions. UPF can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing on the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), uplink traffic authentication (e.g., Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF may include an uplink classifier to support traffic routing to the data network. DN can be various network operator services, Internet access, or third-party services, including or similar to application servers. UPF can interact with SMF via an N4 reference point between SMF and UPF.

[0054] For example, the AUSF can store data for UE 101 authentication and handle authentication-related functions. The AUSF can utilize common authentication frameworks for various access types. The AUSF can communicate with the AMF via the N12 reference point between the AMF and AUSF; and with the UDM via the N13 reference point between the UDM and AUSF. Additionally, the AUSF can present an interface based on Nausf services.

[0055] The Access Management Function (AMF) can, for example, be responsible for registration management (e.g., registering UE 101, etc.), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF can be the termination point of the N11 reference point between the AMF and SMF. The AMF can provide transmission of SM messages between UE 110 and the SMF and act as a transparent proxy for routing SM messages. The AMF can provide transmission of SMS messages between UE 101 and the Short Message Service (SMS) Function (SMSF). The AMF can act as a Security Anchoring Function (SEAF), which may include interaction with the AMF and UE 101 and / or receiving intermediate keys established due to the UE 101 authentication process. In the case of authentication using the Universal Subscriber Identity Module (USIM), the AMF can retrieve security material from the AMF. The AMF may include a Single Connection Mode (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF can be the termination point of the RAN control plane (CP) interface, which may include or be the N2 reference point between (R)AN 110 and the AMF; and the AMF is the termination point of the non-access stratum (NAS) (N1) signaling and performs NAS encryption and integrity protection.

[0056] The AMF can support NAS signaling with UE 101 via a non-3GPP (N3) Interoperability Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be the termination point of the N2 interface between the control plane (R)AN 110 and the AMF, and can also be the termination point of the N3 reference point between the user plane (R)AN 101 and the UPF. Therefore, the AMF can process N2 signaling from the SMF and AMF for PDU sessions and QoS, encapsulate / decapsulate packets for Internet Protocol (IP) Security (IPSec) and N3 tunneling, mark N3 user plane packets in the uplink, and perform QoS corresponding to the N3 packet markings, thus taking into account the QoS requirements associated with such markings received via N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between UE 101 and AMF via the N1 reference point between UE 101 and AMF, and relay uplink and downlink user plane packets between UE 101 and UPF. The N3IWF also provides a mechanism for establishing IPsec tunnels using UE 101. The AMF can present an interface based on Namf services and can be the N14 reference point between two AMFs and the 5G Equipment Identity Register (5G-EIR). Figure 1 The terminus of the N17 reference point (not shown in the image) between the reference points.

[0057] UE 101 can register with the AMF to receive network services. Registration Management (RM) is used to register or deregister UE 101 with the network (e.g., the AMF) and to establish a UE context within the network (e.g., the AMF). UE 101 can operate in either RM-REGISTRED or RM-DEREGISTRED state. In RM-DEREGISTRED state, UE 101 is not registered with the network, and the UE context in the AMF does not maintain valid location or routing information for UE 101, therefore the AMF cannot reach UE 101. In RM-REGISTERRED state, UE 101 is registered with the network, and the UE context in the AMF maintains valid location or routing information for UE 101, therefore the AMF can reach UE 101. In RM-REGISTERED state, UE 101 can perform mobility registration update procedures, periodic registration update procedures triggered by the expiration of periodic update timers (e.g., notifying the network that UE 101 is still active), and registration update procedures to update UE capability information or renegotiate protocol parameters with the network, etc.

[0058] The AMF can store one or more RM contexts for UE 101, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc., which in particular indicates or stores the registration status and periodic update timers for each access type. The AMF can store 5GC Mobility Management (MM) contexts that are the same as or similar to the Enhanced Packet System (EPS) MM ((E)MM) context. In various implementations, the AMF can store Coverage Enhancement (CE) Mode B limitation parameters for UE 101 in the associated MM or RM context. The AMF can derive values ​​from UE usage setting parameters already stored in the UE context (and / or MM / RM context) when needed.

[0059] Figure 2Exemplary components of device 200 according to some aspects are shown. In some aspects, device 200 may include at least application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 coupled together as shown. The components of the illustrated device 200 may be included in a UE or RAN node. In some aspects, device 200 may include fewer components (e.g., the RAN node may not utilize application circuitry 202, but instead include a processor / controller to process IP data received from a CN such as 5GC 120 or Evolved Packet Core (EPC). In some aspects, device 200 may include additional components such as 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 200, etc.), or input / output (I / O) interfaces. In other respects, 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 cloud-RAN (C-RAN) implementation).

[0060] Application circuit 202 may include one or more application processors. For example, application circuit 202 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 a 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 200. In some aspects, the processor of application circuit 202 may process IP data packets received from EPC.

[0061] Baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 206 and generate baseband signals for the transmit signal path of RF circuitry 206. Baseband circuitry 204 may interact with application circuitry 202 to generate and process baseband signals and control the operation of RF circuitry 206. For example, in some aspects, baseband circuitry 204 may include a third-generation (3G) baseband processor 204A, a fourth-generation (4G) baseband processor 204B, a fifth-generation (5G) baseband processor 204C, or other existing, under development, or future generations (e.g., second-generation (2G), sixth-generation (6G), etc.) baseband processor 204D. Baseband circuitry 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions that can communicate with one or more radio networks via RF circuitry 206. In other aspects, some or all of the functions of the baseband processors 204A-D may be included in modules stored in memory 204G and may be executed via a central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some aspects, the modulation / demodulation circuitry of the baseband circuitry 204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some aspects, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. The aspects of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other aspects.

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

[0063] In some aspects, baseband circuit 204 can provide communication compatible with one or more radio technologies. For example, in some aspects, baseband circuit 204 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. The aspect in which baseband circuit 204 is configured to support radio communication with more than one radio protocol may be referred to as a multimode baseband circuit.

[0064] RF circuit 206 can communicate with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various aspects, RF circuit 206 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 206 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 208 and providing a baseband signal to baseband circuit 204. RF circuit 206 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 204 and providing an RF output signal to FEM circuit 208 for transmission.

[0065] In some aspects, the receive signal path of RF circuit 206 may include mixer circuit 206a, amplifier circuit 206b, and filter circuit 206c. In some aspects, the transmit signal path of RF circuit 206 may include filter circuit 206c and mixer circuit 206a. RF circuit 206 may also include synthesizer circuit 206d for synthesizing the frequency used by mixer circuit 206a in both the receive signal path and transmit signal path. In some aspects, mixer circuit 206a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 208 based on the synthesized frequency provided by synthesizer circuit 206d. Amplifier circuit 206b may be configured to amplify the down-converted signal, and filter circuit 206c 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 may be provided to baseband circuit 204 for further processing. In some respects, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some respects, the mixer circuit 206a of the receiving signal path may include a passive mixer, but the scope of each respects is not limited in this respect.

[0066] In some respects, the mixer circuit 206a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuitry system 206d to generate an RF output signal for the FEM circuitry 208. The baseband signal can be provided by the baseband circuitry 204 and can be filtered by the filter circuitry 206c.

[0067] In some aspects, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some aspects, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some aspects, the mixer circuit 206a for the receive signal path and the mixer circuit 206a may be arranged for direct down-conversion and direct up-conversion, respectively. In some aspects, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may be configured for superheterodyne operation.

[0068] In some aspects, the output baseband signal and the input baseband signal may be analog baseband signals, but the range of aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative aspects, RF circuit 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuit 204 may include a digital baseband interface for communicating with RF circuit 206.

[0069] In some dual-mode applications, separate radio IC circuits can be provided to handle signals for each spectrum, but the range of applications is not limited in this respect.

[0070] In some respects, synthesizer circuit 206d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the range of respects is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 206d can be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0071] Synthesizer circuit 206d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some respects, synthesizer circuit 206d can be a fractional N / N+1 synthesizer.

[0072] In some respects, the frequency input can be provided by a voltage-controlled oscillator (VCO), but this is not required. The divider control input can be provided by the baseband circuit 204 or the application circuit 202 according to the desired output frequency. In some respects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application circuit 202.

[0073] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, 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 exemplary aspects, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these aspects, 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0074] In some aspects, the synthesizer circuit 206d can be configured to generate a carrier frequency as the output frequency, while in others, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used 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 aspects, the output frequency can be the LO frequency (fLO). In some aspects, the RF circuit 206 may include an IQ / polarity converter.

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

[0076] In some aspects, FEM circuit 208 may include a TX / RX switch to switch between transmit 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 206). The transmit signal path of FEM circuit 208 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of one or more antennas 210).

[0077] In some respects, the PMC 212 can manage the power supplied to the baseband circuitry 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 212 is typically included when the device 200 is capable of being battery powered, for example, when the device is included in a UE. The PMC 212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0078] and Figure 2 The PMC 212 is shown coupled only to the baseband circuit 204. However, in other respects, the PMC 212 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 202, the RF circuit 206, or the FEM circuit 208) or perform similar power management operations for other components.

[0079] In some respects, the PMC 212 can control or otherwise become part of various power-saving mechanisms of the device 200. For example, if the device 200 is in the RRC_Connected state, where it remains connected to the RAN node as expected to receive traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the device 200 can be powered down for short intervals, thereby saving power.

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

[0081] 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 is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0082] The processor of application circuit 202 and the processor of baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 204 can be used alone or in combination to perform Layer 3 (L3), Layer 2 (L2), or Layer 1 (L1) functions, while the processor of application circuit 202 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include the Radio Resource Control (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.

[0083] refer to Figure 3 This diagram illustrates a user equipment (UE) device or other network device / component (e.g., gNB, eNB, or other participating network entity / component). Device 300 includes: one or more processors 310 (e.g., one or more baseband processors) including processing circuitry and associated interfaces; transceiver circuitry 320 (e.g., including RF circuitry, which may include transmitter circuitry (e.g., associated with one or more transmit chains) and / or receiver circuitry (e.g., associated with one or more receive chains), the transmitter and receiver circuitry may employ common circuitry elements, different circuitry elements, or combinations thereof); and memory 330 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processors 310 or transceiver circuitry 320).

[0084] Memory 330 (and other memory components discussed herein, such as memory, data storage devices, etc.) may include one or more machine-readable media, including instructions that, when executed by a machine or component herein, cause a machine or other device to perform actions of a method or apparatus or system for communication using various communication technologies according to the aspects, embodiments, and examples described herein. It should be understood that the aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium (e.g., the memory or other storage device described herein). Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media or computer-readable storage devices may be any available medium accessible by a general-purpose or special-purpose computer. Such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or other tangible and / or non-transitory media that can be used to carry or store desired information or executable instructions. Furthermore, any connection may also be referred to as a computer-readable medium.

[0085] On one hand, the UE / gNB device 300 can be configured to protect against inequality between different transport blocks (TBs) in physical layer encapsulation (e.g., EPC packets, transport opportunities, MCOT, single transport bursts, TTI or other encapsulation protocols or related encapsulation parameters used to encapsulate data from higher layers into frames for over-the-air transmission) by processing / generating / encoding / decoding physical layer transports comprising multiple different TBs. Physical layer transports can be received, transmitted, or provided by the communication / transmitter circuitry 320 to similarly process / generate physical layer transports with four or fewer spatial layers via physical channels in the NR network.

[0086] Processor 310 may be a component of an application circuit or a processor of a baseband circuit that can be used to execute one or more instances of a protocol stack. For example, processor 310 of a baseband circuit may be configured individually or in combination to execute various aspects or implementations of autonomous TCI state updates or TCI indications based on beam reports. Autonomous TCI state updates or TCI indications based on beam reports may refer to UE 101, for example, reporting a beam report with a TCI state update or beam change, without first being signaled by a TCI indication or TCI identifier that signals / triggers / indicates a switch of TCI state for the TCI state update. Instead, UE 101 autonomously configures the TCI update and provides a beam report to gNB 111 to indicate the TCI state update or beam change. To minimize or prevent beam mismatch, if UE 101 updates the TCI state or beam and gNB 111 remains in a different / previous state, UE 101 may receive an ACK or NACK from gNB 111 before subsequently activating the TCI state update or beam change.

[0087] On one hand, processor 310 can generate or process ACK or NACK for TCI status updates in the DCI based on at least one of the following: a specific radio network temporary identifier (e.g., ACK-RNTI), a conventional DCI that schedules PDSCH or PUSCH, a dedicated SS / CORESET, or a MAC CE. ACK or NACK can be determined implicitly or explicitly in response to a beam report that signals a TCI update.

[0088] refer to Figure 4 This document illustrates an exemplary autonomous TCI state update with a confirmation process 400 according to various aspects thereof. A UE 402 (e.g., 101, 300, etc.) can measure one or more TCI states corresponding to one or more beams and, in response to one or more conditions for initiating a beam change or TCI state update, autonomously generates a beam report 416 without a TCI indication / identification / trigger from a base station (BS) or gNB 404 (e.g., gNB 111, 300, etc.). The UE 402 provides the beam report 416 with the TCI state update, along with a TCI index or corresponding beam quality. The beam report 416 may include one or more TCI states and corresponding TCI indices and beam qualities (e.g., RSRP, SINR, etc.).

[0089] UE 402 can provide TCI status updates to the beam report via communication 406, which can be PUSCH, PUCCH, uplink control information (UCI) multiplexed with PUSCH, MAC CE, or other communication with base station 404. In response to BS 404 receiving and decoding the beam report, BS or gNB 404 transmits the ACK in DCI 418 to UE 101 via downlink physical channel (e.g., PDCCH) 408 or other communication. BS 404 can provide the ACK in DCI 418 in a group-based manner as a set of ACK blocks allocated to different UEs in DCI format. UE 402 can then identify which ACK or NACK applies to beam report 416. In response to identifying the ACK associated with the beam report, UE 402 can then activate the TCI state for transmission on the corresponding beam.

[0090] On one hand, BS 404 can provide DCI based on a New Radio RNTI (e.g., ACK-RNTI), where the value of the RNTI can be predefined or configured by RRC signaling. In response to receiving DCI, the UE can subsequently identify ACK / NACK using the predefined or RRC-signaled ACK-RNTI.

[0091] On the other hand, after a delay of X symbols / slots following the transmission of beam report 416 by UE 402, UE 402 can initiate DCI monitoring for ACK or NACK. Beam report 416 can be used for TCI updates, with gNB 404 and UE 402 activating / updating to the same TCI state or beam. The action delay X can be predefined, reported by the UE, or configured by gNB 404 for autonomous TCI updates.

[0092] On the other hand, in response to gNB 404 receiving a beam report, DCI cell format 418 can be unicast to UE 402, which provides a report with a specific ACK. If UE 402 does not receive or recognize the ACK, UE 402 can retransmit the beam report.

[0093] Alternatively or otherwise, gNB 404 may provide DCI format 418 in a group-based manner, such that multiple UEs including UE 402 share DCI format 418 comprising multiple ACK / NACK blocks. The DCI format 418 message may include an ACK index in the DCI for each UE, which may be configured by gNB, RRC, or higher-layer signaling. In one example, DCI format 418 may be multiple ACK / NACK blocks. For example, the DCI or DCI format 418 may have different fields or resource blocks or indicators that have an ACK index associated with each UE (e.g., ACK block 1, ACK block 2…ACK block N, where N is a positive integer and is any number of UEs active on the serving cell of gNB 404 and configured for autonomous TCI state updates).

[0094] On the other hand, DCI 418 can be transmitted in a serving cell that has a beam report or in another serving cell based on a serving cell index. The serving cell index can be configured by higher-layer signaling or RRC signaling. Therefore, TCI status updates or beam-based TCI indications can be configured for cross-cell ACK / NACK transmissions. For example, DCI 418 can be transmitted to UE 402 from another serving cell (e.g., another PCell, PSCell, or other network cell) to acknowledge a beam report. Based on the serving cell index provided to UE 402, UE 402 can determine which serving cell to monitor and decode the associated ACK / NACK from the other serving cell, subsequently activating a TCI status update indicated by the beam report from the other serving cell.

[0095] refer to Figure 5 This document illustrates an exemplary processing flow 500 for autonomous TCI state updates with ACK / NACK signaling or TCI indication based on beam reports, according to various aspects thereof. Processing flow 500 may begin at 502, where UE 101 transmits a beam report to indicate an autonomous TCI state update. UE 101 may transmit the beam report based on an uplink hybrid automatic repeat request (UL HARQ) process allocated for the autonomous TCI update. The UL HARQ process index may be predefined or configured by higher-layer signaling. UE 101 may have the UL HARQ process identified by the UL HARQ process index, which operates as an identifier or ID of the resource to be transmitted. Therefore, gNB 111 can know the received HARQ process and associate it with an autonomous TCI update for receiving beam reports from UE 101.

[0096] Processing flow 500 also includes determining at decision 504 whether to receive and recognize an ACK in response to the transmission of a beam report. If no indication is received or decoded, a NACK can be recognized. Alternatively, a NACK can be explicitly indicated by the DCI. For example, a new field or bit field (a 1-bit field, or other number of bits) can be introduced such that the value corresponds to either ACK or NACK. If a NACK is determined and an ACK is not explicitly or implicitly recognized through signaling behavior of gNB 111, UE 101 can retransmit the beam report at 512.

[0097] For example, the DCI providing ACK or NACK can be a conventional DCI that schedules PDSCH or PUSCH. The DCI can indicate whether the latest beam report for autonomous TCI update was correctly detected X symbols / slots transmitted before the DCI. X can be predefined or configured by RRC signaling, or reported by UE 101 to gNB 111 via UE capability, for example, where X can be a positive integer.

[0098] As part of the ACK decision process 504, UE 101 can determine at 506 whether the received DCI has scheduled a new transmission. For example, a new data indicator field or other indicator can be switched for the corresponding HARQ process (e.g., UL HARQ process). In this case, UE 101 can identify the presence of an ACK indication at 508 based on the scheduling of the new transmission. In response to implicitly identifying or decoding the ACK via explicit indication or via a request for a new transmission from the gNB, UE 101 can operate by activating the TCI state of the beam report at 510. Alternatively, if a retransmission is scheduled, UE 101 can implicitly determine that a NACK has been indicated and operate to retransmit the beam report, as at 512.

[0099] refer to Figure 6 This document illustrates another exemplary processing flow 600 for autonomous TCI status updates with ACK / NACK signaling or TCI indications based on beam reports, according to various aspects thereof. Processing flow 600 may begin at 602, transmitting beam reports for autonomous TCI updates via a dedicated search space (SS) or a dedicated control resource set (CORESET).

[0100] On one hand, gNB 111 acknowledgments can be transmitted via PDCCH in a dedicated SS or dedicated CORESET. A dedicated SS / CORESET can be configured by gNB 111 or higher-layer signaling (e.g., by RRC signaling), or it can be predefined. A dedicated SS / CORESET can be configured based on a bandwidth portion (BWP), component carrier (CC), or frequency band. For example, an SS / CORESET for a specific BWP, CC, or bandwidth can be associated with an ACK / NACK for autonomous TCI status updates or a beam-based TCI indication for UE 101.

[0101] Alternatively or in addition, DCI transmitted in a dedicated SS / CORESET can be based on a conventional DCI format or associated with a specific RNTI (e.g., Cell RNTI (C-RNTI) / Modulation and Coding Scheme (MCS)-C-RNTI). Specifically, as a dedicated SS / CORESET, the specific SS / CORESET of the DCI is not used for other PDCCH transmissions except in response to, acknowledgment of ACK or NACK for autonomous TCI status updates or beam-based TCI indications to prevent beam mismatch. Therefore, a DCI on a specific BWP, CC, or frequency band with a specific SS or CORESET can be designated as a dedicated SS / CORESET for beam reporting acknowledgment or non-acknowledgment.

[0102] At position 604, UE 101 monitors for ACK and determines whether ACK or NACK is present. Depending on the circumstances, after UE 101 sends a beam report for autonomous TCI update, UE 101 may begin monitoring DCI after X symbols / slots. Therefore, the action delay X can be configured to determine part of the ACK / NACK for beam report during autonomous TCI state update. X can be a positive-zero integer, and this value can be predefined, configured by gNB or RRC signaling, or reported by UE capabilities, and is therefore a known parameter.

[0103] Alternatively, the ACK / NACK timer for autonomous TCI state updates can be specifically configured to monitor SS / CORESET monitoring provided by gNB 111, as described above. The timer can be started when UE 101 begins monitoring the DCI in the SS / CORESET, for example, X symbols / slots after sending a beam report. The timer can be reset in response to correctly decoding the DCI in the SS / CORESET at 608. This means the UE detects an ACK, and UE 101 accordingly activates the TCI state for the beam report at 610. However, if the timer times out, as at 606, UE 101 can determine that the beam report was not correctly received or decoded by gNB 111. This means UE 101 determines a NACK and stops monitoring the SS / CORESET. UE 101 can then retransmit the beam report for TCI state updates or remain in the current state, as at 612.

[0104] On the one hand, the duration of the timer can be configured by higher-level signaling (e.g., RRC) or predefined.

[0105] Alternatively or in addition, the PDCCH in a dedicated SS / CORESET can be transmitted over the old beam, or it can be based on the new beam selected from the beam report or reported by the UE. This can also be an indication of whether ACK / NACK is implied, but it is not mandatory. If transmitted over the old beam, NACK can be determined, but ACK / NACK can be determined by combining or utilizing other aspects or factors discussed herein. Similarly, if ACK is transmitted over the new beam, ACK can be implicitly determined, or it can be weighed against other aspects to support ACK.

[0106] refer to Figure 7 This document illustrates an exemplary ACK / NACK signaling 700 for autonomous TCI status updates or TCI indication based on beam reports, according to various aspects thereof. In one aspect, the ACK / NACK can be transmitted from the gNB 111 via a Media Access Control (MAC) control element (MACCE). The MAC CE can indicate whether the latest beam report for autonomous TCI updates was correctly detected to have been transmitted X symbols / slots prior to the DCI. For example, X can be predefined or configured by RRC signaling, or reported by UE capabilities, and is a positive integer.

[0107] In addition or alternatively, the MAC CE can indicate whether gNB 111 has received the decoding status of beam reports for each serving cell. For example, the MAC CE format can include the serving cell index and associated ACK / NACK status for beam-based TCI indication or autonomous TCI status updates. The MAC CE can be represented, for example, as follows: Cj indicates serving cell j; Aj indicates the ACK / NACK status of the beam report in serving cell j. Thus, for example, C7 can be associated with serving cell C with index 7 to ACK / NACK A with index 7. For example, each field can be a date field or a bit field with one or more data or one or more indications such as bit indications. Although octagonal or 8-block blocks are shown in signaling such as bitmaps or datasets corresponding to ACK / NACKs of multiple serving cells, any number of additional blocks can be configured based on the multiple serving cells associated with beam-based TCI indication / autonomous TCI status updates. For example, this can depend on the multiple serving cells active for UE 101.

[0108] refer to Figure 8 This section illustrates another exemplary ACK / NACK signaling 800 for autonomous TCI state updates or beam-based TCI indications according to various aspects of this document. The acknowledgment signaling can be determined based on a timer, using the ACK / NACK reporting mechanism configured at UE 101. UE 101 can trigger an autonomous TCI state update by providing a beam report at symbol / slot 802. At 804, the timer starts X symbols / slots after the last symbol of the beam report transmission. X can be predefined or configured by RRC signaling, or reported by UE capability. Additionally, the duration of the timer can also be configured by gNB 111, higher-layer signaling, RRC signaling, or predefined. Similar to various aspects of this document, the timer can start after beam reporting at 804. The timer can be reset if UE 101 receives a PDCCH to trigger beam reporting. For example, if UE 101 receives a signaling notification to trigger an aperiodic beam report or retransmission before the timer expires at 806. If the timer times out at timeout 806, UE 101 may assume or implicitly recognize that the beam report was correctly decoded by gNB 111 and continue to activate the TCI state with the beam indicated in the provided beam report.

[0109] refer to Figure 9 This illustrates another exemplary ACK / NACK signaling 900 for autonomous TCI status updates or beam-based TCI indications, according to various aspects of this document. Similar to... Figure 8 ,exist Figure 9At position 902, UE 101 provides a beam report. After X symbols / slots, UE 101 initiates a timer-based ACK / NACK mechanism. However, upon timeout at position 906, UE 101 assumes or implicitly determines that the beam report has not been correctly decoded by gNB 111 and either stops autonomous TCI updates or retransmits the beam report. The timer can be reset if UE 101 receives a trigger for the beam report according to any one or more aspects described herein, or if an ACK is recognized / detected. For example, the gNB can provide PDCCH for aperiodic beam reports or other signals, physical channels, or beam report types besides aperiodic.

[0110] On the other hand, UE 101 can transmit beam reports via UCI / PUCCH or MAC CE. Therefore, the current ACK / NACK associated with MAC CE signaling can be used to provide ACK / NACK corresponding to, for example, a beam report-based TCI indication or an autonomous TCI state update initiated by UE 101. Beam reports can be transmitted in different ways, such as periodic / semi-persistent / aperiodic methods.

[0111] In the CSI report configuration (e.g., CSI-reportConfig) or in information elements associated with the CSI report configuration and associated resource parameters, the gNB 111 can provide an ACK / NACK signaling indicator, for example, to indicate whether the beam report is transmitted based on MAC CE or via other signaling aspects described herein (such as UCI or PUCCH) based on a legacy method. For example, if this indicator is disabled for MAC CE-based reporting, the UE 101 used for beam-based reporting in an autonomous TCI state update can still use UCI or PUCCH for that beam report. This means that the beam-based TCI indicator can be activated for legacy signaling or activated via MAC CE.

[0112] If UE 101 receives a DCI (e.g., New Data Indicator (NDI)) for scheduling a new transmission in the same HARQ process as the beam report, UE 101 may assume that the beam report was successfully decoded. Otherwise, UE 101 may assume that the beam report was not successfully decoded to NACK.

[0113] Alternatively, if the beam report contains more than one beam or associated TCI status, acknowledgments can be transmitted based on the beam with the highest reporting beam quality (e.g., L1-RSRP or L1-SINR). Acknowledgments can be transmitted based on the old TCI / beam or based on the beam report transmitted by the new beam.

[0114] refer to Figure 10 This illustrates an example of autonomous TCI state updates or TCI indications based on beam reports, considering various aspects associated with action delay and UE behavior. For example, UE 101 can provide beam reports with more than one TCI state and other indications. At 1002, the beam report may include a TCI index and beam quality associated with different TCI states. For example, the beam report may include TCI 1 associated with L1-RSRP (e.g., -80dBm). Another TCI state, TCI 2, may include differential (e.g., -4dB) associated with the beam quality of another TCI state. After UE 101 receives an ACK for the beam report used for autonomous TCI updates at 1004, after an action delay of N symbols / slots, UE 101 may update the active TCI state associated with the beam report at 1006. This action delay N may be predefined or configured by gNB 111, RRC signaling, or reported by UE capabilities.

[0115] On one hand, beam reporting can be measured based on multiple configured TCI states. The gNB 111 can configure these TCI states for beam measurement and then report these TCI states in the beam report. When an autonomous TCI state update is initiated by providing a beam report, the UE 101 can configure the beam report with the associated TCI index and the associated beam quality. In response to two or more different reference signals (RS) being in or associated with a TCI state, beam reporting can be based on the RS providing QCL-TypeD (spatial Rx parameter) indication. The gNB 111 can then configure the TCI state QCLed with one of the multiple RSs to switch to the appropriate beam or TCI state as UE 101.

[0116] On the one hand, when there are two RSs in TCI state, UE 101 can provide two QCL type indications, for example, one for QCL type A and the other for QCL type D. Type D is used for spatial parameter indication of beam indication.

[0117] UE 101 can report multiple (M)TCI state indices in the beam report, and M TCI states can be considered as active TCI states. Each of these M TCI states may include a TCI state with index m that has been applied as a new beam. Index m may be predefined as the first TCI state in the priority of TCI states with the highest beam quality, configured by gNB 111, indicated by higher-layer signaling (e.g., via RRC or MAC CE), or indicated by DCI format (e.g., DCI format 1_1 / 1_2).

[0118] exist Figure 10 In the example, UE 101 can report multiple beams (e.g., TCI 1 and TCI 2) and their corresponding Layer 1 (L1) RSRPs in the beam report. Then, at 1006, UE 101 receives an ACK for that beam port. TCI state 1 and TCI state 2 then become the active TCI states. For example, TCI state 1 can be applied as the new TCI state for the corresponding channel because TCI 1 provides better L1-RSRP. gNB 101 can retain the ability to control changes to different states based on TCI updates or other TCI update signaling. However, in the absence of any additional TCI update signaling, gNB 111 can apply TCI state 1 based on additional information provided in the beam report with a TCI state indicating a TCI update for beam-based reporting.

[0119] refer to Figure 11 This illustrates another example of autonomous TCI state updates or beam-based TCI indications based on various aspects associated with action delay and UE behavior. Similar to... Figure 10 UE 101 can provide beam reports with more than one TCI state and other indications. At 1102, the beam report may include a TCI index and beam quality associated with different TCI states. For example, the beam report may include TCI 1 associated with L1-RSRP (e.g., -80dBm). Another TCI state, TCI 2, may include differential (e.g., -4dB) associated with the beam quality of another TCI state. After a delay of N symbols / slots following UE 101 receiving an ACK for the beam report used for autonomous TCI update at 1104, UE 101 may update the active TCI state associated with the beam report at 1106. This delay N may be predefined or configured by gNB 111, RRC signaling, or reported by UE capability.

[0120] On one hand, beam reports used for autonomous TCI updates can be measured based on at least one of the following: SSB or CSI-RS. UE 101 may consider the SSB or CSI-RS resources used to configure beam reports. UE 101 may further report the SSB Resource Index (SSBRI) or CSI-RS Resource Index (CRI) and the corresponding beam quality (e.g., L1-RSRP / L1-SINR) in the beam reports used for autonomous TCI status updates.

[0121] The association between TCI and SSB / CSI-RS can be configured to use beam reports to determine which TCI state is activated / used at UE 101. In one aspect, the association between TCI and SSB / CSI-RS can be configured by gNB 111 or based on higher-layer signaling. The association between TCI and SSB / CSI-RS can also be determined through quasi-cooperative positioning (QCL) configuration, as an implicit association method. TCI and SSB / CSI-RS can be considered associated if the source reference signal in TCI and SSB / CSI-RS share the same QCL source, or if the source reference signal (RS) in TCI is the same as that in SSB / CSI-RS.

[0122] In this example, UE 101 has already reported the quality of SSB 1 or SSB 2 at 1102, and after receiving the ACK at 1104, UE 101 applies TCI state 1 and TCI state 2 as the active TCI states, because TCI 1 is associated with SSB 1 and TCI 2 is associated with SSB 2. For example, TCI can be applied to the corresponding channel based on the higher quality. Similarly, CSI-RS can be reported and considered as part of beamforming and TCI state updates.

[0123] Alternatively, gNB 111 or UE 101 can be further configured to use beam reports for downlink TCI updates, uplink TCI updates, or UL and DL TCI updates. For example, UE 101 can update the DL / UL TCI status of the DL / UL channel accordingly after receiving an acknowledgment of the beam report at 1104. In other words, UE 101 can update the DL / UL TCI status of the corresponding DL / UL channel after receiving / identifying an acknowledgment of the provided beam report. This update to the DL / UL TCI status depends on whether the measurement reference signal is based on the DL TCI status, the UL TCI status, or a combination of the UL and DL TCI status.

[0124] Alternatively, a separate field can be introduced in CSI-reportConfig to indicate whether the UE 101 should apply a beam report for the UL or DL ​​TCI status, and to indicate the type of target TCI update for the beam report used for autonomous TCI updates.

[0125] Alternatively, in beam reports used for autonomous TCI updates, UE 101 can indicate whether the TCI status update is for UL, DL, or both. The difference between these two aspects is that, firstly, it is controlled by the gNB for UL / DL or both, and secondly, it is controlled by the UE 101, thus the UE can signal whether the report is for UL / DL or both. This can be indicated, for example, based on the beam being reported or based on the report instance. In one example, for each beam in the beam report, a 2-bit indicator can be provided to indicate whether the TCI status update applies to UL or DL, or both. In another example, gNB 111 can indicate whether this is for a separate TCI indication or a combined TCI indication. If the beam report is for a separate TCI indication, a 1-bit indicator can be introduced for each beam to report whether the beam is for UL or DL. If this is for a combined TCI indication, no additional indicator is needed, and the conventional beam format discussed herein can be used.

[0126] While the methods described herein are shown and described as a series of actions or events, it should be understood that the order of such actions or events shown should not be construed as limiting. For example, some actions may occur in a different order and / or simultaneously with other actions or events besides those shown and / or described herein. Furthermore, not all of the shown actions may be required to implement one or more aspects or embodiments of this specification. Additionally, one or more of the actions depicted herein may be performed in one or more separate actions and / or phases. For ease of description, reference may be made to the foregoing figures. However, the methods are not limited to any specific embodiments, aspects, or examples provided within this disclosure and can be applied to any system / device / component in the systems disclosed herein.

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

[0128] This disclosure will now be described with reference to the accompanying drawings, wherein similar reference numerals throughout are used to denote similar elements, and the structures and devices shown therein are not necessarily drawn to scale. As used herein, the terms “component,” “system,” “interface,” etc., are intended to refer to computer-related entities, hardware, software (e.g., in execution), and / or firmware. For example, a component can be a processor (e.g., a microprocessor, controller, or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer, and / or user equipment with processing devices (e.g., a mobile phone, etc.). By way of example, an application running on a server and a server can also be components. One or more components may reside in a process, and components may be located on a single computer and / or distributed across two or more computers. This document may describe a set of elements or other sets of components, wherein the term “set” can be interpreted as “one or more.”

[0129] Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored, such as by utilizing modules, for example. Components can communicate via local and / or remote processes, for example, based on signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or throughout a network, such as the Internet, a local area network, a wide area network, or similar networks with other systems via signals).

[0130] For example, a component can be a device with a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry can be operated by a software application or firmware application executed by one or more processors. The one or more processors can be internal or external to the device and can execute at least a portion of the software or firmware application. As another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component may include one or more processors to execute software and / or firmware that at least partially endows the electronic component with that function.

[0131] The use of the term “exemplary” is intended to present the concept in a specific manner. 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. That is, “X adopts A or B” is satisfied if X adopts A; X adopts B; or X adopts both A and B. 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 and Claims, such terms are intended to be included in a manner similar to the term “comprising.” Furthermore, in the context 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.

[0132] As used herein, the term "circuit" may refer to, be part of, or may include: an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), or associated memory (shared, dedicated, or grouped) operatively coupled to the circuit, which executes one or more software or firmware programs, combinational logic circuitry, or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0133] As used herein, the term "processor" can refer to virtually any computing processing unit or device, including but not limited to single-core processors; single-processors with software multithreading capabilities; multi-core processors; multi-core processors with software multithreading capabilities; multi-core processors with hardware multithreading technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, application-specific integrated circuit, digital signal processor, field-programmable gate array, programmable logic controller, complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and / or processes described herein. Processors can utilize nanoscale architectures, such as, but not limited to, molecular and quantum dot-based transistors, switches, and gates, to optimize space utilization or enhance the performance of mobile devices. Processors can also be implemented as a combination of computing processing units.

[0134] Implementations may include subjects such as methods, means for performing actions or blocks of the methods, at least one machine-readable medium including 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 implementations and embodiments described herein.

[0135] The first embodiment is a user equipment (UE), including: a memory; and processing circuitry configured to: transmit a beam report to indicate an autonomous TCI state update from a first Transmission Configuration Indicator (TCI) state to a second TCI state; determine an acknowledgment (ACK) or non-acknowledgment (NACK) indicating whether the beam report has been decoded; and activate the second TCI state of the autonomous TCI state update based on the ACK or retransmit the beam report based on the NACK.

[0136] The second embodiment may include the first embodiment, wherein the processing circuitry is further configured to receive downlink control information (DCI) via the physical downlink control channel (PDCCH) based on an ACK radio network temporary identifier (ACK-RNTI) indicating the decoding state of the beam report corresponding to the ACK or NACK.

[0137] The third embodiment may include the first embodiment or the second embodiment, wherein the processing circuitry is further configured to: monitor the DCI based on X symbols / time slots after transmitting the beam report to identify the ACK or the NACK, where X is a positive integer, which is predefined, configured by radio resource control (RRC) signaling, or reported by UE capability.

[0138] The fourth embodiment may include any one or more embodiments of the first to third embodiments, wherein the processing circuitry is further configured to: receive the DCI from a serving cell that has the beam report configured; or receive the DCI from another serving cell other than the serving cell that has the beam report configured and the associated serving cell index, so as to be able to monitor the DCI from the other serving cell.

[0139] The fifth embodiment may include any one or more embodiments of the first to fourth embodiments, wherein the DCI is received via unicast transmission or group-based transmission, and in response to receiving the DCI via the group-based transmission, the processing circuitry is further configured to determine the ACK or NACK associated with the beam report based on the ACK index from a resource block shared among different UEs.

[0140] The sixth embodiment may include any one or more embodiments of the first to fifth embodiments, wherein the DCI is configured to schedule the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) and indicate whether the beam report is correctly decoded, wherein the processing circuitry is further configured to determine whether the beam report is correctly decoded by the base station based on the bit field of the DCI or based on the scheduling of new transmissions / retransmissions of the DCI.

[0141] The seventh embodiment may include any one or more embodiments of the first to sixth embodiments, wherein the processing circuitry is further configured to determine the ACK or the NACK via a dedicated search space (SS) or a dedicated control resource set (CORESET) of the PDCCH, wherein the dedicated SS or the dedicated CORESET is configured according to a bandwidth portion (BWP), according to a component carrier (CC), or according to a frequency band.

[0142] The eighth embodiment may include any one or more embodiments of the first to seventh embodiments, wherein the processing circuitry is further configured to: monitor the dedicated SS or the dedicated CORESET based on a plurality of symbols / time slots after transmitting the beam report to identify the ACK or the NACK, and based on the duration of a timer initiated while monitoring the dedicated SS or the dedicated CORESET; and determine the NACK in response to a timer duration timeout before detecting the ACK by decoding the DCI.

[0143] The ninth embodiment may include any one or more embodiments of the first to eighth embodiments, wherein the processing circuitry is further configured to: receive a Media Access Control (MAC) control element (MAC CE) indicating the ACK or NACK corresponding to the decoding status of the beam reports of multiple serving cells based on X symbols / time slots after the transmission of the beam report, wherein X is a positive integer, which is predefined, configured by RRC signaling, or reported by UE capability.

[0144] The tenth embodiment may include any one or more embodiments of the first to ninth embodiments, wherein the processing circuitry is further configured to: monitor the duration of a timer that initiates a timer for X symbols / slots after transmitting the beam report to identify the ACK or the NACK, where X is a positive integer, the integer being predefined, configured by RRC signaling, or reported by UE capability; reset the timer in response to receiving a PDCCH to trigger the beam report or aperiodic beam report; and determine, in response to a timeout of the timer duration, whether the beam report was not acknowledged as the NACK or whether the beam report was acknowledged as the ACK.

[0145] The eleventh embodiment may include any one or more embodiments of the first to tenth embodiments, wherein the processing circuitry is further configured to: transmit the beam report via MAC CE to indicate the autonomous TCI state update by at least one of the following: periodic transmission, semi-persistent transmission, or aperiodic transmission; and determine that the beam report is acknowledged as the ACK in response to receiving a DCI that schedules a new transmission for the same HARQ process corresponding to the beam report.

[0146] The twelfth embodiment may include any one or more embodiments of the first to eleventh embodiments, wherein the processing circuitry is further configured to: activate the second TCI state of the autonomous TCI state update based on the ACK based on the action delay of N symbols / slots for the autonomous TCI update, where N is a positive integer, which is predefined, configured by RRC signaling, or reported by UE capability.

[0147] The thirteenth embodiment may include any one or more embodiments of the first to twelfth embodiments, wherein the processing circuitry is further configured to: in response to more than one reference signal (RS) corresponding to the TCI state, measure and report the beam quality of the TCI state based on the RS providing quasi-cooperative positioning (QCL)-TypeD indication.

[0148] The fourteenth embodiment may include any one or more embodiments of the first to thirteenth embodiments, wherein the processing circuitry is further configured to configure the beam report based on at least one of the following: a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS), wherein the beam report includes at least one of the following: an SSB resource index (SSBRI) or a CSI-RS resource index (CRI), and one or more beam qualities corresponding to at least one of the following: the SSBRI or the CRI associated with at least one of the SSB or the CSI-RS.

[0149] The fifteenth embodiment may include any one or more embodiments of the first to fourteenth embodiments, wherein the processing circuitry is further configured to: provide, via the beam report, an indication as to whether the beam report is associated with an uplink (UL) TCI update, a downlink (DL) TCI update, or both the UL TCI update and the DL TCI update, based on the reported beam or a report instance of the beam report.

[0150] The sixteenth embodiment is a base station, including: a memory and processing circuitry configured to: receive beam reports based on autonomous transmission configuration indicator (TCI) status updates; and transmit an indication of whether the beam report has been successfully decoded, either an acknowledgment (ACK) or a non-acknowledgment (NACK).

[0151] The seventeenth embodiment may include the sixteenth embodiment, wherein the processing circuitry is further configured to provide downlink control information (DCI) based on a radio network temporary identifier (RNTI) specific to the decoding status indication of the ACK or NACK based on the beam report, wherein the RNTI is predefined or configured via radio resource control (RRC) signaling.

[0152] The eighteenth embodiment may include any one or more embodiments of the sixteenth to seventeenth embodiments, wherein the processing circuitry is further configured to: receive the beam report via a serving cell associated with the beam report or another serving cell via a plurality of UEs through unicast transmission or group-based transmission, and configure a serving cell index corresponding to a UE among the plurality of UEs based on higher-layer signaling or RRC signaling, and provide a DCI indicating the ACK or the NACK.

[0153] The nineteenth embodiment may include any one or more embodiments of the sixteenth to eighteenth embodiments, wherein the processing circuitry is further configured to: monitor the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) based on X symbols / time slots after transmitting the beam report before providing the DCI to provide the indication of the ACK or the NACK, wherein the DCI is configured to schedule the Physical Downlink Shared Channel (PDSCH) or the PUSCH, and wherein X is a positive integer, which is predefined, configured by Radio Resource Control (RRC) signaling, or reported by UE capabilities.

[0154] The twentieth embodiment may include any one or more embodiments of the sixteenth to nineteenth embodiments, wherein the processing circuitry is further configured to: allocate an uplink hybrid automatic repeat request (UL HARQ) process for the autonomous TCI state update based on a predefined or higher-layer signaling-configured HARQ process index; and provide a DCI that schedules the transmission of the UL HARQ process or the retransmission of the UL HARQ process based on the beam report, wherein scheduling the transmission based on the updated TCI of the beam report indicates that the beam report has been successfully decoded into the ACK, and the retransmission indicates that the beam report has not been successfully decoded into the NACK.

[0155] The twenty-first embodiment may include any one or more embodiments of the sixteenth to twentieth embodiments, wherein the processing circuitry is further configured to transmit the indication of the ACK or the NACK via a pre-existing beam or a beam selected from the beam report via a PDCCH in a dedicated search space (SS) or a dedicated control resource set (CORESET), wherein the dedicated SS or the dedicated CORESET is configured according to a bandwidth portion (BWP), according to a component carrier (CC), or according to a frequency band, wherein the DCI in the dedicated SS or the dedicated CORESET is based on a DCI format or associated with a cell (C)-RNTI or modulation and coding scheme (MCS)-C-RNTI.

[0156] The twenty-second embodiment may include any one or more embodiments of the sixteenth to twenty-first embodiments, wherein the processing circuitry is further configured to transmit the indication of the ACK or the NACK via a media access control (MAC) control element (MAC CE), wherein the MAC CE is configured with a serving cell index corresponding to the status of the ACK or the NACK reported for the beam associated with the serving cell index.

[0157] The twenty-third embodiment may include any one or more embodiments of the sixteenth to twenty-second embodiments, wherein the processing circuitry is further configured to receive the beam report via the MAC CE or the other type of uplink transmission based on a Channel State Information Report (CSI) report configuration (CSI-reportConfig) indicating whether the beam report is transmitted via a MAC CE or another type of uplink transmission.

[0158] The twenty-fourth embodiment may include any one or more embodiments of the sixteenth to twenty-third embodiments, wherein the processing circuitry is further configured to: in response to the beam report being associated with a plurality of beams, provide a beam to the ACK based on the beam quality of the plurality of beams associated with the beam report, wherein the beam report includes a TCI index and the beam quality associated with the beam among the plurality of beams.

[0159] The twenty-fifth embodiment may include any one or more embodiments of the sixteenth to twenty-fourth embodiments, wherein the processing circuitry is further configured to: receive the beam report including different reference signals (RS) associated with the TCI state in the autonomous TCI state update; determine the updated beam based on the TCI state index associated with the beam report and at least one of the following: the highest beam quality among a plurality of beams, the priority order of the plurality of beams, or an indication of the updated beam from higher-layer signaling; and provide the ACK for the updated beam to be activated.

[0160] The twenty-sixth embodiment may include any one or more embodiments of the sixteenth to twenty-fifth embodiments, wherein the processing circuitry is further configured to: provide an indication of whether the beam report will be configured for downlink TCI update, uplink TCI update, or both downlink TCI update and uplink TCI update, such that the user equipment (UE) can update the TCI state based on the indication.

[0161] The twenty-seventh embodiment may be a baseband processor, including: a memory and processing circuitry, the processing circuitry being configured to: transmit a beam report to indicate an autonomous transmission configuration indicator (TCI) status update; determine an acknowledgment (ACK) or non-acknowledgment (NACK) indicating whether the beam report has been decoded; and activate the TCI status of the autonomous TCI status update or retransmit the beam report based on the ACK.

[0162] The twenty-eighth embodiment may include the twenty-seventh embodiment, wherein the processing circuitry is further configured to process downlink control information (DCI) via the physical downlink control channel (PDCCH) based on a radio network temporary identifier (RNTI) specific to the decoding status indicated by the beam report for the ACK or NACK, wherein the RNTI is predefined or configured via radio resource control (RRC) signaling.

[0163] The twenty-ninth embodiment may include any one of the twenty-seventh to twenty-eighth embodiments, wherein the processing circuitry is further configured to: receive DCI via unicast transmission or group-based transmission; and, in response to the DCI transmitted via the group-based transmission, determine the ACK or NACK associated with the beam report based on the ACK index of the resource block corresponding to a different UE.

[0164] The thirtieth embodiment may include any one of the twenty-seventh to twenty-ninth embodiments, wherein the processing circuitry is further configured to: generate the beam report for the autonomous TCI state update based on the hybrid automatic repeat request (HARQ) process index of the uplink (UL) HARQ, wherein the HARQ process index is predefined or configured via higher-layer signaling; and receive a DCI that schedules a transmission of the UL HARQ process based on the beam report or triggers a retransmission of the UL HARQ process, wherein scheduling the transmission based on the updated TCI of the beam report indicates that the beam report has been successfully decoded into the ACK, and the retransmission indicates that the beam report has not been successfully decoded into the NACK.

[0165] The 31st embodiment may include any one of the 27th to 30th embodiments, wherein the processing circuitry is further configured to determine the ACK or the NACK via a dedicated search space (SS) or a dedicated control resource set (CORESET) of the PDCCH, wherein the dedicated SS or the dedicated CORESET is configured according to a bandwidth portion (BWP), according to a component carrier (CC), or according to a frequency band.

[0166] The thirty-second embodiment may include any one of the twenty-seventh to thirty-first embodiments, wherein the processing circuitry is further configured to: transmit the beam report via a media access control (MAC) control element (MAC CE) to indicate the autonomous TCI state update by at least one of the following: periodic transmission, semi-persistent transmission, or aperiodic transmission; and determine that the beam report is acknowledged as the ACK in response to receiving a DCI that schedules a new transmission for the same HARQ process corresponding to the beam report.

[0167] The thirty-third embodiment may include any one of the twenty-seventh to thirty-second embodiments, wherein the system processing circuitry is further configured to: in response to more than one reference signal (RS) corresponding to a TCI state, measure and report the beam quality of the TCI state based on the RS providing a quasi-cooperative positioning (QCL)-TypeD indication in the beam report.

[0168] The thirty-fourth embodiment may include an apparatus comprising means for performing one or more elements of the method or any other method or process described herein, as described in or related to any of the first to twenty-first embodiments.

[0169] The thirty-fifth embodiment may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described or associated with any one of the first to twenty-first embodiments.

[0170] The thirty-sixth embodiment may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing the method described or associated with any one of the first to twenty-first embodiments, or any other method or process described herein.

[0171] The thirty-seventh embodiment may include any of the methods, techniques, or processes, or parts or components thereof, described or related to any of the first to twenty-first embodiments.

[0172] The thirty-eighth embodiment may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or part thereof, as described or associated with any one of the first to twenty-first embodiments.

[0173] The thirty-ninth embodiment may include signals, or portions or components thereof, as described or associated with any of embodiments 1 to 29.

[0174] The fortieth embodiment may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages or portions or components thereof as described or associated with any of the first to twenty-first embodiments, or otherwise described in this disclosure.

[0175] The forty-first embodiment may include a data-encoded signal or part or component thereof as described or associated with any of the first to twenty-first embodiments, or otherwise described in this disclosure.

[0176] The forty-second embodiment may include a signal or part or component thereof encoded as a datagram, packet, frame, segment, protocol data unit (PDU) or message as described or associated with any of the first to twenty-first embodiments, or otherwise described in this disclosure.

[0177] The forty-third embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process or part thereof as described or associated with any one of the first to thirty-first embodiments.

[0178] The forty-fourth embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any one of the first to twenty-first embodiments.

[0179] The forty-fifth embodiment may include signals in a wireless network as shown and described herein.

[0180] The forty-sixth embodiment may include a method for communicating in a wireless network as shown and described herein.

[0181] The forty-seventh embodiment may include a system for providing wireless communication as shown and described herein.

[0182] The forty-eighth embodiment may include a device for providing wireless communication as shown and described herein.

[0183] Furthermore, standard programming and / or engineering techniques can be used to implement the various aspects or features described herein as methods, apparatus, or articles of art. As used herein, the term "article of art" is intended to cover a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., high-density disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., EPROMs, cards, sticks, key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data. Furthermore, a computer program product may include a computer-readable medium having one or more instructions or codes that are operable to cause a computer to perform the functions described herein.

[0184] Communication media embody computer-readable instructions, data structures, program modules, or other structured or unstructured data in data signals such as modulated data signals, such as carrier waves or other transmission mechanisms, and include any information delivery or transmission medium. The term "modulated data signal" or signal refers to a signal whose one or more characteristics are set or altered in a manner that encodes information in one or more signals. By way of example, and not limitation, communication media include wired media such as wired networks or direct wired connections, and wireless media such as acoustic, RF, infrared, and other wireless media.

[0185] An exemplary storage medium can be coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor. Furthermore, in some aspects, the processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a user terminal. Alternatively, the processor and storage medium can reside as discrete components in the user terminal. Furthermore, in some aspects, the process and / or actions of a method or algorithm can reside as one or any combination or set of code and / or instructions on a machine-readable and / or computer-readable medium, and can be incorporated into a computer program product.

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

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

Claims

1. A user equipment (UE), comprising: Radio frequency (RF) circuits; Memory; as well as Processing circuitry, the processing circuitry being configured to execute instructions stored in the memory to: A beam report is transmitted via the RF circuit. The beam report is based on the HARQ process index of the uplink UL Hybrid Automatic Repeat Request (HARQ) process for use in the autonomous transport configuration indicator (TCI) state update. The beam report indicates the autonomous TCI state update to change from a first TCI state to a second TCI state for the serving cell. The HARQ process index is predefined or configured via higher-layer signaling. Receive downlink control information (DCI) transmission, wherein the DCI transmission is scheduled for transmission of the UL HARQ process or triggers retransmission for the UL HARQ process, wherein the transmission is scheduled to indicate that the beam report is successfully decoded as an ACK, and the retransmission is triggered to indicate that the beam report is not successfully decoded as a NACK. In response to the ACK, the transmission for the ULHARQ process is transmitted based on the second TCI state updated by the autonomous TCI state; and In response to the NACK, the beam report is retransmitted.

2. The UE according to claim 1, wherein the processing circuit is further configured to: The DCI transmission is received via the Physical Downlink Control Channel (PDCCH) based on the ACK radio network temporary identifier ACK-RNTI, which indicates the decoding status of the ACK or NACK corresponding to the beam report.

3. The UE according to claim 1, wherein the processing circuit is further configured to: The DCI transmission is detected based on X symbols or time slots following the transmission of the beam report, to identify the ACK or NACK, where X is a positive integer that is predefined, configured by Radio Resource Control (RRC) signaling, or reported by UE capabilities.

4. The UE according to claim 1, wherein the processing circuit is further configured to: The DCI transmission is detected by monitoring a serving cell index configured by higher-layer signaling to discover transmissions from another serving cell, wherein the indication of ACK or NACK is based on the monitoring of the DCI transmission.

5. The UE of claim 4, wherein the DCI transmission is a group-based DCI transmission comprising a plurality of ACK blocks for a plurality of respective UEs, and wherein determining the ACK or the NACK is further based on an ACK index corresponding to an ACK block for the UE from among the plurality of ACK blocks for the plurality of respective UEs, wherein the ACK index is configured by higher-layer signaling.

6. The UE according to claim 1, wherein the processing circuit is further configured to: The ACK or NACK is determined via a dedicated search space SS or a dedicated control resource set CORESET of the PDCCH, wherein the dedicated SS or the dedicated CORESET is configured for each bandwidth portion (BWP), for each component carrier (CC), or for each frequency band.

7. The UE of claim 6, wherein the processing circuit is further configured to: Based on a number of symbols or time slots used to identify the ACK or NACK after the transmission of the beam report, and based on the duration of a timer started when monitoring the dedicated SS or the dedicated CORESET, the dedicated SS or the dedicated CORESET is monitored; and The NACK is determined in response to a timer duration timeout before the ACK is detected by decoding the DCI.

8. The UE according to claim 1, wherein the processing circuit is further configured to: The beam report is transmitted via the Medium Access Control (MAC) control element (CE) to indicate the autonomous TCI state update through at least one of the following: periodic transmission, semi-persistent transmission, or aperiodic transmission.

9. The UE according to claim 1, wherein the processing circuit is further configured to: In response to determining the ACK, the second TCI state of the autonomous TCI state update is activated based on the action delay of N symbols or time slots for the autonomous TCI update, where N is a positive integer that is predefined, configured by RRC signaling, or reported by UE capability.

10. The UE according to claim 1, wherein the processing circuit is further configured to: In response to more than one reference signal RS associated with the TCI state, the beam quality for the TCI state is measured and reported based on the RS providing quasi-cooperative positioning QCL-TypeD indication.

11. The UE according to claim 1, wherein the processing circuit is further configured to: The beam report is configured based on one or more measurements of at least one of the following: a Synchronization Signal Block (SSB) or a Channel State Information Reference Signal (CSI-RS), wherein the beam report includes at least one of the following: an SSB Resource Index (SSBRI) associated with the SSB or a CSI-RS Resource Index (CRI) associated with the CSI-RS, and one or more beam qualities corresponding to at least one of the SSBRI or the CRI.

12. The UE of claim 1, wherein the beam report includes an indication for each reported beam or for each instance of the beam report, of whether the beam report is associated with an uplink UL TCI update, a downlink DLTCI update, or both the UL TCI update and the DLTCI update.

13. A base station, comprising: Radio frequency (RF) circuits; Memory; and Processing circuitry, the processing circuitry being configured to execute instructions stored in the memory to: Receive a beam report, the beam report indicating an autonomous TCI state update from a first Transport Configuration Indicator (TCI) state to a second TCI state based on the HARQ process index of the uplink UL Hybrid Automatic Repeat Request (HARQ) process, for use in the autonomous TCI state update, wherein the HARQ process index is predefined or configured via higher-layer signaling; and Downlink control information (DCI) is transmitted via the RF circuit. The DCI schedules transmissions for the UL HARQ process or triggers retransmissions for the UL HARQ process. The scheduled transmission indicates that the beam report has been successfully decoded as an ACK, and the triggered retransmission indicates that the beam report has not been successfully decoded as a NACK.

14. The base station according to claim 13, wherein the processing circuit is further configured to: The DCI is transmitted based on a Radio Network Temporary Identifier (RNTI) that indicates the ACK or NACK based on the decoding status of the beam report, wherein the RNTI is predefined or configured via Radio Resource Control (RRC) signaling.

15. The base station according to claim 13, wherein the processing circuit is further configured to: The DCI indicating the ACK or NACK is transmitted via a serving cell or another serving cell associated with the beam report, via a group-based transmission for multiple UEs, and the serving cell index corresponding to the UE among the multiple UEs is configured based on higher-layer signaling or RRC signaling.

16. The base station according to claim 13, wherein the processing circuit is further configured to: Before transmitting the DCI to provide the indication of the ACK or the NACK, the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) is monitored based on X symbols or time slots after the transmission of the beam report, wherein the DCI is configured to schedule the Physical Downlink Shared Channel (PDSCH) or the PUSCH, and wherein X is a positive integer that is predefined, configured by Radio Resource Control (RRC) signaling, or reported by UE capabilities.

17. The base station according to claim 13, wherein the processing circuit is further configured to: The DCI is transmitted via an old beam or a beam selected from the beam report via a dedicated search space (SS) or a dedicated control resource set (CORESET) containing a PDCCH, wherein the dedicated SS or the dedicated CORESET is configured for each bandwidth portion (BWP), for each component carrier (CC), or for each frequency band, wherein the DCI in the dedicated SS or the dedicated CORESET is based on a DCI format or associated with a cell C-RNTI or a modulation and coding scheme MCS-C-RNTI.

18. The base station according to claim 13, wherein the processing circuit is further configured to: In response to the beam report being associated with multiple beams, a beam is provided to the ACK based on the beam quality of the multiple beams associated with the beam report, wherein the beam report includes a TCI index and the beam quality associated with the multiple beams.

19. The base station according to claim 13, wherein the processing circuit is further configured to: Receive the beam report, which includes different reference signals RS associated with the TCI state in the autonomous TCI state update; The updated beam is determined based on the TCI status index associated with the beam report and at least one of the following: the highest beam quality among multiple beams, the priority order of the multiple beams, or an indication of the updated beam from higher-layer signaling; and The ACK is provided for the updated beam to be activated.

20. The base station according to claim 13, wherein the processing circuit is further configured to: Provides an indication of whether the beam report will be configured for downlink TCI update, uplink TCI update, or both downlink and uplink TCI update, so that the user equipment (UE) can update the TCI status based on the indication.

21. A baseband processor, comprising: Memory; and Processing circuitry, the processing circuitry being configured to execute instructions stored in the memory to: A beam report is provided, which is based on the HARQ process index of the uplink UL Hybrid Automatic Repeat Request (HARQ) process for use in the autonomous Transport Configuration Indicator (TCI) state update, wherein the beam report indicates the autonomous TCI state update to change from a first TCI state to a second TCI state for the serving cell, and wherein the HARQ process index is predefined or configured via higher-layer signaling. Receive downlink control information (DCI) transmission, wherein the DCI transmission is scheduled for transmission of the UL HARQ process or triggers retransmission for the UL HARQ process, wherein the transmission is scheduled to indicate that the beam report is successfully decoded as an ACK, and the retransmission is triggered to indicate that the beam report is not successfully decoded as a NACK. as well as In response to the ACK, the transmission for the ULHARQ process is transmitted based on the second TCI state updated by the autonomous TCI state; and In response to the NACK, the beam report is retransmitted.

22. The baseband processor of claim 21, wherein the processing circuit is further configured to: The DCI is received via the Physical Downlink Control Channel (PDCCH) based on a Radio Network Temporary Identifier (RNTI) specific to indicating the ACK or NACK, wherein the RNTI is predefined or configured via Radio Resource Control (RRC) signaling.

23. The baseband processor of claim 21, wherein the processing circuitry is further configured to: The DCI is received via group-based transmission; and The ACK or NACK associated with the beam report is determined based on the ACK index of the resource block corresponding to the different UEs.

24. The baseband processor of claim 21, wherein the processing circuitry is further configured to: The DCI is received via a dedicated search space (SS) or a dedicated control resource set (CORESET) of the PDCCH, wherein the dedicated SS or the dedicated CORESET is configured for each bandwidth portion (BWP), for each component carrier (CC), or for each frequency band.

25. The baseband processor of claim 21, wherein the processing circuitry is further configured to: In response to more than one reference signal RS corresponding to the TCI state, the beam quality for the TCI state is measured and reported based on the RS which provides a quasi-cooperative positioning QCL-TypeD indication in the beam report.

Images