WO2025169167A1

WO2025169167A1 - Indicating target bler to ue

Info

Publication number: WO2025169167A1
Application number: PCT/IB2025/051380
Authority: WO
Inventors: Sudha LOHANI; Zaigham KAZMI; Daniel CEDARHOLM; Rongyan Lin
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2024-02-08
Filing date: 2025-02-10
Publication date: 2025-08-14
Anticipated expiration: 2026-08-08

Abstract

A method, system and apparatus are disclosed. A network node configured to communicate with a user equipment (UE) is described. The network node is configured to and/or includes a radio interface and/or processing circuitry configured to determine at least one target block error rate (BEER) for the network node to achieve based on at least one parameter and transmit an indication to the UE indicating the at least one target BEER.

Description

INDICATING TARGET BLER TO UE

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular, to indicating a target Block Error Rate (BLER) to user equipment (UE).

Background

[0002] The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile UEs, as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0003] In a wireless network, the channel conditions may change, which may cause unexpected loss of data. If radio frequency (RF) conditions degrade, the same coding scheme that worked before may no longer work, and the receiver may fail to decode. In modern cellular networks, such as LTE or NR, transmitters can pick one of many different modulation and coding schemes (MCSs) from a predefined set of MCSs to meet the channel conditions. If RF conditions are below a predetermined threshold (e.g., bad conditions), the transmitter may select an MCS that uses lower modulation order and lower coding rate. If the channel conditions are good such as above the predetermined threshold, the transmitter may select an MCS that uses higher modulation order and higher coding rate.

[0004] Varying channels or varying channel conditions may be handled via link adaptation. For example, the transmitter may adapt its encoding (modulation order and coding rate) to the channel. A traditional approach to link adaptation is generally as follows:

1. Network internally maintains state of channel that is representative of Information Carrying Capacity of channel, e.g., Channel State For Link Adaptation (CS4LA). a. Downlink: Channel state information is provided by UE via Channel State Information (CSI) reports comprising of Channel Quality Indicator (CQI), Rank Indicator (RI), Reference Signal Received Power (RSRP), etc. i. The channel quality information (CQI) values are standardized by 3GPP. b. Uplink: Network can measure the uplink channel quality by measuring the uplink signal transmitted by UE. The uplink signal could be either user data or reference signal or both.

2. The network generally applies offset to estimated CS4LA (mapped from measured/reported channel state) to account for inaccuracies in the measurement and to account for the fact that the measured/reported values become less representative of the channel as time passes. The result is effective CS4LA. a. The offset is computed with a goal of achieving and maintaining a target Block Error Rate (BLER). See point 5-6 below. b. How the offset is applied could be a proprietary algorithm or public domain knowledge.

3. To transmit a packet over the air, the network maps effective CS4LA to a suitable MCS. The MCS values are standardized by 3GPP. a. Downlink: Network uses the MCS to encode the packet to be transmitted using the selected MCS. b. Uplink: Network informs UE of the chosen MCS, and the UE uses that MCS to encode the packet to be transmitted.

4. Transmitter sends a packet over the air using the selected MCS,

5. The transmitter receives feedback from the receiver if the receiver was able to successfully decode the transmitted packet or not, a. Downlink: Feedback is provided by the UE via HARQ feedback. b. Uplink: Network knows itself whether decoding succeeded or failed.

6. If the feedback is negative (NACK), the transmitter may decrease its CS4LA by a value stepdown. If the feedback is positive (ACK), the transmitter may increase its CS4LA by stepUp.

[0005] Generally stepdown is much larger than stepUp and proportional to target BLER, e.g., to support 1% BLER, a transmitter may use stepdown that is 100 times larger than stepUp, i.e.: stepdown = 100*stepUp.

[0006] One problem is that 3 GPP has defined two sets of CQI tables purporting to two different BLER targets:

1. CQI Table-1 and CQI Table-2 are associated with Target BLER of 10'¹. 2. CQI Table-3 is associated with Target BLER of 10'⁵.

[0007] More specifically, 3GPP TS 38.214 V17.4.0 (See Section 5.2.2.1) states:

Based on an unrestricted observation interval in time unless specified otherwise in this Clause, and an unrestricted observation interval in frequency, the UE shall derive for each CQI value reported in uplink slot n the highest CQI index which satisfies the following condition:

- A single PDSCH transport block with a combination of modulation scheme, target code rate and transport block size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CSI reference resource, could be received with a transport block error probability not exceeding:

- 0.1, if the higher layer parameter cqi-Table in CSI-ReportConfig configures 'tablel' (corresponding to Table 5.2.2. 1-2), or 'table2' (corresponding to Table 5.2.2. 1-3), or if the higher layer parameter cqi-Table in CSI-ReportConfig configures 'table4-rl7' (corresponding to Table 5.2.2. 1-5), or

- 0.00001, if the higher layer parameter cqi-Table in CSI-ReportConfig configures 'table3' (corresponding to Table 5.2.2.1-4).

[0008] This gives the UE some discretion on how to report CSI. The CSI reported by a UE is not an abstract representation of channel, rather a value that UE believes or estimates would help the system achieve the desired BLER target:

• 10'¹ if UE is configured with CQI table-1.

• 10'³ if UE is configured with CQI table-3.

[0009] However, some operators want a combination of different target BLERs and CQI/MCS tables as per their deployment scenario and consumer usage, e.g.:

• Some applications such as extended reality (XR), virtual reality (VR), and industrial internet of things (loT) may require a target BLER in between such as 10'³.

• Some operators want to use CQI table-3 and MCS table-3 with 10'¹ target BLER as this might give them more coverage.

• Some scenarios may require low target BLER such as 10'³ with CQI table- 1 and MCS table-1 because UEs may not support CQI table-3 and MCS table-3 but are running applications that require low target BLER.

[0010] Additionally, new research indicates that dynamically changing target BLER can increase spectral efficiency without compromising the quality of service. New methods also include machine learning to adapt the target BLER dynamically to changing RF channel condition for this purpose. This poses problem as the UE does not know what target BLER the network is trying to achieve. The UE only knows CQI/MCS table that it is configured with. Further, UEs may manipulate CSI reporting to try to achieve a BLER that is associated with the CQI/MCS table that it is configured with, while the network may be trying to achieve a different BLER. This creates two control loops at the opposite ends with opposite objectives.

[0011] FIGS. 1-6 show a comparison of CQI and RI reported by the UE when the network has a different target BLER and CQI table-3 is configured. Put differently, a comparison of CQI and RI reported by the UE (vendor 1) configured with CQI table 3 when network is targeting different target BLER is shown. For the comparison, tests were run with three different target BLER: 10-1, 10-2 and 10-3 . For all the tests, CQI table 3 is configured in the UE and the channel condition do not change. The plots present reported CQI, translation of reported CQI to spectral efficiency and reported rank in sequence from top to bottom. From the plots, it is clear that UE reported rank gets lower for higher target BLER and is lowest when the network targets 10-1 BLER.

[0012] When the network targets higher BLER than what the CQI table indicates, the network uses relatively more aggressive MCS and/or layers and thus the UE observes more NACKs, and hence higher BLER than that defined for CQI table 3 in 3GPP TS 38.214. The above example of FIGS. 1-6 are an indication that UE is trying to adapt the channel state report to achieve lower BLER because CQI table 3 is configured.

[0013] FIGS. 7-12 show the comparison of CQI and RI reported by the UE when the network has a different target BLER, and CQI table 1 is configured in the UE. Put differently, a comparison of CQI and RI reported by the UE (vendor 2) configured with CQI table 1 when network is targeting different target BLER is shown. For comparison, tests were run with two different target BLER : 10-1 and 10-3. For all the tests, the channel condition do not change. The plots present reported CQI, translation of CQI to spectral efficiency and reported rank in sequence from top to bottom. From the plots, it is clear that UE reported rank gets higher occasionally for lower target BLER. When network targets low BLER, UE observes lesser number of NACKs and hence lower BLER than that defined for CQI table 1 in 3GPP TS 38.214. The example shown in FIGS. 7-12 are an indication that UE adapts channel state report towards higher BLER to improve efficiency while maintaining the BLER indicated by CQI table configured.

[0014] Some conventional technology obtains additional information from UE to further optimize the link adaptation algorithm but does not consider problems described above. For example, some conventional technology provides a mechanism to obtain additional information from UE including ML based channel state prediction to help improve the link adaptation algorithm on the network side. However, there is no mechanism that solves the problem of both network and UE independently trying to achieve different target BLERs.

SUMMARY

[0015] Some embodiments advantageously provide methods, systems, and apparatuses for indicating a target Block Error Rate (BLER) to user equipment (UE).

[0016] Some embodiments provide indicating to the UE what target BLER the network node is trying to achieve. The target BLER may be provided via RRC signaling as a single target BLER or provided as a set of target BLERs. Which target BLER the network node is currently trying to achieve may be dynamically indicated via MAC CE, DCI or other mechanism. In some embodiments, there is no additional requirement on the UE, except to not try to achieve a different target BLER. The UE may either just follow the network directive and report CSI as per the actual channel state without additional manipulation or report CSI that may help achieve the indicated target BLER.

[0017] Some embodiments ensure that the UE is aware of what target BLER the network is trying to achieve so it does not attempt to force a different BLER target.

[0018] One or more benefits associated with one or more embodiments are:

• Avoiding running of two conflicting control loops between the network node and the UE.

• Optimizing the link adaptation with the assistance from the UE.

• Introduction of just one information element in existing signaling.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0019] FIGS. 1-6 show a comparison of CQI and RI reported by the UE when the network has a different target BLER and CQI table-3 is configured;

[0020] FIGS. 7-12 show the comparison of CQI and RI reported by the UE when the network has different target BLER, and CQI table 1 is configured in the UE; [0021] FIG. 13 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0022] FIG. 14 is a block diagram of a host computer communicating via a network node with a user equipment over an at least partially wireless connection according to some embodiments of the present disclosure;

[0023] FIG. 15 is a diagram illustrating example arrangements and methods implemented in a communication system including a host computer, a network node and a user equipment for executing a client application at a user equipment according to some embodiments of the present disclosure;

[0024] FIG. 16 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0025] FIG. 17 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0026] FIG. 18 shows an example link adaptation process according to some embodiments of the present disclosure;

[0027] FIG. 19 shows an example process for indicating a single target BLER value or a set of discrete values with an indication of active target BLR according to some embodiments of the present disclosure;

[0028] FIG. 20 shows another example process for indicating BLER according to some embodiments of the present disclosure; and

[0029] FIG. 21 shows an example system model, including a network node in communication with multiple UEs.

DETAILED DESCRIPTION

[0030] Before describing in detail representative embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to indicating a target Block Error Rate (BLER) to user equipment (UE). Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0031] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0032] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication.

[0033] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

[0034] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0035] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0036] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0037] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0038] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and/or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. [0039] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0040] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 13 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0041] Also, it is contemplated that a UE 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

[0042] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0043] The communication system of FIG. 13 as a whole enables connectivity between one of the connected UEs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected UEs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected UE 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the UE 22a towards the host computer 24.

[0044] A network node 16 is configured to include a node management unit 32 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., network node functions. A user equipment 22 is configured to include a UE management unit 34 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., UE functions.

[0045] Example implementations, in accordance with an embodiment, of the UE 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0046] Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0047] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a UE 22 connecting via an OTT connection 52 terminating at the UE 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the user equipment 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to observe/monitor/ control/transmit to/receive from the network node 16 and or the user equipment 22.

[0048] The communication system 10 further includes a network node 16 provided in a communication system 10 and includes hardware 58 enabling it to communicate with the host computer 24 and with the UE 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

[0049] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0050] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include node management unit 32 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., network node functions.

[0051] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

[0052] The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0053] Thus, the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the UE 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the UE 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0054] The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 84 of the user equipment 22 may include a UE management unit 34 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., UE functions.

[0055] In some embodiments, the inner workings of the network node 16, UE 22, and host computer 24 may be as shown in FIG. 14 and independently, the surrounding network topology may be that of FIG. 13.

[0056] In FIG. 14, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the user equipment 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0057] The wireless connection 64 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0058] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and UE 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the UE 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’ s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0059] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the UE 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the UE 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the UE 22.

[0060] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a UE 22 to a network node 16. In some embodiments, the UE 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

[0061] Although FIGS. 13 and 14 show various “units” such as node management unit 32, and UE management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. FIG. 15 shows a communication diagram of a host computer 24 communicating via a network node 16 with a UE 22 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE 22, network node 16, and host (such as host computer 24) discussed in the preceding paragraphs will now be described with reference to FIG. 15.

[0062] Embodiments of host computer 24 include hardware, such as a communication interface, processing circuitry, and memory. The host computer 24 also includes software, which is stored in or accessible by the host computer 24 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 22 connecting via an over-the-top (OTT) connection 52 extending between the UE 22 and host computer 24. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 52.

[0063] The network node 16 includes hardware enabling it to communicate with the host computer 24 and UE 22. The connection 66 may be direct or pass through a core network (like core network 14 in FIG. 13) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0064] The UE 22 includes hardware and software, which is stored in or accessible by UE 22 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 22 with the support of the host computer 24. In the host computer 24, an executing host application may communicate with the executing client application via the OTT connection 52 terminating at the UE 22 and host computer 24. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 52.

[0065] The OTT connection 52 may extend via a connection 66 between the host computer 24 and the network node 16 and via a wireless connection 64 between the network node 16 and the UE 22 to provide the connection between the host computer 24 and the UE 22. The connection 66 and wireless connection 64, over which the OTT connection 52 may be provided, have been drawn abstractly to illustrate the communication between the host computer 24 and the UE 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0066] As an example of transmitting data via the OTT connection 52, in Block SI 00, the host computer 24 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 22. In other embodiments, the user data is associated with a UE 22 that shares data with the host computer 24 without explicit human interaction. In step Block SI 02, the host computer 24 initiates a transmission carrying the user data towards the UE 22. The host computer 24 may initiate the transmission responsive to a request transmitted by the UE 22. The request may be caused by human interaction with the UE 22 or by operation of the client application executing on the UE 22. The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in Block SI 04, the network node 16 transmits to the UE 22 the user data that was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In Block S106, the UE 22 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 22 associated with the host application executed by the host computer 24.

[0067] In some examples, the UE 22 executes a client application which provides user data to the host computer 24. The user data may be provided in reaction or response to the data received from the host computer 24. Accordingly, in Block SI 08, the UE 22 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 22. Regardless of the specific manner in which the user data was provided, the UE 22 initiates, in Block SI 10, transmission of the user data towards the host computer 24 via the network node 16. In Block SI 12, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the UE 22 and initiates transmission of the received user data towards the host computer 24. In Block SI 14, the host computer 24 receives the user data carried in the transmission initiated by the UE 22.

[0068] One or more of the various embodiments improve the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 forms the last segment. More precisely, the teachings of these embodiments may improve e.g., data rate, latency, power consumption, and thereby provide benefits such as reduced user waiting time, better responsiveness, extended battery lifetime, etc..

[0069] In an example scenario, factory status information may be collected and analyzed by the host computer 24. As another example, the host computer 24 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host computer 24 may collect and analyze realtime data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host computer 24 may store surveillance video uploaded by a UE. As another example, the host computer 24 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host computer 24 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[0070] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and UE 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host computer 24 and/or UE 22. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 16. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host computer 24. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while monitoring propagation times, errors, etc.

[0071] FIG. 16 is a flowchart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the node management unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to determine (Block SI 00) at least one target block error rate (BLER) for the network node 16 to achieve based on at least one parameter and transmit (Block SI 02) an indication to the UE 22 indicating the at least one target BLER.

[0072] In some embodiments, the method further includes receiving a capability indication from the UE 22 indicating the UE 22 supports receiving the at least one target BLER from the network node 16.

[0073] In some other embodiments, the at least one target BLER is based on an operator configuration for a cell for at least for the UE 22.

[0074] In some embodiments, the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE 22 and/or UE type.

[0075] In some other embodiments, the at least one target BLER includes a set of target BLER, and the method further includes transmitting another indication of an active target BLR in the set.

[0076] In some embodiments, the indication is transmitted via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.

[0077] FIG. 17 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the UE management unit 34), processor 86, radio interface 82 and/or communication interface 60. User equipment 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to receive (Block SI 04) an indication from the network node 16 indicating the at least one target block error rate (BLER) for the network node 16 to achieve, where the at least one target BLER is based on at least one parameter, determine (Block SI 06) the at least one target BLER based on the indication, and perform (Block SI 08) at least one action based on the determination.

[0078] In some embodiments, the method further includes transmitting a capability indication to the network node indicating the UE 22 supports receiving the at least one target BLER from the network node 16.

[0079] In some other embodiments, the at least one target BLER is based on an operator configuration for a cell for at least for the UE 22. [0080] In some embodiments, the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE 22 and/or UE type.

[0081] In some other embodiments, the at least one target BLER includes a set of target BLER, and the method further includes receiving another indication of an active target BLR in the set.

[0082] In some embodiments, the indication is received via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.

[0083] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for indicating a target Block Error Rate (BLER) to user equipment (UE).

[0084] FIG. 18 shows an example link adaptation process. At step S200, the network node 16 (e.g., gNB) initializes and stores CS4LA value, and at step S202, the UE 22 transmits CSI periodically. At step S204, network node 16 updates CS4LA, and at step S206, an MCS is selected based on CS4LA. At step S208, the network node 16 transmits packet with the selected MCS, and at step S210, the UE 22 attempts to decode. At step S212, feedback such as ACK/NACK is transmitted by UE 22, and at step S214, network node 16 updates CS4LA. At step S216, network node 16 determines a new MCS based on updated CS4LA, selected for the next transmission. The steps of FIG. 18 may be associated with one or more steps corresponding to downlink or uplink, which may include one or more of the following:

Downlink:

[0085] StepO: Network node 16 starts by initializing CS4LA to a default initial value.

[0086] Stepl: UE 22 periodically monitors the channel and provide channel state information (CSI) that may include Channel Quality Indicator (CQI), signal strength (RSRP, RSRQ), Rank Indicator (RI), Precoding Matrix Indicator (PMI) and other parameters.

[0087] Stepl: Network node 16 uses CSI to compute CS4LA of the channel. [0088] Step3: To transmit a packet in the downlink, network node 16 maps CS4LA to an MCS and uses that MCS to encode and modulate the bits to be transmitted. The packet is transmitted over the air.

[0089] Step4: UE 22 attempts to decode the packet. If packet is decoded successfully, UE sends ACK to the gNB. If decoding fails, it sends NACK.

[0090] Step5: Network node 16 uses feedback from the UE 22 to update the stored CS4LA value.

• If feedback was ACK, CS4LA is increased.

• If feedback was NACK, CS4LA is decreased.

[0091] Step6: For the next transmission, network node 16 uses the updated CS4LA to determine MCS for encoding and modulating the data.

[0092] StepO: Network node 16 starts by initializing CS4LA to a default initial value.

[0093] Stepl: To schedule a UE 22 in the uplink and grant resources for uplink transmission, network node 16 maps stored CS4LA to an MCS and provides that MCS to UE 22. UE 22 uses that MCS to encode and modulate the bits to be transmitted. The packet is transmitted over the air.

[0094] Stepl: Network node 16 attempts to decode the packet.

[0095] Step3: Network node 16 uses decoding result to update the stored CS4LA value.

• If decoding was successful, CS4LA is increased.

• If decoding failed, CS4LA is decreased.

[0096] Step4: Network node 16 may also use other parameters to update the CS4LA, e.g., SINR of the received packet on the uplink.

[0097] Step5: For the next transmission, network node 16 uses the updated CS4LA to determine MCS for encoding and modulating the data and provides that MCS to the UE 22 for the next transmission.

[0098] Performing the steps of the process shown in FIG. 18 may result in UE 22 trying to achieve a target BLER that is different from the network node 16, e.g.: • If BLER target of network node 16 is different than that specified in 3GPP standards for the configured CQI Table, UE 22 may report either too conservatively or too aggressively depending on the CQI table configured.

• Such channel state report may also impact control channel performance as well.

[0099] One or more embodiments of the present disclosure provide indicating the BLER target. The link adaptation algorithm on the network node side may perform or achieve one or more of the following:

• UE 22 connects to the network node 16 and indicates whether it supports accepting indication of target BLER from the network node 16.

• Network node 16 determines the target BLER for that UE 22. The target BLER o May be configured by the operator for the cell for all UEs 22. o Could be selected based on the UE characteristics, e.g., QoS required by the application, UE type, etc.

• Network node 16 indicates the target BLER to the UE 22.

[0100] FIG. 19 shows an example process for indicating a single target BLER value or a set of discrete values with an indication of active target BLR to the UE 22 in an RRC Reconfiguration message. At step S300, an RRC connection is established, at step S302, the network node 16 selects a target BLER, and at step S304, the network node 16 transmits a UE capability enquiry. At step S306, the UE confirms that it supports BLER indications. At step S308, an RRC reconfiguration is performed. At step S310, UE 22 transmits a message indicating that RRC reconfiguration is complete. At step S311, the UE may consider configured target BLER, and at step S312, transmit a CSI report. At step S314, UE 22 receives data transfer, and at step S316, transmits HARQ feedback. At step S318, network node 16 adjust channel state estimate and selects MCS. At step S320, data transfer is performed.

[0101] FIG. 20 shows another example process for indicating BLER. The network node 16 may indicate a single target BLER value or a set of discrete values with an indication of active target BLR to the UE 22 in an RRC Reconfiguration message. Later, UE 22 starts an application that results in a change in target BLER. More specifically, at step S400, an RRC connection is established, at step S402, the network node 16 selects a target BLER, and at step S404, the network node 16 transmits a UE capability enquiry. At step S406, the UE 22 confirms that it supports BLER indications. At step S408, an RRC reconfiguration is performed. At step S410, UE 22 transmits a message indicating that RRC reconfiguration is complete. At step S412, link adaptation is performed, with the target BLER. At step S414, UE 22 starts XR game, and at step S416, DRB setup is performed. At step S418, UE 22 received MAC CE, and at step S420, link adaptation is performed with another BLER. The target BLER may be indicated to the UE 22 via RRC reconfiguration, via MAC CE, or via DCI in both of the examples shown in FIGS. 19 and 20.

[0102] Some embodiments provide an RRC information element (IE) such as:

RRC IE :

PDSCH-Config : : = SEQUENCE { dlbler-targetSet-rlxx sequence { activeBlerTarget Bier-Target OPTIONAL, dlBler-TargetList ( S I ZE ( 1 . . maxBlerTarget ) ) OF Bler- target OPTIONAL, }

}

Bier-Target : : = ENUMERATED { 10% , 1 % , 0 . 1 % , 0 . 01 % . . . }

MaxBlerTarget INTEGER : : = 8

[0103] The first value in dlbler-targetList stands for activeBlerlndex 0 in MAC CE, the 2^nd value stands for activeBlerlndex 1, etc. If the IE activeBlerTarget is absent, the default value may be up to UE implementation.

[0104] Some other embodiments provide for MAC CE (e.g., BLER MAC CE) and downlink control information (DCI) such as:

MAC CE:

DCI:

In DCI format 1 1 and DCI format 1 2, a new field may be added, such as: ActiveBlerlndex: 0, or [log2(7)] bit, where I is number of entries in dlBler- TargetList if present. [0105] FIG. 21 shows an example system model, including a network node 16 in communication with multiple UEs 22 (e.g., UEs 22a, 22b, 22c, 22d). More specifically, network node 16 communicates with multiple UEs 22 over an RF channel. The UEs 22 may require different target BLER either due to running different applications or being in different channel conditions or being a member of different service class. If a UE 22 supports, the network node 16 can indicate the UE 22 specific target BLER to the UE 22. The target BLER for any given UE 22 may also be changed through the life of the UE 22 or network node 16. In that case, the network node may indicate the new target BLER to the UE 22.

[0106] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD- ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0107] Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. [0108] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0109] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0110] It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0111] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a standalone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0112] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0113] Abbreviations that may be used in the preceding description include:

BLER Block Error Rate

CQI Channel Quality Indicator

CS4LA Channel State For Link Adaptation gNB gNodeB

HARQ Hybrid Automatic Repeat Request

ICC Information Carrying Capacity

LA Link Adaptation

LTE Long-Term Evolution

MCS Modulation and Coding Scheme

NR New Radio

NS A Non Stand Alone

PDSCH Physical Data Shared Channel

RA Random Access

RAR Random Access Response

RF Radio Frequency

RSRP Reference Signal Received Power

SA Stand Alone

SINR Signal-to-Interference-plus-Noise Ratio

UE User Equipment

[0114] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Claims

Claims: What is claimed is:

1. A network node configured to communicate with a user equipment (UE), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine at least one target block error rate (BLER) for the network node to achieve based on at least one parameter; and transmit an indication to the UE indicating the at least one target BLER.

2. The network node of claim 1, wherein the network node is further configured to: receive a capability indication from the UE indicating the UE supports receiving the at least one target BLER from the network node.

3. The network node of any one of claims 1 and 2, wherein the at least one target BLER is based on an operator configuration for a cell for at least for the UE.

4. The network node of any one of claims 1-3, wherein the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE and/or UE type.

5. The network node of any one of claims 1 -4, wherein the at least one target BLER includes a set of target BLER, and the network node is configured to transmit another indication of an active target BLR in the set.

6. The network node of any one of claims 1-5, wherein the indication is transmitted via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.

7. A method implemented in a network node configured to communicate with a user equipment (UE), the method comprising: determining at least one target block error rate (BLER) for the network node to achieve based on at least one parameter; and transmitting an indication to the UE indicating the at least one target BLER.

8. The method of claim 7, wherein the method further includes: receiving a capability indication from the UE indicating the UE supports receiving the at least one target BLER from the network node.

9. The method of any one of claims 7 and 8, wherein the at least one target BLER is based on an operator configuration for a cell for at least for the UE.

10. The method of any one of claims 7-9, wherein the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE and/or UE type.

11. The method of any one of claims 7-10, wherein the at least one target BLER includes a set of target BLER, and the method further includes transmitting another indication of an active target BLR in the set.

12. The method of any one of claims 7-11, wherein the indication is transmitted via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.

13. A user equipment (UE) configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive an indication from the network node indicating the at least one target block error rate (BLER) for the network node to achieve, the at least one target BLER being based on at least one parameter; determine the at least one target BLER based on the indication; and perform at least one action based on the determination.

14. The UE of claim 13, wherein the UE is further configured to: transmit a capability indication to the network node indicating the UE supports receiving the at least one target BLER from the network node.

15. The UE of any one of claims 13 and 14, wherein the at least one target BLER is based on an operator configuration for a cell for at least for the UE.

16. The UE of any one of claims 13-15, wherein the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE and/or UE type.

17. The UE of any one of claims 13-16, wherein the at least one target BLER includes a set of target BLER, and the UE is configured to receive another indication of an active target BLR in the set.

18. The UE of any one of claims 13-17, wherein the indication is received via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.

19. A method implemented in a user equipment (UE) configured to communicate with a network node, the method comprising: receiving an indication from the network node indicating the at least one target block error rate (BLER) for the network node to achieve, the at least one target BLER being based on at least one parameter; determining the at least one target BLER based on the indication; and performing at least one action based on the determination.

20. The method of claim 19, wherein the method further includes: transmitting a capability indication to the network node indicating the UE supports receiving the at least one target BLER from the network node.

21. The method of any one of claims 19 and 20, wherein the at least one target BLER is based on an operator configuration for a cell for at least for the UE.

22. The method of any one of claims 19-21, wherein the at least one parameter may be based on UE characteristics including quality of service required by an application executable by the UE and/or UE type.

23. The method of any one of claims 19-22, wherein the at least one target BLER includes a set of target BLER, and the method further includes receiving another indication of an active target BLR in the set.

24. The method of any one of claims 19-23, wherein the indication is received via at least one of a radio resource control reconfiguration message, medium access control (MAC) control element (CE), and via download control information.