WO2022031487A1 - Channel state information accuracy in nr urllc - Google Patents

Abstract

An apparatus and system to provide channel state information (CSI) in Ultra-Reliable and Low Latency Communications (URLLC) are described. A CSI report configuration that contains information to measure channel state information reference signals (CSI-RS) is provided to a UE. A PDCCH contains downlink assignment DCI that contains, for an aperiodic CSI, a field to request the CSI. The UE measures the CSI and provides a CSI report that contains the CSI on a PUCCH or a PUSCH. The CSI report is multiplexed and the individual CSI reports prioritized such that part 2 contains prioritized multiplexed CSI reports and CSI part 1 includes indexing of the prioritized multiplexed CSI reports.

Description

CHANNEL STATE INFORMATION ACCURACY IN NR URLLC PRIORITY CLAIM

[0001] This application claims the benefit of pri ority to United States

Provisional Patent Application Serial No. 63/063,085, filed August 7, 2020, which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments pertain to fifth generation (5G) wireless communications. In particular, some embodiments relate to Ultra-Reliable and Low Latency Communications (URLLC) in 5G systems. BACKGROUND

[0003] The use and complexity of wireless systems, which include 4^th generation (4G) and 5^th generation (5G) networks among others, has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, especially with the advent of next generation (NG) (or new⁷ radio (NR) systems). As expected, a number of issues abound with the advent of any new technology, including increasing energy efficiency in user equipments (UEs).

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. lake numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1A illustrates an architecture of a network, in accordance with some aspects. [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. IC illustrates a non-roaming 5G system architecture in accordance with some aspects. [0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates a method of providing channel state information (CSI) feedback in accordance with some embodiments. DETAILED DESCRIPTION

[0010] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0011] FIG. I A illustrates an architecture of a network in accordance with some aspects. The network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function can be implemented as a. discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure. [0012] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein. [0013] Any of the radio links described herein (e.g., as used in the network 140A or any other illustrated network) may operate according to arty exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0014] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for Sow-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs. [0015] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. [0016] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, 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 System (UNITS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0017] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising 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), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0018] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). [0019] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes I l l and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The

RAN 1 10 may include one or more RAN nodes for providing macrocells, e.g.. macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0020] Arty of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill 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. In an example, any of the nodes 111 and/or 1 12 can be a gNB, an eNB, or another type of RAN node.

[0021] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the S I interface 113 is split into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 1 1 1 and 112 and MMEs 121.

[0022] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/ addressing resolution, location dependencies, etc. [0023] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the ILAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0024] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application sewer 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 13 LA, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application sewer 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0025] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0026] In some aspects, the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new⁷ radio network using communications in the licensed (5GNR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrowband-loT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0027] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core networl</5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via .Xn interfaces. [0028] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge sewer, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0029] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication with RAN 1 10 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SME) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)Zhome subscriber server (HSS) 146.

[0030] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy.

The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0031] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network.

The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system). [0032] The AF 150 may provide information on the packet flow to the

PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0033] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).

More specifically, the IMS 168B includes a CSCF, which can act. as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.

The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0034] In some aspects, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0035] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 1 10 and the AMF 132), N3 (between the RAN 1 10 and the UPF 134), N4 (between the SAIF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the

AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. 1 C can also be used.

[0036] FIG. 1C illustrates a 5G system architecture 140C and a service- based representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G sy stem architectures can be sendee-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0037] In some aspects, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following servicebased interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a sendee-based interface exhibited by the SMI 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a senice-based interface exhibited by the PCF 148), a Nudm 158E (a servicebased interface exhibited by the UDM 146), Naf 158F (a sendee-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a sendee-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other sendee-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0038] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0039] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet

PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity. [0040] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system ) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0041] Accordingly, the term “module” (and “component'’) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general -purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0042] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory' 204 and a static memory? 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and Ul navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0043] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instractions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instractions 224.

[0044] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instractions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instractions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory' devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM): and CD-ROM and DVD-ROM disks.

[0045] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks). Plain

Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802, 16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium 226.

[0046] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory' (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry'” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic sy stem) with the program code used to carry' out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0047] The term ‘‘processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry’” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[0048] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile Telecommunications Sy stem (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 1 1), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3 GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel.

15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel, 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.

19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS ( 1 G )), Total Access Communication SystemZExtended Total Access Communication System (TACS/ETACS), Digital /AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (I MTS). Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (I heap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WIDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. 1 lad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (VOX) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short. Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European 1TS-G5 system (i.e. the European flavor of IEEE 802. 1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range

5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

^0049^ Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2,4 GHz, 3.4-3.6 GHz, 3, 6-3, 8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - .3800 MHz, .3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio

Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz. (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC’s "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61 .56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit

Wireless Systems (MGWS)ZWiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary' basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0050] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g. by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g. with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0051] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0052] Some of the features in this document are defined for the network side, such as APs, eNBs, NR or gNBs --- note that this term is typically used in the context of 3GPP fifth generation (5G) communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0053] Enhancement of new radio (NR) technology to support ultrareliable low-latency communication (URLLC) in industrial internet of things scenarios (HOT) is one of the issues addressed in Release 17. In particular, enhancing channel state information (CSI) feedback in URLLC/IIOT may be used for more accurate modulation and coding scheme (MCS) selection in the target scenarios. Channel state information reference signals (CSI-RS) sent by the gNB are measured by the UE, and a CSI report responsive to the measurements is transmitted by the UE to the gNB. The CSI measurements are used to provide channel estimation and coherent demodulation, for example, for channel -dependent scheduling, link adaptation, and transmission settings related to multi-antenna transmission.

[0054] The gNB may provide a CSI-RS configuration for the CSI-RS to be transmitted. The CSI-RS configuration specifies the number of CSI-RS, the CSI-RS periodicity, the CSI-RS subframe offset within the CSI-RS period, and the CSI-RS configuration within a resource-block pair (which resource elements from the possible resource elements are to be used)

[0055] It should be noted that link adaptation for URLLC use cases has its own specifics. In many scenarios, the URLLC data transmissions are relatively small and transmitted using single transport block. This creates a large variation in terms of interference statistics when a given transmission point changes allocation parameters and presence of data frequently because in every time occasion a new transmission may be transmitted for a new user. This situation is different from typical Enhanced Mobile Broadband (eMBB) scenarios in which the packets for transmission are relatively large and are transmitted using multiple transport blocks and therefore slots. In classical eMBB assumptions, the channel state measured in the beginning of the DL session is usually applied for upcoming transport blocks with possible outer loop adjustment based on Hybrid Automatic Repeat Request (HARQ) acknowledgements. Outer loop adjustment is used to adjust a signal -to-noise ratio threshold that is updated online based on feedback representing the accuracy of the transmission to provide a predetermined average block error rate (BLER). In particular, a correction term is generated that is the accumulation of predefined steps dependent on whether a HARQ acknowledgement (ACK) (increase) or NACK (decrease) is received from the UE.

[0056] However, for URLLC/IIOT scenarios with bursty interference, the classical link adaptation assumption may not work well because there may be not enough time to measure the channel after the packet is triggered, the measurement performed in one slot may not be accurate if applied to another slot, and there may be no chance to apply outer-loop link adaptation mechanism, since even⁷ negative acknowledgement can contribute to the latency.

[0057] Under these assumptions, enhancements to the CSI framework to overcome the above issues associated with the link adaptation and CSI framework in URL.LC may involve a number of actions. These actions may include, for example, aperiodic CSI (A-CSI) multiplexing on a physical uplink control channel (PUCCH) triggered by a downlink (DL) assignment, using a CSI report measurements filtering/averaging configuration, using a UE-based CSI report content prioritization, and using compact reporting for two Channel Quality Indicator (CQI ) tables.

[0058] A-CSI OH PUCCH

[0059] Currently NR specification supports several modes for CSI reporting: periodic CSI on a PUCCH, semi -persistent CSI on a PUCCH, a semi- persistent CSI on a physical uplink shared channel (PUSCH), aperiodic CSI on a PUSCH.

[0060] The reporting on PUCCH may not be able to cany many information bits. For example, periodic CSI can only be wideband, for a Type 1 codebook, with a limited number of ports, etc. At the same time, aperiodic CSI on a PUSCH has a specific physical structure with flexible payload and can carry up to hundreds of bits. Aperiodic CSI can support both sub-band and wideband granularity for both a Type 1 or Type 2 codebook, etc. Furthermore, the A-CSI on the PUSCH can only be triggered by an uplink (UL) grant downlink control information (DCI) 0_1 or 0_2. In some case, A-CSI may be better to be triggered by a DL assignment DCI or a group common DCI, since UL grant usage may introduce extra overhead if there is no active UL transmission. [0061] In one embodiment, the A-CSI may be requested by a DCI carrying a DL assignment, e.g. DCI format l_0, 1_1, and 1_2. A new radio resource control (RRC) information message or a flag in the existing message may be added to enable or disable an A-CSI request in a DL assignment. This may be separately configured per DCI format, e.g. separate activation of the A- CSI request on the PUCCH capability for DCI format 1_1 and 1__2.

[0062] The following components may be used to support the concept of an A-CSI on a PUCCH requested by a DL assignment:

[0063] A “CSI request” field is added at least into DCI formats 1_1 and

1 2, The presence of “CSI request” field may be conditional to the higher layer configuration of the A-CSI by DL assignment feature. Optionally, the “CSI request” field can be added to the DCI format 1 0. The field may be of size 0, 1, 2, 3, 4, or 6 bits, whose specific value is indicated by a RRC parameter reportTriggerSize . The procedure of decoding and interpretation of this field may be fully reused from that in the DCI formats 0__l and 0_2. [0064] A PUCCH resource for A-CSI may be indicated in DCI formats

1_1 and 1_2 using a combination of PUCCH resource indication and a slot or sub-slot offset indicated by PDSCH-to-HARQ feedback indicator.

[0065] A PUCCH resource indication can be provided using one of the following. In one example, the PUCCH resource and the time gap to the resource for CSI mapping follows the PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of TS 38.213 signaled for HARQ-ACK. In another example, a separate PUCCH resource indication may be added into the payload of DCI formats 1_1 and 1_2 (optionally for l__0 as well). The PUCCH resource indication may not be present, if the A-CSI reporting on the PUCCH is disabled. If present, the size of the field may depend on higher layer configuration or may be fixed in specification. For example, the size of the field can be 0, 1, 2, or 3 bits depending on higher layer configuration. The higher layer configuration may convey a table of addressed PUCCH configurations, and the size of the table may define the size of the corresponding bitfield in the DCI. [0066] A slot and/or symbol offset to the PUCCH resource for A-CSI may be indicated in DCI formats 1_1 and 1_2 using one of the following examples. In one example, the time gap to the HARQ-ACK feedback indicated in a PDSCH-to-HARQ feedback timing indicator - 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of TS 38.213 may be reused as a time gap for A-CSI. In another example, a new PDCCH-to-CSI-Report slot and/or symbol offset between the end of request DCI slot (or the last symbol carrying the request DCI) and the start of CSI report, slot (or the first symbol carrying the CSI report) may be added into the payload of DCI formats 1 1 and 1 2 (optionally to 1 0 as well). A higher layer table may be separately provided by an RRC message with the possible slot or symbol offset values; the index of the particular entry' in the table may be signaled in the DCI field. In this case, the size of the DCI field may be calculated from the table size as ceiling(log2(‘^tnumber of entries in the table”)). The table may be separately provided for different DCI formats 1 1 and 1_2 (optionally l_0) and may have independent sizes. In case of collision with a PUSCH, the PUCCH can be multiplexed following the rules for a PUCCH with P/SP-CSI.

[0067] CSI report measurements filtering/averaging [0068] Another potential source of more accurate CSI measurements and reporting is to let a UE to apply additional processing over the reporting hypotheses provided by the gNB.

[0069] It may be shown that in the bursty interference case if no coordination is assumed, an instantaneous measurement in one environment may not be applicable to another environment. One situation is when a presence of an interferer is missed in the CSI report, but when a transmission is again scheduled and overlaps with the resource that is also utilized by the interferer. In this case, filtering and/or averaging may be used to account for strong interference. [0070] In one embodiment, a CSI report configuration may be extended with an additional filtering/averaging enabling flag. If the flag is enabled, the UE is expected to apply the filtering/averaging over a set number of CSI-RS resources. The number of CSI-RS resources used for filtering/averaging may be also provided as part of CSI report configuration and may be optionally present. [0071] In relation to the above embodiment, the filtering may employ a liner average over channel amplitudes measured on CSI-RS for channel and/or for interference. Alternatively, a filter emphasizing larger interference measurements may be applied, e.g. a maximum interference from the interference measurements on multiple occasions of CSI-RS IM. The multiple occasions of CSI-RS and/or CSI-IM may be defined as those that fall within a configured time-window with respect to the reporting instance.

[0072] UE-based CSI report content prioritization [0073] The CSI report may measure as many hypotheses as possible with the smallest granularity (e.g. sub-band size) as possible. This approach may be problematic as processing of such a report can be quite complex and can take long time, as well as the payload of such a report being large, thus creating issues with overhead and reliability of the reporting itself. [0074] An appropriate composition of the reported measurement based on thresholds, conditions, triggers can help to filter out the hypotheses which may not provide important information to the gNB scheduler. CSI report prioritization may be used for the parts earned on CSI part 2. CSI part 1 has a fixed payload size and is used to identify the number of information bits in part 2. A set of CSI reports that can be multiplexed has an associated priority calculated using semi-static rules, such as report index, cell index, etc.

Depending on the number of available resources for the CSI, the lower priority measurements may not be transmitted.

[0075] In one embodiment, for multiplexing/reporting of more than one CSI report in the same CSI part 1 and part 2, the priority of a report may be associated with the measurement result of one or multiple of the CSI report contents'. CQI, rank indicator (RI), Precoding Matrix Indicator (PMI), CSI Resource Indicator (CRI), layer indicator (LI), etc. If the prioritized report is going to be multiplexed on CSI part 1 and CSI part 2, then: in one example, CSI part 1 carries a “table of contents” for CSI part 2, where the CSI part 2 conveys the prioritized reports. The table may convey indexes of the reports which were prioritized for multiplexing. In another example, CSI part 1 carries a “table of contents” and a part of the prioritized CSI reports, while the CSI part 2 conveys the rest of the content of the prioritized CSI reports. [0076] Related to the above embodiment, a threshold to decide the priority of a report and/or to directly include the priority into the CSI channel may be provided by an RRC message as part of the CSI reporting configuration. For example, a CQI threshold CQI T and RI threshold R_T may be configured, and if the measured CQI is lower than the threshold CQI T, and/or the measured

RI is lower than the threshold RI_T, the corresponding CSI report is prioritized for multiplexing. Alternatively, one or more CQI thresholds may be configured, each conditioned on a configured or specified hypothesis on the rank. In another set of examples, the measurement may be prioritized when the corresponding measurement is above the threshold. Furthermore, whether the measurements are prioritized if above the threshold or below the threshold may be configurable per CSI report configuration.

[0077] Alternatively, an interference Reference Signal Received Power (RSRP), receive (RX) power, interference noise ratio (INR), or loT or other interference measure related threshold may be configured and compared with the measurement on CSI-RS IM for a given CSI report in order to decide whether to multiplex the report or not.

[0078] In one embodiment, the dynamic prioritization described above may be applied to CSI carried on PUCCH using same mechanisms. [0079] In one embodiment, for a periodic CSI, if the difference in a measurement, for a given report in occasion ‘n’ and the measurement on the previous periodic occasion ^£n - P’ where the report was triggered is smaller than a ‘delta_measuremenf , then this periodic CSI report is deprioritized for multiplexing. That means if a periodic measurement is not sufficiently changed, it is omitted from the report,

[0080] Compact reporting for two CQI tables

[0081] In some cases, it is useful for the gNB to know⁷ the CQI for both a 10% BLER target and 0.001% BLER target. This can be achieved by configuring at least, two different CSI reports with different CQI tables. In such situations, the different CSI measurement configurations may be similar, for example, the CSI measurement configurations may differ only by the associated CQI table. In this context, it may be possible to further optimize the CSI computation time and reporting overhead if a single CSI report can be associated with two different tables.

[0082] In one embodiment, a second CQI table may be optionally configured for a CSI report configuration in CSI-ReportConfig, and the associated CSI report may carry additional information . The additional information may be carried, for instance, by extending the related bitfield, based on the second CQI table. The additional information may be one of the following: a second CQI associated with the second CQI table and a second RI associated with this CQI; a second CQI associated with the second CQI table under the assumption of the RI associated with the CQI of the first table; alternatively, the RI may be derived based on the second CQI and the first CQI is derived based on this RI; or a numerical difference (delta CQI) between the CQI of the first table and CQI calculated based on the second table, and RI is either separately indicated or associated with the first CQI or the second CQI. [0083] Related to the above embodiment, the CSI computation timeline may not be increased if a CSI report, is provided with the second CQI table. Alternatively, the CSI computation time may be increased by ^£c’ symbols, where ‘c’ may be 0, 1, 2, 3, 4, etc.

[0084] FIG. 3 illustrates a method of providing CSI feedback in accordance with some embodiments. Some embodiments may have additional operations. In the method 300, at operation 302 a gNB may transmit to the UE a CSI report configuration for the UE to report CSI in URLLC based on CSI-RS. At operation 304, the gNB may transmit, to the UE a PDCCH that contains DCI with a field to request transmission by the UE of the CSI. In response, at operation 306, the gNB may receive from the UE a CSI report that, contains the CSI on a PUCCH or a PUSCH.

[0085] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that, form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient, detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0086] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the ait upon reviewing the above description. [0087] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[0088] The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1 .72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of di sclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus for a 5^th generation NodeB (gNB), the apparatus comprising: processing circuitry configured to: encode, for transmission to a user equipment (UE), a channel state information (CSI) report configuration for the UE to report CSI in Ultra-Reliable and Low Latency Communications (URLLC) based on channel state information reference signals (CSI-RS); encode, for transmission to the UE, a physical downlink control channel (PDCCH) that contains downlink control information (DCI), the DCI containing a field to request an aperiodic CSI; and decode, from the UE, a CSI report that contains the CSI on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) in response to transmission of the DCI, and a memory configured to store the CSI report configuration.

2. The apparatus of claim 1, wherein: the DCI has DCI format 1 1 or 1 2 and carries a downlink assignment, and the field is a CSI request field.

3. The apparatus of claim 2, wherein: the CSI request field has a size of 0, 1, 2, 3, 4, or 6 bits, and the processing circuitry is further configured to encode, for transmission to the UE, a radi o resource control (RRC) parameter that, i ndi cates the size of the CSI request field.

4. The apparatus of claim I, wherein the processing circuitry is further configured to encode, for transmission to the UE, a radio resource control (RRC) message that activates aperiodic CSI triggered by downlink assignment, and whether the field is present is dependent on transmission of the RRC message.

5. The apparatus of claim 1, wherein the CSI report is carried on a same PUCCH resource as indicated for a Hybrid Automatic Repeat Request acknowledgement (HARQ-ACK) field and a PDSCH-to-HARQ slot offset field.

6. The apparatus of claim 1, wherein the CSI report is carried on a PUCCH resource indicated in the DCI, and a slot offset from the DCI to the PUCCH is indicated in the DCI.

7. The apparatus of claim 1, wherein the CSI report configuration comprises a filtering or averaging-enabling flag that indicates in response to the flag being enabled that the UE is to apply a filter or average over a predetermined number of CSI-RS resources.

8. The apparatus of claim 7, wherein the CSI report configuration further comprises the predetermined number of CSI-RS resources.

9. The apparatus of claim 7, wherein at least one of: the filter provides a liner average over channel amplitudes measured on CSI-RSs for at least one of channel or interference measurements, or the filter is applied to determine a maximum interference from the interference m easurements .

10. The apparatus of claim 1, wherein the processing circuitry is further configured to decode, from the UE, multiplexed CSI reports in a single CSI part 1 and CSI part 2, a priority of each multiplexed CSI report associated with a measurement result contained in the CSI report.

11 . The apparatus of claim 10, wherein the processing circuitry is further configured to encode, for transmission to the UE, a radio resource control (RRC) message containing a measurement threshold of per multiplexed CSI report or per CSI report quantity to determine the priorities.

12. The apparatus of claim 10, wherein the CSI part 2 contains prioritized multiplexed CSI reports and the CSI part 1 includes indexing of the prioritized multiplexed CSI reports.

13. The apparatus of claim 10, wherein a periodic CSI report that is multiplexed contains periodic measurements that have changed more than a predetermined threshold from an immediately previous periodic measurement.

14. The apparatus of claim 1, wherein: the CSI report configuration comprises a first and second Channel

Quality Indicator (CQI) table, and the CSI report contains information in an extension of a bitfield, based on the second CQI table, a second CQI level, a CQI level difference between a first CQI and a second CQI, and other CQI encoding schemes.

15. The apparatus of claim 14, wherein the processing circuitry is further configured to avoid an increase in a CSI computation timeline in response to the CSI report being provided with the second CQI table.

16. The apparatus of claim 1, wherein at least one of: a PUCCH resource and time gap to a resource for CSI mapping follows a PUCCH resource indicator or a PUCCH resource indication is in a payload of the DC I, or the PUCCH resource indication is not present in response to aperiodic CSI being disabled.

17. An apparatus for a user equipment (UE), the apparatus comprising: processing circuitry' configured to: decode, from a 5^th generation NodeB (gNB ), a channel state information (CSI) report configuration for the UE to report CSI in Ultra¬

Reliable and Low Latency Communications (URLLC) based on channel state information reference signals (CSI-RS); decode, from the gNB, a physical downlink control channel (PDCCH) that contains downlink control information (DCI), the DCI containing a field to request an aperiodic CSI; measure CSI-RS based on the DCI; and encode, for transmission to the gNB, a CSI report that contains the CSI on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) in response to transmission of the DCI; and a memory configured to store the CSI report configuration.

18. The apparatus of claim 17, wherein: the DCI has DCI format 1_1 or 1__2 and carries a downlink assignment, and the field is a CSI request field.

19. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a 5^th generation NodeB (gNB), the one or more processors to configure the gNB to, when the instructions are executed: encode, for transmission to a user equipment (UE), a channel state information (CSI) report configuration for the UE to report CSI in Ultra-Reliable and Low Latency Communications (URLLC) based on channel state information reference signals (CSI-RS); encode, for transmission to the UE, a physical downlink control channel (PDCCH) that contains downlink control information (DCI), the DCI being a downlink assignment DCI or group common DCI and containing a field to request the CSI in response to the CSI being aperiodic CSI; and decode, from the UE, a CSI report that contains the CSI on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) in response to transmission of the DCI.

20. The medium of claim 19, wherein: the one or more processors further configure the gNB to, when the instructions are executed encode, for transmission to the UE, a radio resource control (RRC) parameter that, indicates a size of the CSI request field, the DCI has DCI format l_0, 1_1, or 1_2, and the field is a CSI request field.