Channel State Information (CSI) Extension for Multiple Transmit / Receive Point (TRP) Operation of a Single Downlink Control Information (DCI)

Abstract

A user equipment (UE), a baseband processor, or other network device (e.g., a base station, an E-Node B, etc.) may be operable to process or generate a CSI report based on a CSI report configuration for single transmission / reception point (sTRP) operation and multiple TRP (mTRP) operation. The CSI report is based on a number of weighted CSI report priority variables, which may include measurements associated with the sTRP operation and measurements associated with the mTRP operation, and the measurements associated with the sTRP operation may be configured with a different priority than the measurements associated with the mTRP operation.

Description

[Technical Field]

[0001] The present disclosure relates to wireless technologies including channel state information (CSI) extensions for single downlink control information (DCI) multiple transmit / receive point (TRP) operation. [Background technology]

[0002] Mobile communications in next-generation wireless communication systems, 5G, or new radio (NR) networks, provide ubiquitous connectivity and access to information and data sharing capabilities worldwide. 5G networks and network slicing are a unified, service-based framework that meets diverse and sometimes conflicting performance criteria and aims to deliver services to highly heterogeneous application domains, from Enhanced Mobile Broadband (eMBB) to massive Machine-Type Communications (mMTC), Ultra-Reliable Low-Latency Communications (URLLC), and other communications. Generally, NR is based on the third generation partnership project (3GPP) long-term evolution (LTE) advanced technology and evolves with additional enhanced radio access technologies (RATs) to enable seamless and faster wireless connectivity solutions. 5G wireless networks are expected to support massive connectivity, high capacity, ultra-reliability, and low latency.

[0003] Such diverse use case scenarios require a disruptive approach for the realization of future 5G systems. It is assumed that multiple transmission / reception points (multi-TRPs) will be essential in 5G to improve reliability, coverage, and capacity performance through flexible deployment scenarios. For example, to support the exponential growth of mobile data traffic in 5G and enable coverage expansion, wireless devices are expected to access networks consisting of multiple TRPs (i.e., macrocells, small cells, picocells, femtocells, remote radio heads, relay nodes, etc.). [Brief explanation of the drawings]

[0004] [Figure 1] FIG. 1 shows an example block diagram illustrating an example of user equipment(s) (UE) communicatively coupled to a network having network components as peer devices usable in connection with various embodiments (aspects) described herein.

[0005] [Figure 2] 1 illustrates exemplary components of a device that can be used in accordance with various aspects described herein.

[0006] [Figure 3] FIG. 1 illustrates an example simplified block diagram of a user equipment (UE) wireless communication device or other network device / component (e.g., eNB, gNB), in accordance with various aspects.

[0007] [Figure 4] 1 illustrates example channel state information CSI extensions for single transmit / receive point (sTRP) and multiple TRP (mTRP) operation, in accordance with various aspects.

[0008] [Figure 5] 1 illustrates an example process flow for CSI extension for sTRP and mTRP operation, in accordance with various aspects.

[0009] [Figure 6] 10 illustrates another example process flow for CSI extension for sTRP and mTRP operation, in accordance with various aspects.

[0010] [Figure 7] 10 illustrates another example process flow for CSI extension for sTRP and mTRP operation, in accordance with various aspects.

[0011] [Figure 8] 1 illustrates another example process flow and CSI reporting configuration for CSI extension for sTRP and mTRP operations, in accordance with various aspects.

[0012] [Figure 9] 1 illustrates another example process flow and CSI reporting configuration for CSI extension for sTRP and mTRP operations, in accordance with various aspects.

[0013] [Figure 10] 1 illustrates another example CSI extension for sTRP and mTRP operation, in accordance with various aspects. DETAILED DESCRIPTION OF THE INVENTION

[0014] Considering various concerns regarding multiple transmission / reception points (mTRPs) used in 5G to improve reliability, coverage, and capacity performance through flexible deployment scenarios, channel state information (CSI) report priority extensions, dynamic channel measurement resource (CMR) resource configuration, and CSI compression may be configured according to aspects of the present disclosure to support multiple TRP (mTRP) operation. In particular, CSI reporting may be configured for both mTRPs and single TRPs (sTRPs). Users at the cell edge may be served with low quality of service (QoS) due to relatively long distances from base stations and unfavorable channel conditions (e.g., inter-cell interference (ICI) from neighboring base stations). Multiple TRP or mTRP operation may be one key to mitigating ICI through dynamic coordination between mTRPs to provide integrated scheduling and transmission / reception. In this way, wireless devices at the cell edge can be served by mTRP operation to improve their signal transmission / reception, resulting in increased throughput.

[0015] While some existing networks may support some mTRP schemes, the supported features may not accommodate newly identified deployment scenarios in 5G. For example, transmitting multiple control signals via mTRP may be beneficial to improve the reliability of ultra-reliable low-latency communications (uRLLC), vehicle-to-everything (V2X), and high-speed train use cases by providing link diversity gains, especially for cell-edge users. Furthermore, the high carrier frequencies (e.g., millimeter waves) in 5G facilitate the deployment of a large number of antennas (e.g., so-called massive MIMO) at base stations, which requires beam management procedures for mTRP technology.

[0016] In one aspect, a user equipment (UE) or other network component may receive a downlink control information (DCI) or radio resource control (RRC) message having a CSI resource configuration for generating a channel state information (CSI) report based on sTRP and / or mTRP operations. The CSI report may be generated based on the CSI report configuration and multiple CSI report priority variables, including measurements for sTRP and mTRP operations. In one example, the CSI report may be based on one or more CSI report priority variables associated with measurements for sTRP operations that have a different priority (e.g., higher or lower priority) than measurements for mTRP operations. The UE may calculate priorities to be associated with these measurements as a function of one or more of the CSI report priority variables and to generate the CSI report according to, for example, the UE capacity or payload for a single report. Similarly, a base station or gNB may configure DCI for both sTRP and mTRP according to these operations.

[0017] Currently, reference signal configurations or CMR resource configurations signaled by RRC can be slow, on the order of hundreds of milliseconds (ms) to a few seconds, compared to baseband signaling milliseconds or faster. However, MAC CEs can be signaled faster, on the order of a few ms, 3-5 ms, or 10 ms. In one aspect, a UE or other network component can receive and process a medium access control (MAC) control element (MAC-CE) configured by a base station or gNB, which dynamically modifies / updates the CMR resources of the CSI report configuration. The MAC-CE can include, for example, a CSI report configuration ID, a serving cell index, one or more selections of several CMR resources for sTRP measurements, and several pairs of CSI resources configured for mTRP measurements. In addition, corresponding CSI interference measurement (CS-IM) resources can also be configured based on these MAC-CE modifications / updates. For example, CSI-IM resources including zero-power interference measurement resources (IMRs) may be activated or deactivated according to updates to the number of CSI resources for sTRP and the number of CSI resource pairs for mTRP measurements in order to dynamically update the CMR and IMR resources for CSI reports.

[0018] In another aspect, a CSI report may be generated based on CSI compression such that one or more reporting quantities of an sTRP operation that are shared or common with reporting quantities of an mTRP operation are reported once in the CSI report rather than being repeated or overlapping each other. This implementation may save resources in terms of payload. The reporting quantities may include, for example, a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast resource block indicator (SSBRI), a rank indicator (RI), a precoding matrix indicator (PMI), or a layer indicator (LI). Furthermore, one or more indicators of CSI compression may be reported in the CSI report corresponding to one or more reporting quantities in the CSI report to indicate that the reporting quantity values ​​are shared and reported only once. This may allow a gNB not to decode quantities unnecessarily or a UE not to report quantities unnecessarily.

[0019] Additional aspects and details of the disclosure are further described below with reference to the figures.

[0020] 1 illustrates an exemplary architecture of a system 100 of networks according to various embodiments (aspects). The following description is provided for the exemplary system 100 capable of interfacing with LTE system standards, and 5G or NR system standards, as provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this respect, and the described embodiments may 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.

[0021] As shown in FIG. 1, system 100 includes UE 101a and UE 101b (collectively referred to as "UE(s) 101").In this example, the UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more cellular networks), but may also be a consumer electronic device, a mobile phone, a smartphone, a feature phone, a tablet computer, a wearable computing device, a personal digital assistant (PDA), a pager, a wireless handset, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an onboard diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an Electronic Engine Management System (EEMS), an electronic / engine control unit (ECU), an electronic / engine control module ... The computing device may include any mobile or non-mobile computing device such as electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, Machine Type Communication (MTC) devices, Machine to Machine (M2M), Internet of Things (IoT) devices, and / or the like.

[0022] In some embodiments, any of the UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications utilizing short-term UE connections. IoT UEs 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 Services (ProSe) or Device-to-Device (D2D) communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. An IoT network describes IoT UEs connecting with each other, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) over short-term connections. IoT UEs may also run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate IoT network connectivity.

[0023] The UE 101 may be configured to connect to, e.g., be communicatively coupled to, a Radio Access Network (RAN) 110. In an embodiment, the RAN 110 may be a next generation (NG) RAN or 5G RAN, an evolved-UMTS Terrestrial RAN (E-UTRAN), or a legacy RAN such as a UTRAN or GERAN. As used herein, terms such as "NG RAN" may refer to a RAN 110 operating in an NR or 5G system 100, and terms such as "E-UTRAN" may refer to a RAN 110 operating in an LTE or 4G system 100. The UE 101 utilizes connections (or channels) 102 and 104, respectively, which each include a physical communication interface / layer.

[0024] Alternatively, or in addition, each UE 101 can be configured with dual connectivity (DC) as multi-RAT or multi-Radio Dual Connectivity (MR-DC), where a multiple Rx / Tx capable UE can be configured to utilize resources provided by two different nodes (e.g., 111, 112, or other network nodes) that can be connected over a non-ideal backhaul, for example, one providing NR access and the other providing either E-UTRA for LTE or 5G NR access. One node can function as a master node (MN) and the other as a secondary node (SN). The MN and SN can be connected via a network interface, with at least the MN connected to the core network 120. At least one of the MN or SN can operate with shared spectrum channel access. All functionality specified for the UE can be used for integrated access and backhaul mobile termination (IAB-MT). Similar to the UE 101, the IAB-MT can access the network either using one network node or using two different nodes using the EN-DC architecture, the NR-DC architecture, etc.

[0025] In MR-DC, a group of serving cells associated with a master node can be configured as a Master Cell Group (MCG), comprising a Special Cell (SpCell) as a Primary Cell (PCell) and optionally one or more Secondary Cells (SCells). The MCG can be a radio access node providing a control plane connection to the Core Network (CN) 120, such as a Master eNB (in EN-DC), a Master ng-eNB (in NGEN-DC), or a Master gNB (in NR-DC and NE-DC). An SpCell can refer to either a PCell of an MCG or a Primary Secondary Cell (PSCell) of a Second Cell Group (SCG), depending on whether the MAC entity is associated with an MCG or an SCG, respectively. An SpCell can refer to a PCell of an MCG or an SCG. An SCG in MR-DC can be a group of serving cells associated with an SN, including an SPCell as a PSCell and optionally one or more SCells.

[0026] In this example, connections 102 and 104 are illustrated as air interfaces for enabling a communicative coupling and may align with a cellular communication protocol, such as a Global System for Mobile communications (GSM) protocol, a Code-Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over-cellular (POC) protocol, a Universal Mobile Telecommunications Service (UMTS) protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any of the other communication protocols described herein. In an embodiment, UE 101 may exchange communication data directly via ProSe interface 105. The ProSe interface 105 may alternatively be referred to as the SL interface 105 and may comprise one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0027] The UE 101b is shown configured to access the AP 106 (also referred to as a "WLAN node 106," "WLAN 106," "WLAN terminal 106," "WT 106," etc.) via a connection 107. The connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, and the AP 106 may comprise a Wireless Fidelity (WiFi) router. In this example, the AP 106 is connected to the Internet without connecting to a wireless system core network, as shown (described in further detail below). In various embodiments, the UE 101b, the RAN 110, and the AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operation and / or LTE-WLAN Radio Level Integration (LWIP) operation with IPsec tunnels. LWA operation may involve the UE 101b in radio resource control RRC_CONNECTED being configured by the RAN nodes 111a-111b to utilize LTE and WLAN radio resources. LWIP operation may involve the UE 101b using WLAN radio resources (e.g., connection 107) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 107. IPsec tunneling may involve encapsulating the entire original IP packet and adding a new packet header, thereby protecting the IP packet's original header.

[0028] The RAN 110 may include one or more access AN or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111 or "RAN nodes 111") that enable the connections 102 and 104. As used herein, the terms "access node," "access point," etc. may describe equipment that provides wireless baseband functionality for data and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, Transmission Reception Points (TRxPs), TRPs, etc., and may include earth 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. may refer to a RAN node 111 operating in an NR or 5G system 100 (e.g., a gNB), and the terms "E-UTRAN node" etc. may refer to a RAN node 111 operating in an LTE or 5G system 100 (e.g., an Next Generation NodeB (gNB)). According to various embodiments, the RAN node 111 may be implemented as one or more of dedicated physical devices, such as a macrocell base station and / or a low power (LP) base station, to provide a femtocell, picocell, or other similar cell having a smaller coverage area, lower user capacity, or higher bandwidth compared to a macrocell.

[0029] In some embodiments, all or part of the 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 embodiments, the CRAN or vBBUP may implement RAN function splitting, such as a Packet Data Convergence Protocol (PDCP) splitting, where the Radio Resource Control (RRC) and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by individual RAN nodes 111; a Media Access Control (MAC) / Physical (PHY) layer splitting, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" splitting, where the RRC, PDCP, RLC, MAC, and upper parts of the PHY layer are operated by the CRAN / vBBUP and the lower part of the PHY layer is operated by individual RAN nodes 111. This virtualized framework allows freed processor cores of the RAN node 111 to run other virtualized applications.

[0030] In some implementations, individual RAN nodes 111 may represent individual gNB Distributed Units (DUs) connected to a gNB Control Unit (CU) via individual F1 interfaces. In these implementations, the gNB-DUs may include one or more remote radio heads or RF front end modules (RFEMs), and the gNB-CUs may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to a CRAN / vBBUP. In some cases, the gNB-DUs, gNB-CUs, or other functions of the RAN nodes 111 may be co-located, while in other cases they are not co-located and / or operated by different entities. Additionally or alternatively, one or more of the RAN nodes 111 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol termination for the UE 101 and are connected to 5GC via an NG interface.

[0031] Any of the RAN nodes 111 may terminate the air interface protocols and may be the first point of contact for the UE 101. In some embodiments, any of the RAN nodes 111 may perform various logical functions for the RAN 110, including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0032] In embodiments, the UEs 101 may be configured to communicate with either one another or the RAN nodes 111 using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals over multi-carrier communication channels 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), although the scope of the embodiments is not limited in this respect. An OFDM signal may include multiple orthogonal subcarriers.

[0033] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, also called a resource grid or time-frequency resource grid, which represents the downlink physical resources within each slot. Such a time-frequency plane representation is common in OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit of the resource grid is denoted as a resource element. Each resource grid contains a number of resource blocks, which represent the mapping of a particular physical channel to resource elements. Each resource block contains a set of resource elements, which, in the frequency domain, can represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels conveyed using such resource blocks.

[0034] According to various embodiments, the UE 101 and the RAN node 111 communicate data (e.g., transmit and receive) over 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").

[0035] The PDSCH conveys user data and higher layer signaling to the UEs 101. The physical downlink control channel (PDCCH) carries, among other things, information regarding the transport format and resource allocation for the PDSCH channel. It may also inform the UEs 101 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information for the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 101b in a cell) may be performed by any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information may be transmitted on the PDCCH used (e.g., assigned) for each of the UEs 101.

[0036] The PDCCH conveys control information using control channel elements (CCEs). Before being mapped to resource elements, PDCCH complex-valued symbols may first be organized into quadruplets and then shuffled using a subblock interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, and each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs depending on the size of the DCI and the channel conditions. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, 16).

[0037] In aspects where the system 100 is a 5G or NR system, the 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) that connect to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB that connect to the 5GC 120, and / or between two eNBs that connect to the 5GC 120. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data transfer and flow control functions. The Xn-C may provide mobility support for the UE 101 in connected mode (e.g., CM-CONNECTED), including management and error handling functions, functions to manage the Xn-C interface, and functions to manage UE mobility in connected mode between one or more RAN nodes 111. Mobility support can include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111 and control of user plane tunnels between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The Xn-U protocol stack can include a transport network layer built on an Internet Protocol (IP) transport layer, a User Datagram Protocol (UDP) layer and / or a GPRS Tunneling Protocol for the User Plane (GTP-U) layer on top of the IP layer(s) to carry user plane PDUs. The Xn-C protocol stack can include an application layer signaling protocol (called the Xn Application Protocol (Xn-AP)) and a transport network layer built on the Stream Control Transmission Protocol (SCTP). SCTP can be on top of the IP layer and can provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission is used to deliver signaling PDUs.In other 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 stack(s) shown and described herein.

[0038] The RAN 110 is shown communicatively coupled to a core network, in this embodiment, a core network (CN) 120. The CN 120 may comprise multiple network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UEs 101) connected to the CN 120 via the RAN 110. The components of the CN 120 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored on one or more computer-readable storage media (described in further detail below). A logical instantiation of the CN 120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures may be used to virtualize one or more network functions on physical resources, including a combination of industry-standard server hardware, storage hardware, or switches, or may be performed by dedicated hardware. In other words, an NFV system can be used to run a virtual or reconfigurable implementation of one or more Evolved Packet Core (EPC) components / functions.

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

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

[0041] In an aspect, when the CN 120 is an EPC (referred to, for example, as "EPC 120"), the RAN 110 may connect with the CN 120 via an S1 interface 112. In an embodiment, the S1 interface 112 may be divided into two parts: an S1 user plane (S1-U) interface 114 that carries traffic data between the RAN node 111 and the S-GW, and an S1-MME interface 115 that is a signaling interface between the RAN node 111 and the MME.

[0042] 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).

[0043] The UPF can function, for example, as an anchor point for intra-RAT and inter-RAT mobility, an external Protocol Data Unit (PDU) session point for interconnection with the data network (DN), and a branching point for supporting multi-homed PDU sessions. The UPF can also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), perform uplink traffic validation (e.g., mapping Service Data Flows (SDFs) to Quality of Service (QoS) flows), enforce transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF may include an uplink classifier to support routing traffic flows to the data network. The DN can be various network operator services, Internet access, or third-party services, and includes or resembles an application server. The UPF can interact with the SMF via the N4 reference point between the SMF and the UPF.

[0044] The AUSF may, for example, store data for authentication of the UE 101 and handle authentication-related functionality. The AUSF may facilitate a common authentication framework for various access types. The AUSF may communicate with the AMF via the N12 reference point between the AMF and the AUSF, and may communicate with the UDM via the N13 reference point between the UDM and the AUSF. Additionally, the AUSF may present a Nausf service-based interface.

[0045] The AMF may be involved in, for example, registration management (e.g., for registering the UE 101), connection management, reachability management, mobility management, and lawful interception and access authentication and authorization of AMF-related events. The AMF may be the termination point of the N11 reference point between the AMF and the SMF. The AMF provides transport of SM messages between the UE 110 and the SMF and can function as a transparent proxy for routing SM messages. The AMF can also perform transport for SMS messages between the UE 101 and a Short Message Service (SMS) Function (SMSF). The AMF can function as a Security Anchor Function (SEAF), which may include receiving intermediate keys established as a result of the interaction between the AUSF and the UE 101 and / or the UE 10 authentication process. When Universal Subscriber Identity Module (USIM)-based authentication is used, the AMF can obtain security materials from the AUSF. The AMF may also include a Single-Connection Mode (SCM) function that receives keys from the SEA to use to derive access network-specific keys. Furthermore, the AMF may be the termination point of the RAN Control Plane (CP) interface, which may be or include the N2 reference point between the (R)AN 110 and the AMF, and the AMF may also be the termination point of Non Access Stratum (NAS) (N1) signaling and perform NAS ciphering and integrity protection.

[0046] The AMF may also support NAS signaling with the UE 101 via a non-3GPP (N3) Interworking Function (IWF) interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point of the N2 interface between the (R)AN 110 and the AMF for the control plane, and the termination point of the N3 reference point between the (R)AN 101 and the UPF for the user plane. Thus, the AMF may handle 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 enforce QoS corresponding to N3 packet markings taking into account QoS requirements associated with such markings received via N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between the UE 101 and the AMF, and can relay uplink user plane packets and downlink user plane packets between the UE 101 and the UPF, via the N1 reference point between the UE 101 and the AMF. The N3IWF also provides a mechanism for IPsec tunnel establishment with the UE 101. The AMF can present a Namf service-based interface and can be the termination point for the N14 reference point between two AMFs and the N17 reference point between the AMF and the 5G Equipment Identity Register (5G-EIR) (not shown in Figure 1).

[0047] The UE 101 can register with the AMF to receive network services. Registration Management (RM) is used to register or deregister the UE 101 with a network (e.g., the AMF) and establish a UE context within the network (e.g., the AMF). The UE 101 can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 101 is not registered with the network, and the UE context in the AMF does not hold valid location or routing information for the UE 101, so that the UE 101 is not reachable by the AMF. In the RM-REGISTERED state, the UE 101 is registered with the network, and the UE context in the AMF can hold valid location or routing information for the UE 101, so that the UE 101 is reachable by the AMF. In the RM-REGISTERED state, the UE 101 may, among other things, perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiry of a periodic update timer (e.g., to inform the network that the UE 101 is still active), update UE capability information, or perform a registration update procedure to renegotiate protocol parameters with the network, among other things.

[0048] The AMF may store one or more RM contexts for the UE 101, each RM context being associated with a particular access to the network. An RM context may be a data structure, database object, etc. that indicates or stores, among other things, a registration state and periodic update timer per access type. The AMF may also store a 5GC Mobility Management (MM) context, which may be the same as or similar to an (Enhanced Packet System (EPS)) Mobility Management (MM) (Enterprise Mobility Management (E)MM)) context. In various embodiments, the AMF may store Coverage Enhancement (CE) Mode B regulatory parameters for the UE 101 in the associated MM context or RM context. The AMF may also derive values ​​from the UE's usage configuration parameters already stored in the UE context (and / or MM / RM context), as needed.

[0049] 2 illustrates example components of a device 200 according to some aspects. In some aspects, device 200 may include, at least as shown, an application circuit 202, a baseband circuit 204, a radio frequency (RF) circuit 206, a front-end module (FEM) circuit 208, one or more antennas 210, and a power management circuitry (PMC) 212 coupled together. The components of device 200 illustrated in the figure may be included in a UE or a RAN node. In some aspects, device 200 may include fewer elements (e.g., a RAN node may not utilize application circuit 202 and instead may include a processor / controller that processes IP data received from a CN, such as a 5GC120 or an Evolved Packet Core (EPC)). In some embodiments, device 200 may include additional elements such as, for example, memory / storage, a display, a camera, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations within device 200, etc.), or input / output (I / O) interfaces. In other aspects, the components described below may be included in two or more devices (e.g., the above circuitry may be included separately in two or more devices for a Cloud-RAN (C-RAN) implementation).

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

[0051] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuitry 206 and generate baseband signals for the transmit signal path of the RF circuitry 206. The baseband circuitry 204 may interface with the application circuitry 202 for generating and processing the baseband signals and for controlling the operation of the RF circuitry 206. For example, in some aspects, the 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 baseband processor(s) 204D of other existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of the baseband processors 204A-204D) can handle various radio control functions that enable communication with one or more wireless networks via the RF circuitry 206. In another aspect, some or all of the functionality of the baseband processors 204A-D may be included in modules stored in the memory 204G and executed via the central processing unit 204E. The memory 204G may include executable components or instructions that cause one or more processors (e.g., the baseband circuitry 204) to perform aspects, processes, or operations herein. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. 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 convolutional, tail-biting convolutional, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Aspects of the modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other aspects.

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

[0053] In some aspects, the baseband circuitry 204 may provide communications compatible with one or more wireless technologies. For example, in some aspects, the baseband circuitry 204 may support communications with a Next Generation (NG)-Radio Access Network (RAN), an evolved universal terrestrial radio access network (EUTRAN), or other wireless metropolitan area network (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. An aspect in which the baseband circuitry 204 is configured to support wireless communications of two or more wireless protocols may be referred to as a multimode baseband circuit.

[0054] The RF circuitry 206 can enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various aspects, the RF circuitry 206 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 206 can include a receive signal path that can include circuitry to downconvert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. The RF circuitry 206 can also include a transmit signal path that can include circuitry to upconvert baseband signals provided by the baseband circuitry 204 and provide an RF output signal to the FEM circuitry 208 for transmission.

[0055] In some aspects, the receive signal path of the RF circuit 206 may include a mixer circuit 206a, an amplifier circuit 206b, and a filter circuit 206c. In some aspects, the transmit signal path of the RF circuit 206 may include a filter circuit 206c and the mixer circuit 206a. The RF circuit 206 may also include a combiner circuit 206d that combines frequencies used by the mixer circuit 206a of the receive signal path and the transmit signal path. In some aspects, the mixer circuit 206a of the receive signal path may be configured to downconvert the RF signal received from the FEM circuit 208 based on the combined frequency provided by the combiner circuit 206d. The amplifier circuit 206b may be configured to amplify the downconverted signal, and the filter circuit 206c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 204 for further processing. In some aspects, the output baseband signal may be a zero-frequency baseband signal, although this is not a requirement. In some aspects, mixer circuitry 206a of the receive signal path may include a passive mixer, although the scope of the aspects is not limited in this respect.

[0056] In some aspects, the mixer circuit 206a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by the synthesis circuit 206d to generate an RF output signal for the FEM circuit 208. The baseband signal may be provided by the baseband circuit 204 and filtered by the filter circuit 206c.

[0057] In some aspects, mixer circuit 206a in the receive signal path and mixer circuit 206a in the transmit signal path may include two or more mixers and may be configured for quadrature downconversion and quadrature upconversion, respectively. In some aspects, mixer circuit 206a in the receive signal path and mixer circuit 206a in the transmit signal path may include two or more mixers and may be configured for image rejection (e.g., Hartley image rejection). In some aspects, mixer circuit 206a in the receive signal path and mixer circuit 206a may be configured for direct downconversion and direct upconversion, respectively. In some aspects, mixer circuit 206a in the receive signal path and mixer circuit 206a in the transmit signal path may be configured for superheterodyne operation.

[0058] In some aspects, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the 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, the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 204 may include a digital baseband interface that communicates with the RF circuitry 206.

[0059] In some dual-mode embodiments, separate radio IC circuitry may be provided for processing signals in each spectrum, although the scope of the embodiments is not limited in this respect.

[0060] In some aspects, the combining circuit 206d may be a fractional-N combiner or a fractional-N / N+1 combiner, although the scope of the aspects is not limited in this respect as other types of frequency combiners may be suitable. For example, the combining circuit 206d may be a delta-sigma combiner, a frequency multiplier, or a combiner comprising a phase-locked loop with a frequency divider.

[0061] The combining circuit 206d may be configured to combine, based on a frequency input and a divider control input, an output frequency used by the mixer circuit 206a of the RF circuit 206. In some aspects, the combining circuit 206d may be a fractional N / N+1 combiner.

[0062] In some aspects, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not a requirement. The divider control input may be provided by either the baseband circuitry 204 or the application processor 202, depending on the desired output frequency. In some aspects, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuitry 202.

[0063] The synthesis circuit 206d of the RF circuit 206 may include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the divider may be a dual modulus 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 either N or N+1 (e.g., based on the implementation) to provide a fractional division ratio. In some exemplary aspects, the DLL may include a cascaded tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these aspects, the delay elements may be configured to divide the VCO period into Nd equal-phase packets, 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 cycle.

[0064] In some aspects, the combiner circuit 206d may be configured to generate the carrier frequency as the output frequency, while in other aspects the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with different phases relative to each other. In some aspects, the output frequency may be the LO frequency (fLO). In some aspects, the RF circuit 206 may include an IQ / polar converter.

[0065] The FEM circuitry 208 may include a receive signal path that 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 the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 that are transmitted by one or more of the one or more antennas 210. In various aspects, amplification through the transmit or receive signal path can occur solely in the RF circuitry 206, solely in the FEM circuitry 208, or in both the RF circuitry 206 and the FEM circuitry 208.

[0066] In some aspects, the FEM circuitry 208 may include a TX / RX switch that switches between transmit and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low noise amplifier (LNA) that amplifies a received RF signal and provides the amplified received RF signal as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) that amplifies an input RF signal (e.g., provided by the RF circuitry 206) and one or more filters that generate an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 210).

[0067] In some aspects, the PMC 212 can manage the power supplied to the baseband circuitry 204. Specifically, the PMC 212 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. When the device 200 can be powered by a battery, for example, when the device is included in a UE, the PMC 212 can often be included. The PMC 212 can improve power conversion efficiency while providing desirable packaging size and heat dissipation characteristics.

[0068] 2 shows the PMC 212 coupled only to the baseband circuitry 204. However, in other aspects, the PMC 212 may additionally or alternatively be coupled to other components, including, but not limited to, the application circuitry 202, the RF circuitry 206, or the FEM circuitry 208, to perform similar power management operations.

[0069] In some aspects, PMC 212 can control or otherwise be a part of various power saving mechanisms of device 200. For example, if device 200 is in an RRC_Connected state where it is still connected to a RAN node because it expects to receive traffic soon, after a period of inactivity the device can enter a state known as discontinuous reception mode (DRX). While in this state, device 200 can save power by powering down for short intervals.

[0070] If there is no data traffic activity for an extended period of time, the device 200 can transition to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 enters a very low power state and periodically wakes up to listen to the network and perform paging, then powers down again. The device 200 cannot receive data in this state and can transition back to the RRC_Connected state to receive data.

[0071] In an additional power-saving mode, the device may be allowed to be unavailable from the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this time, the device may be completely unable to reach the network and may power down completely. Any data transmitted during this time will be significantly delayed, but the delay is deemed acceptable.

[0072] The processors of the application circuitry 202 and the baseband circuitry 204 can be used to execute elements of one or more instances of a protocol stack. For example, the processors of the baseband circuitry 202 can be used, alone or in combination, to execute Layer 3 (L3), Layer 2 (L2), or Layer 1 (L1) functions, and the processor of the application circuitry 204 can further execute Layer 4 functions (e.g., a transmission communication protocol (TCP) layer and a user datagram protocol (UDP) layer) using data (e.g., packet data) received from these layers. As described above, Layer 3 can include a radio resource control (RRC) layer, which is described in more detail below. As described above, Layer 2 can include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which are described in more detail below. As described herein above, Layer 1 may include the physical (PHY) layer of the UE / RAN node.

[0073] 3, a block diagram of a user equipment (UE) or another network device / component (e.g., a gNB, eNB, or other participating network entity / component) is shown. The device 300 includes one or more processors 310 (e.g., one or more baseband processors) with processing circuitry and associated interface(s), transceiver circuitry 320 (e.g., with RF circuitry that 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) that may use common circuit elements, separate circuit elements, or a combination 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 processor(s) 310 or transceiver circuitry 320).

[0074] Memory 330 (as well as other memory components described herein, e.g., memory, data storage, etc.) may include one or more machine-readable medium(s) containing instructions that, when executed by a machine or component described herein, cause the machine or other device to perform operations of a method, apparatus, or system for communicating using multiple communication technologies in accordance with 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. If implemented in software, functions can be stored on or transmitted over a computer-readable medium (e.g., a memory or other storage device described herein) as one or more instructions or code. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media or computer-readable storage devices may be any available medium that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible and / or non-transitory medium that can be used to hold or store desired information or executable instructions. Also, any connection may be referred to as a computer-readable medium.

[0075] In one aspect, the UE / gNB device 300 can operate to configure, by processing / generating / encoding / decoding, a physical layer transmission comprising multiple transport blocks (TBs) based on unequal protection between different TBs in a physical layer encapsulation (e.g., EPC packet, transmission opportunity, MCOT, single transmission burst, TTI, or other encapsulation protocol, or related encapsulation parameter for encapsulating data from higher layers into a frame for transmission over the air). The physical layer transmission can be received, transmitted, or provided using the communication / transmitter circuitry 320 to similarly process / generate a physical layer transmission with a spatial layer over a physical channel in the NR network.

[0076] The processor 310 may be a component of an application circuit or a processor of a baseband circuit, which may be used to execute components or elements of one or more instances of a protocol stack. For example, the processor 310 of the baseband circuit may be configured to execute various aspects or embodiments for CSI extension for mTRP operation, such as single TRP (sTRP) and mTRP operation for CSI reporting, alone or in combination. Different schemes may be configured for mTRP operation. This includes multi-DCI-based multi-TRP operation in which two different control information (e.g., different DCIs) schedule transport blocks (TBs) for mTRP operation. Furthermore, several schemes may be configured for single DCI-based multi-TRP operation. For example, a spatial domain multiplexing (SDM) scheme may be used for a single TB, and various frequency domain multiplexing (FDM) schemes (e.g., FDM scheme A for single TB and FDM scheme B for dual TB) and a time domain multiplexing (TDM) scheme for intra-slot repetition may be used. CSI reporting and CSI report generation via processor(s) 310 can be utilized to enable link adaptation for further CSI enhancement, as well as explicit interference hypothesis testing to optimize the precoder for each TRP and efficient switching between single-TRP and multi-TRP operation.

[0077] In one aspect, the processor(s) 310 can configure a set of CMR resources for CSI reporting configuration and distinguish which CMR resources come from which TRP. Thus, the gNB 111 (e.g., as the device 300) can configure a total of K resources, including K1 resources for the first TRP and K2 resources for the second TRP. s K CSI resources can be signaled to the UE 101 (e.g., as the device 300), s = K1 + K2 includes CMR resources configured for single TRP measurements. The gNB 111 can also configure N pairs of CMR resource pairs for mTRP measurements. Thus, two groups of CMR resources for sTRP measurements and N CIS resource pairs can be utilized for mTRP measurements, for example, by CSI report configuration via RRC messages.

[0078] In the case of a CSI report or test measurement configuration, the UE 101 can also report both sTRP (single TRP) resources and mTRP resources in one CSI report. For example, the UE 101 can inform the gNB 111 what the preferred single TRP is (e.g., either the first TRP or the second TRP) and which resources and transmission scheme details the UE 101 prefers (e.g., CRI, PMI, RI, CQI, or other quantities). Thus, the UE 101 can report what the preferred mTRP is, including, for example, which resources the UE 101 prefers from the first TRP or which are preferred from the second TRP.

[0079] 4, an example CSI extension for sTRP and mTRP operations is shown, according to various aspects of the present specification. The UE 101 (e.g., 300) can receive an RRC message or DCI 404 in a physical channel 402 having a CSI reporting configuration provided by the gNB 111 to enable / trigger reporting of both sTRP and mTRP measurements. The UE 101 can then measure both sTRP and mTRP measurements in sTRP and mTRP operations (or testing operations via hypothesis testing) and generate a CSI report 410 in an uplink physical channel 408.

[0080] In various aspects, CSI report priority may be calculated based on CSI report priority variables, which may include report type, report amount, serving cell index, reporting configuration ID, and sTRP / mTRP operation. Each of these variables may be weighted in priority, and if the priority weighting / ordering for one variable is the same or similar to the weighting for another variable, the next variable may be configured as being more significant than another less weighted variable. For example, report type may carry a greater weighting than report amount, which may have a greater weighting than serving cell index or reporting configuration ID. In one aspect, sTRP / mTRP operation measurements may be given the highest priority weighting / ranking among the priority variables or the lowest priority weighting / ranking among the measurements.

[0081] Additionally, within each priority variable, factors / parameters associated with each priority variable may also be given different priorities / rankings / orderings. For example, report types may include, e.g., aperiodic CSI (AP-CSI) on PUSCH, semi-persistent CSI (SP-CSI) on PUSCH, SP-CSI on PUCCH, and persistent CSI (P-CSI) on PUCCH, where each may have a ranking / priority order from highest to lowest along with the report type. Report quantities may include link adaptation measures for beam management, such as beam quality (e.g., Layer 1 (L1)-Reference Signal Received Power (RSRP) or L1-Signal-to-Interference-and-Noise Ratio (SINR)), or others (e.g., precoder matrix indicator (PMI), channel quality indicator (CQI), rank indicator (RI), etc.). Similarly, each of these may be given a specific priority as a sub-priority or ranking with a report quantity having its own priority within the CSI report priority variable.

[0082] In one aspect, when the gNB 111 configures the UE 101 to report both single-TRP (sTRP) measurements and multi-TRP measurements (mTRP), a CSI extension in a single DCI for multi-TRP in a single CSI report is configured. The corresponding CSI can be divided into two or more parts, each part having a different priority. A CSI report can have measurements corresponding to different parts of one or more CSI, each having a different priority. Alternatively or additionally, a CSI priority variable in the CSI report can be weighted or assigned a priority such that mTRP measurements have a higher priority compared to sTRP measurements. Alternatively or additionally, sTRP measurements can have a higher priority compared to mTRP measurements.

[0083] The UE 101 may be configured to process multiple CSIs, particularly when an mTRP is configured for multiple reports being reported in a single CSI report based on the received CSI report configuration. These CSIs may have different properties with different time domain priorities, as described above with respect to report type, report amount, serving cell and configuration ID, and different priority variables by sTRP / mTRP, which may be measured, tested, and defined for the CSI report.

[0084] For example, the UE 101 can uniquely calculate CSI and uniquely calculate CSI priority. This CSI priority can be configured for at least two purposes: configuring uplink control information (UCI) multiplexing omission as UCI omission and performing CSI multiplexing so that CSI can be carried in the same PUCCH or the same PUSCH payload. If the total CSI size is larger than what the payload can carry or what the corresponding PUCCH / PUSCH can carry, CSI skipping or UCI omission can be performed, in which some CSI reports may be ignored or not reported based on CSI report priority. Thus, lower-priority CSI may be multiplexed in a later portion of the payload, and if the size of the payload is not large enough, those CSI or partitioned portions may be skipped or omitted.

[0085] CSI priority may be related to the processing complexity in the CSI processing unit (CPU). UE 101 may report the number of CPUs that UE 101 can process per slot by informing gNB 111 how many CSI processing units (or CPUs) the UE can process in each slot based on the UE capabilities. If gNB 111 configures CSI reporting such that more CPUs than UE 101 can process or more than UE capabilities are utilized, UE 101 may not be required to update CSI reports that exceed the UE reporting capabilities.

[0086] The UE behavior when the CSI reporting configuration requires more CPU than the UE capabilities may be referred to herein as a CPU overbooking process. As a result of the CPU overbooking process, the UE 101 may be forced to change the CSI processing order, for example. In one aspect, when the CPU overbooking process occurs, the UE 101 may report old / current measurements for the CSI report despite the updated CSI reporting configuration.

[0087] In a single CSI report configuration in which sTRP and mTRP measurements are reported, the UE 101 can configure the priority according to different variables, including whether the measurement is for sTRP operation, mTRP operation, or both, when utilizing CSI priority to reduce the impact on CSI multiplexing and UCI omission operation, or CPU overbooking processing, for example. CSI multiplexing involves combining different CSI measurements for a CSI report, while UCI omission can refer to omitting the CSI portion of the report according to priority in uplink transmission.

[0088] In one aspect, the corresponding CSI may be divided into two or more portions, and each portion may be associated with a different priority. For example, a multi-TRP measurement may have a higher priority compared to a single-TRP measurement. Alternatively or additionally, a single-TRP measurement may have a higher priority compared to a multi-TRP measurement.

[0089] Referring to FIG. 5, an example process flow 500 for CSI report priority enhancement for sTRP and mTRP operations is shown, according to an aspect of the present specification. The process flow may begin at 502 by processing an RRC or DCI to configure sTRP and mTRP for measurements and generate a CSI report. At 504, the CSI may be divided into two or more CSI portions. A determination 506 may be made as to whether the portions (e.g., sTRP measurements, mTRP measurements, different CSI, etc.) have the same priority. If the portions are configured with the same priority, the process may proceed to reference label “A” or “A′” in FIG. 8 or FIG. 9, respectively. If the CSI portions have different priorities, the process proceeds to either 508, where mTRP measurements are given higher priority for CSI reporting than sTRP, or 510, where sTRP measurements have higher priority than mTRP.

[0090] Referring to FIG. 6, another example process flow 600 for CSI reporting priority enhancement for sTRP and mTRP according to an aspect of the present specification is shown. Process flow operations 602 and 604 may be similar to operations 502 and 504 of FIG. 5, for example. In 602, the UE 101 may process a single RRC or a single DCI that configures the UE to report both sTRP and mTRP. The corresponding CSI may be divided into two or more CSI portions. Each CSI portion may then be assigned the same or a different priority, such that each CSI portion is associated with a sub-CSI reporting priority. The CSI report may be configured differently depending on the impact on CPU overbooking (e.g., CPU overload) based on the sub-CSI reporting priority.

[0091] If a determination 606 is made that the CSI portions do not have the same priority, a decision 608 may determine whether more CPU is configured via a CSI report configuration (e.g., CSI-reportConfig, etc.) for the CSI report than the UE capabilities. If the CPU exceeds the UE capabilities in 608, a determination may be made in 610 regarding whether one or more sub-CSI report priorities affect CPU overbooking or processing capabilities of the CSI reports for the sTRP and mTRP. Alternatively, if it is determined that the CSI portions are assigned the same priority, process flow 600 may proceed to reference signs "A or A'" in Figures 8 and 9, respectively.

[0092] After dividing / partitioning the CSI into multiple CSI portions associated with priorities for the CSI report (as sub-CSI report priorities), UE 101 may configure all or none of the multiple CSI portions for the CSI report depending on whether one or more of the CSI portions with sub-CSI report priorities do not affect the CPU overbooking processing and the total CSI exceeds the payload amount for the physical channel transmission of the CSI report.

[0093] In one aspect, if it is determined in decision 610 that the sub-CSI report priority of the CSI portion does not affect CPU overbooking processing such that the gNB 111 configures more CPU than the UE capability for CSI reporting, then the UE 101 may determine in 610 to process all portions of the CSI report for reporting measurements in 612. Alternatively or additionally, the UE 101 may omit updating all of the CSI portions in the CSI report in 612.

[0094] In decision 610, if it is determined that the sub-CSI report priority affects CPU overbooking processing and more CPUs are configured for CSI reporting than the UE capabilities, UE 101 may determine to omit independently updating the CSI measurements for each individual portion of the CSI report depending on the sub-CSI report priority of the CSI portion.

[0095] In one aspect, for example, if gNB111 or RRC configures more CSI processing units than UE101 can process in a single CSI report, UE101 may be configured with the flexibility to select whether to process all of the CSI portions in the CSI report, process some of the CSI portions in the CSI report, or process none of the CSI portions in the CSI report.

[0096] For example, if UE 101 can process only one CPU and one CSI report has both single-TRP and multi-TRP, each utilizing one CPU, UE 101 may be allowed to process higher priority CSI measurements and skip lower priority CSI measurements. Thus, the CSI processing order may be determined by the CSI report priority within a single CSI report configuration.

[0097] Referring to FIG. 7, another example process flow 600 for CSI reporting priority enhancement for sTRP and mTRP according to an aspect of the present specification is shown. Process flow operations 702 and 704 may be similar to, for example, operations 502 and 504 of FIG. 5 and operations 602 and 604 of FIG. 6. At 702, the UE 101 may process a single RRC or a single DCI that configures the UE to report both sTRP and mTRP. At 704, the corresponding CSI may be divided into two or more CSI portions. Each CSI portion may then be assigned the same or a different priority, such that each CSI portion is associated with a sub-CSI reporting priority. The CSI reports may be configured differently depending on the impact on CSI multiplexing and UCI omission based on the sub-CSI reporting priority. For example, an impact may be observed when CSI measurements of CSI portions with lower priority may be multiplexed at the lower end of the CSI transmission and omitted in the UCI, for example, based on a reporting priority variable, which is further described in FIG. 8.

[0098] At 706, a determination is made as to whether the sub-CSI report priorities are the same or different from each other. If they are not the same, the process proceeds to decision 708. If they are the same, the process proceeds to reference "A or A'" in Figures 8 and 9, respectively.

[0099] At 708, if the total CSI to be reported in the CSI report exceeds a single payload of the PUCCH / PUSCH, a determination may be made as to whether sub-CSI report priorities associated with the CSI portions affect CSI multiplexing operations and UCI omission. If the determination is "no," UE 101 may choose to provide all of the CSI portions of the CSI report or omit all of the portions of the CSI report. However, if it is determined that there is an impact on CSI multiplexing operations and UCI omission, UE 101 may omit CSI content for each individual CSI portion of the CSI report independently based on priority.

[0100] 8, an exemplary process flow 800 with resulting CSI reports for sTRPs and mTRPs according to an embodiment of the present disclosure is shown. Process flow 800 begins at reference character A in FIGS. 5-7.

[0101] In response to receiving the CSI report configuration, UE 101 generates multiple CSI reports for sTRP and mTRP measurements and multiplexes them into the same payload, where UE 101 may be configured to multiplex both sTRP and mTRP measurements as a mixture into one CSI report for a single transmission.

[0102] At 802, the UE 101 may generate a CSI report by ordering different CSI portions within each CSI sub-report. At 804, the portions are ordered within each CSI sub-report by mTRP and sTRP measurements, and the CSI sub-reports are concatenated to create a single CSI report 810. In this manner, different measurement reports as CSI sub-reports are divided for corresponding CSI in multiple portions with the same priority. Different measurement reports may be multiplexed according to mTRP and sTRP measurements, and then different CSI measurement reports as CSI sub-reports may be concatenated together into one CSI report.

[0103] 8 may also imply a priority when UE 101 is performing UCI omission, such that lower portions or lower-indexed reports / portions may be omitted first. This implies that when UCI omission is performed, UE 101 first omits report-by-report, and then first attempts to omit either the sTRP or mTRP portion from a particular CSI report, for example, depending on the priority associated with the sTRP or mTRP. UE 101 may then report everything from the other CSI report portions, resulting in a priority implementation.

[0104] 9, another exemplary process flow 900 with resulting CSI reports for sTRPs and mTRPs according to an embodiment of the present disclosure is shown. Process flow 900 begins at reference character A' in FIGS. 5-7.

[0105] At 902, the UE 101 concatenates all sTRP portions together and all mTRP portions together separately. At 904, each of these concatenated portions is further concatenated together by order in the CSI report. In other words, the UE 101 can first order the portions with respect to the sTRP or mTRP, and then order them within the CSI report in the order of the different measurement reports as CSI sub-reports.

[0106] In this case, it is implied that the mTRP has priority over the sTRP-concatenated portion with respect to CSI multiplexing and UCI omission. This is an example of treating the sTRP as lower priority. Alternatively or additionally, the sTRP may have a higher ordering or implicit priority in the CSI report than the mTRP, for example, by a different indexing order. Thus, even if the priority associated with each report portion or sub-report is not different, the ordering can still imply a priority with respect to CSI multiplexing and UCI omission.

[0107] 10, another example of another CSI extension for mTRP operation is shown in accordance with various aspects herein. The UE 101 may further receive an updated configuration 1004 on a downlink physical channel 1002 from the gNB 111 to dynamically update CMR resources in the CSI report configuration for a single CSI report 1010 transmission on an uplink physical channel (e.g., PUCCH or PUSCH).

[0108] The MAC-CE may include a CSI report configuration ID, a serving cell index, and one or more selections for CSI resources. The selections may include some CSI resources for sTRP measurements (e.g., K1 resources for the first TRP and K2 resources for the second TRP) and some N' pairs of CSI resources configured for mTRP measurements. RRC signaling may operate to configure a superset of resources, such as K1 and K2 resources for sTRP and N pairs for mTRP. The gNB 111 may be configured to dynamically modify or update these resources, for example, by using the MAC-CE, instead of using RRC to reconfigure these resources.

[0109] The CSI reporting configuration update may be identified by the UE 101 using at least two reporting variables: a serving cell index indicating the serving cell, and a reporting configuration ID (e.g., CSI-reportConfigId). The RRC may configure a superset, or a large set of K (K+K) resources for sTRP and a large set of N pairs for mTRP, while the gNB 111 may modify the CMR resource selection via the MAC-CE within this superset. For example, the MAC-CE may be used to select a subset of this larger superset of CMR resources in various manners.

[0110] In one example, the gNB 111 may provide, along with the MAC-CE, a bitmap indicating the CMR resources to be activated or deactivated. The CMR resources (as CSI resources for CSI measurements) in the bitmap may be the maximum number of configured resources (K max ) and the maximum number of resource pairs for mTRP can be,N maxA bit corresponding to a bitmap location in the bitmap may indicate that the corresponding CMR resource or reference signal is activated for measurement or deactivated for measurement to generate CSI reports for both sTRP and mTRP.

[0111] In another example, rather than utilizing a bitmap, the MAC-CE can reduce overhead by indicating how many first resources to select from in superset order. For example, the network or gNB 111 can indicate K1', K2', N', where K1' indicates a selection of a first CMR resource for a first TRP, K2' indicates a second CMR resource for a second TRP, and N' indicates the number of first pairs of resources for mTRP measurement. For example, the gNB 111 can configure 16 K1, 16 K2, and 16 N, but then indicate to the UE 101 that K1' is equal to 2, K2' is equal to 2, and N' is equal to 1. In response, UE 101 measures the first two CMR resources in the first set of the superset for the first TRP for sTRP operation, measures the first two CSI resources in the second set of the superset for the second TRP for sTRP operation, and then measures only the first pair of resources for mTRP operation. Each of K1', K2', and N' may be a different resource, for example, in order of priority of the superset. UE 101 then generates a CSI report according to the updated CSI reporting configuration based on MAC-CE CMR resource selection using K1', K2', and N' in order of priority or index within the superset, for example.

[0112] In other aspects, corresponding CSI-IM resources may also be configured based on MAC-CE modification / updates to enable dynamic CMR resource selection and CSI-IM configuration. For example, CSI-IM resources (including zero-power interference measurement resources (IMRs)) may be activated or deactivated according to updates to the number of CSI resources for sTRP and the number of pairs for mTRP measurements to dynamically update CMR resources for CSI reporting.

[0113] For every CMR that includes a single CMR resource for sTRP measurement or a pair of CSI resources for mTRP measurement, the gNB 111 can configure a corresponding CSI-IM resource. This can be pre-configured or pre-determined, for example, as a one-to-one mapping of CMR resources to CSI-IM resources. If the gNB 111 configures, for example, eight CMR resources for a first TRP, eight CMR resources for a second TRP, and eight pairs of CMR resources for an mTRP, the gNB 111 configures a total of 24 zero-power IMR or CSI-IM resources in one-to-one correspondence with the total CMR resources. In a further example, if the MAC-CE selects a particular CMR, the corresponding IMR or CSI-IM can also be activated. Similarly, if the network deactivates a CMR, the network also deactivates the corresponding IMR or CSI-IM.

[0114] In other aspects, the gNB 111 can provide instructions to the UE 101 to report only sTRP tests, mTRP tests, or both in dynamic updates via the MAC-CE. Through CSI reporting configuration, the UE 101 can be configured to enable reporting of both sTRP tests and mTRP tests according to a measurement hypothesis. However, the gNB 111 can dynamically change the CSI reporting via the MAC-CE to configure only sTRP measurements, only mTRP measurements, or both sTRP and mTRP by testing measurements for the CSI reports (in a single transmission or a single CSI report). In particular, a single DCI / RRC message can enable mTRP measurement with sTRP measurement in a single CSI report by a single TRP hypothesis, multiple TRP hypotheses (as test techniques or methodologies), while the MAC-CE can use the values ​​of CSI-ReportConfigId (CSI report configuration ID), a ServCellIndex (serving cell index), and report hypothesis selection for sTRP, mTRP, or both to dynamically update the measurement hypothesis. This can be communicated in the MAC-CE using, for example, a bitmap. The bitmap can indicate whether the corresponding measurement hypothesis is activated or deactivated. For example, if only sTRP is indicated to be reported by the UE 101, the UE 101 can configure measurement testing for only sTRP for the next CSI report.

[0115] Additionally or alternatively, the UE 101 can configure the CSI report by performing a CSI compression operation to reduce the payload of the CSI report transmission. The CSI report can comprise various reporting quantities that can be shared or common between the sTRP report portion and the mTRP report portion of the CSI report. These reporting quantities can include, for example, a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast resource block indicator (SSBRI), a rank indicator (RI), a precoding matrix indicator (PMI), and a layer indicator (L1). The CRI indicates to the gNB 111 which CSI-RS is preferred for transmission. The SSBRI indicates a preferred synchronization signal block (SSB) for CMR resource selection. Then, once the CMR resource is selected, the UE 101 can further configure how many layers are preferred by the RI and which digital precoder is preferred by the PMI in the CSI report. All of these reporting quantities can increase the payload of the CSI report, especially when the UE 101 reports both the sTRP and the mTRP. In the case of mTRP, the UE 101 must report what the UE's preferred configuration is for two or more TRPs (e.g., both TRP1 and TRP2). Thus, CSI compression can reduce the size of the CSI report by removing any redundant values ​​that may be duplicated or common within the complete CSI report. For example, the UE 101 may prefer the same CRI for both the sTRP and the mTRP. For example, the UE 101 may indicate to the gNB 111 that it prefers the same resources from the first TRP regardless of whether an sTRP or an mTRP is being reported. Another example is that the UE 101 may prefer the same PMI. Thus, the UE 101 will prefer the precoding matrix from the first TRP regardless of whether there is an sTRP or an mTRP transmission. Thus, the UE 101 may be enabled to compress its CSI overhead.In this case, some values / variables do not need to be reported twice as part of different reporting quantity values ​​by the UE 101 configured to perform CSI compression of the CSI report. Thus, CSI compression can allow one or more of the reporting quantities to be shared and compressed between the sTRP and the mTRP in a single CSI report, for example, to reduce overhead.

[0116] Additionally or alternatively, the UE 101 can report whether the CSI report utilizes CSI compression. For example, the UE 101 can indicate in the CSI report whether the reporting amount is shared between different TRP, sTRP, or mTRP operations and therefore not reported twice. The UE preference for the reporting amount may be determined primarily based on the channel or channel quality, for example, regarding whether the UE 101 compresses or shares a CRI or PMI. Thus, the UE 101 can configure a field or flag in the CSI report to indicate to the gNB 111 that the same PMI or CRI is being reported for the sTRP and the mTRP. The UE 101 will then report only one of the PMIs for one TRP and will not report the PMI twice, or the UE can set a different flag to report the same CRI so that the gNB 111 does not need to decode another CRI in the CSI report, for example.

[0117] Although the methods described within this disclosure are illustrated and described herein as a series of acts or events, it is understood that the illustrated order of such acts or events is not to be construed in a limiting sense. For example, some acts may occur in a different order and / or concurrently with other acts or events other than those illustrated and / or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the description herein. Furthermore, one or more of the acts shown herein may be performed in one or more separate acts and / or phases. For ease of explanation, reference may be made to the above figures. However, these methods are not limited to any particular embodiments, aspects, or examples provided within this disclosure and may be applied to any of the systems / devices / components disclosed herein.

[0118] It is well understood that the use of personal information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personal information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users.

[0119] The present disclosure will now be described with reference to the accompanying drawings, wherein like reference numerals are used to refer to like elements throughout, and wherein the structures and devices depicted are not necessarily drawn to scale. As used herein, terms such as “component,” “system,” “interface,” and the like are intended to refer to computer-related entities, hardware, (e.g., executing) software, and / or firmware. For example, a component may 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 PC, and / or user equipment (e.g., a mobile phone) equipped with a processing device. Illustratively, an application running on a server and that server may also be a component. One or more components may reside within a process, and a component may be localized on one computer and / or distributed among two or more computers. This specification may describe a set of elements or other components, where the term “set” may be interpreted as “one or more.”

[0120] Further, these components may execute, e.g., as modules, from various computer-readable storage media having various data structures stored thereon. Components may communicate, for example, via local and / or remote processes, pursuant to signals comprising one or more data packets (e.g., data from a component interacting with another component via signals in a local system, a distributed system, and / or across a network, e.g., the Internet, a local area network, a wide area network, or a similar network with other systems).

[0121] As another example, a component may be a device having particular functionality provided by mechanical parts operated by electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by software or firmware applications executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware applications. As yet another example, a component may be a device that provides particular functionality through electronic components without mechanical parts, where the electronic components may comprise one or more processors that execute software and / or firmware that at least partially impart the functionality of the electronic components.

[0122] The use of the word "exemplary" is intended to make a concept concrete. The term "or" as used herein is intended to mean an inclusive "or," not an exclusive "or." That is, unless otherwise specified or clear from the context, "X uses A or B" is intended to mean any of all possible permutations. That is, "X uses A," "X uses B," or "X uses both A and B" all satisfy "X uses A or B." Additionally, the articles "a" and "an," as used in this application and the appended claims, should generally be interpreted to mean "one or more" unless otherwise specified or clear from the context to refer to the singular form. Furthermore, when "including," "includes," "having," "has," "with," or variations thereof are used in either the detailed description or the claims, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, in situations where one or more numbered items are recited (e.g., "first X," "second X," etc.), in some situations the context may indicate that one or more numbered items are separate or the same, but in general these one or more numbered items may be separate or the same.

[0123] As used herein, the term "circuitry" refers to, can be a part of, or can include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or associated memory (shared, dedicated, or group) operably coupled to a circuit that executes one or more software or firmware programs, a combinatorial logic circuit, or other suitable hardware component that provides the described functionality. In some embodiments, a circuit may be implemented in, or functions associated with, one or more software or firmware modules may be performed by, one or more software or firmware modules. In some embodiments, a circuit may include logic operable at least partially in hardware.

[0124] As used herein, the term "processor" can refer to virtually any computing processing unit or device, including, but not limited to, a single-core processor, a single processor with software multithreading execution capabilities, a multi-core processor, a multi-core processor with software multithreading execution capabilities, a multi-core processor with hardware multithreading technology, a parallel platform, and a parallel platform with distributed shared memory. Furthermore, a processor can refer to an integrated circuit, an application-specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a 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. A processor can utilize nanoscale architectures, including, but not limited to, molecular dot and quantum dot-based transistors, switches, and gates, etc., to optimize space usage or improve mobile device performance. A processor can also be implemented as a combination of computing processing units.

[0125] Examples (embodiments) may include subject matter such as a method, means for performing an operation or block of a method, at least one machine-readable medium containing 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 the operation of the method or the operation of an apparatus or system to perform simultaneous communications using multiple communication technologies according to the embodiments and examples described herein.

[0126] A first example may be a user equipment (UE) comprising: a memory; and a processing circuit configured to receive a radio resource control (RRC) message having a CSI report configuration corresponding to a channel state information (CSI) report based on a single transmit / receive point (sTRP) operation and a multiple TRP (mTRP) operation; and generate a CSI report based on the CSI report configuration and a plurality of CSI report priority variables associated with measurements for the sTRP operation and measurements for the mTRP operation.

[0127] A second embodiment may include the first embodiment, wherein the processing circuitry is further configured to generate the CSI report based on a CSI report priority variable associated with measurements for sTRP operations having a higher or lower priority than measurements for mTRP operations.

[0128] A third example may include the first or second example, wherein the processing circuitry is further configured to: divide the CSI into a plurality of CSI portions associated with different priorities for the CSI report; and, in response to the CSI report configuration configuring more CSI processing units (CPUs) than associated UE capabilities for the CSI report, omit updating one or more of the plurality of CSI portions from the CSI report based on the different priorities.

[0129] A fourth example may include any one or more of the first to third examples, wherein the processing circuitry is further configured to: divide the CSI into a plurality of CSI portions associated with different priorities for the CSI report; determine whether the different priorities of the plurality of CSI portions affect CSI multiplexing and uplink control information (UCI) omission; and omit one or more CSI portions of the plurality of CSI portions from the CSI report based on the different priorities in response to one or more of the different priorities of the plurality of CSI portions affect the CSI multiplexing and UCI omission such that the total CSI exceeds a payload of a physical channel transmission for the CSI report.

[0130] A fifth example may include any one or more of the first to fourth examples, wherein the processing circuitry is further configured to determine whether to transmit the multiple CSI portions in the CSI report or to omit the multiple CSI portions from the CSI report in response to different priorities of the multiple CSI portions not affecting the CSI multiplexing and the UCI omission and the total CSI exceeding a payload of a physical channel transmission for the CSI report.

[0131] A sixth example may include any one or more of the first to fifth examples, wherein the processing circuit is further configured to generate the CSI report by dividing different CSI report measurements of the corresponding CSI into multiple CSI sub-reports having the same priority by ordering multiple CSI sub-reports in a concatenated sequence for the CSI report and ordering the different CSI report measurements of the corresponding CSI based on a first association with an sTRP operation and a second association with an mTRP operation within the multiple CSI sub-reports in the concatenated sequence, or by concatenating different CSI report measurements of the corresponding CSI based on a first association with an sTRP operation and a second association with an mTRP operation and concatenating multiple CSI sub-reports within the different CSI report measurements of the corresponding CSI ordered based on the first association or the second association.

[0132] A seventh embodiment may include any one or more of the first to sixth embodiments, wherein the processing circuitry is further configured to receive a medium access control (MAC) control element (MAC-CE) to dynamically modify channel management resources (CMRs) of the CSI report configuration, wherein the MAC-CE includes a CSI report configuration ID, a serving cell index, and one or more selections of the number of CSI resources for sTRP measurements and the number of CSI resource pairs configured for mTRP measurements.

[0133] An eighth embodiment may include any one or more of the first to seventh embodiments, wherein the MAC-CE includes a bitmap indicating which reference signals are deactivated or activated for measurements in the CSI report, the number of CSI resources for sTRP measurements includes a maximum number of CSI resources for sTRP measurements from a superset of resources in the CSI report configuration, and the number of CSI resource pairs configured for mTRP measurements includes a maximum number of CSI resource pairs from the superset of resources.

[0134] A ninth embodiment may include any one or more of the first to eighth embodiments, wherein the MAC-CE includes: a first number of first resources in a priority order of a first set of resources to select for sTRP measurement of a first TRP; a second number of first resources in a priority order of a second set of resources for sTRP measurement of a second TRP; and a third number of first resources in a priority order of a number of CSI resource pairs for mTRP measurement.

[0135] A tenth example may include any one or more of the first to ninth examples, wherein the processing circuitry is further configured to activate or deactivate corresponding CSI-Interference Measurement (CSI-IM) resources based on a one-to-one mapping of the CSI report configuration to the CMR as modified via the MAC-CE.

[0136] An eleventh embodiment may include any one or more of the first to tenth embodiments, wherein the processing circuitry is further configured to receive a MAC-CE for dynamically modifying a CMR of the CSI report configuration, wherein the MAC-CE includes a CSI report configuration ID, a serving cell index, and one or more instructions for modifying reporting of the CSI report using only sTRP testing, only mTRP testing, or both sTRP testing and mTRP testing.

[0137] A twelfth embodiment may include any one or more of the first to eleventh embodiments, wherein the processing circuitry is further configured to generate the CSI report using CSI compression such that one or more report quantities of the sTRP operation that are shared or common with one or more report quantities of the mTRP operation are reported only once in the CSI report, and the one or more report quantities include one or more of a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast resource block indicator (SSBRI), a rank indicator (RI), a precoding matrix indicator (PMI), or a layer indicator (LI).

[0138] A thirteenth embodiment may include any one or more of the first to twelfth embodiments, wherein the processing circuitry is further configured to provide an indicator of CSI compression corresponding to one or more reporting quantities in the CSI report.

[0139] A fourteenth example may be a baseband processor comprising: a memory; and a processing circuit configured to receive a radio resource control (RRC) message having a CSI report configuration that enables channel state information (CSI) reporting based on single transmit / receive point (sTRP) operation and multiple TRP (mTRP) operation, and to transmit a CSI report using measurements of the sTRP operation and the mTRP operation based on the CSI report configuration.

[0140] A fifteenth example may include the fourteenth example, in which the processing circuitry is further configured to generate the CSI report based on a plurality of weighted CSI report priority variables, wherein the plurality of weighted CSI report priority variables include a measurement associated with an sTRP operation, a measurement associated with an mTRP operation, a report type, a report amount, a serving cell index, and a report configuration ID.

[0141] A sixteenth embodiment may include any one or more of the fourteenth to fifteenth embodiments, wherein the processing circuitry is further configured to configure measurements associated with sTRP operations with a different priority than measurements associated with mTRP operations.

[0142] A seventeenth embodiment may include any one or more of the fourteenth to sixteenth embodiments, wherein the processing circuitry is further configured to: divide the CSI into a plurality of CSI portions associated with priorities for the CSI report; determine whether one or more of the priorities affect CSI multiplexing and uplink control information (UCI) omission; and omit one or more CSI portions of the plurality of CSI portions from the CSI report based on the priorities in response to the one or more of the priorities affecting the CSI multiplexing and UCI omission and the total CSI exceeding a payload amount of a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) for the CSI report.

[0143] An eighteenth embodiment may include any one or more of the fourteenth to seventeenth embodiments, wherein the processing circuitry is further configured to: divide the CSI into a plurality of CSI portions associated with priorities for the CSI report; and, in response to one or more of a CSI processing unit (CPU) overbooking process for the CSI report and the priorities that do not affect the CSI processing unit exceed a UE capability for physical channel transmission of the CSI report, perform measurements on all of the plurality of CSI portions for the CSI report or perform measurements on none of the plurality of CSI portions for the CSI report.

[0144] A 19th example may include any one or more of the 14th to 18th examples, wherein the processing circuit is further configured to generate a CSI report for measurements of both the sTRP operation and the mTRP operation by dividing different CSI measurement reports for the corresponding CSI into multiple CSI parts having the same priority by multiplexing mTRP measurements and sTRP measurements in different CSI measurement reports for the corresponding CSI and concatenating the different CSI measurement reports into a CSI report, or by concatenating multiple CSI parts associated with the sTRP operation, concatenating the multiple CSI parts associated with the mTRP operation, and ordering the multiple CSI parts associated with the sTRP operation and the multiple CSI parts associated with the mTRP operation based on the different CSI measurement reports for the corresponding CSI in the CSI report.

[0145] A twentieth embodiment is a base station comprising: a memory; and a processing circuit configured to: transmit a radio resource control (RRC) message having a CSI report configuration that enables channel state information (CSI) reporting based on single transmit / receive point (sTRP) operation and multiple TRP (mTRP) operation; and receive a CSI report using measurements of the sTRP operation and the mTRP operation based on the CSI report configuration.

[0146] A twenty-first example may include the twentieth example, wherein the CSI report is based on a plurality of weighted CSI report priority variables, the plurality of weighted CSI report priority variables including a measurement associated with an sTRP operation, a measurement associated with an mTRP operation, a report type, a report amount, a serving cell index, and a report configuration ID, and the measurement associated with the sTRP operation is configured with a different priority than the measurement associated with the mTRP operation.

[0147] A 22nd embodiment may include any one or more of the 20th to 21st embodiments, and the processing circuitry is further configured to send a Medium Access Control (MAC) Control Element (MAC-CE) to dynamically update a Channel Management Resource (CMR) of the CSI report configuration, wherein the MAC-CE includes a CSI report configuration ID, a serving cell index, and one or more selections of the number of CSI resources for sTRP measurements and the number of CSI resource pairs configured for mTRP measurements.

[0148] A 23rd embodiment may include any one or more of the 20th to 22nd embodiments, wherein the processing circuitry is further configured to activate or deactivate corresponding CSI-Interference Measurement (CSI-IM) resources of the CMR based on a one-to-one mapping of the CSI reporting configurations activated or deactivated via the MAC-CE in the bitmap to the CMR.

[0149] A 24th embodiment may include any one of the 20th to 23rd embodiments, wherein the processing circuit is further configured to send a MAC-CE to dynamically modify a CMR of the CSI reporting configuration, wherein the MAC-CE includes a CSI reporting configuration ID, a serving cell index, and one or more instructions to activate or deactivate reporting of an sTRP test, an mTRP test, or both the sTRP test and the mTRP test.

[0150] A twenty-fifth embodiment may include an apparatus comprising means for performing one or more elements of a method described or related to any of the first to twenty-first embodiments, or any other method or process described herein.

[0151] A twenty-sixth example may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of the first through twenty-first examples, or any other method or process described herein.

[0152] A twenty-seventh embodiment may include an apparatus having logic, modules, or circuitry for performing one or more elements of a method described in or related to any one of the first through twenty-first embodiments, or any other method or process described herein.

[0153] The twenty-eighth embodiment may include a method, technique, or process described in or related to any one of the first to twenty-first embodiments, or a portion or part thereof.

[0154] A 29th embodiment may include an apparatus comprising one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of the first to twenty-first embodiments, or a portion thereof.

[0155] The 30th embodiment may include a signal according to any one of the first to twenty-ninth embodiments or a signal related thereto, or a part or portion thereof.

[0156] A thirty-first embodiment may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or relating to any one of the first through twenty-first embodiments or a portion or part thereof, or as described in the present disclosure.

[0157] A thirty-second example may include a signal encoded with data as described in or related to any one of the first to twenty-first examples or parts or portions thereof, or as described in this disclosure.

[0158] A thirty-third embodiment may include a signal encoded using a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any one of the first through twenty-first embodiments or a portion or part thereof, or as described in the present disclosure.

[0159] A thirty-fourth embodiment can include an electromagnetic signal carrying computer-readable instructions that cause one or more processors to perform a method, technique, or process described in or related to any one of the first through twenty-first embodiments or portions thereof, where the execution of the computer-readable instructions by one or more processors can include an electromagnetic signal carrying the computer-readable instructions that cause the one or more processors to perform a method, technique, or process described in or related to any one of the first through twenty-first embodiments or portions thereof.

[0160] A thirty-fifth embodiment may include a computer program having instructions such that execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of the first to twenty-first embodiments or portions thereof.

[0161] A thirty-sixth embodiment may include a signal in a wireless network as shown and described herein.

[0162] A thirty-seventh embodiment may include a method of communicating in a wireless network as shown and described herein.

[0163] A thirty-eighth embodiment may include a system for providing wireless communication as shown and described herein.

[0164] A thirty-ninth embodiment may include a device that provides wireless communication as shown and described herein.

[0165] Furthermore, various aspects or features described herein may be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture," as used herein, is intended to encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, etc.), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., EPROMs, cards, sticks, key drives, etc.). Furthermore, 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 instruction(s) and / or data. Furthermore, a computer program product may include a computer-readable medium having one or more instructions or code operable to cause a computer to perform the functions described herein.

[0166] Communication media includes computer-readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal, e.g., carrier wave or other transport mechanism, and includes any information delivery or transport medium. A "modulated data signal" or signals refers to a signal that has one or more characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0167] An exemplary storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. Further, in some aspects, the processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in some aspects, the processes and / or operations of a method or algorithm may reside as one or any combination of codes and / or instructions on a machine-readable medium and / or computer-readable medium, which may be incorporated into a computer program product.

[0168] In this regard, although the disclosed subject matter has been described in connection with various embodiments and corresponding drawings, it should be understood that, where applicable, other similar embodiments can be used to perform the same, similar, alternative, or substitute functions of the disclosed subject matter, or modifications and additions can be made without departing from the described embodiments. Accordingly, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed according to the breadth and scope of the following appended claims.

[0169] In particular, with regard to the various functions performed by the above-described components (assemblies, devices, circuits, systems, etc.), the terms used to describe such components (including references to "means") are intended to correspond to any component or structure that performs the specified function of the described component (e.g., that is functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs that function in the exemplary implementations of the present disclosure shown herein. Furthermore, while a particular feature may be disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of other implementations, as may be desirable or advantageous for any given or particular application.

Claims

1. A user equipment (UE), a radio frequency (RF) circuit; Memory and a processing circuit that, when executing instructions stored in the memory, causes the UE to: receiving a radio resource control (RRC) message having a channel state information (CSI) report configuration corresponding to a CSI report based on a single transmit / receive point (sTRP) operation and a multiple TRP (mTRP) operation; generating CSI having a plurality of CSI portions based on the sTRP operation and the mTRP operation, each CSI portion having a different priority; determining that the priorities of the plurality of CSI portions affect CSI processing unit (CPU) overbooking for the CSI report; In response to the determining, generating the CSI report by independently omitting one or more CSI portions from the plurality of CSI portions based on the priorities of the plurality of CSI portions; transmitting the CSI report via the RF circuitry. A user equipment (UE) configured to:

2. The processing circuitry may further include:

2. The UE of claim 1, configured to generate the CSI report based on a CSI report priority variable associated with a measurement for the sTRP operation that has a higher priority than a CSI report priority variable associated with a measurement for the mTRP operation.

3. The processing circuitry may further include: determining whether the different priorities of the plurality of CSI portions affect CSI multiplexing and uplink control information (UCI) omission; 2. The UE of claim 1, wherein one or more of the different priorities of the plurality of CSI portions affect the CSI multiplexing and the UCI omission, and wherein, in response to a total CSI exceeding a payload of a physical channel transmission for the CSI report, one or more CSI portions among the plurality of CSI portions are omission based on the different priorities of the plurality of CSI portions.

4. The processing circuitry may further include:

4. The UE of claim 3, wherein the different priorities of the plurality of CSI parts do not affect the CSI multiplexing and the UCI omission, and the UE is configured to determine whether to transmit the plurality of CSI parts in the CSI report or to omit the plurality of CSI parts from the CSI report depending on whether the total CSI exceeds the payload of the physical channel transmission for the CSI report.

5. The processing circuitry may further include:

2. The UE of claim 1, configured to receive a medium access control (MAC) control element (MAC-CE) to dynamically modify one or more channel measurement resources (CMRs) of the CSI report configuration, the MAC-CE including a CSI report configuration ID, a serving cell index, and one or more selections of a number of CSI resources for sTRP measurements and a number of CSI resource pairs configured for mTRP measurements.

6. 6. The UE of claim 5, wherein the MAC-CE further includes a bitmap indicating which reference signals are deactivated or activated for measurements in the CSI report, the number of CSI resources for sTRP measurements includes a maximum number of CSI resources for sTRP measurements from a superset of resources in the CSI report configuration, and the number of pairs of CSI resources configured for mTRP measurements includes a maximum number of pairs of CSI resources from the superset of resources.

7. 6. The UE of claim 5, wherein the MAC-CE includes the number of resources in a first set of resources to select for sTRP measurement of a first TRP, the number of resources in a second set of resources to select for sTRP measurement of a second TRP, and the number of resource pairs in a set of resource pairs to select for mTRP measurement, and the resources in the first set of resources, the second set of resources, and the set of resource pairs are arranged in order of priority.

8. The processing circuitry may further include:

6. The UE of claim 5, configured to activate or deactivate corresponding CSI-Interference Measurement (CSI-IM) resources based on a one-to-one mapping of the CSI reporting configuration to the CMR modified via the MAC-CE.

9. The processing circuitry may further include:

2. The UE of claim 1, configured to receive a medium access control (MAC) control element (MAC-CE) to dynamically modify a channel measurement resource (CMR) of the CSI report configuration, the MAC-CE including a CSI report configuration ID, a serving cell index, and one or more instructions for modifying reporting of the CSI report using only sTRP testing, only mTRP testing, or both sTRP testing and mTRP testing.

10. The processing circuitry may further include:

2. The UE of claim 1, wherein the UE is configured to generate the CSI report using CSI compression such that one or more report quantities of the sTRP operation that are shared or common with one or more report quantities of the mTRP operation are reported only once in the CSI report, wherein the one or more report quantities include one or more of a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast resource block indicator (SSBRI), a rank indicator (RI), a precoding matrix indicator (PMI), or a layer indicator (LI).

11. The processing circuitry may further include: The UE of claim 10 , configured to cause an indicator of CSI compression corresponding to the one or more reporting amounts in the CSI report to be provided in the CSI report.

12. 1. A baseband processor that, when executing instructions stored in a memory, Receiving a radio resource control (RRC) message having a channel state information (CSI) report configuration for a CSI report based on a single transmission / reception point (sTRP) operation and a multiple TRP (mTRP) operation; generating CSI having multiple CSI portions, each CSI portion having a different priority, based on the sTRP operation and the mTRP operation; determining that the priorities of the plurality of CSI portions affect CSI processing unit (CPU) overbooking for the CSI report; generating the CSI report by independently omitting one or more CSI portions from the plurality of CSI portions based on the priorities of the plurality of CSI portions in response to the determining; providing the CSI report to a radio frequency (RF) interface for transmission; a baseband processor configured to perform operations including:

13. The operation further comprises:

13. The baseband processor of claim 12, further comprising: generating the CSI report based on a plurality of weighted CSI report priority variables, the plurality of weighted CSI report priority variables including an association of the sTRP operation or the mTRP operation with a measurement, a report type, a report amount, a serving cell index, and a report configuration ID.

14. The operation further comprises: The baseband processor of claim 12 , further comprising configuring measurements associated with the sTRP operations with a different priority than measurements associated with the mTRP operations.

15. The operation further comprises: determining the priorities of the plurality of CSI portions affect CSI multiplexing and uplink control information (UCI) omission; omitting one or more CSI parts among the plurality of CSI parts based on the priority of the plurality of CSI parts in response to the priority of the plurality of CSI parts affecting the CSI multiplexing and the UCI omission, and a total CSI exceeding a payload amount of a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) for the CSI report.

Images