Delay status reporting

Abstract

A communication device (12) is configured for use in a communication network (10). The communication device (12) transmits a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.

Description

[0001] DELAY STATUS REPORTING

[0002] TECHNICAL FIELD

[0003] The present application relates generally to a communication network, and more particularly relates to delay status report in such a network.

[0004] BACKGROUND

[0005] Some types of data, such as those associated with Extended Reality (XR) or other real-time services, have stringent latency requirements. If a communication device does not receive acknowledgement within a certain amount of time that the data has been delivered, the communication device may discard the data rather than try to retransmit the data, e.g., on the basis that the latency in delivery has made the data stale or otherwise unusable at the receiver. When the duration of time that remains before the communication device will discard the data becomes low, e.g., below a threshold, that data is deemed delay-critical. That is, delay-critical data may include data whose remaining time before discard is below a threshold.

[0006] 3rdGeneration Partnership Project (3GPP) Release 18 introduced a delay status report (DSR), as distinct from the legacy Buffer Status Report (BSR). Generally, a communication device may trigger a DSR to notify a communication network that buffered data at the communication device is or has become delay-critical, i.e., that the data will be discarded soon and should be prioritized by the communication network in its scheduling decisions to avoid being discarded. A DSR in Release 18 thereby includes, for each of one or more Logical Channel Groups (LCGs), a Remaining Time field and a Buffer Size field. For a given LCG, the Buffer Size field indicates a volume of uplink data that is (or is considered to be) delay-critical for that LCG and the Remaining Time field indicates the shortest remaining discard time for the reported delay-critical data. Triggering a DSR only when buffered data has become delay-critical ensures that only data at risk of being discarded due to time constraints is reported, optimizing network resources by focusing on the most timesensitive data. A DSR thereby helps the network manage delay-critical data, ensuring that data packets that are close to their discard time are handled with appropriate urgency to avoid missed deadlines.

[0007] A communication device may not only designate user data that is pending initial transmission as delay-critical, but may also consider control data and retransmission data as delay-critical for delay status reporting purposes. Control data such as Radio Link Control (RLC) STATUS Protocol Data Units (PDUs) or Packet Data Convergence Procotol (PDCP) Control PDUs provide feedback on received and missing data, enabling timely retransmissions. If control data such as this is delayed, the sender may not receiveacknowledgment in time, leading to unnecessary retransmissions or increased latency. Similarly, retransmission data includes data that needs to be resent due to errors in previous transmissions. Prompt retransmission of this data prevents data loss, maintains order, and ensures smooth data flow. Delays in retransmissions can result in higher end-to-end latency, buffer overflows, or degraded service quality, particularly in real-time applications. By classifying control data and retransmission data as delay-critical, the communication device ensures that these transmissions are prioritized in network scheduling decisions.

[0008] 3GPP Release 19 anticipates enhancements to the DSR. One enhancement contemplated is multiple so-called reporting thresholds. Whereas the Release 18 DSR reports the volume of data with a time remaining until discard below a single threshold, the Release 19 DSR can report, for each of multiple reporting thresholds, the volume of data with a time remaining until discard within a range defined by that reporting threshold. The inclusion of multiple reporting thresholds aims to provide a more detailed and adaptive reporting framework, ultimately benefiting applications with diverse latency and throughput requirements.

[0009] Multiple reporting thresholds however introduce challenges with how to handle reporting of control data, retransmission data, and / or other type(s) of data for DSR purposes. With data being reported as associated with respective reporting thresholds, for example, challenges exist regarding with which reporting threshold control data and / or retransmission data should be associated in a DSR, especially if the DSR does not report any delay-critical data (e.g., delay-critical user data pending initial transmission). A need therefore remains for reporting some types of data (e.g., control data and / or retransmission data) in a

[0010] multi-threshold DSR, in a way that minimizes complexity and signaling overhead.

[0011] SUMMARY

[0012] Some embodiments herein enable a delay status report to indicate which type(s) of data are, or are not, included in the data whose amount is reported. For example, a delay status report in some embodiments may indicate that the reported data includes only control data and / or retransmission data, and / or may indicate that the reported data does not include any delay-critical data (e.g., delay-critical user data pending initial transmission). Some embodiments do so by repurposing a remaining time field of the delay status report for such an indication, e.g., leverage possible value(s) that the remaining time field would not otherwise be set to when reporting a volume of data that includes only control data and / or retransmission data. Other embodiments dedicate previously reserved field(s) for this purpose. Still other embodiments repurpose other field(s) in a delay status report, alone or in combination, such as an LOG field that would otherwise indicate the presence of delay information for an LOG and / or a length field that indicates a length of the DSR. Regardless, these and other embodiments herein may advantageously equip the communication networkwith information about which type(s) of data are, or are not, included in the data whose amount is reported by a DSR, in a way that minimizes complexity and / or signaling overhead while still allowing the network to account for the type(s) of the reported data in its scheduling decisions.

[0013] More particularly, embodiments herein include a method performed by a communication device configured for use in a communication network. The method comprises transmitting a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0014] In some embodiments, the delay status report is configurable to indicate that the buffered data whose amount is indicated includes only one or more first types of data.

[0015] In some embodiments, the delay status report indicates the amount of buffered data associated with a first reporting threshold of a first logical channel group, and indicates which one or more types of data are, or are not, included in the buffered data associated with the first reporting threshold of the first logical channel group.

[0016] In some embodiments, the delay status report includes at least a buffer size field and a remaining time field. In some embodiments, the buffer size field has a value that indicates the amount of the buffered data. In some embodiments, the remaining time field is configurable to have any one of multiple possible values. In some embodiments, the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field, and the remaining time field is configurable to indicate which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field. In some embodiments, the multiple possible values of the remaining time field further include a zero value. In some embodiments, the remaining time field being set to the zero value indicates that the buffered data whose amount is indicated by the buffer size field includes only one or more first types of data.

[0017] In embodiments, the first type of data (or first types of data) includes control data and / or retransmission data. The control data may includes one or more Packet Data Convergence Protocol, PDCP, Control Protocol Data Units, PDUs, or one or more Radio Link Control, RLC, Control PDUs. Alternatively or additionally, the retransmission data includes one or more PDCP Service Data Units, SDUs, to be retransmitted, or one or more RLC SDUs to be retransmitted.

[0018] The second type(s) of data includes delay-critical data, e.g., delay-critical user data pending initial transmission, such as delay-critical PDCP SDUs for which no PDCP DataPDU have been constructed and / or PDCP Data PDlls that contain delay-critical PDCP SDlls and have not been submitted to lower layers.

[0019] Specifically, if there are a plurality of types of data including the first type of data and the second type of data (e.g. just both types of data) to be reported and if there are a plurality of reporting thresholds, all data of the first type is included in the lowest reporting threshold. In this case, if there is solely data of the first type of (e.g. no data of the second type of data) associated to the lowest threshold to report the associated remaining time value can be set to the lowest value, e.g. to zero, serving as an indication to the network that there is (likely) no delay critical data in this threshold. An option is to reserve the lowest remaining time value (e.g. zero) serving as an indication to the network that there is only data of the first type of data (control or retransmission data) reported under this threshold. Alternatively, another code value (other than zero) in the “Remaining Time” field could be reserved for such purposes.

[0020] In an embodiment the communication device transmits a delay status report that indicates in a first buffer size field indicative of an amount of buffered data only of the first type of data with a first remaining time field set to zero value. Additionally, the report may indicate a second buffer size field indicative of an amount of buffered data at least partially comprising data of the second type of data with a second remaining time field set to nonzero value.

[0021] In some embodiments, the delay status report is a multi-entry report that is configurable to report, for each of one or more logical channel groups, delay information for buffered data associated with each of multiple reporting thresholds of the logical channel group. In some embodiments, for each of the one or more logical channel groups, the delay status report indicates the amount of buffered data associated with a first reporting threshold of the logical channel group, and indicates which one or more types of data are, or are not, included in the buffered data associated with the first reporting threshold of the logical channel group. In some embodiments, the delay status report is configurable to include multiple sets of fields for each of the one or more logical channel groups. In some embodiments, the multiple sets of fields for a logical channel group include one set of fields for each respective one of the multiple reporting thresholds of the logical channel group. In some embodiments, a set of fields for a reporting threshold of a logical channel group includes at least a buffer size field configurable to have a value that indicates an amount of buffered data associated with the reporting threshold of the logical channel group, and a remaining time field configurable to have one of multiple possible values. In some embodiments, the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount isindicated by the buffer size field. In some embodiments, the remaining time field included in the set of fields for a first reporting threshold of a logical channel group indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field included in the set of fields for the first reporting threshold of the logical channel group. In some embodiments, the multiple possible values of the remaining time field further include a zero value. In some embodiments, the remaining time field being set to the zero value indicates that the buffered data, whose amount is indicated by the buffer size field included in the set of fields for the first reporting threshold of the logical channel group, includes only one or more first types of data.

[0022] In some embodiments, the delay status report is a multi-entry report that is configurable to report, for each logical channel group / of one or more logical channel groups, delay information for buffered data associated with each reporting threshold j of multiple reporting thresholds of the logical channel group. In some embodiments, the delay status report is configurable to include, for each reporting threshold j of each logical channel group / , a buffer size field ij configurable to have a value that indicates an amount of buffered data associated with the reporting threshold j of the logical channel group / , and a remaining time field ij configurable to have a value that indicates a shortest remaining discard time among the buffered data associated with the reporting threshold j of the logical channel group / . In some embodiments, for a first reporting threshold J=1, the remaining time field ij is set to zero if only one or more first types of data are associated with the first reporting threshold j=1 of the logical channel group / .

[0023] In some embodiments, the one or more first types of data include control data and / or retransmission data. In some embodiments, the control data includes one or more Packet Data Convergence Protocol, PDCP, Control Protocol Data Units, PDUs, or one or more Radio Link Control, RLC, Control PDUs. In other embodiments, alternatively or additionally, the retransmission data includes one or more PDCP Service Data Units, SDUs, to be retransmitted, or one or more RLC SDUs to be retransmitted.

[0024] In some embodiments, the method further comprising triggering the delay status report based on a remaining time before discard of at least some of the buffered data being below a reporting threshold.

[0025] Other embodiments herein include a method performed by a radio network node of a communication network. The method comprises receiving, from a communication device, a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0026] In some embodiments, the delay status report is configurable to indicate that the buffered data whose amount is indicated includes only one or more first types of data.In some embodiments, the delay status report indicates the amount of buffered data associated with a first reporting threshold of a first logical channel group, and indicates which one or more types of data are, or are not, included in the buffered data associated with the first reporting threshold of the first logical channel group.

[0027] In some embodiments, the delay status report includes at least a buffer size field and a remaining time field. In some embodiments, the buffer size field has a value that indicates the amount of the buffered data. In some embodiments, the remaining time field is configurable to have any one of multiple possible values. In some embodiments, the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field, and the remaining time field is configurable to indicate which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field. In some embodiments, the multiple possible values of the remaining time field further include a zero value. In some embodiments, the remaining time field being set to the zero value indicates that the buffered data whose amount is indicated by the buffer size field includes only one or more first types of data.

[0028] In some embodiments, the delay status report is a multi-entry report that is configurable to report, for each of one or more logical channel groups, delay information for buffered data associated with each of multiple reporting thresholds of the logical channel group. In some embodiments, for each of the one or more logical channel groups, the delay status report indicates the amount of buffered data associated with a first reporting threshold of the logical channel group, and indicates which one or more types of data are, or are not, included in the buffered data associated with the first reporting threshold of the logical channel group.

[0029] In some embodiments, the delay status report is configurable to include multiple sets of fields for each of the one or more logical channel groups. In some embodiments, the multiple sets of fields for a logical channel group include one set of fields for each respective one of the multiple reporting thresholds of the logical channel group. In some embodiments, a set of fields for a reporting threshold of a logical channel group includes at least a buffer size field configurable to have a value that indicates an amount of buffered data associated with the reporting threshold of the logical channel group, and a remaining time field configurable to have one of multiple possible values. In some embodiments, the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field. In some embodiments, the remaining time field included in the set of fields for a firstreporting threshold of a logical channel group indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field included in the set of fields for the first reporting threshold of the logical channel group. In some embodiments, the multiple possible values of the remaining time field further include a zero value. In some embodiments, the remaining time field being set to the zero value indicates that the buffered data, whose amount is indicated by the buffer size field included in the set of fields for the first reporting threshold of the logical channel group, includes only one or more first types of data.

[0030] In some embodiments, wherein the delay status report is a multi-entry report that is configurable to report, for each logical channel group / of one or more logical channel groups, delay information for buffered data associated with each reporting threshold j of multiple reporting thresholds of the logical channel group. In some embodiments, the delay status report is configurable to include, for each reporting threshold j of each logical channel group / , and a remaining time field ij configurable to have a value that indicates a shortest remaining discard time among the buffered data associated with the reporting threshold j of the logical channel group / . In some embodiments, for a first reporting threshold J=1, the remaining time field ij is set to zero if only one or more first types of data are associated with the first reporting threshold j=1 of the logical channel group / . In some embodiments, the one or more first types of data include control data and / or retransmission data. In some embodiments, the control data includes one or more Packet Data Convergence Protocol, PDCP, Control Protocol Data Units, PDUs, or one or more Radio Link Control, RLC, Control PDUs. In other embodiments, alternatively or additionally, the retransmission data includes one or more PDCP Service Data Units, SDUs, to be retransmitted, or one or more RLC SDUs to be retransmitted.

[0031] In some embodiments, the method further comprises performing scheduling based on the received delay status report.

[0032] Other embodiments herein include a communication device configured to transmit a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0033] In some embodiments, the communication device is configured to perform of any of the steps described above for the communication device.

[0034] Other embodiments herein include a radio network node of a communication network. The radio network node is configured to receive, from a communication device, a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.In some embodiments, the radio network node is configured to perform of any of the steps described above for the radio network node.

[0035] In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the steps described above for the communication device.

[0036] In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a radio network node, causes the radio network node to perform the steps described above for the radio network node.

[0037] In some embodiments, a carrier containing the computer program is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0038] Other embodiments herein include a communication device comprising communication circuitry and processing circuitry. The processing circuitry is configured to transmit a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0039] In some embodiments, the processing circuitry is configured to perform the steps described above for the communication device.

[0040] Other embodiments herein include a radio network node of a communication network, the radio network node comprising communication circuitry and processing circuitry. The processing circuitry is configured to receive, from a communication device, a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0041] In some embodiments, the processing circuitry is configured to perform the steps described above for the radio network node.

[0042] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0043] BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 is a block diagram of a communication device according to some embodiments.

[0045] Figure 2 is a block diagram of a delay status report according to some embodiments. Figure 3 is a block diagram of a delay status report according to other embodiments. Figure 4 is a block diagram of a buffer status report according to some embodiments. Figure 5 is a block diagram of a delay status report according to other embodiments. Figure 6 is a block diagram of a delay status report according to other embodiments.Figure 7 is a logic flow diagram of a method performed by a communication device in accordance with particular embodiments.

[0046] Figure 8 is a logic flow diagram of a method performed by a radio network node of a communication network in accordance with other particular embodiments.

[0047] Figure 9 is a block diagram of a communication device according to some embodiments.

[0048] Figure 10 is a block diagram of a network node according to some embodiments. Figure 11 is a block diagram of a communication system according to some embodiments.

[0049] Figure 12 is a block diagram of a communication system according to other embodiments.

[0050] Figure 13 is a block diagram of a wireless device according to some embodiments. Figure 14 is a block diagram of a network node according to other embodiments. Figure 15 is a block diagram of a virtualization environment according to other embodiments.

[0051] DETAILED DESCRIPTION

[0052] Figure 1 shows a communication device 12 according to some embodiments, e.g., in the form of a user equipment (UE). The communication device 12 is configured to receive service from a communication network 10, e.g., a 5G or6G network. The communication device 10 includes a network node 14 (e.g., a radio network node) that serves the communication device 12 in this regard. The network node 14 may for example make or participate in decisions about whether and / or how to schedule transmissions of data from the communication device 12, e.g., transmissions of uplink data from the communication device 12 to the communication network 10.

[0053] To assist the network node 14 with its scheduling decision-making, the communication device 12 as shown transmits a delay status report 20 to the network node 14, e.g., at a Medium Access Control (MAC) layer. The delay status report 20 is configurable to report delay information 27 about data 18 buffered at the communication device 12, e.g., in a buffer 12B and / or available to a MAC entity of the communication device 12. The buffered data 18 may include Packet Data Convergence Protocol (PDCP) data or Radio Link Control (RLC) data, e.g., received by a MAC entity on one or more logical channels (LCHs).

[0054] The delay status report 20 as shown in this regard indicates an amount 18T of buffered data 18 at the communication device 12, e.g., reflecting a volume of the buffered data 18. Notably, the delay status report 20 also indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated. In embodiments for example where the delay status report 20 is configurable to report any of multiple possible types of buffered data 18, the delay status report 20 effectively specifieswhich of those multiple possible types of buffered data 18 is reported. By indicating this, the delay status report 20 advantageously equips the network node 14 with information about the type(s) 18T of buffered data 18, for use in making decisions about whether and / or how to schedule transmission of that buffered data 18. Alternatively or additionally, indicating the type(s) 18T of buffered data 18 reported by the delay status report 20 informs the network node 14 about how to parse and / or interpret the delay status report 20.

[0055] In some embodiments, for example, the delay status report 20 indicates that the buffered data 18 whose amount is indicated includes only one or more first types 18T-1 of data, e.g., to the exclusion of one or more other types of data that are reportable by the delay status report 20. The first type(s) 18T-1 of data may for instance include control data, e.g., RLC Status PDlls or PDCP Control PDlls. Alternatively or additionally, the first type(s) 18T-1 of data may include retransmission data, e.g., PDCP Service Data Units (SDUs) to be retransmitted, PDCP PDUs to be retransmitted, or RLC Data PDUs pending retransmission.

[0056] In other embodiments, the delay status report 20 alternatively or additionally indicates that the buffered data 18 whose amount is indicated excludes one or more second types 18T-2 of data. The second type(s) 18T-2 of data may for example include delay-critical data, e.g., delay-critical user data pending initial transmission, such as delay-critical PDCP SDUs for which no PDCP Data PDU have been constructed and / or PDCP Data PDUs that contain delay-critical PDCP SDUs and have not been submitted to lower layers.

[0057] In some embodiments, the delay status report 20 is a multi-threshold or multi-entry report. As shown in Figure 2, such a report may be configurable to report delay information 27-1...27-N for each of one or more logical channel groups (LCGs) 23-1...23-N. In fact, in one or more such embodiments, the report 20 is configurable to report, for at least one of the LCG(S) 23-1...23-N, delay information for buffered data associated with each of multiple reporting thresholds 25 of the logical channel group 23-n. As shown, for instance, the delay status report 20 reports delay information 29-1...29-X for each of multiple reporting thresholds 25-1...25-X of LCG 23-1, reports delay information 29-1...29-Y for each of multiple reporting thresholds 25-1...25-Y of LCG 23-N, etc.

[0058] In some embodiments, the delay status report 20 is configurable to indicate the delay information 29 for each reporting threshold 25 of an LCG 23-n with a set of fields, shown as including at least a buffer size field 20A and a remaining time field 20B. As such, the delay status report 20 is configurable to include multiple sets of fields for each of the LCG(s) 23-1...23-N. The multiple sets of fields for an LCG 23-n include one set of fields for each respective one of the multiple reporting thresholds 25 of the LCG 23-n. The set of fields for a reporting threshold 25 of an LCG 23-n includes at least a buffer size field 20A and a remaining time field 20B.The buffer size field 20A for a reporting threshold 25 of an LCG 25-n is configurable to have a value that indicates an amount of buffered data 18 associated with the reporting threshold 25 of the LCG 25-n. The remaining time field 20B for a reporting threshold 25 of an LCG 25-n is configurable to have one of multiple possible values. The multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device 12 discards at least some of the buffered data 18 whose amount is indicated by the buffer size field 20A.

[0059] In this context, though, some embodiments herein repurpose the remaining time field 20B under some circumstances to indicate which one or more types of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. That is, in some embodiments, the remaining time field 20B is configurable to indicate which one or more types of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the corresponding buffer size field 20A.

[0060] In one such embodiment shown in Figure 3, for instance, the remaining time field 20B (e.g., for a reporting threshold 25 of an LCG 25-n) is configurable to have one of multiple possible values 21. These multiple possible values 21 include at least one or more possible values 21A (e.g., 1, 2, 3, etc.) that respectively indicate one or more possible nonzero durations of time remaining before the communication device 12 discards at least some of the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. These value(s) 21 A are thereby appropriately referred to as shortest discard timer value(s) as they may indicate different possible values for the shortest discard timer value amongst data packet(s) represented by the amount 18A of buffered data 18 indicated by the buffer size field 20A. Notably, though, the multiple possible values 21 further include a reserved value 21 B (e.g., 0) that indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. The reserved value 21 B is accordingly labelled as being a data type value. The reserved value 21 B may for instance indicate that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only control data, includes only retransmission data, includes only data that is either control data, retransmission data, or a combination thereof, and / or does not include any delay-critical data. Regardless, the reserved value 21 B may be a lowest possible value for the remaining time field 20B and / or may be a value that would not otherwise be set when reporting an amount 18A of data that includes the one or more types 18T of data. These and other embodiments may thereby leverage possible value(s) that the remaining time field 20B would not otherwise be set to when reporting a volume of data 18 that includes only the indicated type(s) 18T of data.

[0061] For example, if at least some delay-critical data is included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A, the remaining time field 20B is tohave any one of the one or more possible values 21 A that respectively indicate one or more possible non-zero durations of time remaining before the communication device 12 discards the delay-critical data. But, if no delay-critical data is included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A, the remaining time field 20B is to have the reserved value 21 B, in order to indicate which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A.

[0062] Some embodiments repurpose the remaining time field 20B in this way on a reporting threshold by reporting threshold basis. Consider for example a scenario where the buffered data 18 whose amount is indicated by the buffer size field 20A associated with a first reporting threshold 25-1 of a first logical channel group 23-1 includes only control data and / or retransmission data, e.g., no delay-critical data is associated with that first reporting threshold 25-1. In this case, the remaining time field 20B associated with the first reporting threshold 25-1 of the first logical channel group 23-1 has the reserved value 21 B, in order to indicate that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only control data and / or retransmission data. By contrast, the buffered data 18 whose amount is indicated by the buffer size field 20A associated with a second reporting threshold 25-2 of the first logical channel group 23-1 may include at least some delay-critical data, i.e. , not only control data and / or retransmission data. In this case, the remaining time field 20B associated with the second reporting threshold 25-2 of the first logical channel group 23-1 has one of the shortest discard timer value(s) 21 A, in order to indicate a remaining time until discard of at least some of the buffered data indicated by the buffer size field 20A. Remaining time fields 20B associated with different reporting thresholds may thereby be interpreted in different ways, depending on whether the buffered data associated with that reporting threshold includes only control data and / or retransmission data.

[0063] Other embodiments repurpose the remaining time field 20B in this way on an LOG by LOG basis. In some embodiments, for example, certain type(s) of data (e.g., control data and / or retransmission data) are (always) to be reported as associated with the first reporting threshold 25-1 of a first logical channel group 23-1, e.g., the lowest reporting threshold and / or the reporting threshold associated with the highest scheduling priority. That is, if any data 18 buffered for the first logical channel group 23-1 is of the certain type(s), that data 18 is reported as being associated with the first reporting threshold 25-1 of the first LCG 23-1 (i.e., never reported as being associated with any of the other reporting thresholds of the first LCG 23-1). So, if the buffered data 18 whose amount is indicated by the buffer size field 20A associated with the first reporting threshold 25-1 of the first logical channel group 23-1 includes only control data and / or retransmission data (e.g., no delay-critical data), the remaining time field 20B associated with the first reporting threshold 25-1 of the first logicalchannel group 23-1 has the reserved value 21 B, in order to indicate that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only control data and / or retransmission data. But, if the buffered data 18 whose amount is indicated by the buffer size field 20A associated with the first reporting threshold 25-1 of the first logical channel group 23-1 does not include only control data and / or retransmission data (e.g., at least some delay-critical data is included), the remaining time field 20B associated with the first reporting threshold 25-1 of the first logical channel group 23-1 has one of the shortest discard timer value(s) 21 A, in order to indicate a remaining time until discard of at least some of the buffered data 18 indicated by the buffer size field 20A. Remaining time fields 20B associated with the other reporting thresholds of the first logical channel group 23-1 may only have one of the shortest discard timer value(s) 21A, though, as the communication device 12 is not to report control data and / or retransmission data in association with those other reporting thresholds. The delay status report 20 may be configured similarly for any other LCG(s) 25 indicated in the report 20.

[0064] In still other embodiments not shown, the delay status report 20 may include a subset of field(s) that indicates which type(s) 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated. This subset of field(s) may for example include a reserved or dedicated field, e.g., reserved or dedicated for indicating which type(s) 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated. The reserved or dedicated field may for example be a field which indicates that the buffered data includes only control and / or retransmission data.

[0065] Alternatively or additionally, the subset of field(s) may include a length field indicating a length of the delay status report 20.

[0066] Alternatively or additionally, the subset of field(s) may include a field (e.g. an LCGi field) that is configurable to indicate presence of delay information for a logical channel group. For example, the field may be configurable to have any one of multiple possible values. The multiple possible values include a first value (e.g., 1) that indicates presence of delay information in the delay status report for a first logical channel group 23-1 amongst one or more logical channel groups at the communication device 12. The multiple possible values also include a second value (e.g., 0) that indicates the buffered data 18 includes only one or more first types of data and / or excludes one or more second types of data. For example, the field may be an LCGt field, where the first logical channel group is a logical channel group that has a lowest index i in the delay status report 20 amongst any of the one or more logical channel groups. This may thereby be the case when no delay-reporting data is associated with any of the logical channel group(s), e.g., no delay-reporting PDCP SDlls or PDCP Data PDlls that contain the delay-reporting PDCP SDlls.Note that, although some embodiments herein use the buffer size field for indicating the amount 18A of buffered data 18 whose type(s) 18T are indicated by the delay status report 20, other embodiments herein repurpose other field(s) in the delay status report 20 for indicating at least some of that amount 18A. For example, some embodiments repurpose the remaining time field for indicating at least some of the amount 18. Generally, for instance, the delay status report 20 in some embodiments may include a first field (e.g., a remaining time field) configurable to indicate an amount of the first type of data (e.g., control data) included in the buffered data 18 and / or a second field (e.g., a buffer size field) configurable to indicate an amount of the second type of data (e.g., retransmission data) included in the buffered data 18.

[0067] Note also that in some embodiments the buffered data 18 whose type(s) are indicated by the delay status report 20 may be for or associated with a certain logical channel group. Or, in other embodiments, the buffered data 18 whose type(s) are indicated by the delay status report 20 may not be associated with any certain logical channel group. Rather, the buffered data 18 whose type(s) are indicated by the delay status report 20 may be data buffered across multiple logical channel groups.

[0068] Similarly, in some embodiments, the buffered data 18 whose type(s) are indicated by the delay status report 20 may be for or associated with a certain reporting threshold. Or, in other embodiments, the buffered data 18 whose type(s) are indicated by the delay status report 20 may not be associated with any certain reporting threshold. Rather, the buffered data 18 whose type(s) are indicated by the delay status report 20 may be data buffered across multiple reporting thresholds.

[0069] Consider now some embodiments herein in a context where the delay status report 20 is a DSR as otherwise specified by 3GPP, the communication device 12 is a UE, and the DSR indicates whether buffered data includes only control data and / or retransmission data (e.g., the first type(s) of data herein include control data and / or retransmission data).

[0070] In some embodiments, the buffer status report 20 is a Rel-19 Delay Status Report (DSR). The DSR is a MAC Control Element (CE), with separate handling from the legacy Buffer Status Report (BSR). The format for the DSR may be as shown in Figure 4, with multiple pairs of Remaining Time and Buffer Size fields for each LCG, one for each reporting threshold of an LCG.

[0071] In some embodiments, the Buffer Size field is defined as follows. In the Single Entry DSR MAC CE, the Buffer Size field indicates the total amount of delay-critical UL data for an LCG according to the data volume calculation procedure specified in clause 5.5 in TS 38.322 V18.2.0 and clause 5.15 in TS 38.323 V18.5.0 for the associated RLC and PDCP entities, respectively, after the MAC PDU has been built. In the Multiple Entry DSR MAC CE, the field Buffer Size i,j indicates the total amount of delay-reporting data associated with the reportingthreshold j of LCG i, according to the data volume calculation procedure specified in clause 5.15 in TS 38.323 V18.5.0 for the associated RLC and PDCP entities, respectively, after the MAC PDU has been built. If the corresponding LCG is configured with additionalBS-TableAllowed and the amount of data to be reported by this field is within the buffer sizes specified in Table 6.1.3.1-3, the MAC entity shall use the buffer sizes specified in Table 6.1.3.1-3 to set the value of this field; otherwise, the MAC entity shall use Table 6.1.3.1-2 instead. This field is indicated in number of bytes. The length of this field is 8 bits.

[0072] In some embodiments, Delay-critical PDCP SDU is defined as follows: if pdu-SetDiscard is not configured, a PDCP SDU for which the remaining time till discardTimer expiry is less than the remainingTimeThreshold. If pdu-SetDiscard is configured, a PDCP SDU belonging to a PDU Set of which at least one PDCP SDU has the remaining time till discardTimer expiry less than the remainingTimeThreshold.

[0073] In some embodiments, Delay-reporting PDCP SDU is defined as follows, see, e.g., R2-2313697 “Introduction of XR Enhancements”. If pdu-SetDiscard is not configured, a delay-reporting PDCP SDU associated with the i:th dsr-ReportingThreshold is a PDCP SDU for which the remaining time till discardTimer expiry is less than the i:th dsr-ReportingThreshold and larger than or equal to the i-1 :th dsr-ReportingThreshold (if i>1) or larger than zero (if i=1). If pdu-SetDiscard is configured, a delay-reporting PDCP SDU associated with the i:th dsr-ReportingThreshold is a PDCP SDU belonging to a PDU Set of which the PDU Set remaining time is less than the i:th dsr-ReportingThreshold and larger than or equal to the i-1 :th dsr-ReportingThreshold (if i>1) or larger than zero (if i=1). The dsr-ReportingThresholds configured for the PDCP entity are ordered in ascending order.

[0074] A PDU Set here may refer to a set of PDUs that carry data from the same unit of information at the application layer.

[0075] Some embodiments herein enable enhancements to the DSR for support of UL scheduling to enable high XR capacity while meeting delay requirements / avoiding too late PDUs. Some embodiments in this regard enable enhanced DSR (Delay Status Report) reporting with multiple pairs of remaining time and buffer size for an LCG.

[0076] In some embodiments, the DSR will include control PDUs and retransmitted data in the data volume calculation. Some embodiments accommodate for always including this data in the lowest reporting threhsold that has data to be reported. Other embodiments herein accommodate for always including the data in the lowest reporting threhsold, despite if that threshold has delay critical data or not.

[0077] Generally, then, some embodiments address how to handle the control PDUs and retransmitted data in the reporting delay data volume calculation. Some embodiments for example define in which threshold the control and retransmission data should be included,even when not having any data in any reporting thresholds in an LCG. Some embodiments handle this in a way that minimizes the complexity and overhead.

[0078] Some embodiments for example propose ways to handle the reporting of the control PDlls and retransmission data when there is no reporting data in the lowest reporting threshold or any reporting data at all in the LCG. Some embodiments provide an advantage that the network get an expected behavior of the reporting of control PDU and retransmission data with minimal overhead in the reporting.

[0079] In a first embodiment, the control PDlls and retransmission data are always included in the lowest reporting threshold. In this case if there is no delay critical data in that threshold to report, then the remaining time value to use can be defined to always be the lowest value, e.g. 0, since this would be an indication to the network that there is (likely) no delay critical data in this threshold. This is an example of repurposing the remaining time field as described above, e.g., using a reserved or dedicated value (e.g., 0) for this purpose. An option is to reserve the lowest remaining time value so that by using it is an indication that there are only control or retransmission data reported (i.e. DSR never report 0 as remaining time otherwise). Alternatively, another code value (other than zero) in the “Remaining Time” field could be reserved for such purposes.

[0080] In a second embodiment, the control PDlls and retransmission data is included in the reporting threshold that contain delay critical data and the remaining time value of the reporting delay critical data is used. If no reporting threshold contains any delay critical data for this LCG, then a fallback solution similar to the one in the first embodiment, i.e. with a reserved remaining time value, can be used.

[0081] In a third embodiment, if a DSR has been triggered but there is only control PDU and retransmission data to be reported for, i.e. no delay critical data in any of the thresholds in any LCG, then the DSR can be cancelled so that a DSR is not sent with only control and retransmission data. Alternatively, the opposite behavior can be applied so that a DSR is sent even when it contains only control and retransmission data.

[0082] In a fourth embodiment, as an example of the subset of field(s) discussed herein, the Reserve bit “R” can be used to indicate that the reported buffer is related to control PDUs and / or retransmissions. The indicated “remaining time” may be associated to the lowest remaining time from the set of packets pending of retransmissions. The length field in the MAC-CE header can be used to identify that there are more data than the one which should be included if only the data from LCGs is included (e.g. if only 3 LCGs are reported, there should be in total 7 bytes of payload; however, if the length field indicates 8 bytes, the network can understand that there is more information).

[0083] In a fifth embodiment, when no other data is in the buffer, the first field in the DSR field indicating the presence of delay information for the LCGi is set to 0. In other words, allLCGi will be set to 0. This indicates that there is no data in any of the LCG. Then, the following 2 bytes will contain the remaining time and data volume (as in legacy) indicating the packets for retransmission or / and Control PDlls. The indicated “remaining time” could follow the same procedure as described in the first or fourth embodiments (see Figure 5).

[0084] Alternatively, the message could carry both the retransmission and control PDlls in separate fields. Since control PDlls are very small, 4 to 5 bits would be sufficient to indicate the buffer size. A full byte would be, nevertheless, needed. 2 bytes could be used to indicate the buffer size for retransmissions including the BS table and other fields, and yet another byte could be used to provide control PDU buffer size information (see Figure 6).

[0085] When the receiver reads the LCGi byte, optionally together with the Length field, it will conclude that the information contained is related to control PDUs and retransmissions. Typically, if all LCGs are set to 0, no further information would be included; thus, the Length field is exploited to differentiate these two situations. Nonetheless, in some embodiments, even if all LCGi are not set to zero, the Length field would be enough to identify that the MAC CE payload is larger than what would be expected.

[0086] In a sixth embodiment related to the fifth embodiment, there is only control and retransmission data in the different LCGs. Just as in the fifth embodiment all LCGi are then set to 0. Then for each LCGi the remaining time field is used to indicate the size of control data and the field for buffer size is used to indicate the size of retransmission data for that particular LCGi. In this embodiment, either separate values for all LCGs would be reported for or a joint value indicating for all LCGs. In the latter option, it can be configured / defined which type of data should be reported in each field. If only the data mapped to the first field is present, then only that field could be reported.

[0087] A variant of fifth and sixth embodiments is that some LCGs have delay critical data to report but some LCG only have control and retransmission data. The LCGs that have delay critical data will include the control and retransmission data together with the delay critical data as in the first or second embodiment, while the LCGs that have zero delay critical data will report the control and retransmission data in a similar fashion as the fifth or sixth option.

[0088] Specifically, if there are a plurality of types of data including the first type of data and the second type of data (e.g. just both types of data) to be reported and if there are a plurality of reporting thresholds, all data of the first type is included in the lowest reporting threshold. In this case, if there is solely data of the first type of (e.g. no data of the second type of data) associated to the lowest threshold to report, the associated remaining time value can be set to the lowest value, e.g. to zero, serving as an indication to the network that there is (likely) no delay critical data in this threshold. An option is to reserve the lowest remaining time value (e.g. zero) serving as an indication to the network that there is only data of the first type of data (control or retransmission data) reported under this threshold.Alternatively, another code value (other than zero) in the “Remaining Time” field could be reserved for such purposes.

[0089] In an embodiment the communication device transmits a delay status report that indicates in a first buffer size field indicative of an amount of buffered data only of the first type of data with a first remaining time field set to zero value. Additionally, the report may comprise a second buffer size field indicative of an amount of buffered data at least partially comprising data of the second type of data with a second remaining time field set to nonzero value.

[0090] In an embodiment thereto, the delay status report is a multi-entry report to report, for each of a plurality of channel groups, delay information for buffered data associated with each one of the multiple reporting thresholds.

[0091] Therein, for each of the one or more logical channel groups, the delay status report indicates the amount of first buffered data associated with a first reporting threshold refers to a logical channel group that only comprises data of the first type of data. A second logical channel group associated with a second threshold may comprise either data only of the second type of data, or data of both the first type and the second type of data.

[0092] It could be so that the LCG fields set to 0 could still report the control and retransmission data (following the structure of the earlier embodiments) while the LCG fields set to 1 incorporate the control and retransmission data according to other rules. Another way could be to have two fields, containing all the control / retransmission data in the end (or beginning) of the DSR, i.e. after all LCGs have reported the Delay Reporting data. These two fields could then either contain only the control / retx data of the LCG fields set to 0 or all LCGs (and the control / retx data for these LCGs are not multiplexed with Delay reporting data).

[0093] Note that, in some embodiments, RLC PDUs can be categorized into RLC data PDUs and RLC control PDUs. RLC data PDUs are used by TM, UM and AM RLC entities to transfer upper layer PDUs (i.e. RLC SDUs). RLC control PDUs are used by AM RLC entity to perform ARQ procedures. RLC Control PDUs include STATUS PDUs. A STATUS PDU is used by the receiving side of an AM RLC entity to inform the peer AM RLC entity about RLC data PDUs that are received successfully, and RLC data PDUs that are detected to be lost by the receiving side of an AM RLC entity.

[0094] For the purpose of MAC buffer status reporting, the UE shall consider the following as RLC data volume:

[0095] - RLC SDUs and RLC SDU segments that have not yet been included in an RLC data PDU;

[0096] - RLC data PDUs that are pending for initial transmission;

[0097] - RLC data PDUs that are pending for retransmission (RLC AM).For the purpose of MAC delay status reporting, the UE shall consider the following as delay-critical RLC data volume:

[0098] - delay-critical RLC SDlls and delay-critical RLC SDU segments that have not yet been included in an RLC data PDU;

[0099] - RLC data PDUs pending for initial transmission, and containing a delay-critical RLC SDU or a delay-critical RLC SDU segment;

[0100] - RLC data PDUs that are pending for retransmission (RLC AM).

[0101] Regarding delay-critical vs delay-reporting data, consider the following using PDCP as an example. In Rel-18 they call it “delay-critical PDCP data volume”, and the “normal” delay critical data included is then “delay-critical PDCP SDUs” and “PDCP Data PDUs that contain the delay-critical PDCP SDUs” (in addition to control and retransmission data).

[0102] In Rel-19, similar wording is used, so it is “delay-reporting PDCP data volume”, which includes “delay-reporting PDCP SDUs” and “PDCP Data PDUs that contain the delayreporting PDCP SDUs”, as well as control and retransmission data.

[0103] In view of the modifications and variations herein, Figure 7 depicts a method performed by a communication device 12 configured for use in a communication network 10 in accordance with particular embodiments. The method includes transmitting a delay status report 20 that indicates an amount 18A of buffered data 18 at the communication device 12 and that indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated (Block 700).

[0104] In some embodiments, the delay status report 20 indicates that the buffered data 18 whose amount 18A is indicated includes only one or more first types 18T-1 of data and / or excludes one or more second types 18T-2 of data. In some embodiments, the delay status report 20 indicates that the buffered data 18 whose amount 18A is indicated includes only one or more first types 18T-1 of data. In some embodiments, the one or more first types 18T-1 of data include control data. In other embodiments, the one or more first types 18T-1 of data include alternatively or additionally retransmission data. In some embodiments, the delay status report 20 indicates that the buffered data 18 whose amount 18A is indicated excludes one or more second types 18T-2 of data. In some embodiments, the one or more second types 18T-2 of data include delay-critical data.

[0105] In some embodiments, the delay status report 20 indicates the amount 18A of buffered data 18 for a first logical channel group 23-1 , and indicates which one or more types 18T of data are, or are not, included in the buffered data 18 for the first logical channel group 23-1.

[0106] In some embodiments, the delay status report 20 indicates the amount 18A of buffered data 18 associated with a first reporting threshold 25-1 of a first logical channelgroup 23-1, and indicates which one or more types 18T of data are, or are not, included in the buffered data 18 associated with the first reporting threshold 25-1 of the first logical channel group 23-1. In some embodiments, the first reporting threshold 25-1 is a lowest reporting threshold amongst multiple reporting thresholds 25 of the logical channel group 23. In some embodiments, no delay-critical data is associated with the first reporting threshold 25-1 of the first logical channel group 23-1. In some embodiments, no delay-critical data is associated with any of multiple reporting thresholds 25 of the first logical channel group 23-1.

[0107] In some embodiments, the delay status report 20 includes at least a buffer size field 20A and a remaining time field 20B. In some embodiments, the buffer size field 20A has a value that indicates the amount 18A of the buffered data 18. In some embodiments, the remaining time field 20B is configurable to have any one of multiple possible values 21. In some embodiments, the multiple possible values 21 include at least one or more possible values 21 that respectively indicate one or more possible non-zero durations of time remaining before the communication device 12 discards at least some of the buffered data 18 whose amount 18A is indicated by the buffer size field 20A, and the delay status report 20 indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. In some embodiments, the remaining time field 20B is configurable to indicate which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. In some embodiments, the multiple possible values 21 of the remaining time field 20B further include a reserved value that indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the buffer size field 20A. In some embodiments, the remaining time field 20B in the transmitted delay status report 20 has the reserved value. In some embodiments, the reserved value indicates that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only control data. In other embodiments, the reserved value indicates that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only retransmission data. In yet other embodiments, the reserved value indicates that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A includes only data that is either control data, retransmission data, or a combination thereof. In still yet other embodiments, the reserved value indicates that the buffered data 18 whose amount 18A is indicated by the buffer size field 20A does not include any delay-critical data. In some embodiments, the reserved value is 0. In some embodiments, the reserved value is a lowest value possible for the remaining time field 20B. In some embodiments, the buffer size field 20A is a first buffer size field and the remaining time field 20B is a first remaining time field. In some embodiments, the first buffer size field and the first remaining time field are associated with a first logical channel group 23-1 amongst one or more logical channel groups 23 at thecommunication device 12, and a first reporting threshold 25-1 included amongst multiple reporting thresholds 25 of the first logical channel group 23-1. In some embodiments, the value of the first buffer size field indicates an amount 18A of buffered data 18 that is for the first logical channel group 23-1. In other embodiments, the value of the first buffer size field indicates an amount 18A of buffered data 18 that is alternatively or additionally associated with the first reporting threshold 25-1. In some embodiments, the first reporting threshold 25-1 is a lowest reporting threshold amongst the multiple reporting thresholds 25. In some embodiments, no delay-critical data is associated with the first reporting threshold 25-1 of the first logical channel group 23-1. In some embodiments, if at least some delay-critical data is associated with the first reporting threshold 25-1 of the first logical channel group 23-1, the first remaining time field is to have any one of the one or more possible values 21 that respectively indicate one or more possible non-zero durations of time remaining before the communication device 12 discards the delay-critical data included in the buffered data 18 whose amount 18A is indicated by the first buffer size field, and if no delay-critical data is associated with the first reporting threshold 25-1 of the first logical channel group 23-1, the first remaining time field is to have the reserved value to indicate which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated by the first buffer size field. In some embodiments, no delay-critical data is associated with any of the multiple reporting thresholds 25 of the first logical channel group 23-1.

[0108] In some embodiments, the delay status report 20 includes a subset of one or more fields that indicates which one or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated. In some embodiments, the delay status report 20 is a 3GPP Release 19+ delay status report 20, and at least one of the one or more fields in the subset is a Reserved Bit of a 3GPP Release 18 delay status report 20. In some embodiments, at least one of the one or more fields in the subset is a field dedicated for indicating which one or more types 18T of data are, or are not, included in the buffered data 18. In some embodiments, at least one of the one or more fields in the subset is a field dedicated for indicating whether, or that, the buffered data 18 includes only control and / or retransmission data. In some embodiments, at least one of the one or more fields in the subset is a field which indicates that the buffered data 18 includes only control and / or retransmission data. In some embodiments, the delay status report 20 indicates a non-zero duration of time remaining before the communication device 12 discards at least some of the retransmission data included in the buffered data 18 whose amount 18A is indicated. In some embodiments, the subset is included in a set of fields that is associated with a first logical channel group 23-1 amongst one or more logical channel groups 23 at the communication device 12, and a first reporting threshold 25-1 included amongst multiple reporting thresholds 25 of the first logical channel group 23-1. In some embodiments, atleast one of the one or more fields in the subset is a length field indicating a length of the delay status report 20. In some embodiments, at least one of the one or more fields in the subset is a field configurable to have any one of multiple possible values 21. In some embodiments, the multiple possible values 21 include a first value that indicates presence of delay information 27 in the delay status report 20 for a first logical channel group 23-1 amongst one or more logical channel groups 23 at the communication device 12, and a second value that indicates the buffered data 18 includes only one or more first types 18T-1 of data and / or excludes one or more second types 18T-2 of data. In some embodiments, said field has the second value in the transmitted delay status report 20. In some embodiments, the first value is 0 and the second value is 1. In some embodiments, said field is an LCGt field. In some embodiments, the first logical channel group 23-1 is a logical channel group that has a lowest index i in the delay status report 20 amongst any of the one or more logical channel groups 23. In some embodiments, no delay-reporting data is associated with any of the one or more logical channel groups 23, e.g., no delay-reporting PDCP SDlls or PDCP Data PDlls that contain the delay-reporting PDCP SDlls. In some embodiments, said field has the second value in the transmitted delay status report 20 and indicates the buffered data 18 includes only the one or more first types 18T-1 of data. In some embodiments, the one or more first types 18T-1 of data include control data and / or retransmission data. In some embodiments, the delay status report 20 indicates a non-zero duration of time remaining before the communication device 12 discards at least some of the retransmission data included in the buffered data 18. In some embodiments, the delay status report 20 further includes a buffer size field 20A that indicates the amount 18A of the buffered data 18, and a remaining time field 20B configurable to have any one of multiple possible values 21. In some embodiments, the multiple possible values 21 include at least one or more possible values 21 that respectively indicate one or more possible non-zero durations of time remaining before the communication device 12 discards at least some of the buffered data 18 whose amount 18A is indicated by the buffer size field 20A.

[0109] In some embodiments, the delay status report 20 indicates the buffered data 18 includes only first and / or second types 18T-1, 18T-2 of data. In some embodiments, the delay status report 20 includes a first field configurable to indicate an amount 18A of the first type of data included in the buffered data 18. In other embodiments, the delay status report 20 alternatively or additionally includes a second field configurable to indicate an amount 18A of the second type of data included in the buffered data 18. In some embodiments, the delay status report 20 indicates the buffered data 18 includes only the first and second types of data. In some embodiments, the delay status report 20 includes the first field and the second field. In some embodiments, the first field is a remaining time field 20B; if the delay status report 20 does not indicate the buffered data 18 includes only the first and / or secondtypes 18T-1, 18T-2 of data, the remaining time field 20B indicates a non-zero duration of time remaining before the communication device 12 discards at least some of the buffered data 18; and if the delay status report 20 indicates the buffered data 18 includes only the first and / or second types 18T-1 , 18T-2 of data, the remaining time field 20B indicates an amount 18A of the first type of data included in the buffered data 18. In some embodiments, the second field is a buffer size field 20A; if the delay status report 20 does not indicate the buffered data 18 includes only the first and / or second types 18T-1, 18T-2 of data, the buffer size field 20A indicates a total amount 18A of the buffered data 18; and if the delay status report 20 indicates the buffered data 18 includes only the first and / or second types 18T-1 , 18T-2 of data, the buffer size field 20A indicates an amount 18A of the second type of data included in the buffered data 18; (optional: the delay status report 20 further includes a remaining time field 20B that indicates a non-zero duration of time remaining before the communication device 12 discards at least some of the second type of data). In some embodiments, the first type of data is control data. In some embodiments, the second type of data is retransmission data. In some embodiments, the buffered data 18 is data buffered for a first logical channel group 23-1 among one or more logical channel groups 23. In some embodiments, the buffered data 18 is data buffered across multiple logical channel groups 23.

[0110] In some embodiments, the delay status report 20 indicates the amount 18A of buffered data 18 across multiple logical channel groups 23, and indicates which one or more types 18T of data are, or are not, included in the buffered data 18 across the multiple logical channel groups 23.

[0111] In some embodiments, the delay status report 20 indicates the amount 18A of buffered data 18 not associated with any of multiple logical channel groups 23, and indicates which one or more types 18T of data are, or are not, included in the buffered data 18 not associated with any of the multiple logical channel groups 23.

[0112] In some embodiments, the delay status report 20 indicates the amount 18A of the buffered data 18 as a total amount of delay-reporting data. In other embodiments, the delay status report 20 indicates the amount 18A of the buffered data 18 as a total amount of delayreporting data and non-delay-reporting data. In some embodiments, delay-critical data, control data, and retransmission data are, or are considered to be, delay-reporting data. In other embodiments, alternatively or additionally, non-delay-reporting data comprises buffered data 18 that is not delay-reporting data, is not considered to be delay-reporting data, and is ahead of at least some delay-reporting data in a transmission sequence.

[0113] In some embodiments, the delay status report 20 is a multi-threshold or multi-entry report that is configurable to report, for each of one or more logical channel groups 23, delay information 27 for buffered data 18 associated with each of multiple reporting thresholds 25of the logical channel group 23. In some embodiments, the delay status report 20 is configurable to include multiple sets of fields for each of the one or more logical channel groups 23. In some embodiments, the multiple sets of fields for a logical channel group 23 include one set of fields for each respective one of the multiple reporting thresholds 25 of the logical channel group 23. In some embodiments, a set of fields for a reporting threshold of a logical channel group 23 includes at least a buffer size field 20A configurable to have a value that indicates an amount 18A of buffered data 18 associated with the reporting threshold of the logical channel group 23, and a remaining time field 20B configurable to have one of multiple possible values 21. In some embodiments, the multiple possible values 21 include at least one or more possible values 21 that respectively indicate one or more possible nonzero durations of time remaining before the communication device 12 discards at least some of the buffered data 18 whose amount 18A is indicated by the buffer size field 20A.

[0114] In some embodiments, the buffered data 18 includes Packet Data Convergence Protocol, PDCP, data or Radio Link Control, RLC, data.

[0115] In some embodiments, the buffered data 18 includes uplink data available to a Medium Access Control, MAC, entity of the communication device 12. In some embodiments, the buffered data 18 includes one or more Protocol Data Units, PDUs, received by the MAC entity on one or more logical channels.

[0116] In some embodiments, control data comprises one or more PDCP Control PDUs. In some embodiments, retransmission data includes for Acknowledged Mode, AM, Data Radio Bearers, DRBs, PDCP Service Data Units, SDUs, to be retransmitted. In other embodiments, retransmission data includes, alternatively or additionally, for AM DRBs, PDCP Data PDUs to be retransmitted.

[0117] In some embodiments, control data comprises one or more Radio Link Control, RLC, Control PDUs.

[0118] In some embodiments, retransmission data includes, for AM DRBs, RLC Data PDUs pending for retransmission.

[0119] In some embodiments, the method further comprises triggering the delay status report 20 based on a remaining time before discard of at least some of the buffered data 18 being below a reporting threshold (Block 710).

[0120] In some embodiments, the delay status report 20 is transmitted to a radio network node 14 of a communication network 10.

[0121] Figure 8 depicts a method performed by a radio network node 14 of a communication network 10 in accordance with other particular embodiments. The method includes receiving, from a communication device 12, a delay status report 20 that indicates an amount 18A of buffered data 18 at the communication device 12 and that indicates whichone or more types 18T of data are, or are not, included in the buffered data 18 whose amount 18A is indicated (Block 800).

[0122] In some embodiments, the method comprises any of the steps described above for a communication device 12.

[0123] In some embodiments, the method further comprises performing scheduling based on the received delay status report 20 (Block 810).

[0124] Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0125] Embodiments also include a communication device 12 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 device 12. The power supply circuitry is configured to supply power to the communication device 12.

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

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

[0128] 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 device 12. 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 output information 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.

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

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

[0131] Embodiments further include a network node 14 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 14. In some embodiments, the network node 14 further comprises communication circuitry.

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

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

[0134] Figure 9 for example illustrates a communication device 12 as implemented in accordance with one or more embodiments. As shown, the communication device 12 includes processing circuitry 910 and communication circuitry 920. The communication circuitry 920 (e.g., radio circuitry) is configured to transmit and / or receive information to and / 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 device 12. The processing circuitry 910 is configured to perform processing described above, e.g., in Figure 7, such as by executing instructions stored in memory 930. The processing circuitry 910 in this regard may implement certain functional means, units, or modules.Figure 10 illustrates a network node 14 as implemented in accordance with one or more embodiments. As shown, the network node 14 includes processing circuitry 1010 and communication circuitry 1020. The communication circuitry 1020 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 1010 is configured to perform processing described above, e.g., in Figure 8, such as by executing instructions stored in memory 1030. The processing circuitry 1010 in this regard may implement certain functional means, units, or modules.

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

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

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

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

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

[0140] Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.

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

[0142] 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 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1102 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 1102, including one or more access network nodes 1110 and / or core network nodes 1108.

[0143] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). 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.

[0144] The network nodes 1110 facilitate direct or indirect connection of one or more UEs 1112 to the core network 1106 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 of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 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 1100 mayinclude and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0145] The UEs 1112 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 1110 and other communication devices. Similarly, the network nodes 1108, 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1102) with the UEs 1112 and / or with other network nodes or equipment in the telecommunications network 1102 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 1102. More specifically, UEs 1112 may send messages, data, and / or other signals to network nodes 1108, 1110 or other elements of the telecommunications network 1102 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 1108, 1110 may send messages, data, and other signals to UEs 11122, other network nodes 1108, 1110, and other devices in telecommunications network 1102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1112 by transmitting the message to an access network node 1110 that will then transmit the message to the intended UE 1112. Similarly, a core network node 108 may receive a particular message from a UE 1112 by receiving the message from an access network node 1110 that itself received the message from the UE 1112.

[0146] In the depicted example, the core network 1106 connects elements of the access network 1104 (e.g., one or more of the network nodes 1110) to one or more host computing systems, such as host 1116. 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 1106 includes one or more core network nodes (e.g., core network node 1108) of various types, one or more of which may be generally referred to as network nodes 1108. Network nodes 1108 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 descriptions thereof are generally applicable to the corresponding components of the core network node 1108. 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 (AUSF), 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).

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

[0148] As a whole, the communication system 1100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1100 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 1100 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 1100 supporting different standards, protocols, or rule sets.

[0149] As one example, in certain embodiments, access network 1104 may contain some access network nodes 1110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1110 support (or the same access network nodes 1110 additionally support) non-3GPP RATs, such as Wi-Fi ora proprietary RAT. As another example, telecommunications network 1102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a 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.Telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1102. For example, the telecommunications network 1102 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.

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

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

[0152] As another example, the hub 1114 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 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0153] The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110B. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g., UE 1112C and / or 1112D), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 isconnected to the core network 1106 and / or one or more UEs via a wired connection.

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

[0155] Figure 12 is another example of a communication system 1200 according to some embodiments. As used herein, the communication system 1200 includes multiple access points (APs) 1210 (with four exemplary APs 1210A, 1210B, 1210C, and 1210D being depicted) and multiple wireless devices, referred to in the context of communication system 1200 as stations (STAs) 1212 (referred to individually as STA 1212A, STA 1212B, STA 1212C, STA 1212D, and STA 1212E). STA 1212A is served by AP 1210A in a first basic service set (BSS) 1220A. STA 1210B and STA 1210C are served by AP 1210B in a second BSS, BSS 1220B. STA 1212D is served by AP 1210C in a third BSS, BSS 1220C. STA 1212E is served by AP 1210D in a fourth BSS, BSS 1220D. Stations 1212 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 1212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0156] Each of STAs 1212 may connect through a radio link to one of APs 1210. For example, depending on location or channel conditions experienced by a given STA 1212, 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.

[0157] Each AP 1210 may provide data connectivity to STAs 1212 connected to a particular AP 1210. As illustrated, APs 1210 may be connected to a data network 1230. In this way, APs 1210 may also provide data connectivity between STAs 1212 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 1212 and its serving AP 1210may be used for providing various kinds of services to STA 1212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1212 and / or on a device linked to STA 1212. By way of example, Figure 12 illustrates an application service platform 1232 provided in data network 1230. The application(s) executed on STA 1212 and / or on one or more other devices linked to STA 1212 may use the radio link for data communication with one or more other STA 1212 and / or the application service platform 1232, thereby enabling utilization of the corresponding service(s) at STA 1212.

[0158] Figure 13 shows a wireless device 1300, which may be configured to operate in communication system 1100 of Figure 11 or in communication system 1200 of Figure 120. The wireless device 1300 may be alternatively referred to as a UE 1300, like a UE 1112 within the context of communication system 1100, or as a station (STA) 1300 or as a non-access-point station (non-AP STA) 1300, like a STA 1212 within the context of the communication system 1200, 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.

[0159] A wireless device 1300 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 1300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1300 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).In particular embodiments, wireless device 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1300 may include all or a subset of the components shown in Figure 13. The level of integration between the components may vary from one embodiment of wireless device 1300 to another. In general, in a particular embodiment of wireless device 1300, processing circuitry 1302, input / output interface 1306, power source 1308, memory 1310, and communication interface 1312 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 1300. Further, certain embodiments of wireless devices 1300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0160] The processing circuitry 1302 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 1310. The processing circuitry 1302 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 1302 may include multiple central processing units (CPUs).

[0161] In the example, the input / output interface 1306 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 1300. 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, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.In some embodiments, the power source 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and / or an external power source, to the various parts of wireless device 1300 via input circuitry or an interface such as an electrical power cable. Power source 1308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1300 to which power is supplied.

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

[0163] The memory 1310 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 1310 may allow wireless device 1300 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 1310, which may be or comprise a device-readable storage medium.

[0164] The processing circuitry 1302 may be configured to communicate with an access network or other network via or using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 mayinclude 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 1318 and / or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0165] In the illustrated embodiment, communication functions of the communication interface 1312 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.

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

[0167] As another example, wireless device 1300 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 1300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.Wireless device 1300, 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 1300 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 1300 shown in Figure 13.

[0168] As yet another specific example, in an loT scenario, wireless device 1300 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 1300 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 1300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 1300 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.

[0169] In practice, any number of wireless devices 1300 may be used together with respect to a single use case. For example, a first wireless device 1300 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 1300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1300 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 1300 can also include more than one of the functionalities described above. For example, wireless device 1300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Figure 14 shows a network node 1400 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 1400 may be configured to operate in communication system 1100 of Figure 11, like network nodes 1108 or 1110, or in communication system 1200 of Figure 12, like an AP 1210 or a station 1212. 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).

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

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

[0172] In particular embodiments, network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. In general, in a particular embodiment of network node 1400, processing circuitry 1402, memory 1404, communication interface 1406, and power source 1408 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 1400.

[0173] The network node 1400 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 thenetwork node 1400 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 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1404 or portions of memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, 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 1400.

[0174] The processing circuitry 1402 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 1404, to provide network node 1400 functionality.

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

[0176] The memory 1404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1402. The memory 1404 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 beingexecuted by the processing circuitry 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and / or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated.

[0177] The communication interface 1406 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 1406 comprises port(s) / terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1300 may be capable of wireless communication and communication interface 1406 may also include radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, an antenna 1410. Particular embodiments of radio front-end circuitry 1418 include filter(s) 1420 and amplifier(s) 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 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 1418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1420 and / or amplifiers 1422. The radio signal(s) may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0178] In certain alternative embodiments, network node 1400 may be capable of wireless communication but does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

[0179] The antenna 1410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1410 isseparate from the network node 1400 and connectable to the network node 1400 through one or more interfaces or ports.

[0180] The antenna 1410, communication interface 1406, and / or the processing circuitry 1402 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 1400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1410, the communication interface 1406, and / or the processing circuitry 1402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

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

[0183] Figure 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may beimplemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 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 1500 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.

[0184] Applications 1502 (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.

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

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

[0187] In the context of NFV, each of the VMs 1508 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 1508, and that part of hardware 1504 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 1508 on top of the hardware 1504 and corresponds to an application 1502.Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 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 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 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 1512 which may alternatively be used for communication between hardware nodes and radio units.

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

[0189] 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 maybe 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.

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

[0191] Group A Embodiments

[0192] A1. A method performed by a communication device, the method comprising:

[0193] transmitting a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0194] A2. The method of embodiment A1 , wherein the delay status report indicates that the buffered data whose amount is indicated includes only one or more first types of data and / or excludes one or more second types of data.

[0195] A3. The method of embodiment A2, wherein the delay status report indicates that the buffered data whose amount is indicated includes only one or more first types of data, wherein the one or more first types of data include:

[0196] control data; and / or

[0197] retransmission data.

[0198] A4. The method of embodiment A2, wherein the delay status report indicates that the buffered data whose amount is indicated excludes one or more second types of data, wherein the one or more second types of data include delay-critical data.

[0199] A5. The method of any of embodiments A1-A4, wherein the delay status report indicates the amount of buffered data for a first logical channel group, and indicates which one or more types of data are, or are not, included in the buffered data for the first logical channel group.

[0200] A6. The method of any of embodiments A1-A5, wherein the delay status report indicates the amount of buffered data associated with a first reporting threshold of a first logical channel group, and indicates which one or more types of data are, or are not, included in thebuffered data associated with the first reporting threshold of the first logical channel group.

[0201] A7. The method of embodiment A6, wherein the first reporting threshold is a lowest reporting threshold amongst multiple reporting thresholds of the logical channel group.

[0202] A8. The method of any of embodiments A6-A7, wherein no delay-critical data is associated with the first reporting threshold of the first logical channel group.

[0203] A9. The method of any of embodiments A6-A7, wherein no delay-critical data is associated with any of multiple reporting thresholds of the first logical channel group.

[0204] A10. The method of any of embodiments A1-A9, wherein the delay status report includes at least a buffer size field and a remaining time field, wherein the buffer size field has a value that indicates the amount of the buffered data, wherein the remaining time field is configurable to have any one of multiple possible values, wherein the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field, and wherein the delay status report indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field.

[0205] A11. The method of embodiment A10, wherein the remaining time field is configurable to indicate which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field.

[0206] A12. The method of embodiment A11, wherein the multiple possible values of the remaining time field further include a reserved value that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the buffer size field, wherein the remaining time field in the transmitted delay status report has the reserved value.

[0207] A13. The method of embodiment A12, wherein the reserved value indicates that the buffered data whose amount is indicated by the buffer size field:

[0208] includes only control data; or

[0209] includes only retransmission data; or

[0210] includes only data that is either control data, retransmission data, or a combination thereof; ordoes not include any delay-critical data.

[0211] A14. The method of any of embodiments A12-A13, wherein the reserved value is 0.

[0212] A15. The method of any of embodiments A12-A14, wherein the reserved value is a lowest value possible for the remaining time field.

[0213] A16. The method of any of embodiments A10-A5, wherein the buffer size field is a first buffer size field and the remaining time field is a first remaining time field, wherein the first buffer size field and the first remaining time field are associated with:

[0214] a first logical channel group amongst one or more logical channel groups at the communication device; and

[0215] a first reporting threshold included amongst multiple reporting thresholds of the first logical channel group.

[0216] A17. The method of embodiment A16, wherein the value of the first buffer size field indicates an amount of buffered data that is:

[0217] for the first logical channel group; and / or

[0218] associated with the first reporting threshold.

[0219] A18. The method of any of embodiments A16-A17, wherein the first reporting threshold is a lowest reporting threshold amongst the multiple reporting thresholds.

[0220] A19. The method of any of embodiments A16-A18, wherein no delay-critical data is associated with the first reporting threshold of the first logical channel group.

[0221] A20. The method of embodiment A19, wherein:

[0222] if at least some delay-critical data is associated with the first reporting threshold of the first logical channel group, the first remaining time field is to have any one of the one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards the delay-critical data included in the buffered data whose amount is indicated by the first buffer size field; and

[0223] if no delay-critical data is associated with the first reporting threshold of the first logical channel group, the first remaining time field is to have the reserved value to indicate which one or more types of data are, or are not, included in the buffered data whose amount is indicated by the first buffer size field.A21. The method of any of embodiments A16-A18, wherein no delay-critical data is associated with any of the multiple reporting thresholds of the first logical channel group.

[0224] A22. The method of any of embodiments A1-A9, wherein the delay status report includes a subset of one or more fields that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0225] A23. The method of embodiment A22, wherein the delay status report is a 3GPP Release 19+ delay status report, and wherein at least one of the one or more fields in the subset is a Reserved Bit of a 3GPP Release 18 delay status report.

[0226] A24. The method of any of embodiments A22-A23, wherein at least one of the one or more fields in the subset is a field dedicated for indicating which one or more types of data are, or are not, included in the buffered data.

[0227] A25. The method of any of embodiments A22-A23, wherein at least one of the one or more fields in the subset is a field dedicated for indicating whether, or that, the buffered data includes only control and / or retransmission data.

[0228] A26. The method of any of embodiments A22-A25, wherein at least one of the one or more fields in the subset is a field which indicates that the buffered data includes only control and / or retransmission data.

[0229] A27. The method of embodiment A26, wherein the delay status report indicates a non-zero duration of time remaining before the communication device discards at least some of the retransmission data included in the buffered data whose amount is indicated.

[0230] A28. The method of any of embodiments A22-A27, wherein the subset is included in a set of fields that is associated with:

[0231] a first logical channel group amongst one or more logical channel groups at the communication device; and

[0232] a first reporting threshold included amongst multiple reporting thresholds of the first logical channel group.

[0233] A29. The method of any of embodiments A22-A28, wherein at least one of the one or more fields in the subset is a length field indicating a length of the delay status report.A30. The method of any of embodiments A22-A29, wherein at least one of the one or more fields in the subset is a field configurable to have any one of multiple possible values, wherein the multiple possible values include:

[0234] a first value that indicates presence of delay information in the delay status report for a first logical channel group amongst one or more logical channel groups at the communication device; and

[0235] a second value that indicates the buffered data includes only one or more first types of data and / or excludes one or more second types of data.

[0236] A31. The method of embodiment A30, wherein said field has the second value in the transmitted delay status report.

[0237] A32. The method of any of embodiments A30-A31 , wherein the first value is 1 and the second value is 0.

[0238] A33. The method of any of embodiments A30-A32, wherein said field is an LCGt field, wherein the first logical channel group is a logical channel group that has a lowest index i in the delay status report amongst any of the one or more logical channel groups.

[0239] A34. The method of any of embodiments A30-A33, wherein no delay-reporting data is associated with any of the one or more logical channel groups, e.g., no delay-reporting PDCP SDlls or PDCP Data PDlls that contain the delay-reporting PDCP SDlls.

[0240] A35. The method of any of embodiments A30-A34, wherein said field has the second value in the transmitted delay status report and indicates the buffered data includes only the one or more first types of data, wherein the one or more first types of data include control data and / or retransmission data.

[0241] A36. The method of embodiment A35, wherein the delay status report indicates a non-zero duration of time remaining before the communication device discards at least some of the retransmission data included in the buffered data.

[0242] A37. The method of any of embodiments A22-A36, wherein the delay status report further includes:

[0243] a buffer size field that indicates the amount of the buffered data; and

[0244] a remaining time field configurable to have any one of multiple possible values,wherein the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field.

[0245] A38. The method of any of embodiments A1-A36, wherein the delay status report indicates the buffered data includes only first and / or second types of data, wherein the delay status report includes:

[0246] a first field configurable to indicate an amount of the first type of data included in the buffered data; and / or

[0247] a second field configurable to indicate an amount of the second type of data included in the buffered data.

[0248] A39. The method of embodiment A38, wherein the delay status report indicates the buffered data includes only the first and second types of data, wherein the delay status report includes the first field and the second field.

[0249] A40. The method of any of embodiments A38-A39, wherein:

[0250] the first field is a remaining time field,

[0251] if the delay status report does not indicate the buffered data includes only the first and / or second types of data, the remaining time field indicates a non-zero duration of time remaining before the communication device discards at least some of the buffered data; and

[0252] if the delay status report indicates the buffered data includes only the first and / or second types of data, the remaining time field indicates an amount of the first type of data included in the buffered data.

[0253] A41. The method of any of embodiments A39-A40, wherein:

[0254] the second field is a buffer size field,

[0255] if the delay status report does not indicate the buffered data includes only the first and / or second types of data, the buffer size field indicates a total amount of the buffered data; and

[0256] if the delay status report indicates the buffered data includes only the first and / or second types of data, the buffer size field indicates an amount of the second type of data included in the buffered data;

[0257] (optional: the delay status report further includes a remaining time field that indicates a non-zero duration of time remaining before the communication devicediscards at least some of the second type of data).

[0258] A42. The method of any of embodiments A38-A41 , wherein the first type of data is control data.

[0259] A43. The method of any of embodiments A38-A42, wherein the second type of data is retransmission data.

[0260] A44. The method of any of embodiments A38-A43, wherein the buffered data is data buffered for a first logical channel group among one or more logical channel groups.

[0261] A45. The method of any of embodiments A38-A43, wherein the buffered data is data buffered across multiple logical channel groups.

[0262] A46. The method of any of embodiments A1-A45, wherein the delay status report indicates the amount of buffered data across multiple logical channel groups, and indicates which one or more types of data are, or are not, included in the buffered data across the multiple logical channel groups.

[0263] A47. The method of any of embodiments A1-A46, wherein the delay status report indicates the amount of buffered data not associated with any of multiple logical channel groups, and indicates which one or more types of data are, or are not, included in the buffered data not associated with any of the multiple logical channel groups.

[0264] A48. The method of embodiment A6, wherein the delay status report indicates the amount of the buffered data as:

[0265] a total amount of delay-reporting data; or

[0266] a total amount of delay-reporting data and non-delay-reporting data.

[0267] A49. The method of embodiment A48, wherein:

[0268] delay-critical data, control data, and retransmission data are, or are considered to be, delay-reporting data; and / or

[0269] non-delay-reporting data comprises buffered data that is not delay-reporting data, is not considered to be delay-reporting data, and is ahead of at least some delay-reporting data in a transmission sequence.

[0270] A50. The method of any of embodiments A1-A49, wherein the delay status report is a multi-threshold or multi-entry report that is configurable to report, for each of one or more logical channel groups, delay information for buffered data associated with each of multiple reporting thresholds of the logical channel group.

[0271] A51. The method of embodiment A50, wherein the delay status report is configurable to include multiple sets of fields for each of the one or more logical channel groups, wherein the multiple sets of fields for a logical channel group include one set of fields for each respective one of the multiple reporting thresholds of the logical channel group, wherein a set of fields for a reporting threshold of a logical channel group includes at least:

[0272] a buffer size field configurable to have a value that indicates an amount of buffered data associated with the reporting threshold of the logical channel group; and a remaining time field configurable to have one of multiple possible values, wherein the multiple possible values include at least one or more possible values that respectively indicate one or more possible non-zero durations of time remaining before the communication device discards at least some of the buffered data whose amount is indicated by the buffer size field.

[0273] A52. The method of any of embodiments A1-A51 , wherein the buffered data includes Packet Data Convergence Protocol, PDCP, data or Radio Link Control, RLC, data.

[0274] A53. The method of any of embodiments A1-A52, wherein the buffered data includes uplink data available to a Medium Access Control, MAC, entity of the communication device.

[0275] A54. The method of embodiment A53, wherein the buffered data includes one or more Protocol Data Units, PDUs, received by the MAC entity on one or more logical channels.

[0276] A55. The method of any of embodiments A1-A54, wherein control data comprises one or more PDCP Control PDUs.

[0277] A56. The method of any of embodiments A1-A55, wherein retransmission data includes: for Acknowledged Mode, AM, Data Radio Bearers, DRBs, PDCP Service Data Units, SDUs, to be retransmitted; and / or

[0278] for AM DRBs, PDCP Data PDUs to be retransmitted.

[0279] A57. The method of any of embodiments A1-A56, wherein control data comprises one or more Radio Link Control, RLC, Control PDUs.A58. The method of any of embodiments A1-A57, wherein retransmission data includes, for AM DRBs, RLC Data PDlls pending for retransmission.

[0280] A59. The method of any of embodiments A1-A58, further comprising triggering the delay status report based on a remaining time before discard of at least some of the buffered data being below a reporting threshold.

[0281] A60. The method of any of embodiments A1-A59, wherein the delay status report is transmitted to a radio network node of a communication network.

[0282] Group B Embodiments

[0283] B1. A method performed by a radio network node of a communication network, the method comprising:

[0284] receiving, from a communication device, a delay status report that indicates an amount of buffered data at the communication device and that indicates which one or more types of data are, or are not, included in the buffered data whose amount is indicated.

[0285] B2. The method of embodiment B1 , comprising any step of any of embodiments A2-A58.

[0286] B3. The method of any of embodiments B1-B2, further comprising performing scheduling based on the received delay status report.

[0287] Group C Embodiments

[0288] C1. A communication device configured to perform any of the steps of any of the Group A embodiments.

[0289] 02. A communication device comprising processing circuitry configured to any of the steps of any of the Group A embodiments.

[0290] 03. A communication device comprising:

[0291] communication circuitry; and

[0292] processing circuitry configured to perform any of the steps of any of the Group A embodiments.

[0293] 04. A communication device comprising:

[0294] processing circuitry configured to perform any of the steps of any of the Group Aembodiments; and

[0295] power supply circuitry configured to supply power to the communication device.

[0296] C5. A communication device comprising:

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

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

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

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

[0301] 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;

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

[0303] 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

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

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

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

[0307] 010. A network node configured to perform any of the steps of any of the Group B embodiments.C11. A network node comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0308] C12. A network node comprising:

[0309] communication circuitry; and

[0310] processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0311] C13. A network node comprising:

[0312] processing circuitry configured to perform any of the steps of any of the Group B embodiments;

[0313] power supply circuitry configured to supply power to the network node.

[0314] C14. A network node comprising:

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

[0316] C15. The network node of any of embodiments C10-C14, wherein the network node is a base station.

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

[0318] 017. The computer program of embodiment 016, wherein the network node is a base station.

[0319] 018. A carrier containing the computer program of any of embodiments 016-017, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0320] ABBREVIATIONS

[0321] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).5GC 5G Core Network

[0322] XR extended Reality

[0323] MAC CE MAC Control Element

[0324] DRB Data Radio Bearer

[0325] LCH Logical Channel

[0326] LCG Logical Channel Group

[0327] UE User Equipment3GPP 3rd Generation Partnership Project 5G 5th Generation

[0328] 6G 6thGeneration

[0329] ABS Almost Blank Subframe

[0330] ARQ Automatic Repeat Request

[0331] AWGN Additive White Gaussian Noise

[0332] BCCH Broadcast Control Channel

[0333] BCH Broadcast Channel

[0334] CA Carrier Aggregation

[0335] CC Carrier Component

[0336] CCCH SDU Common Control Channel SDU

[0337] CDMA Code Division Multiplex Access

[0338] CGI Cell Global Identity

[0339] CIR Channel Impulse Response

[0340] CP Cyclic Prefix

[0341] CPICH Common Pilot Channel

[0342] CQI Channel Quality Information

[0343] C-RNTI Cell RNTI

[0344] CSI Channel State Information

[0345] DCCH Dedicated Control Channel

[0346] DL Downlink

[0347] DM Demodulation

[0348] DMRS Demodulation Reference Signal

[0349] DRX Discontinuous Reception

[0350] DTX Discontinuous Transmission

[0351] DTCH Dedicated Traffic Channel

[0352] DUT Device Under Test

[0353] E-CID Enhanced Cell-ID (positioning method)

[0354] Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast Services

[0355] ECGI Evolved CGI

[0356] eNB E-UTRAN NodeB

[0357] ePDCCH Enhanced Physical Downlink Control Channel

[0358] E-SMLC Evolved Serving Mobile Location Center

[0359] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0360] FDD Frequency Division Duplex

[0361] FFS For Further Study

[0362] gNB Base station in NR

[0363] GNSS Global Navigation Satellite System

[0364] HARQ Hybrid Automatic Repeat Request

[0365] HO Handover

[0366] HSPA High Speed Packet Access

[0367] HRPD High Rate Packet Data

[0368] LOS Line of Sight

[0369] LPP LTE Positioning Protocol

[0370] LTE Long-Term Evolution

[0371] MAC Medium Access Control

[0372] MAC Message Authentication Code

[0373] MBSFN Multimedia Broadcast Multicast Service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests

[0374] MIB Master Information Block

[0375] MME Mobility Management Entity

[0376] MSC Mobile Switching Center

[0377] NPDCCH Narrowband Physical Downlink Control Channel NR New Radio

[0378] OCNG OFDMA Channel Noise Generator

[0379] OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System

[0380] OTDOA Observed Time Difference of Arrival

[0381] O&M Operation and Maintenance

[0382] PBCH Physical Broadcast Channel

[0383] P-CCPCH Primary Common Control Physical Channel PCell Primary Cell

[0384] PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel

[0385] PDCP Packet Data Convergence Protocol

[0386] PDP Power Delay Profile

[0387] PDSCH Physical Downlink Shared Channel

[0388] PGW Packet Gateway

[0389] PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network

[0390] PMI Precoding Matrix Indicator

[0391] PRACH Physical Random Access Channel

[0392] PRS Positioning Reference Signal

[0393] PSS Primary Synchronization Signal

[0394] PUCCH Physical Uplink Control Channel

[0395] PUSCH Physical Uplink Shared Channel

[0396] RACH Random Access Channel

[0397] QAM Quadrature Amplitude Modulation

[0398] RAN Radio Access Network

[0399] RAT Radio Access Technology

[0400] RLC Radio Link Control

[0401] RLM Radio Link Monitoring

[0402] RNC Radio Network Controller

[0403] RNTI Radio Network Temporary Identifier

[0404] RRC Radio Resource Control

[0405] RRM Radio Resource Management

[0406] RS Reference Signal

[0407] RSCP Received Signal Code Power

[0408] RSRP Reference Symbol Received Power OR Reference Signal Received Power

[0409] RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

[0410] RSSI Received Signal Strength Indicator

[0411] RSTD Reference Signal Time Difference

[0412] SCH Synchronization Channel

[0413] SCell Secondary Cell

[0414] SDAP Service Data Adaptation Protocol

[0415] SDU Service Data Unit

[0416] SFN System Frame Number

[0417] SGW Serving Gateway

[0418] SI System InformationSIB System Information Block

[0419] SNR Signal to Noise Ratio

[0420] SON Self-Organizing Network

[0421] SS Synchronization Signal

[0422] SSS Secondary Synchronization Signal TDD Time Division Duplex

[0423] TDOA Time Difference of Arrival

[0424] TOA Time of Arrival

[0425] TSS Tertiary Synchronization Signal

[0426] TTI Transmission Time Interval

[0427] UE User Equipment

[0428] UL Uplink

[0429] UMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wideband CDMA

[0430] WLAN Wireless Local Area Network

Claims

CLAIMS1. A method performed by a communication device (12) configured for use in a communication network (10), the method comprising:transmitting (700) a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.

2. The method of claim 1 , wherein the delay status report (20) is configurable to indicate that the buffered data (18) whose amount (18A) is indicated includes only one or more first types (18T-1) of data.

3. The method of any of claims 1-2, wherein the delay status report (20) indicates the amount (18A) of buffered data (18) associated with a first reporting threshold (25-1) of a first logical channel group (23-1), and indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) associated with the first reporting threshold (25-1) of the first logical channel group (23-1).

4. The method of any of claims 1-3, wherein the delay status report (20) includes at least a buffer size field (20A) and a remaining time field (20B), wherein the buffer size field (20A) has a value that indicates the amount (18A) of the buffered data (18), wherein the remaining time field (20B) is configurable to have any one of multiple possible values (21), wherein the multiple possible values (21) include at least one or more possible values (21) that respectively indicate one or more possible non-zero durations of time remaining before the communication device (12) discards at least some of the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A), and wherein the remaining time field (20B) is configurable to indicate which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A).

5. The method of claim 4, wherein the multiple possible values (21) of the remaining time field (20B) further include a zero value, wherein the remaining time field (20B) being set to the zero value indicates that the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A) includes only one or more first types (18T-1) of data.

6. The method of any of claims 1-5, wherein the delay status report (20) is a multi-entry report that is configurable to report, for each of one or more logical channel groups (23),58delay information (27) for buffered data (18) associated with each of multiple reporting thresholds (25) of the logical channel group (23).

7. The method of claim 6, wherein, for each of the one or more logical channel groups (23), the delay status report (20) indicates the amount (18A) of buffered data (18) associated with a first reporting threshold (25-1) of the logical channel group (23), and indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) associated with the first reporting threshold (25-1) of the logical channel group (23).

8. The method of any of claims 6-7, wherein the delay status report (20) is configurable to include multiple sets of fields for each of the one or more logical channel groups (23), wherein the multiple sets of fields for a logical channel group (23) include one set of fields for each respective one of the multiple reporting thresholds (25) of the logical channel group (23), wherein a set of fields for a reporting threshold of a logical channel group (23) includes at least:a buffer size field (20A) configurable to have a value that indicates an amount (18A) of buffered data (18) associated with the reporting threshold of the logical channel group (23); anda remaining time field (20B) configurable to have one of multiple possible values (21), wherein the multiple possible values (21) include at least one or more possible values (21) that respectively indicate one or more possible non-zero durations of time remaining before the communication device (12) discards at least some of the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A).

9. The method of claim 8, wherein the remaining time field (20B) included in the set of fields for a first reporting threshold (25-1) of a logical channel group (23) indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A) included in the set of fields for the first reporting threshold (25-1) of the logical channel group (23).

10. The method of claim 9, wherein the multiple possible values (21) of the remaining time field (20B) further include a zero value, wherein the remaining time field (20B) being set to the zero value indicates that the buffered data (18), whose amount (18A) is indicated by the buffer size field (20A) included in the set of fields for the first reporting threshold (25-1) of the logical channel group (23), includes only one or more first types (18T-1) of data.5911. The method of any of claims 1-10, wherein the delay status report (20) is a multi-entry report that is configurable to report, for each logical channel group / of one or more logical channel groups (23), delay information (27) for buffered data (18) associated with each reporting threshold j of multiple reporting thresholds (25) of the logical channel group (23), wherein the delay status report (20) is configurable to include, for each reporting threshold j of each logical channel group / :a buffer size field ij configurable to have a value that indicates an amount (18A) of buffered data (18) associated with the reporting threshold j of the logical channel group / ; anda remaining time field ij configurable to have a value that indicates a shortest remaining discard time among the buffered data (18) associated with the reporting threshold j of the logical channel group / ;wherein, for a first reporting threshold (25-1) J=1, the remaining time field ij is set to zero if only one or more first types (18T-1) of data are associated with the first reporting threshold (25-1) j=1 of the logical channel group / .

12. The method of any of claims 2, 5, 10, or 11, wherein the one or more first types (18T-1) of data include control data and / or retransmission data.

13. The method of claim 12, wherein:the control data includes one or more Packet Data Convergence Protocol, PDCP, Control Protocol Data Units, PDUs, or one or more Radio Link Control, RLC, Control PDUs; and / orthe retransmission data includes one or more PDCP Service Data Units, SDUs, to be retransmitted, or one or more RLC SDUs to be retransmitted.

14. The method of any of claims 1-13, further comprising triggering the delay status report (20) based on a remaining time before discard of at least some of the buffered data (18) being below a reporting threshold.

15. A method performed by a radio network node (14) of a communication network (10), the method comprising:receiving (800), from a communication device (12), a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.6016. The method of claim 15, wherein the delay status report (20) is configurable to indicate that the buffered data (18) whose amount (18A) is indicated includes only one or more first types (18T-1) of data.

17. The method of any of claims 15-16, wherein the delay status report (20) indicates the amount (18A) of buffered data (18) associated with a first reporting threshold (25-1) of a first logical channel group (23-1), and indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) associated with the first reporting threshold (25-1) of the first logical channel group (23-1).

18. The method of any of claims 15-17, wherein the delay status report (20) includes at least a buffer size field (20A) and a remaining time field (20B), wherein the buffer size field (20A) has a value that indicates the amount (18A) of the buffered data (18), wherein the remaining time field (20B) is configurable to have any one of multiple possible values (21), wherein the multiple possible values (21) include at least one or more possible values (21) that respectively indicate one or more possible non-zero durations of time remaining before the communication device (12) discards at least some of the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A), and wherein the remaining time field (20B) is configurable to indicate which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A).

19. The method of claim 18, wherein the multiple possible values (21) of the remaining time field (20B) further include a zero value, wherein the remaining time field (20B) being set to the zero value indicates that the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A) includes only one or more first types (18T-1) of data.

20. The method of any of claims 15-19, wherein the delay status report (20) is a multi-entry report that is configurable to report, for each of one or more logical channel groups (23), delay information (27) for buffered data (18) associated with each of multiple reporting thresholds (25) of the logical channel group (23).

21. The method of claim 20, wherein, for each of the one or more logical channel groups (23), the delay status report (20) indicates the amount (18A) of buffered data (18) associated with a first reporting threshold (25-1) of the logical channel group (23), and indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) associated with the first reporting threshold (25-1) of the logical channel group (23).6122. The method of any of claims 20-21, wherein the delay status report (20) is configurable to include multiple sets of fields for each of the one or more logical channel groups (23), wherein the multiple sets of fields for a logical channel group (23) include one set of fields for each respective one of the multiple reporting thresholds (25) of the logical channel group (23), wherein a set of fields for a reporting threshold of a logical channel group (23) includes at least:a buffer size field (20A) configurable to have a value that indicates an amount (18A) of buffered data (18) associated with the reporting threshold of the logical channel group (23); anda remaining time field (20B) configurable to have one of multiple possible values (21), wherein the multiple possible values (21) include at least one or more possible values (21) that respectively indicate one or more possible non-zero durations of time remaining before the communication device (12) discards at least some of the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A).

23. The method of claim 22, wherein the remaining time field (20B) included in the set of fields for a first reporting threshold (25-1) of a logical channel group (23) indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated by the buffer size field (20A) included in the set of fields for the first reporting threshold (25-1) of the logical channel group (23).

24. The method of claim 23, wherein the multiple possible values (21) of the remaining time field (20B) further include a zero value, wherein the remaining time field (20B) being set to the zero value indicates that the buffered data (18), whose amount (18A) is indicated by the buffer size field (20A) included in the set of fields for the first reporting threshold (25-1) of the logical channel group (23), includes only one or more first types (18T-1) of data.

25. The method of any of claims 15-24, wherein the delay status report (20) is a multi-entry report that is configurable to report, for each logical channel group / of one or more logical channel groups (23), delay information (27) for buffered data (18) associated with each reporting threshold j of multiple reporting thresholds (25) of the logical channel group (23), wherein the delay status report (20) is configurable to include, for each reporting threshold j of each logical channel group / :a buffer size field i,j configurable to have a value that indicates an amount (18A) of buffered data (18) associated with the reporting threshold j of the logical62channel group / ; anda remaining time field ij configurable to have a value that indicates a shortest remaining discard time among the buffered data (18) associated with the reporting threshold j of the logical channel group / ;wherein, for a first reporting threshold (25-1) J=1, the remaining time field ij is set to zero if only one or more first types (18T-1) of data are associated with the first reporting threshold (25-1) j=1 of the logical channel group / .

26. The method of any of claims 16, 19, 24, or 25, wherein the one or more first types (18T-1) of data include control data and / or retransmission data.

27. The method of claim 26, wherein:the control data includes one or more Packet Data Convergence Protocol, PDCP, Control Protocol Data Units, PDUs, or one or more Radio Link Control, RLC, Control PDUs; and / orthe retransmission data includes one or more PDCP Service Data Units, SDUs, to be retransmitted, or one or more RLC SDUs to be retransmitted.

28. The method of any of embodiments 15-27, further comprising performing scheduling based on the received delay status report (20).

29. A communication device (12) configured to:transmit a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.

30. The communication device (12) of claim 29, configured to perform the method of any of claims 2-14.

31. A radio network node (14) of a communication network (10), the radio network node (14) configured to:receive, from a communication device (12), a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.

32. The radio network node (14) of claim 31 , configured to perform the method of any of claims 16-28.

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

34. A computer program comprising instructions which, when executed by at least one processor of a communication device (12), causes the communication device (12) to perform the method of any of claims 15-28.

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

36. A communication device (12) comprising:communication circuitry; andprocessing circuitry configured to transmit a delay status report (20) that indicates an amount (18A) of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount (18A) is indicated.

37. The communication device (12) of claim 36, the processing circuitry configured to perform the method of any of claims 2-14.

38. A radio network node (14) of a communication network (10), the radio network node (14) comprising:communication circuitry; andprocessing circuitry configured to receive, from a communication device (12), a delay status report (20) that indicates an amount of buffered data (18) at the communication device (12) and that indicates which one or more types (18T) of data are, or are not, included in the buffered data (18) whose amount is indicated.

39. The radio network node (14) of claim 38, the processing circuitry configured to perform the method of any of claims 16-28.

Images