User Equipment (UE) and Base Station

Abstract

Various embodiments herein provide techniques related to CWI for a wideband and one or more subbands of the wideband. In an embodiment, a user equipment (UE) transmits a wideband channel quality index (CQI) report related to channel state information (CSI) for the wideband. The UE may further identify a number of bits to use for a subband CQI report related to one of the one or more subbands from a set of 2, 3, 4, and 5, and transmit the subband CQI report based on the identified number of bits. Other embodiments may be described and / or claimed.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority to U.S. Provisional Patent Application No. 63 / 230,274, filed on August 6, 2021; and U.S. Provisional Patent Application No. 63 / 251,524, filed on October 1, 2021.

[0002] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to channel state information (CSI) reporting.

Background Art

[0003] Various embodiments may generally relate to the field of wireless communication.

Brief Description of the Drawings

[0004] Embodiments are readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are shown by way of illustration and not limitation in the figures of the accompanying drawings.

Figure 1

[0005]

Figure 2

[0006]

Figure 3

[0007]

Figure 4

[0008]

Figure 5

[0009]

Figure 6

DETAILED DESCRIPTION OF THE INVENTION

[0010] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details such as specific structures, architectures, interfaces, techniques, etc. are set forth in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0011] Release 17 (Rel-17) of the 3rd Generation Partnership Project (3GPP (registered trademark)) specifications may include or be related to improvements to 5th Generation (5G) / New Radio (NR) technologies to better support Ultra-Reliable Low-Latency Communication (URLLC) in Industrial Internet of Things (IIoT) scenarios. This support for URLLC / IIoT may be related to extending Channel State Information (CSI) feedback for more accurate Modulation and Coding Scheme (MCS) selection in target scenarios. In some cases, link adaptation for URLLC use cases may have its own specific considerations as follows: - In many scenarios, URLLC data transmissions can be relatively small and transmitted using a single transport block. This results in large variations in interference statistics when the assigned parameters and the presence of data change frequently at a given transmission point, because a new user may request a new transmission each time. - This situation is different from the legacy Extended Mobile Broadband (eMBB) scenario where packets for transmission may need to be relatively large and transmitted using multiple transport blocks and thus slots. In the legacy eMBB scenario, the channel state measured at the start of a downlink (DL) session can be applied for future transport blocks using possible outer loop adaptation based on Hybrid Automatic Repeat reQuest (HARQ) acknowledgments. - In the case of URLLC / IIoT scenarios with concentrated interference, legacy link adaptation may not function well for one or more of the following reasons: ○ There may not be enough time to measure the channel after the packet is triggered; ○ Measurements performed in one slot may not be accurate when applied to another slot; and / or ○ There may be no opportunity to apply the outer loop link adaptation mechanism because negative acknowledgments can contribute to latency.

[0012] Under these conditions, knowledge of channel information may need to be as accurate as possible so that a 5G base station (which may be referred to as a "gNB") can analyze separate CSI reports for different bands and slots and potentially re-predict the signal quality distribution in the time and frequency domains. This can help the gNB know the probability of having a SINR lower than a given target (referred to herein as "SINR_target" and which may be predefined, for example) or higher than SINR_target for a given target packet error rate.

[0013] In some cases, it may be desirable to extend the sub-band CQI reporting signaling granularity from 2 bits to 3 - 4 bits, assuming that it can provide more information about SINR in each sub-band compared to the wideband CQI report. However, this may not be very helpful for the gNB to understand / estimate the tail of the SINR distribution, which is important for predicting worst-case performance.

[0014] Under these assumptions, improvements to the CSI framework can be considered. In some embodiments, the link adaptation in URLLC and the problems described above associated with the CSI framework can be solved, removed, or mitigated by one or more of the following: - Extended sub-band CQI signaling for extended range CQI reporting - Use of multiple CQI tables for extended range CQI reporting. The legacy 3GPP specifications for NR may support CQI reporting using 4-bit wideband CQI. For example, see Tables 5.2.2.1-2 [Normal 64 Quadrature Amplitude Modulation (QAM) Table], 5.2.2.1-3 [256QAM Table], and 5.2.2.1-4 [Low Spectral Efficiency (SE) 64QAM Table] from 3GPP Technical Specification (TS) 38.214. These exemplary tables may be related to different ranges of SINR / SE and are copied below for reference. The legacy 3GPP specifications may further support differential sub-band CQI reporting using 2-bit indications, which are interpreted with respect to the wideband CQI values signaled using 4 bits. This is further shown in Table 5.2.2.1-1 in 3GPP TS38.214, which is copied below for reference. Table 5.2.2.1-2: 4-bit CQI Table [Table 1] Table 5.2.2.1-3: 4-bit CQI Table 2 [Table 2] Table 5.2.2.1-4: 4-bit CQI Table 3 [Table 3] Table 5.2.2.1-1 from TS38.214: Mapping of Sub-band Differential CQI Values to Offset Levels [Table 4] For one or more of the above tables, especially as may be seen in Table 5.2.2.1-1 from TS38.214, sub-band information may be clipped at levels -1 and +2 from the wideband CQI. In the case of URLLC use cases, such clipping can be highly detrimental as information regarding strong interference or channel fading in a given sub-band is inaccurate, especially in the negative region. Further, if the UE has good quality in some sub-bands, information may be lost beyond the above two levels.

[0015] To avoid loss of sub-band channel quality information, 3 or 4-bit sub-band CQI signaling is used, and thus can provide either 8 or 16 levels of sub-band CQI with respect to or regardless of the wideband (WB) CQI.

[0016] However, in some cases, the signaling extension may not provide the desired system performance because the tails of the SINR distribution, e.g., very low or very high SINR, may be inadequately represented by the signaling limited to the legacy CQI table, as shown in Figure 1. For example, as seen in Figure 1, there may be a portion of the SINR distribution that is difficult to represent using the legacy 2 - 4 bit CQI table, beyond CQI = 15 (e.g., to its right) or below CQI = 1 (e.g., to its left). As a result, the "clipping" effect described above may occur.

[0017] In the following section, techniques for expanding the range of effective SINR reported by CQI are presented, which can solve the problem of inaccurate effective SINR distribution prediction in the gNB scheduler. Specifically, the embodiments herein can expand the legacy CQI table through various options described below.

[0018] Extended Range CQI Reporting In one exemplary embodiment, the UE may be configured using an alternative sub - band CQI signaling mechanism, where the sub - band CQI is signaled by an X - bit payload, where X is a value from 2, 3, 4, or 5. In some embodiments, the value of X may be signaled by the base station to the UE. Specifically, the base station may provide the value of X via dedicated radio resource control (RRC) signaling, and the actual sub - band CQI may be calculated from the wide - band CQI and the X - bit payload using one or a combination of the following novel procedures: - Exemplary technique 1: The X - bit sub - band CQI may be interpreted as an offset from the reported wide - band CQI, provided that at least one or two code points in the X - bit range indicate either or both of a very low SINR (outage SINR) and a very high SINR. ○ Here, "very high SINR" can be interpreted as a channel quality corresponding to an SE value that is at least Y bits / sec / Hz higher than the spectral efficiency (SE) of CQI = 15, where Y may be, for example, 0.5, 1, 1.5 or any other positive value. Y may be pre - defined in the specification or may be configurable by the network for the UE as part of the CSI measurement and reporting framework. ○ Here, "very low SINR" can be interpreted as a channel quality corresponding to an SE value that is at least Z bits / sec / Hz less than the SE of CQI = 1, where Z may be, for example, 0.5, 1, 1.5 or any other positive value. Z may be pre - defined in the specification or may be configurable by the network for the UE as part of the CSI measurement and reporting framework. - Exemplary technique 2: The "out - of - range" CQI value = 0 may be associated with a more precise meaning of "out - of - range". The UE may be configured to interpret CQI = 0 as being associated with an SE value that is at least Z bits / sec / Hz less than the SE value of CQI = 1 in a configured table. - Example Technique 3: For X-bit differential sub-band CQI reporting, the UE may be configured regarding how to use the 2^X levels of differential signaling for the WB CQI, e.g., where to place the WB_CQI on the scale. For example, the UE may be configured / instructed to always report the X-bit difference for the WB CQI using A levels above the WB CQI and (2^X - A) levels equal to or lower than the WB CQI. Special handling may be applied when |WB CQI + SB diff CQI| is < 1 or > 15, e.g., how to handle the values obtained as a result outside the legacy range of 0...15. The value of A may be predefined, for example, either as 2^(X - 1) or 2^(X - 1) - 1; or it may be calculated based on the actual WB CQI value, e.g., A = min(15 - WB_CQI, 2^X), which means that the differential CQI cannot report values greater than 15 or less than 0 in this case. Alternative calculations for A may be considered as follows: ○ A = min(16 - WB_CQI, 2^X) ○ A = min(15 - WB_CQI, 2^(X - 1)) ○ A = min(16 - WB_CQI, 2^(X - 1)) ○ etc.

[0019] If |WB_CQI - SB_CQI_difference| exceeds the range 0...15, specific handling may be applied. For example, it may be defined that all step-downs or step-ups from the boundaries of the effective SINR range defined by CQI = 1 and CQI = 15 may be interpreted as a BdB offset from the SINR corresponding to CQI = 1 or CQI = 15, where the BdB offset may be predefined in the specification (e.g., as 1, 1.5, 2, 2.5, 3 dB, etc.) or may be configurable as part of the CSI reporting and measurement configuration.

[0020] Alternatively, the UE may be configured / instructed to append additional CQI table values to those associated with the current CSI report and measurement configuration. For example, if the UE is configured using the low SE 64QAM table (defined in Table 5.2.2.1-4), it may append higher values by obtaining entries 14 and 15 from the 64QAM table or entries 11, 12, 13, 14, 15 from the 256QAM table (defined in Table 5.2.2.1-2 or Table 5.2.2.1-3, respectively). - Exemplary technique 4: A special combination of WB_CQI and SB_CQI that provides additional information may be introduced. For example, if 4-bit SB CQI reporting is employed, the meaning of WB_CQI may change because the normal WB_CQI can be directly derived from the individual SB_CQIs. For example, WB_CQI may be interpreted as an offset (in terms of SE or SINR) to the SB_CQI report that can provide additional information beyond the SINR range of a single CQI table. - Exemplary Technique 5: In one embodiment, assuming that sub-band CQIs are reported for all sub-bands, the UE may be instructed to use an extended bit field of X = 3 or 4 bits for reporting differential sub-band CQIs for the lowest M sub-bands or the highest N sub-bands, or both, where the values of M and N may be specified (e.g., as fixed values or as a function of the total number of sub-bands), or may be configured for the UE via dedicated upper layer signaling. Such an approach can enable a better trade-off between a higher range of sub-band CQI reporting and the increased UL control information (UCI) incurred UL overhead (OH) in terms of using an extended bit field for sub-band CQI reporting for all sub-bands, because in many scenarios it may be expected that reporting sub-band CQIs for WB_CQI using a 2-bit offset according to the Rel-15 NR specification may be sufficient for a significant number of sub-bands. - Exemplary Technique 6: In one embodiment, when all sub-bands are configured with 4-bit CQI reporting, the WB CQI may be reinterpreted such that the SB CQI is calculated as the value obtained by adding the CQI offset signaled in the WB CQI taking a range from [-8...+7] or another range [X...X+15] to the 4-bit SB CQI value, where X may be configured or pre-defined from -15 to 15. ○ When the resulting SB CQI is <1 or >15, the corresponding SE is scaled. For example, for CQI = 0, the SE may be derived from CQI = 1 by scaling twice, or assuming two repetitions of the same TB associated with CQI = 1. For CQI = -1, the scaling may be three times, or assuming three repetitions of the same TB, and so on. Moreover, the modulation, SE, code rate, and number of repetitions corresponding to a given CQI value <1 and >15 may be configured by the RRC. - Exemplary Technique 7: In one embodiment, when all sub - bands are configured using 4 - bit CQI reports, the WB CQI may be reinterpreted as the minimum effective SINR among the shown sub - bands that includes values less than the SINR corresponding to CQI = 1. The mapping table between the effective SINR / SE for CQI < 1 and the values signaled in WB CQI may be configured by RRC or may be pre - defined in the specification.

[0021] Reporting of Multiple CQI Tables Similar to the mechanisms discussed in the previous sub - sections, it may be possible to extend the range of values for the reported effective SINR by configuring / enabling the UE to report WB_CQI and SB_CQI based on multiple CQI tables. As can be seen in the CQI discussed above, different tables cover different ranges of SINR / SE: the normal 64QAM table covers SE from 0.1523 to 5.5547, the 256QAM table covers SE from 0.1523 to 7.4063, and the low SE 64QAM table covers SE from 0.0586 to 4.5234.

[0022] When the ranges of different tables are combined, for example, in the case of low SE 64QAM+64QAM or low SE 64QAM+256QAM, it covers a larger distribution of the channel's effective SINR: 0.0586 to 7.4063 in the latter case.

[0023] In one example, the UE may be configured / instructed to report WB_CQI using a first CQI table and a first BLER target, and SB_CQI using an X - bit differential or absolute signaling using a second CQI table BLER target. The first and second BLER targets may be configurable separately from the CQI tables.

[0024] In one example, the UE may be configured / instructed to report the WB_CQI and SB_CQI for a first table for a first BLER target, and the WB_CQI and X-bit difference or absolute SB_CQI for a second table for a second BLER target.

[0025] In one example, the UE may be configured / instructed to report the absolute SB_CQI for a first table for a first BLER target, and the WB_CQI interpreted as an offset to the SINR or SE associated with the SB_CQI of the first table for obtaining the SB_CQI associated with a second table for a second BLER target. In particular, SB_CQI_1 = SB_CQI_0 + F(WB_CQI), where F() is a function for converting the WB_CQI value to an offset for obtaining SB_CQI_1 of another table from SB_CQI_0 of the first table.

[0026] In one example, the UE may be configured using multiple CQI tables and a single BLER target for each CSI report configuration, and the table in which the CQI is signaled may be selected by the UE implementation and indicated in the CSI report together with the CQI value. In particular, 1 bit may be used to indicate one of two tables. This may be done either by a separate field in the CSI report or by using, for example, the MSB or LSB of the WB CQI or SB CQI. For example, in the case of a 4-bit SB-CQI, 1 bit is used for table reporting and 3 bits are used for the SB-CQI.

[0027] Exemplary techniques Figure 2 shows an exemplary technique executed by a user equipment (UE) according to various embodiments. In some embodiments, the technique of Figure 2 may be executed by a UE, one or more elements of the UE, and / or one or more electrical devices including or implementing one or more elements of the UE. The technique may include, at 205, identifying channel state information (CSI) for a wideband and one or more sub-bands of the wideband. As described above, the CSI may be related to the wideband signal-to-interference-plus-noise ratio (SINR) or SINR measurements. The CSI may further be related to the SINR or SINR measurements of each of the one or more sub-bands.

[0028] The technique may further include, at 210, transmitting a wideband channel quality indicator (CQI) report related to the wideband CSI to a base station.

[0029] The technique may further include, at 215, identifying the number of bits to be used for a sub-band CQI report for one of the one or more sub-bands from the set of 2, 3, 4, and 5. More specifically, the identification at 215 may be an identification of a 2-bit CQI table, a 3-bit CQI table, a 4-bit CQI table, or a 5-bit CQI table used for the sub-band CQI report, as described above.

[0030] The technique may further include, at 220, transmitting a sub-band CQI report based on the number of bits identified at 215. For example, the sub-band CQI report may be transmitted based on a 2-bit CQI table, a 3-bit CQI table, a 4-bit CQI table, or a 5-bit CQI table. The CQI report may be related to the CSI of the sub-band.

[0031] Figure 3 shows alternative exemplary techniques performed by a base station, according to various embodiments. In some embodiments, the techniques of Figure 3 may be performed by a base station, one or more elements of the base station, and / or one or more electrical devices that include or implement one or more elements of the base station. The techniques may include, at 305, identifying a wideband CQI report related to a wideband (e.g., in a transmission received from a UE). The techniques may further include, at 310, processing the wideband CQI to report wideband CSI. As described above, the wideband CSI may be related to wideband SINR and / or SINR measurements.

[0032] The techniques may further include, at 315, identifying a subband CQi report related to one of one or more subbands (e.g., in a transmission received from a UE). The subband CQI report may be transmitted using 5 bits. For example, in some embodiments, the subband CQI report may be transmitted based on a 5-bit CQI table. In other embodiments, the subband CQI report may be transmitted using 2 - 4 bits.

[0033] The techniques may further include, at 320, processing the subband CQI report to identify subband CSI. As described above, the subband CSI may be related to subband SINR and / or SINR measurements.

[0034] Note that the techniques described above are intended as examples of techniques for particular embodiments, and other embodiments may include more or fewer elements, elements arranged in a different order, elements occurring simultaneously with each other, etc.

[0035] Systems and Implementations Figures 4 - 5 show various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0036] Figure 4 shows a network 400 according to various embodiments. Network 400 may operate in a manner consistent with 3GPP technical specifications for an LTE or 5G / NR system. However, the exemplary embodiments are not limited in this regard, and the described embodiments may be applicable to other networks that benefit from the principles described herein, such as future 3GPP systems and the like.

[0037] Network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. UE 402 may be communicatively coupled to RAN 404 by a Uu interface. UE 402 may be a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-vehicle entertainment device, instrument cluster, head-up display device, on-vehicle diagnostic device, dash-top mobile device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, network appliance, machine type communication device, M2M or D2D device, IoT device, etc., but is not limited thereto.

[0038] In some embodiments, network 400 may include a plurality of UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0039] In some embodiments, UE402 may further communicate with AP406 via an over-the-air connection. AP406 may manage a WLAN connection, which may function to offload some / all network traffic from RAN404. The connection between UE402 and AP406 may be consistent with any IEEE 802.11 protocol, where AP406 can be a Wireless Fidelity (Wi-Fi (registered trademark)) router. In some embodiments, UE402, RAN404, and AP406 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may involve RAN404 configuring UE402 to utilize both cellular radio resources and WLAN resources.

[0040] RAN404 may include one or more access nodes, e.g., AN408. AN408 may terminate an air interface protocol for UE402 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN408 may enable data / voice connectivity between CN420 and UE402. In some embodiments, AN408 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, e.g., a virtual network that may be referred to as a CRAN or a virtual baseband unit pool. AN408 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN408 may be a macrocell base station or a low-power base station providing a femtocell, picocell, or other similar cell having a coverage area smaller than, user capacity smaller than, or bandwidth higher than that of a macrocell.

[0041] In embodiments where RAN404 includes a plurality of ANs, they may be coupled to each other via an X2 interface (when RAN404 is an LTE RAN) or an Xn interface (when RAN404 is a 5G RAN). In some embodiments, the X2 / Xn interface, which may be separated into a control / user plane interface, may enable the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0042] Each of the ANs of RAN404 may manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE402. UE402 may be connected to a plurality of cells provided by the same or different ANs of RAN404 simultaneously. For example, UE402 and RAN404 may use carrier aggregation to enable UE402 to connect to a plurality of component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a master node providing the MCG, and the second AN may be a secondary node providing the SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0043] RAN404 may provide an air interface via an authorized spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / Scell. Before accessing the unlicensed spectrum, the node may perform a media / carrier sensing operation based on, for example, the listen-before-talk (LBT) protocol.

[0044] In a V2X scenario, UE402 or AN408 may be, or may function as, an RSU, which may refer to any transportation infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. The RSU implemented in or by a UE may be referred to as a "UE-type RSU"; the eNB may be referred to as an "eNB-type RSU"; the gNB may be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to a roadside radio frequency circuit that provides connectivity support to passing vehicle UEs. The RSU may include intersection map geometry, traffic statistics, an internal data storage circuit for storing media, and applications / software for detecting and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally, or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weather-resistant housing suitable for outdoor installation and may include a network interface controller that provides a wired connection (e.g., Ethernet (registered trademark)) to a traffic signal controller or a backhaul network.

[0045] In some embodiments, RAN 404 may be an LTE RAN 410 having an eNB, e.g., eNB 412. The LTE RAN 410 may provide the following characteristics to the LTE air interface: an SCS of 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection in the UE. The LTE air interface may operate in the sub-6 GHz band.

[0046] In some embodiments, RAN 404 may be an NG-RAN 414 having a gNB, e.g., gNB 416, or an ng-eNB, e.g., ng-eNB 418. The gNB 416 may connect to 5G-capable UEs using the 5G NR interface. The gNB 416 may connect to the 5G core through an NG interface that may include an N2 interface or an N3 interface. The ng-eNB 418 may connect to the 5G core through the NG interface, but may connect to UEs through the LTE air interface. The gNB 416 and the ng-eNB 418 may be connected to each other through the Xn interface.

[0047] In some embodiments, the NG interface may be split into two parts, namely, an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between nodes of the NG-RAN 414 and the UPF 448, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between nodes of the NG-RAN 414 and the AMF 444.

[0048] NG-RAN414 may provide the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, repetition codes, simplex codes, and Reed-Muller codes for control, and LDPC for data to the 5G-NR air interface. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but use PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band including the sub-6 GHz band, or on the FR2 band including the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0049] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, a BWP may be used for dynamic adaptation of the SCS. For example, UE 402 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When a BWP change is signaled to UE 402, the transmission SCS is similarly changed. Another use case example of BWPs is related to power saving. In particular, multiple BWPs may be configured for UE 402 using different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP that includes fewer PRBs may be used for data transmission under low traffic load, while enabling power saving in UE 402 and in some cases in gNB 416. A BWP that includes more PRBs may be used for scenarios with higher traffic loads. RAN 404 is communicatively coupled to CN 420, which includes network elements that provide various functions to support customers / subscribers (e.g., users of UE 402) with data and telecommunications services. The components of CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of CN 420 onto physical computing / storage resources in a server, switch, etc. The logical instantiation of CN 420 may be referred to as a network slice, and a partial logical instantiation of CN 420 may be referred to as a network sub-slice.

[0050] In some embodiments, CN 420 may be an LTE CN 422, which may also be referred to as an EPC. As shown, LTE CN 422 may include an MME 424, an SGW 426, an SGSN 428, an HSS 430, a PGW 432, and a PCRF 434, which are coupled to each other via interfaces (or "reference points"). The functions of the elements of LTE CN 422 may be briefly introduced as follows.

[0051] The MME 424 may implement mobility management functions that track the current location of the UE 402 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0052] The SGW 426 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for handovers between RAN nodes and may provide an anchor for mobility between 3GPPs. Other roles may include lawful interception, charging, and enforcement of any policies.

[0053] The SGSN 428 may track the location of the UE 402 and perform security functions and access control. Additionally, the SGSN 428 may perform signaling between EPC nodes for mobility between different RAT networks; PDN and S-GW selection as specified by the MME 424; MME selection for handover, etc. The S3 reference point between the MME 424 and the SGSN 428 may enable the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0054] The HSS 430 may include a database for network users that contains subscription-related information to support the handling of communication sessions by network entities. The HSS 430 can provide support for routing / roaming, authentication, authorization, name / address resolution, location dependency, etc. The S6a reference point between the HSS 430 and the MME 424 may enable the transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 420.

[0055] The PGW 432 may terminate the SGi interface towards a data network (DN) 436 which may include an application / content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled to the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 436 may be a public, private PDN external to the operator, or an intra-operator packet data network, for example, for the provisioning of IMS services. The PGW 432 may be coupled to the PCRF 434 via a Gx reference point. The PCRF 434 is a policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app / content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules to a PCEF having appropriate TFT and QCI (via the Gx reference point).

[0056] In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, an AMF 444, an SMF 446, a UPF 448, an NSSF 450, a NEF 452, an NRF 454, a PCF 456, a UDM 458, and an AF 460 coupled to each other via interfaces (or “reference points”) as shown. The functions of the elements of the 5GC 440 may be briefly introduced as follows. The AUSF 442 may store data for the authentication of the UE 402 and handle authentication-related functions. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 via the reference points as shown, the AUSF 442 may present an Nausf service-based interface.

[0057] The AMF 444 may enable other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications regarding mobility events related to the UE 402. The AMF 444 may be responsible for registration management (e.g., registering the UE 402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446 and function as a transparent proxy for routing SM messages. The AMF 444 may also provide transport for SMS messages between the UE 402 and the SMSF. The AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Further, the AMF 444 may be an endpoint of the RAN CP interface, which may include or be the N2 reference point between the RAN 404 and the AMF 444; the AMF 444 is an endpoint of the NAS (N1) signaling and may perform NAS encryption and integrity protection. The AMF 444 may also support NAS signaling with the UE 402 via the N3 IWF interface.

[0058] The SMF446 is responsible for SM (e.g., session establishment, tunnel management between the UPF448 and the AN408); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuring traffic steering in the UPF448 to route traffic to the appropriate destination; terminating the interface towards the policy control function; controlling part of policy enforcement, charging, and QoS; lawful interception (for SM events and the interface to the LI system); terminating the SM part of the NAS message; downlink data notification; initiating AN-specific SM information sent to the AN408 via the AMF444 via N2; and determining the SSC mode of the session. SM may refer to the management of the PDU session, and the PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE402 and the data network 436.

[0059] The UPF448 may function as an anchor point for RAT-internal and RAT-intermobility, an external PDU session point of interconnect to the data network 436, and a branching point to support multi-home PDU sessions. The UPF448 also performs packet routing and forwarding, performs packet inspection, enforces the user plane part of the policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs uplink traffic verification (e.g., SDF to QoS flow mapping), performs transport level packet marking in the uplink and downlink, and may perform downlink packet buffering and downlink data notification triggering. The UPF448 may include an uplink classifier to support routing traffic flows to the data network.

[0060] The NSSF 450 may select a set of network slice instances to serve the UE 402. The NSSF 450 may determine the permitted NSSAI and, if necessary, the mapping to the subscribed S-NSSAI. The NSSF 450 may also determine a set of AMFs or a list of candidate AMFs to be used to serve the UE 402, based on a suitable configuration and, in some cases, by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444, using which the UE 402 may be registered by interacting with the NSSF 450, whereby a change of AMF may be brought about. The NSSF 450 may interact with the AMF 444 via the N22 reference point; and communicate with another NSSF in the visited network via an N31 reference point (not shown). In addition, the NSSF 450 may present an Nnssf service-based interface.

[0061] NEF452 may securely expose services and functions provided by 3GPP network functions for third parties, internal disclosure / re-disclosure, AF (e.g., AF460), edge computing, or fog computing systems, etc. In such embodiments, NEF452 may authenticate, authorize, or throttle the AF. NEF452 may transform information exchanged with AF460 and information exchanged with internal network functions. For example, NEF452 may transform between AF service identifiers and internal 5GC information. NEF452 may receive information from other NFs based on the published capabilities of the other NFs. This information may be stored in NEF452 as structured data or in a data storage NF using a standardized interface. The stored information may then be re-exposed by NEF452 to other NFs and AFs or used for other purposes such as analysis. Additionally, NEF452 may present an Nnef service-based interface. NRF454 may support a service discovery function, receive NF discovery requests from NF instances, and provide information on discovered NF instances to the NF instances. NRF454 also maintains information on available NF instances and the services they support. As used herein, terms such as "instantiate," "instantiation," etc. may refer to the generation of an instance, and "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, NRF454 may present an Nnrf service-based interface. PCF456 may provide them to control plane functions to enforce policy rules and may support a unified policy framework for managing network behavior. PCF456 may implement a front end to access subscription information related to policy decisions in the UDR of UDM458. In addition to communicating with functions via the reference points shown, PCF456 presents an Npcf service-based interface.The UDM458 may well handle subscription-related information to support the handling of communication sessions by network entities and may store the subscription data of the UE402. For example, the subscription data may be communicated via the N8 reference point between the UDM458 and the AMF444. The UDM458 may include two parts, namely, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM458 and the PCF456, and / or structured data for publication and application data for the NEF452 (including PFD for application detection, application request information for multiple UEs402). The Nudr service-based interface may be presented by the UDR221 to enable the UDM458, the PCF456, and the NEF452 to access a specific set of stored data and to read, update (e.g., add, modify), delete, and subscribe for notifications of related data changes in the UDR. The UDM may include a UDM-FE, which is responsible for processing credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via the reference points shown, the UDM458 may present a Nudm service-based interface. The AF460 may provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0062] In some embodiments, the 5GC 440 may enable edge computing by selecting operator / third-party services that should be geographically close to the point where the UE 402 is attached to the network. Thereby, latency and the load on the network can be reduced. To provide an edge computing implementation, the 5GC 440 may select a UPF 448 near the UE 402 and perform traffic steering to the data network 436 via the N6 interface from the UPF 448. This may be based on UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on the operator's deployment, if the AF 460 is considered a trusted entity, the network operator may permit the AF 460 to directly interact with the relevant NF. Additionally, the AF 460 may present a Naf service-based interface. The data network 436 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers including, for example, an application / content server 438.

[0063] FIG. 5 schematically shows a wireless network 500 according to various embodiments. The wireless network 500 may include a UE 502 that wirelessly communicates with an AN 504. The UE 502 and the AN 504 are similar to the components named similarly elsewhere in this specification and may be substantially interchangeable with them. UE 502 may be communicatively coupled to AN 504 via connection 506. Connection 506 is shown as an air interface to enable communicative coupling and may be consistent with a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies. UE 502 may include a host platform 508 coupled to a modem platform 510. The host platform 508 may include an application processing circuit 512 coupled to the protocol processing circuit 514 of the modem platform 510. The application processing circuit 512 may execute various applications for UE 502 that source / sink application data. The application processing circuit 512 may further implement one or more layer operations to transmit / receive application data with a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations. The protocol processing circuit 514 may implement one or more of the layer operations to facilitate transmission or reception of data via connection 506. The layer operations implemented by the protocol processing circuit 514 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 510 may further include a digital baseband circuit 516 that may implement one or more layer operations that are the “lower” layer operations executed by the protocol processing circuit 514 in the network protocol stack. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.The modem platform 510 may further include a transmit circuit 518, a receive circuit 520, an RF circuit 522, and an RF front end (RFFE) 524, and the RFFE 524 may include or be connected to one or more antenna panels 526. Briefly, the transmit circuit 518 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 520 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 522 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 524 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and configuration of the components of the transmit circuit 518, the receive circuit 520, the RF circuit 522, the RFFE 524, and the antenna panel 526 (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM at mmWave or sub-6 GHz frequencies. In some embodiments, the transmit / receive components may be configured in multiple parallel transmit / receive chains and may be arranged in the same or different chips / modules, etc. In some embodiments, the protocol processing circuit 514 may include one or more instances of a control circuit (not shown) to provide control functions for the transmit / receive components. UE reception may be established by and through the antenna panel 526, the RFFE 524, the RF circuit 522, the receive circuit 520, the digital baseband circuit 516, and the protocol processing circuit 514. In some embodiments, the antenna panel 526 may receive transmissions from the AN504 by receive beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 526.

[0064] UE transmission may be established by and via a protocol processing circuit 514, a digital baseband circuit 516, a transmission circuit 518, an RF circuit 522, an RFFE 524, and an antenna panel 526. In some embodiments, the transmission components of UE 504 may apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 526. Similar to UE 502, AN 504 may include a host platform 528 coupled to a modem platform 530. The host platform 528 may include an application processing circuit 532 coupled to a protocol processing circuit 534 of the modem platform 530. The modem platform may further include a digital baseband circuit 536, a transmission circuit 538, a reception circuit 540, an RF circuit 542, an RFFE circuit 544, and an antenna panel 546. The components of AN 504 are similar to the similarly named components of UE 502 and may be substantially interchangeable therewith. In addition to performing data transmission / reception as described above, the components of AN 508 may perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. FIG. 6 is a block diagram showing components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein according to some exemplary embodiments. Specifically, FIG. 6 shows an illustrative representation of a hardware resource 600 including one or more processors (or processor cores) 610, one or more memory / storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuit. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resource 600.

[0065] Processor 610 may include, for example, processor 612 and processor 614. Processor 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

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

[0067] Communication resource 630 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 604 or one or more databases 606 or other network elements via network 608. For example, communication resource 630 may include wired communication components (for coupling via, e.g., USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth (or Bluetooth Low Energy) components, Wi-Fi components, and other communication components.

[0068] Command 650 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of processors 610 to execute any one or more of the methodologies discussed herein. Command 650 may be wholly or partially present in at least one of processors 610 (e.g., within the cache memory of the processor), memory / storage device 620, or any suitable combination thereof. Further, any portion of Command 650 may be transferred from any combination of peripheral devices 604 or database 606 to hardware resource 600. Accordingly, the memory of processor 610, memory / storage device 620, peripheral devices 604, and database 606 are examples of computer-readable and machine-readable media.

[0069] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the example section below. For example, a baseband circuit as described above in connection with one or more of the foregoing drawings may be configured to operate in accordance with one or more of the examples described below. For another example, a circuit associated with a UE, a base station, a network element, etc. as described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples described in the example section below. Example Example 1 is a system and / or method for transmitting a channel state information (CSI) report for enhanced ultra-reliable low-latency communication (URLLC), receiving, by a UE, a CSI reporting configuration from a gNB; receiving, by the UE, a requested CSI report from the gNB; measuring, by the UE, one or more CSIs using wideband and subband CQIs; and A stage in which a UE reports one or more CSI reports on a PUCCH or PUSCH A system and / or method may be included that comprises Example 2 may include the method of Example 1 or any other example herein, where a UE may be configured using an alternative sub-band CQI signaling mechanism, the sub-band CQI is signaled by an X-bit payload, where X is a value from 2, 3, 4, 5, and the actual sub-band CQI may be calculated from the wideband CQI and the X-bit payload. Example 3 may include the method of Example 2 or any other example herein, where the X-bit sub-band CQI may be interpreted as an offset from the reported wideband CQI, provided that at least one or two code points in the X-bit range indicate one or both of a very low SINR (outage SINR) and a very high SINR. Example 4 may include the method of Example 3 or any other example herein, where "very high SINR" may be interpreted as a channel quality corresponding to an SE value that is at least Y bits / sec / Hz higher than the spectral efficiency (SE) of CQI = 15, where Y may be, for example, 0.5, 1, 1.5, or any other positive value. Y may be pre-defined in the specification or may be configurable by the network for the UE as part of the CSI measurement and reporting framework. Example 5 may include the method of Example 3 or any other example herein, where "very low SINR" may be interpreted as a channel quality corresponding to an SE value that is at least Z bits / sec / Hz lower than the SE of CQI = 1, where Z may be, for example, 0.5, 1, 1.5, or any other positive value. Z may be pre-defined in the specification or may be configurable by the network for the UE as part of the CSI measurement and reporting framework. Example 6 may include the method of Example 2 or any other example herein, where a "out-of-range" CQI value = 0 may be associated with a more precise meaning of "out-of-range". The UE may be configured to interpret CQI = 0 as being associated with an SE value that is at least Z bits / sec / Hz less than the CQI value = 1 in the configured table. Example 7 may include the method of Example 2 or any other example herein, regarding how the UE may be configured for X-bit differential sub-band CQI reporting, e.g., how to use the 2^X levels of differential signaling for WB CQI, such as where to place WB_CQI on the scale. Example 8 may be configured / instructed such that the UE always reports an X-bit difference for WB CQI using A levels above WB CQI and (2^X - A) levels equal to or lower than WB CQI. Special handling may be applied when |WB CQI + SB diff CQI| is < 1 or > 15, e.g., how to handle values obtained as a result outside the legacy range of 0...15. Example 8 may include the method of Example 7 or any other example herein. Example 9 may include the method of Example 7 or any other example herein, where specific handling may be applied when |WB_CQI - SB_CQI_difference| exceeds the range 0...15. For example, it may be defined that all step-downs or step-ups from the boundaries of the effective SINR range defined by CQI = 1 and CQI = 15 may be interpreted as a BdB offset from the SINR corresponding to CQI = 1 or CQI = 15, where the BdB offset may be pre-defined in the specification (e.g., as 1, 1.5, 2, 2.5, 3 dB, etc.) or may be configurable as part of the CSI reporting and measurement configuration. Example 10 is that when 4-bit SB CQI reporting is adopted, the meaning of WB_CQI can change because the normal WB_CQI can be directly derived from separate SB_CQIs, and it may include the method of Example 2 or any other example in this specification. For example, WB_CQI may be interpreted as an offset (in terms of SE or SINR) to the SB_CQI report that can provide additional information beyond the SINR range of a single CQI table. Example 11 is that assuming sub-band CQIs are reported for all sub-bands, the UE may be instructed to use an extended bit field of X = 3 or 4 bits for reporting differential sub-band CQIs for the lowest M sub-bands or the highest N sub-bands, or both, where the values of M and N may be specified (e.g., as fixed values or as a function of the total number of sub-bands), or may be configured for the UE via dedicated upper layer signaling, and it may include the method of Example 2 or any other example in this specification. Example 12 is that the UE may be configured / instructed to report WB_CQI using a first CQI table and a first BLER target, and SB_CQI using an X-bit differential or absolute signaling using a second CQI table BLER target, and it may include the method of Example 1 or any other example in this specification. Example 13 is that the UE may be configured / instructed to report WB_CQI and SB_CQI for a first table for a first BLER target, and WB_CQI and X-bit differential or absolute SB_CQI for a second table for a second BLER target, and it may include the method of Example 1 or any other example in this specification. Example 14 may be configured / instructed such that the UE reports a WB_CQI interpreted as an offset to the SINR or SE associated with the SB_CQI of the first table for the first BLER target and the SB_CQI associated with the second table for the second BLER target, and may include the method of Example 1 or any other example herein. Example 15 may be configured with a plurality of CQI tables and a single BLER target for each CSI report configuration, and the table from which the CQI is signaled may be selected by the UE implementation and indicated in the CSI report together with the CQI value, and may include the method of Example 1 or any other example herein.

[0070] Example 16 may be reinterpreted such that when all sub-bands are configured with 4-bit CQI reporting, the WB CQI is calculated as the value obtained by adding the CQI offset signaled in the WB CQI, where the SB CQI takes a range from [-8... +7] or another range [X... X + 15] to the 4-bit SB CQI value, and X may be configured or pre-defined from -15 to 15, and may include the method of Example 1 or any other example herein.

[0071] Example 17 may include the method of Example 16 or any other example herein, where if the resulting SB CQI is <1 or >15, the corresponding SE is scaled. For example, when CQI = 0, the SE may be derived from CQI = 1 by scaling by 2 or assuming two repetitions of the same TB associated with CQI = 1. When CQI = -1, the scaling may be 3 or assuming three repetitions of the same TB, and so on. Additionally, the modulation, SE, code rate, and number of repetitions corresponding to a given CQI value <1 and >15 may be configured by the RRC.

[0072] In Example 18, when all sub-bands are configured using 4-bit CQI reports, the WB CQI may be reinterpreted as the minimum effective SINR among the sub-bands shown that includes values less than the SINR corresponding to CQI = 1, and may include the method of Example 1 or any other example herein. The mapping table between the effective SINR / SE for CQI < 1 and the values signaled in the WB CQI may be configured by the RRC or may be pre-defined in the specification.

[0073] Example 19 is a method of a UE, comprising: receiving configuration information for CSI reporting; receiving a request for a CSI report; obtaining one or more CSIs using wideband and sub-band CQIs based on the configuration information and the request stage; and reporting one or more CSIs using wideband and sub-band CQIs. The method may be included.

[0074] Example 20 may include the method of Example 19 or any other example herein, where one or more CSIs are reported on the PUCCH or PUSCH. Example 21 may include the method of Examples 19 - 20 or any other example herein, where the request includes a payload to indicate the sub-band CQI.

[0075] Example 22 may include the method of Example 21 or any other example herein, where the sub-band CQI is indicated by the payload and the wideband CQI.

[0076] Example 23 may include the method of Examples 21 - 22 or any other example herein, where the payload is 2 to 5 bits.

[0077] Example 24 may include the method of Examples 19 - 23 or any other example herein, where the report is for extended ultra-reliable low-latency communication URLLC.

[0078] Example 25 is a method performed by a user equipment (UE), comprising: identifying channel state information (CSI) for a wideband and one or more sub-bands of the wideband, where the CSI is related to the wideband signal-to-interference and noise ratio (SINR) and the respective SINR of the one or more sub-bands; transmitting a wideband channel quality indicator (CQI) report related to the wideband CSI; identifying, from the set of 2, 3, 4, and 5, the number of bits to be used for a sub-band CQI report related to one of the one or more sub-bands; and transmitting a sub-band CQI report based on the identified number of bits, where the sub-band CQI report is related to the CSI of the sub-band may include a method.

[0079] Example 26 may include the method of Example 25 and / or any other example herein, where the identified number of bits is based on an indication received from a base station.

[0080] Example 27 may include the method of any one of Examples 25 - 26 and / or any other example herein, where the sub-band CQI report indicates that the sub-band has a spectral efficiency (SE) value higher than the highest possible SE value that can be signaled by a 4-bit CQI table.

[0081] Example 28 may include the method of Example 27 and / or any other example herein, where the CQI report indicates that the sub-band has an SE value that is at least Y bits / second / hertz (Hz) higher than the highest possible SE value indicated by a 4-bit CQI table, and Y is predefined or provided to the UE via upper layer signaling.

[0082] Example 29 may include the method of any one of Examples 25-26 and / or any other example herein, showing that the sub-band CQI report has an SE value smaller than the spectral efficiency (SE) of the lowest possible effective CQI value by which the sub-band can be signaled by a 4-bit CQI table.

[0083] Example 30 shows that the sub-band CQI report has an SE value that is at least Z bits / second / hertz (Hz) smaller than the SE of the smallest possible effective CQI value indicated by a 4-bit CQI table, where Z is predefined or provided to the UE via upper layer signaling, and may include the method of Example 29 and / or any other example herein.

[0084] Example 31 may include the method of any one of Examples 25-26 and / or any other example herein, showing that the sub-band CQI report indicates a measured CQI of 0 corresponding to an SE value of at least Z bits / second / hertz (Hz) smaller than CQI value = 1.

[0085] Example 32 may include the method of any one of Examples 25-26 and / or any other example herein, where the sub-band CQI report includes 2^(number of identified bits) levels with respect to the wideband CQI report, and the UE is further configured using A levels above the reported wideband CQI value and (2^(number of identified bits)-A) levels below the reported wideband CQI value.

[0086] Example 33 may include the method of Example 32 and / or any other example herein, where the value of A is specified as a function of the number of identified bits for the sub-band CQI report.

[0087] Example 34 may include the method of Example 32 and / or any other example herein, where the value of A is a function of the number of identified bits of the sub-band CQI report and the reported wideband CQI value.

[0088] Example 35 is such that all sub - bands are configured using 4 - bit CQI reports, and the sub - band CQI value is determined as the sum of the value reported by the UE in the sub - band CQI report and the value reported by the UE in the wide - band CQI report interpreted as an offset having a range of [-8...+7] or [X...X + 15], where the value of X is provided to the UE by the upper layer from the set of integers {-15,...,15}, and may include the methods of Examples 25 - 26 and / or any other examples herein.

[0089] Example 36 may include the method of Example 35 and / or any other examples herein, where if the sub - band CQI value is lower than 1 or higher than 15, the corresponding spectral efficiency (SE) is scaled.

[0090] Example 37 is a method performed by a base station, identifying a wide - band channel quality index (CQI) report related to a wide - band from a user equipment (UE); processing the wide - band CQI report to identify wide - band channel state information (CSI), where the wide - band CSI is related to the wide - band signal - to - interference - and - noise ratio (SINR); identifying a sub - band CQI report related to one of one or more sub - bands from the UE, where the sub - band CQI report is transmitted using 5 bits; and processing the sub - band CQI report to identify sub - band CSI, where the sub - band CSI is related to the sub - band SINR may include a method comprising.

[0091] Example 38 may include the method of Example 37 and / or any other examples herein, further comprising transmitting an indication to the UE that the sub - band CQI report is transmitted using a 5 - bit CQI table.

[0092] Example 39 may include the method of any of Examples 37 - 38 and / or any other example herein, showing that the sub - band CQI report has a spectral efficiency (SE) value higher than the highest possible SE value that the sub - band can be signaled by a 4 - bit CQI table.

[0093] Example 40 may include the method of Example 39, showing that the CQI report has an SE value that is at least Y bits / second / hertz (Hz) higher than the highest possible SE value indicated by a 4 - bit CQI table, where Y is predefined or provided to the UE via upper - layer signaling.

[0094] Example 41 may include the method of any of Examples 37 - 38 and / or any other example herein, showing that the sub - band CQI report has an SE value smaller than the spectral efficiency (SE) value of the lowest possible valid CQI value that the sub - band can be signaled by a 4 - bit CQI table.

[0095] Example 42 may include the method of Example 41 and / or any other example herein, showing that the sub - band CQI report has an SE value that is at least Z bits / second / hertz (Hz) smaller than the SE of the smallest possible valid CQI value indicated by a 4 - bit CQI table, where Z is predefined or provided to the UE via upper - layer signaling.

[0096] Example 43 may include the method of any of Examples 37 - 38 and / or any other example herein, showing that the sub - band CQI report shows a measured CQI of 0 corresponding to an SE value of at least Z bits / second / hertz (Hz) smaller than CQI value = 1.

[0097] Example 44 may include the method of any of Examples 37 - 38 and / or any other example herein, where the sub - band CQI report includes 2^(the number of bits used to transmit the sub - band CQI report) levels with respect to the wide - band CQI report, and the UE is further configured using A levels above the reported wide - band CQI value and (2^(the number of bits used to transmit the sub - band CQI report)-A) levels below the reported wide - band CQI value.

[0098] Example 45 may include the method of Example 44 and / or any other example herein, where the value of A is specified as a function of the number of identified bits for the sub - band CQI report.

[0099] Example 46 may include the method of Example 44 and / or any other example herein, where the value of A is a function of the number of bits used to transmit the sub - band CQI report and the reported wide - band CQI value.

[0100] Example Z01 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1 - 46, or any other method or process described herein.

[0101] Example Z02 may include one or more non - transitory computer - readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method described in or related to any of Examples 1 - 46, or any other method or process described herein.

[0102] Example Z03 may include an apparatus comprising logic, module, or circuitry for performing one or more elements of the method described in or related to any of Examples 1 - 46, or any other method or process described herein.

[0103] Example Z04 may include a method, technique, or process, or a part or portion thereof, as described in or related to any of Examples 1 to 46.

[0104] Example Z05 may include an apparatus comprising one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to execute a method, technique, or process, or a part thereof, as described in or related to any of Examples 1 to 46.

[0105] Example Z06 may include a signal, or a part or portion thereof, as described in or related to any of Examples 1 to 46.

[0106] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message, or a part or portion thereof, or something otherwise described in the present disclosure, as described in or related to any of Examples 1 to 46.

[0107] Example Z08 may include a signal encoded using data, or a part or portion thereof, or something otherwise described in the present disclosure, as described in or related to any of Examples 1 to 46.

[0108] Example Z09 may include a signal encoded using a datagram, packet, frame, segment, protocol data unit (PDU), or message, or a part or portion thereof, or something otherwise described in the present disclosure, as described in or related to any one of Examples 1 to 46.

[0109] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, and the execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or a portion thereof, as described in or related to any of Examples 1-46.

[0110] Example Z11 may include a computer program containing instructions, and the execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, as described in or related to any of Examples 1-46.

[0111] Example Z12 may include signals in a wireless network as illustrated and described herein.

[0112] Example Z13 may include a method of communicating in a wireless network as illustrated and described herein.

[0113] Example Z14 may include a system for providing wireless communication as illustrated and described herein.

[0114] Example Z15 may include a device for providing wireless communication as illustrated and described herein.

[0115] Any of the examples described above may be combined with any other example (or combination of examples) unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description and is not intended to be exhaustive or to limit the scope of the embodiments to the exact forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0116] Abbreviations Unless otherwise used differently in this specification, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed in this specification. 3GPP: 3rd Generation Partnership Project 4G: 4th Generation 5G: 5th Generation 5GC: 5G Core Network AC: Application Client ACR: Application Context Relocation ACK: Acknowledgment ACID: Application Client Identifier AF: Application Function AM: Acknowledgment Mode AMBR: Aggregate Maximum Bit Rate AMF: Access and Mobility Management Function AN: Access Network ANR: Automatic Neighbor Relation AOA: Angle of Arrival AP: Application Protocol, Antenna Port, Access Point API: Application Programming Interface APN: Access Point Name ARP: Allocation and Retention Priority ARQ: Automatic Repeat reQuest AS: Access Stratum ASP: Application Service Provider ASN.1: Abstract Syntax Notation One AUSF: Authentication Server Function AWGN: Additive White Gaussian Noise BAP: Backhaul Adaptive Protocol BCH: Broadcast Channel BER: Bit Error Ratio BFD: Beam Failure Detection BLER: Block Error Rate BPSK: Binary Phase Shift Keying BRAS: Broadband Remote Access Server BSS: Business Support System BS: Base Station BSR: Buffer Status Report BW: Bandwidth BWP: Bandwidth Part C-RNTI: Cell Radio Network Temporary Identity CA: Carrier Aggregation, Certification Authority CAPEX: Capital Expenditure CBRA: Collision-Based Random Access CC: Component Carrier, Country Code, Cyclic Redundancy Checksum CCA: Clear Channel Assessment CCE: Control Channel Element CCCH: Common Control Channel CE: Coverage Enhancement CDM: Content Delivery Network CDMA: Code Division Multiple Access CDR: Charging Data Request CDR: Charging Data Response CFRA: Collision-Free Random Access CG: Cell Group CGF: Charging Gateway Function CHF: Charging Function CI: Cell Identity CID: Cell ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier to Interference Ratio CK: Cipher Key CM: Connection Management, Conditional Obligation CMAS: Commercial Mobile Alert Service CMD: Command CMS: Cloud Management System CO: Conditional Optional CoMP: Coordinated Multipoint CORESET: Control Resource Set COTS: Commercial Off-The-Shelf CP: Control Plane, Cyclic Prefix, Connection Point CPD: Connection Point Descriptor CPE: Customer Premises Equipment CPICH: Common Pilot Channel CQI: Channel Quality Indicator CPU: CSI Processing Unit, Central Processing Unit C / R: Command / Response Field Bit CRAN: Cloud Radio Access Network, Cloud RAN CRB: Common Resource Block CRC: Cyclic Redundancy Check CRI: Channel State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI: Cell RNTI CS: Circuit Switching CSCF: Call Session Control Function CSAR: Cloud Service Archive CSI: Channel State Information CSI-IM: CSI Interference Measurement CSI-RS: CSI Reference Signal CSI-RSRP: CSI Reference Signal Received Power CSI-RSRQ: CSI Reference Signal Received Quality CSI-SINR: CSI Signal-to-Noise and Interference Ratio CSMA: Carrier Sense Multiple Access CSMA / CA: CSMA with Collision Avoidance CSS: Common Search Space, Cell-Specific Search Space CTF: Charging Trigger Function CTS: Clear to Send CW: Codeword CWS: Contention Window Size D2D: Device-to-Device DC: Dual Connectivity, Direct Current DCI: Downlink Control Information DF: Deployment Flavor DL: Downlink DMTF: Distributed Management Task Force DPDK: Data Plane Development Kit DM-RS, DMRS: Demodulation Reference Signal DN: Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Radio Bearer DRS: Discovery Reference Signal DRX: Discontinuous Reception DSL: Domain Specific Language, Digital Subscriber Line DSLAM: DSL Access Multiplexer DwPTS: Downlink Pilot Time Slot E-LAN: Ethernet Local Area Network E2E: End-to-End EAS: Edge Application Server ECCA: Extended Clear Channel Assessment, Extended CCA ECCE: Enhanced Control Channel Element, Enhanced CCE ED: Energy Detection EDGE: Enhanced Data Rate for GSM Evolution EAS: Edge Application Server EASID: Edge Application Server Identification ECS: Edge Configuration Server ECSP: Edge Computing Service Provider EDN: Edge Data Network EEC: Edge Enable Client EECID: Edge Enable Client Identification EES: Edge Enable Server EESID: Edge Enable Server Identification EHE: Edge Host Environment EGMF: Exposure Governance Management Function EGPRS: Enhanced GPRS EIR: Equipment Identity Register eLAA: Enhanced Licensed Assisted Access, Enhanced LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB: evolved NodeB, E-UTRAN NodeB EN-DC: E-UTRA-NR Dual Connectivity EPC: evolved Packet Core EPDCCH: Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE: Energy per Resource Element EPS: evolved Packet System EREG: Enhanced REG, Enhanced Resource Element Group ETSI: European Telecommunications Standards Institute ETWS: Earthquake and Tsunami Warning System eUICC: embedded UICC, embedded Universal Integrated Circuit Card E-UTRA: evolved UTRA E-UTRAN: evolved UTRAN EV2X: Enhanced V2X F1AP: F1 Application Protocol F1-C: F1 Control Plane Interface F1-U: F1 User Plane Interface FACCH: Fast Associated Control Channel FACCH / F: Fast Associated Control Channel / Full Rate FACCH / H: Fast Associated Control Channel / Half Rate FACH: Forward Access Channel FAUSCH: Fast Uplink Signaling Channel FB: Functional Block FBI: Feedback Information FCC: Federal Communications Commission FCCH: Frequency Correction Channel FDD: Frequency Division Duplex FDM: Frequency Division Multiplexing FDMA: Frequency Division Multiple Access FE: Front End FEC: Forward Error Correction FFS: For Further Study FFT: Fast Fourier Transform feLAA: Further enhanced authorization support access, further enhanced LAA FN: Frame number FPGA: Field Programmable Gate Array FR: Frequency range FQDN: Fully Qualified Domain Name G-RNTI: GERAN Radio Network Temporary Identity GERAN: GSM Edge RAN, GSM Edge Radio Access Network GGSN: Gateway GPRS Support Node GLONASS: GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB: Next-generation NodeB gNB-CU: gNB Centralized Unit, Next-generation NodeB Centralized Unit gNB-DU: gNB Distributed Unit, Next-generation NodeB Distributed Unit GNSS: Global Navigation Satellite System GPRS General Packet Radio Service GPSI: General Public Subscription Identifier GSM: Global System for Mobile Communications, Groupe Special Mobile GTP: GPRS Tunneling Protocol GTP-U: GPRS Tunneling Protocol for the User Plane GTS: Go-to-Sleep signal (related to WUS) GUMMEI: Global Unique MME Identifier GUTI: Global Unique Temporary UE Identity HARQ: Hybrid ARQ, Hybrid Automatic Repeat Request HANDO: Handover HFN: Hyperframe Number HHO: Hard Handover HLR: Home Location Register HN: Home Network HO: Handover HPLMN: Home Public Land Mobile Network HSDPA: High Speed Downlink Packet Access HSN: Hopping Sequence Number HSPA: High Speed Packet Access HSS: Home Subscriber Server HSUPA: High Speed Uplink Packet Access HTTP: HyperText Transfer Protocol HTTPS: HyperText Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443) I-Block: Information Block ICCID: Integrated Circuit Card Identification IAB: Integrated Access and Backhaul ICIC: Inter-Cell Interference Coordination ID: Identity, Identifier IDFT: Inverse Discrete Fourier Transform IE: Information Element IBE: In-Band Emission IEEE: Institute of Electrical and Electronics Engineers IEI: Information Element Identifier IEIDL: Information Element Identifier Data Length IETF: Internet Engineering Task Force IF: Infrastructure IIOT: Industrial Internet of Things IM: Interference Measurement, Intermodulation, IP Multimedia IMC: IMS Credential IMEI: International Mobile Equipment Identity IMGI: International Mobile Group Identity IMPI: IP Multimedia Private Identity IMPU: IP Multimedia Public Identity IMS: IP Multimedia Subsystem IMSI: International Mobile Subscriber Identity IoT: Internet of Things IP: Internet Protocol Ipsec: IP Security, Internet Protocol Security IP-CAN: IP Connectivity Access Network IP-M: IP Multicast IPv4: Internet Protocol Version 4 IPv6: Internet Protocol Version 6 IR: Infrared IS: Synchronization IRP: Integrated Reference Point ISDN (Registered Trademark): Integrated Services Digital Network ISIM: IM Service Identification Module ISO: International Organization for Standardization ISP: Internet Service Provider IWF: Interworking Function I-WLAN: Interworking WLAN Constraint Length of Superimposed Code, USIM: Individual Key kB: Kilobyte (1000 bytes) kbps: Kilobits per Second Kc: Cryptographic Key Ki: Individual Subscriber Authentication Key KPI: Key Performance Indicator KQI: Key Quality Indicator KSI: Key Set Identifier ksps: Kilosymbols per Second KVM: Kernel Virtual Machine L1: Layer 1 (Physical Layer) L1-RSRP: Layer 1 Reference Signal Received Power L2: Layer 2 (Data Link Layer) L3: Layer 3 (Network Layer) LAA: Licensed-Assisted Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Life Cycle Management LCR: Low Chip Rate LCS: Location Service LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Lower Layer Compatibility LMF: Location Management Function LOS: Line of Sight LPLMN: Local PLMN LPP: LTE Positioning Protocol LSB: Least Significant Bit LTE: Long Term Evolution LWA: LTE-WLAN Aggregation LWIP: LTE / WLAN Radio Level Integration with IPsec Tunnel LTE: Long Term Evolution M2M: Machine to Machine MAC: Media Access Control (in the context of protocol layering) MAC: Message Authentication Code (in the context of security / encryption) MAC-A: MAC used for authentication and key sharing (in the context of TSG T WG3) MAC-I: MAC used for data integrity of signaling messages (in the context of TSG T WG3) MANO: Management and Orchestration MBMS: Multimedia Broadcast and Multicast Service MBSFN: Multimedia Broadcast Multicast Service Single Frequency Network MCC: Mobile Country Code MCG: Master Cell Group MCOT: Maximum Channel Occupancy Time MCS: Modulation and Coding Scheme MDAF: Management Data Analytics Function MDAS: Management Data Analytics Service MDT: Minimization of Drive Tests ME: Mobile Equipment MeNB: Master eNB MER: Message Error Ratio MGL: Measurement Gap Length MGRP: Measurement Gap Repetition Period MIB: Master Information Block, Management Information Base MIMO: Multiple-Input Multiple-Output MLC: Mobile Location Center MM: Mobility Management MME: Mobility Management Entity MN: Master Node MNO: Mobile Network Operator MO: Measurement Object, Mobile Originating MPBCH: MTC Physical Broadcast Channel MPDCCH: MTC Physical Downlink Control Channel MPDSCH: MTC Physical Downlink Shared Channel MPRACH: MTC Physical Random Access Channel MPUSCH: MTC Physical Uplink Shared Channel MPLS: Multi-Protocol Label Switching MS: Mobile Station MSB: Most Significant Bit MSC: Mobile Switching Center MSI: Minimum System Information, MCH Scheduling Information MSID: Mobile Station Identifier MSIN: Mobile Station Identification Number MSISDN: Mobile Subscriber ISDN Number MT: Mobile Terminated, Mobile Termination MTC: Machine-Type Communication mMTC: Massive MTC, Massive Machine-Type Communication MU-MIMO: Multi-User MIMO MWUS: MTC Wake-Up Signal, MTC WUS NACK: Negative Acknowledgment NAI: Network Access Identifier NAS: Non-Access Stratum, Non-Access Stratum layer NCT: Network Connectivity Topology NC-JT: Non-Coherent Joint Transmission NEC: Network Function Exposure NE-DC: NR-E-UTRA Dual Connectivity NEF: Network Exposure Function NF: Network Function NFP: Network Forwarding Path NFPD: Network Forwarding Path Descriptor NFV: Network Function Virtualization NFVI: NFV Infrastructure NFVO: NFV Orchestrator NG: Next Generation, Next Gen NGEN-DC: NG-RAN E-UTRA-NR Dual Connectivity NM: Network Manager NMS: Network Management System N-PoP: Network Point of Presence NMIB, N-MIB: Narrowband MIB NPBCH: Narrowband Physical Broadcast Channel NPDCCH: Narrowband Physical Downlink Control Channel NPDSCH: Narrowband Physical Downlink Shared Channel NPRACH: Narrowband Physical Random Access Channel NPUSCH: Narrowband Physical Uplink Shared Channel NPSS: Narrowband Primary Synchronization Signal NSSS: Narrowband Secondary Synchronization Signal NR: New Radio, Nearby Relationship NRF: NF Repository Function NRS: Narrowband Reference Signal NS: Network Service NSA: Non-Standalone Operation Mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Assistance Information S-NNSAI Single NSSAI NSSF: Network Slice Selection Function NW: Network NWUS: Narrowband Wake-up Signal, Narrowband WUS NZP: Non-zero Power O&M: Operation and Maintenance ODU2: Optical Channel Data Unit Type 2 OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access OOB: Out-of-band OOS: Out-of-synchronization OPEX: Operating Expenses OSI: Other System Information OSS: Operation Support System OTA: Over-the-air PAPR: Peak-to-Average Power Ratio PAR: Peak-to-Average Ratio PBCH: Physical Broadcast Channel PC: Power Control, Personal Computer PCC: Primary Component Carrier, Primary CC P-CSCF: Proxy CSCF PCell: Primary Cell PCI: Physical Cell ID, Physical Cell Identity PCEF: Policy and Charging Enforcement Function PCF: Policy Control Function PCRF: Policy Control and Charging Rules Function PDCP: Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer PDCCH: Physical Downlink Control Channel PDCP: Packet Data Convergence Protocol PDN: Packet Data Network, Public Data Network PDSCH: Physical Downlink Shared Channel PDU: Protocol Data Unit PEI: Permanent Equipment Identifier PFD: Packet Flow Description P-GW: PDN Gateway PHICH: Physical Hybrid ARQ Indicator Channel PHY: Physical Layer PLMN: Public Land Mobile Network PIN: Personal Identification Number PM: Performance Measurement PMI: Precoding Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: Push-to-Talk over Cellular PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH: Physical RACH PRB: Physical Resource Block PRG: Physical Resource Block Group ProSe: Proximity Service, Proximity-Based Service PRS: Positioning Reference Signal PRR: Packet Reception Radio PS: Packet Service PSBCH: Physical Sidelink Broadcast Channel PSDCH: Physical Sidelink Downlink Channel PSCCH: Physical Sidelink Control Channel PSSCH: Physical Sidelink Shared Channel PSCell: Primary SCell PSS: Primary Synchronization Signal PSTN: Public Switched Telephone Network PT-RS: Phase Tracking Reference Signal PTT: Push-to-Talk PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel QAM: Quadrature Amplitude Modulation QCI: QoS Class Identifier QCL: Quasi-Co-Location QFI: QoS Flow ID, QoS Flow Identifier QoS: Quality of Service QPSK: Quadrature (4-Phase) Phase Shift Keying QZSS: Quasi-Zenith Satellite System RA-RNTI: Random Access RNTI RAB: Radio Access Bearer, Random Access Burst RACH: Random Access Channel RADIUS: Remote Authentication Dial-In User Service RAN: Radio Access Network RAND: Random Number (used for authentication) RAR: Random Access Response RAT: Radio Access Technology RAU: Routing Area Update RB: Resource Block, Radio Bearer RBG: Resource Block Group REG: Resource Element Group Rel: Release REQ: Request RF: Radio Frequency RI: Rank Indicator RIV: Resource Indicator Value RL: Radio Link RLC: Radio Link Control, Radio Link Control Layer RLC AM: RLC Acknowledged Mode RLC UM: RLC Unacknowledged Mode RLF: Radio Link Failure RLM: Radio Link Monitoring RLM-RS: Reference Signal for RLM RM: Registration Management RMC: Reference Measurement Channel RMSI Residual MSI, Residual Minimum System Information RN: Relay Node RNC: Radio Network Controller RNL: Radio Network Layer RNTI: Radio Network Temporary Identifier ROHC: Robust Header Compression RRC: Radio Resource Control, Radio Resource Control Layer RRM: Radio Resource Management RS: Reference Signal RSRP: Reference Signal Received Power RSRQ: Reference Signal Received Quality RSSI: Received Signal Strength Indicator RSU: Road Side Unit RSTD: Reference Signal Time Difference RTP: Real-time Transport Protocol RTS: Request to Send RTT: Round Trip Time Rx: Reception, Receiving, Receiver S1AP: S1 Application Protocol S1-MME: S1 for Control Plane S1-U: S1 for User Plane S-CSCF: Serving CSCF S-GW: Serving Gateway S-RNTI: SRNC Radio Network Temporary Identity S-TMSI: SAE Temporary Mobile Station Identifier SA: Standalone Operation Mode SAE: System Architecture Evolution SAP: Service Access Point SAPD: Service Access Point Descriptor SAPI: Service Access Point Identifier SCC: Secondary Component Carrier, Secondary CC SCell: Secondary Cell SCEF: Service Capability Exposure Function SC-FDMA: Single Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management SCS: Subcarrier Spacing SCTP: Stream Control Transmission Protocol SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL: Supplementary Downlink SDNF: Structured Data Storage Network Function SDP: Session Description Protocol SDSF: Structured Data Storage Function SDT: Small Data Transmission SDU: Service Data Unit SEAF: Security Anchor Function SeNB: Secondary eNB SEPP: Security Edge Protection Proxy SFI: Slot Format Indication SFTD: Space-Frequency Time Diversity, SFN and Frame Timing Difference SFN: System Frame Number SgNB: Secondary gNB SGSN: Serving GPRS Support Node S-GW: Serving Gateway SI: System Information SI-RNTI: System Information RNTI SIB: System Information Block SIM: Subscriber Identity Module SIP: Session Initiation Protocol SiP: System in Package SL: SideLink SLA: Service Level Agreement SM: Session Management SMF: Session Management Function SMS: Short Message Service SMSF: SMS Function SMTC: SSB-Based Measurement Timing Configuration SN: Secondary Node, Sequence Number SoC: System on Chip SON: Self-Organizing Network SpCell: Special Cell SP-CSI-RNTI: Semi-Persistent CSI RNTI SPS: Semi-Persistent Scheduling SQN: Sequence Number SR: Scheduling Request SRB: Signaling Radio Bearer SRS: Sounding Reference Signal SS: Synchronization Signal SSB: Synchronization Signal Block SSID: Service Set Identifier SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator SSC: Session and Service Continuity SS-RSRP: Synchronization Signal Based Reference Signal Received Power SS-RSRQ: Synchronization Signal Based Reference Signal Received Quality SS-SINR: Synchronization Signal Based Signal-to-Noise and Interference Ratio SSS: Secondary Synchronization Signal SSSG: Search Space Set Group SSSIF: Search Space Set Indicator SST: Slice / Service Type SU-MIMO: Single-User MIMO SUL: Supplementary Uplink TA: Timing Advance, Tracking Area TAC: Tracking Area Code TAG: Timing Advance Group TAI: Tracking Area Identity TAU: Tracking Area Update TB: Transport Block TBS: Transport Block Size TBD: To Be Determined TCI: Transmission Configuration Indicator TCP: Transmission Control Protocol TDD: Time Division Duplexing TDM: Time Division Multiplexing TDMA: Time Division Multiple Access TE: Terminal Equipment TEID: Tunnel Endpoint Identifier TFT: Traffic Flow Template TMSI: Temporary Mobile Subscriber Identity TNL: Transport Network Layer TPC: Transmission Power Control TPMI: Transmission Precoding Matrix Indicator TR: Technical Report TRP, TRxP: Transmission / Reception Point TRS: Tracking Reference Signal TRx: Transceiver TS: Technical Specification TTI: Transmission Time Interval Tx: Transmission, Transmitting, Transmitter U-RNTI: UTRAN Radio Network Temporary Identity UART: Universal Asynchronous Receiver / Transmitter UCI: Uplink Control Information UE: User Equipment UDM: Unified Data Management UDP: User Datagram Protocol UDSF: Unstructured Data Storage Network Function UICC: Universal Integrated Circuit Card UL: Uplink UM: Unauthorized Mode UML: Unified Modeling Language UMTS: Universal Mobile Telecommunications System UP: User Plane UPF: User Plane Function URI: Uniform Resource Identifier URL: Uniform Resource Locator URLLC: Ultra-Reliable Low-Latency USB: Universal Serial Bus USIM: Universal Subscriber Identity Module USS: UE-Specific Search Space UTRA: UMTS Terrestrial Radio Access UTRAN: Universal Terrestrial Radio Access Network UwPTS: Uplink Pilot Time Slot V2I: Vehicle-to-Infrastructure V2P: Vehicle-to-Pedestrian V2V: Vehicle-to-Vehicle V2X: Vehicle-to-Everything VIM: Virtualization Infrastructure Manager VL: Virtual Link VLAN: Virtual LAN, Virtual Local Area Network VM: Virtual Machine VNF: Virtualized Network Function VNFFG: VNF Forwarding Graph VNFFGD: VNF Forwarding Graph Descriptor VNFM: VNF Manager VoIP: Voice over IP, Voice over Internet Protocol VPLMN: Visited Public Land Mobile Network VPN: Virtual Private Network VRB: Virtual Resource Block WiMAX (registered trademark): Worldwide Interoperability for Microwave Access WLAN: Wireless Local Area Network WMAN: Wireless Metropolitan Area Network WPAN: Wireless Personal Area Network X2-C: X2-Control Plane X2-U: X2-User Plane XML: Extensible Markup Language XRES: Expected User Response XOR: Exclusive OR ZC: Zadoff-Chu ZP: Zero Power Terms For the purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed in this specification.

[0117] As used herein, the term "circuit" refers to hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., that are configured to provide the described functionality, and that are part of, or include, these. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code used to execute the functions of that program code. In these embodiments, the combination of the hardware element and the program code may be referred to as a particular type of circuit.

[0118] As used herein, the term "processor circuit" refers to a circuit capable of continuously and automatically executing a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data, being part of, or including the same. The processing circuit may include one or more processing cores that execute instructions, and one or more memory structures that store programs and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-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. The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit". As used herein, the term "interface circuit" refers to a circuit that enables the exchange of information between two or more components or devices, being part of, or including the same. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0119] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be regarded as synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, reconfigurable mobile device, etc. Further, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0120] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be regarded as synonymous with and may be referred to as networked computer, networked hardware, network device, network node, router, switch, hub, bridge, wireless network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc., and / or may be referred to as such.

[0121] As used herein, the term "computer system" refers to any type of interconnected electronic device, computer device, or its components. Additionally, the term "computer system" and / or "system" may refer to various components of computers communicatively coupled to each other. Further, the term "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems communicatively coupled to each other and configured to share computing and / or networking resources.

[0122] As used herein, terms such as "appliance" and "computer appliance" refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide certain computing resources. A "virtual appliance" is a virtual machine image that virtualizes or emulates a computer appliance or is otherwise implemented by a hypervisor-based device dedicated to providing certain computing resources.

[0123] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "Hardware resources" may refer to computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc. by a virtualization infrastructure. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity for providing services and may include computing and / or network resources. System resources may be regarded as a set of coherent functions, network data objects, or services that are accessible through a server where such system resources exist on a single host or multiple hosts and are clearly identifiable.

[0124] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or a data stream. The term "channel" may be synonymous with and / or equivalent to any of the following terms: "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", and / or any other similar term that indicates a path or medium through which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0125] As used herein, terms such as "instantiate" and "instantiation" refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0126] The terms "couple" and "communicatively couple", along with their derivatives, are used herein. The term "couple" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly couple" may mean that two or more elements are in direct contact with each other. The term "communicatively couple" may mean that two or more elements can contact each other by communication, including through a wireless communication channel or link through a wire or other interconnect connection.

[0127] The term "information element" refers to a structural element that includes one or more fields. The term "field" refers to the individual content of an information element or data element that contains content.

[0128] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0129] The term "SSB" refers to the SS / PBCH block.

[0130] The term "primary cell" refers to the MCG cell operating on the primary frequency where the UE either performs the initial connection establishment procedure or starts the connection re-establishment procedure.

[0131] The term "primary SCG cell" refers to the SCG cell where the UE performs random access when executing the Reconfiguration with Sync procedure for DC operation.

[0132] The term "secondary cell" refers to the cell that provides additional radio resources on a special cell for a UE configured with CA.

[0133] The term "secondary cell group" refers to the serving cell including the PSCell and a subset of zero or more secondary cells for a UE configured with DC.

[0134] The term "serving cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell including the primary cell.

[0135] The term "serving cell" or "serving cells" refers to a set of cells including a special cell and all secondary cells for a UE in RRC_CONNECTED configured using CA.

[0136] The term "special cell" refers to the PCell of MCG or the PSCell of SCG in the case of DC operation; otherwise, the term "special cell" refers to the Pcell. [Other possible items] [Item 1] A user equipment (UE) comprising: One or more processors; and One or more computer-readable media having instructions wherein the instructions, when executed by the one or more processors, cause the UE to: Identify channel state information (CSI) for a wideband and one or more sub-bands of the wideband, where the CSI is related to the signal-to-interference-and-noise ratio (SINR) of the wideband and the SINR of each of the one or more sub-bands; Transmit a wideband channel quality index (CQI) report related to the CSI of the wideband; Identify, from the set of 2, 3, 4, and 5, the number of bits to be used for a sub-band CQI report related to one of the one or more sub-bands; and Transmit a sub-band CQI report based on the identified number of bits, where the sub-band CQI report is related to the CSI of the sub-band for the purpose of causing the above to be done. The UE [Item 2] The UE according to item 1, wherein the identified number of bits is based on an indication received from a base station. [Item 3] The UE according to any one of items 1 to 2, wherein the sub-band CQI report indicates that the sub-band has a spectral efficiency (SE) value higher than the highest possible SE value that can be signaled by a 4-bit CQI table. [Item 4] The UE according to item 3, wherein the CQI report indicates that the sub-band has an SE value at least Y bits / second / hertz (Hz) higher than the SE of the highest possible value indicated by a 4-bit CQI table, where Y is predefined or provided to the UE via upper layer signaling. [Item 5] The UE according to any one of items 1 to 2, wherein the sub-band CQI report indicates that the sub-band has an SE value smaller than the SE of the lowest possible valid CQI value that can be signaled by a 4-bit CQI table. [Item 6] The sub-band CQI report indicates that the sub-band has an SE value that is at least Z bits / second / Hertz (Hz) less than the SE of the minimum possible effective CQI value that can be indicated by the 4-bit CQI table, where Z is predefined or provided to the UE via upper layer signaling, the UE according to item 5. [Item 7] The UE according to any one of items 1 to 2, wherein the sub-band CQI report indicates a measured CQI of 0 corresponding to a spectral efficiency (SE) value that is at least Z bits / second / Hertz (Hz) less than the CQI value = 1. [Item 8] The UE according to any one of items 1 to 2, wherein the sub-band CQI report includes 2^(number of identified bits) levels with respect to the wideband CQI report, and the UE is further configured using A levels above the reported wideband CQI value and (2^(number of identified bits) - A) levels below the reported wideband CQI value. [Item 9] The UE according to item 8, wherein the value of A is specified as a function of the number of identified bits for the sub-band CQI report. [Item 10] The UE according to item 8, wherein the value of A is a function of the number of identified bits of the sub-band CQI report and the reported wideband CQI value. [Item 11] The UE according to any one of items 1 to 2, wherein all sub-bands are configured using 4-bit CQI reporting, and the sub-band CQI value is determined as the sum of the value reported by the UE in the sub-band CQI report and the value reported by the UE in the wideband CQI report interpreted as an offset having a range of [-8...+7] or [X...X+15], and the value of X is provided to the UE by the upper layer from the integers {-15,...,15}. [Item 12] The UE according to item 11, wherein when the sub-band CQI value is lower than 1 or higher than 15, the corresponding spectral efficiency (SE) is scaled. [Item 13] A base station, one or more processors; and one or more computer-readable media having instructions wherein the instructions, when executed by the one or more processors, cause the base station to identify, from a user equipment (UE), a wideband channel quality index (CQI) report related to the wideband; Processing the wideband CQI report to identify the wideband channel state information (CSI), where the wideband CSI is related to the signal-to-interference and noise ratio (SINR) of the wideband; Identifying, from the UE, a sub-band CQI report related to one of one or more sub-bands, where the sub-band CQI report is transmitted using 5 bits; and Processing the sub-band CQI report to identify the CSI of the sub-band, where the sub-band CSI is related to the SINR of the sub-band A base station for causing the above to be performed. [Item 14] The base station according to item 13, wherein the command is further for transmitting, to the UE, an indication that the sub-band CQI report is transmitted using a 5-bit CQI table. [Item 15] The base station according to any one of items 13 to 14, wherein the sub-band CQI report indicates that the sub-band has a spectral efficiency (SE) value higher than the highest possible SE value that the sub-band can be signaled by a 4-bit CQI table. [Item 16] The base station according to item 15, wherein the CQI report indicates that the sub-band has an SE value at least Y bits per second per hertz (Hz) higher than the SE of the highest possible value indicated by a 4-bit CQI table, where Y is predefined or provided to the UE via upper layer signaling. [Item 17] The base station according to any one of items 13 to 14, wherein the sub-band CQI report indicates that the sub-band has an SE value smaller than the SE of the lowest possible valid CQI value that the sub-band can be signaled by a 4-bit CQI table. [Item 18] The base station according to item 17, wherein the sub-band CQI report indicates that the sub-band has an SE value at least Z bits per second per hertz (Hz) smaller than the SE of the smallest possible valid CQI value indicated by a 4-bit CQI table, where Z is predefined or provided to the UE via upper layer signaling. [Item 19] The base station according to any one of Items 13 to 14, wherein the sub-band CQI report indicates a measured CQI of 0 corresponding to a spectral efficiency (SE) value that is at least Z bits / second / hertz (Hz) less than the CQI value = 1. [Item 20] The base station according to any one of Items 13 to 14, wherein the sub-band CQI report includes 2^(the number of bits used to transmit the sub-band CQI report) levels with respect to the wideband CQI report, and the UE is further configured using A levels exceeding the reported wideband CQI value and (2^(the number of bits used to transmit the sub-band CQI report) - A) levels less than the reported wideband CQI value. [Item 21] The base station according to Item 20, wherein the value of A is specified as a function of the number of identified bits for the sub-band CQI report. [Item 22] The base station according to Item 20, wherein the value of A is a function of the number of bits used to transmit the sub-band CQI report and the reported wideband CQI value. [Item 23] One or more computer-readable media comprising instructions that, when executed by the one or more processors, cause a user equipment (UE) to identify channel state information (CSI) for a wideband and one or more sub-bands of the wideband, where the CSI is related to the signal-to-interference and noise ratio (SINR) of the wideband and the SINR of each of the one or more sub-bands; transmit a wideband channel quality index (CQI) report related to the CSI of the wideband; identify, from the set of 2, 3, 4, and 5, the number of bits to be used for a sub-band CQI report related to one of the one or more sub-bands; and transmit a sub-band CQI report based on the identified number of bits, where the sub-band CQI report is related to the CQI of the sub-band for causing the above to be performed. One or more computer-readable media. [Item 24] One or more computer-readable media comprising instructions that, when executed by the one or more processors, cause a base station to Identifying, from a user equipment (UE), a wideband channel quality index (CQI) report related to the wideband; Processing the wideband CQI report to identify channel state information (CSI) of the wideband, where the CSI of the wideband is related to a signal-to-interference and noise ratio (SINR) of the wideband; Identifying, from the UE, a sub-band CQI report related to one of one or more sub-bands, where the sub-band CQI report is transmitted using 5 bits; and Processing the sub-band CQI report to identify CSI of the sub-band, where the CSI of the sub-band is related to an SINR of the sub-band One or more computer-readable media for causing the above to be performed.

Claims

1. A user equipment (UE), a memory storing identified channel state information (CSI) for a wideband and one or more sub-bands of the wideband, where the CSI is related to a signal-to-interference and noise ratio (SINR) of the wideband and a respective SINR of the one or more sub-bands; and one or more processors, transmitting a wideband channel quality index (CQI) report related to the CSI of the wideband; identifying, from a set of 2, 3, 4, and 5, a number of bits to be used for a sub-band CQI report for one of the one or more sub-bands; and transmitting a sub-band CQI report based on the identified number of bits, where the sub-band CQI report is related to the CSI of the sub-band one or more processors configured to perform and comprising, the sub-band CQI report indicates that the sub-band has a spectral efficiency (SE) value higher than a highest possible SE value that the sub-band can be signaled by a 4-bit CQI table, the sub-band CQI report indicates that the sub-band has an SE value that is at least Y bits / second / hertz (Hz) higher than the SE of the highest possible value indicated by a 4-bit CQI table, where Y is predefined or provided to the UE via upper layer signaling, UE.

2. The UE according to claim 1, wherein the identified number of bits is based on an indication received from a base station.

3. The UE according to claim 1 or 2, wherein the sub-band CQI report indicates that the sub-band has an SE value smaller than a spectral efficiency (SE) of a lowest possible valid CQI value that the sub-band can be signaled by a 4-bit CQI table.

4. The sub-band CQI report indicates that the sub-band has an SE value that is at least Z bits / second / Hertz (Hz) smaller than the SE of the lowest possible effective CQI value that can be indicated by the 4-bit CQI table, where Z is predefined or provided to the UE via upper layer signaling, the UE according to claim 3.

5. The sub-band CQI report indicates a measured CQI of 0 corresponding to an SE value that is at least Z bits / second / Hertz (Hz) smaller than CQI value = 1, the UE according to claim 1 or 2.

6. The sub-band CQI report includes 2^(number of identified bits) levels with respect to the wideband CQI report, and the UE is further configured using A levels that exceed the reported wideband CQI value and (2^(number of identified bits) - A) levels that are less than the reported wideband CQI value, the UE according to claim 1 or 2.

7. The value of A is specified as a function of the number of identified bits for the sub-band CQI report, the UE according to claim 6.

8. The value of A is a function of the number of identified bits of the sub-band CQI report and the reported wideband CQI value, the UE according to claim 6.

9. All sub-bands are configured using 4-bit CQI reporting, and the sub-band CQI value is determined as the sum of the 4-bit sub-band CQI value reported by the UE in the sub-band CQI report and the value reported by the UE in the wideband CQI report interpreted as an offset having a range of [-8...+7] or [X...X+15], where the value of X is provided to the UE by the upper layer from the set of integers {-15,...,15}, the UE according to claim 1 or 2.

10. The UE according to claim 9, wherein when the sub-band CQI value is lower than 1 or higher than 15, the corresponding spectral efficiency (SE) is scaled.

11. A base station, one or more processors; and one or more computer-readable media having instructions comprising, the instructions, when executed by the one or more processors, cause the base station to receive, from a user equipment (UE), a wideband channel quality index (CQI) report related to a wideband; process the received wideband CQI report to identify channel state information (CSI) of the wideband, wherein the CSI of the wideband is related to a signal-to-interference and noise ratio (SINR) of the wideband; receive, from the UE, a sub-band CQI report related to one of one or more sub-bands, wherein the sub-band CQI report is transmitted using 5 bits; and process the received sub-band CQI report to identify CSI of the sub-band, wherein the CSI of the sub-band is related to an SINR of the sub-band for performing, the sub-band CQI report indicates that the sub-band has a spectral efficiency (SE) value higher than the highest possible SE value that the sub-band can be signaled by a 4-bit CQI table, the sub-band CQI report indicates that the sub-band has an SE value at least Y bits / second / hertz (Hz) higher than the SE of the highest possible value indicated by a 4-bit CQI table, where Y is predefined or provided to the UE via upper layer signaling, a base station.

12. The base station according to claim 11, wherein the command is further for transmitting, to the UE, an indication that the sub-band CQI report is transmitted using a 5-bit CQI table.

13. The base station according to claim 11 or 12, wherein the sub-band CQI report indicates that the sub-band has an SE value smaller than a spectral efficiency (SE) of a lowest possible valid CQI value that the sub-band can be signaled by a 4-bit CQI table.

14. The base station according to claim 13, wherein the sub-band CQI report indicates that the sub-band has an SE value that is at least Z bits / second / hertz (Hz) smaller than the SE of the lowest possible valid CQI value indicated by a 4-bit CQI table, and Z is predefined or provided to the UE via upper layer signaling.

15. The base station according to claim 11 or 12, wherein the sub-band CQI report indicates a measured CQI of 0 corresponding to an SE value that is at least Z bits / second / hertz (Hz) smaller than CQI value = 1.

16. The base station according to claim 11 or 12, wherein the sub-band CQI report includes 2^(number of bits used to transmit the sub-band CQI report) levels with respect to the wideband CQI report, and the UE is further configured using A levels exceeding the reported wideband CQI value and (2^(number of bits used to transmit the sub-band CQI report) - A) levels less than the reported wideband CQI value.

Images