Retransmissions by a communication node

Abstract

A communication node (12A) is disclosed. The communication node (12A) receives (700) signaling (24) that governs retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received. The communication node (12A), based on the received signaling (24), handles (710) retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

Description

[0001] RETRANSMISSIONS BY A COMMUNICATION NODE

[0002] TECHNICAL FIELD

[0003] The present application relates generally to a communication node and relates more particularly to data unit retransmisions by the communication node.

[0004] BACKGROUND

[0005] The Radio Link Control (RLC) protocol is a component of a communication protocol stack, which may be positioned in a data link layer (Layer 2), e.g., between a Medium Access Control (MAC) layer below and a Packet Data Convergence Protocol (PDCP) layer above. As part of the user plane and control plane, RLC plays a role in managing data transmission between communication nodes, providing functions such as segmentation, concatenation, retransmission (in Acknowledged Mode), and in-sequence delivery to ensure reliable communication.

[0006] RLC Acknowledged Mode (AM) is a reliable, bidirectional data transfer mode that ensures error-free delivery through Automatic Repeat reQuest (ARQ) mechanisms. In AM, the sender segments and numbers RLC Service Data Units (SDUs) into Protocol Data Units (PDUs), which are then transmitted and monitored for successful reception. If a PDU is lost or corrupted, the receiver detects the missing sequence numbers and responds with an RLC Status Report, which explicitly indicates which PDUs have been received successfully and which require retransmission, i.e. , ACK / NACK status. The sender then retransmits the missing PDUs for which a negative acknowledgement (NACK) was received, ensuring insequence and lossless data delivery. This mechanism enhances reliability, making AM suitable for error-sensitive applications such as TCP-based services and signaling messages. However, the retransmission process introduces additional latency, making AM less ideal for delay-sensitive applications like real-time voice or video.

[0007] For extended Reality (XR) traffic or traffic with low latency requirements in terms of small packet delay budgets (PDBs), PDU discard timers may exist at the communication device with values that are based on the importance of the packet data unit (PDU). These timers can be quite short especially for low importance (PDU) traffic. If a PDU discard timer governing a PDU expires before a successful acknowledgement or retransmission of the PDU, the PDU is discarded, e.g., to prevent indefinite retransmissions.

[0008] It is desirable to speed up the retransmission process, e.g., to better accommodate delay-sensitive traffic. If the receiver sends a RLC Status Report too late, the sender may have already discarded one or more PDUs that would have been accounted for in the RLC Status Report. This would result in lower quality of experience (QoE). On the other hand, ifthe receiver sends an RLC Status Report too early, it may prompt unnecessary retransmissions which could have been successfully received.

[0009] One approach to speed up the retransmission process is to allow a sender to ‘autonomously’ perform a retransmission of a PDU, e.g., without having to wait for an RLC Status Report. However, challenges exist with how to enable autonomous retransmissions in a resource-efficient way, e.g., to avoid autonomous retransmissions unnecessarily consuming transmission resources and thereby reducing system capacity.

[0010] SUMMARY

[0011] Some embodiments herein introduce signaling to govern autonomous retransmission by a communication node, i.e., retransmission of a data unit (e.g., RLC PDU) without having received a report of whether a prior transmission of the data unit was successfully received. The signaling may thereby enable autonomous retransmission to be configurable and / or adaptable, e.g., as needed to account for changing circumstances or conditions. Where the communication node is a communication device (e.g., user equipment, UE), for instance, the signaling may be transmitted to the communication device from a communication network. The signaling from the network in this case may enable the network to control or otherwise govern autonomous uplink transmission by the communication device, e.g., as needed to manage or adapt to changing demands on system capacity.

[0012] The signaling in some embodiments may include a configuration of one or more conditions under which the communication node is to, or is allowed to, trigger or perform autonomous retransmission. One such example may be a condition that a result of a signal measurement performed by the communication node be above a signal measurement threshold, e.g., where the signal measurement threshold may be indicated by the signaling. The signal measurement threshold may for instance be set in a way that targets preventing cell-edge or bad radio condition communication nodes from performing autonomous retransmissions. As another example, the condition(s) may include a condition that a time remaining before discard of a data unit is below a time threshold. The time threshold may for instance be set in a way that targets selectively performing autonomous retransmissions for data units that are delay-critical, but avoiding the associated resource consumption for other data units that are not (yet) delay-critical.

[0013] More particularly, embodiments herein include a method performed by a communication node. The method comprises receiving signaling that governs retransmission of a data unit by the communication node without the communication node having received a report of whether a prior transmission of the data unit was successfully received. In some embodiments, the method further comprises, based on the received signaling, handling retransmission of a data unit by the communication node without the communication nodehaving received a report of whether a prior transmission of the data unit was successfully received.

[0014] Other embodiments herein include a method comprising transmitting, to a communication node, signaling that governs retransmission of a data unit by the communication node without the communication node having received a report of whether a prior transmission of the data unit was successfully received.

[0015] Other embodiments herein include a method performed by a communication node. The method comprises receiving signaling that governs which data units the communication node is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted. The method in some embodiments may further comprise handling multiplexing of data units according to the received signaling.

[0016] Other embodiments herein include a method comprising transmitting signaling that governs which data units a communication node is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted.

[0017] Embodiments herein further include corresponding apparatus, computer programs, and carriers of those computer programs.

[0018] BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a block diagram of communication nodes according to some embodiments.

[0020] Figure 2 is a block diagram of a communication node according to some embodiments.

[0021] Figure 3A is an exemplary graph of frame latency measured over radio access network (RAN) according to some embodiments.

[0022] Figure 3B is a graph of cumulative distribution functions of a number of transport blocks required to deliver a video frame according to some embodiments.

[0023] Figure 4 is a graph of characteristics of XR traffic arrival compared to typical webbrowsing and VoIP traffic, according to some embodiments.

[0024] Figure 5 illustrates an exemplary format of Delay Status Reporting (DSR) according to some embodiments.

[0025] Figure 6 is a call flow diagram of a procedure for combined polling and autonomous retransmission.

[0026] Figure 7 is a flow diagram of a method performed by a communication node in accordance with particular embodiments.

[0027] Figure 8 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.Figure 9 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0028] Figure 10 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0029] Figure 11 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0030] Figure 12 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0031] Figure 13 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0032] Figure 14 is a flow diagram of a method performed by a communication node in accordance with other particular embodiments.

[0033] Figure 15 is a block diagram of a communication node according to some embodiments.

[0034] Figure 16 is a block diagram of a network node according to some embodiments. Figure 17 is a block diagram of a communication system according to some embodiments.

[0035] Figure 18 is a block diagram of a communication system according to other embodiments.

[0036] Figure 19 is a block diagram of a wireless device according to some embodiments. Figure 20 is a block diagram of a network node according to other embodiments. Figure 21 is a block diagram of a virtualization environment according to other embodiments.

[0037] DETAILED DESCRIPTION

[0038] Figure 1 shows communication nodes 12A and 12B according to some embodiments, generally referred to as communication nodes 12. Each of the communication nodes 12A, 12B may be configured for use in or with a communication network, e.g., a 3rdGeneration Partnership Project (3GPP) network. Communication node 12A may for example be a communication device (e.g., a user equipment, UE) or a network node such as a radio network node or a core network node. Likewise, communication device 12B may itself be a communication device or a network node such as a radio network node or a core network node.

[0039] Communication node 12A as shown performs a transmission 14 of a data unit 16 towards communication node 12B, e.g., in the sense that the transmission 14 conveys the data unit 16 or includes data from the data unit 16. The data unit 16 may for example be aprotocol data unit (PDU) of a layer of a transmission protocol stack of the communication node 12A, e.g., a PDU of a Radio Link Control (RLC) layer.

[0040] The communication node 12A may perform the transmission 14 in an acknowledged mode (AM), e.g., an RLC AM or other mode that ensures error-free delivery through Automatic Repeat reQuest (ARQ) mechanisms. In these and other embodiments, then, communication node 12B may be configured to transmit a report 18 of whether the transmission 14 of the data unit 16 was successfully received by communication node 12B. Where the data unit 16 is an RLC PDU, for instance, the report 18 may be an RLC Status Report. Upon reception of this report 18, the communication node 12A may be configured to perform a retransmission 20 of the data unit 16.

[0041] The communication node 12A according to embodiments herein though is capable of “autonomously” performing the retransmission 20 of the data unit 16, even before or without having received any report 18 of whether the prior transmission 14 of the data unit 16 was successfully received. When the retransmission 20 is performed without the communication node 12A having received a report 18 of whether the prior transmission 14 of the data unit 16 was successfully received, the retransmission 20 may optionally be referred to as an ‘autonomous retransmission’ for convenience. The ‘autonomous’ nature of the retransmission 20 may thereby refer to the retransmission 20 being performed independent of any such report 18, so that the retransmission 20 is not triggered or controlled by such report 18 but rather is self-initiated by the communication node 12A.

[0042] In this context, embodiments herein introduce signaling 24 that governs autonomous retransmission 20 by the communication node 12A. The signaling 24 may for example govern whether, when, and / or how autonomous retransmission 20 is, or is allowed, to be triggered or performed by the communication node 12A. The communication node 12A may receive this signaling 24 from communication node 12B or from another communication node (not shown).

[0043] In some embodiments where the communication node 12A is a communication device, the communication node 12A may receive the signaling 24 from a network node 22 of a communication network. Figure 2 shows one such example where the communication node 12A is a communication device that receives communication service from a communication network 10. As shown, the network node 22 transmits the signaling 24 to the communication node 12A in the form of a communication device. In some embodiments, the network node 22 that transmits the signaling 24 is the communication node 12B to which the communication node 12A performs autonomous retransmission 20. Either way, the signaling 24 in this case enables the communication network 10 to configure, control, adapt, and / or otherwise govern autonomous retransmission 20 by the communication node 12A, e.g., as needed to manage or adapt to changing circumstances or demands on system capacity.The signaling 24 may for example govern whether and / or under what condition(s) 26 the communication node 12A is to, or is allowed to, trigger or perform autonomous retransmission 20. The signaling 24 in this case may include a configuration of one or more conditions 26 under which the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of the data unit 16 without having received a report 18 of whether the prior transmission 14 of the data unit 16 was successfully received.

[0044] In some embodiments, any one of the condition(s) 26 being fulfilled means that the communication node 12A is to, or is allowed, to trigger or perform an autonomous retransmission 20. In this case, the communication node 12A is to, or is allowed to, trigger or perform the retransmission 20 if any of the condition(s) 26 are fulfilled. In other embodiments, all of the condition(s) 26 must be fulfilled in order for the communication node 12A to trigger or perform an autonomous retransmission 20, or to be allowed to trigger or perform an autonomous retransmission 20. In this case, then, the communication node 12A is to, or is allowed to, trigger or perform the retransmission 20 if all of the condition(s) 26 are fulfilled.

[0045] In some embodiments, the condition(s) 26 are specific to a certain data unit 16 to be retransmitted, in which case the condition(s) 26 must be fulfilled for a certain data unit 16 in order for the communication node 12A to perform, or be allowed to perform, an autonomous retransmission 20 of that certain data unit 16. In other embodiments, the condition(s) 26 are not specific to any certain data unit 16, in which case the condition(s) 26 being fulfilled means that the communication node 12A may perform or be allowed to perform an autonomous retransmission 20 of any data unit 16.

[0046] In some embodiments, the condition(s) 26 include a condition that a result of a signal measurement performed by the communication node 12A be above or below a signal measurement threshold. The signaling 24 in this case may indicate the signal measurement threshold. In one specific embodiment, the condition may be that the result of a signal measurement be above the signal measurement threshold. The signal measurement threshold in this case may be set in a way that targets preventing the communication node 12A from performing autonomous retransmission 20 if the communication node 12A has poor channel conditions, e.g., at a cell-edge. The condition in this case may thereby aim to conserve transmission resources that would be consumed by potentially repeated autonomous retransmissions in poor channel conditions.

[0047] In other embodiments, the condition(s) 26 include a condition that a time remaining before discard of a data unit 16 is below a time threshold. The time threshold may for instance be set in a way that targets selectively performing autonomous retransmission 20 for data units 16 that are delay-critical and thereby at risk of being discarded, but avoiding the associated resource consumption for other data units that are not (yet) delay-critical. Insome embodiments, this time remaining before discard may be reflected by a value of a discard timer for a data unit 16, in which case the condition may be that the value of the discard timer be below the time threshold. In other embodiments, the condition is specified in terms of a packet delay budget (PDB) that remains for the data unit 16, in which case the condition may be that the value of the PDB remaining be below the time threshold.

[0048] Other examples of condition(s) 26 are given later herein.

[0049] In any case, the communication node 12A may evaluate the condition(s) 26 for fulfilment to decide whether or not to trigger or perform autonomous retransmission 20 of a data unit 16. If the condition(s) 26 are not fulfilled, the communication node 12A may refrain from triggering or performing the autonomous retransmission 20, e.g., opting to instead wait for the report 18. On the other hand, if the condition(s) 26 are fulfilled, the communication node 12A may proceed to trigger or perform the autonomous retransmission 20, i.e. , without waiting for the report 18.

[0050] In other embodiments, though, such as in those of Figure 2, fulfilment of the condition(s) 26 may just prompt the communication node 12A to transmit a report 30 indicating that one or more of the condition(s) 26 are fulfilled. Where the condition(s) 26 are associated with a measurement by the communication node 12A, this report 30 may be a measurement report that reports an event associated with a measurement, e.g., where the reported event corresponds to fulfilment of the condition(s) 26. Either way, in the case of Figure 2, the network node 22 may determine based on the report 30 to configure and / or command the communication node 12A to trigger or perform autonomous retransmission 20. That is, the condition(s) 26 in these embodiments function as condition(s) 26 which must be fulfilled in order for the communication node 12A to trigger or perform autonomous retransmission 20, but the communication node 12A must still be configured or commanded by the communication network 10 to actually do so. The report 30 may thereby assist the communication network 10 with a decision about whether to configure or command the communication node 12A to trigger or perform autonomous retransmission 20.

[0051] Consider now some embodiments herein as exemplified in a context where the communication network 10 may be a 5G or6G network, the communication node 12A may be exemplified as a user equipment (UE), communication node 12B may be exemplified as a network node 22 in the form of a gNB, the retransmission 20 may be exemplified as an uplink (UL) retransmission, the data unit 16 may be exemplified as an RLC PDU, and the report 18 may be exemplified as an RLC Status Report.

[0052] 5G is the fifth generation of mobile communications, addressing a wide range of use cases from enhanced mobile broadband (eMBB) to ultra-reliable low-latency communications (LIRLLC) to massive machine type communications (mMTC). 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NRphysical and higher layers are reusing parts of the LTE specification, and to that add needed components when motivated by new use cases.

[0053] Low-latency high-rate applications such as extended Reality (XR) and cloud gaming are important in 5G era. XR may refer to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It is an umbrella term for different types of realities including Virtual reality (VR), Augmented reality (AR), Mixed reality (MR), and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. 5G NR is designed to support applications demanding high rate and low latency in line with the requirements posed by the support of XR and cloud gaming applications in NR networks. 3GPP Release 17 contains a study item on XR Evaluations for NR (See 3GPP TR 23.700-60 V18.0.0). The main objectives are to identify the traffic model for each application of interest, the evaluation methodology and the key performance indicators of interest for relevant deployment scenarios, and to carry out performance evaluations accordingly in order to investigate possible standardization enhancements in potential follow-up SI / WI.

[0054] Low-latency high-rate XR applications

[0055] The low-latency applications like XR and cloud gaming require bounded latency, not necessarily ultra-low latency. The end-to-end latency budget may be in the range of 20-80 ms, which needs to be distributed over several components including application processing latency, transport latency, radio link latency, etc. For these applications, short transmission time intervals (TTIs) or mini-slots targeting ultra-low latency may not be effective.

[0056] Figure 3A shows an example of frame latency measured over radio access network (RAN), excluding application & core network latencies. It can be seen that there exist frame latency spikes in RAN. The sources for the latency spikes may include queuing delay, timevarying radio environments, time-varying frame sizes, among others. Tools that can help to remove latency spikes are beneficial to enable better 5G support for this type of traffic.

[0057] In addition to bounded latency requirements, the applications like XR and cloud gaming also require high-rate transmission. This can be seen from the large frame sizes originated from this type of traffic. The typical frame sizes may range from tens of kilobytes to hundreds of kilobytes. The frame arrival rates may be 60 or 120 frames per second (fps). As a concrete example, a frame size of 100 kilobytes and a frame arrival rate of 120 fps can lead to a rate requirement of 95.8 Mbps.

[0058] A large video frame is usually fragmented into smaller IP packets and transmitted as several transport blocks (TBs) over several TTIs in RAN. Figure 3B shows an example of the cumulative distribution functions of the number of transport blocks required to deliver a video frame with size ranging from 20 KB to 300 KB. For example, Figure 3B shows that for delivering the frames with a size of 200 KB each, the median number of needed TBs is 5.The characteristics of XR traffic arrival are quite distinct from typical web-browsing and VoIP traffic as shown in Figure 4. It is well expected that the arrival time is quasi-periodic and largely predictable as VoIP. However, its data size is order of magnitude larger than VoIP, as discussed above. In addition, similar to web-browsing, the data size is different at every application PDU arrival instance due to dynamics of contents and human motion.

[0059] As mentioned above, many XR applications will generate traffic periodically with a variable size. When the application packet enters the internet, the initial packet may be transmitted into a single PDU in the network or may be segmented several PDUs. One application packet could, for instance, correspond to one or several IP packets.

[0060] IP packets will arrive to the PDCP layer i.e., PDCP SDUs, and the PDCP layer will create PDCP PDUs and will deliver then to lower layers. When an IP packet arrives to PDCP, the PDCP layer starts a PDCP discard timer. When this timer expires, the PDCP discards the PDCP SDU as well as the corresponding PDCP Data PDU. If the PDCP PDU was delivered to lower layers, PDCP indicates the discard to lower layers. Lower layers e.g. RLC will discard the PDCP PDUs (RLC SDU) if these RLC SDU or any segment of the RLC SDU has not yet been transmitted to lower layers.

[0061] As discussed above, an application PDU e.g., a video frame, is divided into multiple IP packets. All these IP packets which belong to one video frame can be defined as PDU Set.

[0062] 3GPP Rel-18 XR features

[0063] SA2 in 3GPP TR 23.700-60 V18.0.0 identified that PDU sets could be assigned with a PDU Set Importance indicator. This parameter can be used to identify the importance of a PDU Set within a QoS flow. RAN may use it for PDU Set level packet discarding in presence of congestion.

[0064] *PDU Set as defined by 23.700-60: PDU Set: A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services, as used in TR 26.926). In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts all or of the information unit, when some PDUs are missing.

[0065] In Rel18 XR Wl new solutions for UL PDU Set handling was introduced however no explicit information about the PDU Sets is delivered to the network.

[0066] Furthermore, two new buffer reporting enhancements were introduced in Rel-18; Delay Status Reporting (DSR) and Refined Buffer Status Reporting (Refined BSR). The DSR is a new MAC CE, with separate handling from the legacy BSR. The format for the DSR is as shown in Figure 5.RLC Retransmissions

[0067] Some embodiments exploit an RLC retransmission mechanism as specified in 2.3 of 3GPP TS 38.322 V18.0.0 is triggered at the TX RLC entity upon the reception of the RLC status report from the RX RLC entity. With the RLC status report indicating the RLC SNs which are negatively acknowledged.

[0068] Some embodiments include methods to speed up the RLC retransmissions.

[0069] According to embodiments herein, the RLC Tx entity can trigger an autonomous retransmission without receiving the RLC status report.

[0070] There currently exist certain challenge(s). The current Radio Link Control (RLC) acknowledgement mode (AM) involves a hand-shaking mechanism between the (RLC) Tx entity and (RLC) Rx entity where the Rx entity informs the Tx entity via an RLC status report about the packets that have been successfully / unsuccessfully received i.e., ACK / NACK status. Based on this status report, the Tx entity can then retransmit the packets for which a negative acknowledgement (NACK) was received. For uplink (UL) transmissions, the network provides the RLC status report to the UE. However, it is up to network implementation when the status reports are sent in the downlink (DL). In addition, there is also a polling mechanism specified where the Tx entity can request the Rx entity to send the RLC status report.

[0071] For XR traffic or traffic with low latency requirements in terms of small packet delay budgets (PDBs), new discard timers (in addition to an old discard timer) are based on the importance of the packet data unit (PDU). These timers can be quite short especially for low importance (PDU) traffic. For UL traffic, the network is not fully aware of the remaining time of the PDB or remaining time to discard for the PDUs as there is no exact mapping between the RLC PDUs and delay critical data although some estimate of this information is available at the network. However, it is not aware how long the RLC PDU(s) has been queued and as a result it is possible that the network provides the RLC status report too late, resulting in the PDU already being discarded or too early resulting in unnecessary retransmission of the PDU which could have been successfully received by the network. The discarding issue could result in significant loss of quality of experience (QoE) especially if high importance (PDU) traffic is unnecessarily discarded.

[0072] Autonomous retransmissions operate as a solution to speed up such RLC retransmissions, i.e., the RLC Tx entity can trigger a retransmission without receiving the RLC status report. As an example, the autonomous retransmissions may be used for UL transmissions i.e., UE triggers autonomous RLC retransmissions without an RLC status report from the gNB.

[0073] However, one issue related to the autonomous retransmission is with respect to its effect on UL capacity. If too many UEs or a UE performs autonomous retransmission toooften, then this leads to resource starvation for other UEs in the network. This is often the case with UEs in cell-edge conditions where usually the data sent in the UL is subject to segmentation i.e., a single PDU is split into multiple small PDUs. Then, autonomous retransmission results in 2X consumption of UL resources where X is the segmentation factor, so more the segmentation, the double the resource consumption. The other aspect is the relation to the PDU sets this is still unclear in terms of design.

[0074] Embodiments herein provide solutions to prevent UEs from causing resource starvation and considering the design of autonomous transmissions considering PDU sets.

[0075] Some embodiments in this regard ppropose solutions to control the autonomous retransmissions or provide conditions under which a UE (in UL) can perform autonomous retransmissions:

[0076] 1. Prevent UEs in bad channel conditions for e.g., cell-edge UEs from performing autonomous retransmissions by configuring signal thresholds.

[0077] 2. Tie the autonomous retransmissions with the PDU sets considering how much or what percentage of the PDU sets have been transmitted.

[0078] 3. Tie the trigger of autonomous retransmissions on the remaining time to discard or the related PDB / PSDB.

[0079] Methods to control the triggering of the RLC autonomous retransmissions.

[0080] Certain embodiments may provide one or more of the following technical advantage(s). Prevents resource starvation for other UEs in the network due to autonomous retransmissions and enables the use of such retransmissions in a controlled manner.

[0081] Network Configured Conditions for UE to perform Autonomous Retransmissions In a first embodiment, the network 10 configures a UE capable of performing autonomous retransmissions with a set of one or more conditions under which such a retransmission is allowed to be performed (autonomously). The condition(s) may be examples of condition(s) 26 in Figure 1-2.

[0082] In a second embodiment, the condition is a signal strength threshold value either in terms of received signal strength indicator (RSSI), radio signal reference power (RSRP), radio signal reference quality (RSRQ) or signal to interference plus noise ratio (SINR).

[0083] A network can configure only UEs that satisfy certain signal strength values / thresholds to perform autonomous retransmissions. The network can identify such UEs based on the reporting of their signal strength information. If the reported signal strength information is greater (or less) than a network chosen threshold, the network will configure the UE with autonomous retransmissions. For example, the network can choose not to configure the cell-edge or bad ratio condition UEs with a signal strength < network chosen threshold or vice-versa with autonomous retransmissions. This configuration can beRRC or MAC depending on the need of configuration update speed.

[0084] In another aspect of this embodiment, the UE can be configured with a signal strength threshold value. Upon applying this threshold value, the UE can check if it is eligible to perform autonomous retransmissions by comparing its signal strength value (RSSI / RSRP / RSRQ / SINR) against the configured threshold value.

[0085] In yet another aspect of this embodiment, the UE can evaluate the eligibility criterion in two ways, if the current signal strength value is greater (or less) than the configured threshold:

[0086] • The UE is allowed to directly perform autonomous retransmissions. For example, if the signal strength information is less (or greater) than the configured threshold, such UEs are usually cell-edge or have bad radio conditions and should not perform autonomous RLC retransmissions.

[0087] • The UE is not directly allowed to perform autonomous retransmissions. Upon evaluating the signal strength information against the configured threshold, the UE will inform the network (e.g., via report 30 in Figure 2) that it now satisfies or does not satisfy the signal strength condition to perform an autonomous retransmission. The UE can inform the network in the UL using an UL control message (for e.g., UAI based on RRC). The network can then configure the UE with an autonomous retransmission based on the previous embodiment.

[0088] In a third embodiment, another embodiment which can be combined with the previous embodiments, is that the network configures the UE with the logical channel IDs (LCIDs) which are allowed to have autonomous retransmissions. The network could further restrict autonomous retransmissions to specific QoS Flow IDs (QFI) within an LCID.

[0089] The network can also configure / command multiplexing restrictions i.e. , data within a LCID or among LCIDs which should not be concatenated in the same transport block. These embodiments exemplify Embodiments AAAA1-AAAA9 in Group A Embodiments herein.

[0090] For example, the network may request the UE to not concatenate MAC SDUs from the same or different LCIDs which contain data so that its time left compared to a certain threshold is below a configured value. This could be that data having a PDSB left (PSDB minus queued time) or discard timer value is below a certain threshold should not be multiplexed in the same transport block with data which PDSB left, or discard timer value is above the said threshold.

[0091] In another example a first transmitted RLC PDU from a first LCID with autonomous retransmissions is not allowed to be multiplexed with data from second LCID without autonomous retransmission. While if configured with an autonomous retransmission, theRLC PDU is allowed to be multiplexed with data from second LCID.

[0092] Additionally, the network could configure a condition that limits autonomous retransmissions to certain size transport blocks. In other words, the network could configure a maximum transport block size threshold. When a transport block is above the configured threshold, the UE would not perform autonomous retransmissions. In another aspect of this embodiment, the network can alternatively or additionally configure a condition that limits autonomous retransmissions based on the size of the segmentation the data undergoes. For example, if a PDU is segmented more (or less) than X times, then it is not or is allowed to perform autonomous retransmissions. The size of the transport block explained above can also refer to the size of the segmentation.

[0093] This can be used in combination with all the above.

[0094] In a fourth embodiment, when transmitting data based on PDU Set information, the condition for autonomous retransmissions can be dependent on the amount or percentage of data that has been transmitted from a specific PDU Set. It may be deemed unnecessary to start autonomous retransmissions if too little of the PDU Set data has been transmitted or too much of the PDU set data is yet to be initially transmitted. Thus, a threshold can be set so that a certain amount of data needs to have been initially transmitted before autonomous retransmissions can be performed. For example, if at least X #PDUs in a PDU set has been transmitted is when the UE is allowed to trigger an autonomous retransmission.

[0095] Another condition can be a percentage or amount of successful reception of PDUs within a PDU set for e.g., assuming 4 PDUs within a PDU set and the configured amount is 1 , autonomous retransmissions can be performed on subsequent PDUs only after the first PDU of this PDU set was successfully received. If the configured amount is 2, then the UE is allowed to perform autonomous retransmissions on subsequent PDUs only after two PDUs of this PDU set were successfully received. Forthose PDUs Essentially, autonomous retransmissions should be related to whether a PDU set can be transmitted. For example, assuming 4 PDUs belong to a PDU set,

[0096] In another aspect of this embodiment, the condition to perform autonomous retransmissions is tied to the discarding of data, i.e. the discard timer or PDB or PSDB. It may be so that when time is very short to discard there is no time to wait for RLC status reports to perform RLC retransmissions and the only chance is to rely on autonomous retransmissions. Thus, a time threshold can be configured by the network which will trigger autonomous retransmission of the data if the remaining time to discard is lower than the set value. This trigger may also be tied to the PDU Set, i.e. so that all data from the same PDU Set will perform retransmissions if any data in the PDU Set is below the time threshold or if only all the data from the PDU set is below the time threshold.

[0097] This percentage can also be coupled with a remaining time threshold, i.e. bothcertain remaining times to discard need to be left and certain amounts of data need to have been transmitted for it to be deemed worthwhile to perform autonomous retransmissions.

[0098] In yet another embodiment any combination of the above thresholds may be configured together. E.g., a certain amount of data needs to have been transmitted from a PDU Set while also the SINR need to be high enough.

[0099] Further, one or more of the above thresholds is combined with number of HARQ retransmissions. For example, if the remaining time is larger than a first threshold and the number of performed re-transmissions exceeds a second threshold the UE triggers an autonomous RLC re-transmission.

[0100] In a fifth embodiment, after the RLC autonomous transmission is triggered but before transmission is not yet started, it can wait for a certain time and the triggered process can be terminated if certain conditions are met. These conditions for termination may be referred to as termination condition(s), e.g., as referred to in Embodiments AAA1-AAA3 and A28-A35. For example, when the autonomous transmission is triggered, a timer is started. When the timer is expired, the autonomous retransmission process is terminated although the transmission did not occur yet. The timer value is configured by the network. The timer can be also expired immediately when any one or combination of following conditions are met so that unnecessary autonomous retransmission is avoided.

[0101] • If the earliest time for sending RLC retransmission, e.g., the time that the next grant indicates, is later than when the timer is expired.

[0102] • if the number of HARQ NACK exceeds the threshold or,

[0103] • if the PDB discard timer is expired or,

[0104] • if the any one or more RLC SDUs that are planned to be autonomously transmitted are considered as being received, e.g., RLC status report indicates ACKs of any planned RLC SDUs to be autonomously transmitted or • if the RLF (radio link failure) is detected

[0105] In some embodiments the number of RLC re-transmissions (TX_COUNT) includes autonomous re-transmission while other embodiments exclude autonomous retransmissions from TX_COUNT. In one embodiment, the autonomous re-transmissions are limited by new RRC parameter “maximum autonomous re-transmissions”.

[0106] Network Signaling Aspects:

[0107] In a sixth embodiment, although the UE can perform autonomous retransmissions, additionally the network can configure this UE with an indication for whether it is allowed to perform an autonomous retransmission. Further, the network can also configure the UE with an activation and deactivation command for such autonomous retransmissions, e.g., as an example of Embodiment A36.The indication for allowance and the (de)activation command can be different for e.g., the network can always configure a UE to allow autonomous retransmissions on a higher configuration level (for e.g., RRC-level), but based on certain conditions (as listed below), activate, or deactivate such autonomous retransmissions on a lower configuration level (for e.g., MAC CE). This indication can be carried in a DL control signaling (for e.g., DL RRC / MAC CE).

[0108] In another aspect, the network can be based on certain conditions (as listed above) only allow UEs to perform autonomous retransmissions on a higher configuration level (for e.g., RRC-level), then reconfigure the UE to disallow or vice-versa.

[0109] An example of an RRC configuration is as follows:

[0110] RLC-Config information element

[0111] - ASN1 START

[0112] - TAG-RLC-CONFIG-START

[0113] RLC-Config ::= CHOICE {

[0114] am SEQUENCE {

[0115] ul-AM-RLC UL-AM-RLC,

[0116] dl-AM-RLC DL-AM-RLC

[0117] },

[0118] um-Bi-Directional SEQUENCE {

[0119] ul-UM-RLC UL-UM-RLC,

[0120] dl-UM-RLC DL-UM-RLC

[0121] },

[0122] um-Uni-Directional-UL SEQUENCE {

[0123] ul-UM-RLC UL-UM-RLC

[0124] },

[0125] um-Uni-Directional-DL SEQUENCE {

[0126] dl-UM-RLC DL-UM-RLC

[0127] UL-AM-RLC ::= SEQUENCE {

[0128] sn-FieldLength SN-FieldLengthAM OPTIONAL, -- Cond Reestab t-PollRetransmit T-PollRetransmit,

[0129] pollPDU PollPDU,

[0130] poll Byte PollByte,maxRetxThreshold ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 }

[0131] DL-AM-RLC ::= SEQUENCE {

[0132] sn-FieldLength SN-FieldLengthAM OPTIONAL, -- Cond Reestab t-Reassembly T-Reassembly,

[0133] t-StatusProhibit T-StatusProhibit

[0134] }

[0135] UL-UM-RLC ::= SEQUENCE {

[0136] sn-FieldLength SN-FieldLengthUM OPTIONAL -- Cond Reestab }

[0137] DL-UM-RLC ::= SEQUENCE {

[0138] sn-FieldLength SN-FieldLengthUM OPTIONAL, -- Cond Reestab t-Reassembly T-Reassembly

[0139] }

[0140] T-PollRetransmit ::= ENUMERATED {

[0141] ms5, ms10, ms15, ms20, ms25, ms30, ms35,

[0142] ms40, ms45, ms50, ms55, ms60, ms65, ms70,

[0143] ms75, ms80, ms85, ms90, ms95, ms100, ms105,

[0144] ms110, ms115, ms120, ms125, ms130, ms135,

[0145] ms140, ms145, ms150, ms155, ms160, ms165,

[0146] ms170, ms175, ms180, ms185, ms190, ms195,

[0147] ms200, ms205, ms210, ms215, ms220, ms225,

[0148] ms230, ms235, ms240, ms245, ms250, ms300,

[0149] ms350, ms400, ms450, ms500, ms800, rnslOOO,

[0150] ms2000, ms4000, ms1-v1610, ms2-v1610, ms3-v1610, ms4-v1610, spare"!}

[0151] PollPDU ::= ENUMERATED {

[0152] p4, p8, p16, p32, p64, p128, p256, p512, p1024, p2048, p4096, p6144, p8192, p12288, p16384,p20480, p24576, p28672, p32768, p40960, p49152, p57344, p65536, infinity, spare8, spare7, spare6, spare5, spare4, spare2, spare"!}Pol I Byte ::= ENUMERATED {

[0153] kB1, kB2, kB5, kB8, kB10, kB15, kB25, kB50, kB75,kB100, kB125, kB250, kB375, kB500, kB750, kBIOOO,

[0154] kB1250, kB1500, kB2000, kB3000, kB4000, kB4500, kB5000, kB5500, kB6000, kB6500, kB7000, kB7500,

[0155] mB8, mB9, mB10, mB11, mB12, mB13, mB14, mB15, mB16, mB17, mB18, mB20, mB25, mB30, mB40, infinity, spare20, spare19, spare18, spare17, spare16,

[0156] spare15, spare14, spare13, spare12, spare'll,

[0157] sparelO, spare9, spare8, spare7, spare6, spare5,

[0158] spare4, spare3, spare2, spare"!}

[0159] T-Reassembly ::= ENUMERATED {

[0160] msO, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

[0161] ms40, ms45, ms50, ms55, ms60, ms65, ms70,

[0162] ms75, ms80, ms85, ms90, ms95, ms100, ms110,

[0163] ms120, ms130, ms140, ms150, ms160, ms170,

[0164] ms180, ms190, ms200, spare"!}

[0165] T-StatusProhibit ::= ENUMERATED {

[0166] msO, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

[0167] ms40, ms45, ms50, ms55, ms60, ms65, ms70,

[0168] ms75, ms80, ms85, ms90, ms95, ms'! 00, ms'! 05,

[0169] ms'! 10, ms115, ms120, ms125, ms130, ms135,

[0170] ms140, ms145, ms150, ms155, ms160, ms165,

[0171] ms170, ms175, ms180, ms185, ms190, ms195,

[0172] ms200, ms205, ms210, ms215, ms220, ms225,

[0173] ms230, ms235, ms240, ms245, ms250, ms300,

[0174] ms350, ms400, ms450, ms500, ms800, ms1000,

[0175] ms1200, ms1600, ms2000, ms2400, spare2, sparel}

[0176] SN-FieldLengthUM ::= ENUMERATED {size6, size12}

[0177] SN-FieldLengthAM ::= ENUMERATED {size12, size18}

[0178] RLC-Config-v1610 ::= SEQUENCE {

[0179] dl-AM-RLC-v1610 DL-AM-RLC-V1610}

[0180] RLC-Config-v1700 ::= SEQUENCE {

[0181] dl-AM-RLC-v1700 DL-AM-RLC-v1700,

[0182] dl-UM-RLC-v1700 DL-UM-RLC-v1700

[0183] }

[0184] DL-AM-RLC-V1610 ::= SEQUENCE {

[0185] t-StatusProhibit-v1610 T-StatusProhibit-v1610 OPTIONAL, -- Need R

[0186] }

[0187] DL-AM-RLC-V1700 ::= SEQUENCE {

[0188] t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL -- Need R }

[0189] DL-UM-RLC-V1700 ::= SEQUENCE {

[0190] t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL -- Need R }

[0191] T-StatusProhibit-v1610 ::= ENUMERATED { ms1, ms2, ms3, ms4, spare4, spare3, spare2, spare"!}

[0192] T-ReassemblyExt-r17 ::= ENUMERATED {ms210, ms220, ms340, ms350, ms550, ms1100, ms1650, ms2200}

[0193] Auto-ReTx-r19 BOOLEAN

[0194] - TAG-RLC-CONFIG-STOP

[0195] - ASN1STOP

[0196] Now consider some embodiments herein as applicable to timely RLC retransmissions, where polling enhancements and / or autonomous retransmissions may be pursued. In some embodiments, both solutions can be configured independently. In other embodiments, there is a unified solution and depending on network configuration either one can be used. This comes down to the triggers used for the two solutions. As detailed below, a common trigger in the remaining time to discard can be used as the framework for a unified solution. Of course, it is still possible to configure either one of the two solutions.Regarding timely RLC Retransmissions, autonomous retransmissions could have an effect on system capacity, suggesting that only the polling enhancements would be appropriate. To address this, both solutions could be specified by 3GPP and it be left to the network to configure one or the other. Further, as a compromise, another solution could be where the two solutions are combined as follows: If the remaining time drops below a threshold, poll is triggered. If scheduling request (SR) is not received within a time, then Tx can autonomously retransmit the delay critical packet.

[0197] Regarding triggers for Polling Enhancements and Autonomous Retransmissions, in order to better understand the autonomous retransmission solution and its interaction with the polling enhancements, different triggers may be considered:

[0198] A. Configured number of failed HARQ retransmissions

[0199] B. Remaining time of an RLC PDU less than a threshold

[0200] Configured number of failed HARQ retransmissions

[0201] For (A), the network in some embodiments can configure a threshold of failed HARQ retransmissions beyond which the UE can perform an autonomous RLC retransmission i.e. , stop the associated HARQ process early and trigger RLC retransmission. However, the early stopping of the HARQ process can already be achieved in the following ways:

[0202] 1. gNB can just configure lesser number of overall HARQ retransmissions. The outcome is the same as if the (lower number of) overall HARQ retransmissions fail, RLC retransmissions are triggered earlier.

[0203] 2. gNB schedules HARQ retransmissions using the NDI bit:

[0204] a. If in a scheduling DCI, the NDI bit remains the same (i.e., not flipped), then the gNB implies that the previous HARQ attempt was unsuccessful, and the UE should continue HARQ retransmissions for this process. But if the NDI bit was flipped, then gNB implies that the previous HARQ transmission was successful, and the UE can flush its buffer related to this HARQ process. b. Thus, if the gNB realizes that subsequent HARQ retransmissions for an RLC PDU will be unsuccessful, it can send a scheduling DCI with the NDI bit flipped (i.e., provide a fake ACK for a HARQ retransmission), thereby flushing the HARQ buffer for this PDU. Then, the gNB sends an RLC status report with the corresponding PDU marked as NACK thereby triggering an early RLC retransmission. Essentially, send a fake ACK for HARQ to trigger early RLC retransmission.

[0205] c. The gNB can also always trigger an RLC retransmission if the RLC status report is sent before the HARQ retransmissions are complete.As the gNB is aware of the HARQ information, there are ample ways using legacy / current specifications to trigger an early RLC retransmission. There is no gain to achieve in latency with autonomous retransmissions considering HARQ.

[0206] Thus, in some embodiments, HARQ is not considered as a trigger for autonomous retransmission, e.g., a failed number of HARQ retransmissions is not considered as a trigger for autonomous retransmission

[0207] Remaining time of an RLC PDU less than a threshold

[0208] In (B), considering that the gNB is not aware of the timing information of an RLC PDU at the UE, some embodiments trigger autonomous retransmission based on the remaining time of the PDU. In some embodiments, the remaining time threshold of the PDU is also applicable to the polling mechanism as the RLC status reports can be sent either too frequently (too early) or sparsely (too late). Frequent status reports are not always necessary because not all the RLC PDUs are delay critical at a given time i.e. , overheads in transmission. On the other hand, it cannot be too sparse (too late) because this would result in the RLC PDU to be discarded if received too late. Essentially, the current polling mechanism might not always be synchronized with the delay requirements of the AMD PDU as the gNB is unaware of the remaining time to discard. Thus, the current polling mechanism cannot consider the delay criticality of the RLC PDU in the buffer, i.e., it is a trade-off between transmission overhead and timely reception of the RLC status PDU. As a result, such enhancements to the polling mechanism could consider the delay criticality of the AMD PDU in the buffer. The advantages are that the polling is set only when required and it helps the Rx entity to send the RLC status report in a timely manner. Some embodiments accordingly consider the remaining time threshold of an RLC PDU as a trigger for both autonomous retransmissions and enhanced polling mechanism.

[0209] However, some embodiments consider that, for the autonomous retransmission to be relevant, the remaining time threshold allows for the HARQ retransmissions to complete. For example, with a BLER target of 10%, the success rate of the initial transmission is 90% and with subsequent HARQ retransmissions, the success rate is 99% making the autonomous retransmissions relevant for 1% of failure cases. Thus, some embodiments combine the autonomous retransmission with the polling enhancement, e.g., consistent with R2-2409958, Discussion on Fast RLC Retransmission, Apple, Rel-19, November 18-22, 2024, Orlando, USA. The procedure of this combined approach is as shown in Figure 6.

[0210] As shown in Figure 6, when the remaining time is less than the threshold_polling, it triggers the polling bit to be set. Further, when the remaining time is less than the threshold_retx, UE can trigger an autonomous retransmission if an RLC status report wasnot received. Such a mechanism allows completion of the HARQ retransmissions avoiding the case when an autonomous retransmission is triggered even though the RLC PDU was successfully received at the gNB.

[0211] In Figure 6, the two timers are only shown for the purposes of illustration; these can also be combined into one timer. This also gives the flexibility to configure the UE with either the polling enhancement or autonomous retransmission by either setting threshold_polling or threshold_retx to zero. Hence, for autonomous retransmission and polling enhancements considering the remaining time threshold of a PDU, some embodiments: (A) Configure two thresholds to trigger the enhanced polling mechanism and autonomous retransmissions respectively; (B) Configure a single timer to monitor the remaining time of an RLC PDU for the enhanced polling mechanism and autonomous retransmission, or configure two timers respectively; and / or (C) By setting one of the two thresholds to zero, the gNB can configure either the enhanced polling mechanism or autonomous retransmission.

[0212] Consider now additional Triggers for Autonomous Retransmissions in some embodiments. Considering the impact on UL capacity, cell-edge users with bad radio channel conditions should not be allowed to perform autonomous retransmissions as the RLC PDU undergoes a lot of segmentation resulting in a 2X consumption of the UL resources per UE. For example, if segmented into 4 PDUs, it results in eight times the UL resources. In addition to segmentation, the link adaptation for such users is also quite robust and there is no need for autonomous retransmissions. Accordingly, the network in some embodiments may configure the UEs to perform autonomous retransmission based on signal strength.

[0213] Consider now other embodiments related to UE Capability for the combined Tx-Rx approach. It is appropriate that the UE support for this approach is based on a new optional UE capability. But the combined Tx-Rx approach involves two sets of features, one, where the Tx side stops transmissions of an outdated SDU and two, where the Rx side abandons the outdated SDUs based on a local timer. Bundling the two features into a single capability forces the vendors to implement both features thereby delaying implementation and time to market. For UE capability, some embodiments avoid bundling such independent features into a single capability. Some embodiments thereby define two capabilities to cover the Tx-side and Rx-side features allowing vendors to stagger their implementation of this feature resulting in faster time to market.

[0214] In particular, some embodiments define two UE capabilities for the combined Tx-Rx approach as follows: (A) Tx-side UE capability, where the Tx side stops the transmissions of an outdated SDUs, including new related procedures fore.g., RLF; and (B) Rx-side UE capability, where the Rx side abandons the outdated SDU based on a new RLC timer, abandoned SDUs are positively acknowledged in the RLC STATUS report.Although some embodiments are written with respect to the UE communicating with the network and the problem described above relates to UL transmissions, embodiments herein are applicable in any case where a Tx entity communicates with the Rx entity without loss of generality. Further, although described in the context of RLC retransmissions, the embodiments are also equally applicable to any other form of retransmission for e.g., HARQ. Furthermore, although described for UL transmissions, the same is also applicable for DL and sidelink (SL) / device-to-device (D2D) transmissions, where two devices communicate directly with each other.

[0215] In view of the modifications and variations herein, Figure 7 depicts a method performed by a communication node 12A in accordance with particular embodiments. The method includes receiving signaling 24 that governs retransmission 20 of a data unit 16 by the communication node 12A without the communication node 12A having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 700).

[0216] In some embodiments, the signaling 24 includes a configuration of one or more conditions 26 under which the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received if any of the one or more conditions 26 are fulfilled. In other embodiments, the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received if all of the one or more conditions 26 are fulfilled. In some embodiments, the one or more conditions 26 include a condition that a result of a signal measurement performed by the communication node 12A be above or below a signal measurement threshold. In some embodiments, the configuration indicates the signal measurement threshold. In some embodiments, the one or more conditions 26 include a condition that the data unit 16, or a transmission unit containing the data unit 16, has a size that is smaller than a size threshold. In some embodiments, the configuration indicates the size threshold. In some embodiments, the condition is that a transmission unit containing the data unit 16 has a size that is smaller than the size threshold, wherein the transmission unit is a transport block. In some embodiments, the one or more conditions 26 include a condition that the data unit 16 is segmented into a number of segments that is more or less than a segmentation number threshold. In some embodiments, the configuration indicates the segmentation number threshold. In some embodiments, the data unit 16 belongs to a set of data units 16, wherein the one or moreconditions 26 include a condition that at least a threshold number or percentage of data units 16 in the set have been transmitted. In some embodiments, the configuration indicates the threshold number or percentage. In some embodiments, the data unit 16 belongs to a set of data units 16, wherein the one or more conditions 26 include a condition that at least a threshold number or percentage of data units 16 in the set have been transmitted and successfully received. In some embodiments, the configuration indicates the threshold number or percentage. In some embodiments, the set of data units 16 is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer. In some embodiments, the one or more conditions 26 include a condition. In some embodiments, the condition includes a time remaining before discard of the data unit 16 is below a time threshold. In other embodiments, the condition includes a value of a discard timer for the data unit 16 is below a time threshold. In yet other embodiments, the condition includes a packet delay budget that remains for the data unit 16 is below a time threshold. In some embodiments, the data unit 16 belongs to a set of data units 16, wherein the one or more conditions 26 include a condition. In some embodiments, the condition includes a time remaining before discard of any data unit 16 in the set is below a time threshold. In other embodiments, the condition includes a value of a discard timer for any data unit 16 in the set is below a time threshold. In yet other embodiments, the condition includes a packet delay budget that remains for any data unit 16 in the set is below a time threshold. In some embodiments, the data unit 16 belongs to a set of data units 16. In some embodiments, the one or more conditions 26 include a condition for each of the data units 16 in the set. In some embodiments, the condition includes a time remaining before discard of the data unit 16 in the set is below a time threshold. In other embodiments, the condition includes a value of a discard timer for the data unit 16 in the set is below a time threshold. In yet other embodiments, the condition includes a packet delay budget that remains for the data unit 16 in the set is below a time threshold. In some embodiments, the configuration indicates the time threshold. In some embodiments, the one or more conditions 26 include a condition. In some embodiments, the condition includes the data unit 16 has been previously transmitted at least a threshold number of times. In other embodiments, the condition includes the data unit 16 has been previously transmitted at least a threshold number of times, excluding times that the data unit 16 has been re-transmitted without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, configuration indicates the threshold number of times. In some embodiments, the method further comprises detecting that one or more of the one or more conditions 26 are fulfilled. In some embodiments, the method further comprises, based on said detecting, autonomously performing retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In someembodiments, the method further comprises, based on said detecting, transmitting a report 30 indicating that one or more of the one or more conditions 26 are fulfilled. In some embodiments, the method further comprises, after transmitting the report 30, receiving signaling 24 that configures the communication node 12A to perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received.

[0217] In some embodiments, the signaling 24 includes a configuration of whether the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received.

[0218] In some embodiments, the signaling 24 includes a configuration for triggering or performing retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received.

[0219] In some embodiments, the signaling 24 includes a configuration of one or more termination conditions under which the communication node 12A is to, or is allowed to, terminate a pending retransmission 20 of a data unit 16 that was triggered without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the one or more termination conditions include a condition that the pending retransmission 20 has been pending for at least a threshold duration of time. In some embodiments, the one or more termination conditions include a condition that a timer expires. In some embodiments, the timer is to be started when the pending retransmission 20 is triggered and is to be stopped when the pending retransmission 20 is performed. In some embodiments, the timer is set to be expired by setting a value of the timer to zero if an earliest time for performing the pending retransmission 20 is later than a time at which the timer is set to expire. In some embodiments, the one or more termination conditions include a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit 16. In some embodiments, the one or more termination conditions include a condition that a packet delay budget discard timer for the data unit 16 expires. In some embodiments, the one or more termination conditions include a condition that radio link failure is detected for a radio link over which the data unit 16 is to be retransmitted. In some embodiments, for each of one or more other data units 16, a pending retransmission 20 of the other data unit 16 has been triggered without having received a report 18 of whether a prior transmission 14 of the other data unit 16 was successfully received, and the one or more termination conditions include a condition that the communication device receives a report that at least one of the one or more other data units 16 have been successfully received.In some embodiments, the signaling 24 further includes a command to activate or deactivate the configuration, wherein the command is received after the configuration.

[0220] In some embodiments, the configuration is a radio resource control, RRC, configuration, and the command is conveyed in a medium access control, MAC, control element, CE. In some embodiments, the method further comprises activating or deactivating the configuration according to the command.

[0221] In some embodiments, the signaling 24 governs retransmission 20 of a data unit 16 carrying data from one or more specified logical channels of the communication node 12A. In some embodiments, the signaling 24 indicates one or more respective identities of the one or more logical channels.

[0222] In some embodiments, the signaling 24 governs retransmission 20 of a data unit 16 carrying data from one or more specified quality of service, QoS, flows of the communication node 12A, wherein the signaling 24 indicates one or more respective identities of the one or more QoS flows.

[0223] In some embodiments, a data unit 16 is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report 18 is an RLC status report.

[0224] In some embodiments, the signaling 24 is received at an RLC entity of the communication node 12A.

[0225] In some embodiments, the communication node 12A is a communication device. In some embodiments, the retransmission 20 is an uplink retransmission from the communication device to a communication network 10 or a sidelink retransmission from the communication device to another communication device.

[0226] In some embodiments, the communication node 12A is a network node.

[0227] In some embodiments, the signaling 24 is received from a network node 22.

[0228] In some embodiments, the retransmission 20 is an autonomous retransmission. In some embodiments, the method further comprises detecting fulfilment of one or more of the one or more termination conditions, and based on said detecting, terminating a pending retransmission 20 of a data unit 16.

[0229] In some embodiments, the method further comprises, based on the received signaling 24, handling retransmission 20 of a data unit 16 by the communication node 12A without the communication node 12A having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 710).

[0230] Figure 8 depicts a method performed by a communication node 12A in accordance with other particular embodiments. The method includes receiving signaling 24 that includes a configuration that configures the communication node 12A to report fulfillment of one or more conditions 26 for the communication node 12A to trigger or perform retransmission 20of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 800).

[0231] In some embodiments, the configuration configures the communication node 12A to transmit a report 30 when any of the one or more conditions 26 are fulfilled. In other embodiments, the configuration configures the communication node 12A to transmit a report 30 when all of the one or more conditions 26 are fulfilled.

[0232] In some embodiments, the one or more conditions 26 are the one or more conditions 26 of any of embodiments A4-A21

[0233] In some embodiments, the method further comprises detecting fulfilment of one or more of the one or more conditions 26 (Block 810). In some embodiments, the method further comprises reporting the detected fulfilment according to the received signaling 24 (Block 820).

[0234] Figure 9 depicts a method performed by a communication node 12A in accordance with other particular embodiments. The method includes receiving signaling 24 that includes a configuration of one or more termination conditions under which the communication node 12A is to, or is allowed to, terminate a pending retransmission 20 of a data unit 16 that was triggered without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 900).

[0235] In some embodiments, the method further comprises detecting fulfilment of one or more of the one or more termination conditions (Block 910). In some embodiments, the method further comprises, based on said detecting, terminating a pending retransmission 20 of a data unit 16 (Block 920).

[0236] Figure 10 depicts a method performed by a communication node 12A in accordance with other particular embodiments. The method includes receiving signaling 24 that governs which data units 16 the communication node 12A is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted (Block 1000).

[0237] In some embodiments, the signaling 24 indicates that the communication node 12A is not allowed to multiplex into the same transmission unit a data unit 16 that meets a condition, and a data unit 16 that does not meet the condition. In some embodiments, the condition is that a time remaining before discard of the data unit 16 is below a time threshold. In other embodiments, the condition is that a value of a discard timer for the data unit 16 is below a time threshold. In yet other embodiments, the condition is that a packet delay budget that remains for the data unit 16 is below a time threshold. In some embodiments, the signaling 24 indicates the condition and / or one or more values associated with the condition. In some embodiments, the condition is that the communication device is configured to, or is allowed to, trigger or perform retransmission 20 of the data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16was successfully received. In some embodiments, the condition is that the data unit 16 is from one of one or more specified logical channels for which the communication node 12A is configured to trigger or perform autonomous retransmission 20.

[0238] In some embodiments, a data unit 16 is a MAC PDU or an RLC PDU.

[0239] In some embodiments, a transmission unit is a transport block.

[0240] In some embodiments, the method further comprises handling multiplexing of data units 16 according to the received signaling 24 (Block 1010).

[0241] Figure 11 depicts a method in accordance with other particular embodiments. The method includes transmitting, to a communication node 12A, signaling 24 that governs retransmission 20 of a data unit 16 by the communication node 12A without the communication node 12A having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 1100).

[0242] In some embodiments, the signaling 24 includes a configuration of one or more conditions 26 under which the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received if any of the one or more conditions 26 are fulfilled. In other embodiments, the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received if all of the one or more conditions 26 are fulfilled. In some embodiments, the one or more conditions 26 include a condition that a result of a signal measurement performed by the communication node 12A be above or below a signal measurement threshold. In some embodiments, the configuration indicates the signal measurement threshold. In some embodiments, the one or more conditions 26 include a condition that the data unit 16, or a transmission unit containing the data unit 16, has a size that is smaller than a size threshold. In some embodiments, the configuration indicates the size threshold. In some embodiments, the condition is that a transmission unit containing the data unit 16 has a size that is smaller than the size threshold. In some embodiments, the transmission unit is a transport block. In some embodiments, the one or more conditions 26 include a condition that the data unit 16 is segmented into a number of segments that is more or less than a segmentation number threshold. In some embodiments, the configuration indicates the segmentation number threshold. In some embodiments, the data unit 16 belongs to a set of data units 16, wherein the one or more conditions 26 include a condition that at least a threshold number or percentage of data units 16 in the set have been transmitted. In some embodiments, theconfiguration indicates the threshold number or percentage. In some embodiments, the data unit 16 belongs to a set of data units 16, wherein the one or more conditions 26 include a condition that at least a threshold number or percentage of data units 16 in the set have been transmitted and successfully received. In some embodiments, the configuration indicates the threshold number or percentage. In some embodiments, the set of data units 16 is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer. In some embodiments, the one or more conditions 26 include a condition. In some embodiments, the condition includes a time remaining before discard of the data unit 16 is below a time threshold. In other embodiments, the condition includes a value of a discard timer for the data unit 16 is below a time threshold. In yet other embodiments, the condition includes a packet delay budget that remains for the data unit 16 is below a time threshold. In some embodiments, the data unit 16 belongs to a set of data units 16. In some embodiments, the one or more conditions 26 include a condition that a time remaining before discard of any data unit 16 in the set is below a time threshold. In other embodiments, the one or more conditions 26 include a condition that a value of a discard timer for any data unit 16 in the set is below a time threshold. In yet other embodiments, the one or more conditions 26 include a condition that a packet delay budget that remains for any data unit 16 in the set is below a time threshold. In some embodiments, the data unit 16 belongs to a set of data units 16. In some embodiments, the one or more conditions 26 include a condition for each of the data units 16 in the set. In some embodiments, the condition includes a time remaining before discard of the data unit 16 in the set is below a time threshold. In other embodiments, the condition includes a value of a discard timer for the data unit 16 in the set is below a time threshold. In yet other embodiments, the condition includes a packet delay budget that remains for the data unit 16 in the set is below a time threshold. In some embodiments, the configuration indicates the time threshold. In some embodiments, the one or more conditions 26 include a condition that the data unit 16 has been previously transmitted at least a threshold number of times. In other embodiments, the one or more conditions 26 include a condition that the data unit 16 has been previously transmitted at least a threshold number of times, excluding times that the data unit 16 has been re-transmitted without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the configuration indicates the threshold number of times.

[0243] In some embodiments, the signaling 24 includes a configuration of whether the communication node 12A is to, or is allowed to, trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received.In some embodiments, the signaling 24 includes a configuration for triggering or performing retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received.

[0244] In some embodiments, the signaling 24 includes a configuration of one or more termination conditions under which the communication node 12A is to, or is allowed to, terminate a pending retransmission 20 of a data unit 16 that was triggered without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the one or more termination conditions include a condition that the pending retransmission 20 has been pending for at least a threshold duration of time. In some embodiments, the one or more termination conditions include a condition that a timer expires. In some embodiments, the timer is to be started when the pending retransmission 20 is triggered and is to be stopped when the pending retransmission 20 is performed. In some embodiments, the timer is set to be expired by setting a value of the timer to zero if an earliest time for performing the pending retransmission 20 is later than a time at which the timer is set to expire. In some embodiments, the one or more termination conditions include a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit 16. In some embodiments, the one or more termination conditions include a condition that a packet delay budget discard timer for the data unit 16 expires. In some embodiments, the one or more termination conditions include a condition that radio link failure is detected for a radio link over which the data unit 16 is to be retransmitted. In some embodiments, for each of one or more other data units 16, a pending retransmission 20 of the other data unit 16 has been triggered without having received a report 18 of whether a prior transmission 14 of the other data unit 16 was successfully received, and the one or more termination conditions include a condition that the communication device receives a report 18 that at least one of the one or more other data units 16 have been successfully received. In some embodiments, the signaling 24 further includes a command to activate or deactivate the configuration. In some embodiments, the command is received after the configuration. In some embodiments, the configuration is a radio resource control, RRC, configuration, and the command is conveyed in a medium access control, MAC, control element, CE.

[0245] In some embodiments, the signaling 24 governs retransmission 20 of a data unit 16 carrying data from one or more specified logical channels of the communication node 12A. In some embodiments, the signaling 24 indicates one or more respective identities of the one or more logical channels.

[0246] In some embodiments, the signaling 24 governs retransmission 20 of a data unit 16 carrying data from one or more specified quality of service, QoS, flows of the communicationnode 12A, wherein the signaling 24 indicates one or more respective identities of the one or more QoS flows.

[0247] In some embodiments, a data unit 16 is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report 18 is an RLC status report.

[0248] In some embodiments, the signaling 24 is transmitted to an RLC entity of the communication node 12A.

[0249] In some embodiments, the communication node 12A is a communication device. In some embodiments, the retransmission 20 is an uplink retransmission from the communication device to a communication network or a sidelink retransmission from the communication device to another communication device.

[0250] In some embodiments, the communication node 12A is a network node.

[0251] In some embodiments, the method is performed by a network node 22.

[0252] In some embodiments, the retransmission 20 is an autonomous retransmission. Figure 12 depicts a method in accordance with other particular embodiments. The method includes transmitting signaling 24 that includes a configuration that configures a communication node 12A to report fulfillment of one or more conditions 26 for the communication node 12A to trigger or perform retransmission 20 of a data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 1200).

[0253] In some embodiments, the configuration configures the communication node 12A to transmit a report 30 when any of the one or more conditions 26 are fulfilled. In other embodiments, the configuration configures the communication node 12A to transmit a report 30 when all of the one or more conditions 26 are fulfilled.

[0254] Figure 13 depicts a method in accordance with other particular embodiments. The method includes transmitting signaling 24 that includes a configuration of one or more termination conditions under which a communication node 12A is to, or is allowed to, terminate a pending retransmission 20 of a data unit 16 that was triggered without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received (Block 1300).

[0255] Figure 14 depicts a method in accordance with other particular embodiments. The method includes transmitting signaling 24 that governs which data units 16 a communication node 12A is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted (Block 1400).

[0256] In some embodiments, the signaling 24 indicates that the communication node 12A is not allowed to multiplex into the same transmission unit a data unit 16 that meets a condition. In other embodiments, the signaling 24 indicates that the communication node 12A is not allowed to multiplex into the same transmission unit a data unit 16 that does notmeet the condition. In some embodiments, the condition is that a time remaining before discard of the data unit 16 is below a time threshold. In other embodiments, the condition is that a value of a discard timer for the data unit 16 is below a time threshold. In yet other embodiments, the condition is that a packet delay budget that remains for the data unit 16 is below a time threshold. In some embodiments, the signaling 24 indicates the condition and / or one or more values associated with the condition. In some embodiments, the condition is that the communication device is configured to, or is allowed to, trigger or perform retransmission 20 of the data unit 16 without having received a report 18 of whether a prior transmission 14 of the data unit 16 was successfully received. In some embodiments, the condition is that the data unit 16 is from one of one or more specified logical channels for which the communication node 12A is configured to trigger or perform autonomous retransmission 20.

[0257] Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication node 12A, 12B configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B.

[0258] Embodiments also include a communication node 12A, 12B comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. The power supply circuitry is configured to supply power to the communication node 12A, 12B.

[0259] Embodiments further include a communication node 12A, 12B comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. In some embodiments, the communication node 12A, 12B further comprises communication circuitry.

[0260] Embodiments further include a communication node 12A, 12B comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication node 12A, 12B is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B.

[0261] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio frontend circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to outputinformation from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[0262] Embodiments herein also include a network node 22 configured to perform any of the steps of any of the embodiments described above for the network node 22.

[0263] Embodiments also include a network node 22 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 22. The power supply circuitry is configured to supply power to the network node 22.

[0264] Embodiments further include a network node 22 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 22. In some embodiments, the network node 22 further comprises communication circuitry.

[0265] Embodiments further include a network node 22 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 22 is configured to perform any of the steps of any of the embodiments described above for the network node 22.

[0266] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry 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, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include 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 several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0267] Figure 15 for example illustrates a communication node 12A, 12B as implemented in accordance with one or more embodiments. As shown, the communication node 12A, 12B includes processing circuitry 1510 and communication circuitry 1520. The communication circuitry 1520 (e.g., radio circuitry) is configured to transmit and / or receive information toand / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication node 12A, 12B. The processing circuitry 1510 is configured to perform processing described above, e.g., in any one or more of Figures 7-14, such as by executing instructions stored in memory 1530. The processing circuitry 1510 in this regard may implement certain functional means, units, or modules.

[0268] Figure 16 illustrates a network node 22 as implemented in accordance with one or more embodiments. As shown, the network node 22 includes processing circuitry 1610 and communication circuitry 1620. The communication circuitry 1620 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1610 is configured to perform processing described above, e.g., in Figure 11-14, such as by executing instructions stored in memory 1630. The processing circuitry 1610 in this regard may implement certain functional means, units, or modules.

[0269] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0270] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0271] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0272] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0273] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0274] Figure 17 shows an example of a communication system 1700 in accordance with some embodiments.

[0275] In the example, the communication system 1700 includes a telecommunications network 1702 that includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more core network nodes 1708. The access network 1704 includes one or more access network nodes or base stations of various types,access network nodes 1710A and 171 OB are depicted (which may be collectively referred to as network nodes 1710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1704 may include more than one access network technology. The network nodes 1710 of access network 1704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 1712A, 1712B, 1712C, and 1712D (one or more of which may be generally referred to as UEs 1712) to the core network 1706 over one or more wireless connections.

[0276] Moreover, 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 telecommunications network 1702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1702 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 1702, including one or more access network nodes 1710 and / or core network nodes 1708.

[0277] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-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). An ORAN 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 network 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 O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0278] The network nodes 1710 facilitate direct or indirect connection of one or more UEs 1712 to the core network 1706 over one or more wireless connections. 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 ofsignals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1700 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 1700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0279] The UEs 1712 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 1710 and other communication devices. Similarly, the network nodes 1708, 1710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1702) with the UEs 1712 and / or with other network nodes or equipment in the telecommunications network 1702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1702. More specifically, UEs 1712 may send messages, data, and / or other signals to network nodes 1708, 1710 or other elements of the telecommunications network 1702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1708, 1710 may send messages, data, and other signals to UEs 17122, other network nodes 1708, 1710, and other devices in telecommunications network 1702 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1712 by transmitting the message to an access network node 1710 that will then transmit the message to the intended UE 1712. Similarly, a core network node 108 may receive a particular message from a UE 1712 by receiving the message from an access network node 1710 that itself received the message from the UE 1712.

[0280] In the depicted example, the core network 1706 connects elements of the access network 1704 (e.g., one or more of the network nodes 1710) to one or more host computing systems, such as host 1716. 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 1706 includes one or more core network nodes (e.g., core network node 1708) of various types, one or more of which may be generally referred to as network nodes 1708. Network nodes 1708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptionsthereof are generally applicable to the corresponding components of the core network node 1708. Example core network nodes provide 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 (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0281] The host 1716 may be under the ownership or control of a service provider other than an operator or provider of the access network 1704 and / or the telecommunications network 1702. The host 1716 may be operated by the service provider or on behalf of the service provider. The host 1716 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.

[0282] As a whole, the communication system 1700 of Figure 17 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1700 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1700 supporting different standards, protocols, or rule sets.

[0283] As one example, in certain embodiments, access network 1704 may contain some access network nodes 1710 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1710 support (or the same access network nodes 1710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, asa result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0284] Telecommunications network 1702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1702. For example, the telecommunications network 1702 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.

[0285] In some examples, one or more of the UEs 1712 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 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1704. 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).

[0286] In the example, the hub 1714 communicates with the access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712C and / or 1712D) and network nodes (e.g., network node 1710B). In some examples, the hub 1714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1714 may be a broadband router enabling access to the core network 1706 for the UEs. As another example, the hub 1714 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 1710, or by executable code, script, process, or other instructions in the hub 1714.

[0287] As another example, the hub 1714 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 1714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.The hub 1714 may have a constant / persistent or intermittent connection to the network node 171 OB. The hub 1714 may also allow for a different communication scheme and / or schedule between the hub 1714 and UEs (e.g., UE 1712C and / or 1712D), and between the hub 1714 and the core network 1706. In other examples, the hub 1714 is connected to the core network 1706 and / or one or more UEs via a wired connection.

[0288] Moreover, the hub 1714 may be configured to connect to an M2M service provider over the access network 1704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1710 while still connected via the hub 1714 via a wired or wireless connection. In some embodiments, the hub 1714 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 171 OB. In other embodiments, the hub 1714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0289] Figure 18 is another example of a communication system 1800 according to some embodiments. As used herein, the communication system 1800 includes multiple access points (APs) 1810 (with four exemplary APs 1810A, 1810B, 1810C, and 1810D being depicted) and multiple wireless devices, referred to in the context of communication system 1800 as stations (STAs) 1812 (referred to individually as STA 1812A, STA 1812B, STA 1812C, STA 1812D, and STA 1812E). STA 1812A is served by AP 1810A in a first basic service set (BSS) 1820A. STA 1810B and STA 1810C are served by AP 1810B in a second BSS, BSS 1820B. STA 1812D is served by AP 1810C in a third BSS, BSS 1820C. STA 1812E is served by AP 1810D in a fourth BSS, BSS 1820D. Stations 1812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0290] Each of STAs 1812 may connect through a radio link to one of APs 1810. For example, depending on location or channel conditions experienced by a given STA 1812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.Each AP 1810 may provide data connectivity to STAs 1812 connected to a particular AP 1810. As illustrated, APs 1810 may be connected to a data network 1830. In this way, APs 1810 may also provide data connectivity between STAs 1812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1812 and its serving AP 1810 may be used for providing various kinds of services to STA 1812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1812 and / or on a device linked to STA 1812. By way of example, Figure 18 illustrates an application service platform 1832 provided in data network 1830. The application(s) executed on STA 1812 and / or on one or more other devices linked to STA 1812 may use the radio link for data communication with one or more other STA 1812 and / or the application service platform 1832, thereby enabling utilization of the corresponding service(s) at STA 1812.

[0291] Figure 19 shows a wireless device 1900, which may be configured to operate in communication system 1700 of Figure 17 or in communication system 1800 of Figure 180. The wireless device 1900 may be alternatively referred to as a UE 1900, like a UE 1712 within the context of communication system 1700, or as a station (STA) 1900 or as a non-access-point station (non-AP STA) 1900, like a STA 1812 within the context of the communication system 1800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, and wireless terminal. Other examples include any type of 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.

[0292] A wireless device 1900 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, wireless device 1900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1900 may represent a device that is intended for sale to, oroperation 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, wireless device 1900 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).

[0293] In particular embodiments, wireless device 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input / output interface 1906, a power source 1908, a memory 1910, a communication interface 1912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1900 may include all or a subset of the components shown in Figure 19. The level of integration between the components may vary from one embodiment of wireless device 1900 to another. In general, in a particular embodiment of wireless device 1900, processing circuitry 1902, input / output interface 1906, power source 1908, memory 1910, and communication interface 1912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1900. Further, certain embodiments of wireless devices 1900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0294] The processing circuitry 1902 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 1910. The processing circuitry 1902 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 1902 may include multiple central processing units (CPUs).

[0295] In the example, the input / output interface 1906 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 wireless device 1900. Examples of an input device include a touch-sensitive or presencesensitive 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, anaccelerometer, 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.

[0296] In some embodiments, the power source 1908 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 to supply power to circuitry or to charge an associated battery. The power source 1908 may further include power circuitry for delivering power from the power source 1908 itself, and / or an external power source, to the various parts of wireless device 1900 via input circuitry or an interface such as an electrical power cable. Power source 1908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1900 to which power is supplied.

[0297] The memory 1910 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 1910 includes one or more programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by wireless device 1900, any of a variety of various operating systems or combinations of operating systems.

[0298] The memory 1910 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 UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1910 may allow wireless device 1900 to access instructions, 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 1910, which may be or comprise a device-readable storage medium.The processing circuitry 1902 may be configured to communicate with an access network or other network via or using the communication interface 1912. The communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922. The communication interface 1912 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 1918 and / or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., antenna 1922) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0299] In the illustrated embodiment, communication functions of the communication interface 1912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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.

[0300] In particular embodiments, wireless device 1900 may provide an output of data captured via a sensor, through its communication interface 1912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1900 can be communicated through a wireless connection to a network node via another wireless device 1900. In particular embodiments, such 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).

[0301] As another example, wireless device 1900 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, wireless device 1900may 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.

[0302] Wireless device 1900, 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, 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 smartwatch, a fitness tracker, 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. In particular embodiments, wireless device 1900 represents an loT device that 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 example embodiment of wireless device 1900 shown in Figure 19.

[0303] As yet another specific example, in an loT scenario, wireless device 1900 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 wireless device and / or a network node. Wireless device 1900 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, wireless device 1900 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 1900 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.

[0304] In practice, any number of wireless devices 1900 may be used together with respect to a single use case. For example, a first wireless device 1900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1900 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 wireless device 1900 can also include more than one of the functionalities described above. For example, wireless device 1900 might comprise thesensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0305] Figure 20 shows a network node 2000 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 telecommunications network. In accordance with respective embodiments, network node 2000 may be configured to operate in communication system 1700 of Figure 17, like network nodes 1708 or 1710, or in communication system 1800 of Figure 18, like an AP 1810 or a station 1812. 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., 0-Rll, 0-Dll, O-CU).

[0306] Network nodes 2000 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. Network node 2000 may be a relay node or a relay donor node controlling a relay. Network nodes 2000 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).

[0307] Other examples of network nodes 2000 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).

[0308] In particular embodiments, network node 2000 includes a processing circuitry 2002, a memory 2004, a communication interface 2006, and a power source 2008. In general, in a particular embodiment of network node 2000, processing circuitry 2002, memory 2004, communication interface 2006, and power source 2008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 2000.The network node 2000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 2000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 2000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 2004 or portions of memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 2000.

[0309] The processing circuitry 2002 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 components, such as the memory 2004, to provide network node 2000 functionality.

[0310] In some embodiments, the processing circuitry 2002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of radio frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 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 2012 and baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units.

[0311] The memory 2004 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 thatmay be used by the processing circuitry 2002. The memory 2004 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 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and / or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and memory 2004 is integrated.

[0312] The communication interface 2006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 2006 comprises port(s) / terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1900 may be capable of wireless communication and communication interface 2006 may also include radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, an antenna 2010. Particular embodiments of radio front-end circuitry 2018 include filter(s) 2020 and amplifier(s) 2022. The radio front-end circuitry 2018 may be connected to an antenna 2010 and processing circuitry 2002. The radio front-end circuitry may be configured to condition signals communicated between antenna 2010 and processing circuitry 2002. The radio front-end circuitry 2018 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 2018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 2020 and / or amplifiers 2022. The radio signal(s) may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0313] In certain alternative embodiments, network node 2000 may be capable of wireless communication but does not include separate radio front-end circuitry 2018, instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes one or more ports or terminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012, as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown).The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through one or more interfaces or ports.

[0314] The antenna 2010, communication interface 2006, and / or the processing circuitry 2002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 2000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 2010, the communication interface 2006, and / or the processing circuitry 2002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 2000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0315] The power source 2008 provides power to the various components of network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 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 2008. As a further example, the power source 2008 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.

[0316] Embodiments of the network node 2000 may include additional components beyond those shown in Figure 20 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 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2000.

[0317] Figure 21 is a block diagram illustrating a virtualization environment 2100 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 includevirtualizing 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 2100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a 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 2100 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.

[0318] Applications 2102 (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.

[0319] Hardware 2104 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 2106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 2108A and VM 2108B (which may be collectively referred to as VMs 2108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 2106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 2108.

[0320] The VMs 2108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 2106. Different embodiments of the instance of a virtual appliance 2102 may be implemented on one or more of VMs 2108, 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.

[0321] In the context of NFV, each of the VMs 2108 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 2108, and that part of hardware 2104 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 of the VMs 2108 on top of the hardware 2104 and corresponds to an application 2102.

[0322] Hardware 2104 may be implemented in a standalone network node with generic or specific components. Hardware 2104 may implement some functions via virtualization. Alternatively, hardware 2104 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 2110, which, among others, oversees lifecycle management of applications 2102. In some embodiments, hardware 2104 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 2112 which may alternatively be used for communication between hardware nodes and radio units.

[0323] 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.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.

[0324] Some embodiments herein may be enumerated as follows:

[0325] Group A Embodiments

[0326] A1. A method performed by a communication node, the method comprising:

[0327] receiving signaling that governs retransmission of a data unit by the communication node without the communication node having received a report of whether a prior transmission of the data unit was successfully received.

[0328] A2. The method of embodiment A1 , wherein the signaling includes a configuration of one or more conditions under which the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0329] A3. The method of embodiment A2, wherein the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received if:

[0330] any of the one or more conditions are fulfilled; or

[0331] all of the one or more conditions are fulfilled.

[0332] A4. The method of any of embodiments A2-A3, wherein the one or more conditions include a condition that a result of a signal measurement performed by the communication node be above or below a signal measurement threshold.

[0333] A5. The method of embodiment A4, wherein the configuration indicates the signal measurement threshold.A6. The method of any of embodiments A2-A5, wherein the one or more conditions include a condition that the data unit, or a transmission unit containing the data unit, has a size that is smaller than a size threshold.

[0334] A7. The method of embodiment A6, wherein the configuration indicates the size threshold.

[0335] A8. The method of any of embodiments A6-A7, wherein the condition is that a transmission unit containing the data unit has a size that is smaller than the size threshold, wherein the transmission unit is a transport block.

[0336] A9. The method of any of embodiments A2-A8, wherein the one or more conditions include a condition that the data unit is segmented into a number of segments that is more or less than a segmentation number threshold.

[0337] A10. The method of embodiment A9, wherein the configuration indicates the segmentation number threshold.

[0338] A11. The method of any of embodiments A2-A10, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that at least a threshold number or percentage of data units in the set have been transmitted.

[0339] A12. The method of embodiment A11 , wherein the configuration indicates the threshold number or percentage.

[0340] A13. The method of any of embodiments A2-A12, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that at least a threshold number or percentage of data units in the set have been transmitted and successfully received.

[0341] A14. The method of embodiment A13, wherein the configuration indicates the threshold number or percentage.

[0342] A15. The method of any of embodiments A11-A14, wherein the set of data units is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer.

[0343] A16. The method of any of embodiments A2-A15, wherein the one or more conditionsinclude a condition that:

[0344] a time remaining before discard of the data unit is below a time threshold;

[0345] a value of a discard timer for the data unit is below a time threshold; or

[0346] a packet delay budget that remains for the data unit is below a time threshold.

[0347] A17. The method of any of embodiments A2-A16, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that:

[0348] a time remaining before discard of any data unit in the set is below a time threshold; a value of a discard timer for any data unit in the set is below a time threshold; or a packet delay budget that remains for any data unit in the set is below a time threshold.

[0349] A18. The method of any of embodiments A2-A16, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that, for each of the data units in the set:

[0350] a time remaining before discard of the data unit in the set is below a time threshold; a value of a discard timer for the data unit in the set is below a time threshold; or a packet delay budget that remains for the data unit in the set is below a time threshold.

[0351] A19. The method of any of embodiments A16-A18, wherein the configuration indicates the time threshold.

[0352] A20. The method of any of embodiments A2-A19, wherein the one or more conditions include a condition:

[0353] the data unit has been previously transmitted at least a threshold number of times; or the data unit has been previously transmitted at least a threshold number of times, excluding times that the data unit has been re-transmitted without having received a report of whether a prior transmission of the data unit was successfully received.

[0354] A21. The method of embodiment A20, wherein the configuration indicates the threshold number of times.

[0355] A22. The method of any of embodiments A2-A21 , further comprising detecting that one or more of the one or more conditions are fulfilled.A23. The method of embodiment A22, further comprising, based on said detecting, autonomously performing retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0356] A24. The method of embodiment A22, further comprising, based on said detecting, transmitting a report indicating that one or more of the one or more conditions are fulfilled.

[0357] A25. The method of embodiment A24, further comprising, after transmitting the report, receiving signaling that configures or commands the communication node to perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0358] A26. The method of embodiment A1 , wherein the signaling includes a configuration of whether the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0359] A27. The method of any of embodiments A1-A26, wherein the signaling includes a configuration for triggering or performing retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0360] A28. The method of any of embodiments A1-A27, wherein the signaling includes a configuration of one or more termination conditions under which the communication node is to, or is allowed to, terminate a pending retransmission of a data unit that was triggered without having received a report of whether a prior transmission of the data unit was successfully received.

[0361] A29. The method of embodiment A28, wherein the one or more termination conditions include a condition that the pending retransmission has been pending for at least a threshold duration of time.

[0362] A30. The method of any of embodiments A28-A29, wherein the one or more termination conditions include a condition that a timer expires, wherein the timer is to be started when the pending retransmission is triggered and is to be stopped when the pending retransmission is performed.A31. The method of embodiment A30, wherein the timer is set to be expired by setting a value of the timer to zero if an earliest time for performing the pending retransmission is later than a time at which the timer is set to expire.

[0363] A32. The method of any of embodiments A28-A31 , wherein the one or more termination conditions include a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit.

[0364] A33. The method of any of embodiments A28-A32, wherein the one or more termination conditions include a condition that a packet delay budget discard timer for the data unit expires.

[0365] A34. The method of any of embodiments A28-A33, wherein the one or more termination conditions include a condition that radio link failure is detected for a radio link over which the data unit is to be retransmitted.

[0366] A35. The method of any of embodiments A28-A34, wherein, for each of one or more other data units, a pending retransmission of the other data unit has been triggered without having received a report of whether a prior transmission of the other data unit was successfully received, and wherein the one or more termination conditions include a condition that the communication device receives a report that at least one of the one or more other data units have been successfully received.

[0367] A36. The method of any of embodiments A2-A35, wherein the signaling further includes a command to activate or deactivate the configuration, wherein the command is received after the configuration.

[0368] A37. The method of embodiment A36, wherein the configuration is a radio resource control, RRC, configuration, and the command is conveyed in a medium access control, MAC, control element, CE.

[0369] A38. The method of any of embodiments A36-A37, further comprising activating or deactivating the configuration according to the command.

[0370] A39. The method of any of embodiments A1-A38, wherein the signaling governs retransmission of a data unit carrying data from one or more specified logical channels of thecommunication node, wherein the signaling indicates one or more respective identities of the one or more logical channels.

[0371] A40. The method of any of embodiments A1-A39, wherein the signaling governs retransmission of a data unit carrying data from one or more specified quality of service, QoS, flows of the communication node, wherein the signaling indicates one or more respective identities of the one or more QoS flows.

[0372] A41. The method of any of embodiments A1-A40, wherein a data unit is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report is an RLC status report.

[0373] A42. The method of any of embodiments A1-A41 , wherein the signaling is received at an RLC entity of the communication node.

[0374] A43. The method of any of embodiments A1-A42, wherein the communication node is a communication device.

[0375] A44. The method of embodiment A43, wherein the retransmission is an uplink retransmission from the communication device to a communication network or a sidelink retransmission from the communication device to another communication device.

[0376] A45. The method of any of embodiments A1-A42, wherein the communication node is a network node.

[0377] A46. The method of any of embodiments A1-A45, wherein the retransmission is an autonomous retransmission.

[0378] A47. The method of any of embodiments A28-A35, further comprising:

[0379] detecting fulfilment of one or more of the one or more termination conditions; and based on said detecting, terminating a pending retransmission of a data unit.

[0380] A48. The method of any of embodiments A1-A47, further comprising, based on the received signaling, handling retransmission of a data unit by the communication node without the communication node having received a report of whether a prior transmission of the data unit was successfully received.

[0381] AA1. A method performed by a communication node, the method comprising:receiving signaling that includes a configuration that configures the communication node to report fulfillment of one or more conditions for the communication node to trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0382] AA2. The method of embodiment AA1, wherein the configuration configures the communication node to transmit a report when:

[0383] any of the one or more conditions are fulfilled; or

[0384] all of the one or more conditions are fulfilled.

[0385] AA3. The method of any of embodiments AA1-AA2, wherein the one or more conditions are the one or more conditions of any of embodiments A4-A21.

[0386] AA4. The method of any of embodiments AA1-AA3, further comprising:

[0387] detecting fulfilment of one or more of the one or more conditions; and

[0388] reporting the detected fulfilment according to the received signaling.

[0389] AA5. The method of any of embodiments AA1-AA4, further comprising any one or more steps of the method of any of embodiments A1-A47.

[0390] AAA1. A method performed by a communication node, the method comprising:

[0391] receiving signaling that includes a configuration of one or more termination conditions under which the communication node is to, or is allowed to, terminate a pending retransmission of a data unit that was triggered without having received a report of whether a prior transmission of the data unit was successfully received.

[0392] AAA2. The method of embodiment AAA1, wherein the one or more termination conditions comprise the one or more termination conditions according to any of embodiments A29-35.

[0393] AAA3. The method of any of embodiments AAA1-AAA2, further comprising:

[0394] detecting fulfilment of one or more of the one or more termination conditions; and based on said detecting, terminating a pending retransmission of a data unit.

[0395] AAAA1. A method performed by a communication node, the method comprising:

[0396] receiving signaling that governs which data units the communication node is allowed,or is not allowed, to multiplex into the same transmission unit to be transmitted.

[0397] AAAA2. The method of embodiment AAAA1 , wherein the signaling indicates that the communication node is not allowed to multiplex into the same transmission unit:

[0398] a data unit that meets a condition; and

[0399] a data unit that does not meet the condition.

[0400] AAAA3. The method of embodiment AAAA2, wherein the condition is that:

[0401] a time remaining before discard of the data unit is below a time threshold;

[0402] a value of a discard timer for the data unit is below a time threshold; or

[0403] a packet delay budget that remains for the data unit is below a time threshold.

[0404] AAAA4. The method of any of embodiments AAAA2-AAAA3, wherein the signaling indicates the condition and / or one or more values associated with the condition.

[0405] AAAA5. The method of embodiment AAAA2, wherein the condition is that the communication device is configured to, or is allowed to, trigger or perform retransmission of the data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0406] AAAA6. The method of embodiment AAAA2, wherein the condition is that the data unit is from one of one or more specified logical channels for which the communication node is configured to trigger or perform autonomous retransmission.

[0407] AAAA7. The method of any of embodiments AAAA1-AAAA6, wherein a data unit is a MAC PDU or an RLC PDU.

[0408] AAAA8. The method of any of embodiments AAAA1-AAAA7, wherein a transmission unit is a transport block.

[0409] AAAA9. The method of any of embodiments AAAA1-AAAA8, further comprising handling multiplexing of data units according to the received signaling.

[0410] Group B Embodiments

[0411] B1. A method comprising:

[0412] transmitting, to a communication node, signaling that governs retransmission of adata unit by the communication node without the communication node having received a report of whether a prior transmission of the data unit was successfully received.

[0413] B2. The method of embodiment B1 , wherein the signaling includes a configuration of one or more conditions under which the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0414] B3. The method of embodiment B2, wherein the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received if:

[0415] any of the one or more conditions are fulfilled; or

[0416] all of the one or more conditions are fulfilled.

[0417] B4. The method of any of embodiments B2-B3, wherein the one or more conditions include a condition that a result of a signal measurement performed by the communication node be above or below a signal measurement threshold.

[0418] B5. The method of embodiment B4, wherein the configuration indicates the signal measurement threshold.

[0419] B6. The method of any of embodiments B2-B5, wherein the one or more conditions include a condition that the data unit, or a transmission unit containing the data unit, has a size that is smaller than a size threshold.

[0420] B7. The method of embodiment B6, wherein the configuration indicates the size threshold.

[0421] B8. The method of any of embodiments B6-B7, wherein the condition is that a transmission unit containing the data unit has a size that is smaller than the size threshold, wherein the transmission unit is a transport block.

[0422] B9. The method of any of embodiments B2-B8, wherein the one or more conditions include a condition that the data unit is segmented into a number of segments that is more or less than a segmentation number threshold.

[0423] B10. The method of embodiment B9, wherein the configuration indicates the segmentationnumber threshold.

[0424] B11. The method of any of embodiments B2-B10, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that at least a threshold number or percentage of data units in the set have been transmitted.

[0425] B12. The method of embodiment B11, wherein the configuration indicates the threshold number or percentage.

[0426] B13. The method of any of embodiments B2-B12, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that at least a threshold number or percentage of data units in the set have been transmitted and successfully received.

[0427] B14. The method of embodiment B13, wherein the configuration indicates the threshold number or percentage.

[0428] B15. The method of any of embodiments B11-B14, wherein the set of data units is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer.

[0429] B16. The method of any of embodiments B2-B15, wherein the one or more conditions include a condition that:

[0430] a time remaining before discard of the data unit is below a time threshold;

[0431] a value of a discard timer for the data unit is below a time threshold; or

[0432] a packet delay budget that remains for the data unit is below a time threshold.

[0433] B17. The method of any of embodiments B2-B16, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that:

[0434] a time remaining before discard of any data unit in the set is below a time threshold; a value of a discard timer for any data unit in the set is below a time threshold; or a packet delay budget that remains for any data unit in the set is below a time threshold.

[0435] B18. The method of any of embodiments B2-B16, wherein the data unit belongs to a set of data units, wherein the one or more conditions include a condition that, for each of the data units in the set:a time remaining before discard of the data unit in the set is below a time threshold; a value of a discard timer for the data unit in the set is below a time threshold; or a packet delay budget that remains for the data unit in the set is below a time threshold.

[0436] B19. The method of any of embodiments B16-B18, wherein the configuration indicates the time threshold.

[0437] B20. The method of any of embodiments B2-B19, wherein the one or more conditions include a condition:

[0438] the data unit has been previously transmitted at least a threshold number of times; or the data unit has been previously transmitted at least a threshold number of times, excluding times that the data unit has been re-transmitted without having received a report of whether a prior transmission of the data unit was successfully received.

[0439] B21. The method of embodiment B20, wherein the configuration indicates the threshold number of times.

[0440] B22 - B25. Reserved.

[0441] B26. The method of embodiment B1 , wherein the signaling includes a configuration of whether the communication node is to, or is allowed to, trigger or perform retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0442] B27. The method of any of embodiments B1-B26, wherein the signaling includes a configuration for triggering or performing retransmission of a data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0443] B28. The method of any of embodiments B1-B27, wherein the signaling includes a configuration of one or more termination conditions under which the communication node is to, or is allowed to, terminate a pending retransmission of a data unit that was triggered without having received a report of whether a prior transmission of the data unit was successfully received.

[0444] B29. The method of embodiment B28, wherein the one or more termination conditionsinclude a condition that the pending retransmission has been pending for at least a threshold duration of time.

[0445] B30. The method of any of embodiments B28-B29, wherein the one or more termination conditions include a condition that a timer expires, wherein the timer is to be started when the pending retransmission is triggered and is to be stopped when the pending retransmission is performed.

[0446] B31. The method of embodiment B30, wherein the timer is set to be expired by setting a value of the timer to zero if an earliest time for performing the pending retransmission is later than a time at which the timer is set to expire.

[0447] B32. The method of any of embodiments B28-B31 , wherein the one or more termination conditions include a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit.

[0448] B33. The method of any of embodiments B28-B32, wherein the one or more termination conditions include a condition that a packet delay budget discard timer for the data unit expires.

[0449] B34. The method of any of embodiments B28-B33, wherein the one or more termination conditions include a condition that radio link failure is detected for a radio link over which the data unit is to be retransmitted.

[0450] B35. The method of any of embodiments B28-B34, wherein, for each of one or more other data units, a pending retransmission of the other data unit has been triggered without having received a report of whether a prior transmission of the other data unit was successfully received, and wherein the one or more termination conditions include a condition that the communication device receives a report that at least one of the one or more other data units have been successfully received.

[0451] B36. The method of any of embodiments B2-B35, wherein the signaling further includes a command to activate or deactivate the configuration, wherein the command is received after the configuration.

[0452] B37. The method of embodiment B36, wherein the configuration is a radio resource control, RRC, configuration, and the command is conveyed in a medium access control, MAC,control element, CE.

[0453] B38. Reserved.

[0454] B39. The method of any of embodiments B1-B38, wherein the signaling governs retransmission of a data unit carrying data from one or more specified logical channels of the communication node, wherein the signaling indicates one or more respective identities of the one or more logical channels.

[0455] B40. The method of any of embodiments B1-B39, wherein the signaling governs retransmission of a data unit carrying data from one or more specified quality of service, QoS, flows of the communication node, wherein the signaling indicates one or more respective identities of the one or more QoS flows.

[0456] B41. The method of any of embodiments B1-B40, wherein a data unit is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report is an RLC status report.

[0457] B42. The method of any of embodiments B1-B41 , wherein the signaling is transmitted to an RLC entity of the communication node.

[0458] B43. The method of any of embodiments B1-B42, wherein the communication node is a communication device.

[0459] B44. The method of embodiment B43, wherein the retransmission is an uplink retransmission from the communication device to a communication network or a sidelink retransmission from the communication device to another communication device.

[0460] B45. The method of any of embodiments B1-B42, wherein the communication node is a network node.

[0461] B46. The method of any of embodiments B1-B45, wherein the retransmission is an autonomous retransmission.

[0462] BB1. A method comprising:

[0463] transmitting signaling that includes a configuration that configures a communication node to report fulfillment of one or more conditions for the communication node to trigger or perform retransmission of a data unit without havingreceived a report of whether a prior transmission of the data unit was successfully received.

[0464] BB2. The method of embodiment BB1, wherein the configuration configures the communication node to transmit a report when:

[0465] any of the one or more conditions are fulfilled; or

[0466] all of the one or more conditions are fulfilled.

[0467] BB3. The method of any of embodiments BB1-BB2, wherein the one or more conditions are the one or more conditions of any of embodiments B4-B21.

[0468] BB4. The method of any of embodiments BB1-BB4, further comprising any one or more steps of the method of any of embodiments B1-B47.

[0469] BBB1. A method comprising:

[0470] transmitting signaling that includes a configuration of one or more termination conditions under which a communication node is to, or is allowed to, terminate a pending retransmission of a data unit that was triggered without having received a report of whether a prior transmission of the data unit was successfully received.

[0471] BBB2. The method of embodiment BBB1, wherein the one or more termination conditions comprise the one or more termination conditions according to any of embodiments B29-B5.

[0472] BBBB1. A method comprising:

[0473] transmitting signaling that governs which data units a communication node is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted.

[0474] BBBB2. The method of embodiment BBBB1 , wherein the signaling indicates that the communication node is not allowed to multiplex into the same transmission unit:

[0475] a data unit that meets a condition; and

[0476] a data unit that does not meet the condition.

[0477] BBBB3. The method of embodiment BBBB2, wherein the condition is that:

[0478] a time remaining before discard of the data unit is below a time threshold;

[0479] a value of a discard timer for the data unit is below a time threshold; ora packet delay budget that remains for the data unit is below a time threshold.

[0480] BBBB4. The method of any of embodiments BBBB2-BBBB3, wherein the signaling indicates the condition and / or one or more values associated with the condition.

[0481] BBBB. The method of embodiment BBBB2, wherein the condition is that the communication device is configured to, or is allowed to, trigger or perform retransmission of the data unit without having received a report of whether a prior transmission of the data unit was successfully received.

[0482] BBBB6. The method of embodiment BBBB2, wherein the condition is that the data unit is from one of one or more specified logical channels for which the communication node is configured to trigger or perform autonomous retransmission.

[0483] BBBB7. The method of any of embodiments BBBB1-BBBB6, wherein a data unit is a MAC PDU or an RLC PDU.

[0484] BBBB8. The method of any of embodiments BBBB1-BBBB7, wherein a transmission unit is a transport block.

[0485] Group C Embodiments

[0486] C1. A communication node configured to perform any of the steps of any of the Group A or Group B embodiments.

[0487] C2. A communication node comprising processing circuitry configured to any of the steps of any of the Group A or Group B embodiments.

[0488] C3. A communication node comprising:

[0489] communication circuitry; and

[0490] processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments.

[0491] C4. A communication node comprising:

[0492] processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments; and

[0493] power supply circuitry configured to supply power to the communication node.C5. A communication node comprising:

[0494] processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication node is configured to perform any of the steps of any of the Group A or Group B embodiments.

[0495] 06. The communication node of any of embodiments 01 -05, wherein the communication node is a communication device.

[0496] 07. A user equipment (UE) comprising:

[0497] an antenna configured to send and receive wireless signals;

[0498] radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

[0499] the processing circuitry being configured to perform any of the steps of any of the Group A or Group B embodiments;

[0500] an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

[0501] a battery connected to the processing circuitry and configured to supply power to the UE.

[0502] 08. A computer program comprising instructions which, when executed by at least one processor of a communication node, causes the communication node to perform any of the steps of any of the Group A or Group B embodiments.

[0503] 09. A carrier containing the computer program of embodiment 08, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0504] REFERENCES

[0505] 1. 3GPP TR 23.700-60, V18.0.0 (2022-12)

[0506] 2. 3GPP TS 38.322, V18.0.0 (2023-12)

Claims

CLAIMS1. A method performed by a communication node (12A), the method comprising:receiving (700) signaling (24) that governs retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; andbased on the received signaling (24), handling (710) retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

2. The method of claim 1 , wherein the signaling (24) includes a configuration of one or more conditions (26) under which the communication node (12A) is to, or is allowed to, trigger or perform retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

3. The method of claim 2, wherein the one or more conditions (26) include a condition (26) that a result of a signal measurement performed by the communication node (12A) be above or below a signal measurement threshold.

4. The method of any of claims 2-3, wherein the one or more conditions (26) include one or more of:a condition (26) that the data unit (16), or a transmission unit containing the data unit (16), has a size that is smaller than a size threshold; ora condition (26) that the data unit (16) is segmented into a number of segments that is more or less than a segmentation number threshold.

5. The method of any of claims 2-4, wherein the one or more conditions (26) include one or more of:a condition (26) that at least a threshold number or percentage of data units (16) in a set of data units (16) to which the data unit (16) belongs have been transmitted; ora condition (26) that at least a threshold number or percentage of data units (16) in a set of data units (16) to which the data unit (16) belongs have been transmitted and successfully received.

666. The method of claim 5, wherein the set of data units (16) is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer.

7. The method of any of claims 2-6, wherein the one or more conditions (26) include one or more of:a condition (26) that (i) a time remaining before discard of the data unit (16) is below a time threshold, (ii) a value of a discard timer for the data unit (16) is below a time threshold, or (iii) a packet delay budget that remains for the data unit (16) is below a time threshold; ora condition (26) that (i) a time remaining before discard of any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold, (ii) a value of a discard timer for any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold, or (iii) a packet delay budget that remains for any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold.

8. The method of any of claims 2-7, wherein the one or more conditions (26) include one or more of:a condition (26) that the data unit (16) has been previously transmitted at least a threshold number of times; ora condition (26) that the data unit (16) has been previously transmitted at least a threshold number of times, excluding times that the data unit (16) has been re-transmitted without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

9. The method of any of claims 2-8, wherein said handling comprises:detecting that one or more of the one or more conditions (26) are fulfilled; and based on said detecting, autonomously performing retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

10. The method of any of claims 2-8, wherein said handling comprises:detecting that one or more of the one or more conditions (26) are fulfilled; based on said detecting, transmitting a report (30) indicating that one or more of the one or more conditions (26) are fulfilled; andafter transmitting the report (30), receiving signaling (24) that configures or67commands the communication node (12A) to perform retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

11. The method of claim 1 , wherein the signaling (24) includes:a configuration of whether the communication node (12A) is to, or is allowed to, trigger or perform retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; and / ora configuration for triggering or performing retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

12. The method of any of claims 1-11, wherein the signaling (24) includes a configuration of one or more termination conditions under which the communication node (12A) is to, or is allowed to, terminate a pending retransmission (20) of a data unit (16) that was triggered without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received, and wherein said handling comprises:detecting fulfilment of one or more of the one or more termination conditions; and based on said detecting, terminating a pending retransmission (20) of a data unit (16).

13. The method of claim 12, wherein the one or more termination conditions include one or more of:a condition that the pending retransmission (20) has been pending for at least a threshold duration of time;a condition that a timer expires, wherein the timer is to be started when the pending retransmission (20) is triggered and is to be stopped when the pending retransmission (20) is performed;a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit (16);a condition that a packet delay budget discard timer for the data unit (16) expires; or a condition that radio link failure is detected for a radio link over which the data unit (16) is to be retransmitted14. The method of claim 13, wherein the one or more termination conditions include the condition that the timer expires, wherein the timer is set to be expired by setting a value of68the timer to zero if an earliest time for performing the pending retransmission (20) is later than a time at which the timer is set to expire.

15. The method of any of claims 12-14, wherein, for each of one or more other data units (16), a pending retransmission (20) of the other data unit (16) has been triggered without having received a report (18) of whether a prior transmission (14) of the other data unit (16) was successfully received, and wherein the one or more termination conditions include a condition that the communication device receives a report that at least one of the one or more other data units (16) have been successfully received.

16. The method of any of claims 2-15, wherein the signaling (24) further includes a command to activate or deactivate the configuration, wherein the command is received after the configuration, and wherein the method further comprises activating or deactivating the configuration according to the command.

17. The method of any of claims 1-16, wherein the signaling (24):governs retransmission (20) of a data unit (16) carrying data from one or more specified logical channels of the communication node (12A), wherein the signaling (24) indicates one or more respective identities of the one or more logical channels; and / orgoverns retransmission (20) of a data unit (16) carrying data from one or more specified quality of service, QoS, flows of the communication node (12A), wherein the signaling (24) indicates one or more respective identities of the one or more QoS flows.

18. The method of any of claims 1-17, wherein a data unit (16) is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report (18) is an RLC status report, and wherein the signaling (24) is received at an RLC entity of the communication node (12A).

19. The method of any of claims 1-18, wherein the communication node (12A) is a communication device, wherein the retransmission (20) is an uplink retransmission from the communication device to a communication network or a sidelink retransmission from the communication device to another communication device.

20. The method of any of claims 1-19, wherein the retransmission (20) is an autonomous retransmission.6921. A method comprising:transmitting (1100), to a communication node (12A), signaling (24) that governs retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

22. The method of claim 21 , wherein the signaling (24) includes a configuration of one or more conditions (26) under which the communication node (12A) is to, or is allowed to, trigger or perform retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

23. The method of claim 22, wherein the one or more conditions (26) include a condition (26) that a result of a signal measurement performed by the communication node (12A) be above or below a signal measurement threshold.

24. The method of any of claims 22-23, wherein the one or more conditions (26) include one or more of:a condition (26) that the data unit (16), or a transmission unit containing the data unit (16), has a size that is smaller than a size threshold; ora condition (26) that the data unit (16) is segmented into a number of segments that is more or less than a segmentation number threshold.

25. The method of any of claims 22-24, wherein the one or more conditions (26) include one or more of:a condition (26) that at least a threshold number or percentage of data units (16) in a set of data units (16) to which the data unit (16) belongs have been transmitted; ora condition (26) that at least a threshold number or percentage of data units (16) in a set of data units (16) to which the data unit (16) belongs have been transmitted and successfully received.

26. The method of claim 25, wherein the set of data units (16) is a set of protocol data units, PDlls, that carries a payload of one unit of information from an application layer.

27. The method of any of claims 22-26, wherein the one or more conditions (26) include one or more of:70a condition (26) that (i) a time remaining before discard of the data unit (16) is below a time threshold, (ii) a value of a discard timer for the data unit (16) is below a time threshold, or (iii) a packet delay budget that remains for the data unit (16) is below a time threshold; ora condition (26) that (i) a time remaining before discard of any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold, (ii) a value of a discard timer for any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold, or (iii) a packet delay budget that remains for any data unit (16) in a set of data units (16) to which the data unit (16) belongs is below a time threshold.

28. The method of any of claims 22-27, wherein the one or more conditions (26) include one or more of:a condition (26) that the data unit (16) has been previously transmitted at least a threshold number of times; ora condition (26) that the data unit (16) has been previously transmitted at least a threshold number of times, excluding times that the data unit (16) has been re-transmitted without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

29. The method of claim 21 , wherein the signaling (24) includes:a configuration of whether the communication node (12A) is to, or is allowed to, trigger or perform retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; and / ora configuration for triggering or performing retransmission (20) of a data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

30. The method of any of claims 21-29, wherein the signaling (24) includes a configuration of one or more termination conditions under which the communication node (12A) is to, or is allowed to, terminate a pending retransmission (20) of a data unit (16) that was triggered without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received, and wherein said handling comprises:detecting fulfilment of one or more of the one or more termination conditions; and based on said detecting, terminating a pending retransmission (20) of a data unit (16).7131. The method of claim 30, wherein the one or more termination conditions include one or more of:a condition that the pending retransmission (20) has been pending for at least a threshold duration of time;a condition that a timer expires, wherein the timer is to be started when the pending retransmission (20) is triggered and is to be stopped when the pending retransmission (20) is performed;a condition that the communication device receives more than a threshold number of negative acknowledgements of the data unit (16);a condition that a packet delay budget discard timer for the data unit (16) expires; or a condition that radio link failure is detected for a radio link over which the data unit (16) is to be retransmitted32. The method of claim 31 , wherein the one or more termination conditions include the condition that the timer expires, wherein the timer is set to be expired by setting a value of the timer to zero if an earliest time for performing the pending retransmission (20) is later than a time at which the timer is set to expire.

33. The method of any of claims 30-32, wherein, for each of one or more other data units (16), a pending retransmission (20) of the other data unit (16) has been triggered without having received a report (18) of whether a prior transmission (14) of the other data unit (16) was successfully received, and wherein the one or more termination conditions include a condition that the communication device receives a report that at least one of the one or more other data units (16) have been successfully received.

34. The method of any of claims 22-33, wherein the signaling (24) further includes a command to activate or deactivate the configuration, wherein the command is received after the configuration, and wherein the method further comprises activating or deactivating the configuration according to the command.

35. The method of any of claims 21-34, wherein the signaling (24):governs retransmission (20) of a data unit (16) carrying data from one or more specified logical channels of the communication node (12A), wherein the signaling (24) indicates one or more respective identities of the one or more logical channels; and / orgoverns retransmission (20) of a data unit (16) carrying data from one or morespecified quality of service, QoS, flows of the communication node (12A), wherein the signaling (24) indicates one or more respective identities of the one or more QoS flows.

36. The method of any of claims 21-35, wherein a data unit (16) is a Radio Link Control, RLC, Protocol Data Unit, PDU, and wherein the report (18) is an RLC status report, and wherein the signaling (24) is received at an RLC entity of the communication node (12A).

37. The method of any of claims 21-36, wherein the communication node (12A) is a communication device, wherein the retransmission (20) is an uplink retransmission from the communication device to a communication network or a sidelink retransmission from the communication device to another communication device.

38. The method of any of claims 21-37, wherein the retransmission (20) is an autonomous retransmission.

39. A communication node (12A) configured to:receive signaling (24) that governs retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; andbased on the received signaling (24), handle retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

40. The communication node (12A) of claim 39, configured to perform the method of any of claims 2-20.

41. A node configured to:transmit, to a communication node (12A), signaling (24) that governs retransmission (20) of a data unit (16) by the communication node (12A) without the communication node (12A) having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received.

42. The node of claim 41 , configured to perform the method of any of claims 21-38.

43. A computer program comprising instructions which, when executed by at least one processor of a communication node (12A), causes the communication node (12A) to perform the method of any of claims 1-20.

44. A computer program comprising instructions which, when executed by at least one processor of a node, causes the node to perform the method of any of claims 21-38.

45. A carrier containing the computer program of any of claims 43-44, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

46. A method performed by a communication node (12A), the method comprising:receiving (1000) signaling (24) that governs which data units (16) the communication node (12A) is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted; andhandling (1010) multiplexing of data units (16) according to the received signaling (24).

47. The method of claim 46, wherein the signaling (24) indicates that the communication node (12A) is not allowed to multiplex into the same transmission unit:a data unit (16) that meets a condition; anda data unit (16) that does not meet the condition.

48. The method of claim 47, wherein the condition is that:a time remaining before discard of the data unit (16) is below a time threshold; a value of a discard timer for the data unit (16) is below a time threshold;a packet delay budget that remains for the data unit (16) is below a time threshold; the communication device is configured to, or is allowed to, trigger or perform retransmission (20) of the data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; orthe data unit (16) is from one of one or more specified logical channels for which the communication node (12A) is configured to trigger or perform autonomous retransmission (20).

49. The method of any of claims 46-48, wherein a data unit (16) is a MAC PDU or an RLC PDU, and wherein a transmission unit is a transport block.7450. A method performed by a node, the method comprising:transmitting (1400) signaling (24) that governs which data units (16) a communication node (12A) is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted.

51. The method of claim 50, wherein the signaling (24) indicates that the communication node (12A) is not allowed to multiplex into the same transmission unit:a data unit (16) that meets a condition (26); anda data unit (16) that does not meet the condition (26).

52. The method of claim 51 , wherein the condition (26) is that:a time remaining before discard of the data unit (16) is below a time threshold; a value of a discard timer for the data unit (16) is below a time threshold;a packet delay budget that remains for the data unit (16) is below a time threshold; the communication device is configured to, or is allowed to, trigger or perform retransmission (20) of the data unit (16) without having received a report (18) of whether a prior transmission (14) of the data unit (16) was successfully received; orthe data unit (16) is from one of one or more specified logical channels for which the communication node (12A) is configured to trigger or perform autonomous retransmission (20).

53. The method of any of claims 50-52, wherein a data unit (16) is a MAC PDU or an RLC PDU, and wherein a transmission unit is a transport block.

54. A communication node (12A) configured to:receive signaling (24) that governs which data units (16) the communication node (12A) is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted; andhandle multiplexing of data units (16) according to the received signaling (24).

55. The communication node (12A) of claim 54, configured to perform the method of any of claims 47-49.

56. A node configured to:transmit signaling (24) that governs which data units (16) a communication node75(12A) is allowed, or is not allowed, to multiplex into the same transmission unit to be transmitted.

57. The node of claim 56, configured to perform the method of any of claims 51-53.

58. A computer program comprising instructions which, when executed by at least one processor of a communication node (12A), causes the communication node (12A) to perform the method of any of claims 46-49.

59. A computer program comprising instructions which, when executed by at least one processor of a node, causes the node to perform the method of any of claims 50-53.

60. A carrier containing the computer program of any of claims 58-59, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Images