Radio device and method in a wireless communication network

Abstract

A method performed by a radio device for controlling Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network is provided. The radio device determines (501) that a first HARQ data transmission has failed. The data comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU. The radio device selects (502) any one out or more out of a segmentation scheme for the transmitted data, and a re-concatenation and / or reassembly scheme for the transmitted data. The radio device retransmits (504) the data as a second HARQ data transmission according to the selected scheme.

Description

[0001] RADIO DEVICE AND METHOD IN A WIRELESS COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to a radio device and method performed thereby for controlling Hybrid Automatic Repeat Request data transmissions in a wireless communication network.

[0004] BACKGROUND

[0005] Subscriber node, Internet Protocol Multimedia Subsystem node, event subscriber node and method in a communication network

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0007] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0008] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0009] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0010] A 5G user-plane architecture and protocols are described with help of Figure 1. The UE is connected over the air via the Uu protocol with the RAN gNB. The gNB may be separated into a distributed unit (DU) and a centralized unit (CU), connected via F1 interface. The gNB is connected to the ON including a user-plane function (UPF). Typically, Internet Protocol (IP) data is transported via UE-gNB-UPF. The RAN protocol stack between the UE and the gNB includes the Service Data Adaptation Protocol (SDAP) protocol, for handling mapping of Quality of Service (QoS) flows as established by the UPF to data radio bearers (DRBs) established by the gNB. The protocol data convergence protocol (PDCP) is among others responsible for encryption and / or integrity protection and handover forwarding and retransmission. For handovers between gNBs, the Xn interface is employed. The radio link control (RLC) is among others responsible for segmentation of higher layer PDCP / IP data to fit the transport blocks (TBs) available for the lower layer over the air transmission. Also, retransmissions are based on automatic repeat request (ARQ) in acknowledged mode of RLC. Medium Access Protocol (MAC) supports scheduling of transmissions over the air, and entails the hybrid automated repeat request (HARQ) protocol. The physical layer (PHY) handles e.g. modulation and coding and the actual physical transmission.

[0011] Background on HARQ

[0012] In 3GPP radio access networks, e.g. 5G NR, the HARQ protocol facilitates retransmissions of data in case of transmission errors over the air.

[0013] For downlink (DL) HARQ, data transmissions are assigned by downlink control indicators (DCI) carried on the physical downlink control channel (PDCCH) and data is transmitted on the physical downlink shared channel (PDSCH). Different encoding is applied to these channels resulting in different error rates. HARQ feedback, i.e. positive (ACK) or negative acknowledgement (NACK) of data reception from the UE is transmitted as uplink (UL) control information (UCI) either on the physical uplink control channel (PLICCH) or physical uplink shared channel (PLISCH) multiplexed with other uplink data, since simultaneous transmission of PLICCH and PLISCH imposes challenges on the radio frequency (RF) implementation. Different encoding of these channels may result in different error rates, where transmission on PLICCH is typically more robust. However, it is noteworthy that the transmissions on the PLISCH undergo the UL HARQ protocol, i.e. are also subject to retransmissions to correct any decoding errors. Furthermore, the code rate for UCI on PUSCH can be adjusted by varying the number of resources for the UCI.

[0014] PUCCH

[0015] Besides HARQ feedback, the PUCCH may also carry scheduling requests and / or CSI reports. Due to carrier aggregation scheduling, the use of Code Block Groups (CBGs) and / or MIMO layers, the number of UCI bits and thus, the amount of resources for PUCCH may vary. To be optimized for different PUCCH payload sizes, different PUCCH formats (PF) were specified as summarized in the table below.

[0016] PLICCH format 4 differs from PLICCH format 3 in the use of orthogonal cover codes (OCC) and is used for Frequency Range (FR) 2-2.

[0017] To minimize the UCI bits, a dynamic HARQ codebook is used by default, meaning that HARQ feedback resources are only allocated for DL transmissions that actually take place. If carrier aggregation and CBG transmission is used, the HARQ codebook size may become very large. If there are not enough PLICCH resources for simultaneous HARQ feedback and CSI transmission, the CSI is dropped.

[0018] UCI on PUSCH

[0019] When UCI is transmitted on PUSCH, up to two HARQ feedback bits are always punctured. If more HARQ feedback bits are transmitted on PUSCH, rate matching is used for the UL data.

[0020] HARQ error cases

[0021] Since there is a probability that a UE misses a DCI / PDCCH carrying DL scheduling assignments, the UE would incorrectly calculate the HARQ codebook size. To solve this, downlink assignment index (DAI) counters are utilized in the DCI. The DAI field in the DCI indicates the amount of resources reserved for DL HARQ feedback. Thus, regardless of whether the device missed any previous scheduling assignments or not, the amount of resources, such as the expected count of HARQ feedback bits, to use for the DL HARQ feedback is known. The UE sets bit positions to “NACK” which correspond to the missed DCIs, such as missing DAI. Nevertheless, there is still an ambiguity as the gNB cannot distinguish whether a UE missed a DCI or a corresponding transport block, and usage of DAI comes with complexities in carrier aggregation scheduling on top of the use of Code Block Groups (CBGs) and MIMO layers, as these resources between individual carriers need to be coordinated.

[0022] The use of the counter DAI (cDAI) and total DAI (tDAI) in the DL DCI is illustrated in Figure 2 and allows the UE to detect missed DCIs and determine the HARQ codebook size for UCI transmission to the network. It should be noted that HARQ IDs in the example used in Figure 2 are used on different carriers for the sake of simplicity only. Each carrier has its own set of HARQ processes and may thus use the same HARQ ID as another carrier. The DAI pair in the first row denotes the actual cDAI / tDAI, while the DAI pair in the second row assumes only 2 bits for the DAI transmission, and the cDAI / tDAI to be provided in the DCI is the actual cDAI / tDAI mod 4. The DCI further informs the UE about the time offset between DCI reception and HARQ feedback transmission.

[0023] Figure 3 shows HARQ feedback provided in the UCI. The UE provides the HARQ- FB as a bitmap. Based on the DAIs, the UE calculates the size of the HARQ-FB bitmap and the bitmap positions for the corresponding HARQ ACK / NACKs. For missed DCIs, the UE sets NACK. Thus, the network cannot distinguish whether the UE had missed the DCI or whether it had been unable to decode the transport block.

[0024] Furthermore, if the gNB does not receive any HARQ feedback / UCI on PUCCH or PUSCH. In such a case, the gNB does not know whether the UE had missed the scheduling DCI or whether the UE transmitted HARQ feedback, which was however not detected by the gNB. Another approach that addresses the ambiguity is the one-shot HARQ feedback request, which was introduced in the context of NR-U. It gives the gNB the possibility to request the UE to send HARQ feedback for all HARQ processes. Other common failures of the downlink HARQ protocol are that transmission errors of the PUCCH lead to flipping of the transmitted HARQ feedback, e.g. from NACK to ACK, i.e. a false positive, or from ACK to NACK, i.e. a false negative. False negatives will lead to unnecessary retransmissions and thus, inefficient resource usage, and false positives may be addressed by the acknowledged mode (AM) of the radio link control (RLC) protocol.

[0025] HARQ timing

[0026] The slot timing between DL data transmission and HARQ feedback, denoted as K1 , is determined based on the K1 field in DCI. K1=0 means that the HARQ-FB is provided in the same slot, K1=1 means that the HARQ-FB is provided in the next slot, etc.

[0027] For NR-U, a non-numerical K1 value can be used, indicating that the network has not yet decided when the UE shall send the HARQ-FB for a given HARQ process. Instead, the network can, at a later point of time, request a “one-shot” HARQ feedback for all (active / non-active) HARQ processes. When the UE receives such a HARQ-FB request, it sets the HARQ-FB bits to ACK for successfully decoded transport blocks, and all others to NACK. The ACKs are only flushed when the UE receives a toggled New Data Indicator (NDI) for that HARQ process. As in legacy, the NACK may indicate to the network that the UE either missed the DCI or that it unsuccessfully decoded the corresponding TB.

[0028] Radio Link Control

[0029] The radio link control (RLC) protocol, which resides on top of the HARQ protocol, in acknowledged mode (AM), is able to detect and correct HARQ residual errors. Therefore, RLC maintains its own state of which data packets are already successfully received. This is based on RLC status reporting from the receiver. Counters and timers are employed to poll, trigger and if needed retransmit RLC status reports and retransmit RLC data until reception success is ensured. RLC status reports are considered data in the HARQ protocol, meaning they undergo HARQ retransmissions in case of unsuccessful reception. The drawback of RLC retransmissions is increased latency.

[0030] SUMMARY

[0031] An object of embodiments herein is to improve the performance of a wireless communication network. Embodiments herein may be understood to aim to provide an efficient mechanism for retransmitting radio link control packet data units using a selected scheme. This may be performed in order to enable a mechanism for controlling hybrid automatic repeat request data transmissions.

[0032] According to a first aspect of embodiments herein, the object is achieved by a method performed by a radio device for controlling Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network.

[0033] The radio device determines that a first HARQ data transmission has failed. The data comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU.

[0034] The radio device selects any one out or more out of a segmentation scheme for the transmitted data, and a re-concatenation and / or reassembly scheme for the transmitted data.

[0035] The radio device retransmits the data as a second HARQ data transmission according to the selected scheme.

[0036] According to a first aspect of embodiments herein, the object is achieved by a radio device configured to control Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network.

[0037] The radio device is configured to determine that a first HARQ data transmission has failed, wherein the data is adapted to comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU.

[0038] The radio device is configured to select any one out or more out of:

[0039] - a segmentation scheme for the transmitted data, and

[0040] - a re-concatenation and / or reassembly scheme for the transmitted data.

[0041] The radio device is configured to retransmit the data as a second HARQ data transmission according to the selected scheme. Embodiments herein target to handle HARQ data transmissions. Upon determining that a HARQ data transmission has failed, the radio device selects a scheme for retransmitting the data, and retransmits the data according to the selected scheme.

[0042] Embodiments herein bring the advantage of an efficient mechanism for controlling HARQ data transmissions, faster RLC retransmissions with lower overhead and an overall improved system spectral efficiency and latency for the end user. This is achieved by selecting a scheme for retransmitting the RLC PDU, and retransmitting the data as a second HARQ transmission, resulting in an improved performance of the wireless communication network.

[0043] BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0045] Figure 1 is a schematic diagram illustrating an 5G user-plane architecture according to prior art.

[0046] Figure 2 is a schematic diagram illustrating an example according to prior art.

[0047] Figure 3 is a schematic diagram illustrating an example according to prior art.

[0048] Figure 4 is a schematic block diagram illustrating embodiments of a wireless communications network.

[0049] Figure 5 is a flowchart depicting embodiments of a method in a radio device.

[0050] Figure 6 is a schematic block diagram illustrating a non-limiting example of a radio device according to embodiments herein.

[0051] Figure 7 shows an example of a communication system QQ100 in accordance with some embodiments.

[0052] Figure 8 shows a UE QQ200 in accordance with some embodiments.

[0053] Figure 9 shows a network node QQ300 in accordance with some embodiments.

[0054] Figure 10 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 9, in accordance with various aspects described herein.

[0055] Figure 11 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.

[0056] Figure 12 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION

[0057] As a part of developing embodiments herein the inventors identified a problem which first will be discussed.

[0058] A general problem with RLC retransmissions is their large delays, as RLC retransmissions are based on RLC timers, which are configured with delays allowing a certain number of, e.g., more spectrally efficient, HARQ retransmissions before triggering RLC retransmissions.

[0059] It is unclear how RLC retransmissions, with their functionality of segmentation and potentially also concatenation of higher layer payload data can be triggered more efficiently by lower layers.

[0060] An object of embodiments herein is to improve the performance of the wireless communications network by providing a more efficient HARQ transmission.

[0061] According to embodiments herein, methods for controlling retransmissions based on the reception of reliable HARQ feedback, such as downlink HARQ feedback, received on the uplink PUSCH, is provided. Further, embodiments herein provide a method for how RLC segmentation and re-concatenation and / or re-assembly may be applied in the RLC transmitter based on this reliable HARQ NACK.

[0062] According to examples of embodiments herein, a reliable HARQ NACK may trigger a retransmission of RLC data. The retransmitted data may comprise re-segmented RLC PDUs or RLC PDUs with re-segmented RLC data, in case of retransmission transport block size is lower than original. Adding RLC header fields may be required in this case.

[0063] Further, according to examples of embodiments herein, a reliable HARQ NACK may trigger a retransmission of RLC data. The retransmitted data may comprise reconcatenated and / or reassembled RLC PDUs or RLC PDUs with reassembled RLC data, in case of retransmission transport block size is larger than original. Removing RLC header fields may be performed in this case.

[0064] Examples of embodiments herein may e.g., provide the advantage of avoidance of redundant retransmission, faster RLC status reporting round trip time and an overall improved system spectral efficiency and latency for the end user. Further, examples of embodiments herein may bring the advantage of a reduction of overhead for RLC retransmissions.

[0065] Figure 4 is a schematic overview depicting a wireless communication network 100, wherein embodiments herein may be implemented. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0066] Network nodes, such as a radio device 110, operate in the wireless communication network 100. Each of the network nodes e.g. provides a number of cells and may use these cells for communicating with other network nodes. Each of the network nodes may be a transmission and reception point e.g., a radio access network node such as a base station, a radio base station, a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR / g Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE served by the network node depending e.g. on the radio access technology and terminology used.

[0067] UEs, such as a radio device 121, operate in the wireless communication network 100. The radio device 121 may e.g. be a UE, a wireless device, an NR device, a mobile station, a wireless terminal, an internet of things (loT) device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to- everything (V2X) device, Vehicle-to-Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to-lnfrastructure (V2I) device, a Vehicle-to-Network (V2N) device, a WiFi device, an LTE device, a non-access point (non-AP) STA, a STA, that communicates via a base station, and one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN) or the IMS network 105. It should be understood by the skilled in the art that the term UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0068] Methods herein may in one aspect be performed by the radio device 110, 121. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 4, may be used for performing or partly performing the methods of embodiments herein.

[0069] The cloud 190 may comprise a cloud network infrastructure. A cloud network infrastructure may e.g. be a collection of hardware and software elements such as computing power, networking, storage, and virtualization resources needed to enable cloud computing in a wireless communications network such as e.g. a communications network.

[0070] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0071] A method according to embodiments will now be described from the view of the radio device 110, 121 together with Figure 5. Figure 5 depicts example embodiments of a method performed by the radio device 110, 121 e.g., for controlling HARQ data transmissions in the wireless communication network 100. The radio device 110, 121 may comprise the radio device 110. The radio device 110 may, as mentioned above, be a network node, such as e.g., a radio access network node, a base station, a NodeB, an eN, or a gNB, to mention a few examples. The radio device 110, 121 may comprise the radio device 121. The radio device 121 may, as mentioned above, be a e.g., a UE, a wireless device, an NR device, a mobile station, a wireless terminal or an loT device, to mention a few examples. Thus, the method presented below is applicable to both DL and UL HARQ data transmissions. The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0072] Action 501

[0073] The radio device 110, 121 determines a status of a first HARQ data transmission. The data comprises comprising at least one RLC PDU. This may, as explained below e.g., mean that the radio device 110, 121 determines whether the first HARQ data transmission has failed or not. Alternatively, or additionally, it may e.g., mean that the radio device 110, 121 fails to determine whether or not the first HARQ data transmission has succeeded. In some embodiments, determining the status of the first HARQ data transmission comprises any one or more out of determining that the first HARQ data transmission has failed in response to receiving a HARQ NACK, and failing to determine that the first HARQ data transmission has succeeded in response to not receiving a HARQ Acknowledgement, ACK, within a first time period. Thus, when the radio device 110, 121 receives a NACK associated with the first HARQ transmission, the radio device 110, 121 determines that the first HARQ transmission has failed. Further, when the radio device 110, 121 does not receive a ACK within a e.g., configured time period, the radio device 110, 121 determines that it cannot determine whether or not the first HARQ data transmission has failed or succeeded, i.e., the radio device 110, 121 fails to determine that the first HARQ data transmission has succeeded. By failing to determine that the first HARQ transmission has succeeded, the radio device 110, 121 may assume, and thus determine, that the HARQ transmission has failed. In some examples of the above, receiving the NACK and / or not receiving the ACK may comprise receiving a reliable NACK and / or not receiving a reliable ACK. A reliable ACK and / or NACK may e.g., mean that the HARQ feedback, i.e., the ACK and / or NACK, has passed a cyclic redundancy check.

[0074] In some embodiments, determining that a first HARQ data transmission has failed comprises identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDlls to HARQ transport blocks.

[0075] Action 502

[0076] The radio device 110, 121 selecting any one out or more out of a segmentation scheme for the transmitted data, and a re-concatenation and / or reassembly scheme for the transmitted data. The segmentation transmission scheme may comprise segmenting the transmitted data before retransmission. This may mean that it is the segmented data that is transmitted in the HARQ retransmission. The re-concatenation and / or reassembly transmission scheme may comprise re-concatenating and / or reassembling the data that was transmitted in the first HARQ data transmission with other data.

[0077] In some embodiments, selecting the segmentation scheme or the re-concatenation and / or reassembly scheme is based on a size of a transport block size available for retransmitting the data. When the transport block size is smaller than the data, the segmentation scheme may be selected. Correspondingly, when the transport block size is larger than the data, the re-concatenation and / or reassembly scheme may be selected.

[0078] Action 503 In some embodiments, the radio device 110, 121 performs the selected scheme, such as the segmentation scheme or the re-concatenation and / or reassembly scheme. In other words, after selecting the scheme, the radio device 110, 121 segments and / or the re-concatenate and / or reassembles the transmitted data according to the selected scheme.

[0079] In some embodiments, performing the segmentation scheme comprises segmenting an RLC Service Data Unit, SDU, or an RLC SDU segment comprised in the RLC PDU. Each new RLC SDU segment is added to a respective first RLC PDU. Alternatively, performing the segmentation scheme comprises segmenting the RLC PDU into a plurality of first PDU segments. In other words, the radio device 110, 121 may generate a plurality of first RLC PDUs, where the respective first RLC PDUs comprises a respective RLC SDU segment. The respective RLC SDU segments are segments of the RLC SDU or RLC SDU segment comprised in RLC PDU in the first HARQ data transmission. Alternatively, in other words, the radio device 110, 121 may generate a plurality of first RLC PDU segments, where the respective first RLC PDU segments comprises a respective RLC PDU segment. The respective RLC PDU segments are segments of the RLC PDU comprised in the first HARQ data transmission.

[0080] Segmenting the RLC SDU, RLC SDU segment and RLC PDU may comprises determining a size of the resulting first RLC PDU. The size may be dependent on a transport block size available for the transmission of the resulting first RLC PDU.

[0081] In some embodiments, the segmentation scheme further comprises generating a sequence number for the respective first RLC PDUs or the respective first RLC PDU segment. The generated sequence number may be added in a header of the respective first RLC PDU or the respective first RLC PDU segment. The sequence number may be a sequence number that is not previously assigned. In other words, the segmentation scheme may comprise assigning a sequence number to the respective first RLC PDU or the respective first RLC PDU segment.

[0082] In some embodiments, a segment indication may be added in to the respective RLC PDU segments. The segment indication may e.g., indicate which part of the RLC PDU comprised in the first HARQ transmission is present the respective RLC PDU segments.

[0083] In some embodiments, performing the re-concatenation and / or reassembly scheme comprises re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs. The at least two RLC SDU segments are reconcatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU. Alternatively, performing the re-concatenation and / or reassembly scheme comprises re-concatenating and / or reassembling at least two RLC PDlls segments. The at least two RLC PDU segments are re-concatenated and / or reassembled into the second RLC PDU. In other words, the radio device 110, 121 may generate a second RLC PDU, where the second RLC PDU comprises the at least two RLC SDU segments. The at least two SDU segments comprise the RLC SDU segment comprised in the RLC PDU in the first HARQ data transmission and at least one further RLC SDU segment. The at least two RLC SDU segments may be segments belonging to the same RLC SDU. Alternatively, in other words, the radio device 110, 121 may generate a second RLC PDU segments, where the second RLC PDU comprises the at least two RLC PDU segments. The at least two RLC PDU segments comprise the RLC PDU segment comprised in the first HARQ data transmission and at least on other PDU segment. The at least two RLC PDU segments may be segments belonging to the same RLC PDU.

[0084] Re-concatenating and / or reassembling the at least two RLC SDU segments and the at least two RLC PDU segments may comprise determining a size of the resulting second RLC PDU. The size may be dependent on a transport block size available for the transmission of the resulting second RLC PDU.

[0085] In some embodiments, the sequence number is omitted in a header of the second PDU, for example when RLC Unacknowledged Mode (UM) or an RLC mode without RLC status reporting is employed.

[0086] Action 504

[0087] The radio device 110, 121 retransmits the data as a second HARQ data according to the selected scheme. This may e.g., mean that retransmitting the data comprises transmitting the second HARQ data transmission, where the second HARQ data transmission comprises segments of the data in the first HARQ data transmission when the segmentation scheme is selected, or the data in the first HARQ data transmission reconcatenated and / or reassembled with other data when the re-concatenation and / or reassembly scheme is selected.

[0088] In some embodiments, retransmitting the data comprises retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU. This depends on whether the segmentation scheme or the re-concatenation and / or reassembly scheme is selected, as explained above.

[0089] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above. According to embodiments herein, feedback for HARQ is received reliably, i.e. , the HARQ feedback has passed a cyclic redundancy check (CRC) and if needed is retransmitted until the CRC passes. In this case, HARQ feedback may serve as indicator of successful transmission for higher layer data or control information transmissions that are transmitted via HARQ.

[0090] Embodiments herein is applicable to both DL and UL HARQ, although the examples below focus mainly on DL HARQ. In DL HARQ, data transmissions are assigned via PDCCH / DCI and transmitted via PDSCH. HARQ feedback is assumed to be transmitted reliably via PUSCH, i.e., undergoing the UL HARQ protocol with its own feedback and retransmission scheme. Another way to determine HARQ reception status may be to expect the arrival of a reliable ACK within a time window. The latter may e.g., be used for contention-based UL. In this case, for DL HARQ, absence of a reliable ACK transmission, e.g., due to unresolved contention in UL, is treated as a NACK for DL HARQ. For contention-based UL, in the case of UL HARQ, absence of a reliable ACK is interpreted as NACK and may thus be considered as indicator for HARQ or higher layer retransmission, as further explained below.

[0091] According to examples of embodiments herein, retransmissions of RLC PDUs in RLC UM may be triggered by HARQ NACK receptions provided as local NACK to RLC, i.e. for RLC PDUs of a certain logical channel included in the NACKed HARQ transport block. For this purpose, the transmitter side RLC / HARQ entities, such as the radio device 110, 121 , may maintain a mapping of RLC PDUs per HARQ transport block, also in case no RLC PDU sequence numbers are included. A different identifier, e.g. a hash of the RLC PDU may be employed. This mapping is specific for a certain time or time frame when a transport block is transmitted, not necessarily for a HARQ identifier, since this HARQ identifier is reused after a certain time, while required RLC PDU retransmissions included in a HARQ transport block at times before that HARQ round trip time, may still be required to be retransmitted.

[0092] According to some examples of embodiments herein, assuming NR RLC UM as a baseline, where one RLC UM PDU includes only one RLC SDU or RLC SDU segment, the local NACK triggers segmentation of the RLC UM SDU, or RLC UM SDU segment, included in the NACKed RLC UM PDU. A sequence number may be added in RLC PDUs comprising the RLC SDU segments. In other words, the original data included in the HARQ transport block is not retransmitted. Instead, modified data is transmitted, such as the new RLC SDU segments, and also e.g., modified RLC PDU protocol headers, in this case including a sequence number. Segmentation only needs to apply when a transport block sizes, or more specifically the number of bits in the transport block available for this specific RLC entity, for the retransmission is smaller than for the original data transmission. Otherwise, the same RLC PDU may be retransmitted. For the new sequence number assignments for the RLC PDUs including segments, a sequence number that was not yet used may to be assigned.

[0093] According to some examples of embodiments herein, assuming NR RLC UM as baseline, in case a local NACK triggers retransmissions with a transport block size large enough for several RLC UM PDUs and these RLC UM PDUs comprises segments of RLC UM SDUs, re-concatenation and / or reassembly of these RLC SDU segments may be attempted to form a RLC UM PDU comprise the complete RLC SDU, if possible, according to the transport block size. In this example, previously included sequence numbers in the RLC UM PDU with segments may not be required anymore, i.e. , they may be omitted from protocol headers. It is noted that this embodiment of “reassembly” may be configured to be applied while the previous embodiment of “segmentation at retransmission” may be configured to not be applied, i.e., the functionality is independent of each other.

[0094] According to some examples of embodiments herein, similarly as in LTE RLC AM according to current standards, assuming LTE RLC UM as a baseline, where one RLC UM PDU may include several RLC SDUs or RLC SDU segments, which may be denoted also RLC concatenation, the local NACK may trigger re-segmentation of the RLC UM PDU. Necessary protocol header fields of the RLC UM PDU segments may be added to indicate which segments of the original RLC UM PDU are being retransmitted, e.g., a segmentation offset field indicating to which byte segments of the RLC UM PDU the RLC UM PDU segment belongs to. Further, indicators of whether a first byte of the original RLC UM PDU or a last byte of the RLC UM PDU is included may be added as header fields. It is noteworthy that in case the LTE RLC UM PDU includes only segments of one RLC SDU, similar methods as in NR, as described above, may be applied.

[0095] According to some examples of embodiments herein, assuming LTE RLC UM as baseline, in case a local NACK triggers retransmission of an RLC UM PDU segment, and the transport block size for the retransmission is larger than the RLC UM PDU segment, re-concatenation and / or reassembly of this RLC UM PDU segment with other RLC UM PDU segments may be attempted to form a complete RLC UM PDU. In this case, the additional protocol headers, e.g., as mentioned above, of the RLC UM PDU segments may be omitted, i.e., only the protocol header fields of the original RLC UM PDU may be required. It may thus be checked whether the potentially resulting RLC UM PDU would fit in the transport block size, to determine whether the re-concatenation / reassembly is attempted. It is noteworthy that in case the LTE RLC UM PDU includes only segments of one RLC SDU, similar methods as in NR, as described above, may be applied.

[0096] The methods described above apply to the transmitter side. At the receiver side, reassembly of complete RLC SDUs is achieved based on reception of transmitted or retransmitted RLC SDU segments, for which the corresponding RLC SDU and the received segments, e.g., bytes are identified based on the included RLC PDU header fields. Potential duplicate reception of RLC SDU segments is handled by discarding, based on identification of the duplicate data in similar manner. This means legacy methods may be applied in the receiver, even though the transmitter side handles transmissions more efficiently, according to examples of embodiments herein.

[0097] To perform the method actions above, the radio device 110, 121 is e.g., configured to control HARQ data transmissions in the wireless communication network 100. The radio device 110, 121 may comprise an arrangement depicted in Figure 6.

[0098] The radio device 110, 121 may comprise an input and output interface 600 configured to communicate with each other. The input and output interface 600 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0099] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 610 of a processing circuitry in the radio device 110, 121 depicted in Figure 6, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the radio device 110, 121. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the radio device 110, 121.

[0100] The radio device 110, 121 and / or processor 610 is e.g., configured to control HARQ data transmissions in the wireless communication network 100.

[0101] The radio device 110, 121 and / or processor 610 is configured to determine that a first HARQ data transmission has failed. The data is adapted to comprises at least one RLC Packet Data Unit, PDU, The radio device 110, 121 and / or processor 610 is configured to select any one out or more out of:

[0102] - A segmentation scheme for the transmitted data, and

[0103] - a re-concatenation and / or reassembly scheme for the transmitted data.

[0104] The radio device 110, 121 and / or processor 610 is configured to retransmit the data as a second HARQ data transmission according to the selected scheme.

[0105] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to determine that the first HARQ data transmission has failed by any one or more out of:

[0106] - Receiving a HARQ Negative Acknowledgement, NACK, and

[0107] - not receiving a HARQ Acknowledgement, ACK, within a first time period.

[0108] In some embodiments, the HARQ NACK is a reliable HARQ NACK.

[0109] In some embodiments, the HARQ ACK is a reliable HARQ ACK.

[0110] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to perform the selected scheme.

[0111] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to perform the segmentation scheme by any one out of:

[0112] - Segmenting an RLC Service Data Unit, SDU, or RLC SDU segment comprised in the RLC PDU, wherein each new RLC SDU segment is added to a respective first RLC PDU.

[0113] - segmenting the RLC PDU into a plurality of first PDU segments.

[0114] In some embodiments, the segmentation scheme may further be adapted to comprise to generate a sequence number for the respective first RLC PDUs or the respective first RLC PDU segments, and add a generated sequence number in a header of the respective first RLC PDUs or the respective first RLC PDU segments.

[0115] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to perform the re-concatenation and / or reassembly scheme by any one out of:

[0116] - Re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs. The at least two RLC SDU segments are adapted to be reconcatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU,

[0117] - re-concatenating and / or reassembling at least two RLC PDUs segments, wherein the at least two RLC PDU segments are adapted to be re-concatenated and / or reassembled into a second RLC PDU. In some embodiments, a sequence number is adapted to be omitted in a header of the second RLC PDU.

[0118] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to retransmit the data by retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU.

[0119] In some embodiments, the radio device 110, 121 and / or processor 610 may further be configured to determine that the first HARQ data transmission has failed by identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDUs to HARQ transport blocks.

[0120] The radio device 110, 121 may further comprise respective a memory 620 comprising one or more memory units. The memory 620 comprises instructions executable by the processor 610 in the radio device 110, 121.

[0121] The memory 620 is arranged to be used to store instructions, data, configurations, identifiers, HARQ data transmissions, RLC PDUs, RLC SDUs, RLC SDU segments, RLC PDU segments, parameters, applications to perform the methods herein when being executed in the radio device 110, 121.

[0122] In some embodiments, a computer program 630 comprises instructions, which when executed by the at least one processor 610, cause the at least one processor 610 of the radio device 110, 121 to perform the actions above.

[0123] In some embodiments, a respective carrier 640 comprises the respective computer program 630, wherein the carrier 640 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0124] Thus, embodiments herein may disclose the radio device 110, 121 e.g., configured to control HARQ data transmissions in the wireless communications network 100. The radio device 110, 121 comprises the processor 610 and the memory 620, said memory 620 comprising instructions executable by said processor 610 whereby said radio device 110, 121 is operative to perform any of the methods herein.

[0125] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0126] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0127] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0128] Embodiments

[0129] Below, some example Embodiments 1-20 are shortly described. See e.g., Figures 4-6.

[0130] Embodiment 1. A method performed by a radio device 110, 121 e.g., for controlling Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network 100, the method comprising any one or more out of: determining 501 that a first HARQ data transmission has failed, wherein the data comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU, selecting 502 any one out or more out of:

[0131] - a segmentation scheme for the transmitted data, and

[0132] - a re-concatenation and / or reassembly scheme for the transmitted data, and retransmitting 504 the data as a second HARQ data transmission according to the selected scheme.

[0133] Embodiment 2. The method according to embodiment 1 , wherein determining 501 that the first HARQ data transmission has failed comprises any one or more out of:

[0134] - receiving a reliable HARQ Negative Acknowledgement, NACK, and

[0135] - not receiving a reliable HARQ Acknowledgement, ACK, within a first time period.

[0136] Embodiment 3. The method according to any of embodiments 1-2, wherein the method further comprises: performing 503 the selected scheme.

[0137] Embodiment 4. The method according to any of embodiments 3 wherein performing 503 the segmentation scheme comprises any one out of:

[0138] - segmenting an RLC Service Data Unit, SDU, or RLC SDU segment comprised in the RLC PDU, wherein each new RLC SDU segment is added to a respective first RLC PDU.

[0139] - segmenting the RLC PDU into a plurality of first PDU segments.

[0140] Embodiment 5. The method according to embodiment 4, wherein the segmentation scheme further comprises generating a sequence number for the respective first RLC PDUs or the respective first RLC PDU segments, and adding a generated sequence number in a header of the respective first RLC PDUs or the respective first RLC PDU segments.

[0141] Embodiment 6. The method according to embodiment 3, wherein performing 503 the re-concatenation and / or reassembly scheme comprises any one out of:

[0142] - re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs, wherein the at least two RLC SDU segments are re-concatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU, - re-concatenating and / or reassembling at least two RLC PDlls segments, wherein the at least two RLC PDU segments are re-concatenated and / or reassembled into a second RLC PDU.

[0143] Embodiment 7. The method according to embodiment 6, wherein a sequence number is omitted in a header of the second RLC PDU.

[0144] Embodiment 8. The method according to any of embodiments 1-7, wherein retransmitting 504 the data comprises retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU.

[0145] Embodiment 9. The method according to any of embodiments 1-8, wherein determining 501 that a first HARQ data transmission has failed comprises identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDUs to HARQ transport blocks.

[0146] Embodiment 10. A computer program 630 comprising instructions, which when executed by a processor 610, causes the processor 630 to perform actions according to any of the embodiments 1-9.

[0147] Embodiment 11. A carrier 640 comprising the computer program 630 of embodiment 10, wherein the carrier 640 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0148] Embodiment 12. A radio device 110, 121 e.g., configured to control Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network 100, the radio device 110, 121 further being configured to any one or more out of: determine that a first HARQ data transmission has failed, wherein the data is adapted to comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU, select any one out or more out of:

[0149] - a segmentation scheme for the transmitted data, and

[0150] - a re-concatenation and / or reassembly scheme for the transmitted data, and retransmit the data as a second HARQ data transmission according to the selected scheme. Embodiment 13. The radio device 110, 121 according to embodiment 12, wherein the radio device 110, 121 is further configured to determine that the first HARQ data transmission has failed by any one or more out of:

[0151] - receiving a reliable HARQ Negative Acknowledgement, NACK, and

[0152] - not receiving a reliable HARQ Acknowledgement, ACK, within a first time period.

[0153] Embodiment 14. The radio device 110, 121 according to any of embodiments 12- 13, wherein the radio device 110, 121 is further configured to: perform the selected scheme.

[0154] Embodiment 15. The radio device 110, 121 according to any of embodiments 14 wherein the radio device 110, 121 is configured to perform the segmentation scheme by any one out of:

[0155] - segmenting an RLC Service Data Unit, SDU, or RLC SDU segment comprised in the RLC PDU, wherein each new RLC SDU segment is added to a respective first RLC PDU.

[0156] - segmenting the RLC PDU into a plurality of first PDU segments.

[0157] Embodiment 16. The radio device 110, 121 according to embodiment 15, wherein the segmentation scheme is further adapted to comprise to generate a sequence number for the respective first RLC PDUs or the respective first RLC PDU segments, and add a generated sequence number in a header of the respective first RLC PDUs or the respective first RLC PDU segments.

[0158] Embodiment 17. The radio device 110, 121 according to embodiment 14, wherein the radio device 110, 121 is further configured to perform the re-concatenation and / or reassembly scheme by any one out of:

[0159] - re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs, wherein the at least two RLC SDU segments are adapted to be reconcatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU,

[0160] - re-concatenating and / or reassembling at least two RLC PDUs segments, wherein the at least two RLC PDU segments are adapted to be re-concatenated and / or reassembled into a second RLC PDU. Embodiment 18. The radio device 110, 121 according to embodiment 17, wherein a sequence number is adapted to be omitted in a header of the second RLC PDU.

[0161] Embodiment 19. The radio device 110, 121 according to any of embodiments 12-

[0162] 18, wherein the radio device 110, 121 is further configured to retransmit the data by retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU.

[0163] Embodiment 20. The radio device 110, 121 according to any of embodiments 12-

[0164] 19, wherein the radio device 110, 121 is further configured to determine that the first HARQ data transmission has failed by identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDUs to HARQ transport blocks.

[0165] ADDITIONAL EXPLANATION

[0166] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0167] Figure 7 shows an example of a communication system QQ100 in accordance with some embodiments.

[0168] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110, being examples of the radio device 110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0169] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O- CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112, being examples of the radio device 121) to the core network QQ106 over one or more wireless connections.

[0170] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0171] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0172] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0173] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0174] As a whole, the communication system QQ100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0175] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0176] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0177] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0178] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0179] Figure 8 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0180] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0181] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0182] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0183] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0184] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0185] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0186] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0187] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0188] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0189] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0190] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

[0191] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0192] Figure 9 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0193] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0194] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cel l / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0195] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0196] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units. The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0197] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0198] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0199] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0200] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0201] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0202] Figure 10 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0203] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 8 and 9, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0204] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0205] Figure 11 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O- Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0206] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0207] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0208] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0209] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0210] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0211] Figure 12 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 7 and / or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure 7 and / or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure 7 and / or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.

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

[0213] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

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

[0215] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0216] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0217] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0218] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the performance of the wireless communications network by providing a more efficient HARQ transmission, avoidance of redundant retransmission, faster RLC status reporting round trip time, an overall improved system spectral efficiency and latency for the end user, and a reduction of overhead for RLC retransmissions.

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

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

[0221] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0222] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0223] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS:Claims1. A method performed by a radio device (110, 121) for controlling Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network 100, the method comprising: determining (501) that a first HARQ data transmission has failed, wherein the data comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU, selecting (502) any one out or more out of:- a segmentation scheme for the transmitted data, and- a re-concatenation and / or reassembly scheme for the transmitted data, and retransmitting (504) the data as a second HARQ data transmission according to the selected scheme.

2. The method according to claim 1 , wherein determining (501) that the first HARQ data transmission has failed comprises any one or more out of:- receiving a HARQ Negative Acknowledgement, NACK, and- not receiving a HARQ Acknowledgement, ACK, within a first time period.

3. The method according to claim 2, wherein any one or more out of:- the HARQ NACK is a reliable HARQ NACK, and- the HARQ ACK is reliable HARQ ACK.

4. The method according to any of claims 1-3, wherein the method further comprises: performing (503) the selected scheme.

5. The method according to any of claims 4 wherein performing (503) the segmentation scheme comprises any one out of:- segmenting an RLC Service Data Unit, SDU, or RLC SDU segment comprised in the RLC PDU, wherein each new RLC SDU segment is added to a respective first RLC PDU.- segmenting the RLC PDU into a plurality of first PDU segments.

6. The method according to claim 5, wherein the segmentation scheme further comprises generating a sequence number for the respective first RLC PDlls or the respective first RLC PDU segments, and adding a generated sequence number in a header of the respective first RLC PDUs or the respective first RLC PDU segments.

7. The method according to claim 4, wherein performing (503) the reconcatenation and / or reassembly scheme comprises any one out of:- re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs, wherein the at least two RLC SDU segments are re-concatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU,- re-concatenating and / or reassembling at least two RLC PDUs segments, wherein the at least two RLC PDU segments are re-concatenated and / or reassembled into a second RLC PDU.

8. The method according to claim 7, wherein a sequence number is omitted in a header of the second RLC PDU.

9. The method according to any of claims 1-8, wherein retransmitting (504) the data comprises retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU.

10. The method according to any of claims 1-9, wherein determining (501) that a first HARQ data transmission has failed comprises identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDUs to HARQ transport blocks.

11. A computer program (630) comprising instructions, which when executed by a processor (610), causes the processor (630) to perform actions according to any of the claims 1-10.

12. A carrier (640) comprising the computer program (630) of claim 11, wherein the carrier (640) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

13. A radio device (110, 121) configured to control Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network 100, the radio device (110, 121) further being configured to: determine that a first HARQ data transmission has failed, wherein the data is adapted to comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU, select any one out or more out of:- a segmentation scheme for the transmitted data, and- a re-concatenation and / or reassembly scheme for the transmitted data, and retransmit the data as a second HARQ data transmission according to the selected scheme.

14. The radio device (110, 121) according to claim 13, wherein the radio device (110, 121) is further configured to determine that the first HARQ data transmission has failed by any one or more out of:- receiving a HARQ Negative Acknowledgement, NACK, and- not receiving a HARQ Acknowledgement, ACK, within a first time period.

15. The radio device (110, 121) according to claim 14, wherein any one or more out of:- the HARQ NACK is a reliable HARQ NACK, and- the HARQ ACK is reliable HARQ ACK.

16. The radio device (110, 121) according to any of claims 13-15, wherein the radio device (110, 121) is further configured to: perform the selected scheme.

17. The radio device (110, 121) according to any of claims 16 wherein the radio device (110, 121) is configured to perform the segmentation scheme by any one out of:- segmenting an RLC Service Data Unit, SDU, or RLC SDU segment comprised in the RLC PDU, wherein each new RLC SDU segment is added to a respective first RLC PDU.- segmenting the RLC PDU into a plurality of first PDU segments.

18. The radio device (110, 121) according to claim 17, wherein the segmentation scheme is further adapted to comprise to generate a sequence number for the respective first RLC PDlls or the respective first RLC PDU segments, and add a generated sequence number in a header of the respective first RLC PDlls or the respective first RLC PDU segments.

19. The radio device (110, 121) according to claim 16, wherein the radio device (110, 121) is further configured to perform the re-concatenation and / or reassembly scheme by any one out of:- re-concatenating and / or reassembling at least two RLC SDU segments comprised in different RLC PDUs, wherein the at least two RLC SDU segments are adapted to be reconcatenated and / or reassembled into a single RLC SDU comprised in a second RLC PDU,- re-concatenating and / or reassembling at least two RLC PDUs segments, wherein the at least two RLC PDU segments are adapted to be re-concatenated and / or reassembled into a second RLC PDU.

20. The radio device (110, 121) according to claim 19, wherein a sequence number is adapted to be omitted in a header of the second RLC PDU.

21. The radio device (110, 121) according to any of claims 13-20, wherein the radio device (110, 121) is further configured to retransmit the data by retransmitting the respective first RLC PDU, the respective first RLC PDU segments, or the second RLC PDU.

22. The radio device (110, 121) according to any of claims 13-21 , wherein the radio device (110, 121) is further configured to determine that the first HARQ data transmission has failed by identifying the RLC PDU comprised in the HARQ data transmission based on a mapping of RLC PDUs to HARQ transport blocks.

23. A radio device (110, 121) configured to control Hybrid Automatic Repeat Request, HARQ, data transmissions in a wireless communication network 100, the radio device (110, 121) comprises a processor (610) and a memory (620)m said memory (620) comprising instructions executable by said processor (610) whereby the radio device (110, 121) is operative to:determine that a first HARQ data transmission has failed, wherein the data is adapted to comprises at least one Radio Link Control, RLC, Packet Data Unit, PDU, select any one out or more out of:- a segmentation scheme for the transmitted data, and - a re-concatenation and / or reassembly scheme for the transmitted data, and retransmit the data as a second HARQ data transmission according to the selected scheme.The radio device (110, 121) according to claim 22, wherein the radio device (110, 121) operative perform the method according to any claims 2-10.

Images