User Equipment and Method

Abstract

An exemplary embodiment of the present disclosure relates to a solution for Buffer Status Report (BSR) enhancement, in which a terminal device transmits, to a network device, delay information for at least one buffered data packet, the delay information indicating at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a BSR is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

Description

[Technical Field]

[0001] FIELD Exemplary embodiments of the present disclosure relate generally to the field of communications technologies, and more particularly to an apparatus, method, and medium for buffer status report (BSR) enhancements. [Background technology]

[0002] Communication systems are being developed to meet the increasing demand for wireless data traffic. New Radio (NR) communication and various other types of wireless communication systems are being required to support various services, such as eXtended Reality (XR) services. These services place stricter requirements on the transmission delay of wireless communication systems.

[0003] In a communication network, a terminal device wishing to transmit data sends a Buffer Status Report (BSR) to a network device indicating the amount of data buffered for transmission, and the network device responds by allocating appropriate uplink resources and transmission opportunities to the terminal device so that the terminal device can transmit the data. Summary of the Invention [Problem to be solved by the invention]

[0004] Embodiments of the present disclosure generally provide an apparatus, method, and computer storage medium for BSR extensions. [Means for solving the problem]

[0005] In a first aspect, a first communications device is provided, comprising: a processor configured to cause the first communications device to transmit, to a network device, delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

[0006] In a second aspect, a second communications device is provided, comprising: a processor configured to: receive from the terminal device delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between the arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from the delay budget for the at least one data packet; and determine a remaining delay budget for the at least one data packet based on the delay information.

[0007] In a third aspect, a communication method is provided, the method including transmitting, from the terminal device to a network device, delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering of the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

[0008] In a fourth aspect, a communication method is provided, comprising: receiving, at a network device, delay information for at least one data packet buffered at a terminal device, the delay information indicating at least one of a reference time for buffering of the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval between the arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted from a delay budget for the at least one data packet, a second time interval between the arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from the delay budget for the at least one data packet; and determining a remaining delay budget for the at least one data packet based on the delay information.

[0009] In a fifth aspect, there is provided a computer readable medium having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to perform a method according to the third or fourth aspect.

[0010] Other features of the present disclosure will become readily apparent from the following description. [Brief explanation of the drawings]

[0011] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the accompanying drawings.

[0012] [Figure 1] FIG. 1 illustrates an exemplary communication environment in which exemplary embodiments of the present disclosure may be implemented.

[0013] [Figure 2] 1 illustrates a signaling flow for communication according to some embodiments of the present disclosure.

[0014] [Figure 3] 1 illustrates an example timeline showing various events occurring from the time buffering of a data packet begins to the time a network device receives a BSR.

[0015] [Figure 4A] 1 illustrates an example format of a BSR MAC CE according to some embodiments of the present disclosure. [Figure 4B] 1 illustrates an example format of a BSR MAC CE according to some embodiments of the present disclosure. [Figure 4C] 1 illustrates an example format of a BSR MAC CE according to some embodiments of the present disclosure.

[0016] [Figure 5A]10 illustrates an example format of a BSR MAC CE according to some other embodiments of the present disclosure. [Figure 5B] 10 illustrates an example format of a BSR MAC CE according to some other embodiments of the present disclosure. [Figure 5C] 10 illustrates an example format of a BSR MAC CE according to some other embodiments of the present disclosure.

[0017] [Figure 6A] 1 shows an example timeline illustrating various events that occur from the time the last BSR is sent to the time a network device receives a new BSR. [Figure 6B] 1 shows an example timeline illustrating various events that occur from the time the last BSR is sent to the time a network device receives a new BSR.

[0018] [Figure 7] FIG. 1 illustrates a flowchart of a method implemented in a terminal device according to some embodiments of the present disclosure.

[0019] [Figure 8] FIG. 1 illustrates a flowchart of a method implemented in a network device according to some embodiments of the present disclosure.

[0020] [Figure 9] FIG. 1 is a schematic block diagram of an apparatus suitable for practicing exemplary embodiments of the present disclosure.

[0021] Throughout the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0022] The principles of the present disclosure will be described with reference to several embodiments. It should be understood that these embodiments are set forth for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitations on the scope of the present disclosure. The embodiments described herein can be embodied in various ways other than those described below.

[0023] In the following description and claims, unless defined otherwise, all technical and scientific terms used have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0024] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communication (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, in-vehicle devices for V2X communications where X represents pedestrian, vehicle, or infrastructure / network, devices for Integrated Access and Backhaul (IAB), spacecraft or air vehicles in a Non-terrestrial network (NTN) including Satellites and High Altitude Platforms (HAPs) including Unmanned Aircraft Systems (UASs), Augmented Reality (AR), Mixed Reality (MR), and other technologies. This includes, but is not limited to, extended reality (XR) devices, which include different types of reality such as real reality (VR), virtual reality (VR), unmanned aerial vehicles (UAVs), commonly known as drones, i.e., aircraft without a human pilot, devices on high speed trains (HST), image capture devices such as digital cameras, sensors, gaming devices, music storage and playback devices, and internet appliances that enable wireless or wired internet access and browsing.The "terminal device" may also have "multicast / broadcast" capabilities and support public safety and mission-critical, V2X applications, transparent IPV4 / IPV6 multicast delivery, IPTV, smart TV, wireless services, over-the-air software delivery, group communication, and IoT applications. It may also incorporate one or more Subscriber Identity Modules (SIMs), known as multi-SIMs. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0025] The term "network device" refers to a device capable of providing or hosting a cell or coverage area over which terminal devices can communicate. Examples of network devices include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a transmission reception point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a low-power node such as an IAB node, a femto node, a pico node, and a reconfigurable intelligent surface (RIS).

[0026] A terminal device or network device may have artificial intelligence (AI) or machine learning capabilities, which typically include models trained from a large amount of collected data for a specific function and can be used to predict some information.

[0027] A terminal device or network device may operate in multiple frequency ranges, such as FR1 (e.g., 450 MHz to 6000 MHz), FR2 (e.g., 24.25 GHz to 52.6 GHz), frequency bands greater than 100 GHz, and terahertz (THz). It can also operate in licensed, unlicensed, and shared spectrum. A terminal device may have multiple connections with network devices in Multi-Radio Dual Connectivity (MR-DC) application scenarios. A terminal device or network device can operate in full duplex, flexible duplex, and cross division duplex modes.

[0028] Embodiments of the present disclosure may be implemented in test equipment, such as a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal equipment, a test network equipment, or a channel emulator. In some embodiments, the terminal equipment may be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is an eNB and the second RAT device is a gNB. Information related to the different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In some embodiments, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device to the terminal device directly or via the first network device. In some embodiments, information regarding the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device, and information regarding the reconfiguration of the terminal device configured by the second network device may be transmitted to the terminal device directly from the second network device or via the first network device.

[0029] In this disclosure, unless the context clearly indicates otherwise, the singular forms "a," "the," and "the" are intended to include the plural. The term "comprises" and variations thereof are interpreted as open-ended terms meaning "including, but not limited to." The term "based on" is interpreted as "based at least in part on." The terms "one embodiment" and "embodiment" are interpreted as "at least one embodiment." The term "another embodiment" is interpreted as "at least one other embodiment." Terms such as "first," "second," etc. may refer to different objects or the same object. The following content may include other definitions, both explicit and implicit.

[0030] In some instances, values, procedures, or devices are referred to as "optimal," "lowest," "highest," "minimum," "maximum," etc. It is understood that such descriptions are intended to indicate choices among multiple functional alternatives used, and that such choices are not necessarily better, smaller, higher, or more preferred than other choices.

[0031] As used herein, the terms "resource," "transmission resource," "uplink resource," or "downlink resource" may refer to any resource for performing communication, such as a time domain resource, a frequency domain resource, a space domain resource, a code domain resource, or any other resource that enables communication. Hereinafter, unless otherwise specified, both frequency domain and time domain resources are used as examples of transmission resources for describing some embodiments of the present disclosure. It should be noted that the exemplary embodiments of the present disclosure are equally applicable to other resources in other domains.

[0032] The embodiments of the present disclosure provide a solution for BSR extension. The principles and embodiments of the present disclosure are described in detail below with reference to the drawings.

[0033] 1 is a schematic diagram of an exemplary communication environment 100 in which exemplary embodiments of the present disclosure may be implemented. In the communication environment 100, multiple communication devices, including terminal devices 110 and network devices 120, may communicate with each other.

[0034] 1, network device 120 may be a base station that serves terminal device 110. The coverage area of ​​network device 120 may be referred to as a cell (not shown). In communication environment 100, network device 120 and terminal device 110 may communicate data and control information with each other.

[0035] It should be understood that the number of devices and their connections in Figure 1 are shown for illustrative purposes only and are not intended to limit the present disclosure. Communication environment 100 may include any suitable number of devices adapted to implement embodiments of the present disclosure. For example, more terminal devices and / or network devices may be present in communication environment 100. Although not shown, communication environment 100 may participate in a core network having core network devices for supporting communications.

[0036] Communications in communication environment 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Embodiments of the present disclosure may be performed in accordance with any currently known or future-developed generation of communication protocols. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or sixth generation (6G) networks.

[0037] In communication environment 100, terminal device 110 may communicate with one or more network devices 120. In some embodiments, network device 120 may include a transmission reception point (TRP). A network device 120 that serves terminal device 110 may be referred to as the serving network device of terminal device 110. In some exemplary embodiments, a link from network device 120 to terminal device 110 is referred to as a downlink (DL), and a link from terminal device 110 to network device 120 is referred to as an uplink (UL).

[0038] In a communication network, a terminal device and a network device may communicate traffic data, control information, etc. In some examples, the terminal device may transmit a buffer status report (BSR) to the network device indicating the amount of data it has buffered for transmission. In response, the network device allocates appropriate uplink resources and transmission opportunities to the terminal device so that the terminal device can transmit the data.

[0039] Various real-time applications are latency-sensitive and require relatively short latency and relatively small latency variation. Examples of real-time applications include augmented reality (XR) applications, multimedia applications, Voice over Internet Protocol (VoIP), video conferencing applications, virtual reality applications, and online games. In particular, latency issues can significantly impact the user experience. For example, an online mobile game may experience repeated pauses or delays due to issues occurring in the lower layers of the wireless protocol stack (e.g., wireless interference).

[0040] In some applications, data beyond a certain delay budget may be useless, so uplink resources need to be allocated in advance, so it is desirable for the terminal device to be able to perform delay reporting of buffered data in the uplink.

[0041] According to an exemplary embodiment of the present disclosure, a solution for BSR enhancement is provided, in which a terminal device transmits delay information for at least one data packet to a network device. The delay information may indicate information regarding a specific delay time and a delay time interval, thereby enabling the network device to determine a remaining delay budget for the at least one data packet. This solution allows the network device to flexibly schedule resources taking into account the remaining delay budget of the data packet and prioritize the scheduling of corresponding delayed data, thereby improving capacity.

[0042] Exemplary embodiments of the present disclosure will now be described in detail.

[0043] 2 illustrates a signaling flow 200 for communication in accordance with some embodiments of the present disclosure. For ease of explanation, the signaling flow 200 is described with reference to FIG. 1, and involves a terminal device 110 and a network device 120.

[0044] In signaling flow 200, terminal device 110 transmits (205) delay information for at least one data packet buffered at terminal device 110 to the network. The delay information provides network device 120 with appropriate information for deriving a remaining delay budget for the at least one data packet when network device 120 receives the delay information. Thus, upon receiving (210) the delay information, network device 120 determines (215) a remaining delay budget for the at least one data packet based on the delay information. In some embodiments, the remaining delay budget may be determined with respect to at least the time the delay information was received. In some embodiments, the delay information may be transmitted to network device 120 in a BSR, although it is also possible to transmit the delay information and other data buffer status information separately.

[0045] As used herein, a data packet may refer to any suitable data unit. Generally, each protocol layer receives a data packet from a higher layer, processes the data packet to generate a new data packet, and transmits the new data packet to a lower protocol layer. In each protocol layer, a data packet from the higher layer may be called a service data unit (SDU), and a data packet generated by the protocol layer may be called a protocol data unit (PDU). Thus, in two adjacent protocol layers, a PDU of the higher protocol layer may be considered an SDU of the lower protocol layer.

[0046] In some embodiments, the delay information can be determined per data packet, e.g., per PDU, or per SDU. In some embodiments, the delay information can be determined per data packet set, e.g., per PDU set. A PDU set consists of one or more data packets (e.g., one or more PDUs) carrying the payload of one unit of information generated at the application level (e.g., a frame or video slice for XR media, XRM, or a service). In some embodiments, all PDUs in a PDU set are required by the application layer to use the information of the corresponding unit. In other embodiments, the application layer can recover some or all of the information unit even if some PDUs are missing.

[0047] Buffering delays can occur for various reasons. The delay occurs from the time a data packet is buffered. FIG. 3 illustrates an example timeline 300 illustrating various events from the time data packet buffering begins to the time a network device receives a BSR. As illustrated, assume that at least one data packet (e.g., a PDU or a set of PDUs) arrives at the access stratum (AS) layer from an upper layer at time t0. This time t0 is also referred to as the arrival time of the at least one data packet at the AS layer. Resources for transmitting delay information (or BSR) are granted at time t1. The terminal device 110 generates a BSR for the at least one data packet at time t2. The BSR is transmitted at time t3, e.g., via the Uu interface. Time t3 can be determined based on the granted resources. In some embodiments, the transmission of the BSR at time t3 is a new transmission (i.e., an initial transmission). According to a hybrid automatic repeat request (HARQ) mechanism, one or more retransmissions of the BSR may occur after the initial transmission. The BSR is received by network device 120 at time t4.

[0048] In some embodiments, the delay information may indicate a reference time for buffering at least one data packet (a single packet, e.g., a PDU, an SDU, or a set of data packets, e.g., a PDU set). In some embodiments, the reference time may include an arrival time of the at least one data packet at the AS layer, e.g., time t0 as shown in FIG. 3, where time t0 may be the start of buffering of the at least one data packet. In some embodiments, the reference time may be any time known to both the terminal device 110 and the network device 120. This reference time may be set relative to the arrival time of the at least one data packet. For example, it may be set to have a predetermined time interval relative to the arrival time t0. In some embodiments, the reference time may be indicated in units of symbols within a time slot or other suitable time units.

[0049] On the network device 120 side, the remaining delay budget for at least one data packet can be determined based on the reference time indicated by the delay information. Specifically, the network device 120 can determine the time interval (also referred to herein as the "third time interval") between the reference time and the time at which the BSR is received (e.g., time t4 in FIG. 3). If the reference time is t0 in FIG. 3, the time interval is determined to be (t4-t0). The network device 120 can derive the time interval (t4-t0) because it can know when the BSR (which reports the buffer status of at least one data packet) is received. The network device 120 can determine the remaining delay budget for at least one data packet ("t PDB The network device 120 may know the delay budget t for at least one data packet. PDB The remaining delay budget can be determined by subtracting the third time interval from t. PDB -(t4-t0).

[0050] At least one data packet must be within the delay budget t PDB , and if its delay exceeds the delay budget t, the data packet is deemed not useful. PDB may be the packet delay budget (PDB) of the PDU or the PDU set delay budget (PSDB) of the PDU set. In some embodiments, the delay budget t for at least one data packet PDB may be determined based on the type of service or application, for example, the delay requirement of the service or application for the at least one data packet. In some embodiments, the delay budget t PDBmay be determined based on the value of a discard timer (e.g., discardTimer) of a protocol entity, such as a PDCP entity. The expiration of the discard timer may be the expiration of the delay budget. In some embodiments, the delay budget t PDB may be the delay budget at the Uu interface or the PDB or the PSDB, and may be set by the network device 120 or other network devices. PDB can be configured for a service, application, data radio bearer (DRB), logical channel (LCH), logical channel group (LCG), Packet Data Convergence Protocol (PDCP) entity, etc. The delay budget t for at least one data packet PDB may be determined in other suitable manners, including but not limited to.

[0051] In some embodiments, the delay information reported by terminal device 110 may indicate a first time interval between the arrival time of the at least one data packet (e.g., time t0 in FIG. 3 ) and the time the BSR is transmitted (e.g., time t3 in FIG. 3 ). The first time interval (t3-t0) may represent a delay of the at least one data packet when the BSR is transmitted by terminal device 110. In some embodiments, the time the BSR is transmitted may be the time of a new (or initial) transmission of the BSR.

[0052] The network device 120 can determine the remaining delay budget based on the first time interval reported by the terminal device 110. Because resources for the transmission of the BSR are allocated by the network device 120, the network device 120 can also know the time when the BSR is transmitted, e.g., time t3 in FIG. 3. The network device 120 can determine the time interval (sometimes referred to as the "fourth time interval") between the time when the BSR is transmitted (e.g., time t3 in FIG. 3) and the time when the BSR is received (e.g., time t4 in FIG. 3), which is represented as (t4-t3). The network device 120 can determine the remaining delay budget t PDB The remaining delay budget for at least one data packet can be determined by subtracting the sum of the first time interval (t3-t0) and the fourth time interval (t4-t3) from t. PDB -(t3-t0)-(t4-t3).

[0053] In some embodiments, the delay information reported by terminal device 110 is a delay budget t PDB may represent a first result obtained by subtracting a first time interval (t3-t0) from t. PDB -(t3-t0), which takes into account the delay of at least one data packet before the BSR transmission and can represent the "remaining delay budget" of at least one data packet at the time of the BSR transmission. PDB If the BSR indicates a time interval (t3-t0), the network device 120 further determines a fourth time interval (t4-t3) between the time the BSR was transmitted and the time the BSR was received, and sets the remaining delay budget to t PDB -(t3-t0)-(t4-t3).

[0054] In some embodiments, the delay information reported by terminal device 110 may indicate a second time interval between the arrival time of the at least one data packet (e.g., time t0 in FIG. 3 ) and the time when resources for transmitting the BSR are granted (e.g., time t1 in FIG. 3 ). The second time interval (t1-t0) may represent the delay of the at least one data packet when resources for transmitting the BSR are granted.

[0055] The network device 120 can determine the remaining delay budget based on the second time interval reported by the terminal device 110. Because the resources for transmitting the BSR are allocated by the network device 120, the network device 120 can also know the time when the resources for transmitting the BSR are granted (e.g., time t1 in FIG. 3). The network device 120 can determine the time interval (sometimes referred to as the "fifth time interval") between the time when the resources for transmitting the BSR are granted (e.g., time t1 in FIG. 3) and the time when the BSR is received (e.g., time t4 in FIG. 3), which is represented as (t4 - t1). The network device 120 can determine the remaining delay budget t PDB The remaining delay budget for at least one data packet can be determined by subtracting the sum of the second time interval (t1-t0) and the fifth time interval (t4-t1) from t. PDB -(t1-t0)-(t4-t1).

[0056] In some embodiments, the delay information reported by terminal device 110 is a delay budget t PDB The second result may be expressed as t minus a second time interval (t1-t0). PDB -(t1-t0), which can represent the "remaining delay budget" of at least one data packet when resources for BSR transmission are granted, taking into account the delay of at least one data packet before BSR resource grant. PDBIf the BSR indicates a delay budget of t -(t - t), the network device 120 may further determine a fifth time interval (t - t) between the time resources for the BSR transmission were granted and the time the BSR was received. The network device 120 may then determine the remaining delay budget as t PDB -(t1-t0)-(t4-t1).

[0057] There are several examples of delay information reported by the terminal device 110, which enable the network device 120 to determine the remaining delay budget. If the remaining delay budget is explicitly determined by the network device 120, the network device 120 can flexibly schedule uplink resources for data packet transmissions taking the remaining delay budget into consideration without exceeding the delay budget of the data packets. By prioritizing the scheduling of corresponding delayed data, system capacity can be improved.

[0058] In some embodiments, as described above, the delay information may be included in a BSR and reported to network device 120. A BSR that includes delay information may also be referred to as a delayed BSR. In some embodiments, whether to report delay information or a delayed BSR may be configured by network device 120. Terminal device 110 may receive configuration information from network device 120 or another network entity indicating whether to report delay information (or a delayed BSR) for a DRB, LCH, LCG, PDCP entity, or any other entity associated with the data packet. If the configuration information indicates that delay information should be reported, terminal device 110 may report delay information for at least one data packet corresponding to a DRB, LCH, LCG, PDCP entity, etc.

[0059] In some embodiments, a delay threshold or budget threshold may be configured for a DRB, an LCH, an LCG, a PDCP entity, or any other entity associated with a data packet. Terminal device 110 may receive configuration information indicating the delay threshold or budget threshold from network device 120 or another network entity. In some embodiments, if the delay of at least one data packet exceeds the delay threshold (which may be referred to as a “first delay threshold”) or if the remaining delay budget for at least one data packet is lower than the budget threshold (which may be referred to as a “first budget threshold”), terminal device 110 may determine that reporting of delay information or a delayed BSR may be triggered. Terminal device 110 transmits the delay information to network device 120.

[0060] At the terminal device 110 side, the remaining delay budget may be determined by counting the delay of at least one data packet from the arrival time of the at least one data packet (e.g., time t0 in FIG. 3) and subtracting that delay from the delay budget of the at least one data packet.

[0061] In some embodiments, if the delay of a PDCP SDU or PDU set exceeds a delay threshold, or if the remaining delay budget of a PDCP SDU or PDU set is less than a budget threshold, the PDCP entity of terminal device 110 can instruct a lower layer (e.g., MAC layer) to trigger a delay information report (or BSR). For the MAC layer, a delay information report (or BSR) is triggered when an instruction to trigger a delay information report (or BSR) is received from a higher layer (e.g., PDCP layer). In some embodiments, the trigger conditions for a BSR are specified in Table 1 below. [Table 1]

[0062] In some embodiments, all SDUs / PDUs belonging to the same PDU set may share the same arrival time from the upper layer (equal to the arrival time of the first SDU / PDU belonging to the PDU set), and therefore may have the same delay or remaining delay budget.

[0063] In some embodiments, when a BSR (e.g., a delay BSR) is triggered because the delay of at least one data packet exceeds a corresponding delay threshold (or the remaining delay budget of at least one data packet is less than a corresponding budget threshold), terminal device 110 may include a delay buffer size in the reported BSR. In some embodiments, the delay buffer size may be determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is less than a second budget threshold. The second delay threshold may be the same as or different from the first delay threshold that triggers the BSR, and similarly, the second budget threshold may be the same as or different from the first budget threshold that triggers the BSR. In some examples, the calculation of the delay buffer size at the PDCP layer is specified in Table 2 below, and the calculation of the delay buffer size at the radio link control (RLC) layer is specified in Table 3 below. [Table 2] [Table 3]

[0064] Note that "delay exceeds threshold" in Table 2 and / or Table 3 can also be replaced with "remaining delay budget is less than threshold."

[0065] In some embodiments, when delay information is included in a BSR (sometimes referred to as a "first BSR"), which may be referred to as a delayed BSR as described above, this BSR may be defined to include a remaining delay budget or reference time (e.g., earliest arrival time t0). The remaining delay budget is the first result of subtracting a first time interval from the delay budget, e.g., t PDB -(t3-t0), the second result of subtracting a second time interval from the delay budget, e.g., t PDB -(t1-t0), or a first time interval, e.g., t3-t0, or a second time interval, e.g., t1-t0. In some embodiments, this BSR may additionally or alternatively include a delay buffer size. In some embodiments, this BSR may additionally or alternatively include an indication of whether delay information and / or a delay buffer size is included in the first BSR. In some embodiments, the first BSR may include a BSR MAC CE.

[0066] In some embodiments, the delay information and / or delay buffer size is reported in a first BSR (e.g., BSR MAC CE) for each LCG. The first BSR may include a first field indicating an identifier of the LCG for which the delay information and / or delay buffer size is reported. The identifier of the LCG may be included, for example, in the BSR MAC CE. In some embodiments, the MAC subheader may include a logical channel identity (LCID) or an extended LCID (eLCID) value to identify the new BSR MAC CE.

[0067] In some embodiments, the first BSR may include a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across the logical channels of the LCG. For example, the remaining delay budget field in the first BSR may indicate the remaining delay budget of a data packet (e.g., a PDCP SDU or PDU set) having the shortest remaining delay budget across all logical channels of the LCG after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure). This field may be an index to a delay table. In another example, the earliest arrival time in the first BSR may indicate the arrival time of the earliest data packet (e.g., a PDCP SDU or PDU set) across all logical channels of the LCG after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure).

[0068] In some embodiments, the first BSR may further include a third field indicating a delay buffer size for at least one data packet whose delay exceeds the second delay threshold or whose remaining delay budget is lower than the second budget threshold across the logical channels of the LCG. For example, the delay buffer size field in the first BSR may indicate the total amount of available data that exceeds the delay threshold (or is lower than the budget threshold) according to a data volume calculation procedure (e.g., according to Table 2 and / or Table 3 above) across all logical channels of the LCG after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure). The amount of data may be indicated in number of bytes. The buffer size calculation may not take into account the size of the RLC header and MAC subheader.

[0069] In some embodiments, the first BSR may further include a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR. This fourth field is a new field introduced in the BSR and indicates whether 1) only legacy buffer size, or 2) only delay buffer size and / or remaining delay budget (or earliest arrival time), or 3) both should be reported for the LCG. In some embodiments, the reserved (R) field (e.g., reserved bit) in the MAC header may be reused to indicate whether delay buffer size and / or remaining delay budget (or earliest arrival time) are included in the corresponding BSR.

[0070] The fields defined in the delayed BSR MAC CE are defined as shown in Table 4. [Table 4]

[0071] 4A-4C show example formats of a BSR MAC CE according to some embodiments of the present disclosure. Note that the size of each field is not specified in the figures and may vary. These figures are provided as illustrative examples only.

[0072] FIG. 4A shows an example 410 of BSR MAC CE Format 1. In this example, the LCG ID field identifies the LCG for which buffer status is being reported in the BSR MAC CE. As shown, eight bits for eight LCGs (LCG0, LCG1, ..., LCG7) are identified in the BSR, with one or more bits set to the value "1" for one or more LCGs for which buffer status is being reported and bits for other LCGs for which buffer status is not being reported set to the value "0." The Buffer Size field identifies the total amount of data available across all logical channels of the logical channel group after the MAC PDU is constructed. The amount of data is given in bytes. If the LCG ID field indicates that buffer status is being reported for m LCGs, there may be m Buffer Size fields.

[0073] 4A, the buffer size field in the BSR may be followed by optional fields for delay buffer size and remaining delay budget or earliest arrival time. For each LCG of the m LCGs for which buffer status is being reported, the delay buffer size field (if included) and remaining delay budget or earliest arrival time field (if included) may be adjacently located.

[0074] Figure 4B shows an example 420 of BSR MAC CE format 2. Unlike the example of Figure 4A, in the example of Figure 4B, the buffer size field, delay buffer size field (if included), and remaining delay budget or earliest arrival time field (if included) for one LCG may be arranged as consecutive fields, followed by three similar fields for another LCG.

[0075] 4C shows an example 430 of a shortened BSR MAC CE, BSR MAC CE Format 3. In this example, the LCG ID field identifies the LCG, and the buffer size field indicates the corresponding buffer size for the identified LCG. Additionally, a delay buffer size field (if included) and a remaining delay budget or earliest arrival time field (if included) for the identified LCG may be included immediately after the buffer size field.

[0076] In some embodiments, the delay information and / or delay buffer size may be reported in a first BSR (e.g., BSR MAC CE) for each LCH. The first BSR may include a first field indicating an identifier of the LCH for which the delay information and / or delay buffer size is being reported. In some embodiments, the identifier of the LCH may be included in, for example, the BSR MAC CE. In some embodiments, the MAC subheader may include an LCID or eLCID value to identify the new BSR MAC CE. In some embodiments, a logical channel ID field may be included in the first BSR to identify the logical channel instance for which the delay buffer size is being reported. In some embodiments, an LCID i field may be included in the first BSR and may be mapped to the logical channel instance for which the delay buffer size is being reported.

[0077] In some embodiments, the first BSR may include a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time for the LCH. For example, the remaining delay budget field in the first BSR may indicate the remaining delay budget of the UL packet (e.g., PDCP SDU or PDU set) having the shortest remaining delay budget for the corresponding logical channel after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure). This field may be an index to a delay table. In another example, the earliest arrival time in the first BSR may indicate the arrival time of the earliest data packet (e.g., PDCP SDU or PDU set) for the corresponding logical channel after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure).

[0078] In some embodiments, the first BSR may further include a second field indicating a delay buffer size for at least one data packet for the corresponding LCH whose delay exceeds the second delay threshold or whose remaining delay budget is lower than the second budget threshold. For example, the delay buffer size field in the first BSR may indicate the total amount of available data that exceeds (or is lower than) the threshold according to the data volume calculation procedure (e.g., according to Table 2 and / or Table 3 above) for the corresponding logical channel after the MAC PDU is constructed (i.e., after the logical channel prioritization procedure). The data amount is indicated in number of bytes. The sizes of the RLC header and MAC subheader are not taken into account in the buffer size calculation.

[0079] In some embodiments, the first BSR may further include a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR. This fourth field is a new field introduced in the BSR and indicates whether 1) only legacy buffer size, or 2) only delay buffer size and / or remaining delay budget (or earliest arrival time), or 3) both should be reported for the LCH. In some embodiments, the reserved (R) field (e.g., reserved bit) in the MAC header may be reused to indicate whether delay buffer size and / or remaining delay budget (or earliest arrival time) are included in the corresponding BSR.

[0080] The fields defined in the delayed BSR MAC CE are defined as shown in Table 5. [Table 5]

[0081] 5A-5C show example formats of a BSR MAC CE according to some embodiments of the present disclosure. Note that the size of each field is not specified in the figures and may vary. These figures are provided as illustrative examples only.

[0082] FIG. 5A shows an example BSR MAC CE Format 1 510. In this example, the LCG ID field (optional) identifies the LCG for which the buffer status is being reported, and the buffer size field indicates the corresponding buffer size for the identified LCG. Additionally, the BSR includes a logical channel ID field to identify the logical channel instance for which the delay buffer size and / or delay information is being reported. The delay buffer size field (if included) and remaining delay budget or earliest arrival time field (if included) of the identified LCG for the corresponding logical channel may immediately follow the logical channel ID field. If information for multiple logical channels is being reported, similar logical channel ID, delay buffer size, and remaining delay budget or earliest arrival time fields may be included in the BSR. In the example of FIG. 5A, it is assumed that delay buffer sizes and / or delay information for a total of n logical channels are being reported. In this example, the Delay Buffer Size field (if included) and the remaining delay budget or earliest arrival time field (if included) for an LCH are placed as consecutive fields after the Logical Channel ID field, and may be followed by another Logical Channel ID field (if present).

[0083] FIG. 5B shows an example 520 of a BSR MAC CE format 2. In this example, the LCID i field identifies the LCH for which delay buffer size and / or delay information is being reported. As shown, the BSR includes a field containing 8 bits for eight LCIDs (LCID0, LCID1, ..., LCG7), where one or more bits for one or more LCHs for which delay buffer size and / or delay information is being reported are set to a value of "1," and bits for other LCHs for which delay buffer size and / or delay information is not being reported are set to a value of "0." If the LCID field indicates that the buffer status of m LCHs is being reported, there may be m delay buffer size fields and m remaining delay budget or earliest arrival time fields. In this example, the delay buffer size field (if included) and remaining delay budget or earliest arrival time field (if included) for one LCH may be arranged as consecutive fields, followed by two similar fields for another LCH.

[0084] FIG. 5C shows an example BSR MAC CE Former 3 530. In this example, the LCG ID and buffer size fields are similar to the example of FIG. 4A. To identify the logical channel instance for which delay buffer size and / or delay information is being reported, the BSR may be defined to further include a logical channel ID field. The delay buffer size field (if included) and remaining delay budget or earliest arrival time field (if included) for the identified LCG for the corresponding logical channel may immediately follow the logical channel ID field. If information for multiple logical channels is being reported, similar logical channel ID, delay buffer size, and remaining delay budget or earliest arrival time fields may be included in the BSR. In the example of FIG. 5C, it is assumed that delay buffer size and / or delay information for a total of n logical channels is being reported.

[0085] Although several example formats for the BSR MAC CE have been provided, various formats can be defined for carrying delay information, remaining delay budget or earliest arrival time, delay buffer size, and / or other delay-related information in accordance with embodiments of the present disclosure.

[0086] In some embodiments, a first BSR (e.g., a delayed BSR) containing delay information of a delay, a remaining delay budget or earliest arrival time, a delay buffer size, and / or other delay-related information may be transmitted with a relatively high priority. For example, the first BSR may be transmitted with a higher priority than a second BSR without delay information for the data packets. The second BSR may be, for example, a normal BSR or a periodic BSR. A trigger for reporting a BSR at the MC entity may be specified as shown in Table 6. [Table 6]

[0087] In some instances, discarding packets at the transmitter may invalidate a previous BSR and result in more resources being scheduled than necessary, resulting in increased power consumption and reduced overall cell capacity.

[0088] 6A illustrates an example timeline 610 depicting various events from the time the last BSR is transmitted to the time a new BSR is received by a network device. As illustrated, after the last BSR is transmitted and before a new BSR is generated and transmitted in accordance with a received UL grant, one or more data packets may be discarded due to the expiration of a corresponding discard timer or for other reasons (e.g., discarding low priority or important data during congestion).

[0089] Considering discarded data packets, some embodiments of the present disclosure propose to trigger a BSR when one or more data packets are discarded, particularly when one or more PDU sets are discarded. Generally, a PDU set may contain a relatively large amount of data, so discarding a PDU set or part of a PDU set may have a significant impact on buffer size. According to embodiments of the present disclosure, triggering a BSR when one or more data packets are discarded can avoid scheduling more resources than necessary, thereby saving power consumption and increasing overall cell capacity.

[0090] In some embodiments, if at least one buffered data packet (e.g., at least one PDCP SDU or PDU set) is discarded by a PDCP entity in the PDCP layer of terminal device 110, the PDCP entity may send a first indication of packet discard or a second indication to trigger a BSR to a lower layer, e.g., the MAC layer. That is, the packet discard may be considered a BSR-triggering event.

[0091] In some embodiments, at the MAC layer, upon receiving a first indication to discard a packet or a second indication to trigger a BSR from the PDCP layer, the MAC entity of terminal device 110 may determine a buffer size of the LCH or LCG corresponding to the at least one discarded buffered data packet. The MAC entity may trigger a BSR to be reported if the calculated buffer size satisfies one or more conditions.

[0092] In some embodiments, if the buffer size is different (e.g., smaller) than the last reported buffer size for the LCH or LCG (e.g., in the last BSR), the MAC entity of the terminal device 110 may trigger a BSR (e.g., a delayed BSR or other type of BSR).

[0093] In some embodiments, if the buffer size is different (e.g., smaller) than the last reported buffer size for the LCH or LCG (e.g., in the last BSR) and if the first quantization level of the buffer size is different from the second quantization level of the last reported buffer size, the MAC entity of terminal device 110 can trigger a BSR (e.g., a delayed BSR or another type of BSR). In general, terminal device 110 can map the buffer size or buffer sizes to certain quantization levels (also referred to as “buffer size levels”) according to a mapping table. This mapping table can include specific indices mapped to specific buffer size values. Because the indices (or quantization levels) can map to a specific range of buffer sizes, it makes sense for the MAC entity to trigger a BSR if the quantization level changes after a packet discard (e.g., the buffer size index in the mapping table is different). In some embodiments, the triggered BSR can be a regular BSR.

[0094] In some embodiments, if the index of the buffer size table is small, the quantization step for the buffer size is small, and therefore a reference quantization level (e.g., an index mapped to a buffer size) may be set for terminal device 110. If the quantization level of the last reported buffer size is equal to or greater than the reference quantization level, the MAC entity of terminal device 110 may trigger a BSR when it determines that the buffer size is different (e.g., smaller) than the last reported buffer size for the LCH or LCG (e.g., in the last BSR) and the first quantization level of the buffer size is different from the second quantization level of the last reported buffer size.

[0095] In some embodiments, alternatively or additionally, the MAC entity of terminal device 110 may trigger a BSR if the buffer size after packet discard is different (e.g., smaller) than the last reported buffer size for the LCH or LCG (e.g., in the last BSR) and if the difference between the buffer size and the last reported buffer size exceeds a difference threshold (and / or if the difference in quantization levels exceeds a certain difference threshold). The difference threshold may be configured.

[0096] In some embodiments, alternatively or additionally, the MAC entity of terminal device 110 may trigger a BSR if the buffer size after packet discard is equal to zero.

[0097] In some examples, as shown in timeline 620 of Figure 6B, during the period between the last reported BSR and the newly generated BSR, there may be one or more new transmissions carrying some data packets of the LCG or LCH before the new BSR is generated. If these data packets are not taken into account in the comparison of the last reported buffer size and the newly calculated buffer size, the difference between them will not be accurate.

[0098] In some embodiments, in addition to considering at least one discarded buffered data packet, the buffer size may be determined based on at least one data packet corresponding to the LCH or LCG transmitted after the last reported BSR. That is, when comparing the last reported buffer size and the newly calculated buffer size for the LCH or LCG, the size of data transmitted between the last reported BSR and the newly generated BSR may be considered. For example, the newly calculated buffer size may be compared to the "last reported buffer size" minus the "size of data transmitted between the last reported BSR and the newly generated BSR."

[0099] 7 illustrates a flowchart of a method 700 implemented in a terminal device according to some embodiments of the present disclosure. For ease of explanation, the method 700 is described from the perspective of the terminal device 110 of FIG.

[0100] In block 710, terminal device 110 transmits delay information for at least one data packet buffered at the terminal device to a network device (e.g., network device 120). The delay information indicates at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time when a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

[0101] In some embodiments, the reference time comprises an arrival time of at least one data packet at an access stratum (AS) layer.

[0102] In some embodiments, the delay budget for the at least one data packet is determined or configured at the air interface based on a value of a discard timer for the at least one packet.

[0103] In some embodiments, the terminal device 110 may receive configuration information from the network device indicating whether to report delay information for a data radio bearer (DRB), a logical channel, a logical channel group (LCG), or a packet data convergence protocol (PDCP) entity, and may transmit the delay information to the network device pursuant to a determination that the configuration information indicates that the delay information is to be reported.

[0104] In some embodiments, following a determination that the delay of at least one data packet exceeds a first delay threshold or that the remaining delay budget for at least one data packet is lower than a first budget threshold, terminal device 110 may transmit delay information to a network device.

[0105] In some embodiments, the delay information is included in a first BSR, the first BSR further including at least one of a remaining delay budget, an earliest arrival time, a delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in the first BSR.

[0106] In some embodiments, the delay buffer size is determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold.

[0107] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel group (LCG) and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across the logical channels of the LCG. In some embodiments, the first BSR further includes at least one of a third field indicating a delay buffer size for at least one data packet having a delay above a second delay threshold or a remaining delay budget below a second budget threshold across the logical channels of the LCG, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0108] In some embodiments, the first BSR includes a first field indicating a logical channel (LCH) identifier and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time for the LCH, and further includes at least one of a third field indicating a delay buffer size for at least one data packet for the LCH whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0109] In some embodiments, the delay information is included in a first BSR, and the first BSR is transmitted with a higher priority than a second BSR without delay information for the data packets.

[0110] In some embodiments, following a determination that at least one buffered data packet has been discarded, terminal device 110 may transmit a first indication of packet discard or a second indication triggering a BSR from a Packet Data Convergence Protocol (PDCP) entity to a Medium Access Control (MAC) entity.

[0111] In some embodiments, upon receiving the first or second indication, the terminal device 110 may determine, by a MAC entity, a buffer size for the LCH or LCG corresponding to the at least one discarded buffered data packet, and trigger, by the MAC entity, a BSR to be reported according to at least one of the following determinations: the buffer size is different from a last reported buffer size for the LCH or LCG; a first quantization level of the buffer size is different from a second quantization level of the last reported buffer size; the second quantization level is greater than or equal to a reference quantization level; the difference between the buffer size and the last reported buffer size exceeds a difference threshold; and the buffer size is equal to zero.

[0112] In some embodiments, the buffer size is determined based on at least one data packet corresponding to an LCH or LCG transmitted after the last reported BSR and at least one buffered data packet that was discarded.

[0113] 8 illustrates a flowchart of a method 800 implemented in a network device according to some embodiments of the present disclosure. For ease of explanation, the method 800 is described in terms of the network device 120 of FIG.

[0114] At block 810, the network device 120 receives from the terminal device delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time when a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from the delay budget for the at least one data packet, a second time interval between the arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from the delay budget for the at least one data packet. At block 820, the network device 120 determines a remaining delay budget for the at least one data packet based on the delay information.

[0115] In some embodiments, the reference time comprises an arrival time of at least one data packet at an access stratum (AS) layer.

[0116] In some embodiments, following a determination that the delay information indicates a reference time, the network device 120 may determine a remaining delay budget by subtracting a third time interval between the reference time and the time the BSR was received from the delay budget for the at least one data packet.

[0117] In some embodiments, following a determination that the delay information indicates the first outcome, network device 120 may determine the remaining delay budget by subtracting the fourth time interval between the time the BSR was transmitted and the time the BSR was received from the first outcome.

[0118] In some embodiments, following a determination that the delay information indicates the first time interval, the network device 120 may determine a remaining delay budget by subtracting the sum of the first time interval and the fourth time interval from the delay budget.

[0119] In some embodiments, following a determination that the delay information indicates the second outcome, network device 120 may determine the remaining delay budget by subtracting from the second outcome the fifth time interval between the time resources for transmission of the BSR were granted and the time the BSR was received.

[0120] In some embodiments, following a determination that the delay information indicates the second time interval, the network device 120 may determine the remaining delay budget by subtracting the sum of the second time interval and the fifth time interval from the delay budget.

[0121] In some embodiments, the delay budget for the at least one data packet is determined or configured at the air interface based on a value of a discard timer for the at least one packet.

[0122] In some embodiments, the network device 120 may further transmit configuration information to the terminal device indicating whether to report delay information for a data radio bearer (DRB), a logical channel, a logical channel group (LCG), or a packet data convergence protocol (PDCP) entity corresponding to the at least one data packet. Pursuant to determining that the configuration information indicates that delay information is to be reported, the network device 120 may transmit the delay information to the terminal device.

[0123] The delay information is included in a first BSR, the first BSR further including at least one of a remaining delay budget, an earliest arrival time, a delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in the first BSR.

[0124] In some embodiments, the delay buffer size is determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold.

[0125] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel group (LCG), a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across the logical channels of the LCG, a third field indicating a delay buffer size for at least one data packet having a delay above a second delay threshold or a remaining delay budget below a second budget threshold across the logical channels of the LCG, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0126] In some embodiments, the first BSR includes a first field indicating a logical channel (LCH) identifier and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time for the LCH, and further includes at least one of a third field indicating a delay buffer size for at least one data packet for the LCH whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0127] 9 is a schematic block diagram of an apparatus 900 suitable for implementing embodiments of the present disclosure. The apparatus 900 may be considered another exemplary implementation of any of the apparatuses shown in FIG. 1. Thus, the apparatus 900 may be implemented in, or at least as part of, the terminal device 110 or the network device 120.

[0128] As shown, the apparatus 900 comprises a processor 910, a memory 920 coupled to the processor 910, a suitable transmitter (TX) / receiver (RX) 940 coupled to the processor 910, and a communication interface coupled to the TX / RX 940. The memory 910 stores at least a portion of a program 930. The TX / RX 940 is for bidirectional communication. The TX / RX 940 has at least one antenna to facilitate communication, although in practice the access nodes referred to in this disclosure may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as, for example, an X2 / Xn interface for bidirectional communication between eNBs / gNBs, an S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and an eNB / gNB, an Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0129] The program 930 is assumed to include program instructions that, when executed by the associated processor 910, cause the device 900 to operate in accordance with embodiments of the present disclosure, as described herein with reference to Figures 1-8. Embodiments of the present disclosure may be implemented by computer software executable by the processor 910 of the device 900, by hardware, or by a combination of software and hardware. The processor 910 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 910 and the memory 920 may form a processing means 950 suitable for implementing various embodiments of the present disclosure.

[0130] Memory 920 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 920 is shown in device 900, device 900 may have multiple physically distinct memory modules. Processor 910 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 900 may have multiple processors, such as application-specific integrated circuit chips that are time-slaved to a clock that synchronizes the main processor.

[0131] In some embodiments, the terminal device comprises circuitry configured to: transmit, to the network device, delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of: a reference time for buffering the at least one data packet; a first time interval between an arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval from a delay budget for the at least one data packet; a second time interval between an arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from a delay budget for the at least one data packet. According to embodiments of the present disclosure, the circuitry may be configured to perform any of the methods implemented by the terminal device as described above.

[0132] In some embodiments, the network device comprises circuitry configured to: receive from the terminal device delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from the delay budget for the at least one data packet; and determine a remaining delay budget for the at least one data packet based on the delay information. According to embodiments of the present disclosure, the circuitry may be configured to perform any of the methods implemented by the network device as described above.

[0133] The term "circuitry" as used in this disclosure may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As another example, a circuit may be any portion of a hardware processor with software, where the hardware processor includes digital signal processor(s), software, and memory(s) that work together to cause a device, such as a terminal device or network device, to perform various functions. As yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software / firmware to operate, but the software may not be present when not necessary for operation. As used in this disclosure, the term circuitry also includes simply a hardware circuit or processor(s) or portion of a hardware circuit or processor(s) and its (or their) associated software and / or firmware implementation.

[0134] In summary, embodiments of the present disclosure provide the following aspects:

[0135] In one aspect, the terminal device comprises a processor configured to cause the terminal device to transmit to the network device delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering of the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

[0136] In some embodiments, the reference time comprises an arrival time of at least one data packet at an access stratum (AS) layer.

[0137] In some embodiments, the delay budget for the at least one data packet is determined or configured at the air interface based on a value of a discard timer for the at least one packet.

[0138] In some embodiments, the processor is further configured to cause the terminal device to receive configuration information from the network device indicating whether to report delay information for a data radio bearer (DRB), a logical channel, a logical channel group (LCG), or a packet data convergence protocol (PDCP) entity, and, in accordance with a determination that the configuration information indicates that the delay information is to be reported, transmit the delay information to the network device.

[0139] In some embodiments, the processor is further configured to cause the terminal device to transmit delay information to the network device in accordance with a determination that the delay of at least one data packet exceeds a first delay threshold or that the remaining delay budget for at least one data packet is lower than the first budget threshold.

[0140] In some embodiments, the delay information is included in a first BSR, the first BSR further including at least one of a remaining delay budget, an earliest arrival time, a delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in the first BSR.

[0141] In some embodiments, the delay buffer size is determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold.

[0142] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel group (LCG) and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across the logical channels of the LCG, and the first BSR further includes at least one of a third field indicating a delay buffer size for at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is lower than the second budget threshold across the logical channels of the LCG, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0143] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel (LCH) and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time for the LCH, and the first BSR further includes at least one of a third field indicating a delay buffer size for at least one data packet for the LCH whose delay exceeds a second delay threshold or whose remaining delay budget is lower than the second budget threshold, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0144] In some embodiments, the delay information is included in a first BSR, and the first BSR is transmitted with a higher priority than a second BSR without delay information for the data packets.

[0145] In some embodiments, the processor is further configured to cause the terminal device to, in accordance with a determination that at least one buffered data packet has been discarded, send a first indication of packet discard or a second indication triggering a BSR from a Packet Data Convergence Protocol (PDCP) entity to a Medium Access Control (MAC) entity.

[0146] In some embodiments, the processor is further configured to, upon receiving the first instruction or the second instruction, cause the terminal device to: determine, by the MAC entity, a buffer size for the LCH or LCG corresponding to the at least one buffered data packet that was discarded; and trigger, by the MAC entity, a reported BSR according to at least one of the following determinations: the buffer size is different from a last reported buffer size for the LCH or LCG; a first quantization level of the buffer size is different from a second quantization level of the last reported buffer size; the second quantization level is greater than or equal to a reference quantization level; a difference between the buffer size and the last reported buffer size exceeds a difference threshold; and the buffer size is equal to zero.

[0147] In some embodiments, the buffer size is determined based on at least one data packet corresponding to an LCH or LCG transmitted after the last reported BSR and at least one buffered data packet that was discarded.

[0148] In one aspect, a network device comprises a processor configured to: receive from the terminal device delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of: a reference time for buffering of the at least one data packet; a first time interval between an arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval from a delay budget for the at least one data packet; a second time interval between an arrival time of the at least one data packet and a time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; and determine a remaining delay budget for the at least one data packet based on the delay information.

[0149] In some embodiments, the reference time comprises an arrival time of at least one data packet at an access stratum (AS) layer.

[0150] In some embodiments, the processor is further configured to cause the network device to: determine a remaining delay budget by subtracting a third time interval between the reference time and the time the BSR was received from the delay budget for the at least one data packet in accordance with a determination that the delay information indicates the reference time; determine a remaining delay budget by subtracting a fourth time interval between the time the BSR was transmitted and the time the BSR was received from the first result in accordance with a determination that the delay information indicates a first result; determine a remaining delay budget by subtracting a sum of the first and fourth time intervals from the delay budget in accordance with a determination that the delay information indicates the first time interval; determine a remaining delay budget by subtracting a fifth time interval between the time resources for transmitting the BSR were granted and the time the BSR was received from the second result in accordance with a determination that the delay information indicates a second result; and determine a remaining delay budget by subtracting a sum of the second and fifth time intervals from the delay budget in accordance with a determination that the delay information indicates a second time interval.

[0151] In some embodiments, the delay budget for the at least one data packet is determined or configured at the air interface based on a value of a discard timer for the at least one packet.

[0152] In some embodiments, the processor is further configured to cause the network device to: send configuration information to the terminal device indicating whether to report delay information for a data radio bearer (DRB), logical channel, logical channel group (LCG), or packet data convergence protocol (PDCP) entity corresponding to the at least one data packet; and, in accordance with a determination that the configuration information indicates that the delay information is to be reported, send the delay information to the terminal device.

[0153] The delay information is included in a first BSR, the first BSR further including at least one of a remaining delay budget, an earliest arrival time, a delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in the first BSR.

[0154] In some embodiments, the delay buffer size is determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold.

[0155] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel group (LCG) and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across the logical channels of the LCG, and the first BSR further includes at least one of a third field indicating a delay buffer size for at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is lower than the second budget threshold across the logical channels of the LCG, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0156] In some embodiments, the first BSR includes a first field indicating an identifier of a logical channel (LCH) and a second field indicating delay information for at least one data packet having the shortest remaining delay budget or earliest reference time for the LCH, and the first BSR further includes at least one of a third field indicating a delay buffer size for at least one data packet for the LCH whose delay exceeds a second delay threshold or whose remaining delay budget is lower than the second budget threshold, and a fourth field indicating whether delay information and / or delay buffer size is included in the first BSR.

[0157] In one aspect, a communication method includes transmitting delay information from the terminal device to a network device for at least one data packet buffered at the terminal device, the delay information indicating at least one of a reference time for buffering of the at least one data packet, a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted, a first result of subtracting the first time interval from a delay budget for the at least one data packet, a second time interval between an arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR, and a second result of subtracting the second time interval from a delay budget for the at least one data packet.

[0158] In one aspect, a communication method includes receiving, from a terminal device at a network device, delay information for at least one data packet buffered at the terminal device, the delay information indicating at least one of: a reference time for buffering of the at least one data packet; a first time interval between an arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval between the arrival time of the at least one data packet and a time at which a buffer status report (BSR) is transmitted from a delay budget for the at least one data packet; a second time interval between the arrival time of the at least one data packet and a time at which resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; and determining a remaining delay budget for the at least one data packet based on the delay information.

[0159] In one aspect, a terminal device comprises at least one processor and at least one memory coupled to the at least one processor and having instructions stored therein that, when executed by the at least one processor, cause the device to perform the method implemented by the terminal device.

[0160] In one aspect, a network device comprises at least one processor and at least one memory coupled to the at least one processor and having instructions stored thereon that, when executed by the at least one processor, cause the device to perform the method implemented by the network device.

[0161] In one aspect, a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform the above-described method implemented by the above-described terminal device.

[0162] In one aspect, a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform the above-described method implemented by the above-described network device.

[0163] In one aspect, a computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the above method implemented by the above terminal device.

[0164] In one aspect, a computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the above method implemented by the above network device.

[0165] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or some other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described in this disclosure may be implemented in, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller, or other computing device, or some combination thereof.

[0166] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (e.g., computer-executable instructions included in program modules) that execute on a device by a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 8-9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various embodiments. The machine-executable instructions for the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.

[0167] Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that when executed by the processor or controller, the program code performs the functions / acts specified in the flowcharts and / or block diagrams. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0168] The program code may be embodied in a machine-readable medium, which may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of machine-readable storage media include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0169] Furthermore, although operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or sequentially, or that all of the operations shown be performed, to achieve desirable results. In certain situations, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above description, these should not be construed as limiting the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

[0170] Although the present disclosure has been described in language specific to structural features and / or methodological operations, it is to be understood that the present disclosure, which is limited to the appended claims, is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as example forms of implementing the claims.

Claims

1. Delay information for at least one data packet buffered at a terminal device, a reference time for buffering said at least one data packet; a first time interval between the arrival time of the at least one data packet and the time a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval from the delay budget for the at least one data packet; a second time interval between the arrival time of the at least one data packet and the time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; transmitting the delay information to a network device indicative of at least one of: a processor configured to cause the terminal device to Terminal device.

2. the reference time comprises an arrival time of the at least one data packet at an access stratum (AS) layer; The delay budget for the at least one data packet is determined based on a value of a discard timer for the at least one packet or is configured at a wireless interface.

10. The apparatus of claim 1.

3. The processor: receiving configuration information from the network device indicating whether to report delay information for a data radio bearer (DRB), a logical channel, a logical channel group (LCG), or a packet data convergence protocol (PDCP) entity; transmitting the delay information to the network device in accordance with a determination that the configuration information indicates that the delay information is to be reported; The terminal device is further configured to:

10. The apparatus of claim 1.

4. The processor: transmitting the delay information to the network device in accordance with a determination that the delay of the at least one data packet exceeds a first delay threshold or that a remaining delay budget for the at least one data packet is less than a first budget threshold; The terminal device is further configured to:

10. The apparatus of claim 1.

5. The delay information is included in a first BSR, the first BSR comprising: the remaining delay budget, Earliest arrival time, Delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in a first BSR; and further comprising at least one of the delay buffer size is determined based on at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold.

10. The apparatus of claim 1.

6. the first BSR includes a first field indicating an identifier of a logical channel group (LCG) and a second field indicating the delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across logical channels of the LCG; The first BSR comprises: a third field indicating the delay buffer size for at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold across a logical channel of the LCG; and a fourth field indicating whether the delay information and / or the delay buffer size is included in the first BSR.

6. The apparatus of claim 5.

7. the first BSR includes a first field indicating an identifier of a logical channel (LCH) and a second field indicating the delay information for at least one data packet having a shortest remaining delay budget or an earliest reference time for the LCH; The first BSR comprises: a third field indicating the delay buffer size for at least one data packet for which the delay exceeds a second delay threshold or the remaining delay budget is below a second budget threshold for the LCH; and a fourth field indicating whether the delay information and / or the delay buffer size is included in the first BSR.

6. The apparatus of claim 5.

8. the delay information is included in a first BSR, and the first BSR is transmitted with a higher priority than a second BSR without delay information for the data packet; 10. The apparatus of claim 1.

9. The processor: sending, from a Packet Data Convergence Protocol (PDCP) entity to a Medium Access Control (MAC) entity, the first indication of packet discard or the second indication triggering a BSR according to determining that at least one buffered data packet has been discarded; The terminal device is further configured to:

10. The apparatus of claim 1.

10. The processor: Upon receiving the first indication or the second indication, determining, by the MAC entity, a buffer size for the LCH or LCG corresponding to the at least one buffered data packet that has been discarded; the buffer size is different from the last reported buffer size for the LCH or LCG; a first quantization level of the buffer size is different from a second quantization level of the last reported buffer size; the second quantization level is equal to or greater than a reference quantization level; the difference between the buffer size and the last reported buffer size exceeds a difference threshold; and said buffer size being equal to zero; triggering a BSR to be reported by said MAC entity according to at least one of the determinations of The terminal device is further configured to:

10. The apparatus of claim 9.

11. The buffer size is determined based on at least one data packet corresponding to the LCH or the LCG transmitted after a last reported BSR and the at least one buffered data packet that has been discarded.

11. The apparatus of claim 10.

12. Delay information for at least one data packet buffered at a terminal device, a reference time for buffering said at least one data packet; a first time interval between the arrival time of the at least one data packet and the time a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval from the delay budget for the at least one data packet; a second time interval between the arrival time of the at least one data packet and the time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; receiving from a terminal device the delay information indicating at least one of: determining a remaining delay budget for the at least one data packet based on the delay information; a processor configured to cause the network device to Network equipment.

13. The processor: determining the remaining delay budget by subtracting a third time interval between the reference time and the time the BSR was received from the delay budget for the at least one data packet in accordance with determining that the delay information indicates the reference time; determining the remaining delay budget by subtracting a fourth time interval between the time the BSR was transmitted and the time the BSR was received from the first result in accordance with determining that the delay information indicates the first result; and determining the remaining delay budget by subtracting the sum of the first time interval and the fourth time interval from the delay budget in response to determining that the delay information indicates the first time interval; determining the remaining delay budget by subtracting a fifth time interval between the time the resources for transmission of the BSR were granted and the time the BSR was received from the second result in accordance with determining that the delay information indicates the second result; and determining the remaining delay budget by subtracting the sum of the second time interval and the fifth time interval from the delay budget in response to determining that the delay information indicates the second time interval; and further configured to cause the network device to:

13. The apparatus of claim 12.

14. The processor: transmitting, to the terminal device, configuration information indicating whether to report delay information for a data radio bearer (DRB), a logical channel, a logical channel group (LCG), or a packet data convergence protocol (PDCP) entity corresponding to the at least one data packet; receiving the delay information from the terminal device in accordance with a determination that the configuration information indicates that the delay information is to be reported; and further configured to cause the network device to:

13. The apparatus of claim 12.

15. The delay information is included in a first BSR, the first BSR comprising: the remaining delay budget, Earliest arrival time, Delay buffer size, and an indication of whether the delay information and / or the delay buffer size is included in a first BSR; further comprising at least one of:

13. The apparatus of claim 12.

16. the first BSR includes a first field indicating an identifier of a logical channel group (LCG) and a second field indicating the delay information for at least one data packet having the shortest remaining delay budget or earliest reference time across logical channels of the LCG; The first BSR comprises: a third field indicating the delay buffer size for at least one data packet whose delay exceeds a second delay threshold or whose remaining delay budget is below a second budget threshold across a logical channel of the LCG; and a fourth field indicating whether the delay information and / or the delay buffer size is included in the first BSR; further comprising at least one of:

16. The apparatus of claim 15.

17. the first BSR includes a first field indicating an identifier of a logical channel (LCH) and a second field indicating the delay information for at least one data packet having a shortest remaining delay budget or an earliest reference time for the LCH; The first BSR comprises: a third field indicating the delay buffer size for at least one data packet for which the delay exceeds a second delay threshold or the remaining delay budget is below a second budget threshold for the LCH; and a fourth field indicating whether the delay information and / or the delay buffer size is included in the first BSR; further comprising at least one of:

16. The apparatus of claim 15.

18. Delay information for at least one data packet buffered at a terminal device, a reference time for buffering said at least one data packet; a first time interval between the arrival time of the at least one data packet and the time a buffer status report (BSR) is transmitted; a first result of subtracting the first time interval from the delay budget for the at least one data packet; a second time interval between the arrival time of the at least one data packet and the time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; transmitting the delay information indicating at least one of the following from the terminal device to the network device; A communication method including:

19. Delay information for at least one data packet buffered at a terminal device, a reference time for buffering said at least one data packet; a first time interval between the arrival time of the at least one data packet and the time a buffer status report (BSR) is transmitted; a first result of subtracting a first time interval between an arrival time of the at least one data packet and a time a buffer status report (BSR) is transmitted from a delay budget for the at least one data packet; a second time interval between the arrival time of the at least one data packet and the time when resources are granted for transmission of the BSR; and a second result of subtracting the second time interval from the delay budget for the at least one data packet; receiving, at a network device, the delay information indicating at least one of: determining a remaining delay budget for the at least one data packet based on the delay information; A communication method including:

20. 20. The method of claim 19, further comprising: storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method of claim 18 or 19; Computer-readable medium.

Images