WO2019197027A1

WO2019197027A1 - Methods and apparatuses for selective modulation and coding scheme (mcs) exclusion

Info

Publication number: WO2019197027A1
Application number: PCT/EP2018/059361
Authority: WO
Inventors: Silvio MANDELLI; Siegfried Klein; Le Hang Nguyen
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2018-04-12
Filing date: 2018-04-12
Publication date: 2019-10-17
Anticipated expiration: 2020-10-12

Abstract

Systems, methods, apparatuses, and computer program products for dynamically controlling and/or setting a modulation and coding scheme (MCS) value in communication systems are provided. One method may include determining, by at least one network node in a first layer, a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that a medium access control (MAC) layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the MAC layer cannot schedule. The method may then include transmitting the parameter representing the index of the minimum MCS to a second layer.

Description

TITLE:

METHODS AND APPARATUSES FOR SELECTIVE MODULATION AND CODING SCHEME (MCS) EXCLUSION

FIELD:

[0001] Some example embodiments may generally relate to user plane (U- plane) layers in mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology. Also, certain example embodiments may relate to medium access control (MAC) scheduling and/or related protocol layers, and service types such as ultra-reliable low-latency-communication (URLLC).

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. Fifth generation (5G) or new radio (NR) wireless systems refer to the next generation (NG) of radio systems and network architecture. It is estimated that NR will provide bitrates on the order of 10-20 Gbit/s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. It is noted that, in 5G or NR, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in E-UTRAN or eNB in LTE) may be referred to as a next generation or 5G Node B (gNB).

SUMMARY:

[0003] One embodiment may be directed to a method that may include determining, by at least one network node in a first layer, a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that the medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule. The method may also include transmitting the parameter representing the index of the minimum modulation and coding scheme to a second layer.

[0004] Another embodiment is directed to an apparatus that may include at least one processor and at least one memory comprising computer program code. The apparatus may include at least one network node in a first layer. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to determine a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that the medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule, and to transmit the parameter representing the index of the minimum modulation and coding scheme to a second layer.

[0005] Another embodiment is directed to an apparatus that may include determining means for determining a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that a medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule. The apparatus may include at least one network node in a first layer. The apparatus may also include transmitting the parameter representing the index of the minimum modulation and coding scheme to a second layer.

[0006] Another embodiment is directed to a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: determining, by at least one network node in a first layer, a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that the medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule, and transmitting the parameter representing the index of the minimum modulation and coding scheme to a second layer.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0007] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0008] Fig. 1 illustrates an example graph depicting complementary cumulative distribution function (CCDF) of a successful transmission latency with fixed MCS, with link adaptation (FA), and with FA removing the lowest rate, according to certain example embodiments;

[0009] Fig. 2 illustrates a graph depicting additional examples of CCDF of a successful transmission latency with different fixed MCS, according to some example embodiments;

[0010] Fig. 3 illustrates an example signaling diagram depicting the message flow, according to one example embodiment;

[0011] Fig. 4 illustrates another example signaling diagram depicting the message flow, according to another example embodiment;

[0012] Fig. 5a illustrates an example flow diagram of a method, according to one example embodiment; [0013] Fig. 5b illustrates an example flow diagram of a method, according to another example embodiment;

[0014] Fig. 6a illustrates an example block diagram of an apparatus, according to one example embodiment; and

[0015] Fig. 6b illustrates an example block diagram of an apparatus, according to another example embodiment.

DETAILED DESCRIPTION:

[0016] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for dynamically controlling and/or setting a modulation and coding scheme (MCS) value in communication systems, such as LTE or NR, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0017] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases“certain embodiments,”“some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases“in certain embodiments,”“in some embodiments,”“in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. [0018] Additionally, if desired, the different functions or steps discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or steps may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0019] Ongoing third generation partnership project (3 GPP) new radio (NR) standardizations are investigating communications dedicated to critical applications, such as but not limited to autonomous driving, remote surgery, industrial automation, etc. Ultra-Reliable Low-Latency Communications (URLLC) may be required to support these applications, which may demand a successful and reliable packet transmission with challenging RAN latency, e.g., down to 0.5 ms with reliability of r = 1— 10-*, with x > 5.

[0020] Naturally, achieving URLLC transmission in the uplink (UL) may be the most challenging part, since one should take into account the scheduling request (SR) delay before starting the transmission. According to simulations assumptions in line with scenarios considered by 3GPP, at least one round trip time - with UE processing time of 0.143 ms it will be 0.7144 ms - is necessary to transmit a packet in the first chance possible, with 2- OFDM symbols mini-slots, 15 kHz subcarrier spacing and no other users in the scheduler’s queue. Therefore, a first transmission’s reliability may already be very high, to reduce the latency introduced by retransmissions. Typical investigated working points are 1% target block error ratio (BLER) for the first transmission (although different values, e.g. 0.1% or 10%, can be considered depending on how many re-tx can be afforded, given the latency budget).

[0021] Fig. 1 illustrates an example complementary cumulative distribution function (CCDF) of a successful transmission latency with fixed MCS, with link adaptation (LA) where all MCS are used, and with LA removing the two lowest rate MCS, namely QPSK 1/8 and QPSK 1/10. Simulations show that adopting a fixed quadrature phase shift keying (QPSK) with code rate 1/8 (a very low-rate MCS), allows for achieving the performance in Fig. 1, in terms of latency CCDF. However, applying LA, namely dynamically associating a MCS based on the channel quality indicator (CQI) or a generic signal-to-noise-and-interference ratio (SINR) estimate, allows for achieving the desired link BLER with just the necessary amount of resources, allowing more aggressive MCS to be used.

[0022] One problem that arises relates LA for UL scheduled URLLC transmissions. For example, if there are too many users demanding for very low-rate MCS, the scheduler queue grows and impairs URLLC performance (as shown in the curve of Fig. 1 labelled‘LA CR1/10 & 1/8 included’), where exploiting LA does not provide any gains with respect to the fixed conservative scheme. This is due to the fact that low-rate MCSs require more time-frequency resources to deliver the same amount of information, thus, even if the network is not fully congested, the queues may no longer be empty with“ultra-reliability” (e.g., with probability of 99.999%).

[0023] Currently, there is no way for the radio resource control (RRC) or the 5G core network (5GC) to signal the MAC layer to exclude some MCS for the ones that can be potentially selected for transmission. As introduced above, system-level simulations regarding UL scheduled (GB) URLLC, show that adopting a fixed QPSK with code rate 1/8 (a very low-rate MCS), allows for achieving the performance in Fig. 1, in terms of latency CCDF. Fig. 2 illustrates additional examples of CCDF of a successful transmission latency with different fixed MCS. More conservative MCS may reach better floors, since they can successfully transmit with lower SINR. However, more conservative MCS require more resources, which may therefore result in a bigger delay. For example, as depicted in Fig. 1, with the offered traffic of the considered scenario, QPSK 1/10 is not even achieving a lower floor than QPSK 1/8. However, applying LA, namely dynamically associating a MCS based on the CQI or a generic SINR estimate, may achieve the desired link BLER with less resources (roughly 45% less PRBs used in the considered scenario), thereby allowing more aggressive MCS to be used. However, from a URLLC perspective, the gain is negligible because the performance is dominated by low-rate MCS, as depicted by the two solid and dotted-dashed curves in Fig. 1.

[0024] According to an example embodiment, by removing the possibility that users transmit with low-rate MCS, URLLC performance drastically increases (e.g., see dashed curve in Fig. 1), since the few users requiring a lot of resources are not in the system anymore. In one example, this may be managed by systems similar to admission control (AC) or overload control (OC) in the RRC, or in higher layers in the 5GC managing interactions between gNBs. As an example, if a user is thrown out of the system, they may simply be demoted to a lower QoS DRB. This operation may be performed by the SDAP layer in the gNB-CU, which associates DRBs with their respective 5QI.

[0025] In view of the above, there is a need for being able to dynamically control, by the RRC, the minimum MCS allowed to be used by the MAC layer. Certain example embodiments may include a process or algorithm that is run in a layer higher than the MAC scheduler, such as RRC, which can decide and communicate to the MAC layer a new integer parameter MIN_MCS. The parameter MIN_MCS may represent the index of the minimum rate MCS that the MAC layer is allowed to schedule and/or the maximum rate MCS that the MAC layer cannot schedule (i.e., the minimum minus 1).

[0026] Fig. 3 illustrates an example signaling diagram depicting the message flow, according to one example embodiment. As illustrated in the example of Fig. 3, a distributed unit (DU) 301 running in the MAC layer may transmit, at 310, a message to monitor QoS performance of one or more data radio bearers (DRBs), or a group of them given by the common Qos flag, to a centralized unit - control plane (CU-CP) 302 running in the RRC layer. It is noted that, in one example embodiment, QoS performance may be measured in terms of the experienced packet transmission’s latency distribution (e.g., in order to analyze latency and reliability together). In the example of Fig. 3, at 320, CU-CP 302 may run a process or algorithm that is configured to decide and communicate to the MAC layer the integer parameter, MIN_MCS, representing the index of the minimum rate MCS that the MAC layer is allowed to schedule and/or the maximum rate MCS that the MAC layer cannot schedule. As one example, in normal conditions, MIN_MCS may be equal to 0; however, if the algorithm 320 decides to remove from the list the lower-rate MCS, then MIN_MCS may become values larger than 0. Thus, based on the offered traffic and its 5QI (representing the Quality of Service), according to certain example embodiments, the algorithm 320 can react to achieve a better URLLC performance, as can be observed from Fig. 1, where the dashed line represents the case where QPSK 1/10 and QPSK 1/8 are excluded, i.e., MIN_MCS = 2. It is noted that this is just one example and this example relies on the order of MCS, which may be for example ordered in an increasing order of robustness. More details regarding the algorithm 320 and its implementation will be discussed below.

[0027] In one example embodiment, the interface of the communications between DU 301 and Cu-CP 302 may be standardized and go through the Fl interface. As illustrated in the example of Fig. 3, the CU-CP may transmit, at 330, an indication of which MCS can be used by the MAC layer for a particular class of DRB. For instance, in one embodiment, the CU-CP 302 may transmit, based on the results of algorithm 320, MIN_MCS and/or a list of MCS removed from the system. The MCS may be removed for the entire system or for one or more 5QI. As an example, in a set of N MCS that are ordered according to their aggressiveness from 0 (the least aggressive MCS) to N-l, CU-CP 302 may transmit the MIN_MCS to the MAC layer. This information allows the MAC layer to decide which MCS can be used. As an alternative, in certain example embodiments, when no order is provided for the MCS, a list of MCS removed from the system may be provided to the MAC layer. In some example embodiments, the MIN_MCS may be associated with a single DRB or with a list of DRBs.

[0028] According to an example embodiment, the signaling of MIN MCS from the RRC layer (e.g., from CU-CP 302) to the MAC layer (e.g., to DU 301) may happen periodically and/or based on request from the MAC layer, if an algorithm in the MAC scheduler detects the need of changing MIN_MCS. For example, as shown in the example of Fig. 3, DU 301 may transmit an update request at 340 or may transmit a periodic update request at 350. The request(s) may also go through the Fl interface. In some example embodiments, the periodical 350 or triggered request 340 updates may be implemented in the same way. According to certain example embodiments, 5GC 303 may also transmit, at 360, periodical or triggered update requests to the CU-CP 302. In some examples, the MAC layer may inform the CU-CP 302 (e.g., SDAP layer) that for certain users, associated to MCS < MIN MCS, a URLLC 5QI cannot be guaranteed.

[0029] In some example embodiments, this approach may be implemented by mechanisms or logical entities above gNBs, for example located in the 5GC, where one or more servers may manage this process in a coordinated way for different cells, and then signals to one or more gNB(s) its decisions. In this way, according to certain examples, the information may flow through both the NG and Fl interface. Fig. 4 illustrates an example signaling diagram depicting the message flow according to the example where the process or algorithm 410 may be run in the 5GC 403. In one example, the algorithm 410 may the same or similar to the algorithm 320 discussed above in connection with Fig. 3.

[0030] As depicted in the example of Fig. 4, 5GC 403 may execute the algorithm at 410 and transmit at 420, based on the results of algorithm 410, MIN_MCS and/or a list of MCS removed from the system to CU-CP 402. In one example, at 430, CU-CP 402 may receive, from DU 401, a request to monitor QoS performance of one or more DRBs at 420, and then CU-CP 402 may transmit, at 440, the MIN_MCS and/or a list of MCS removed from the system (as previously indicated by 5GC 403). According to certain example embodiments, CU-CP 402 may receive a triggered update request at 450 or may receive a periodic update request at 470. In some examples, upon receipt of an update request, CU-CP 402 may transmit, at 460, an update request to the 5GC 403. In response to the update request the 5GC may execute the algorithm 410 and transmit, at 480, an update of the MIN_MCS and/or list of MCS removed from the system. In an example, CU-CP 402 may transmit, at 490, the updated MIN_MCS and/or list of MCS removed from the system to DU 401. It is noted that, in certain example embodiments, the parameter MIN_MCS may also be a vector, where each element in the vector may be associated with a different URLLC QoS and/or each element in the vector may be related to the MIN_MCS that can be used for a DRB associated to each specific 5QI.

[0031] As discussed above, certain example embodiments may include a process or algorithm that decides the index of the minimum rate MCS that the MAC layer is allowed to schedule. In some examples, the algorithm may reside either in the gNB (e.g., RRC layer) or may be executed by one or more servers in a cloud configuration. According to certain examples, the algorithm is configured to track the URLLC performance of the DRBs with URLLC 5QI. In other words, the algorithm may keep track of an estimated distribution of the latency experienced for a successful packet transmission and the used MCS, for different URLLC 5QI.

[0032] In the following examples, the most stringent requirement deliberated by 3GPP, that is 1 ms latency with 10^L-5 reliability, is considered. Therefore, in certain example embodiments, the algorithm may be run for every user group belonging to critical URLLC applications, e.g., the ones with 5QI 76,77,78,79 (of Table 5.7.4-1 of reliability from 3GPP S2- 1772320).

[0033] According to certain examples, the algorithm may monitor how many URLLC users and traffic are active (e.g., as it is done for AC/OC). Moreover, in an example embodiment, the algorithm can understand how much low-rate MCS are impacting the URLLC performance, thereby keeping track of the latency and MCS distributions. Then, if the algorithm detects that there is a degradation in the performance due to low-rate MCS, it can react by informing the gNB (or a group of them in the centralized 5GC approach) to change MIN_MCS for that specific 5QI class, hereafter referred to as MIN_MCS(C). It is noted that also some AC/OC can be taken accordingly, e.g., not accepting any more users for a specific 5QI. In example embodiments, the signalling may pass through the Fl interface in case that the algorithm is run in the gNB (i.e., Fig. 3), or both the Fl and NG interface if the algorithm is running in the 5GC (i.e., Fig. 4).

[0034] In some example embodiments, from the highest priority class C to the lowest, if some users constantly require MCS with rate lower than MIN_MCS(C), then the algorithm may be configured to demote those users to a lower QoS (i.e., less stringent URLLC requirement) or to expel those users from the system. In one example, if the aggregated URLLC performance is not satisfied (from latency distribution evaluated at the 10^L-5 quantile, in the factory automation case), and if the load of low-rate MCS(s) is impairing the URLLC performance, then the algorithm may be configured to increase MIN_MCS(C) to exclude more low-rate MCS from the system.

[0035] In another example, if the aggregated URLLC performance is well satisfied and the distribution of the queueing delay is not impairing ongoing URLLC traffic, then the algorithm may be configured to lower MIN_MCS(C) to allow more low-rate MCS. It is noted that the delay budget may be composed of delays from encoding or decoding, SR, transmission, retransmissions, as well as from queueing. In an embodiment, MIN_MCS can be lowered if this does not cause individual transmissions to exceed their delay budget. So, certain example embodiments may be configured to take into account the queueing delay when deciding whether and how to modify the MIN MCS.

[0036] Fig. 5a illustrates an example flow diagram of a method for dynamically controlling and/or setting a MCS value in a communication system, such as 5G or NR, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 5a may be performed by a network node, such as a base station, node B, eNB, gNB, or any other access node, or one or more servers in a 5GC or cloud configuration. In some example embodiments, the method of Fig. 5a may be performed by CU-CP 302, 402 (e.g., gNB in RRC layer) or 5GC 303, 403 (e.g., server(s) in 5GC) illustrated in Figs. 3 and 4, respectively.

[0037] As illustrated in the example of Fig. 5 a, the method may optionally include, at 500, receiving a request to monitor quality of service (QoS) performance of one or more DRB(s). In certain examples, the receiving 500 of the request may include receiving a periodic update request to monitor the QoS performance of the DRB(s). In other examples, the receiving 500 of the request may include receiving a triggered update request to monitor the QoS performance of the DRB(s). According to some example embodiments, the receiving 500 of the request may include receiving the parameter over the FI interface and/or NG interface.

[0038] In certain example embodiments, the receiving 500 may include receiving the request by one or more network node(s) at a layer that is higher than the MAC layer. In one example, the layer that is higher than the MAC layer may include a RRC layer or a layer above RRC, such as 5GC.

[0039] According to an example embodiment, the method may also include, at 505, executing a process or algorithm for determining, by the network node(s) in the layer higher than the MAC layer, a parameter representing an index of a minimum MCS that the MAC layer is allowed to schedule. In some example embodiments, the determining 505 may include determining the parameter for one or more users or user groups belonging to critical URLLC applications, such as autonomous driving applications, remote surgery, industrial automation, or any other application where it may be important to provide URLLC. In one example embodiment, the method may then include, at 510, transmitting the parameter representing the index of the minimum modulation and coding scheme to a lower layer. In certain example embodiments, the lower layer may be a MAC layer or RRC layer. According to some example embodiments, the transmitting 510 may include transmitting the parameter over the Fl interface and/or NG interface.

[0040] Fig. 5b illustrates a flow diagram of an example implementation of the process or algorithm for determining 505 the parameter representing the index of the minimum MCS the MAC layer is allowed to schedule, according to an example embodiment. In some example embodiments, the process of Fig. 5b may be performed for one or more priority class(es). As illustrated in the example of Fig. 5b, the process may include, at 520, monitoring an estimated distribution of latency experienced for a successful packet transmission and the MCS used for at least one URLLC 5QI. The process may then include determining, at 530, whether aggregated URLLC performance is being satisfied. For example, the determining 530 may include determining whether low rate MCS is impacting the URLLC performance.

[0041] When it is determined, at 530, that the aggregated URLLC performance is being satisfied, then the process may include, at 550, lowering the minimum MCS for the priority class and, at 570, indicating the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, the indicating 570 may include informing the gNB(s) to change (e.g., lower) the minimum MCS for a specific 5QI. When it is determined, at 530, that the aggregated URLLC performance is not being satisfied, then the process may include, at 540, determining whether the load of the low rate MCS is impairing URLLC performance. If it is determined that the load of the low rate MCS is impairing URLLC performance, then the process may include, at 560, increasing the minimum MCS to exclude more low rate MCS(s) from the system and, at 570, indicating the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, the indicating 570 may include informing the gNB(s) to change (e.g., increase) the minimum MCS for a specific 5QI. In some examples, when the process determines at 560 that the minimum MCS should be increased, the process may further include expelling users or not accepting any more users for the specific 5QI. If it is determined that the load of the low rate MCS is not impairing URLLC performance, then the process may return to step 520.

[0042] Fig. 6a illustrates an example of an apparatus 10 according to an example embodiment. In an example embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be a base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), WLAN access point, mobility management entity (MME), and/or subscription server associated with a radio access network, such as a LTE network, 5G or NR or other radio systems which might benefit from an equivalent procedure.

[0043] It should be understood that, in some example embodiments, apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a front-haul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 6a.

[0044] As illustrated in the example of Fig. 6a, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in Fig. 6a, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0045] Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[0046] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0047] In an example embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0048] In some example embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, BT-LE, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink). Transceiver 18 may comprise one or more RF chains for down and/or upconverting RF signals, for example comprising diplexers, front end RF amplifiers, mixers, filters, voltage controlled oscillators and the like, the activation of part or all of which may be activated in accordance with example embodiments.

[0049] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other example embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and/or output device (I/O device).

[0050] In an example embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0051] According to some example embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 18 may be included in or may form a part of transceiving circuitry.

[0052] As used herein, the term“circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term“circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0053] As introduced above, in example embodiments, apparatus 10 may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, WLAN access point, or the like. In one example, apparatus 10 may be a gNB and/or CU-CP in a RRC layer. According to example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the example embodiments described herein, such as the system or signaling flow diagrams illustrated in Figs. 3, 4, 5a or 5b. For example, in certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform one or more of the steps performed by the CU-CP 302 or CU-CP 402 illustrated in Figs. 3 and 4, respectively, or the steps depicted in Figs. 5a or 5b. In example embodiments, for instance, apparatus 10 may be configured to perform a process for dynamically controlling and/or setting a MCS value.

[0054] For instance, in some example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to receive a request to monitor QoS performance of one or more DRB(s) from a MAC layer (e.g., a gNB or DU in the MAC layer). In one example embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to receive a request over the Fl interface. According to an example embodiment, apparatus 10 may then be controlled by memory 14 and processor 12 to execute a process or algorithm to determine a parameter representing an index of a minimum MCS that the MAC layer is allowed to schedule. In certain example embodiments, the process to determine the parameter may be performed for one or more priority class(es). In some example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to determine the parameter for one or more users or user groups belonging to critical URLLC applications, such as autonomous driving applications, remote surgery, industrial automation, or any other application where it may be important to provide URLLC.

[0055] According to one example implementation of the process to determine the parameter representing the minimum MCS, apparatus 10 may be controlled by memory 14 and processor 12 to monitor an estimated distribution of latency experienced for a successful packet transmission and the MCS used for at least one URLLC 5QI. In one example embodiment, apparatus 10 may also be controlled by memory 14 and processor 12 to determine whether aggregated URLLC performance is being satisfied. For example, apparatus 10 may be controlled to determine whether low rate MCS is impacting the URLLC performance.

[0056] If it is determined that the aggregated URLLC performance is being satisfied, then apparatus 10 may be controlled by memory 14 and processor 12 to lower the minimum MCS for the priority class and to indicate the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, apparatus 10 may be controlled to inform the gNB(s) to change (e.g., lower) the minimum MCS for a specific 5QI.

[0057] If it is determined that the aggregated URLLC performance is not being satisfied, then apparatus 10 may be controlled by memory 14 and processor 12 to determine whether the load of the low rate MCS is impairing URLLC performance. If it is determined that the load of the low rate MCS is impairing URLLC performance, then apparatus 10 may be controlled by memory 14 and processor 12 to increase the minimum MCS to exclude more low rate MCS(s) from the system and to indicate the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, apparatus 10 may be controlled to inform the gNB(s) to change (e.g., increase) the minimum MCS for a specific 5QI. In some examples, when it is determined that the minimum MCS should be increased, apparatus 10 may be further controlled by memory 14 and processor 12 to expel users or stop accepting any more users for the specific 5QI, or to demote users to a lower QoS. If it is determined that the load of the low rate MCS is not impairing URLLC performance, then apparatus 10 may be controlled to continue to monitor an estimated distribution of latency experienced for successful packet transmission and the MCS used for at least one URLLC 5QI.

[0058] In one example embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit the determined parameter representing the index of the minimum modulation and coding scheme to a lower layer. In certain example embodiments, the lower layer may be a MAC layer. According to some example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to transmit the parameter over the Fl interface.

[0059] In certain examples, apparatus 10 may also be controlled by memory 14 and processor 12 to receive a periodic update request to monitor the QoS performance of the DRB(s), or to receive a triggered update request to monitor the QoS performance of the DRB(s). In this case, after receipt of the update request, apparatus 10 may be controlled by memory 14 and processor 12 to perform the process to determine an updated parameter representing the minimum MCS.

[0060] Fig. 6b illustrates an example of an apparatus 20 according to another example embodiment. In example embodiments, apparatus 20 may include one or more of a base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), WLAN access point, mobility management entity (MME), and/or subscription server associated with a radio access network, such as a LTE network, 5G or NR or other radio systems which might benefit from an equivalent procedure.

[0061] In some example embodiments, apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and/or any other radio access technologies.

[0062] It should be understood that, in some example embodiments, apparatus 20 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 6b.

[0063] As illustrated in the example of Fig. 6b, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 6b, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0064] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0065] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0066] In an example embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20. [0067] In example embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to- analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0068] For instance, in one example embodiment, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other example embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and/or output device (FO device). In certain examples, apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0069] In an example embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR. For instance, in an example embodiment, link 70 may represent the NG interface.

[0070] According to some example embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry.

[0071] As discussed above, according to example embodiments, apparatus 20 may be a base station, access point, Node B, eNB, gNB, WLAN access point, MME, and/or subscription server or other server associated with a radio access network, such as a LTE network, 5G or NR. In one example embodiment, apparatus 20 may represent one or more servers in a 5GC and/or cloud configuration. According to certain examples, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein. For instance, in some example embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the diagrams or signaling flow diagrams described herein, such as those illustrated in Figs. 3, 4, 5a or 5b. As an example, apparatus 20 may be controlled to execute one or more of the steps performed by the 5GC illustrated in Figs. 3 or 4, or any of the steps depicted in Figs 5a or 5b. In example embodiments, apparatus 20 may be configured to dynamically control and/or set a MCS value.

[0072] For instance, in some example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to execute a process or algorithm to determine a parameter representing an index of a minimum MCS that the MAC layer is allowed to schedule. In certain example embodiments, the process to determine the parameter may be performed for one or more priority class(es). In some example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to determine the parameter for one or more users or user groups belonging to critical URLLC applications, such as autonomous driving applications, remote surgery, industrial automation, or any other application where it may be important to provide URLLC.

[0073] In one example implementation of the process to determine the parameter representing the minimum MCS, apparatus 20 may be controlled by memory 24 and processor 22 to monitor an estimated distribution of latency experienced for a successful packet transmission and the MCS used for at least one URLLC 5QI. In one example embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to determine whether aggregated URLLC performance is being satisfied. For example, apparatus 20 may be controlled to determine whether low rate MCS is impacting the URLLC performance.

[0074] If it is determined that the aggregated URLLC performance is being satisfied, then apparatus 20 may be controlled by memory 24 and processor 22 to lower the minimum MCS for the priority class and to indicate the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, apparatus 20 may be controlled to inform the gNB(s) to change (e.g., lower) the minimum MCS for a specific 5QI.

[0075] If it is determined that the aggregated URLLC performance is not being satisfied, then apparatus 20 may be controlled by memory 24 and processor 22 to determine whether the load of the low rate MCS is impairing URLLC performance. If it is determined that the load of the low rate MCS is impairing URLLC performance, then apparatus 20 may be controlled by memory 24 and processor 22 to increase the minimum MCS to exclude more low rate MCS(s) from the system and to indicate the updated minimum MCS to one or more gNB(s). In other words, in this example embodiment, apparatus 20 may be controlled to inform the gNB(s) to change (e.g., increase) the minimum MCS for a specific 5QI. In some examples, when it is determined that the minimum MCS should be increased, apparatus 20 may be controlled by memory 24 and processor 22 to expel users or stop accepting any more users for the specific 5QI, or to demote users to a lower QoS. If it is determined that the load of the low rate MCS is not impairing URLLC performance, then apparatus 20 may be controlled to continue to monitor an estimated distribution of latency experienced for successful packet transmission and the MCS used for at least one URLLC 5QI.

[0076] In one example embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to transmit the determined parameter representing the index of the minimum modulation and coding scheme to a lower layer. In certain example embodiments, the lower layer may be a RRC layer. According to some example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to transmit the parameter over the NG interface.

[0077] In certain examples, apparatus 20 may be controlled by memory 24 and processor 22 to receive a periodic update request to monitor the QoS performance of the DRB(s), or to receive a triggered update request to monitor the QoS performance of the DRB(s). In this case, after receipt of the update request, apparatus 20 may be controlled by memory 24 and processor 22 to perform the process to determine an updated parameter representing the minimum MCS.

[0078] Therefore, certain example embodiments provide several technical improvements, enhancements, and/or advantages. Various example embodiments can, for example, enhance the performance of URLLC transmissions, optimize resource usage and reduce unnecessary transmissions. For example, with low/no offered URLLC traffic, according to an example embodiment MIN_MCS will be zero to serve the few users as best, as the queues will be (almost) always empty. Once the offered traffic starts increasing, example embodiments may selectively increase MIN_MCS to avoid a systematic delay. It should be noted that the term“systematic” is not used to refer to all the cases, but to the 10^L-5 of them (for the factory automation traffic 5QI, otherwise the other level of reliability asked by URLLC), since these are the ones of interest for URLLC. When the offered load starts decreasing again and URLLC performance is strongly delivered, example embodiments may try to relax the constraints by allowing more low-rate MCS to be scheduled.

[0079] Consequently, certain example embodiments improve the reliability of URLLC transmissions, improve network load distribution by not selecting overloaded SgNBs, and also improve overall network energy efficiency. As such, example embodiments can improve performance, latency, and/or throughput of networks and network nodes including, for example, access points, base stations/eNBs/gNBs, and mobile devices or UEs. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes.

[0080] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

[0081] In some example embodiments, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and include program instructions to perform particular tasks.

[0082] A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0083] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non- transitory medium.

[0084] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0085] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation. [0086] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. In order to determine the metes and bounds of the example embodiments, therefore, reference should be made to the appended claims.

Claims

WE CLAIM:

1. A method, comprising:

determining, by at least one network node in a first layer, a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that a medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule; and

transmitting the parameter representing the index of the minimum modulation and coding scheme to a second layer.

2. The method according to claim 1, wherein the first layer comprises a layer higher than a medium access control layer and the second layer comprises a lower layer.

3. The method according to claim 2, wherein the layer higher than the medium access control layer comprises a radio resource control layer.

4. The method according to claim 2, wherein the lower layer comprises at least one of a medium access control layer or radio resource control layer.

5. The method according to any one of claims 1-4, further comprising:

receiving, at the at least one network node, a request to monitor quality of service performance of at least one data radio bearer.

6. The method according to claim 5, wherein the receiving further comprises receiving a periodic update request to monitor the quality of service performance of the at least one data radio bearer.

7. The method according to claim 5, wherein the receiving further comprises receiving a triggered update request to monitor the quality of service performance of the at least one data radio bearer.

8. The method according to any one of claims 1-4, wherein the at least one network node comprises at least one of:

at least one server in a fifth generation (5G) core network; or

at least one gNB in a radio resource control layer.

9. The method according to any one of claims 1-4, wherein signaling between the at least one network node in the first layer and the second layer is performed over at least one of a Fl interface or NG interface.

10. The method according to any one of claims 1-4, wherein the transmitting further comprises transmitting the parameter over at least one of a Fl interface or NG interface.

11. The method according to claim 5, wherein the receiving further comprises receiving the request over at least one of a Fl interface or NG interface.

12. The method according to any one of claims 1-4, wherein the determining of the parameter further comprises:

monitoring an estimated distribution of latency experienced for a successful packet transmission and the modulation and coding scheme (MCS) used for at least one ultra-reliable low-latency communication (URLLC) 5G quality indicator (5QI).

13. The method according to claim 12, wherein the monitoring comprises determining whether low rate modulation and coding scheme (MCS) is impacting the ultra-reliable low-latency communication (URLLC) performance.

14. The method according to claim 13, wherein, when it is determined that there is a degradation in the ultra-reliable low-latency communication (URLLC) performance due to the low rate modulation and coding scheme (MCS), the method further comprises informing at least one gNB to change the minimum modulation and coding scheme (MCS) for a specific 5G quality indicator (5QI).

15. The method according to claim 13, wherein, wherein, when it is determined that there is a degradation in the ultra-reliable low-latency communication (URLLC) performance due to the low rate modulation and coding scheme (MCS), the method further comprises:

expelling users or not accepting a subset of additional users or any additional users for the specific 5G quality indicator (5QI); and

signaling information relating to the expelling of users or not accepting any more users for the specific 5G quality indicator (5QI) to the lower layer.

16. The method according to any one of claims 1 or 13-15, wherein the determining further comprises determining the parameter for one or more users or user groups belonging to critical ultra-reliable low-latency communication (URLLC) applications.

17. An apparatus, comprising:

at least one processor; and

at least one memory comprising computer program code,

wherein the apparatus comprises at least one network node in a first layer,

the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to

determine a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that a medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule; and

transmit the parameter representing the index of the minimum modulation and coding scheme to a second layer.

18. The apparatus according to claim 17, wherein the first layer comprises a layer higher than the medium access control layer and the second layer comprises a lower layer.

19. The apparatus according to claim 18, wherein the layer higher than the medium access control layer comprises a radio resource control layer.

20. The apparatus according to claim 18, wherein the lower layer comprises at least one of a medium access control layer or radio resource control layer.

21. The apparatus according to any one of claims 17-20, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

receive a request to monitor quality of service performance of at least one data radio bearer.

22. The apparatus according to claim 21, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

receive a periodic update request to monitor the quality of service performance of the at least one data radio bearer.

23. The apparatus according to claim 21, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

receive a triggered update request to monitor the quality of service performance of the at least one data radio bearer.

24. The apparatus according to any one of claims 17-20, wherein the apparatus comprises at least one of:

at least one server in a fifth generation (5G) core network; or

at least one gNB in a radio resource control layer.

25. The apparatus according to any one of claims 17-20, wherein signaling between the at least one network node in the first layer and the second layer is performed over at least one of a Fl interface or NG interface.

26. The apparatus according to any one of claims 17-20, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

transmit the parameter over at least one of a Fl interface or NG interface.

27. The apparatus according to claim 21, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

receive the request over at least one of a Fl interface or NG interface.

28. The apparatus according to any one of claims 17-20, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

monitor an estimated distribution of latency experienced for a successful packet transmission and the modulation and coding scheme (MCS) used for at least one ultra-reliable low-latency communication (URLLC) 5G quality indicator (5QI).

29. The apparatus according to claim 28, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

determine whether low rate modulation and coding scheme (MCS) is impacting the ultra-reliable low-latency communication (URLLC) performance.

30. The apparatus according to claim 29, wherein, when it is determined that there is a degradation in the ultra-reliable low-latency communication (URLLC) performance due to the low rate modulation and coding scheme (MCS), the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

inform at least one gNB to change the minimum modulation and coding scheme (MCS) for a specific 5G quality indicator (5QI).

31. The apparatus according to claim 29, wherein, wherein, when it is determined that there is a degradation in the ultra-reliable low-latency communication (URLLC) performance due to the low rate modulation and coding scheme (MCS), the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

expel users or not accept a subset of additional users or any additional users for the specific 5G quality indicator (5QI) ; and

signal information relating to the expelling of users or not accepting any more users for the specific 5G quality indicator (5QI) to the lower layer.

32. The apparatus according to any one of claims 17-20, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to:

determine the parameter for one or more users or user groups belonging to critical ultra-reliable low-latency communication (URLLC) applications.

33. An apparatus, comprising:

determining means for determining a parameter representing at least one of an index of a minimum modulation and coding scheme (MCS) that a medium access control layer is allowed to schedule or maximum modulation and coding scheme (MCS) that the medium access control layer cannot schedule,

wherein the apparatus comprises at least one network node in a first layer; and

34. A non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: