Techniques for buffer latency information reporting

By reporting buffer delay information in the cellular communication network by user equipment, the problem of lack of delay information in buffer status reporting in the prior art is solved, and the resource allocation efficiency and delay-aware scheduling performance for delay constraint services are improved.

CN118945718APending Publication Date: 2024-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410570379.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-09
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In existing cellular communication networks, the buffer status report (BSR) only provides buffer size information, lacking delay information, resulting in a reduced resource allocation efficiency for extended reality (XR) services with delay constraints, and the existing technology is difficult to be effective. Implement delay-aware scheduling.

Method used

User equipment (UE) can report buffer delay information, including delay information for data units in each logical channel or logical channel group, and provide more refined delay information through cumulative distribution functions (CDFs) and statistical parameters for the network to perform. More precise resource allocation and scheduling.

Benefits of technology

By providing detailed buffer delay information, the resource allocation efficiency for XR services is improved, resource waste is reduced, the performance of delay-aware scheduling is improved, and the network's support capability for delay-constrained services is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945718A_ABST
    Figure CN118945718A_ABST
Patent Text Reader

Abstract

The present application generally relates to techniques for buffer latency information reporting. The application relates to devices and components including apparatuses, systems, and methods for buffer status reporting in wireless networks.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to other applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 465,744, filed on May 11, 2023, entitled “TECHNOLOGIES FOR BUFFER DELAY INFORMATION REPORTING,” which is incorporated herein by reference in its entirety for all purposes. Technical Field

[0003] The present application relates generally to cellular communication networks, and in particular to techniques for uplink transmission without retransmission. Background Art

[0004] The present application relates generally to communication networks, and in particular to techniques for buffer status reporting in such networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A network environment according to some embodiments is shown.

[0006] Figure 2 Distribution diagrams according to some embodiments are shown.

[0007] Figure 3 A block diagram according to some embodiments is shown.

[0008] Figure 4 Data structures according to some embodiments are shown.

[0009] Figure 5 Data structures according to some embodiments are shown.

[0010] Figure 6 Data structures according to some embodiments are shown.

[0011] Figure 7 Data structures according to some embodiments are shown.

[0012] Figure 8 Data structures according to some embodiments are shown.

[0013] Fig. 9 An operational flow / algorithm structure according to some embodiments is shown.

[0014] Fig.10 An operational flow / algorithm structure according to some embodiments is shown.

[0015] Fig.11 An operational flow / algorithm structure according to some embodiments is shown.

[0016] Fig.12 A user device according to some embodiments is shown.

[0017] Fig.13 A network node according to some embodiments is shown. DETAILED DESCRIPTION

[0018] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details, such as specific structures, architectures, interfaces and / or technologies, are set forth to provide a thorough understanding of the various aspects of some embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that the various aspects of various aspects can be practiced in other examples that deviate from these specific details. In some cases, the description of well-known equipment, circuits and methods is omitted so that the description of various aspects will not be obscured by unnecessary details. For the purpose of this document, the phrase "A or B" refers to (A), (B) or (A and B), and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0019] The following is a glossary of terms that may be used in this disclosure.

[0020] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), and / or a digital signal processor (DSP). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0021] As used herein, the term "processor circuit" refers to, is a part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or a circuit that records, stores, or transmits digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0022] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0023] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio device, reconfigurable radio device, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0024] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0025] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computer, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computer, storage or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0026] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0027] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0028] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0029] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network device, network node, virtualized network function, etc.

[0030] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element that contains content. An information element may include one or more additional information elements.

[0031] Figure 1 A network environment 100 according to some embodiments is shown. The network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some embodiments, the BS 108 is a next generation node B (gNB) providing one or more 3GPP new radio (NR) cells. In other embodiments, the BS 108 is an evolved node B (eNB) providing one or more long term evolution (LTE) cells. The air interface via which the UE 104 and the BS 108 communicate may be compatible with 3GPP technical specifications (TS), such as those defining fifth generation (5G) NR or later system standards (e.g., sixth generation (6G) standards).

[0032] The UE 104 may send a buffer status report (BSR) to the base station 108 to indicate the amount of uplink data that the UE 104 has to transmit. The BSR may be transmitted as a medium access control (MAC) control element (CE) in a physical uplink shared channel (PUSCH). The BSR may be associated with a logical channel (LCH) or a logical channel group (LCG) having one or more LCHs. After receiving the BSR, the BS 108 may determine an appropriate amount of uplink (UL) resources for the UE 104. The BS 108 may then transmit an uplink grant to the UE 104. The UE 104 may use the UL grant for subsequent UL transmissions.

[0033] In various embodiments, the UE 104 may transmit a regular BSR, a periodic BSR, or a padding BSR. A regular BSR may be triggered when new uplink data for an LCH of an LCG becomes available in the MAC buffer and the LCH has a higher priority than any other LCH with buffered data, or no other LCH has buffered data. A regular BSR may also be triggered when a retransmission BSR timer (retxBSR-Timer) times out and the LCH includes buffered data to be transmitted. The retransmission BSR timer may be used to avoid a deadlock situation that may occur when the base station 108 fails to receive the BSR but the UE 104 believes that the BSR transmission was successful. Thus, the retransmission BSR timer provides a limited time period for the UE 104 to wait for an uplink grant before retransmitting the BSR. The retransmission BSR timer is started when the BSR is multiplexed into a MAC protocol data unit (PDU).

[0034] Existing networks include multiple BSR formats, including short BSR format (fixed size), extended short BSR format (fixed size), long BSR format (variable size), extended long BSR format (variable size), short truncated BSR format (fixed size), long truncated BSR format (variable size), and extended long truncated BSR format (variable size). The selection between these formats in existing networks is fixed in clause 5.4.5 of 3GPP TS 38.321v.17.4.02023-03-29. The selection may be based on the number of LCGs available for transmission, whether a logical channel group IAB extension (logicalChannelGroup-IAB-Ext) has been configured, and for padding BSR, the number of available padding bits compared to the size of the various formats.

[0035] Service types are evolving to accommodate new use cases in developing cellular networks. For example, efforts are underway to improve RAN operations to support services with features associated with extended reality (XR) services, providing, for example, high throughput, low latency, and high reliability. Various enhancements to BSR operations may be used to improve capacity for XR use cases. Although some embodiments are described with reference to XR services, other embodiments may apply similar concepts to other types of services.

[0036] BSR tables with finer granularity than existing tables can be used to enhance BSR for XR use cases. The existing BSR tables in 3GPP TS38.321 have quantization errors at the buffer size level, which increase with increasing buffer size levels. Since the packet size of XR services can be quite large (e.g., reference video frames), quantization errors can lead to degradation of resource efficiency.

[0037] XR services may operate based on PDU sets. A PDU set that may correspond to an application data unit may include multiple packets / PDUs. A user plane function (UPF) may identify a PDU set based on a PDU set sequence number (SN); the start / end PDU of a PDU set, a PDU SN within a PDU set, or multiple PDUs within a PDU set.

[0038] A Quality of Service (QoS) flow may be identified using a QoS flow ID, and each PDU set within a QoS flow may be identified using a PDU set SN. Each QoS flow may be used to transmit one or more PDU sets.

[0039] The UPF may further identify information related to the PDU set, such as the importance of the PDU set or dependencies thereon. The UPF may provide the information related to the PDU set to the RAN.

[0040] QoS parameters for PDU set-based QoS processing may include PDU set delay budget (PSDB), PDU set error rate (PSER), whether to discard the PDU set if the PSDB is exceeded, whether all PDUs are required for application layer use of the PDU set, and PDU set priority.

[0041] Characteristics of the buffered PDU sets (eg, importance level of the PDU sets) may be indicated in the BSR.

[0042] Different data units may be buffered in the buffer of an LCH or LCG. For example, a data unit may belong to different PDU sets with different delivery deadlines. For example, due to jitter, data units may arrive at the buffer at different times. In addition, data units may be associated with different QoS flows. Data units may be buffered in different LCHs or LCGs with different delay information.

[0043] In general, a data unit may be any portion of the buffered data. In some instances, a data unit may refer to: a packet data convergence protocol (PDCP) service data unit (SDU) or a PDCP PDU, a group of multiple PDCP SDUs or PDCP PDUs, a radio link control (RLC) PDU or RLC SDU, an RLC SDU segment, a group of multiple RLC PDUs, a group of multiple RLS SDUs, a group of RLS SDU segments, a PDU set, a group of PDU sets, or a portion of the buffered data associated with a specific QoS flow.

[0044] The BSR may be enhanced for XR use cases by including additional types of information. Existing BSRs only provide information about buffer sizes. To facilitate delay-aware scheduling of XR traffic with latency constraints, the BSR may also include information about the delay status of the buffered data. For example, the BSR may include an indication of how long data has been queued, the amount of time remaining before a delivery deadline, or the estimated time before a packet transmission ends.

[0045] There are several ways in which the UE can report buffer delay information. In some instances, the UE can report one buffer delay information per LCH or LCG. For example, the UE can report the shortest remaining time before the transmission deadline among all data units in the LCH or LCG. Reporting a single delay information can result in a small amount of overhead. However, the delay information can mislead the scheduler. For example, the buffer can include urgent and non-urgent data. Urgent data can have a smaller remaining time before the transmission deadline than non-urgent data. By reporting the remaining time before transmitting urgent data, the network can associate all buffered data with the delay information of the urgent data, causing the network to distribute resources inappropriately.

[0046] In some embodiments, the UE 104 may compress, quantize or encode the delay information. The UE 104 may map the delay information into a codeword. In some instances, the UE 104 may use a table to compress, quantize or encode the delay information. Each entry in the table may be associated with a codeword or index, wherein the codeword may have a smaller number of bits than a binary representation of the unquantized or compressed delay information. The UE 104 may map the delay information to an entry represented by ENTRY in the table. The table may associate ENTRY with an index or codeword, and the UE 104 may report the index or codeword to represent the delay information. In some embodiments, the index or codeword may be reserved to indicate that the delay information does not correspond to a valid value or that delay information reporting is not applicable, for example, the UE is not configured to measure / report the delay information of the corresponding LCH / LCG.

[0047] In some instances, the UE may report more than one buffer delay information. For example, the UE may report delay information for some or all data units buffered in the LCH or LCG. The network may have complete information about the UE's UL buffer and may implement more advanced scheduling algorithms at the expense of greater feedback overhead. Specifically, the report may associate each delay information with its corresponding data unit, resulting in greater overhead and complex MAC CE design. It is expected to improve the performance of delay-aware scheduling with a smaller increase in overhead.

[0048] In some embodiments, the UE may report properties associated with the distribution of buffer delay values. For example, the UE may report delay values ​​associated with a selected percentage. In some instances, the UE may report statistical parameters associated with the delay values ​​of the buffered data units.

[0049] In some embodiments, when multiple delay information is reported, the UE may differentially encode the delay information. For example, the report may include a reference report and a dependent (or differential) report. The reference report may include the first delay information. The UE may calculate the differential delay information based on the second delay information and the first (reference) delay information, for example, by subtracting the second delay information from the first delay information. The dependent report may include the differential delay information. The UE may use a reference table to quantize the buffer delay value, and the delay information indicates an entry in the reference table. Some embodiments may disclose a MACCE structure for reporting one or more delay information.

[0050] Figure 2 A distribution graph 200 is shown according to some embodiments. Distribution graph 200 is an example of a distribution of delay information for buffered data.

[0051] The UE may report delay information. The delay information is obtained from measurements. For example, the UE measures the time a data unit has been waiting in a buffer. A data unit may have a deadline by which it must be transmitted. In another example, the UE measures the remaining time before the transmission deadline. Thus, each data unit in the buffer may be associated with a delay value.

[0052] The UE may calculate a cumulative distribution function (CDF) 210 using the delay values ​​of the data units distributed across different portions of the buffered data in one or more LCHs or LCGs. The vertical axis of the distribution graph 200 is the percentage and the horizontal axis is the delay information. Each point on the CDF curve 210 corresponds to a delay information value d and a percentage value A. For example, point Z0 on the CDF curve 210 corresponds to delay information d0 and a percentage value A0, indicating that A0 percent of the data units in the buffer have delay information d0 or less.

[0053] For example, consider that A0 is 25% and d0 is 10 milliseconds (ms) (measuring the remaining time before a delivery deadline), where d0 and A0 correspond to point Z0 on CDF curve 210. Point Z0 may indicate that 25% of the buffered data has a remaining time before a delivery deadline of less than or equal to 10 (ms).

[0054] In one embodiment, the network determines R+1 percentage values, namely A0, A1, A2, ..., AR, and configures the UE with the percentage values. For example, the BS may send the percentage values ​​to the UE via public or dedicated radio resource control (RRC) signaling, or the percentage values ​​may be specified in the 3GPP TS. The UE calculates the delay CDF 210 for the subset of data units it buffers. With the percentage values ​​and the CDF curve 210, the UE may calculate the delay information values ​​d0, d1, d2, ..., and dR.

[0055] The UE may report a set of buffer delay values ​​{d0, d1, d2, ..., dR} or a subset thereof. The UE may report the buffer delay value and the buffer size information. The UE may report the buffer delay value in the same report with the buffer size information or in a report that does not include the buffer size information. For example, the UE may use a first MAC CE to report the buffer delay value and a second MAC CE to report the buffer size information. The UE may send the first MAC CE and the second MAC CE on the same UL transmission or be scheduled in separate UL transmissions.

[0056] In one embodiment, the UE may calculate statistical parameters of the buffer delay values ​​and report a set of multiple statistical parameters. These statistical parameters may be associated with one or more LCHs or LCGs. Examples of statistical parameters that the UE may calculate and report may include, but are not limited to: the maximum value of the delay information in the buffer, the minimum value of the delay information in the buffer, the average value (mean) of the delay information in the buffer, the median value of the delay information in the buffer (the middle value of the sorted delay information), the standard deviation of the delay information in the buffer, or the variance of the delay information in the buffer.

[0057] The BS may configure the UE to report a set of buffer delay values ​​d0 to dR or statistical parameters of the CDF 210. The BS may dynamically configure the UE via downlink control information (DCI) or semi-statically configure the UE via RRC signaling.

[0058] Figure 3 A block diagram 300 is shown according to some embodiments. The block diagram 300 is an example of a delay information reporting model in a control message. The block diagram 300 includes schemes 310, 320, 330 and 340, providing a model for reporting multiple delay information in one MAC CE.

[0059] There are several instances in which the UE may report multiple buffer delay information. The following includes examples of scenarios in which the UE reports multiple buffer delay information. These embodiments are intended to be explained by way of example and are not intended to be limiting. For example, the UE may report multiple delay information corresponding to buffers of different LCHs or LCGs in one MAC CE. The UE may report multiple delay information corresponding to different data units (e.g., PDU sets) in the buffer. The UE may report multiple delay information corresponding to different percentages of buffered data. The UE may report multiple delay information corresponding to different statistical properties of the buffered data. Some of the above examples may be combined, for example, the UE may report delay information for multiple data units buffered in multiple LCHs or LCGs.

[0060] In one embodiment, the control message for reporting the buffer delay information may include a reference report and a dependent report. The UE may specify the first buffer delay information as a reference report. The reference report may include the first buffer delay information or an indication thereof. The UE calculates a dependent (or differential) report based on the second buffer delay value and the reference report (e.g., the first buffer delay information). For example, the differential report may be the difference (subtraction) between the first buffer delay information and the second buffer delay information.

[0061] In one embodiment, the UE may construct a MAC CE by quantizing the reference delay information and the differential delay information. The reference report portion of the MAC CE may include a quantized value or an indication of the reference delay information. Similarly, the dependent report portion of the MAC CE may include a quantized value or an indication of the differential delay information.

[0062] Scheme 310 is an example of reporting a reference report with multiple differential reports in one MAC CE. The UE may specify the first delay information and assign it to the reference report R11. The UE may calculate and generate a first dependency report R12 on the reference report. For example, the UE may calculate R12 by subtracting the second delay information from the first delay information. The UE may calculate and generate a second dependency report R13 on the reference report. For example, the UE may calculate R13 by subtracting the second delay information from the first delay information. The UE may generate a control report, such as a MAC CE, based on the reference report R11, the first dependency report R12, and the second dependency report R13.

[0063] Scheme 320 is an example of reporting two reference reports with multiple differential reports in one MAC CE. The UE may specify the first delay information and assign it to the first reference report R21. The UE may calculate and generate a first dependency report R22 on the first reference report. For example, the UE may calculate R22 by subtracting the second delay information from the first delay information.

[0064] The UE may specify the third delay information and assign it to the second reference report R23. The UE may calculate and generate a second dependency report R24 on the second reference report. For example, the UE may calculate R24 by subtracting the fourth delay information from the third delay information. The UE may calculate and generate a third dependency report R25 on the second reference report. For example, the UE may calculate R25 by subtracting the fifth delay information from the third delay information.

[0065] The UE may generate a control report, such as a MAC CE, based on the reference report R21, the first dependent report R22, the second reference report R23, the third dependent report R24, and the third dependent report R25.

[0066] Scheme 330 is an example of merging similar reports into one reference report with one or more differential reports in one MAC CE. The UE may prepare delay reports 31-1, 31-2, and 33. The UE may determine that delay reports 31-1 and 32-2 have similar values. The UE may represent reports 31-1 and 31-2 with a single reference report 32 in the MAC CE. The UE may use the reference report to calculate differential report 33. Therefore, the MAC CE may include reference report 32 and differential report 33. When the difference between the two reports is less than a threshold, the UE may determine that the two reports are similar.

[0067] Scheme 340 is an example of reporting one reference report in one MAC CE and merging multiple differential reports into one differential report. The UE may prepare delay reports 41, 43-1, and 43-2. ​​The UE may determine that delay reports 43-1 and 43-2 have similar values. The UE may represent reports 43-1 and 43-2 with a single reference report 42 in the MAC CE. The UE may calculate differential report 43 using reference report 41. Therefore, the MAC CE may include reference report 32 and differential report 33. When the difference between the two reports is less than a threshold, the UE may determine that the two reports are similar.

[0068] In one embodiment, the UE may combine schemes 330 and 340. The MAC CE may include one reference report corresponding to the first plurality of delay reports and one differential report corresponding to the second plurality of delay reports. The MAC CE may indicate whether the delay reports are merged and represented by a common value.

[0069] In one embodiment, the MAC CE may indicate the reference report and the association between the dependent report and the reference report. In another embodiment, the BS may infer the reference report from the size of the report (e.g., the resources allocated to the report). The BS may infer the association between the reference report and the dependent report based on the order of the reports in the MAC CE.

[0070] Figure 4 A data structure 400 according to some embodiments is shown. The data structure 400 is an example of a table used by a UE to create reference reports and differential reports.

[0071] Table 410 is an example of a reference report table. Table 410 may include an index 412 column and a buffer delay 414 column. Table 410 may create associations between entries in the same row of the table. For example, index "1" and buffer delay B1 are in the same row, and therefore, buffer delay B1 is associated with index "1". The entries B1, B2, ..., BN in the buffer delay column may be delay values ​​or delay intervals. The UE may compare the buffer delay value with the entries in the buffer delay 414 column and map the buffer delay value to the entry denoted as ENTRY in the buffer delay 414 column. The UE may set the delay report to ENTRY or an index associated with ENTRY.

[0072] In some instances, entries with a buffer delay of 414 columns represent a delay interval. For example, B1 can be an interval, e.g., B1 = [a1,a2], which means the delay value is greater than or equal to a1 but less than or equal to a2. The interval can be represented implicitly or explicitly by the available values. For example, the interval [a1,a2] can be represented by a delay value b1 within the interval, e.g., b1 is in [a1,a2]. The explicit representation can be achieved by a column (not shown in the figure) in Table 410 that associates each interval with a representative value. The implicit representation can use rules or formulas to associate each interval with a value. For example, the interval can be represented by the value of one of its limit points or by the value of its midpoint.

[0073] Rows in Table 410 can be reserved to indicate that the delay does not correspond to a valid value or that reference reporting is not applicable, e.g., the UE is not configured to measure / report the delay information of the corresponding LCH / LCG. For example, the index value "0" can indicate that reference reporting is not applicable or that the measured value is outside the range supported by the table.

[0074] Table 415 is an example of a reference reporting table 410 that uses delay intervals as entries. This example is provided for ease of explanation and is not intended to be a constraint or limitation. This table can be used as a quantization table. For example, Table 415 has 16 indexes that can be represented by 4 bits. Any delay value can be mapped to a row in Table 415. For example, the delay value 57 (ms) can be mapped to the interval 50 < d < 60 (ms) in row 6 associated with index = 5. Thus, the delay report can use four bits associated with the index to report the delay information. When receiving the report, the BS can infer that the reported delay has a value between 50 (ms) and 60 (ms).

[0075] Table 420 is an example of a differential reporting table. Table 420 can include an index 422 column and a buffer delay 424 column. Table 420 can create associations among the entries in the same row of the table. For example, index "1" and buffer differential delay C1 are in the same row; thus, the differential delay C1 is associated with index "1". The entries C1, C2,..., CM in the differential delay column can be positive or negative differential delay values. The UE can calculate the differential buffer delay by subtracting the buffer delay value of the data unit from the reference buffer delay report. The UE can compare the differential buffer delay value with the entries in the differential delay 424 column and map the differential buffer delay value to the entry represented as ENTRY in column 424. The UE can set the differential delay report to ENTRY or the index associated with ENTRY.

[0076] Table 425 is an example of a differential report table 420 using differential delay values ​​as entries. This example is provided for ease of explanation and is not intended to be a constraint or limitation. The table can be used as a quantization table. For example, table 425 has 4 indexes that can be represented by 2 bits. Any differential delay close to +10 (ms) can be mapped to index = 0. For example, a differential delay between 0 (ms) and 15 (ms) can be mapped to index = 0. Therefore, the delay report can use two bits associated with the index to report delay information. Upon receiving the report, the BS can infer that the reported differential delay has a value of +10 (ms).

[0077] In some embodiments, the UE may have one reference reporting table 410 and one differential reporting table 420 for all configured LCHs or LCGs. Alternatively, the UE may have different reference tables associated with different LCHs or LCGs or different differential tables associated with different LCHs or LCGs.

[0078] When receiving the differential report, the BS may calculate the delay information by adding the differential delay associated with the differential report and the reference delay associated with the reference report.

[0079] The UE may select the delay information associated with the reference report as one of the following reports.

[0080] The UE may select a reference report to be associated with delay information associated with a data unit having a maximum (or minimum) size.

[0081] The UE may select a reference report to be associated with delay information associated with a data unit having an earliest arrival time at the buffer.

[0082] The UE may select a reference report to be associated with delay information associated with a data unit having a latest arrival time at the buffer.

[0083] The UE may select a reference report to be associated with delay information associated with a data unit having a minimum (or maximum) remaining time before its transmission deadline.

[0084] The UE may select a reference report to be associated with delay information associated with a data unit that is closest to the average remaining time before transmitting the buffered data units.

[0085] The UE may select a reference report to be associated with delay information associated with data units having a minimum (or maximum) remaining time before being discarded (based on the discard timer setting).

[0086] The UE may select a reference report to be associated with delay information associated with a data unit that is closest to the average remaining time before discarding buffered data units.

[0087] The UE may select a reference report to be associated with delay information associated with a data unit corresponding to a PDU set having the highest (or lowest) importance, for example, based on the PDU set importance information.

[0088] The UE may select a reference report to be associated with delay information associated with the data units corresponding to the lowest (or highest) QoS Flow ID.

[0089] The UE may select a reference report to be associated with delay information associated with a data unit having a maximum (or minimum) packet delay budget (PDB) or a PDU set delay budget (PSDB).

[0090] The UE may select a reference report to be associated with delay information associated with data units buffered in the lowest (or highest) LCH ID.

[0091] The UE may select a reference report to be associated with delay information associated with data units buffered in the lowest (or highest) LCG ID.

[0092] The UE may select a reference report to be associated with delay information associated with a data unit that shares common delay information with most other data units in the buffer.

[0093] The UE may select a reference report to be associated with delay information associated with a data unit having a minimum or maximum remaining time before its transmission deadline.

[0094] The UE may select a reference report to be associated with delay information associated with a data unit having a minimum or maximum remaining time before its transmission deadline.

[0095] The UE may select the reference report associated with the delay information associated with the highest (or lowest) percentile value.

[0096] The UE may select a reference report to be associated with delay information associated with a maximum value, a minimum value, an average value, a median value, a standard deviation value, or a variance value of the delay information in the buffer.

[0097] 3GPP TS may fix the selection rule for reference reporting. The network may use the selection rule to configure the UE. For example, the BS may send RRC signaling to configure the UE with the selection rule.

[0098] In some embodiments, the UE may compress, quantize or encode the delay information. The UE may map the delay information into a codeword. In some instances, even when the UE does not utilize reference delay reporting and differential delay reporting, the UE may compress, quantize or encode the delay information using table 410. Each entry in table 410 may be associated with a codeword or index, wherein the codeword may have a smaller number of bits than a binary representation of the unquantized or compressed delay information. The UE may map the delay information to an entry represented by ENTRY in the table. The table may associate ENTRY with an index or codeword, and the UE may report the associated index or codeword to represent the delay information. In some embodiments, the index or codeword may be reserved to indicate that the delay information does not correspond to a valid value or that delay information reporting is not applicable, for example, the UE is not configured to measure / report the delay information of the corresponding LCH / LCG.

[0099] Figure 5 A data structure 500 according to some embodiments is shown. The data structure 500 is an example of an extended MAC CE format based on the long BSR format. The MAC CE format may include information elements associated with delay information. For example, the MAC CE may include IEs for reference reporting or dependent reporting.

[0100] The data structure 500 may include a bitmap LCG0-7 on the first octet Oct 1. If set, each bit in the bitmap indicates that the MAC CE contains information associated with the corresponding LCG. For example, if LCG0 is set, such as having a value of "1", it indicates that the MAC CE contains information related to the LCG associated with LCG0. The next K octets Oct 2 to Oct K+1 include buffer sizes 510-1 to 510-K. The buffer size may be indicated using one or more octets and may indicate the size of the buffer of the UE 104.

[0101] For each buffer size 501, the MAC CE may include buffer delay information. The MAC CE in the data structure 500 includes one octet for each buffer size. For example, octet K+1 may include buffer delay information 520-1, 530-1, and 540-1 related to buffer size 510-1. Delay information 520-1 may be reference delay information associated with a first delay report of buffer size 510-1. Delay information 530-1 may be differential delay information for a second delay report of buffer size 510-1, and delay information 540-1 may be differential delay information for a third delay report of buffer size 510-1. Similarly, delay information 520-K may be reference delay information associated with a first delay report of buffer size 510-K. Delay information 530-K may be differential delay information for a second delay report of buffer size 510-K, and delay information 540-K may be differential delay information for a third delay report of buffer size 510-K.

[0102] In some embodiments, for example according to Figure 3 In the scheme 330 or 340, two or more buffer size elements may share the same delay information. An additional field in the MAC CE may be needed to indicate whether any delay information element generally corresponds to multiple buffer size elements.

[0103] Figure 6 600 is shown according to some embodiments. The data structure 600 is an example of an extended MAC CE format based on the long BSR format. The MAC CE format may include information elements associated with delay information. For example, the MAC CE may include IEs for reference reporting or dependent reporting. The data structure 600 includes the information elements described above in Figure 5 The bitmap and buffer sizes 510-1 to 510-K described in.

[0104] In data structure 600, each buffer size corresponding to an LCG is also associated with a delay information. One of the LCGs may be selected as a reference. The delay information associated with the reference LCG is reported as reference delay information 630-1. Based on the differential value, delay information of other LCGs with buffer size reports is reported, such as differential delay information reports 630-2 to 630-K. For example, reference delay information 630-1 may correspond to buffer size 510-1. Differential delay information report 630-2 may correspond to buffer size 510-2, and differential delay information report 630-K may correspond to buffer size 510-K.

[0105] In some embodiments, for example according to Figure 3In the scheme 330 or 340, two or more buffer size elements may share the same delay information. An additional field in the MAC CE may be needed to indicate whether any delay information element generally corresponds to multiple buffer size elements.

[0106] Figure 7 A data structure 700 is shown according to some embodiments. Data structure 600 is an example of an extended MAC CE format based on a short BSR format.

[0107] The first octet of the MAC CE may include an LCG identifier (LCG ID) 710 and a buffer size 720. The LCG ID 710 may identify the LCG (or LCH) to which the MAC CE relates. The second octet includes delay information related to the identified LCG. The MAC CE 700 may include a reference delay 730 and one or more differential reports. For example, the MAC CE may include two differential reports 740 and 750.

[0108] Figure 8 A data structure 800 is shown according to some embodiments. Data structure 800 is an example of a table for multiple buffer delay information. One way to reduce feedback overhead is to associate multiple delay information values ​​with one index.

[0109] Table 850 may include an index 810 for indexing each row of the table. The entries in each row of table 850 are associated with the index associated with the row. For example, all entries in the second row of table 850 are associated with index "1". Table 850 may have J+1 rows associated with indexes 0 to J. Table 850 may also include P columns 820-1 to 820-P associated with delay information. Column 820-1 may be associated with first delay information having entries E0 to EJ. Column 820-2 may be associated with second delay information having entries F0 to FJ, and column 820-P may be associated with p-th delay information having entries G0 to GJ.

[0110] In some instances, the entries of delay columns 820-1 to 820-P represent delay intervals. For example, E1 may be an interval, such as E1=[b1, b2], which means that the delay value is greater than or equal to b1 but less than or equal to b2. The interval may be represented implicitly or explicitly by a value. For example, the interval [b1, b2] may be represented by a delay value c1 in the interval, for example, c1 is in [b1, b2]. The explicit representation may be implemented by a column (not in the picture) in table 850 that associates each interval with a representative value. The implicit representation may associate each interval with a value or formula. For example, an interval may be represented by the value of one of its extreme points or by the value of its middle point. In some instances, the delay intervals in the same row may be the same. For example, E1 and F1 may indicate the same delay interval. In some instances, the delay intervals in the same row may overlap. For example, E1 and G1 may intersect with each other. In some instances, the delay intervals in the same row may not intersect. For example, EJ and GJ may not intersect.

[0111] Table 855 is an example of table 850 using delay intervals as entries. This example is provided for ease of explanation and is not intended to be a constraint or limitation. The table can be used as a quantization table. For example, table 855 has 16 indexes that can be represented by 4 bits. Any delay value can be mapped to a row in table 855. For example, a first delay value of 15 (ms), a second delay value of 45 (ms), a third delay value of 47 (ms), and a fourth delay value of 41 (ms) can be mapped to a row with index = 6. Therefore, a delay report can report four delay information using four bits associated with an index. Upon receiving the report, the BS can infer that the reported delay corresponds to a first delay value between 10 (ms) and 20 (ms), a second delay value between 40 (ms) and 50 (ms), a third delay value between 40 (ms) and 50 (ms), and a fourth delay value between 40 (ms) and 50 (ms).

[0112] In one embodiment, a row in table 800 may be reserved to indicate that multiple delay reporting is not applicable. For example, an index value of "0" may indicate that reporting using table 800 is not applicable or that one or more measured values ​​may be outside the range supported by the table.

[0113] Fig. 9 The operation flow / algorithm structure 900 according to some embodiments is shown. The operation flow / algorithm structure 900 may be implemented by a MAC entity in a UE (eg, UE 104 or UE 1200) or a component thereof (eg, processing circuit 1204).

[0114] The operation flow / algorithm structure 900 may include, at 904, determining a distribution of data in a buffer. For example, the UE may determine a CDF of delay values ​​of the data in the buffer. The distribution may be associated with a waiting time of the data in the buffer, a remaining time before a transmission deadline of the data in the buffer, or an estimated time before completing transmission of the data in the buffer. The data in the buffer may be associated with one or more LCHs or one or more LCGs.

[0115] The operation flow / algorithm structure 900 may include: at 906, based on the distribution, determining delay information corresponding to the percentage value. The UE may be configured with one or more percentage values. The UE finds the delay information associated with the percentage, so that each delay information and its corresponding percentage are associated with the CDF.

[0116] The operation flow / algorithm structure 900 may include generating a control message based on the delay value at 908. For example, according to the embodiments herein, the UE may generate a MAC CE and include the delay information and an indication of the delay information in the MAC CE.

[0117] The operational flow / algorithm structure 900 may include transmitting the control message, at 910. The UE may send the MAC CE to the UE in an uplink transmission on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0118] Fig.10 The operation flow / algorithm structure according to some embodiments is shown. The operation flow / algorithm structure 1000 may be implemented by a MAC entity in a UE (eg, UE 104 or UE 1200) or a component thereof (eg, processing circuit 1204).

[0119] The operational flow / algorithm structure 1000 may include determining first delay information associated with first data in the buffer at 1004. For example, the delay information may be based on a CDF and statistical properties of the data.

[0120] The operational flow / algorithm structure 1000 may include determining second delay information associated with second data in the buffer at 1006. For example, the delay information may be based on a CDF and statistical properties of the data.

[0121] The operation flow / algorithm structure 1000 may include: at 1008, determining a differential value based on the first delay information and the second delay information. The UE may select the first delay information as a reference report. The UE may select the first delay information based on a statistical property, CDF or delay characteristic of the data associated with the delay information or based on the QoS, urgency or priority of the LCH or LCG associated with the data. The differential value may be calculated based on a function including the first delay information and the second delay information. For example, the differential value may be the difference between the first delay information and the second delay information or a weighted sum of the two delay information. The UE may use a table to compress or encode the reference report and the differential report as described above.

[0122] The operation flow / algorithm structure 1000 may include: generating a control message including a reference report and a dependent report (or a differential report) at 1010, the reference report being based on the first buffer delay information, and the dependent report being based on the differential value. For example, according to the embodiments of this document, the UE may generate a MAC CE and include the delay information and an indication of the delay information in the MAC CE.

[0123] The operational flow / algorithm structure 1000 may include transmitting the control message, at 1012. The UE may send a MAC CE to the UE in an uplink transmission on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0124] Fig.11 An operational flow / algorithm structure 1100 according to some embodiments is shown. The operational flow / algorithm structure 1100 is an example of operating a BS to provide delay-aware scheduling based on differential delay reports made by a UE. The operational flow / algorithm structure 1100 may be implemented by a network node (e.g., AN 108, network node 1300) or a component thereof (e.g., processor 1304).

[0125] The operation flow / algorithm structure 1100 may include: at 1104, receiving a control message from the UE. The control message may be an uplink control message. For example, the first message may be a MAC CE carrying buffer delay information. The MAC CE may include a reference report and a differential report.

[0126] The operational flow / algorithm structure 1100 may include determining first delay information at 1106. The BS may determine the first delay information based on a reference report of the received control message.

[0127] The operation flow / algorithm structure 1100 may include: determining the second delay information at 1108. The BS may determine the second delay information based on the reference report, the first delay information, or the differential report. For example, the BS may determine a differential value based on the differential report, and calculate the second delay information by adding the differential value to the first delay information.

[0128] The operation flow / algorithm structure 1100 may include: At 1110, a downlink (DL) control message is generated. The BS may perform uplink delay-aware scheduling based on the first delay information and the second delay information. Based on the delay-aware scheduling, the BS may generate a UL grant to allocate resources for UL transmission to the UE. The control message may be a DCI.

[0129] The operational flow / algorithm structure 1100 may include transmitting the DL control message at 1112. The BS may send the DL control message on a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).

[0130] Fig.12 UE 1200 according to some embodiments is shown. UE 1200 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.

[0131] UE 1200 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.

[0132] UE 1200 may include a processor 1204, an RF interface circuit 1208, a memory / storage device 1212, a user interface 1216, a sensor 1220, a driving circuit 1222, a power management integrated circuit (PMIC) 1224, an antenna structure 1226, and a battery 1228. The components of UE 1200 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.12 The block diagram of UE 1200 is intended to show a high-level view of certain of the components of UE 1200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0133] Components of UE 1200 may be coupled to various other components via one or more interconnects 1232, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipsets) to interact with each other.

[0134] The processor 1204 may include processor circuits such as, for example, a baseband processor circuit (BB) 1204A, a central processor unit circuit (CPU) 1204B, and a graphics processor unit circuit (GPU) 1204C. The processor 1204 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1212) to cause the UE 1200 to perform operations as described herein.

[0135] Processor 1204 may perform operations associated with bearer flows as described elsewhere herein.For example, according to embodiments described herein, processor 1204 generates a control message to report buffer delay information.

[0136] In some embodiments, the baseband processor circuit 1204A can access the communication protocol stack 1236 in the memory / storage device 1212 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1204A can access the communication protocol stack 1236 to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1208.

[0137] The baseband processor circuit 1204A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0138] The memory / storage 1212 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1236) that may be executed by one or more processors in the processor 1204 to cause the UE 1200 to perform various operations described herein. The memory / storage 1212 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1200. In some embodiments, some of the memory / storage 1212 may be located on the processor 1204 itself (e.g., L1 cache and L2 cache), while other memory / storage 1212 is located external to the processor 1204 but can be accessed via a memory interface. The memory / storage 1212 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0139] The RF interface circuit 1208 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1200 to communicate with other devices through a radio access network. The RF interface circuit 1208 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.

[0140] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1226 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1204.

[0141] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1226.

[0142] In various embodiments, the RF interface circuit 1208 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0143] Antenna 1226 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1226 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input / multiple output communications. Antenna 1226 may include: microstrip antennas; printed antennas fabricated on the surface of one or more printed circuit boards; patch antennas or phased array antennas. Antenna 1226 may have one or more panels designed for specific frequency bands including frequency bands in FR1 or FR2.

[0144] The user interface circuit 1216 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1200. The user interface 1216 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device for accepting input, including in particular one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1200.

[0145] Sensors 1220 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0146] The driver circuit 1222 may include software elements and hardware elements for controlling a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1200. The driver circuit 1222 may include various drivers, thereby allowing other components to interact with or control various I / O devices that may be present in or connected to the UE 1200. For example, the driver circuit 1222 may include circuits for facilitating coupling a universal integrated circuit card (UICC) or a universal subscriber identity module (USIM) to the UE 1200. For additional examples, the driver circuit 1222 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1220 and controlling and allowing access to the sensor circuit 1220, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0147] The PMIC 1224 may manage power provided to various components of the UE 1200. Specifically, with respect to the processor 1204, the PMIC 1224 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0148] In some embodiments, the PMIC 1224 may control or otherwise be a part of various power saving mechanisms of the UE 1200 including DRX, as discussed herein.

[0149] The battery 1228 can power the UE 1200, but in some examples, the UE 1200 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1228 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1228 can be a typical lead-acid car battery.

[0150] Fig.13 A network node 1300 is shown according to some embodiments. The network node 1300 may be similar to and substantially interchangeable with a base station 108, a device implementing one of the network hops, an integrated access and backhaul (IAB) node, a network controlled repeater, or a server in a core network or an external data network.

[0151] The network node 1300 may include a processor 1304 , RF interface circuitry 1308 (if implemented as an access node), core node (CN) interface circuitry 1312 , memory / storage circuitry 1316 , and antenna structures 1326 .

[0152] Components of network node 1300 may be coupled to various other components via one or more interconnects 1328 .

[0153] The processor 1304, RF interface circuit 1308, memory / storage circuit 1316 (including communication protocol stack 1310), antenna structure 1326 and interconnect 1328 may be similar to those described in detail in the accompanying drawings. Fig.12 Like named elements are shown and described.

[0154] Processor 1304 may perform operations associated with bearer flows as described elsewhere herein.For example, processor 1304 may generate a control message to report buffer delay information according to embodiments described herein.

[0155] The CN interface circuit 1312 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the network node 1300 via optical fiber or wireless backhaul. The CN interface circuit 1312 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1312 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0156] In some embodiments, the network node 1300 may be coupled to a transmit receive point (TRP) using an antenna structure 1326, a CN interface circuit, or other interface circuitry.

[0157] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0158] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0159] Example

[0160] In the following sections, additional exemplary aspects are provided.

[0161] Embodiment 1 includes a method of operating a user equipment (UE), the method comprising: determining a distribution of data in a buffer; based on the distribution, determining delay information corresponding to a percentage value; based on the delay value, generating a control message; and transmitting the control message.

[0162] Embodiment 2 includes a method according to embodiment 1 or other embodiments herein, wherein the control message is a medium access control (MAC) control element (CE).

[0163] Embodiment 3 includes the method according to embodiment 1 or 2 or other embodiments herein, the method further comprising: receiving a configuration including an indication of the percentage value from a base station.

[0164] Embodiment 4 includes a method according to any one of embodiments 1 to 3 or other embodiments herein, wherein the distribution is based on the waiting time of the data in the buffer, the remaining time before the transmission deadline of the data in the buffer, or the estimated time before the transmission of the data in the buffer is completed.

[0165] Embodiment 5 includes a method according to any one of embodiments 1 to 4 or other embodiments herein, wherein the data includes a packet data convergence protocol (PDCP) service data unit (SDU), a PDCP PDU, a radio link control (RLC) SDU, an RLC PDU, an RLC SDU segment, a PDU set, or data associated with a quality of service (QoS) flow.

[0166] Embodiment 6 includes a method according to any one of embodiments 1 to 5 or other embodiments herein, wherein the buffer is associated with a logical channel (LCH) or a logical channel group (LCG).

[0167] Embodiment 7 includes a method according to any one of embodiments 1 to 6 or other embodiments herein, wherein the data in the buffer belongs to one or more protocol data unit (PDU) sets.

[0168] Embodiment 8 includes a method according to any one of embodiments 1 to 7 or other embodiments herein, wherein a first data unit of the data arrives at the buffer at a first arrival time, and a second data unit of the data arrives at the buffer at a second arrival time, and the first arrival time is different from the second arrival time.

[0169] Embodiment 9 includes a method according to any one of embodiments 1 to 8 or other embodiments described herein, wherein the delay information is a statistical value associated with the data in the buffer, and the statistical value includes a maximum value, a minimum value, a mean value, a median value, a standard deviation value, or a variance value.

[0170] Embodiment 10 includes a method for operating a user equipment (UE), the method comprising: determining first buffer delay information associated with first data in a buffer; determining second buffer delay information associated with second data in the buffer; determining a differential value based on the first buffer delay information and the second buffer delay information; generating a control message to indicate the first buffer delay information and the differential value; and transmitting the control message.

[0171] Embodiment 11 includes the method according to embodiment 10 or other embodiments herein, wherein the first delay information is associated with a remaining time before a transmission deadline of the first data in the first buffer or a queuing time in the first buffer.

[0172] Embodiment 12 includes a method according to embodiment 10 or 11 or other embodiments herein, wherein the control message includes a reference report, and the reference report is used to indicate a first buffer delay.

[0173] Embodiment 13 includes a method according to any one of embodiments 10 to 12 or other embodiments herein, the method further comprising: receiving a configuration including a table; and determining the reference report based on the first buffer delay information and the table.

[0174] Embodiment 14 includes a method according to any one of embodiments 10 to 13 or other embodiments herein, the method further comprising: receiving a configuration including a table; and determining the differential value based on the first buffer delay information and the table.

[0175] Embodiment 15 includes a method according to any one of embodiments 10 to 14 or other embodiments described herein, wherein the control message is a medium access control (MAC) control element (CE).

[0176] Embodiment 16 includes a method according to any one of embodiments 10 to 15 or other embodiments described herein, wherein the first buffer is associated with a first logical channel (LCH) or a first logical channel group (LCG), and the second buffer is associated with a second LCH or a second LCG.

[0177] Embodiment 17 includes the method according to any one of embodiments 10 to 16 or other embodiments herein, the method further comprising: determining a distribution based on the first data in the first buffer or the second data in the second buffer.

[0178] Embodiment 18 includes a method according to any one of embodiments 10 to 17 or other embodiments herein, wherein the first delay information is based on a first percentile associated with the distribution, or the second delay information is based on a second percentile associated with the distribution.

[0179] Embodiment 19 includes a method for operating a base station (BS), the method comprising: receiving an uplink control message including a reference report and a differential report from a user equipment (UE); determining first delay information associated with first data in a buffer based on the reference report; determining second delay information associated with the first data or second data in the buffer based on the reference report or the differential report; generating a downlink control message based on the first delay information or the second delay information; and transmitting the downlink control message.

[0180] Embodiment 20 includes a method according to embodiment 19 or other embodiments herein, wherein the control message is a medium access control (MAC) control element (CE).

[0181] Another embodiment may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0182] Another embodiment may include a method, technique or process described or related to any one of Embodiments 1 to 20, or a portion or component thereof.

[0183] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described or related to any one of Embodiments 1 to 20.

[0184] Another embodiment comprises a signal according to or relating to any one of embodiments 1 to 20, or parts or components thereof.

[0185] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of embodiments 1 to 20, or otherwise described in the present disclosure.

[0186] Another embodiment may include a signal encoded with data as described or related to any one of embodiments 1 to 20, or a portion or component thereof, or described in other ways in this disclosure.

[0187] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0188] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or portion thereof, described or related to any one of Embodiments 1 to 20.

[0189] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described or related to any one of Embodiments 1 to 20, or a portion thereof.

[0190] Another embodiment may include a signal in a wireless network as shown and described herein.

[0191]

[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0192]

[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.

[0193]

[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.

[0194] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.

[0195] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method, comprising: Determine the distribution of data in the buffer; Based on the distribution, determining delay information corresponding to the percentage value; as well as Based on the delay value, a control message is generated.

2. The method according to claim 1, further comprising: A configuration received from a base station including an indication of the percentage value is processed.

3. The method of claim 1, wherein the distribution is based on a waiting time of the data in the buffer, a remaining time before a delivery deadline of the data in the buffer, or an estimated time before completing the transmission of the data in the buffer.

4. The method of claim 1, wherein the data comprises a packet data convergence protocol (PDCP) service data unit (SDU), a PDCP PDU, a radio link control (RLC) SDU, an RLC PDU, an RLC SDU segment, a PDU set, or data associated with a quality of service (QoS) flow.

5. The method of claim 1, wherein the buffer is associated with a logical channel (LCH) or a logical channel group (LCG).

6. The method of claim 5, wherein the data in the buffer belongs to one or more sets of protocol data units (PDUs).

7. The method of claim 5, wherein a first data unit of the data arrives at the buffer at a first arrival time and a second data unit of the data arrives at the buffer at a second arrival time, and the first arrival time is different from the second arrival time.

8. The method according to any one of claims 1 to 7, wherein the delay information is a statistical value associated with the data in the buffer, the statistical value comprising a maximum value, a minimum value, an average value, a median value, a standard deviation value, or a variance value.

9. A baseband processor, comprising: A processing circuit, the processing circuit being configured to: determining first buffer delay information associated with first data in the buffer; determining second buffer delay information associated with second data in the buffer; Determining a differential value based on the first buffer delay information and the second buffer delay information; as well as generating a control message including the first buffer delay information and the differential value; and Interface circuitry is provided for communicatively coupling the processing circuitry to components of a device. 10 . The baseband processor of claim 9 , wherein the first delay information is associated with a remaining time before a transmission deadline of the first data in the first buffer or a queuing time in the first buffer.

11. The baseband processor of claim 9, wherein the control message comprises a reference report for indicating a first buffer delay.

12. The baseband processor of claim 11, wherein the processing circuit is further configured to: Processing includes configuration of tables; and Based on the first buffer delay information and the table, the reference report is determined.

13. The baseband processor of claim 9, wherein the processing circuit is further configured to: Processing includes configuration of tables; and The differential value is determined based on the first buffer delay information and the table.

14. The baseband processor of claim 9, wherein the control message is a medium access control (MAC) control element (CE).

15. The baseband processor of claim 9, wherein the first buffer delay information is associated with a first logical channel (LCH) or a first logical channel group (LCG), and the second buffer delay information is associated with a second LCH or a second LCG.

16. The baseband processor of claim 9, wherein the first data and the second data are associated with a logical channel LCH or a logical channel group (LCG).

17. The baseband processor according to any one of claims 9 to 16, wherein the processing circuit is further configured to: A distribution is determined based on the first data in the first buffer or the second data in the second buffer.

18. The baseband processor of claim 17, wherein the first delay information is based on a first percentile associated with the distribution, or the second delay information is based on a second percentile associated with the distribution.

19. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: Processing an uplink control message received from a user equipment (UE), the uplink control message comprising a reference report and a differential report; Determining first delay information associated with first data in the buffer based on the reference report; Determining second delay information associated with the first data or the second data in the buffer based on the reference report or the differential report; as well as A downlink control message is generated based on the first delay information or the second delay information.

20. The one or more computer-readable media of claim 19, wherein the control message is a medium access control (MAC) control element (CE).