TECHNICAL FIELD

Various example embodiments relate generally to improving transmis sion efficiency. BACKGROUND

Considering the diversity of 5G applications, ultra-reliable low-latency communications (URLLC) has been widely envisioned as one of the key enablers to support the new applications. It may be crucial for certain applications to have a transmitted packet to a receiver efficiently and reliably within certain time con- straints.

BRIEF DESCRIPTION

According some aspects, there is provided the subject matter of the in dependent claims. Some further aspects are defined in the dependent claims. The embodiments that do not fall under the scope of the claims are to be interpreted as examples useful for understanding the disclosure.

LIST OF THE DRAWINGS

In the following, the invention will be described in greater detail with reference to the embodiments and the accompanying drawings, in which

Figure 1 presents a communication system, according to an embodi- ment;

Figure 2 shows a periodical communication, according to an embodi ment;

Figures 3 and 4 depict methods, according to some embodiments; Figures 5A to 5C illustrate priority settings, according to some embodi- ments;

Figure 6 depicts a signaling flow diagram, according to an embodiment; Figure 7 illustrates options for acquiring resources, according to some embodiments; and

Figures 8 to 9 show apparatuses, according to some embodiments. DESCRIPTION OF EMBODIMENTS

The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodi ments), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embod iments. For the purposes of the present disclosure, the phrases “A or B” and “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

Embodiments described may be implemented in a radio system, such as one comprising at least one of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE). Term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN). A term “resource” may refer to radio resources, such as a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and/or “reception” may refer to wirelessly transmit ting and/or receiving via a wireless propagation channel on radio resources

The embodiments are not, however, restricted to the systems/RATs given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties. One example of a suitable communications system is the 5G system. The 3GPP solution to 5G is re ferred to as New Radio (NR). 5G has been envisaged to use multiple-input-multiple- output (M1MO) multi-antenna transmission techniques, more base stations or nodes than the current network deployments of LTE (a so-called small cell con cept), including macro sites operating in co-operation with smaller local area ac- cess nodes and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates. 5G will likely be comprised of more than one radio access technology / radio access network (RAT/RAN), each optimized for certain use cases and/or spectrum. 5G mobile communications may have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applica tions, including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and being integrable with existing legacy radio access technologies, such as the LTE.

The current architecture in LTE networks is distributed in the radio and centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge genera tion to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environ ment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer- to-peer ad hoc networking and processing also classifiable as local cloud/fog com puting and grid/mesh computing, dew computing, mobile edge computing, cloud let, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autono- mous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). Edge cloud may be brought into RAN by utilizing network function virtualization (NVF) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. Network slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then custom ised to meet the specific needs of applications, services, devices, customers or op erators.

In radio communications, node operations may in be carried out, at least partly, in a central/centralized unit, CU, (e.g. server, host or node) operationally coupled to distributed unit, DU, (e.g. a radio head/node). It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may vary depending on implementation. Thus, 5G networks architecture may be based on a so-called CU-DU split. One gNB- CU controls several gNB-DUs. The term ‘gNB’ may correspond in 5G to the eNB in LTE. The gNBs (one or more) may communicate with one or more UEs 120. The gNB-CU (central node) may control a plurality of spatially separated gNB-DUs, act ing at least as transmit/receive (Tx/Rx) nodes. In some embodiments, however, the gNB-DUs (also called DU) may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may comprise the layers above RLC layer, such as a packet data con vergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too. It is considered that skilled person is familiar with the OS1 model and the functionalities within each layer.

In an embodiment, the server or CU may generate a virtual network through which the server communicates with the radio node. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head/node. In practice, any digital signal processing task may be performed in either the CU or the DU and the bound ary where the responsibility is shifted between the CU and the DU may be selected according to implementation. Some other technology advancements probably to be used are Soft ware-Defined Networking (SDN), Big Data, and all-IP, to mention only a few non limiting examples. For example, network slicing may be a form of virtual network architecture using the same principles behind software defined networking (SDN) and network functions virtualisation (NFV) in fixed networks. SDN and NFV may deliver greater network flexibility by allowing traditional network architectures to be partitioned into virtual elements that can be linked (also through software). Net work slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then customised to meet the specific needs of applications, services, devices, customers or operators. The plurality of gNBs (access points/nodes), each comprising the CU and one or more DUs, may be connected to each other via the Xn interface over which the gNBs may negotiate. The gNBs may also be connected over next genera tion (NG) interfaces to a 5G core network (5GC), which may be a 5G equivalent for the core network of LTE. Such 5G CU-DU split architecture may be implemented using cloud/server so that the CU having higher layers locates in the cloud and the DU is closer to or comprises actual radio and antenna unit. There are similar plans ongoing for LTE/LTE-A/eLTE as well. When both eLTE and 5G will use similar ar chitecture in a same cloud hardware (HW), the next step may be to combine soft ware (SW) so that one common SW controls both radio access networks/technol ogies (RAN/RAT). This may allow then new ways to control radio resources of both RANs. Furthermore, it may be possible to have configurations where the full pro tocol stack is controlled by the same HW and handled by the same radio unit as the CU.

It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being con structed and managed. 5G (or new radio, NR) networks are being designed to sup port multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.

5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future rail-way/maritime/aeronauti- cal communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in partic ular mega-constellations (systems in which hundreds of (nano) satellites are de ployed). Each satellite in the mega-constellation may cover several satellite-ena- bled network entities that create on-ground cells. The on-ground cells may be cre ated through an on-ground relay node or by a gNB located on-ground or in a satel lite.

The embodiments may be also applicable to narrow-band (NB) Inter- net-of-things (loT) systems which may enable a wide range of devices and services to be connected using cellular telecommunications bands. NB-loT is a narrowband radio technology designed for the Internet of Things (loT) and is one of technolo gies standardized by the 3rd Generation Partnership Project (3GPP). Other 3GPP loT technologies also suitable to implement the embodiments include machine type communication (MTC) and eMTC (enhanced Machine-Type Communication). NB-loT focuses specifically on low cost, long battery life, and enabling a large num ber of connected devices. The NB-loT technology is deployed “in-band” in spectrum allocated to Long Term Evolution (LTE) - using resource blocks within a normal LTE carrier, or in the unused resource blocks within a LTE carrier’s guard-band - or “standalone” for deployments in dedicated spectrum.

The embodiments may be also applicable to device-to-device (D2D), machine-to-machine, peer-to-peer (P2P) communications. The embodiments may be also applicable to vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), in- frastructure-to-vehicle (I2V), or in general to V2X or X2V communications.

Figure 1 illustrates one example of a communication system to which embodiments of the invention may be applied. The system may comprise a control node 110 providing one or more cells, such as cell 100, and a control node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. In another point of view, the cell may define a coverage area or a service area of the corresponding access node. The control node 110, 112 may be an evolved Node B (eNB) as in the LTE and LTE-A, ng-eNB as in eLTE, gNB of 5G, or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The control node 110, 112 may be called a base station, network node, or an access node.

The system may be a cellular communication system composed of a ra dio access network of access nodes, each controlling a respective cell or cells. The access node 110 and/or 112 may provide user equipment (UE) 120 (one or more UEs) with wireless access to other networks such as the Internet. The wireless ac cess may comprise downlink (DL) communication from the control node to the UE 120 and uplink (UL) communication from the UE 120 to the control node.

Additionally, although not shown, one or more local area access nodes may be arranged such that a cell provided by the local area access node at least partially overlaps the cell of the access node 110 and/or 112. The local area access node may provide wireless access within a sub-cell. Examples of the sub-cell may include a micro, pico and/or femto cell. Typically, the sub-cell provides a hot spot within a macro cell. The operation of the local area access node may be controlled by an access node under whose control area the sub-cell is provided. In general, the control node for the small cell may be likewise called a base station, network node, or an access node.

There may additionally be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different control nodes 110, 112. The UEs 120, 122 may communicate with each other, in case D2D communication interface is established between them. The term “terminal device” or “UE” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wire less local loop phones, a tablet, a wearable terminal device, a personal digital assis tant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback ap- pliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an In ternet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a con sumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

In the case of multiple access nodes in the communication network, the access nodes may be connected to each other with an interface. LTE specifications call such an interface as X2 interface. For IEEE 802.11 network (i.e. wireless local area network, WLAN, WiFi), a similar interface Xw may be provided between ac- cess points. An interface between an eLTE access point and a 5G access point, or between two 5G access points may be called Xn. Other communication methods between the access nodes may also be possible. The access nodes 110 and 112 may be further connected via another interface to a core network 116 of the cellular communication system. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise a mobility manage ment entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to/from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC), and there the core network may comprise e.g. an access and mobility management function (AMF) and a user plane function/gateway (UPF), to mention only a few. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integ rity protection, registration management, connection management, mobility man agement, access authentication and authorization, security context management. The UPF node may support packet routing & forwarding, packet inspection and QoS handling, for example.

In 3GPP, there is a Rel-16 working item (WI) for ensuring efficient sup port industrial IoT (IIoT). In the area of IIoT applications, within 3GPP, it has been agreed that a UE should be able to handle up to eight traffic flows of time-sensitive communications (TSC) simultaneously. These flows are typically characterized by periodic transmissions (e.g.0.5, 1 or 2 ms) of small payloads and fixed payload sizes between 20 and 64 Bytes. These may be delivered over the 5G system (5GS), i.e. between UE, UPF and an application server, with a typical allowed latency of one period time and high reliability. Concerning future releases, on top of the usual key performance indicators (KPIs), such as end-to-end latency, message size, service bit rate and transfer internal, additional KPIs including a survival time have been proposed. The survival time indicates to the communication service the time avail able to recover from failure. The survival time can be expressed as a time period or, especially with cyclic traffic, as maximum number of consecutive incorrectly re- ceived or lost messages (i.e. as a maximum allowed consecutive packet losses).

An example for periodic communication is given in Figure 2. A given ap plication delivers the messages/packets to the ingress of the communication sys tem at a given transfer interval, called periodicity. When the messages/packets are correctly received, they are labelled as "UP TIME" of the communication service as well as "UP TIME" from the application’s perspective. Packet that are not received correctly by the receiver, e.g. due to decoding failure, are marked with crosses in connection of boxes labelled “REC.”, where “REC” stands for “received”. From the application layer point of view, the connection is labelled as “OK” as long as the number of consecutive packet losses, or the time duration thereof, is less than the survival time. When the number of consecutive packet losses, or the time duration thereof, is higher than the survival time, the connection is labelled as “FAILURE” from the point of view of the application layer. Therefore, it may be important to find solutions to increase the time when the connection stays “OK” from the point of view of the application layer. Similar as in LTE, in 5G NR, different traffic flows are mapped to differ ent dedicated radio bearers (DRBs), wherein the data on each DRB will be buffered in a logical channel (LCH) associating to this bearer, and medium access control (MAC) will process data from these LCHs by allocating them to available radio re source (e.g. to an uplink grant). Each logical channel may be associated with a spe cific radio link control (RLC) entity. Logical channels may reside between the RLC sublayer and the MAC sublayer which are layer 2 protocols in a protocol stack.

Resource allocation in DL may be gNB implementation issue. However, in uplink, how resources should be allocated among multiple logical channels is up to standardization. Based on the resource grant message signalled in physical downlink control channel (PDCCH) e.g. from the gNB 110 to the UE 120 or in radio resource control (RRC) configuration signalling in case with configured grant re source, the UE has to decide on the amount of data for each logical channel to be included in the new MAC protocol data unit (PDU), and, if necessary, also to allocate space for a MAC Control Element (CE). For each logical channel, there are config ured parameters including LCH priority and LCH mapping restriction rules. For each UL grant, one simple way is to take data out of buffer in the order of the LCH priority. Following this principle, the data from the logical channel with the highest priority is the first to be included into the MAC PDU, followed by data from the log ical channel of the next highest priority, continuing until the MAC PDU size allo cated by the gNB is completely filled or there is no more data to transmit. The mapping of data from LCHs to the MAC PDU, e.g. to transport blocks

(TB), may be restricted due to mapping restrictions. For example, there may be LCH specific restrictions regarding to which TBs data from a given LCH may be mapped. These restrictions may be at least partially based on the logical channel prioritiza tion (LCP). The radio resource control (RRC) protocol may control the LCP proce- dure by configuring mapping restrictions for each logical channel.

LCH priority may be configured via RRC configuration and can only be updated via RRC re-configuration. Since the LCH priority is pre-configured, the pri ority setting has not considered what happens from previous transmissions and does not take into account the tolerable data packet errors/message loss from the application layer. With the current specified UE behaviour, if it is desirable to sup port one application with both high reliability and “maximum allowed consecutive message loss” requirements, the logical channel is set with very high priority which can easily result in over-provisioned radio resource and the data from other low priority channel has to be postponed. It may also be worth knowing on how to map such a message from an application layer further to one or multiple transport blocks (TB) at the physical layer in RAN. The data from the upper layer (e.g. MAC) to the physical layer is car ried in the so-called transport block.

Therefore, one problem to be at least partially tackled by using the pro posed embodiments is related to how to efficiently support applications having limitations with respect to the maximum allowed consecutive packet losses, while keeping communication of other data also efficient.

To at least partially tackle this problem, there is proposed a solution for service flow or logical channel handling by means of cross-packet dependent LCH priority setting/adjustment, by taking into account the aspects due to the introduc- tion of “maximum allowed consecutive message loss”. For example, as configured by the gNB (e.g. gNB 110), and depending on the decoding outcome from previous packet(s), the UE (e.g. the UE 120) may dynamically change the LCH priority when applying logical channel prioritization (LCP) procedure at the MAC layer.

Although applicable to many networks, we will in the following exam- pies focus on 5G, for the sake of simplicity. Also, although escribed as UE to gNB communication, the embodiments are applicable to communications between two UEs, for example, or in general to any communication between any devices.

Figure 3 depicts an example method. For simplicity, let us consider the method to be performed by a user equipment, such the UE 120 of Figure 1. As shown in Figure 3, the UE 120 may in step 300 transmit packets to a receiving de vice, which in this example may be the gNB 110, but in general it may be any re ceiving device, such as another UE 122 in case of sidelink connections. However, for simplicity let us consider it is the gNB 110. The packets in this step may be transmitted per current UE behaviour from any of the LCHs, following prevailing mapping restrictions and LCP. As such, this may include the UE 120 transmitting data from a first logical channel (LCH) to the gNB 110. In an embodiment, the UE is associated or configured with a plurality of LCHs. Each LCH may have a specific (same or different) priority.

The first logical channel is assumed in these example embodiments to be the LCH that is linked with an application/service that has a limitation with re spect to the survival time, e.g. the maximum allowed consecutive packet losses (MCPL). This application may have limitations with respect to a need to communi cate data to the receiving device periodically. Thus, the UE 120 may in this step also send packets which comprise data from this type of application, as well as packets from other LCHs.

In step 302, the UE 120 may determine that the number of consecutive packets from the first LCH, which have not been received successfully at the receiv ing device 110, meets a predetermined criterion. In an embodiment, the determin ing of step 302 is based on monitoring decoding success of consecutive packets transmitted from the first LCH over the sliding window having a predetermined length. The length may be based on the survival time. The starting point of the slid ing window is repeatedly set at a time instant of a previous packet transmission from the first LCH having a successful reception. This ensures that the UE monitors the number of failed packet receptions over a correct time period. The decoding success may comprise considering whether the receiver has correctly extracted the transmitted packet after the decoding. The decoding may fail because of distortions in the received packet or due to the receiver never receiving the transmitted packet, both of which may be due to unreliable propagation channel and/or high interference between the transmitting and the receiving devices. A feedback re garding unsuccessful reception may be received from the receiving device, e.g. via hybrid automatic repeat request (HARQ) procedure, or via any means indicating unsuccessful reception of data packets.

In step 304, the UE 120 may increase priority of the first logical channel to a preconfigured priority level based on the determining (to avoid, or at least re duce the probability of, many consecutive packet losses), and in step 306, the UE 120 may select one or more packets for transmission to the receiving device based on the increased priority. These further packet(s) may be from the first LCH due to the priority of the first LCH being increased.

Let us consider steps 302 and 304 in more details by looking at Figures 5A to 5C. These show how the cross-packet dynamic logical channel priority setting may work in some embodiments. In the beginning of the operation, the LCH prior ity for the LCH #1 is set at 3 (imaginary lowest priority in this example). In case the earlier at least one packet (number is configurable) cannot be decoded success fully, possibly after retransmission if allowed, the priority level of the correspond ing LCH priority is increased by a predetermined amount. In an embodiment of Fig- ure 5A, when the packet is lost (e.g. packet 3 or packet 7, or packet 12), the priority of the LCH is increased from 3 to 2. In case there are two consecutive packet decod ing errors (packets 7 and 8), the LCH priority can be further upgraded to the high est level. In the example embodiment of Figure 5B, when packet numbers 7 and 8 are not received correctly, the priority is increased immediately to the highest pri- ority 1 from the priority 3. Thus, in some embodiments, the increase is not sudden to the highest priority but goes in steps, as in Figures 5A and 5C. This may depend on various aspects, as will be described. In this way, UE 120 may dynamically change the priority level of a given LCH depending on the decoding outcome from the previous packets from the same LCH.

In an embodiment, the predetermined criterion of step 302 is based on a (preconfigured) limit of maximum allowed consecutive packet losses from the first logical channel. In an embodiment, the predetermined criterion is defined as a certain threshold for consecutive packet losses l.e. when the number of consecu tive packet losses is at least the same as the threshold, the criterion may be consid ered met. For example, let us assume in Figure 5A that the maximal allowed con secutive message loss is two. This may be based on periodicity of the application data (i.e. the time duration between two consecutive transmissions). For example, if the periodicity is 5ms, and the survival time is 12 ms, then two missed packets already lead to a time duration between two consecutive receptions from this ap- plication to be at least 15 ms. This is more than the survival time and may thus be undesired. In this case the predetermined criterion may be one packet loss, and as shown in the Figure 5A, the priority of the LCH #1 is increased right after detecting one packet loss. As another example, when the maximum allowed consecutive mes sage loss is set as a higher number, e.g. three or four, then it may be configured so that nothing changes when there is only one message loss. This is shown in Figure 5B, where losing the packet #3 does not cause any adjustment of the priority of the first LCH. Only after e.g. two consecutive message losses (packets 7 and 8) are de tected, the predetermined criterion may be met and priority of the relevant LCH may be increased by a preconfigured amount. Thus, the setting of the predeter- mined criterion may be dependent on the maximum allowed consecutive mes sage/packet loss associated with the application from the first LCH.

In an embodiment, the preconfigured priority level (to which the prior ity is adjusted to when meeting the predetermined criterion) of step 304 is at least partially based on the number of consecutive packets transmitted from the first logical channel which have not been received successfully at the receiving device 110 with respect to (in relation to) the limit of maximum allowed consecutive packet losses from the first LCH. For example, as shown in Figure 5A, the priority is increased by only one unit (from priority level 3 to priority level 2) upon meeting the predetermined criterion. If we assume the maximum limit for consecutive packet losses is two and the criterion is one packet loss, then the ratio between these is 2 (2/1=2). In the example of Figure 5B, assuming the maximum limit for consecutive packet losses is four and the criterion is two packet losses, then the ratio between these is 2 (4/2=2). On the other hand, in the example of Figure 5B, assuming the maximum limit for consecutive packet losses is three and the crite rion is two packet losses, then the ratio between these is 1.5 (3/2=1.5). Thus, the ratio, to be used for defining how the priority is adjusted, is configurable without limiting to any of the examples given.

In an embodiment, there may be multiple predetermined criteria and multiple ways to adjust the priority of the relevant LCH. For example, let us assume the maximum allowed number for the consecutive packet losses from the relevant LCH is set to four. Then, some nonlimiting examples for adjusting the priority com prise the following:

• when one message loss detected (1 ^st threshold/criterion), the priority level is increased by one level e.g. from 5 to 4.

• when two consecutive messages loss detected (2 ^nd thresh old/criterion), the priority level is increased by two levels, e.g. from 5 to 3.

• when three consecutive messages loss detected (3 ^rd thresh old/criterion), the priority level is set as the highest level, e.g. from 5 to 1.

In an embodiment, the preconfigured priority level used in step 304 is at least partially based on number of transport blocks (or MAC PDUs) required for transmitting one message from the application associated with the first logical channel. This is exemplified in Figure 5C, where one application layer message is mapped to two TBs, i.e. one application layer message has to be fragmented and mapped to multiple TBs. In this case, the situation may be different than in Figure 5A. In Figure 5C, the LCH priority is changed once at least one of the two TBs from the same application layer message is not decoded correctly. The situation of two consecutive decoding errors should be handled differently depending whether the missed TBs are corresponding to the same application layer message (e.g. TBs 13, 14) or different (TBs 6, 7). As such, even with the same number of packet loss, the resulting behaviour can be different. In an embodiment, the consecutive packet losses that meet the criterion need to be associated to the same application layer message before the priority of the LCH is increased. In another embodiment, the consecutive packet losses that meet the criterion need not be associated to the same application layer message before the priority of the LCH is increased.

In an embodiment, the UE 120 may decrease the priority of the first logical channel when the number of consecutive packets transmitted from the first logical channel, which have not been received successfully at the receiving device 110, does not meet the predetermined criterion. For example, in Figure 5A, the pri ority of the logical channels is dropped step-wise back when the packet is decoded correctly. I.e. when packet 9 is received correctly, the priority is decreased from 1 to 2. Thus, in an embodiment, the priority is decreased to a previous lower level. When packet 10 is also received correctly, the priority is further decreased to level 3. In another example shown in Figure 5B, the priority is reduced back to the initial level of 3 when a packet is received/decoded correctly. As the monitoring of the predetermined criterion may be based on the sliding window which is reset each time a packet is received correctly, then after the packet 9 (in both Figures 5A and 5B) is received correctly, the predetermined criteria may no longer be met and the priority is decreased. As is clear from the embodiments shown, the among of de crease may be preconfigured. In some embodiments it may be fixed and in some embodiments a step-wise decrease is applied.

In some embodiments, the history of N previous packet transmissions (N being predetermined) may affect the priority decrease, e.g. such that if there are more than M (M<N) packets lost in the previous N packets (although not neces sarily consecutive), the priority may be kept at the increased level although the next packet is successfully received. Thus, in an embodiment, there is a preconfig ured limit for a number of successfully received packets that shall be met with the increased priority before the priority of the relevant LCH is decreased. Other crite ria for decreasing the priority may be established instead or in addition.

In an embodiment, the UE 120 may indicate to the gNB information about the application that is associated with the first LCH. This may comprise e.g. the survival time or the maximum allowed consecutive message loss information of the application. Thus, it may be that the UE is aware of those. The indication is shown in Figure 6 with reference numeral 600. This indication may be omitted in case the gNB 110 becomes aware of those via pre-configuration, for example. Furthermore, the UE 120 may in an embodiment, inform the receiving device 110 in step 602 of Figure 6 how a single application layer message is mapped to at least one transport block at the apparatus. For example, the UE may indicate that one message is mapped to more than one TBs (such as two TBs as in case of Figure 5C). Knowledge of this may be needed so that the gNB 110 knows which and how much of data to expect in the allocated uplink resources. The time instant when the indication of step 602 is performed need not be as shown in Figure 6, but the rule regarding the mapping may be indicated to the gNB 110 at any point, or it may be preconfigured to both the UE and the gNB without explicit indication.

In an embodiment, adjusting the priority level (increase or decrease) of the first logical channel is at least partially based on at least one rule defined by a serving network access node (e.g. gNB 110) for the UE 120. The rule or rules may e.g. indicate to act according to any of the embodiments regarding the priority set ting (which embodiments serve merely as non-limiting example embodiments). That is, the gNB 110 may define the at least one rule for the user equipment. The rule may e.g. indicate what is the predetermined criterion used to be in step 302. Defining the rule may be based on a maximum allowable consecutive packet loss from the first logical channel and/or based on how a single application layer mes sage from the first logical channel is mapped to at least one transport block at the transmitting device. The gNB 110 may, as shown in Figure 6, in step 610 define the rule(s) and then in step 620 indicate the rule(s) to the UE 120. In step 630, the UE may apply the rule(s) for setting the priority of the logical channel(s). The rule(s) may be indicated to the UE 120 over a PDCCH, or e.g. over a system information block (SIB) message or RRC message. The indication of rules may be omitted, in case these are preconfigured to both devices

In an embodiment, the UE 120 may in step 640 of Figure 6 indicate the changed priority of the first logical channel to the receiving device, which may be e.g. the gNB 110 serving the UE 120. This may at the same time serve as an indica tion that the maximum allowed consecutive packet loss for the relevant LCH and its application has been met. However, in an embodiment there is no need for the indication of step 640 as the defined rule(s) may be known to both the UE and the gNB. In case the UE itself autonomously changes the priority, an indication may be needed. In general, the gNB 110 needs to know the LCH priority setting at the UE 120, because the UE needs to know which LCH will be mapped to the uplink re- sources. As mapping is based on LCP, both the UE and the gNB need to have the same understanding of the LCP.

In an embodiment, with respect to step 306 of Figure 3, the next packet for transmission is selected to be transmitted from a buffer of the first logical chan nel. This may be because the priority has been increased which may cause that a data packet of the buffer associated with the first LCH to be selected for transmis sion, assuming the priorities of the other LCHs are at a lower level. This may be beneficial in that the application which is time-constrained is more quickly served.

In an embodiment, the UE 120 may map the next packet to a transport block that is reserved for a logical channel having at least the preconfigured prior ity level. As shown in Figure 7, there may be multiple TBs to be used for uplink grants or otherwise allocated UL resources (may also be other resources in case of DL communication or sidelink communication). Each of the TBs may be reserved for certain LCH or to a certain priority level of the LCH. As said, the RRC may control the LCP procedure by configuring mapping restrictions for each logical channel. These may comprise e.g. allowed subcarrier spacing(s) for transmission, maximum physical uplink shared channel (PUSCH) duration allowed for transmission, an in dication whether a configured grant type can be used for transmission, allowed cell(s) for transmission. Therefore, when the LCH has high priority, the probability to lose a packet may become smaller. That is, LCP restrictions may be enhanced by allowing restrictive mapping between an LCH and certain grant configurations (ei- ther dynamic grants, DG, and/or configured grants, CG). E.g. each transport block may have its own modulation and coding scheme. Thus, the logical channels having higher priority are mappable to transport blocks or uplink grants having increased reliability, compared to grants intended for logical channels having lower priority. In this way, the reliability of the LCH with high priority may be increased. As said, the first logical channel is assumed in these example embodi ments to be the LCH that is linked with an application/service that has a limitation with respect to the survival time, e.g. the maximum consecutive packet losses. However, contrary to general URLLC applications, each individual packet sent on the LCH still have the same delay threshold, but the reliability of the packet is in- creased after a failed packet(s) is/are detected by means of cross-packet depend ent LCH prioritization. Thus, once the LCH priority changes, the UE and the gNB can take actions to increase/decrease the reliability of the following transmission by means of the dynamic cross-packet dependent LCH prioritization. The application may be considered as of ultra-high reliability but having toleration to consecutive packet losses. It means that the ultra-high reliability may not necessarily be applied for each and every packet which is resource-consuming (setting to the highest pos sible priority). The adjustment of the prioritization of the LCH may be dynamic in nature, as the priority may be reset to initial/previous level after a successfully re ceived packet. Following the priority change (from low priority to high priority), there may be need for resource(s) for sending the next packet. Thus, in an embodiment, the UE 120 may acquire a set of at least one resource for the next packet transmis sion. Figure 7 illustrates options for a resource acquisition. Three different scenar ios on how to acquire the resource(s) are discussed below.

In scenario 1 the gNB is aware of the packet loss and the maximum al- lowed consecutive message loss. Such case can take place for example when the UE 120 is configured with UL semi-static configured grant (CG) resource or dynamic grant (DG) resource exclusively for one application/logical channel which sends periodic data packets and the receiving gNB 110 knows that for each allocated re source, there should be one linked UL data packet (i.e. no UL skipping). Therefore, both UE 120 and gNB 110 have the same information regarding which packet is lost. For the gNB 110 to know how to allocate resources for the new packet, the gNB 110 may get information from the UE (explicitly or implicitly) how the appli cation layer message is mapped to TB(s) at the PHY layer of the gNB. This can be conveyed e.g. as discussed in connection of step 602. In an embodiment, the gNB 110 may proactively or after detecting that the number of consecutive packet losses from the first LCH meets the predeter mined criterion, allocate dedicated radio resource(s) to the UE for the latter data packet transmission, as shown with option 700 in Figure 7. Such dedicated re source^) can be a defined by a CG (by activating more CG configurations for the UE 120) or by a dynamic grant (DG) to the UE 120. In an embodiment, the dedicated resource(s) may be on a different carrier (either licensed or unlicensed). In an em bodiment, the dedicated resource(s) may be defined by a packet duplication con figuration over frequency domain and/or spatial domain.

In an embodiment, as shown with option 702, the resource(s) may be autonomously activated and/or derived from the current CG(s) by both UE and gNB without a need of an indication signalled by either UE and gNB to one another. In an example, two CG resources are configured to the same LCH (e.g. CGI: 10 PRBs; CG2: 8 PRBs). In normal case, only CGI resource is used. Once there is packet loss detected, the CG2 resource is automatically used as well. In this way the usage of the second set of resource is triggered by the packet loss from the first set of re source. As both UE and gNB are aware of the packet loss, additional explicit signal ing may not be needed. In an embodiment, the additional resource(s) may be char acterized by a transport format, such as a modulation coding scheme (MCS). The resource(s) may be derived and/or activated from the current transport format used for that LCH or used by an LCH having the same priority as the first LCH with out a need of an indication signalled by either UE and gNB to one another. Thus, the acquisition of the at least one resource may be taken place with or without negotiations between the UE and the gNB.

In scenario 2 it is assumed that the gNB 110 is not aware of the packet loss. This case can take place when e.g. UL skipping is possible. In case multiple LCHs can be mapped to the same CG resource or the packet is delivered over DG resource the gNB 110 knows the multiplexed LCHs only after successful decoding. Therefore, in this case the UE 120 may need to indicate the packet loss to the gNB, e.g. as discussed in connection of step 640. After the UE 120 identifying the priority increase which may be due to detecting that the number of consecutive packet losses from the first LCH meets the predetermined criterion, the UE may update MAC PDU generation procedure at the MAC layer. Before sending the next packet from the same LCH, the UE 120 may in option 704 request from the gNB 110 dedi cated resource(s). That is, the acquiring may be based on transmitting a request to the receiving device 110, and in response to the request, receiving an indication of at least one resource useable for the next packet transmission.

In an embodiment, the resource request may be in a form of a schedul ing request (SR). In case only positive/negative information can be sent, e.g. by dif ferent cyclic shift of the same sequence, then it may not be possible for the UE 120 to send any additional information together with the SR (unless additional channel can be used). In another case, the UE 120 may tell the gNB 110 that the packet over the to-be-allocated DG resource is a duplication of the packet on the original CG resource via e.g. UC1 information. In case additional control information can be sent together with SR, the UE 120 can inform the change of the logical channel priority, after which the gNB 110 may take similar steps as discussed above for scenario 1. In an embodiment, the resource may be based on a CG. The gNB 110 may configure multiple CG configurations (first CG, second CG, etc.) to the same UE 120. Then, in case the UE 120 has changed the priority of the logical channel, the UE 120 may autonomously select at least one resource from another CG configura tion for the first LCH, as shown with option 706. That is, the acquiring of the re- source(s) may in an embodiment be based on utilizing a configured grant of an other logical channel for the transmission on the first logical channel. In case UL UC1 can be sent together with the CG PUSCH, an indication that data from the first LCH is being carried with this TB. Such indication may be a duplication information. Duplication may denote that the same TB sent over a first set of resource and a second set of resource (e.g. via resources based on two different CGs). In order for the gNB to understand that the data is a duplicated TB (same as the TB sent over the first CG resource), this duplication indication may help. Alternatively, the gNB may implicitly consider that the data from a second CG PUSCH carries duplicated data from a first CG PUSCH, in which case such indication may not be needed.

As shown above, in an embodiment, the acquiring may be based on a preconfigured rule that is triggered when the predetermined criterion is met. The rule may define which at least one resource can be used for the next packet trans mission. The rule may define e.g. to use a resource of another CG, or that the next resource is derived/activated based on the current CG.

In scenario 3, the eNB may become aware that the number of consecu- five packets, which have not been received successfully at the gNB 110, meets the predetermined criterion, but the UE may not know this yet. This may be possible by the gNB monitoring sequence numbers of received PDCP packets sent on/from the relevant LCH, for example. The gNB may be in control of the cross-packet de pendent dynamic LCP on the targeted/relevant first LCH. The gNB may e.g. trigger control of LCP, based on monitoring and detecting consecutive packet errors. The gNB may command the UE to adjust LCP in a preconfigured fashion (e.g. increasing at least one of CLP parameters and decreasing it after successful transmission of a next packet) using e.g. LI DC1, L2 MAC for fast control, or L3 RRC signalling. After the gNB triggering the LCP, the UE may e.g. increase the priority of the first LCH. The gNB 110 may also provide resources for the new transmission as illustrated in option 708 of Figure 7.

Looking from the point of view of the receiving device (such as gNB 110), the method, as shown in Figure 4 may comprise in step 400 receiving packets from a transmitting device, such as from the UE 120. In step 402, the gNB 110 may determine that the number of consecutive packets from the first LCH of the UE 120, which have not been received successfully at the gNB 110, meets a predetermined criterion. This determining may be based on the gNB 110 autonomously detecting this or based on an indication received from the UE 120. In step 404, the gNB 110 may decide, based on the determination of step 402, that a priority of the first LCH is increased to the preconfigured priority level. After this, the gNB 110 may in step 406 receive one or more packets from the transmitting device based on the in creased priority. These further packet(s) may be from the first LCH, based on re sources having more transmission reliability than the previous packets from the same first LCH. In an embodiment, after deciding that the priority has been increased, the gNB 110 may perform scheduling for the UE 120 based on the increased priority and/or based on how the single application layer message is mapped to at least one transport block at the UE 120. The scheduling may be based on a sched uling priority which may now consider the changed priority of the first LCH of the UE 120. The gNB 110 may, based on the scheduling, provide at least one resource for the UE 120, the at least one resource being useable for the transmission of the next packet by the UE to the gNB. In an embodiment, the gNB 110 informs the UE 120 that the resource is to be used to increase the reliability of the following packet from the same (=first) logical channel. Such information can be included e.g. in the downlink control information (DCI) carried over PDCCH. In an embodiment, based on the scheduling, the first LCH may be mapped to scheduled TBs. Depending on whether grants for the TB(s) are semi-persistent or dynamic, different signaling options may be used.

Depending on whether or not gNB is autonomously aware of the in creased priority, different option may be envisaged, as illustrated above with sce- narios 1 and 2. For example, in the UE initiated option, the UE needs to indicate to the gNB about the priority change so that the gNB can allocate more proper re source for the UE, if the current resource(s) are not adequate. In an gNB initiated option, the gNB may detect that consecutive losses meeting the predetermined cri terion is met. The gNB 110 may then indicate this to the UE. The gNB 110 may also indicate to the UE a more proper resource, if the current resource(s) are not ade quate, so thatthe UE can map the first LCH to the proper resource(s). In the implicit option where possibly no signaling regarding the priority change is needed (as both know this based on preset rules), the gNB 110 may either configure more than one grant (e.g. two grants) beforehand and the rule that the UE 120 can use the second grant only when the consecutive losses occur such that the predetermined criterion is met, or configure the second grant dynamically when needed.

Owing to the embodiments where per-packet priority or cross-packet dependent priority handling is allowed, the priority of the LCH can be dynamically adjusted based on the successful/failed reception which can lead to reduced re- source waste or the resource can be used for data transmission from other logical channels. For example, in case the application layer requires overall 10 ⁶ reliability and the maximum allowed consecutive message loss is three, by following a proce dure without considering the survival time, a block error rate (BLER) target for each packet may be set at the level of lOA However, when taking into account the maximum allowed consecutive packet loss of three, for example the BLER target can be set to 10 ² before any packet loss. Then, only in case there is a predetermined number of consecutive transmission errors(s) taking place, the priority level and the related reliability of the relevant (first) LCH may be increased.

In an embodiment, the proposal is applicable to real-time lloT applica tions wherein each application packet has a certain delay requirement and the ap- plication will not tolerate up to N consecutive packet losses. Taking a PROF1SAFE application, a bi-standard adopted for industrial automation safety, for an example. The application layer from a user device 120 may generate and send a new “alive” packet to a server per T-apps. In case the server does not receive at least one “alive” packet from the user device 120 during a sliding time interval of N*T-apps, the server considers the user device 120 is dead and therefore stops operation related to the user device 120. Then, depending on monitoring packet losses of “alive” packets, the server may speed up or slow down the operation related to the user device 120. Being aware of such operation, the RAN may prioritize and optimize its own overall operation while reassuring the above - no N consecutive packet losses happening on RAN level for a relevant UEs. Thus, RAN can afford to serve the rele vant UE with best effort as long as there is no packet loss and depending on moni toring consecutive packet losses RAN may increase priority for new packet. The packet loss here may mean that a packet cannot be delivered within T-apps. The cellular network may be using a radio bearer service concept mapped on LCH and therefore the above described per-packet treatment may be translated into LCH prioritization (LCP) comprising intra-UE (prioritization among LCHs of same indi vidual UE).

An embodiment, as shown in Figure 8, provides an apparatus 10 com prising a control circuitry (CTRL) 12, such as at least one processor, and at least one memory 14 including a computer program code (software), wherein the at least one memory and the computer program code (software), are configured, with the at least one processor, to cause the apparatus to carry out any one of the above- described processes. The memory may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The memory may comprise a database for stor ing data.

In an embodiment, the apparatus 10 may comprise the terminal device of a communication system, e.g. a user terminal (UT), a computer (PC), a laptop, a tabloid computer, a cellular phone, a mobile phone, a communicator, a smart phone, a palm computer, a mobile transportation apparatus (such as a car), a household appliance, or any other communication apparatus, commonly called as UE in the description. Alternatively, the apparatus is comprised in such a terminal device. Further, the apparatus may be or comprise a module (to be attached to the UE) providing connectivity, such as a plug-in unit, an “USB dongle”, or any other kind of unit. The unit may be installed either inside the UE or attached to the UE with a connector or even wirelessly. In an embodiment, the apparatus is operating according to a long-term evolution (LTE), according to the long-term evolution ad vanced (LTE-A), or according to New Radio (NR). In an embodiment, the apparatus 10 is or is comprised in the UE 120. The apparatus may further comprise a radio interface (TRX) 16 com prising hardware and/or software for realizing communication connectivity ac cording to one or more communication protocols. The TRX may provide the appa ratus with communication capabilities to access the radio access network, for ex ample. The apparatus may also comprise a user interface 18 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc. The user interface may be used to control the apparatus by the user.

The control circuitry 12 may comprise a communication control circu ity 20 for controlling access to the network, for controlling transmission and recep- tion of packets via the wireless medium, for monitoring communication (e.g. deter mining has a packet gone through to the receiver successfully), and for selecting next packet(s) for transmission, for requesting radio resources, according to any of the embodiments. The control circuitry 12 may further comprise an LCH control circuitry 22 for e.g. setting the priority of the LCHs, according to any of the embod- iments.

An embodiment, as shown in Figure 9, provides an apparatus 50 com prising a control circuitry (CTRL) 52, such as at least one processor, and at least one memory 54 including a computer program code (software), wherein the at least one memory and the computer program code (software), are configured, with the at least one processor, to cause the apparatus to carry out any one of the above- described processes. The memory may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The memory may comprise a database for stor- ing data.

In an embodiment, the apparatus 50 may be or be comprised in a network node, such as in gNB/gNB-CU/gNB-DU of 5G. In an embodiment, the ap paratus is or is comprised in the network node 110.

In an embodiment, a CU-DU (central unit - distributed unit) architec ture is implemented. In such case the apparatus 50 may be comprised in a central unit (e.g. a control unit, an edge cloud server, a server) operatively coupled (e.g. via a wireless or wired network) to a distributed unit (e.g. a remote radio head/node). That is, the central unit (e.g. an edge cloud server) and the radio node may be stand alone apparatuses communicating with each other via a radio path or via a wired connection. Alternatively, they may be in a same entity communicating via a wired connection, etc. The edge cloud or edge cloud server may serve a plurality of radio nodes or a plurality of radio access networks. In an embodiment, at least some of the described processes may be performed by the central unit. In another embodi ment, the apparatus may be instead comprised in the distributed unit, and at least some of the described processes may be performed by the distributed unit. In an embodiment, the execution of at least some of the functionalities of the apparatus 50 may be shared between two physically separate devices (DU and CU) forming one operational entity. Therefore, the apparatus maybe seen to depict the opera tional entity comprising one or more physically separate devices for executing at least some of the described processes. In an embodiment, the apparatus controls the execution of the processes, regardless of the location of the apparatus and re gardless of where the processes/functions are carried out.

The apparatus may further comprise communication interface (TRX) 56 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols. The TRX may provide the ap- paratus with communication capabilities to access the radio access network, for example. The apparatus may also comprise a user interface 58 comprising, for ex ample, at least one keypad, a microphone, a touch display, a display, a speaker, etc. The user interface may be used to control the apparatus by the user.

The control circuitry 52 may comprise a communication control cir- cuitry 60 e.g. for controlling user devices accessing the network via the apparatus, for controlling transmission and reception of packets via the wireless medium, for decoding received packets, for detecting errors in the communication, according to any of the embodiments. The control circuitry 12 may comprise a radio resource control circuity 62 e.g. for controlling resource allocation e.g. to the UE 120 based on scheduling decisions.

In an embodiment, an apparatus carrying out at least some of the embodiments described comprises at least one processor and at least one memory including a computer program code, wherein the at least one memory and the com puter program code are configured, with the at least one processor, to cause the apparatus to carry out the functionalities according to any one of the embodiments described. According to an aspect, when the at least one processor executes the computer program code, the computer program code causes the apparatus to carry out the functionalities according to any one of the embodiments described. Accord ing to another embodiment, the apparatus carrying out at least some of the embod iments comprises the at least one processor and at least one memory including a computer program code, wherein the at least one processor and the computer pro gram code perform at least some of the functionalities according to any one of the embodiments described. Accordingly, the at least one processor, the memory, and the computer program code form processing means for carrying out at least some of the embodiments described. According to yet another embodiment, the appa- ratus carrying out at least some of the embodiments comprises a circuitry includ ing at least one processor and at least one memory including computer program code. When activated, the circuitry causes the apparatus to perform the at least some of the functionalities according to any one of the embodiments described.

As used in this application, the term ‘circuitry’ refers to all of the follow- ing: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memoiy(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a micropro cessor^), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application. As a further example, as used in this application, the term ‘circuitry’ would also cover an implementation of merely a processor (or mul- tiple processors) or a portion of a processor and its (or their) accompanying soft ware and/or firmware. The term ‘circuitry’ would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device. In an embodiment, at least some of the processes described may be car ried out by an apparatus comprising corresponding means for carrying out at least some of the described processes. Some example means for carrying out the pro cesses may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, re ceiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, dis- play, user interface, display circuitry, user interface circuitry, user interface soft ware, display software, circuit, antenna, antenna circuitry, and circuitry.

The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For a hardware implementation, the appa ratuses) of embodiments may be implemented within one or more application- specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programma ble gate arrays (FPGAs), processors, controllers, micro-controllers, microproces- sors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be car ried out through modules of at least one chip set (e.g. procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be imple- mented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the systems described herein may be rear ranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.

Embodiments as described may also be carried out in the form of a com puter process defined by a computer program or portions thereof. Embodiments of the methods described may be carried out by executing at least one portion of a computer program comprising corresponding instructions. The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program. For example, the computer program may be stored on a com puter program distribution medium readable by a computer or a processor. The computer program medium may be, for example but not limited to, a record me dium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example. The computer program medium may be a non-transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art. Following is a list of some aspects of the invention.

According to a first aspect, there is provided an apparatus, comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are config ured, with the at least one processor, to cause the apparatus to: control transmis- sion of packets to a receiving device; determine that a number of consecutive pack ets from a first logical channel, which have not been received successfully at the receiving device, meets a predetermined criterion, wherein the apparatus is asso ciated with a plurality of logical channels; increase priority of the first logical chan nel to a preconfigured priority level based on the determining; select a packet for transmission to the receiving device based on the increased priority.

Various embodiments of the first aspect may comprise at least one fea ture from the following bulleted list:

• wherein the determining is based on monitoring decoding suc cess of consecutive packets transmitted from the first logical channel over the sliding window having a predetermined length, wherein a starting point of the sliding window is repeatedly set at a time instant of a previous packet transmission from the first logical channel having a successful reception.

• wherein the first logical channel comprises data of an application having a limitation with respect to the maximum allowed con secutive packet losses.

• wherein the predetermined criterion is based on the limit of maximum allowed consecutive packet losses from the first logi cal channel. · wherein the preconfigured priority level is at least partially based on the number of consecutive packet losses from the first logical channel in relation to the limit of maximum allowed con secutive packet losses from the first logical channel.

• wherein the preconfigured priority level is at least partially based on number of transport blocks required for transmitting one message from the application associated with the first logical channel.

• decrease the priority of the first logical channel when the prede termined criterion is no longer met.

• wherein changing the priority level of the first logical channel is at least partially based on at least one rule received from the re ceiving device.

• indicate the changed priority of the first logical channel to the receiving device.

• inform the receiving device how a single application layer mes sage is mapped to at least one transport block at the apparatus.

• acquire a set of at least one resource for the packet transmission, wherein the acquiring is based on a preconfigured rule that is triggered when the predetermined criterion is met.

• wherein the rule defines that a configured grant of another logi cal channel is to be utilized for the transmission on the first log ical channel.

• map the selected packet to a transport block that is reserved for a logical channel having at least the preconfigured priority level.

According to a second aspect, there is provided an apparatus, compris ing: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are config ured, with the at least one processor, to cause the apparatus to perform: control reception of packets from a transmitting device; determine that a number of con secutive packets from a first logical channel of the transmitting device, which have not been received successfully at the apparatus, meets a predetermined criterion; decide, based on the determination, that a priority of the first logical channel at the transmitting device is increased to a preconfigured priority level; control reception of a packet from the transmitting device based on the increased priority.

Various embodiments of the second aspect may comprise at least one feature from the following bulleted list:

• perform scheduling for the transmitting device based on at least one of the following: the increased priority and how a single ap plication layer message is mapped to at least one transport block at the transmitting device.

• provide at least one resource for the transmitting device, the at least one resource being useable for the transmission of the packet.

• define at least one rule for the transmitting device that causes the transmitting device to change the priority of the first logical channel, wherein defining the rule is based on at least one of the following: a limit for a maximum allowable consecutive packet loss from the first logical channel and how a single application layer message from the first logical channel is mapped to at least one transport block at the transmitting device.

According to a third aspect, there is provided a method for a transmit- ting device, comprising: transmitting packets to a receiving device; determining that a number of consecutive packets from a first logical channel, which have not been received successfully at the receiving device, meets a predetermined crite rion, wherein the transmitting device is associated with a plurality of logical chan nels; increasing priority of the first logical channel to a preconfigured priority level based on the determining; selecting a packet for transmission to the receiving de vice based on the increased priority.

Various embodiments of the third aspect may comprise at least one fea ture from the bulleted list under the first aspect.

According to a fourth aspect, there is provided a method for a receiving device, comprising: receiving packets from a transmitting device; determining that a number of consecutive packets from a first logical channel of the transmitting device, which have not been received successfully at the receiving device, meets a predetermined criterion; decide, based on the determination, that a priority of the first logical channel at the transmitting device is increased to a preconfigured pri- ority level; receiving a packet from the transmitting device based on the increased priority. Various embodiments of the fourth aspect may comprise at least one fea ture from the bulleted list under the second aspect.

According to a fifth aspect, there is provided a computer program prod uct embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute the method according to the third aspect.

According to a sixth aspect, there is provided a computer program prod uct embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute the method according to the fourth aspect.

According to a seventh aspect, there is provided a computer program product comprising program instructions which, when loaded into an apparatus, execute the method according to the third aspect.

According to an eight aspect, there is provided a computer program product comprising program instructions which, when loaded into an apparatus, execute the method according to the fourth aspect.

According to a ninth aspect, there is provided an apparatus, comprising means for performing the method according to the third aspect, and/or means con figured to cause the apparatus to perform the method according to the third aspect.

According to a tenth aspect, there is provided an apparatus, comprising means for performing the method according to the fourth aspect, and/or means configured to cause the apparatus to perform the method according to the fourth aspect.

According to an eleventh aspect, there is provided computer system, comprising: one or more processors; at least one data storage, and one or more computer program instructions to be executed by the one or more processors in association with the at least one data storage for carrying out the method according to the third aspect and/or the method according to the fourth aspect.

Even though the invention has been described above with reference to an example according to the accompanying drawings, it is clear that the invention is not restricted thereto but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the embodiment. It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. Further, it is clear to a person skilled in the art that the described embodiments may, but are not required to, be com bined with other embodiments in various ways.