WO2018064182A1

WO2018064182A1 - Link adaptation for ultra-reliable low-latency communication

Info

Publication number: WO2018064182A1
Application number: PCT/US2017/053750
Authority: WO
Inventors: Sergey PANTELEEV; Alexey Vladimirovich Khoryaev; Andrey Chervyakov; Dmitry Belov
Original assignee: Intel Corporation
Priority date: 2016-09-30
Filing date: 2017-09-27
Publication date: 2018-04-05

Abstract

Embodiments of link adaptation for ultra-reliable low-latency communication (URLLC) are described. In some embodiments, a user equipment (UE) may encode, for transmission to a Base Station (BS), an indication of a requested reliability value and an indication of a requested latency value, which may be associated with an URLLC. In response to a disablement of a hybrid automatic repeat request (HARQ) operation, the UE may decode, from Radio Resource Control (RRC) signaling received from the BS, an indication of a block error rate (BLER) value, encode, for transmission to the BS, a channel state information (CSI) report, wherein the CSI report is based on the indication of the BLER value. The UE may decode, from signaling received from the BS on a shared channel, a transport block. In some embodiments, the transport block is encoded based on a set of transmission parameters, which may be determined from the CSI report.

Description

LINK ADAPTATION FOR ULTRA- RELIABLE LOW-LATENCY

COMMUNICATION

PRIORITY CLAIM

[0001] This application claims priority under 35 USC 119(e) to

United States Provisional Patent Application Serial No. 62/402,043 filed September 30, 2016, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to Long Term Evolution (LTE) systems. Some embodiments relate to methods, computer readable media, and apparatus for link adaptation, in particular for ultra-reliable low-latency communications (URLLC).

BACKGROUND

[0003] In current LTE systems, the basic closed loop link adaptation operation mode may be based on reporting, for example, channel state information (CSI) reporting. CSI reporting may comprise, for example, one or more channel quality indicators (CQI), rank indicators (RI), and precoding matrix indices (PMI). CSI reporting may be either periodic or aperiodic (e.g., event-triggered) and may be configured for multiple resource sets and multiple hypotheses to facilitate efficient multiple input multiple output (MIMO) and coordinated multipoint (CoMP) operation. Indicators (e.g., CQI and RI) and scheduling fairness may be used to predict spectrum efficiency and to assign suitable transmission parameters for a data transmission.

[0004] A CQI may be assumed to correspond to a spectrum efficiency value which is achieved at block error rate (BLER) of 10%, which may allow efficient use of spectrum resources. A data transmission may demand a minimum amount of spectrum resources to be successfully decoded at a receiver, however, additional spectrum resources may be consumed in instances where a hybrid automatic repeat request (HARQ) retransmission is triggered. An ultra-reliable low-latency communication (U LLC) may utilize a strict error rate target for a given time budget. A general key performance indicator (KPI) for a URLLC may be the achievement of 99.999% reliability within a latency of 1 ms. In some embodiments, a typical LTE operation may achieve a reliability of 90% within a latency of 4 ms and higher reliability values with higher latency values.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 illustrates an architecture of a system of a network in accordance with some embodiments;

[0006] FIG. 2 illustrates example components of a device in accordance with some embodiments;

[0007] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments;

[0008] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments;

[0009] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments;

[0010] FIG. 6 illustrates components of a core network in accordance with some embodiments;

[0011] FIG. 7 is a block diagram illustrating components, according to some example embodiments, of a system to support NFV;

[0012] FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium;

[0013] FIG. 9 illustrates an example operation of link adaptation, in accordance with some embodiments;

[0014] FIG. 10 illustrates an example operation of link adaptation, in accordance with some embodiments; [0015] FIG. 11 illustrates an example operation of link adaptation, in accordance with some embodiments;

[0016] FIG. 12 illustrates an example machine, in accordance with some embodiments.

DETAILED DESCRIPTION

[0017] FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments. For example, a system of a network that is configured to perform a spectrum-efficient ultra-reliable low-latency

communication (URLLC). In some embodiments, the URLLC may include channel state information (CSI) reporting (e.g., single or multiple CSI reporting) and dynamic hybrid automatic repeat request (HARQ) operations for link adaptation, as further described below.

[0018] The system 100 is shown to include a user equipment (UE) 101 and a UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[0019] In some embodiments, any of the UEs 101 and 102 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the

Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network. [0020] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1 10— the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0021] In this embodiment, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0022] The RAN 1 10 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0023] In accordance with some embodiments, the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division

Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 and 112 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0024] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 and 112 to the UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time- frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0025] The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs 101 and 102. The physical downlink control channel PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 111 and 112 based on channel quality information fed back from any of the UEs 101 and 102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

[0026] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCE s, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DO) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8).

[0027] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[0028] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120— via an SI interface 113. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl- mobility management entity (MME) interface 1 15, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0029] In this embodiment, the CN 120 comprises the MMEs 121 , the S-

GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related

information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0030] The S-GW 122 may terminate the S 1 interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0031] The P-GW 123 may terminate an SGi interface toward a PDN.

The P-GW 123 may route data packets between the EPC network 123 and e2ernal networks such as a network including the application server 130

(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

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

communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.

[0033] FIG. 2 illustrates example components of a device 200 in accordance with some embodiments. In some embodiments, the device 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 coupled together at least as shown. The components of the illustrated device 200 may be included in a UE or a RAN node. In some embodiments, the device 200 may include less elements (e.g., a RAN node may not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0034] The application circuitry 202 may include one or more

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

[0035] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processor(s) 204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), si2h generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functionality of baseband processors 204A-D may be included in modules stored in the memory 204G and executed via a Central Processing Unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 204 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other

embodiments.

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

[0037] In some embodiments, the baseband circuitry 204 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).

Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi- mode baseband circuitry.

[0038] RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.

[0039] In some embodiments, the receive signal path of the RF circuitry 206 may include mixer circuitry 206A, amplifier circuitry 206B and filter circuitry 206C. In some embodiments, the transmit signal path of the RF circuitry 206 may include filter circuitry 206C and mixer circuitry 206 A. RF circuitry 206 may also include synthesizer circuitry 206D for synthesizing a frequency for use by the mixer circuitry 206A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206 A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206D. The amplifier circuitry 206B may be configured to amplify the down-converted signals and the filter circuitry 206C may be a low- pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 204 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 206A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0040] In some embodiments, the mixer circuitry 206 A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206D to generate RF output signals for the FEM circuitry 208. The baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206C.

[0041] In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206 A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A of the transmit signal path may be configured for super-heterodyne operation.

[0042] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.

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

[0044] In some embodiments, the synthesizer circuitry 206D may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 206D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0045] The synthesizer circuitry 206D may be configured to synthesize an output frequency for use by the mixer circuitry 206A of the RF circuitry 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 206D may be a fractional N/N+l synthesizer.

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

[0047] Synthesizer circuitry 206D of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0049] FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

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

[0051] In some embodiments, the PMC 212 may manage power provided to the baseband circuitry 204. In particular, the PMC 212 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 212 may often be included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 212 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0052] While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204. However, in other embodiments, the PMC 2 12 may be additionally or alternatively coupled with, and perform similar power

management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.

[0053] In some embodiments, the PMC 212 may control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 200 may power down for brief intervals of time and thus save power.

[0054] If there is no data traffic activity for an extended period of time, then the device 200 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 200 may not receive data in this state, in order to receive data, it transitions back to RRC Connected state.

[0055] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable. [0056] Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0057] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 204 of FIG. 2 may comprise processors 204A-204E and a memory 204G utilized by said processors. Each of the processors 204A-204E may include a memory interface, 304A-304E, respectively, to send/receive data to/from the memory 204G.

[0058] The baseband circuitry 204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory e2ernal to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 316 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG. 2), a wireless hardware connectivity interface 318 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 320 (e.g., an interface to send/receive power or control signals to/from the PMC 212).

[0059] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane 400 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 1 1 1 (or alternatively, the RAN node 112), and the MME 121.

[0060] The PHY layer 401 may transmit or receive information used by the MAC layer 402 over one or more air interfaces. The PHY layer 401 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 405. The PHY layer 401 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MEVIO) antenna processing.

[0061] The MAC layer 402 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0062] The RLC layer 403 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 403 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 403 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[0063] The PDCP layer 404 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[0064] The main services and functions of the RRC layer 405 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE

measurement reporting. Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.

[0065] The UE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer 404, and the RRC layer 405.

[0066] The non-access stratum (NAS) protocols 406 form the highest stratum of the control plane between the UE 101 and the MME 121. The NAS protocols 406 support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 123.

[0067] The S 1 Application Protocol (S I - AP) layer 415 may support the functions of the SI interface and comprise Elementary⁷ Procedures (EPs). An EP is a unit of interaction between the RAN node 111 and the CN 120. The Sl-AP layer services may comprise two groups: UE-associated services and non UE- associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

[0068] The Stream Control Transmission Protocol (SCTP) layer

(alternatively referred to as the SCTP/IP layer) 414 may ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121 based, in part, on the IP protocol, supported by the IP layer 413. The L2 layer 412 and the LI layer 411 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0069] The RAN node 111 and the MME 121 may utilize an Sl-MME interface to exchange control plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and the Sl-AP layer 415.

[0070] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 500 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 1 1 1 (or alternatively, the RAN node 112), the S-GW 122, and the P-GW 123. The user plane 500 may utilize at least some of the same protocol layers as the control plane 400. For example, the UE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer 404.

[0071] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 504 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 111 and the S-GW 122 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer 41 1, the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. The S-GW 122 and the P-GW 123 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. As discussed above with respect to FIG. 4, NAS protocols support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 123.

[0072] FIG. 6 illustrates components of a core network in accordance with some embodiments. The components of the CN 120 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some

embodiments, Network Functions Virtualization (NFV) is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums

(described in further detail below). A logical instantiation of the CN 120 may be referred to as a net work slice 601. A logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice 602 (e.g., the network sub-slice 602 is shown to include the PGW 123 and the PCRF 126).

[0073] NF V architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

[0074] FIG. 7 is a block diagram illustrating components, according to some example embodiments, of a system 700 to support NFV. The system 700 is illustrated as including a virtualized infrastructure manager (VIM) 702, a network function virtualization infrastructure (NFVT) 704, a VNF manager (VNFM) 706, virtualized network functions (VNFs) 708, an element manager (EM) 710, an NFV Orchestrator (NFVO) 712, and a network manager (NM) 714.

[0075] The VIM 702 manages the resources of the NFVI 704. The NFVI 704 can include physical or virtual resources and applications (including hypervisors) used to execute the system 700. The VIM 702 may manage the life cycle of virtual resources with the NFVI 704 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0076] The VNFM 706 may manage the VNFs 708. The VNFs 708 maybe used to execute EPC components/functions. The VNFM 706 may manage the life cycle of the VNFs 708 and track performance, fault and security of the virtual embodiments of VNFs 708. The EM 710 may track the performance, fault and security of the functional embodiments of VNFs 708. The tracking data from the VNFM 706 and the EM 710 may comprise, for example, performance measurement (PM) data used by the VIM 702 or the NFVI 704. Both the VNFM 706 and the EM 710 can scale up/down the quantity of VNFs of the system 700.

[0077] The NFVO 712 may coordinate, authorize, release and engage resources of the NFVI 704 in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM 714 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 710).

[0078] FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840. For

embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800

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

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

[0081] The communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808. For example, the communication resources 830 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0082] Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor's cache memory), the memory/storage devices 820, or any suitable combination thereof. Furthermore, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the

memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.

[0083] In some embodiments, it may be desirable for a given radio access technology (RAT) to utilize one or more target block error rate (BLER) in providing a requested service reliability within a specified latency, for example, a service reliability value and a latency value requested from a user equipment (UE). In some embodiments, a particular RAT may perform spectrum-efficient ultra-reliable low-latency communication (URLLC). In some embodiments, a RAT may perform a URLLC that includes channel state information (CSI) reporting (e.g., single or multiple CSI reporting) and dynamic hybrid automatic repeat request (HARQ) operations. In some embodiments, the HARQ operation related to signal transmissions (e.g., transmission of one or more transport blocks) may be dynamically enabled or disabled, for example, dynamically enabled or disabled according to a requested reliability and a requested latency.

[0084] In some embodiments, a user equipment (UE) may request a specific service reliability (e.g., reliability percentage corresponding to a successful packet reception probability), such as a particular reliability value and a particular latency value, from a base station (BS), with respect to a URLLC. A BS, for example, may be an evolved NodeBs (eNBs) or next Generation NodeBs (gNB), although embodiments are not so limited. In some embodiments, in response to receiving signaling from a UE, specifying a requested service reliability, a BS may calculate a physical layer transmission reliability target. Further, the BS may determine whether to enable HARQ operation for a UE based on certain criteria. For example, criteria may include one or more of long- term channel propagation characteristics, the requested service reliability and latency, and/or a particular HARQ round trip time (RTT) supported by a network. In some embodiments, long-term characteristics may include channel quality information (e.g. channel path loss), reference signal received power (RSRP), reference signal received quality (RSRQ), and signal to interference noise ratio (SINR). In some embodiments, a BS (e.g., eNB, gNB) may configure HARQ operation for one or more UEs for link adaptation. For example, a BS may determine whether to dynamically enable or disable an HARQ operation with respect to a URLLC.

[0085] In some embodiments, the BS may make a semi-static decision of whether to enable an HARQ operation based on, for example, a priori information and the long-term characteristics. The a priori information may include a target latency and reliability (e.g., requested service reliability and latency requested by a UE). The BS (e.g., device of the BS) may analyze whether the BS may support the requested target latency and reliability. In some embodiments, the BS may determine whether the network and the BS can support the requested target latency and reliability by considering a particular frame structure, network configuration and the supported HARQ RTT. [0086] FIG. 9 illustrates an example operation of link adaptation, in accordance with some embodiments. For example, link adaptation with respect to a URLLC. It is important to note that embodiments of the method 900 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 9. In addition, embodiments of the method 900 are not necessarily limited to the chronological order that is shown in FIG. 9. In describing the method 900, reference may be made to FIGs. 1- 8 and 10-11, although it is understood that the method 900 may be practiced with any other suitable systems, interfaces and components.

[0087] In some embodiments, in 905, a BS may receive signaling from a

UE and may decode from the signaling an indication of a requested reliability value and an indication of a requested latency value (e.g., with respect to the URLLC). For example, a UE may transmit signaling including one or more of the indication of the requested reliability value and the indication of the requested latency value via Radio Resource Control (RRC) signaling (e.g., by an information element) or via a control channel (e.g., PDCCH) by a bit field in an uplink control indicator (UCI), although embodiments are not so limited. In some embodiments, a UE may transmit the signaling to the BS to initiate a URLLC for a downlink (DL) and/or uplink (UL) communication.

[0088] In 910, in some embodiments, the BS may make a determination to disable an HARQ operation, based on one or more of the indication of the requested reliabilit y value, the indication of the requested latency value, and one or more long-term channel characteristic indicators (e.g., indicating long-term channel characteristics). In 915, in response to determining to disable the HARQ operation, in some embodiments, the BS may calculate a first block error rate (BLER) value for channel state information (CSI) reporting by the UE. The BS may then communicate the first BLER value (e.g., to the UE), for example in 920, by encoding, for transmission to the UE, Radio Resource Control (RRC) signaling comprising an indication of the first BLER value. In some

embodiments, the BS may transmit the first BLER value to the UE through RRC signaling. However, embodiments are not so limited and the BS may transmit the first BLER value to the UE via a control channel (e.g., PDCCH) by a bit field in a UCI. The transmission of the first BLER value, in some embodiments, may be in accordance with a single-shot transmission operation, although embodiments are not so limited, and a BS may utilize a HARQ-based operation to transmit the first BLER value.

[0089] In some embodiments, in 925, the BS may decode a first CSI report, from signaling (e.g., RRC) received from the UE. For example, a UE may transmit a first CSI report to the BS in response to receiving the first BLER value from the BS and calculating the first CSI report based on the first BLER value. In some embodiments, in response to receiving the first CSI report from the UE, the BS, in 930, may calculate a first set of transmission parameters. For example, the first set of transmission parameters may be based on the first CSI report received from the UE. In some embodiments, transmission parameters may include one or more of a modulation and coding scheme (MCS), a frequency allocation size, a time domain allocation size, and/or a multiple input/multiple output (MEVIO) transmission scheme (e.g., with respect to one or more antennas of the UE), although embodiments are not limited as such. The BS, in some embodiments, may transmit signaling to the UE based on such transmission parameters. For example, in 935, the BS may encode a first transport block, based on the calculated first set of transmission parameters, for transmission to the UE. In some embodiments, the BS may transmit the first transport block on a shared channel (e.g., PDSCH). Further, the BS (e.g., processing circuitry and memory of an apparatus of the BS) may be configured to store, at least, the first CSI report and/or the first set of transmission parameters.

[0090] FIG. 10 illustrates an example operation of link adaptation, in accordance with some embodiments. For example, link adaptation with respect to a URLLC. It is important to note that embodiments of the method 1000 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 10. In addition, embodiments of the method 1000 are not necessarily limited to the chronological order that is shown in FIG. 10. In describing the method 1000, reference may be made to FIGs. 1-9 and 11, although it is understood that the method 1000 may be practiced with any other suitable systems, interfaces and components.

[0091] In some embodiments, in 1005, a BS may receive signaling from a UE and may decode from the signaling an indication of a requested reliability value and an indication of a requested latency value (e.g., with respect to the URLLC). For example, a UE may transmit signaling including one or more of the indication of the requested reliability value and the indication of the requested latency value via Radio Resource Control (RRC) signaling (e.g., by an information element) or via a control channel (e.g., PDCCH) by a bit field in a downlink control indicator (DO), although embodiments are not so limited. In some embodiments, a UE may transmit the signaling to the BS to initiate a URLLC for a downlink (DL) and/or uplink (UL) communication.

[0092] In 1010, in some embodiments, the BS may determine to enable an HARQ operation, based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long-term channel characteristic indicators (e.g., indicating long-term channel characteristics). In 1015, in response to determining to enable the HARQ operation, in some embodiments, the BS may calculate one or multiple BLER values (e.g., a first and second BLER value) for CSI reporting by the UE. The BS may then communicate the first BLER value and second BLER value (e.g., to the UE), for example in 1020, by encoding, for transmission to the UE, RRC signaling comprising an indication of the first BLER value and an indication of the second BLER value. In some embodiments, the BS may transmit the first BLER value and the second BLER value to the UE through RRC signaling. However, embodiments are not so limited and the BS may transmit one or more BLER values (e.g., the first BLER value and the second BLER value) to the UE via a control channel (e.g., PDCCH) by a bit field in a downlink control indicator (DCI).

[0093] In some embodiments, in 1025, the BS may decode one or multiple CSI reports (e.g., a first CSI report and a second CSI report), from signaling (e.g., RRC) received from the UE. For example, a UE may transmit a first CSI report and a second CSI report to the BS in response to receiving the first BLER value and the second BLER value from the BS and calculating the first CSI report and the second CSI report based on the first BLER value and the second BLER value. In some embodiments, the UE may not necessarily receive the first BLER value and the second BLER value simultaneously within signaling and may receive BLER values from the BS in separate signaling.

[0094] In some embodiments, in response to receiving one or more CSI reports (e.g., the first CSI report and the second CSI report) from the UE, the BS, in 1030, may calculate one or multiple sets of transmission parameters (e.g., a first set of transmission parameters and a second set of transmission parameters). For example, the first set of transmission parameters may be based on the first CSI report received from the UE and the second set of transmission parameters may be based on the second CSI report received from the UE. The UE, in some embodiments, may transmit multiple CSI reports within the same signaling or may transmit CSI reports within separate signaling. The transmission parameters may include one or more of a MCS, a frequency allocation size, a time domain allocation size, and/or a MIMO transmission scheme (e.g., with respect to one or more antennas of the UE), although embodiments are not limited as such.

[0095] The BS, in some embodiments, may transmit signaling to the UE based on such transmission parameters. For example, in 1035, the BS may encode one or multiple transport blocks, wherein a transport block may be based on a calculated set of transmission parameters (e.g., the first set of transmission parameters or the second set of transmission parameters). In some

embodiments, the BS may encode a first transport block, based on the first set of transmission parameters, and a second transport block, based on the second set of transmission parameters. In some embodiments, the BS may transmit the one or multiple transport blocks (e.g., the first transport block and the second transport block) on a shared channel (e.g., PDSCH). Further, the BS (e.g., processing circuitry and memory of an apparatus of the BS) may be configured to store, at least, the one or multiple CSI reports (e.g., the first CSI report and the second CSI report) and/or the one or multiple sets of transmission parameters (e.g., the first set of transmission parameters and the second set of transmission parameters).

[0096] In some embodiments, the BS may determine whether to transmit multiple transport blocks in response to receiving HARQ feedback from a UE. For example, in response to receiving a negative acknowledgment (e.g., NACK) from a UE (e.g., indicating a failure to decode a first transport block by the UE), a BS may transmit an additional transport block to a UE. FIG. 1 1 illustrates an example operation of link adaptation, in accordance with some embodiments. In some embodiments, in 1035, a BS may encode for transmission to a UE, a first transport block (e.g., the first transport block encoded based on the first set of transmission parameters). In response to receiving a NACK from the UE, in some embodiments, the BS may then encode a second transport block, in 1110.

[0097] In some embodiments, the BS may transmit the second transport block, according to the second set of transmission parameters, on a shared channel (e.g., PDSCH). In some embodiments, the BS may determine not to transmit multiple transport blocks in response to receiving HARQ feedback from the UE. For example, in response to receiving an acknowledgment (e.g., ACK) from the UE (e.g., indicating a successful decoding of a first transport block by the UE), a BS may refrain from transmitting an additional transport block to the UE. In some embodiments, in 1035, a BS may encode for transmission to a UE, the first transport block. In response to receiving an ACK, in some

embodiments, the BS may refrain from encoding the second transport block, in 1 115.

[0098] In some embodiments, to achieve a particular service reliability (e.g., including a requested reliability value and a latency value by a UE), including, in some embodiments a one-shot reception probability, a control channel reliability and a shared channel reliability may satisfy P < PCPD- Ι^β embodiments of a scheduling request (SR) based UL transmission, the P_C may correspond to a SR based successful reception probability and the downlink control channel reception probability may be P_C = P_grant ' PSR-

[0099] In some embodiments, a BS may configure a target BLER for

1

CQI reporting according to B = 1— P , where P is a target successful reception probability, according to 0 < P < 1, assuming P_C = P_D. In some embodiments, in response to receiving CQI feedback (e.g., a CQI report from a UE), a BS may map the CQI and the provided Rank Indicator (RI) and Precoding Matrix Index (PMI) to a corresponding spectrum efficiency value (SE) and utilize the value to allocate spectrum resources, M (^sec/tf_z), for a packet size S (bits), according to

-≤SE.

M

[00100] In some embodiments, a BS may utilize CQI values (e.g., based on a received CQI report) to determine one or more transmission parameters for an initial transmission (e.g., transport block) to a UE, as well as for a

retransmission (e.g., additional transport block) to the UE, however embodiments are not so limited, as a BS may also utilize PMI and RI to determine the one or more transmission parameters.

[00101] In embodiments where a BS selects transmission parameters for an initial transmission (e.g., first transport block) to a UE according to a first set of transmission parameters calculated based on a first CQI report (e.g., calculated for a first target BLER), the BS may select the first target BLER (e.g., first BLER value) for the initial transmission to provide spectrum efficiency gains assuming that a retransmission (e.g., second transport block) to the UE can recover transmission errors with a total reliability that meets a particular target service reliability (e.g., requested reliability value and requested latency value from the UE). In some embodiments, a second BLER value may correspond to a total service reliability targeted for a URLLC transmission. In some

embodiments, a BS may select target BLER values and transmission parameters for an initial transmission to a UE (e.g., first transport block) and for a retransmission to the UE (e.g., second transport block), within a given latency budget, according to equations (1) and (2)

[00102]

^{1 1}

[00103]

[00104] Where Mi corresponds to the amount of spectrum resources allocated to an initial transmission, and M₂ corresponds to the amount of resources allocated to a retransmission. In some embodiments, and eNB may apply latency constraints according to equations (3) and (4).

[00105]

[00106]

[00107] Where Li corresponds to the time allocated to an initial transmission, L₂ corresponds to the time allocated to a retransmission, LF corresponds to a particular latency for delivering HARQ feedback and scheduling the retransmission, and L corresponds to the available latency budget. In some embodiments, the available latency budget, L, may be dynamically determined based on a requested service latency and queuing (e.g., scheduling), Tx processing, and Rx processing delays.

[00108] In some embodiments, where equation (1) may not be satisfied for an available resource combination and transmission parameters according to equation (2), an eNB may dynamically disable an HARQ operation. In such embodiments, the eNB may assign a one-shot transmission which satisfies a given target service reliability. In some embodiments, if control channels are taken into account, assuming a single initial transmission and a single retransmission, a first BLER (Bi) and a second BLER (B₂) may be determined (e.g., by an eNB) according to equation (5).

[00110] Where Pc corresponds to control channel successful reception probability, PDTX corresponds to probability of detecting that feedback is not transmitted when control channel reception has failed, and PN corresponds to probability to successfully receive NACK feedback. In some embodiments, multiple CSI values for a given BLER target may be reported and measured for different sets of resources and may correspond to a pessimistic interference situation and realistic an interference situation. In some embodiments, a BS may analyze scheduling behavior of one or more neighboring BSs (e.g., eNBs, gNBs) to select a hypothesis for spectrum efficiency estimation in the presence of interference.

[00111] In some embodiments, the efficiency of HARQ may depend on multiple factors including channel propagation conditions and adaptive or non- adaptive retransmissions. With respect to channel propagation conditions, in some embodiments, the selectivity of a propagation channel may impact a spectrum efficiency needed to achieve a particular target BLER. A BLER curve slope may vary according to channel conditions for various UE and eNB configurations, as well as transmission modes. In some embodiments, applying HARQ retransmissions may affect the relative gains in spectrum efficiency. Further, in some embodiments, channel quality may impact the reliability of control channels with respect to ACK/NACK and CSI feedback. In some embodiments, adaptive retransmission (e.g., selection of transmission parameters and SE of a retransmission selected and signaled with a retransmission by a BS) may provide better SE gains due to the ability of the BS to select Mi and M₂ separately (e.g., according to equations (l)-(4)).

[00112] In some embodiments, a non-adaptive HARQ may be constrained by Mi=M₂, although non-adaptive HARQ enhancements may allow selection of different values of Mi and M₂ and may be configured for a particular UE. In some embodiments, constraints with respect to equation (2) may cause the applicability of HARQ to be limited for very small latency budget (L) values. In some embodiments, HARQ combining and channel coding may also affect the slope of a BLER curve and therefore impact the range of transmission parameters that can provide spectrum efficiency gains according to a particular latency constraint and reliability constraint.

[00113] In some embodiments, a BS may utilize semi-static signaling to configure HARQ. In such embodiments, the BS may determine whether to enable HARQ according to a requested service reliability, latency, data rate, and reported or measured long-term channel quality conditions (e.g., stored at the BS). In some embodiments, the BS may make a determination of whether to enable HARQ during a registration of services by a UE, and during connection setup and reconfiguration utilizing, for example, radio resource control signaling (RRC). In some embodiments, a configuration message may comprise a set of target BLER values for one or more CSI reports.

[00114] In some embodiments, the BS may utilize dynamic signaling to configure HARQ. In such embodiments, a BS may dynamically signal an indication of a request for feedback to a UE, for example, in a control channel (e.g., DO) format. Such signaling, in some embodiments, may be independent of a number of retransmissions from the BS. In some embodiments, for an adaptive HARQ, transmission parameters for a retransmission may be dynamically carried (e.g., in DCI) and may be valid for both DL and UL transmissions. In other embodiments, for a non-adaptive HARQ, retransmission parameters may not be updated dynamically (e.g., in an UL operation).

[00115] In such embodiments, the transmission parameters for the retransmission may be preconfigured, configured semi-statically, or signaled dynamically (e.g., in the initial DCI). In some embodiments, a dynamic DCI indication for retransmission may comprise a redundancy version index (RVI) for a synchronous retransmission. An additional index, in some embodiments, may be carried in an initial DCI corresponding to a preconfigured set of transmission parameters that may include one or more of a resource block (RB) assignment, a modulation encoding scheme (MCS), transmission power (e.g., for a UL transmission), a transmission time interval (TTI) duration, and

transmission mode, among other transmission parameters.

[00116] In some embodiments, for a grant-less UL transmission, a BS may configure a set of resources for grant-free UL transmission where the BS expects to receive data from a particular UE in either a contention-based or dedicated resource allocation manner. In such embodiments, a BS may detect a transmission from a UE in resources but may fail to decode a transport block. In such cases, the BS may transmit signaling to the UE (e.g., DCI) including an indication of an unsuccessful reception of the UE's transmission (e.g., within a NACK). In some embodiments, the BS may also include a resource grant for retransmission by the UE (e.g., in a dedicated or contention-based part of resources) and transmission parameters (e.g., RB assignment, MCS,

transmission power, a TTI duration, transmission mode) that may provide for a more reliable reception (e.g., by the BS) of the retransmission from the UE.

[00117] In some embodiments, a BS may configure a UE for one or more target BLER values (e.g., first BLER value, second BLER value for CSI reporting) utilizing, for example, dedicated RRC signaling. Configuration of the one or more target BLER values, in some embodiments, may be applied during a connection setup or reconfiguration as well as during a URLLC service registration. In some embodiments, a UE may report CQI values (e.g., to a BS) in an absolute scale (e.g., using X number of bits for each CQI value). A UE, in some embodiments, may report CQI to a BS in a relative manner. For example, if a second CQI value is reported, in addition to a first CQI value, a UE may report the second CQI value as an offset to the first CQI value according to

[00118] In such embodiments, a fewer number of bits may be used for reporting a second CQI value assuming that CQ^≥ CQI₂ when B > B₂.

Further, in some embodiments, the granularity of the offset may be variable depending on the value of CQI_t. For example, in instances when 0 > CQl_r > 9, three bits may be used to report _CQI with the granularity of 1, and in instances when 8 > CQ^ > 16, three bits may be used to report A_CQI with the granularity of 2, although embodiments are not so limited. In some embodiments, CSI reporting may be periodically calculated and reported (e.g., by a UE) to a BS or may be dynamically triggered. In embodiments of dynamic CSI reporting, a dynamic indication of CSI may be signaled along with ACK/NACK feedback for a given transmission. In such embodiments, a BS may utilize dynamically signaled CSI to determine transmission parameters, for example, for a retransmission to a UE to recover a transport block.

[00119] FIG. 12 illustrates a block diagram of an example machine 1200 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. Examples, as described herein, may include, or may operate by, logic or a number of components, or mechanisms in the machine 1200. Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the machine 1200 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, in an example, the machine readable medium elements are part of the circuitry or are

communicatively coupled to the other components of the circuitry when the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuitry. For example, under operation, execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the machine 1200 follow.

[00120] In alternative embodiments, the machine 1200 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1200 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 1200 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 1200 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[00121] The machine (e.g., computer system) 1200 may include a hardware processor 1202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1204, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) 1206, and mass storage 1208 (e.g., hard drive, tape drive, flash storage, or other block devices) some or all of which may communicate with each other via an interlink (e.g., bus) 1230. The machine 1200 may further include a display unit 1210, an alphanumeric input device 1212 (e.g., a keyboard), and a user interface (UI) navigation device 1214 (e.g., a mouse). In an example, the display unit 1210, input device 1212 and UI navigation device 1214 may be a touch screen display. The machine 1200 may additionally include a storage device (e.g., drive unit) 1208, a signal generation device 1218 (e.g., a speaker), a network interface device 1220, and one or more sensors 1216, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 1200 may include an output controller 1228, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[00122] Registers of the processor 1202, the main memory 1204, the static memory 1206, or the mass storage 1208 may be, or include, a machine readable medium 1222 on which is stored one or more sets of data structures or instructions 1224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1224 may also reside, completely or at least partially, within any of registers of the processor 1202, the main memory 1204, the static memory 1206, or the mass storage 1208 during execution thereof by the machine 1200. In an example, one or any combination of the hardware processor 1202, the main memory 1204, the static memory 1206, or the mass storage 1208 may constitute the machine readable media 1222. While the machine readable medium 1222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 1224.

[00123] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1200 and that cause the machine 1200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non- limiting machine readable medium examples may include solid-state memories, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon based signals, sound signals, etc.). In an example, a non-transitory machine readable medium comprises a machine readable medium with a plurality of particles having invariant (e.g., rest) mass, and thus are compositions of matter. Accordingly, non-transitory machine-readable media are machine readable media that do not include transitory propagating signals. Specific examples of non-transitory machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically

Programmable Read-Only Memory (EPROM), Electrically Erasable

Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto- optical disks; and CD-ROM and DVD-ROM disks.

[00124] The instructions 1224 may be further transmitted or received over a communications network 1226 using a transmission medium via the network interface device 1220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (HDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 1220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1226. In an example, the network interface device 1220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SEVIO), multiple-input multiple-output (MEVIO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 1200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software. A transmission medium is a machine readable medium.

[00125] Examples

[00126] Although an aspect has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. [00127] Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term "aspect" merely for convenience and without intending to voluntarily limit the scope of this application to any single aspect or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[00128] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

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

[00130] The following describes various examples of methods, machine- readable media, and systems (e.g., machines, devices, or other apparatus) discussed herein.

[00131] Example 1 is an apparatus of a user equipment (UE), the apparatus comprising: processing circuitry, configured to: encode, for transmission to a Base Station (BS), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra-reliable low latency communication (URLLC); in response to a disablement of a hybrid automatic repeat request (HARQ) operation, the disablement based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: decode, from Radio

Resource Control (RRC) signaling received from the BS, an indication of a first block error rate (BLER) value; encode, for transmission to the BS, a first channel state information (CSI) report, wherein the first CSI report is based on the indication of the first BLER value; and decode, from signaling received from the BS on a shared channel, a first transport block, wherein the first transport block is encoded based on a first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report; and memory configured to store one or more of the first BLER value and the first transport block.

[00132] In Example 2, the subject matter of Example 1 includes, wherein the processing circuitry is further configured to: in response to an enablement of the HARQ operation, the enablement based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and the one or more long term channel characteristic indicators: decode, from the RRC signaling received from the BS, the indication of the first BLER value and an indication of a second BLER value; encode, for transmission to the BS, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value and the second CSI report is based on the indication of the second BLER value; decode, from signaling received from the BS on a control channel, a first indication of an enablement of the HARQ operation; and decode, from the signaling received from the BS on the shared channel, the transport block, wherein the transport block is encoded based on the first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report.

[00133] In Example 3, the subject matter of Example 2 includes, wherein the processing circuitry is further configured to: decode, from signaling received from the BS on the control channel, a second indication of an enablement of the HARQ operation; and decode, from signaling received from the BS on the shared channel, a second transport block, wherein the second transport block is encoded based on a second set of transmission parameters, and wherein the second set of transmission parameters is determined from the second CSI report.

[00134] In Example 4, the subject matter of Example 3 includes, wherein the signaling is received from the BS in response to a transmission of a negative acknowledgement (NACK) from the UE to the BS.

[00135] In Example 5, the subject matter of Examples 2-4 includes, wherein the processing circuitry is further configured to encode the second CSI report as an offset to the first CSI report.

[00136] In Example 6, the subject matter of Examples 1-5 includes, wherein the BS is one of an evolved node-B (eNB) or a Next Generation

NodeBs (gNB).

[00137] Example 7 is an apparatus of a Base Station (BS), the apparatus comprising: processing circuitry, configured to: decode, from signaling received from a user equipment (UE), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra-reliable low latency communication (URLLC); in response to a determination to disable a hybrid automatic repeat request (HARQ) operation, the determination based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: calculate a first block error rate (BLER) value for channel state information (CSI) reporting by the UE; encode, for transmission to the UE, Radio Resource Control (RRC) signaling comprising an indication of the first BLER value; decode a first CSI report, from signaling received from the UE, wherein the first CSI report is based on the indication of the first BLER value; calculate a first set of transmission parameters based on the first CSI report; and encode a first transport block according to the first set of transmission parameters, for transmission to the UE on a shared channel; and memory configured to store one or more of the first CSI report and the first set of transmission parameters.

[00138] In Example 8, the subject matter of Example 7 includes, wherein the processing circuitry is further configured to: in response to a determination to enable a hybrid automatic repeat request (HARQ) operation, the determin ation based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: calculate the first BLER value and a second BLER value for CSI reporting by the UE; encode, for transmission to the UE, RRC signaling comprising an indication of the first BLER value and an indication of the second BLER value; decode, from signaling received from the UE, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value the second CSI report is based on the indication of the second BLER value; calculate the first set of

transmission parameters based on the first CSI report and a second set of transmission parameters based on the second CSI report; encode the first transport block according to the first set of transmission parameters, for transmission to the UE on the shared channel, and encode a first indication of an enablement of the HARQ operation, for transmission to the UE on a control channel; and in response to decoding, from signaling received from the UE, an indication of a negative acknowledgement (NACK), encode a second transport block according to the second set of transmission parameters, for transmission to the UE on the shared channel.

[00139] In Example 9, the subject matter of Examples 7-8 includes, wherein the processing circuitry is further configured to: in response to decoding, from signaling received from the UE, an indication of an

acknowledgement (ACK), configure the apparatus to refrain from encoding the second transport block. [00140] In Example 10, the subject matter of Examples 8-9 includes, wherein the processing circuitry is configured to: disable the HARQ operation dynamically for transmission of the first transport block or second transport block, according to the indication of the requested reliability value and the indication of the requested latency value.

[00141] In Example 11, the subject matter of Examples 8-10 includes, wherein the processing circuitry is configured to: enable the HARQ operation dynamically for transmission of the first transport block or the second transport block, according to the indication of the requested reliability value and the indication of the requested latency value.

[00142] In Example 12, the subject matter of Examples 8-11 includes, wherein the processing circuitry is configured to: encode the first indication of the enablement of the HARQ operation according to the first set of transmission parameters; and in response to decoding, from the signaling received from the UE, the indication of the NACK, encode a second indication of the enablement of the HARQ operation according to the second set of transmission parameters, for transmission to the UE on the control channel.

[00143] In Example 13, the subject matter of Example 12 includes, wherein the processing circuitry is configured to: select, according to the first CSI report, an aggregation level of the control channel for transmission, to the UE, of the first indication of the enablement of the HARQ operation; and select, according to the second CSI report, an aggregation level of the control channel for transmission, to the UE, of the second indication of the enablement of the HARQ operation.

[00144] In Example 14, the subject matter of Examples 8-13 includes, wherein the shared channel is a physical downlink shared channel (PDSCH) and the control channel is a physical downlink control channel (PDCCH).

[00145] In Example 15 , the subj ect matter of Exampl es 8- 14 includes, wherein any of the first set of transmission parameters and the second set of transmi ssion parameters includes one or more of a modulation and codi ng scheme (MCS), a frequency allocation size, and a time domain allocation size.

[00146] In Example 16, the subject matter of Examples 7-15 includes, wherein the one or more long term channel characteristic indicators include one or more indications of channel quality information, reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference noise ratio (SINR), and HARQ round trip time (RTT).

[00147] In Example 17, the subject matter of Examples 7-16 includes, wherein the processing circuitry is configured to: encode the first transport block, according to the first set of transmission parameters, for a single-shot transmission to the UE on a shared channel.

[00148] In Example 18, the subject matter of Examples 8-17 includes, wherein the processing circuitry is configured to: encode the first transport block according to the first set of transmission parameters and the second transport block according to second set of transmission parameters, for a single-shot transmission to the UE on a shared channel.

[00149] In Example 19, the subject matter of Examples 7-18 includes, wherein the BS is one of an evolved node-B (e B) or a Next

Generation NodeBs (gNB).

[00150] Example 20 is a computer-readable hardware storage device that stores instructions for execution by one or more processors of a User Equipment (UE), the instructions to configure the one or more processors to: encode, for transmission to a Base Station (BS), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra-reliable low latency communication (URLLC); and in response to a disablement of a hybrid automatic repeat request (HARQ) operation, the disablement based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: decode, from Radio Resource Control (RRC) signaling received from the BS, an indication of a first block error rate (BLER) value; encode, for transmission to the BS, a first channel state information (CSI) report, wherein the first CSI report is based on the indication of the first BLER value; and decode, from signaling received from the BS on a shared channel, a first transport block, wherein the first transport block is encoded based on a first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report . [00151] In Example 21, the subject matter of Example 20 includes, wherein the instructions are to further configure the one or more processors to: in response to an enablement of the HARQ operation, the enablement based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and the one or more long term channel characteristic indicators: decode, from the RRC signaling received from the BS, the indication of the first BLER value and an indication of a second BLER value; encode, for transmission to the BS, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value and the second CSI report is based on the indication of the second BLER value; decode, from signaling received from the BS on a control channel, a first indication of an enablement of the HARQ operation; and decode, from the signaling received from the BS on the shared channel, the transport block, wherein the transport block is encoded based on the first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report.

[00152] In Example 22, the subject matter of Example 21 includes, wherein the instructions are to further configure the one or more processors to: decode, from signaling received from the BS on the control channel, a second indication of an enablement of the HARQ operation; and decode, from signaling received from the BS on the shared channel, a second transport block, wherein the second transport block is encoded based on a second set of transmission parameters, and wherein the second set of transmission parameters is determined from the second CSI report.

[00153] In Example 23, the subject matter of Example 22 includes, wherein the signaling is received from the BS in response to a transmission of a negative acknowledgement (NACK) from the UE to the BS.

[00154] In Example 24, the subject matter of Examples 21-23 includes, wherein the instructions are to further configure the one or more processors to encode the second CSI report as an offset to the first CSI report.

[00155] Example 25 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1- 24. [00156] Example 26 is an apparatus comprising means to implement of any of Examples 1-24.

[00157] Example 27 is a system to implement of any of Examples 1- 24.

[00158] Example 28 is a method to implement of any of Examples 1- 24.

Claims

What is claimed is: 1. An apparatus of a user equipment (UE), the apparatus comprising: processing circuitry, configured to: encode, for transmission to a Base Station (BS), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra- reliable low latency communication (URLLC); in response to a disablement of a hybrid automatic repeat request (HARQ) operation, the disablement based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: decode, from Radio Resource Control RRC) signaling received from the BS, an indication of a first block error rate (BLER) value; encode, for transmission to the BS, a first channel state information (CSI) report, wherein the first CSI report is based on the indication of the first BLER value; and decode, from signaling received from the BS on a shared channel, a first transport block, wherein the first transport block is encoded based on a first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report; and memory configured to store one or more of the first BLER value and the first transport block.

2. The apparatus of claim 1, wherein the processing circuitry is further configured to: in response to an enablement of the HARQ operation, the enablement based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and the one or more long term channel characteristic indicators: decode, from the RRC signaling received from the BS, the indication of the first BLER value and an indication of a second BLER value; encode, for transmission to the BS, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value and the second CSI report is based on the indication of the second BLER value; decode, from signaling received from the BS on a control channel, a first indication of an enablement of the HARQ operation; and decode, from the signaling received from the BS on the shared channel, the transport block, wherein the transport block is encoded based on the first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report.

3. The apparatus of claim 2, wherein the processing circuitry is further configured to: decode, from signaling received from the BS on the control channel, a second indication of an enablement of the HARQ operation; and decode, from signaling received from the BS on the shared channel, a second transport block, wherein the second transport block is encoded based on a second set of transmission parameters, and wherein the second set of transmission parameters is determined from the second CSI report.

4. The apparatus of claim 3, wherein the signaling is received from the

BS in response to a transmission of a negative acknowledgement (NACK) from the UE to the BS.

5. The apparatus of claim 2, wherein the processing circuitry is further configured to encode the second CSI report as an offset to the first CSI report.

6. The apparatus of claim 1, wherein the BS is one of an evolved node-B (eNB) or a Next Generation NodeBs (gNB).

7. An apparatus of a Base Station (BS), the apparatus comprising: processing circuitry, configured to: decode, from signaling received from a user equipment (UE), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra-reliable low latency communication (U LLC); in response to a determination to disable a hybrid automatic repeat request (HARQ) operation, the determination based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: calculate a first block error rate (BLER) value for channel state information (CSI) reporting by the UE; encode, for transmission to the UE, Radio Resource

Control (RRC) signaling comprising an indication of the first BLER value; decode a first CSI report, from signaling received from the UE, wherein the first CSI report is based on the indication of the first BLER value; calculate a first set of transmission parameters based on the first CSI report; and encode a first transport block according to the first set of transmission parameters, for transmission to the UE on a shared channel; and memory configured to store one or more of the first CSI report and the first set of transmission parameters.

8. The apparatus claim 7, wherein the processing circuitry is further configured to: in response to a determination to enable a hybrid automatic repeat request (HARQ) operation, the determination based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: calculate the first BLER value and a second BLER value for CSI reporting by the UE; encode, for transmission to the UE, RRC signaling comprising an indication of the first BLER value and an indication of the second BLER value; decode, from signaling received from the UE, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value the second CSI report is based on the indication of the second BLER value; calculate the first set of transmission parameters based on the first CSI report and a second set of transmission parameters based on the second CSI report; encode the first transport block according to the first set of transmission parameters, for transmission to the UE on the shared channel, and encode a first indication of an enablement of the HARQ operation, for transmission to the UE on a control channel; and in response to decoding, from signaling received from the UE, an indication of a negative acknowledgement (NACK), encode a second transport block according to the second set of transmission parameters, for transmission to the UE on the shared channel.

9. The apparatus of any of claims 7-8, wherein the processing circuitry is further configured to: in response to decoding, from signaling received from the UE, an indication of an acknowledgement (ACK), configure the apparatus to refrain from encoding the second transport block.

10. The apparatus of any of claims 7-8, wherein the processing circuitry is configured to: disable the HARQ operation dynamically for transmission of the first transport block or second transport block, according to the indication of the requested reliability value and the indi cation of the requested latency value.

11. The apparatus of any of claims 7-8, wherein the processing circuitry is configured to: enable the HARQ operation dynamically for transmission of the first transport block or the second transport block, according to the indication of the requested reliability value and the indication of the requested latency value.

12. The apparatus of any of claims 7-8, wherein the processing circuitry is configured to: encode the first indication of the enablement of the HARQ operation according to the first set of transmission parameters; and in response to decoding, from the signaling received from the UE, the indication of the NACK, encode a second indication of the enablement of the HARQ operation according to the second set of transmission parameters, for transmission to the UE on the control channel.

13. The apparatus claim 12, wherein the processing circuitry is configured to: select, according to the first CSI report, an aggregation level of the control channel for transmission, to the UE, of the first indication of the enablement of the HARQ operation; and select, according to the second CSI report, an aggregation level of the control channel for transmission, to the UE, of the second indication of the enablement of the HARQ operation.

14. The apparatus claim 8, wherein the shared channel is a physical downlink shared channel (PDSCH) and the control channel is a physical downlink control channel (PDCCH).

15. The apparatus claim 8, wherein any of the first set of transmission parameters and the second set of transmission parameters includes one or more of a modulation and coding scheme (MCS), a frequency allocation size, and a time domain allocation size.

16. The apparatus of claim 7, wherein the one or more long term channel characteristic indicators include one or more indications of channel quality information, reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference noise ratio (SINR), and HARQ round trip time (RTT).

17. The apparatus of claim 7, wherein the processing circuitry is configured to: encode the first transport block, according to the first set of transmission parameters, for a single-shot transmission to the UE on a shared channel.

18. The apparatus claim 8, wherein the processing circuitry is configured to: encode the first transport block according to the first set of transmission parameters and the second transport block according to second set of

transmission parameters, for a single-shot transmission to the UE on a shared channel.

19. The apparatus of claim 7, wherein the BS is one of an evolved node-B (eNB) or a Next Generation NodeBs (gNB).

20. A computer-readable hardware storage device that stores instructions for execution by one or more processors of a User Equipment (UE), the instructions to configure the one or more processors to: encode, for transmission to a Base Station (BS), an indication of a requested reliability value and an indication of a requested latency value, wherein the indication of the requested reliability value and the indication of the requested latency value are associated with an ultra-reliable low latency communication (URLLC); and in response to a disablement of a hybrid automatic repeat request

(HARQ) operation, the disablement based on one or more of the indication of the requested reliability value, the indication of the requested latency value, and one or more long term channel characteristic indicators: decode, from Radio Resource Control (RRC) signaling received from the BS, an indication of a first block error rate (BLER) value; encode, for transmission to the BS, a first channel state information (CSI) report, wherein the first CSI report is based on the indication of the first BLER value; and decode, from signaling received from the BS on a shared channel, a first transport block, wherein the first transport block is encoded based on a first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report.

21. The computer-readable hardware storage device of claim 20, wherein the instructions are to further configure the one or more processors to: in response to an enablement of the HARQ operation, the enablement based on the one or more of the indication of the requested reliability value, the indication of the requested latency value, and the one or more long term channel characteristic indicators: decode, from the RRC signaling received from the BS, the indication of the first BLER value and an indication of a second BLER value; encode, for transmission to the BS, the first CSI report and a second CSI report, wherein the first CSI report is based on the indication of the first BLER value and the second CSI report is based on the indication of the second BLER value; decode, from signaling received from the BS on a control channel, a first indi cation of an enablement of the HARQ operation; and decode, from the signaling received from the BS on the shared channel, the transport block, wherein the transport block is encoded based on the first set of transmission parameters, and wherein the first set of transmission parameters is determined from the first CSI report.

22. The computer-readable hardware storage device of claim 21, wherein the instructions are to further configure the one or more processors to: decode, from signaling received from the BS on the control channel, a second indication of an enablement of the HARQ operation; and decode, from signaling received from the BS on the shared channel, a second transport block, wherein the second transport block is encoded based on a second set of transmission parameters, and wherein the second set of transmission parameters is determined from the second CSI report.

23. The computer-readable hardware storage device of claim 22, wherein the signaling i s received from the BS in response to a transmi ssion of a negative acknowledgement (NACK) from the UE to the BS.

24. The computer-readable hardware storage device of claim 21, wherein the instructions are to further configure the one or more processors to encode the second CSI report as an offset to the first CSI report.