Method and apparatus for PDU set delay status reporting

Abstract

Embodiments of the invention relate to methods and apparatus for delayed status reporting associated with a set of protocol data units (PDUs). In accordance with an embodiment of the present application, a user equipment (UE) comprises: a processor; and a transceiver coupled to the processor; and the processor is configured to: determine delay information associated with one or more sets of protocol data units (PDUs) received from an upper layer of the UE, wherein the delay information includes at least one of: a remaining PDU set delay budget; a PDU set buffer delay; the PDU set delays budget offset; or a first timing when PDUs within the one or more PDU sets are received from the upper layer; and transmitting a report including the delay information, wherein the report is at least one of: a delay budget report (DBR); a delay report (DR); a timing of arrival report (ATR); or an enhanced buffer status report (EBSR).

Description

Technical Field

[0001] Embodiments of the present application relate generally to wireless communication techniques, and more particularly to methods and apparatus for delay status reporting associated with a set of protocol data units (PDUs). Background Art

[0002] Extended Reality (XR) including Augmented Reality (AR) and Virtual Reality (VR) and Cloud Gaming (CG) bring a new promising category of connected devices, applications and services. As a potential work area of ​​3GPP (3rd Generation Partnership Project) Release 18, application and service awareness in the Radio Access Network (RAN) is one of the key features for improving the user experience of XR services. Currently, the details about the delay status report associated with a PDU set (e.g., frame) have not been discussed. Summary of the invention

[0003] Some embodiments of the present application also provide a user equipment (UE). The UE includes: a processor; and a transceiver coupled to the processor; and the processor is configured to: determine delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE, wherein the delay information includes at least one of the following: a remaining PDU set delay budget; a PDU set buffer delay; a PDU set delay budget offset; or a first timing when a PDU within the one or more PDU sets is received from the upper layer; and transmit a report including the delay information, wherein the report is at least one of the following: a delay budget report (DBR); a delay report (DR); an arrival timing report (ATR); or an enhanced buffer status report (EBSR).

[0004] In some embodiments, the delay information includes delay information associated with a first arriving PDU or a last arriving PDU of a PDU set in the one or more PDU sets. In the present application, the arriving PDU may be referred to as an arrived PDU.

[0005] In some embodiments, the remaining PDU set delay budget corresponds to a PDU set with a minimum delay budget among the one or more PDU sets; the PDU set buffer delay corresponds to a PDU set with a maximum buffer delay among the one or more PDU sets; or the first timing corresponds to a PDU set with an earliest arrival timing among the one or more PDU sets.

[0006] In some embodiments, the delay information includes delay information corresponding to a PDU set within the one or more PDU sets having a highest priority logical channel that is allowed to report the delay information in the LCG or in the MAC entity of the UE or in the UE.

[0007] In some embodiments, the delay information includes at least one of: delay information corresponding to a PDU set within the one or more PDU sets with a logical channel having or not having data available for transmission; or delay information corresponding to a PDU set within the one or more PDU sets in an LCG having or not having data available for transmission.

[0008] In some embodiments, the delay information is determined based on at least one of: a PDU set delay budget; a packet delay budget; a PDU set delay budget timer; a PDU set discard timer; an SDU discard timer; a PDU set delay budget offset; a reference time associated with the PDU set; or the first timing.

[0009] In some embodiments, the one or more PDU sets are received by an access stratum (AS) layer of the UE, and wherein the first timing includes at least one of: the arrival timing at the AS layer of the first arriving PDU in the one or more PDU sets from the upper layer; or the arrival timing at the AS layer of a PDU in the one or more PDU sets from the upper layer; or the arrival timing at the AS layer of the last arriving PDU in the one or more PDU sets from the upper layer.

[0010] In some embodiments, in order to determine the remaining PDU set delay budget, the processor of the UE is configured to: start the PDU set delay budget timer when a PDU in the PDU set is received from the upper layer; stop the PDU set delay budget timer at the reference time; and determine the remaining length value of the PDU set delay budget timer.

[0011] In some embodiments, the reference time is: a timing of assembling a medium access control (MAC) PDU containing the delay information into a MAC PDU; or a timing of transmitting the report.

[0012] In some embodiments, the remaining PDU set delay budget is determined based on: the sum of the PDU set delay budget and the PDU set delay budget offset; or the sum of a remaining length value of the PDU set delay budget timer and the PDU set delay budget offset.

[0013] In some embodiments, the remaining PDU set delay budget is determined based on the PDU set delay budget, the first timing and the reference time; the remaining PDU set delay budget is determined based on the PDU set delay budget offset, the PDU set delay budget, the first timing and the reference time; or the PDU set buffer delay is determined based on the first timing and the reference time.

[0014] In some embodiments, the PDU set delay budget offset is received from the upper layer of the UE.

[0015] In some embodiments, the processor of the UE is configured to transmit an indication indicating a capability of the UE to support transmitting the report to the network via the transceiver.

[0016] In some embodiments, the processor of the UE is configured to receive a configuration related to the delay information from the network via the transceiver.

[0017] In some embodiments, the configuration includes at least one of: information for enabling transmission of the report; a trigger threshold associated with a trigger condition; a cancellation threshold associated with a cancellation condition; the PDU set delay budget; the length of the PDU set delay budget timer; the length of the PDU set discard timer; the length of the SDU discard timer; the length of a periodic timer associated with the report; the length of a retransmission timer associated with the report.

[0018] In some embodiments, the configuration is associated with: an LCH that allows reporting of the delay information; an LCG that allows reporting of the delay information; a data radio bearer (DRB) that allows reporting of the delay information; or a MAC entity of the UE that allows reporting of the delay information.

[0019] In some embodiments, the report includes at least one of: information of a logical channel (LCH) corresponding to the delay information; information of a logical channel group (LCG) corresponding to the delay information; information of a data radio bearer (DRB) corresponding to the delay information; or information associated with the one or more PDU sets.

[0020] In some embodiments, the processor of the UE is configured to trigger the reporting based on a triggering condition.

[0021] In some embodiments, the trigger condition includes at least one of the following: when the first arriving PDU in the one or more PDU sets is received from the upper layer; when a PDU with an important indication in the one or more PDU sets is received from the upper layer; when the last arriving PDU in the one or more PDU sets is received from the upper layer; when a periodic timer associated with the report expires; when a retransmission timer associated with the report expires; when the PDU set delay budget is less than or equal to a first trigger threshold associated with the trigger condition; when the PDU set delay is greater than or equal to a second trigger threshold associated with the trigger condition; or when the total number of padding bits of the allocated uplink (UL) resources is greater than or equal to the bit size of the MAC sub-PDU containing the report; or when a request is received from the upper layer; or when a dynamic report request is received from the network.

[0022] In some embodiments, the report is transmitted in response to non-satisfaction of a cancellation condition.

[0023] In some embodiments, the processor of the UE is configured to cancel the reporting based on a cancellation condition.

[0024] In some embodiments, the cancellation condition includes at least one of the following: when the remaining PDU set delay budget is less than or equal to a first cancellation threshold; when the PDU set delay is greater than or equal to a second cancellation threshold; when a PDU set delay budget timer expires; when an SDU discard timer of a PDU within the PDU set expires; when a PDU set discard timer expires; when a MAC PDU containing the report is transmitted, wherein the report is triggered before or at the timing of assembling the MAC PDU; when the padding bits of the allocated uplink (UL) resources are insufficient to accommodate the MAC PDU; or when the padding bits of the allocated UL resources are insufficient to accommodate the MAC PDU, and the report is triggered when the highest logical channel priority is less than or equal to the logical channel priority of all available pending data.

[0025] In some embodiments, the MAC sub-PDU containing the report carries at least one of: a remaining PDU set delay budget associated with a PDU set within the one or more PDU sets for one LCH; two or more remaining PDU set delay budgets associated with two or more PDU sets within the one or more PDU sets for the one LCH; multiple remaining PDU set delay budgets associated with multiple PDU sets within the one or more PDU sets for two or more LCHs; a remaining PDU set delay budget associated with the one or more PDU sets for one LCG; two or more remaining PDU set delay budgets associated with two or more PDU sets within the one or more PDU sets of the one LCG; multiple remaining PDU set delay budgets associated with multiple PDU sets within the one or more PDU sets used for two or more LCGs; PDU set delay budget offsets associated with PDU sets within the one or more PDU sets used for the one LCH or for the one LCG; or multiple remaining PDU set delay budget offsets associated with multiple PDU sets within the one or more PDU sets used for the two or more LCHs or for the two or more LCGs.

[0026] In some embodiments, in response to determining that the delay information includes one or more delay information for one or more LCHs or one or more LCGs, the processor of the UE is configured to prioritize the one or more delay information, and wherein the report includes all or a portion of the prioritized one or more delay information.

[0027] In some embodiments, in response to the allocated uplink (UL) resources having insufficient padding bits to accommodate one or more delay information included in the delay information for one or more LCHs or one or more LCGs, the processor of the UE is configured to: prioritize the one or more delay information in descending order of priority of the one or more LCHs; or prioritize the one or more delay information in descending order of the highest priority logical channel in each of the one or more LCGs; or prioritize the one or more delay information in ascending or descending order of the value of the delay information when the one or more delay information have equal logical channel priorities, wherein the report includes a portion of the prioritized one or more delay information.

[0028] In some embodiments, the priority of the first MAC control element (CE) of the first type of report is greater than or equal to the priority of the second MAC CE used for the first type of BSR; the priority of the first MAC CE is less than or equal to the priority of the second MAC CE; the relationship between the priority of the first MAC CE and the priority of the second MAC CE depends on the implementation scheme of the UE; the priority of the third MAC CE of the second type of report is greater than or equal to the priority of the fourth MAC CE used for the second type of BSR; the priority of the third MAC CE is less than or equal to the priority of the fourth MAC CE; or the relationship between the priority of the third MAC CE and the priority of the fourth MAC CE depends on the implementation scheme of the UE.

[0029] Some embodiments of the present application also provide a network node (e.g., a base station (BS)). The network node includes: a processor; and a transceiver coupled to the processor; and the processor is configured to: transmit a configuration related to delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE to a user equipment (UE) via the transceiver; and receive a report including the delay information from the UE via the transceiver.

[0030] In some embodiments, the delay information comprises at least one of: a remaining PDU set delay budget; a PDU set buffer delay; a PDU set delay budget offset; or a first timing when a PDU within the one or more PDU sets is received from the upper layer.

[0031] In some embodiments, the delay information includes delay information associated with a first arriving PDU or a last arriving PDU of a PDU set within the one or more PDU sets.

[0032] In some embodiments, the remaining PDU set delay budget corresponds to a PDU set with a minimum delay budget among the one or more PDU sets; the PDU set buffer delay corresponds to a PDU set with a maximum buffer delay among the one or more PDU sets; or the first timing corresponds to a PDU set with an earliest arrival timing among the one or more PDU sets.

[0033] In some embodiments, the delay information includes delay information corresponding to a PDU set within the one or more PDU sets having a highest priority logical channel that is allowed to report the delay information in the LCG or in the MAC entity of the UE or in the UE.

[0034] In some embodiments, the delay information includes at least one of: delay information corresponding to a PDU set within the one or more PDU sets with a logical channel having or not having data available for transmission; or delay information corresponding to a PDU set within the one or more PDU sets in an LCG having or not having data available for transmission.

[0035] In some embodiments, the first timing includes at least one of the following: the arrival timing at the access stratum (AS) layer of the first arriving PDU in the one or more PDU sets from the upper layer; or the arrival timing at the AS layer of a PDU in the one or more PDU sets from the upper layer; or the arrival timing at the AS layer of the last arriving PDU in the one or more PDU sets from the upper layer.

[0036] In some embodiments, the configuration includes at least one of: information for enabling transmission of the report; a trigger threshold associated with a trigger condition for the report; a cancellation threshold associated with a cancellation condition for the report; a PDU set delay budget; the length of a PDU set delay budget timer; the length of a PDU set discard timer; the length of an SDU discard timer; the length of a periodic timer associated with the report; or the length of a retransmission timer associated with the report.

[0037] In some embodiments, the configuration is associated with: an LCH that allows reporting of the delay information; an LCG that allows reporting of the delay information; a DRB that allows reporting of the delay information; or a MAC entity of the UE that allows reporting of the delay information.

[0038] In some embodiments, the report is at least one of: a Delay Budget Report (DBR); a Delay Report (DR); an Arrival Timing Report (ATR); or an Enhanced Buffer Status Report (EBSR).

[0039] In some embodiments, the report includes at least one of: information of a logical channel (LCH) corresponding to the delay information; information of a logical channel group (LCG) corresponding to the delay information; information of a data radio bearer (DRB) corresponding to the delay information; or information associated with the one or more PDU sets.

[0040] In some embodiments, the report is included in a MAC sub-PDU, and the MAC sub-PDU includes at least one of the following: one remaining PDU set delay budget associated with a PDU set within the one or more PDU sets for one LCH; two or more remaining PDU set delay budgets associated with two or more PDU sets within the one or more PDU sets for the one LCH; multiple remaining PDU set delay budgets associated with multiple PDU sets within the one or more PDU sets for two or more LCHs; one remaining PDU set delay budget associated with the one or more PDU sets for one LCG; two or more remaining PDU set delay budgets associated with two or more PDU sets within the one or more PDU sets for the one LCG; or multiple remaining PDU set delay budgets associated with multiple PDU sets within the one or more PDU sets for two or more LCGs.

[0041] In some embodiments, the processor of the network node is configured to receive an indication of a capability of the UE to support transmission of the report from the UE via the transceiver.

[0042] Some embodiments of the present application provide a method that can be performed by a UE. The method includes: determining delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE, wherein the delay information includes at least one of the following: a remaining PDU set delay budget; a PDU set buffer delay; a PDU set delay budget offset; or a first timing when a PDU within the one or more PDU sets is received from the upper layer; and transmitting a report including the delay information, wherein the report is at least one of the following: a delay budget report (DBR); a delay report (DR); or an arrival timing report (ATR); or an enhanced buffer status report (EBSR).

[0043] Some embodiments of the present application provide a method that can be performed by a UE. The method includes: transmitting to a user equipment (UE) a configuration related to delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE; and receiving a report including the delay information from the UE.

[0044] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement any one of the above-mentioned methods performed by a UE or a network node (e.g., a BS).

[0045] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered limiting of its scope.

[0047] Figure 1A A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0048] Figure 1B An exemplary diagram illustrating a PDU set delay budget for XR services according to some embodiments of the present application.

[0049] Figure 2 An exemplary flow chart regarding delay information associated with a PDU set according to some embodiments of the present application is illustrated.

[0050] Figure 3 Another exemplary flow chart regarding delay information associated with a PDU set according to some embodiments of the present application is illustrated.

[0051] Figure 4 An exemplary flow chart illustrating a configuration process for delay status reporting according to some embodiments of the present application.

[0052] Figure 5A and 5B An exemplary diagram illustrating a PDU set delay budget for XR services according to some embodiments of the present application.

[0053] Figures 6A to 6D An exemplary MAC PDU including a residual delay budget according to some embodiments of the present application is illustrated.

[0054] Figures 7A to 7D An exemplary MAC PDU including a remaining PDU set delay budget according to some embodiments of the present application is illustrated.

[0055] Figure 8 An exemplary block diagram illustrating an apparatus for delaying status reporting according to some embodiments of the present application.

[0056] Fig. 9 Another exemplary block diagram illustrating an apparatus for delaying status reporting according to some embodiments of the present application. DETAILED DESCRIPTION

[0057] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be implemented by different embodiments intended to be included in the spirit and scope of the present application.

[0058] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided under specific network architectures and new service scenarios, such as the Third Generation Partnership Project (3GPP) LTE and Advanced LTE, 3GPP 5GNR, Advanced 5G, 6G, etc. It is considered that with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and in addition, the terms stated in the present application may be changed, which should not affect the principles of the present application.

[0059] Figure 1A A schematic diagram illustrating a wireless communication system according to some embodiments of the present application. Figure 1A , the wireless communication system 100 includes at least one base station (BS) 101 and at least one UE 102. Specifically, for illustrative purposes, the wireless communication system 100 includes one BS 101 and two UEs 102 (e.g., UE 102a and UE 102b). Figure 1A A specific number of BSs 101 and UEs 102 are depicted in FIG. 1 , but it is contemplated that any number of BSs 101 and UEs 102 may be included in the wireless communication system 100 .

[0060] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, networks based on time division multiple access (TDMA), networks based on code division multiple access (CDMA), networks based on orthogonal frequency division multiple access (OFDMA), LTE networks, networks based on 3GPP, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.

[0061] BS 101 may also be referred to as an NG-RAN node, RAN node, access point, access terminal, base, macro cell, Node B, enhanced Node B (eNB), gNB, home Node B, relay node or device, or described using other terms used in the art. BS 101 is typically part of a radio access network, which may include a controller communicatively coupled to BS 101.

[0062] According to some embodiments of the present application, UE 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem), etc. According to some other embodiments of the present application, UE 102 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network.

[0063] According to some other embodiments of the present application, UE 102 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal or a device, or described using other terms used in the art.

[0064] Figure 1A Both UE 102a and UE 102b in the embodiment of the present invention can transmit information to BS 101 and receive control information from BS 101, for example, via an LTE or NR Uu interface.

[0065] As defined in 3GPP TR23.700-60, a new Quality of Service (QoS) parameter associated with a PDU set is the PDU Set Delay Budget (PSDB), which defines an upper limit on the time that a PDU set may be delayed between the N6 termination point at the UE and the UPF. The PSDB applies to DL PDU sets received by the UPF on the N6 interface and to UL PDU sets sent by the UE. For a certain 5QI, the value of the PSDB is the same in UL and DL. In the case of 3GPP access, the PSDB is used to support the configuration of scheduling and link layer functions (e.g., setting of scheduling priority weights and HARQ target operating points).

[0066] According to 3GPP TR23.700-60, the 5G access network PDU set delay budget (5G-AN PSDB) is determined by subtracting a static value for the core network PDU set delay budget (CN PSDB), which represents the delay between any N6 termination point at the UPF (for any UPF that may be selected for the PDU session) and the 5G-AN from a given PSDB.

[0067] As defined in 3GPP TS38.323, regarding the service data unit (SDU) discard operation, when the discard timer for the PDCP SDU expires, or the successful delivery of the PDCP SDU is confirmed by the PDCP status report, the transmitting PDCP entity shall discard the PDCP SDU and the corresponding PDCP data PDU. If the corresponding PDCP data PDU has been submitted to the lower layer, the discard is indicated to the lower layer. For signaling radio bearers (SRBs), when the upper layer requests PDCP SDU discard, the PDCP entity shall discard all stored PDCP SDUs and PDCP PDUs.

[0068] As defined in 3GPP TR23.501, the Packet Delay Budget (PDB) defines an upper limit on the time that a packet may be delayed between the UE and the N6 terminal point at the UPF. The PDB applies to DL packets received by the UPF on the N6 interface and to UL packets sent by the UE. For a certain 5QI, the value of the PDB is the same in UL and DL. In the case of 3GPP access, the PDB is used to support the configuration of scheduling and link layer functions (for example, the setting of scheduling priority weights and HARQ target operating points). The 5G access network packet delay budget (5G-AN PDB) is determined by subtracting a static value for the core network packet delay budget (CN PDB), which represents the delay between any N6 terminal point at the UPF and the 5G-AN from a given PDB.

[0069] In general, XR, including AR and VR, and CG bring new promising categories of connected devices, applications, and services. A UE with XR services may be referred to as an XR device. XR-specific capacity improvements are a key feature. For example, there is a need to study mechanisms that provide more efficient resource allocation and scheduling for XR service characteristics (e.g., periodicity, multiple streams, jitter, latency, reliability, etc.). However, such mechanisms have not yet been designed. Typically, issues that may affect system capacity are that the network is unaware of the exact buffering delay for uplink (UL) PDU set scheduling optimization due to mismatched configuration grants (CGs), and the network is unaware of BSR transmissions due to UL jitter in arrival time at the UE.

[0070] Currently, the PDU set (e.g., frame) level QoS parameters contain a delay budget for the PDU set for XR services. The system capacity will be up to the PDU set based scheduled transmission within the PDU set delay budget. There is a case where the mismatch between the CG and the XR burst may cause delays if part of the resources are not aligned with the service arrival due to UL jitter. One possibility to avoid transmission delays is to allocate multiple CG opportunities to cover the UL PDU set arrival jitter range at the UE, but more resources are wasted. Therefore, in the case of allocating part of the resources, it is valuable to assist the network in scheduling UL transmissions within the PDU set delay budget. Typically, the network determines the PDB duration from the expected PDU set periodic arrival time or the BSR reception timing. However, due to the mismatch between the CG and the early arriving XR bursts, the network is unaware of the delay time of the data or BSR transmission. Therefore, the network cannot determine the delay time and implement a good scheduling strategy to avoid exceeding the PDU set delay budget. Figure 1B In this case, it is necessary to solve the problem of capability improvement.

[0071] Figure 1B An exemplary schematic diagram illustrating a PDU set delay budget for XR services according to some embodiments of the present application is provided. Figure 1B In the embodiment of the present invention, the PDU set in the PDU set arrival period may arrive at the PDCP layer of the UE with jitter. Figure 1B As shown in , in the time domain, the first PDU set in the first PDU set arrival period arrives with negative arrival jitter, and the second PDU set in the second PDU set arrival period arrives with positive arrival jitter. Therefore, in the time domain, there is a delay between the arrival timing of the PDU set in the first PDU set arrival period and the UL grant of the MAC layer of the UE, for example, the timing of the “first UL grant (for the transmitted data or BSR of the PDU set)”. In the time domain, there is a delay between the arrival timing of the PDU set in the second PDU set arrival period and the timing of the UL grant, for example, the timing of the “third UL grant (for the transmitted data or BSR of the PDU set)”.

[0072] Since the first PDU set in the first PDU set arrival period arrives earlier in the time domain, the “PDU set DB (delay budget)” of the first PDU set in the first PDU set arrival period is different from the original or initial “PDU set DB” of the first PDU set transmitted on the first UL grant (of data or BSR for transmission of the PDU set), such as Figure 1B Similarly, since the second PDU set in the second PDU set arrival period arrives later in the time domain, the "PDU set DB" ( Figure 1B) is also different from the original or initial "PDU set DB" (not shown) of the second PDU set transmitted on the third UL grant in the time domain Figure 1B not shown).

[0073] In order to solve the above problems, the embodiments of the present application design a mechanism for delay status reporting associated with a PDU set of UL transmission of an XR service.

[0074] More specifically, some embodiments of the present application introduce a mechanism for implementing delay-aware scheduling of XR services for capacity enhancement. In some embodiments of the present application, the UE may receive a PDU set delay budget from the network and determine the remaining delay budget corresponding to the UL PDU set. In some embodiments of the present application, the UE may transmit the remainder of a delay budget report (DBR) of the PDU set to the network. The DBR may include information about the delay budget and information about the LCH, information about the LCG, and / or information about the PDU. In some embodiments of the present application, the UE may determine delay information corresponding to a PDU set arriving at the access stratum (AS) layer of the UE from an upper layer at the UE. The delay information may be used to determine the remaining delay budget corresponding to the PDU set. The UE may then transmit a report containing the delay information to the network. In an embodiment of the present application, the remaining delay budget may also be referred to as a remaining delay budget, an available delay budget, or the like.

[0075] More details will be described below in conjunction with the accompanying drawings. It is well known to those skilled in the art that the terms "a / first", "a / second" and "a / third" are only used for clear description and should not be regarded as any substantial limitation, such as a sequence limitation.

[0076] Figure 2 An exemplary flow chart regarding delay information associated with a PDU set according to some embodiments of the present application is illustrated. Figure 2 The exemplary method 200 in may be performed by a UE (eg, Figure 1A Although described with respect to a UE, it should be understood that other devices may be configured to perform similar Figure 2 method of method of method.

[0077] exist Figure 2 In the exemplary method 200 in FIG. 1 , in operation 201, the UE determines delay information associated with one or more PDU sets received from an upper layer of the UE. The delay information may include at least one of the following:

[0078] (1) Remaining PDU set delay budget In some embodiments, the remaining PDU set delay budget corresponds to a PDU set with the smallest delay budget among one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0079] (2) PDU set buffering delay In some embodiments, the PDU set buffering delay corresponds to a PDU set having the largest buffering delay among one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0080] (3)PDU set delay budget offset.

[0081] (4) Timing when receiving a PDU in one or more PDU sets from an upper layer. For simplicity, the timing is hereinafter referred to as "first timing". In some embodiments, the first timing corresponds to a PDU set with the earliest arrival timing in one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0082] In operation 202, the UE transmits a report including delay information. The report may be at least one of the following:

[0083] (1) Delayed Budget Report (DBR);

[0084] (2) Delayed reporting (DR);

[0085] (3) Arrival Timing Report (ATR); or

[0086] (4) Enhanced Buffer Status Report (EBSR).

[0087] In some embodiments, the delay information includes delay information associated with a first arriving PDU or a last arriving PDU of a PDU set within one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE. The first arriving PDU set is the PDU within a PDU that arrives first in the time domain. The last arriving PDU is the PDU within a PDU set that arrives last in the time domain.

[0088] In some embodiments, the delay information includes delay information corresponding to a PDU set within the one or more PDU sets having a highest priority logical channel that is allowed to report delay information in the LCG or in a MAC entity of the UE or in the UE.

[0089] In some embodiments, the delay information includes at least one of the following:

[0090] (1) delay information corresponding to a PDU set with a logical channel having or not having data available for transmission within one or more PDU sets; or

[0091] (2) Delay information corresponding to a PDU set within one or more PDU sets in the LCG that has or does not have data available for transmission.

[0092] In some embodiments, the delay information is determined according to at least one of the following:

[0093] (1) Packet delay budget.

[0094] (2)SDU discard timer.

[0095] (3) Packet delay budget offset.

[0096] (4)PDU set delay budget.

[0097] (5)PDU set delay budget timer.

[0098] (6)PDU set discard timer.

[0099] (7) PDU Set Delay Budget Offset In some embodiments, the PDU Set Delay Budget Offset may be received from an upper layer of the UE.

[0100] (8) Reference time associated with a PDU set In an embodiment, the reference time is: the timing of assembling a medium access control (MAC) PDU containing delay information into a MAC PDU; or the timing of transmitting a report.

[0101] (9) The first timing as mentioned above.

[0102] In some embodiments, one or more PDU sets are received by the AS layer of the UE. The first timing may include at least one of the following:

[0103] (1) the arrival timing at the AS layer of the first arriving PDU in a set of one or more PDUs from upper layers; or

[0104] (2) the arrival timing at the AS layer of a PDU (e.g., with an important indication or an I-slice type indication) in one or more PDU sets from an upper layer; or

[0105] (3) The arrival timing at the AS layer of the last arriving PDU in a set of one or more PDUs from the upper layer.

[0106] In some embodiments, in order to determine the remaining PDU set delay budget, the UE may start a PDU set delay budget timer when receiving a PDU in a PDU set from an upper layer, stop the PDU set delay budget timer at a reference time, and determine the remaining length value of the PDU set delay budget timer.

[0107] In some embodiments, the remaining PDU set delay budget is determined based on:

[0108] (1) The sum of the PDU Set Delay Budget and the PDU Set Delay Budget Offset; or

[0109] (2) The sum of the remaining length value of the PDU set delay budget timer and the PDU set delay budget offset.

[0110] In some embodiments, the remaining PDU set delay budget is determined based on the PDU set delay budget, the first timing and the reference time; the remaining PDU set delay budget is determined based on the PDU set delay budget offset, the PDU set delay budget, the first timing and the reference time; or the PDU set buffer delay is determined based on the first timing and the reference time.

[0111] In some embodiments, the UE may transmit an indication indicating the capabilities of the UE to support transmitting reports to the network.

[0112] In some embodiments, the UE may receive a configuration related to the delay information from the network. In an embodiment, the configuration related to the delay information includes at least one of the following:

[0113] (1) Information used to enable the reported transmission;

[0114] (2) a trigger threshold associated with the trigger condition;

[0115] (3) a cancellation threshold associated with the cancellation condition;

[0116] (4) Packet delay budget;

[0117] (5) The length of the SDU discard timer;

[0118] (6) PDU set delay budget;

[0119] (7) The length of the PDU set delay budget timer;

[0120] (8) The length of the PDU set discard timer;

[0121] (9) The length of the SDU discard timer;

[0122] (10) the length of a periodic timer associated with the report; or

[0123] (11) The length of the retransmission timer associated with the report.

[0124] In some embodiments, the configuration related to the delay information is associated with:

[0125] (1) LCH that allows reporting of delay information;

[0126] (2) LCGs that allow reporting of delay information;

[0127] (3) A DRB that allows reporting of delay information; or

[0128] (4) The MAC entity of the UE is allowed to report delay information.

[0129] In some embodiments, the report transmitted in operation 202 includes at least one of: information of an LCH corresponding to the delay information (e.g., an LCH ID); information of an LCG corresponding to the delay information (e.g., an LCG ID); information of a DRB corresponding to the delay information (e.g., a DRB ID); or information associated with one or more PDU sets.

[0130] In some embodiments, the UE may trigger a report based on a trigger condition. In an embodiment, the trigger condition includes at least one of the following:

[0131] (1) Upon receiving the first arriving PDU in one or more PDU sets from an upper layer;

[0132] (2) When a PDU with an important indication (e.g., a key frame indicator or an I frame type indicator) is received from an upper layer in one or more PDU sets;

[0133] (3) When the last arriving PDU in a set of one or more PDUs is received from the upper layer;

[0134] (4) upon expiration of a periodic timer associated with the report;

[0135] The UE may start a periodic timer after transmission of the report.

[0136] (5) upon expiration of a retransmission timer associated with the report;

[0137] The UE may start a periodic timer after transmission of the report.

[0138] (6) when the PDU set delay budget is less than or equal to the trigger threshold associated with the trigger condition;

[0139] (7) when the PDU set delay is greater than or equal to the trigger threshold associated with the trigger condition;

[0140] (8) When the total number of padding bits of the allocated UL resources is greater than or equal to the bit size of the MAC sub-PDU containing the report;

[0141] (9) Upon request from an upper layer; or

[0142] (10) Upon receiving a dynamic report request (eg, DL MAC CE or DL ​​DCI or DL ​​PDCP Control PDU) from the network.

[0143] In some embodiments, the report is transmitted in response to non-satisfaction of a cancellation condition. In some embodiments, the UE may cancel the report based on the cancellation condition. The cancellation condition may include at least one of the following:

[0144] (1) When the remaining PDU set delay budget is less than or equal to the cancellation threshold;

[0145] (2) When the PDU set delay is greater than or equal to the cancellation threshold;

[0146] (3) Upon expiration of the PDU set delay budget timer;

[0147] (4) When the SDU discard timer expires;

[0148] (5) When the PDU set discard timer expires;

[0149] (6) when transmitting a MAC PDU containing a report, wherein the report is triggered before assembling the MAC PDU or at the timing of assembling the MAC PDU;

[0150] (7) In the case where the padding bits of the allocated UL resources are sufficient to accommodate a MAC PDU without a report, but insufficient to accommodate a MAC PDU with a report; or

[0151] (8) When the padding bits of the allocated UL resources are sufficient to accommodate a MAC PDU without a report but insufficient to accommodate a MAC PDU with a report, and the report is triggered when the highest logical channel priority is less than or equal to the logical channel priority of all available pending data.

[0152] In some embodiments, the MAC sub-PDU comprising the report carries at least one of:

[0153] (1) a remaining PDU set delay budget associated with a PDU set within one or more PDU sets for an LCH;

[0154] (2) two or more remaining PDU set delay budgets associated with two or more PDU sets within one or more PDU sets for one LCH;

[0155] (3) a plurality of remaining PDU set delay budgets associated with a plurality of PDU sets within one or more PDU sets for two or more LCHs;

[0156] (4) a remaining PDU set delay budget associated with one or more PDU sets for an LCG;

[0157] (5) two or more remaining PDU set delay budgets associated with two or more PDU sets within one or more PDU sets for an LCG;

[0158] (6) a plurality of remaining PDU set delay budgets associated with a plurality of PDU sets within one or more PDU sets for two or more LCGs;

[0159] (7) a PDU set delay budget offset associated with a PDU set within one or more PDU sets for an LCH or for an LCG; or

[0160] (8) Multiple remaining PDU set delay budget offsets associated with multiple PDU sets within one or more PDU sets for two or more LCHs or two or more LCGs.

[0161] In some embodiments, in response to determining that the delay information includes one (or more) pieces of delay information for LCH or LCG, the UE may prioritize the one (or more) pieces of delay information. The report may include all or part of the prioritized one (or more) pieces of delay information.

[0162] In some embodiments, in response to the allocated UL resources having insufficient padding bits to accommodate the piece(s) of delay information included in the report for the LCH or LCG, the UE may:

[0163] (1) prioritizing the one or more pieces of delay information in descending order of priority of the LCH; or

[0164] (2) in the case where the one or more pieces of delay information have the same logical channel priority, the one or more pieces of delay information are prioritized in ascending or descending order of the value of the delay information. The report may include a portion of the prioritized one or more pieces of delay information; or

[0165] (3) prioritizing the one or more pieces of delay information in descending order of highest priority logical channel in each of the LCGs; or

[0166] (4) In each of the LCGs, if the one or more pieces of delay information have the same highest logical channel priority, the one or more pieces of delay information are prioritized in ascending or descending order of their values. The report may include a portion of the prioritized one or more pieces of delay information.

[0167] In some embodiments, any of the following may be true:

[0168] (1) The priority of the MAC CE for one type of report (e.g., regular report or periodic report) is greater than or equal to the priority of the MAC CE for one type of BSR (e.g., regular BSR or periodic BSR);

[0169] (2) The priority of a type of reported MAC CE is less than or equal to the priority of a type of BSR MAC CE;

[0170] (3) The relationship between the priority of a type of reported MAC CE and the priority of a type of BSR MAC CE depends on the implementation of the UE; for example, the same priority may be considered.

[0171] (4) The priority of the MAC CE for another type of report (e.g., padding report) is greater than or equal to the priority of the MAC CE for another type of BSR (e.g., padding BSR);

[0172] (5) The priority of the MAC CE for another type of report is less than or equal to the priority of the MAC CE for another type of BSR; or

[0173] (6) The relationship between the priority of the MAC CE for another type of report and the priority of the MAC CE for another type of BSR depends on the implementation of the UE.

[0174] Figure 3 Another exemplary flow chart regarding delay information associated with a PDU set according to some embodiments of the present application is illustrated. Figure 3 The exemplary method 300 in may be performed by a network node (eg, a BS (eg, Figure 1A Although described with respect to a network node, it should be understood that other devices may be configured to perform similar Figure 3 method of method of method.

[0175] exist Figure 3 In the exemplary method 300 of , in operation 301, the network node transmits to the UE a configuration related to delay information associated with one or more PDU sets received from an upper layer of the UE. In operation 302, the network node receives a report including delay information from the UE.

[0176] In some embodiments, the delay information includes at least one of the following:

[0177] (1) Remaining PDU set delay budget For example, the remaining PDU set delay budget may correspond to a PDU set with the smallest delay budget among one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0178] (2) PDU set buffering delay For example, the PDU set buffering delay may correspond to a PDU set having the largest buffering delay among one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0179] (3)PDU set delay budget offset.

[0180] (4) Timing when receiving a PDU in one or more PDU sets from an upper layer. For simplicity, the timing may be expressed as "first timing". For example, the first timing may correspond to a PDU set with the earliest arrival timing in one or more PDU sets in the LCH or in the LCG or in the MAC entity of the UE or in the UE.

[0181] In some embodiments, the delay information includes delay information associated with a first arriving PDU or a last arriving PDU of a PDU set within the one or more PDU sets.

[0182] In some embodiments, the delay information includes delay information corresponding to a PDU set in the LCH or in the LCG or in the MAC entity of the UE or in the UE having the highest priority logical channel for which delay information is allowed to be reported in the LCG or in the MAC entity of the UE or in the UE.

[0183] In some embodiments, the first timing includes at least one of the following:

[0184] (1) the arrival timing at the UE's AS layer of the first arriving PDU in a set of one or more PDUs from upper layers; or

[0185] (2) the arrival timing at the AS layer of a PDU in one or more PDU sets from the upper layer; or

[0186] (3) The arrival timing at the AS layer of the last arriving PDU in a set of one or more PDUs from the upper layer.

[0187] In some embodiments, the delay information includes at least one of the following:

[0188] (1) delay information corresponding to a PDU set with a logical channel having or not having data available for transmission within one or more PDU sets; or

[0189] (2) Delay information corresponding to a PDU set within one or more PDU sets in the LCG that has or does not have data available for transmission.

[0190] In some embodiments, the configuration related to the delay information transmitted in operation 301 includes at least one of the following:

[0191] (1) Information used to enable the reported transmission;

[0192] (2) a trigger threshold associated with the trigger condition of the report;

[0193] (3) the cancellation threshold associated with the reported cancellation condition;

[0194] (4) Packet delay budget;

[0195] (5) The length of the SDU discard timer;

[0196] (6) PDU set delay budget;

[0197] (7) The length of the PDU set delay budget timer;

[0198] (8) The length of the PDU set discard timer;

[0199] (9) The length of the SDU discard timer;

[0200] (10) the length of a periodic timer associated with the report; or

[0201] (11) The length of the retransmission timer associated with the report.

[0202] In some embodiments, the configuration related to the delay information is associated with:

[0203] (1) LCH that allows reporting of delay information;

[0204] (2) LCGs that allow reporting of delay information;

[0205] (3) A DRB that allows reporting of delay information; or

[0206] (4) The MAC entity of the UE is allowed to report delay information.

[0207] In some embodiments, the report received in operation 302 is at least one of:

[0208] (1) Delayed Budget Report (DBR);

[0209] (2) Delayed reporting (DR);

[0210] (3) Arrival Timing Report (ATR); or

[0211] (4) Enhanced Buffer Status Report (EBSR).

[0212] In some embodiments, the report includes at least one of:

[0213] (1) Information of a logical channel (LCH) corresponding to delay information;

[0214] (2) information of a logical channel group (LCG) corresponding to the delay information;

[0215] (3) information corresponding to a data radio bearer (DRB) of delay information; or

[0216] (4) Information associated with one or more PDU sets.

[0217] In some embodiments, the report is included in a MAC sub-PDU, and the MAC sub-PDU includes at least one of the following:

[0218] (1) a remaining PDU set delay budget associated with a PDU set within one or more PDU sets for an LCH;

[0219] (2) two or more remaining PDU set delay budgets associated with two or more PDU sets within one or more PDU sets for one LCH;

[0220] (3) a plurality of remaining PDU set delay budgets associated with a plurality of PDU sets within one or more PDU sets for two or more LCHs;

[0221] (4) a remaining PDU set delay budget associated with one or more PDU sets for an LCG;

[0222] (5) two or more remaining PDU set delay budgets associated with two or more PDU sets within one or more PDU sets for an LCG; or

[0223] (6) A plurality of remaining PDU set delay budgets associated with a plurality of PDU sets within one or more PDU sets for two or more LCGs.

[0224] In some embodiments, the network node may receive an indication indicating the capabilities of the UE to support transmission of reports from the UE.

[0225] Those skilled in the art will appreciate that the sequence of operations in exemplary flowcharts 200 and 300 may be changed, and some of the operations in exemplary flowcharts 200 and 300 may be eliminated or modified without departing from the spirit and scope of the present disclosure. Figure 2 and 3 The details described in the exemplary flow chart are applicable to the embodiments of Figure 1A , 1B And all embodiments from 4 to 9.

[0226] In some embodiments of the present application, the UE reports the remaining or remaining or available PDU set delay budget to the network based on the PDU set delay budget. For example, the UE may determine the remaining delay budget corresponding to the PDU set based on at least the delay budget, and may report a delay budget report (DBR) corresponding to the PDU set to the network so that when the network receives the report from the UE, it assists the network in determining the remaining or remaining or available delay budget corresponding to the PDU set. The DBR may be included in a MAC CE, a PDCP control PDU, an RLC status report, or uplink physical control information, or may be included in a layer 2 header (e.g., an L2 header of the first arriving PDU of the PDU set or an L2 header of an enhanced BSR (EBSR) transmitted for the (first arriving PDU) of the PDU set).

[0227] In some embodiments, the PDU set may be replaced by a frame or data burst. In some embodiments, the 5G-AN PDU set delay budget may be configured by the network or configured as a default value. In some embodiments, the delay budget may be replaced by a 5G-AN PDU set discard timer configured by the network. In some embodiments, the delay budget may be replaced by a 5G-AN SDU discard timer configured by the network. In some embodiments, the delay budget may be replaced by a packet delay budget configured by the network.

[0228] In some embodiments, the MAC entity at the UE determines the remaining delay budget corresponding to the PDU set based on the delay budget configured by the network, and reports the DBR corresponding to the PDU set to the network. In some embodiments, the network may configure the DBR, for example, Figure 4 As shown in .

[0229] Figure 4 An exemplary flow chart illustrating a configuration process for delaying status (or information) reporting according to some embodiments of the present application.

[0230] In operation 411, UE 401 may report DBR capabilities to network 402 (e.g., gNB).

[0231] In operation 412, the network 402 transmits a DBR configuration to the UE 401 in an RRC message (eg, an RRCReconfiguration message), which is used to enable the available delay budget, the remaining delay budget, the time instance T1 (eg, Figure 5B ) or a report of a delay budget offset corresponding to a PDU set.

[0232] For example, the DBR configuration may include at least one of the following information elements (IEs):

[0233] (1) Delay Budget (DB). This IE indicates the available access network delay budget value for a PDU set corresponding to an LCH or DRB when the PDU corresponding to the PDU set is received from an upper layer for the first or last time. The access network delay budget (5G-ANPDB) represents the delay budget for transmitting a PDU set between an access layer (e.g., a PDCP layer or a MAC layer) at a UE 401 and an AS (e.g., a PDCP layer or a MAC layer) at a network 402 from a given PDB.

[0234] (2) periodicDBR-Timer: This IE indicates the value of the periodic DBR timer of the LCH or LCG or the MAC entity in the UE.

[0235] (3) retxDBR-Timer: This IE indicates the value of the retransmission DBR timer of the LCH or LCG or the MAC entity in the UE.

[0236] (4) DBR trigger threshold: This IE indicates the trigger threshold of the LCH or LCG or MAC entity in the UE for DBR.

[0237] (5) DBR cancellation threshold: This IE indicates the cancellation threshold of the LCH or LCG or MAC entity in the UE for DBR.

[0238] (6) DBR allows reporting of the MAC entity of a logical channel or a logical channel group or a UE. This IE indicates that the delay budget reporting of the LCH or LCG or the MAC entity in the UE or the UE to the network 402 is allowed.

[0239] (7) DBR Enable Reporting Data Radio Bearer This IE indicates that delay budget reporting of DRB to the network 402 is enabled.

[0240] In operation 413, after UE 401 receives the DBR configuration from network 402, UE 401 indicates the DBR configuration for LCH or LCG or MAC entity to the MAC entity, and indicates the DBR configuration for DRB to the PDCP entity.

[0241] In operation 414 , the UE 401 transmits an RRCReconfigurationComplete message for DBR configuration to the network 402 .

[0242] Figure 5A and 5B An exemplary diagram illustrating a PDU set delay budget for XR services according to some embodiments of the present application.

[0243] like Figure 5AAs shown in FIG. 1 , for an XR service including PDU set #1 and PDU set #2, since PDU set #1 arrives at the PDCP layer of the UE earlier in the time domain with arrival jitter, there is a buffer delay between the arrival timing of PDU set #1 and the UL grant (DBR for PDU set #1 or EBSR or BSR (for the transmission of the first arriving PDU)) of the MAC layer of the UE. Therefore, the “PDU set #1 delay budget” includes “delay” and “remaining delay budget”, as shown in FIG. Figure 5A As shown in .

[0244] In some embodiments, the UE may determine the remaining delay budget for the PDU set corresponding to the LCH or LCG. Figure 5B The embodiments are described as follows.

[0245] Figure 5B The timing values ​​in correspond to Figure 5A Examples of Figure 5B As shown in FIG. 1 , T1, T4 and T5 are three arrival timing values ​​of a PDU set. T2 is the MAC PDU assembly timing. T3 is the timing of the UL grant (of the transmission of the DRB or EBSR or BSR for the transmission of the (first arriving PDU) of the PDU set). For example:

[0246] T1 = the timing of the first or last reception of a PDU belonging to a PDU set from the upper layer of the UE. The PDU may be an important PDU belonging to a PDU set.

[0247] • T2 = MAC PDU assembly timing of the DBR associated with a PDU set (eg, the first arriving PDU or the last arriving PDU of a PDU set). In some embodiments, "MAC PDU assembly" may also be referred to as "MAC PDU multiplexing" or the like.

[0248] • T3 = Timing of start or end of UL grant for transmitting a MAC PDU containing a DBR associated with a PDU set or for transmitting the first arriving PDU of a PDU set or for transmitting an EBSR or BSR for the transmission of (the first arriving PDU of) a PDU set.

[0249] exist Figure 5A and 5B In some embodiments, the MAC entity of the UE may obtain the T1 value from the PDCP layer of the DRB of the LCH. The PDCP entity of the UE may notify the MAC entity that the PDU set arrives at the AS layer of the UE. The PDCP entity of the UE may notify the corresponding information (e.g., identification (ID)) of the PDU set. The MAC entity may obtain T2 or T3 at the MAC layer.

[0250] Figure 5A The remaining delay budget in can be based on Figure 5BIn one embodiment, the remaining delay budget = "PDU set #1 delay budget" - (T2 - T1). In another embodiment, the remaining delay budget = "PDU set #1 delay budget" - (T3 - T1).

[0251] In some embodiments, the PDU set #1 delay budget may be replaced by the packet delay budget or the length of the SDU discard timer or the time of the PDU set discard timer. For example, the remaining delay budget = "packet delay budget" - (T2 - T1), or the remaining delay budget = "packet delay budget" - (T3 - T1). For example, the remaining delay budget = "length of the SDU discard timer" - (T2 - T1), or the remaining delay budget = "length of the SDU discard timer" - (T3 - T1). For example, the remaining delay budget = "length of the PDU set discard timer" - (T2 - T1), or the remaining delay budget = "length of the PDU set discard timer" - (T3 - T1).

[0252] exist Figure 5A and 5B In some other embodiments, upon receiving a PDU belonging to a PDU set from an upper layer of the UE for the first or last time, the PDCP entity of the UE may notify the MAC entity of the UE that the PDU set has arrived at the AS of the UE. The PDCP entity may also notify the corresponding PDU set information, for example, the ID of the PDU set. The MAC entity may set the delay budget timer corresponding to the PDU set to the delay budget configured by the RRC message, and start the delay budget timer upon receiving the notification from the PDCP entity. The delay budget timer counts down. The MAC entity may then determine the remaining length value of the delay budget timer as the available delay budget until a reference time. The reference time may be the timing when multiplexing or assembling a DBR associated with a PDU set in a MAC PDU, or the transmission timing of a DBR associated with a PDU set. In some other embodiments, the MAC entity may set the delay budget timer corresponding to the PDU set to the packet delay budget or SDU discard timer or PDU set discard timer configured by the RRC message.

[0253] exist Figure 5A and 5BIn some other embodiments, the PDCP entity of the UE may set the delay budget timer corresponding to the PDU set to the delay budget configured by the RRC message, and start the delay budget timer when the PDU belonging to the PDU set is received for the first or last time from the upper layer of the UE. The delay budget timer counts down. When DBR is multiplexed in the MAC PDU, the MAC entity may obtain the remaining value of the delay budget timer from the PDCP layer of the DRB as the available delay budget. The gap between the timing of multiplexing the DBR in the MAC PDU and the start of the UL grant for MAC PDU transmission may be ignored. The delay budget configured by the RRC message may be replaced by the packet delay budget or the SDU discard timer or the PDU set discard timer via the RRC message.

[0254] In some embodiments of the present application, the UE may trigger a delay budget report (DBR) with an LCH configured for DBR (with or without data available for transmission) if at least one of the following trigger conditions is met:

[0255] (1) When the first or last PDU belonging to a PDU set arrives at the AS layer (eg, the PDCP layer of the UE). In this case, the DBR may be referred to as "normal DBR" hereinafter.

[0256] (2) When a PDU belonging to a PDU set with an important indication (e.g., a key frame indicator or an I frame type indicator) from an upper layer arrives at the AS layer (e.g., the PDCP layer). In this case, the DBR may be referred to as "normal DBR" hereinafter.

[0257] (3) Upon expiration of retxDBR-Timer. For example, the UE starts retxDBR-Timer after DBR transmission. For DBR triggered by expiration of retxDBR-Timer, at least one of the LCHs (allowing reporting delay budget) belonging to the LCG contains UL data. In this case, the DBR may be referred to as "regular DBR" hereinafter. The UE may consider the LCH that triggers the DBR to be the LCH with the highest priority (with or without data available for transmission) when the DBR is triggered.

[0258] (4) Upon expiration of periodicDBR-Timer. For example, the UE starts the periodicDBR-Timer after DBR transmission. In this case, DBR may be referred to as "periodic DBR" hereinafter.

[0259] (5) When the delay budget corresponding to the PDU set is less than or equal to the trigger threshold configured by the RRC message. In this case, the DBR may be referred to as "normal DBR" hereinafter.

[0260] (6) UL resources are allocated, and the total number of padding bits of the UL resources is greater than or equal to the size of the MAC CE of the DBR plus its subheader. In this case, the DBR may be referred to as "padding DBR" hereinafter.

[0261] (7) Requested by upper layers of the UE to report the DBR for LCH and for a direction (e.g., UL);

[0262] (8) UL data for LCH (allowing reporting delay budget) becomes available to the MAC entity of the UE. In this case, DBR may be referred to as "normal DBR" hereinafter. For example:

[0263] - the UL data belongs to an LCH (allowed reporting delay budget) with a higher priority than any LCH (allowed reporting delay budget) containing available UL data; or

[0264] - All LCHs (allowing for reporting delay budget) do not contain any UL data available.

[0265] In some embodiments of the present application, the UE may cancel DBR if at least one of the following cancellation conditions is met:

[0266] (1) The remaining delay budget of the PDU set is less than or equal to the cancellation threshold.

[0267] (2) The delay budget timer corresponding to the PDU set or the PDU within the PDU set expires, that is, the remaining delay budget = 0.

[0268] (3) The discard timer corresponding to the PDU set expires.

[0269] (4) The discard timer of the SDU corresponding to the PDU in the PDU set expires.

[0270] (5) When a MAC PDU is transmitted, all DBRs triggered before the MAC PDU assembly timing shall be canceled, and this MAC PDU contains the DBR containing the PDU set delay budget status until (and including) the last event that triggers the DBR before the MAC PDU assembly timing.

[0271] (6) When the UL grant can accommodate all pending data available corresponding to the PDU set for transmission, but the UL grant is not sufficient to additionally accommodate (padding) the MAC CE of the DBR plus its MAC subheader.

[0272] (7) When the UL grant can accommodate all pending data available corresponding to the PDU set for transmission, but the UL grant is not sufficient to additionally accommodate (fill) the MAC CE of the DBR plus its MAC subheader, and if the DBR triggered with the highest logical channel priority is less than or equal to the logical channel priority corresponding to all pending data available for transmission.

[0273] Some embodiments of the present application relate to DBR format design, for example, Figures 6A to 6D and 7A to 7D. A MAC PDU may contain at most one DBR, even if multiple events have triggered the DBR. In some embodiments, the DBR may be per LCH, for example, Figures 6A to 6D In some other embodiments, the DBR may be per LCG, for example, Figures 7A to 7D Embodiment of the invention.

[0274] Figures 6A to 6D An exemplary MAC PDU including a residual delay budget according to some embodiments of the present application is illustrated.

[0275] Fig. 6A Embodiments relate to a delay budget for an LCH in a short DBR format or a short truncated DBR format. Fig. 6A A MAC sub-PDU in DBR format is shown, which includes one DBR for one LCH. Specifically, the MAC sub-PDU includes a MAC sub-header and a MAC CE, which includes the following fields:

[0276] (1) DB (Delay Budget): This field indicates the remaining delay budget corresponding to the PDU set (with the lowest delay budget) for LCH (with or without data available for transmission) after the MAC PDU has been constructed. LCH may have the highest logical channel priority in the MAC entity of the UE or in the UE. The PDU set may have the lowest delay budget in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, LCH may have or may not have data available for transmission. The definition of data available for transmission may be referenced in 3GPP TS38322 and TS38.323. For example, DB may be:

[0277] a) Code index, for example, 1 for 2ms, 2 for 2.5ms, 3 for 3ms; or

[0278] b) An absolute value, for example, 1 ms, 1.5 ms, 2 ms, 2.5 ms or 3 ms. ms is milliseconds.

[0279] (2) LCID (LCH Identifier): This field identifies the logical channel for which the delay budget is reported.

[0280] Optionally, Fig. 6AThe MAC sub-PDU in the packet may further include PDU set information (e.g., PDU set ID). The PDU set ID field indicates the PDU set corresponding to the DB field. For example, the MAC CE includes "remaining delay budget + PDU set #i", such as Fig. 6A For example, the PDU set ID can be:

[0281] (1) PDU set sequence number (SN); or

[0282] (2) Code index, for example, 0 represents the current PDU set being transmitted, or 1 represents the next PDU set to be transmitted.

[0283] Figure 6B Embodiments of the invention relate to one delay budget for each LCH within all LCHs having data available for transmission and / or a DBR for transmission having a long DBR format. Figure 6C Embodiments are directed to one delay budget per LCH within a portion of all LCHs having data available for transmission and / or having a long truncated DBR format for the DBR for transmission in case the UL grant is insufficient to accommodate the DBR of all LCHs. Figure 6B and 6C A MAC sub-PDU in DBR format is shown, which is the DBR of one or more LCHs. Specifically, the MAC sub-PDU includes a MAC sub-header and a MAC CE, which includes the following fields.

[0284] (1) DB: This field indicates the remaining delay budget corresponding to the PDU set (with the lowest delay budget) for LCH (with or without data available for transmission) after the MAC PDU has been constructed. The PDU set may have the lowest delay budget in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCH may or may not have data available for transmission. For the long DBR format and the long truncated DBR format, the DB field is included in ascending order based on LCHi.

[0285] (2) LCHi: For example, Figure 6B and 6C LCH0 to LCH7 shown in.

[0286] a) For Figure 6B In the long DBR format shown in FIG. 1 , the LCHi field indicates the presence of the Remaining Delay Budget field for logical channel i. An LCHi field set to 1 indicates that the Remaining Delay Budget field for logical channel i is reported. An LCHi field set to 0 indicates that the Delay Budget field for logical channel i is not reported. For example, Figure 6BAs shown in , m LCHs may be set to 1 to indicate that m logical channels have remaining delay budgets, namely, remaining delay budget 1, remaining delay budget 2, and remaining delay budget m. In an embodiment, if m=4, there may be 4 remaining delay budgets corresponding to 4 LCHs respectively.

[0287] b) For Figure 6C In the long truncated DBR format shown in FIG. 1 , the LCHi field indicates whether the logical channel i has a remaining delay budget. An LCHi field set to 1 indicates that the logical channel i has a remaining delay budget for transmission. An LCHi field set to 0 indicates that the logical channel i does not have a delay budget for transmission. For example, Figure 6C As shown in , LCH4 is set to 1 to indicate that logical channel 4 has a remaining delay budget, ie, a remaining delay budget of 1.

[0288] Optionally, Figure 6B and 6C The MAC sub-PDU in the may further include PDU set information (e.g., PDU set ID), which indicates the PDU set corresponding to the DB, for example, "remaining delay budget 1 + PDU set #i", "remaining delay budget 2 + PDU set #i" or "remaining delay budget m + PDU set #i", such as Figure 6B or Figure 6C For example, the PDU set ID may be a PDU set SN or a code index.

[0289] Fig.6D Embodiments involve more than one DB per LCH. Fig.6D A MAC sub-PDU in DBR format is shown, which contains two delay budgets for one LCH in long DBR format. The two delay budgets can be placed in ascending or descending order of the delay budgets for each PDU set. Similar to Fig. 6A , Fig.6D The MAC sub-PDU in includes a MAC sub-header and a MAC CE, which includes an LCID and two DBs, for example, a remaining delay budget 1 and a remaining delay budget 2. Optionally, Fig.6D The MAC sub-PDU in the may further include PDU set information corresponding to the DB, for example, "remaining delay budget 1 + PDU set #i" or "remaining delay budget 2 + PDU set #i", such as Fig.6D Optionally, the number of the DB field of the LCH is indicated in another field in the MAC subheader or in the MAC CE payload.

[0290] Figures 7A to 7D An exemplary MAC PDU including a remaining PDU set delay budget according to some embodiments of the present application is illustrated.

[0291] Fig. 7AEmbodiments relate to a delay budget for an LCG in a short DBR format or a short truncated DBR format. Fig. 7A A MAC sub-PDU in DBR format is shown, which includes one DBR for one LCG. Specifically, the MAC sub-PDU includes a MAC sub-header and a MAC CE, which includes an LCG ID and a PDU set DB (delay budget).

[0292] (1) DB: This field indicates the remaining delay budget corresponding to the PDU set (with the lowest delay budget) with LCH (logical channel with the highest priority) in the LCG (with or without data available for transmission). The LCG may have the highest logical channel priority in the MAC entity of the UE or in the UE. The LCH may have the highest logical channel priority in the LCG. The PDU set may have the lowest delay budget in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCG may or may not have data available for transmission. The definition of data available for transmission may be referenced in 3GPP TS38322 and TS38.323. For example, Fig. 7A The DB in is the remaining PDU set delay budget.

[0293] (2) LCG ID: This field identifies the LCH group whose delay budget is being reported.

[0294] Optionally, Fig. 7A The MAC sub-PDU in may further include a PDU set identifier: indicating the PDU set corresponding to the DB. For example, Fig. 7A The DB in is the remaining PDU set delay budget + PDU set #i.

[0295] Figure 7B Embodiments of the invention relate to one delay budget for each LCG within all LCGs having data available for transmission and / or a DBR for transmission having a long DBR format. Figure 7C Embodiments relate to one delay budget per LCG within a portion of all LCGs having data available for transmission and / or DBR for transmission having a long truncated DBR format in case the UL grant is insufficient to accommodate the DBR of all LCGs. Figure 7B and 7C A MAC sub-PDU in DBR format is shown, which is the DBR of one or more LCGs.

[0296] (1) DB: This field indicates the remaining delay budget of the PDU set (with the lowest delay budget) corresponding to the LCH (with the highest priority logical channel) in the LCG (with or without data available for transmission) after the MAC PDU has been constructed. The LCH may have the highest logical channel priority in the LCG. The PDU set may have the lowest delay budget in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCG may or may not have data available for transmission. For the long DBR format and the long truncated DBR format, the DB field is included in ascending order based on LCGi. For example, Figure 7B The DB in is the remaining PDU set delay budget 1, the remaining PDU set delay budget 2 or the remaining PDU set delay budget m. Figure 7C The DB in is the remaining PDU set delay budget 1.

[0297] (2) LCGi: For example, Figure 7B and 7C LCG0 to LCG7 shown in FIG.

[0298] a) For the long DBR format, this field indicates the presence of the DB field for logical channel group i. An LCGi field set to 1 indicates that the DB field for logical channel group i is reported. An LCGi field set to 0 indicates that the DB field for logical channel group i is not reported.

[0299] b) For the Long Truncated DBR format, this field indicates whether the logical channel group i has a delay budget. The LCGi field set to 1 indicates that the logical channel group i has a delay budget. The LCGi field set to 0 indicates that the logical channel group i does not have a delay budget.

[0300] Optionally, Figure 7B and 7C The MAC sub-PDU in the may further include a PDU set ID (e.g., a frame ID) indicating the PDU set corresponding to the DB, for example, "remaining PDU set delay budget 1 + PDU set #i", "remaining PDU set delay budget 2 + PDU set #i", or "remaining PDU set delay budget m + PDU set #i", such as Figure 7B or Figure 7C For example, the PDU set ID may be a PDU set SN or a code index.

[0301] Fig.7D An embodiment involves two or more DBs per LCG. Fig.7D Shows a MAC sub-PDU in DBR format, which contains two delay budgets for one LCG in long DBR. Fig. 7A , Fig.7DThe MAC sub-PDU in includes a MAC sub-header and a MAC CE, which includes an LCG ID and two DBs, for example, a remaining PDU set delay budget 1 and a remaining PDU set delay budget 2. Optionally, Fig.7D The MAC sub-PDU in the may further include a PDU set ID corresponding to the DB, for example, "remaining PDU set delay budget 1 + PDU set #i" or "remaining PDU set delay budget 2 + PDU set #i", such as Fig.7D Optionally, the number of the DB field of the LCG is indicated in another field in the MAC subheader or in the MACCE payload.

[0302] In some embodiments of the present application, the UE may report the DBR that has not been cancelled to the network through at least one of the following operations.

[0303] (1) During the logical channel prioritization procedure, the UE prioritizes DBR (e.g., normal DBR, periodic DBR) in a higher order than "data from any logical channel except data from UL-CCCH".

[0304] (2) If the UL grant is not sufficient to include the DBR of all LCGs (e.g., padding DBR), the UE may prioritize the delay budget reports in descending order of the highest logical channel priority in each of the LCGs; and in case of equal priority of some LCGs, the UE may prioritize the delay budget reports in ascending order of delay budget.

[0305] (3) If the UL grant is not sufficient to include all DBRs of all LCHs (e.g., padding DBRs), the UE may prioritize the delay budget reports in descending order of highest logical channel priority; and in case of equal priority of some LCHs, the UE may prioritize the delay budget reports in ascending order of delay budget.

[0306] In some embodiments, there may be the following operations:

[0307]

[0308]

[0309] In some embodiments, there may be the following operations:

[0310]

[0311]

[0312] In some embodiments of the present application, the UE (MAC entity or PDCP entity) determines the remaining delay budget (or remaining delay budget or available delay budget) corresponding to the PDU set based on "A) the delay budget configured by the network" and "B) the delay budget offset with the upper layer". When delivering the PDU set to the PDCP layer of the UE, the upper layer of the UE may indicate a delay budget offset (e.g., +2ms or -2ms). For example, "-2ms" indicates that the PDU set arrives 2ms later than expected by the AS layer, and "+2ms" indicates that the PDU set arrives 2ms earlier than expected by the AS layer. The UE can determine the remaining delay budget by adding the delay budget offset to the delay budget configured by the RRC message, that is, "remaining delay budget = A) + B)".

[0313] In order to synchronize the delay budget and the discard timer for transmission, the discard timer may also be adjusted accordingly. For example, the PDCP entity of the UE may add the delay budget offset to the SDU discard timer or PDU set discard timer configured by the RRC message before starting the discard timer corresponding to the PDU set or SDU.

[0314] In some embodiments of the present application, the UE may determine the remaining delay budget corresponding to the PDU set based on "A) the delay budget configured by the network", "B) the delay budget offset with the upper layer", and "C) the delay between the first or last reception of the PDU belonging to the PDU set from the upper layer and the reference time".

[0315] The reference time may be a timing when a DBR associated with a PDU set in a MAC PDU is multiplexed, or a transmission timing of a DBR associated with a PDU set.

[0316] For example, the UE may determine the remaining delay budget by adding the delay budget offset to the delay budget configured by the RRC message and by subtracting the delay between the first or last reception of a PDU belonging to a PDU set from an upper layer and a reference time, i.e., "remaining delay budget = A) + B) - C)".

[0317] In some embodiments of the present application, the network configures a discard timer for the UE (e.g., Figure 4 ), and the UE may use an information element (IE) of "discard timer", which may also be referred to as "PDU set discard timer". This IE indicates the value of the discard timer for the PDU set corresponding to the data radio bearer (DRB). For example, the PDCP entity of the UE may set a discard timer corresponding to the PDU set and start the timer when a PDU belonging to the PDU set is received from the upper layer of the UE for the first time or the last time. The discard timer counts down. The UE may discard the PDU set upon expiration of the discard timer.

[0318] In some embodiments of the present application, the MAC CE priority between DBR and BSR may be defined as follows:

[0319] (1) DBR, for example, regular DBR or periodic DBR, which may be a MAC CE of a DBR other than a DBR included for padding having a higher priority than a MAC CE of a BSR other than a BSR included for padding; or

[0320] (2) DBR, e.g., regular DBR or periodic DBR, which may be a MAC CE of a DBR other than a DBR included for padding and a MAC CE of a BSR other than a BSR included for padding. Prioritization among the MAC CEs depends on the implementation of the UE, e.g., the same priority may be considered; or

[0321] (3) DBR, for example, regular DBR or periodic DBR, which may be a MAC CE of a DBR other than a DBR included for padding having a lower priority than a MAC CE of a BSR other than a BSR included for padding; or

[0322] (4) The priority of the MAC CE used to fill the DBR is higher than the priority of the MAC CE used to fill the BSR; or

[0323] (5) The priority order among the MAC CE for filling the DBR and the MAC CE for filling the BSR depends on the implementation scheme of the UE. For example, the same priority may be considered; or

[0324] (6) The priority of the MAC CE used to fill the DBR is lower than the priority of the MAC CE used to fill the BSR.

[0325] In some embodiments, there may be the following operations:

[0326]

[0327]

[0328] In some embodiments of the present application, the UE may determine a delay (i.e., a buffer delay value) corresponding to the PDU set based on at least the first or last PDU of the PDU set belonging to the LCH having an arrival AS layer (e.g., a PDCP entity), and report a delay report (DR) corresponding to the PDU set to the network, so as to assist the network in determining the available or remaining or remaining delay budget corresponding to the PDU set for transmission when the network receives the DR from the UE. The DR may be included in a MACCE, a PDCP control PDU, an RLC status report, or uplink physical control information, or may be included in a layer 2 header (e.g., an L2 header of the first arriving PDU of the PDU set or an L2 header of an enhanced BSR (EBSR) (for transmission of the first arriving PDU of the PDU set)).

[0329] In an embodiment, the network transmits a DR configuration to the UE in an RRC message (e.g., RRCReconfiguration), which is used to enable DR corresponding to the PDU set. The DR configuration may include at least one of the following:

[0330] (1) periodicDR-Timer: This IE indicates the value of the periodic DR timer of the LCH or LCG or MAC entity in the UE.

[0331] (2)retxDR-Timer: This IE indicates the value of the retransmission DR timer of the LCH or LCG or MAC entity in the UE.

[0332] (3) DR trigger threshold: This IE indicates the trigger threshold of the LCH or LCG or MAC entity in the UE for DR.

[0333] (4) DR cancellation threshold: This IE indicates the cancellation threshold of the LCH or LCG or MAC entity in the UE used for DR.

[0334] (5) DR reporting allowed logical channel: This IE indicates that delay budget reporting is allowed to the network for LCH or LCG or MAC entity in UE or UE.

[0335] (6) DR allowed reporting data radio bearer: This IE indicates that delay budget reporting to the network is allowed for DR.

[0336] In some embodiments of the present application, the UE may determine the Figure 5A and 5B For example, there may be the following specific embodiments.

[0337] In an embodiment, the MAC entity of the UE may obtain the T1 value from the PDCP layer of the DRB of the LCH. The MAC entity may obtain T2 or T3 from the PDCP layer of the LCH.

[0338] • T1 = timing of first or last reception of a PDU belonging to a PDU set from an upper layer. The PDU may be an important PDU belonging to a PDU set.

[0339] • T2 = MAC PDU multiplexing timing of the DR associated with the PDU set.

[0340] • T3 = Timing of start or end of MAC CE for transmitting DR associated with a PDU set or for transmitting the first arriving PDU of a PDU set or for transmitting EBSR or BSR for transmission of (the first arriving PDU of) a PDU set.

[0341] In this embodiment, the delay value may be calculated as (T2-T1) or as (T3-T1).

[0342] In another embodiment, when a PDU belonging to a PDU set is received from an upper layer of the UE for the first or last time, the PDCP entity of the UE may notify the MAC entity of the arrival of the PDU set in the AS, and may further notify the corresponding PDU set information, for example, the PDU set ID. The MAC entity may set the delay timer corresponding to the PDU set to 0 and start the timer when the notification is received from the PDCP entity. The delay timer counts. The MAC entity may then determine the length value of the delay timer as the delay until a reference time. The reference time may be the timing when multiplexing a DR associated with a PDU set in a MAC PDU, or the transmission timing of a DR associated with a PDU set or used to transmit the first arriving PDU of a PDU set or used to transmit a BSR for the transmission of a PDU set (the first arriving PDU).

[0343] In another embodiment, the PDCP entity of the UE may set the delay timer corresponding to the PDU set to 0 and start the delay timer when the PDU belonging to the PDU set is received for the first or last time from the upper layer of the UE. The delay timer counts. The MAC entity of the UE may obtain the value of the timer from the PDCP layer of the DRB as a delay in multiplexing (or assembling) the DR in the MAC PDU. For example, the gap between the timing of multiplexing (or assembling) the DR in the MAC PDU and the start or end of the UL grant for MAC PDU transmission is ignored.

[0344] In some embodiments of the present application, the UE may trigger a Delayed Report (DR) with an LCH configured for DR (with data available for transmission) if at least one of the following conditions is met:

[0345] (1) When the first or last PDU belonging to a PDU set with LCH arrives at the access layer (eg, PDCP layer). In this case, the DR may be referred to as "normal DR" hereinafter.

[0346] (2) When the first or last PDU belonging to a PDU set with an important indication (e.g., a key frame indicator or an I frame type indicator) from an upper layer with an LCH arrives at the access layer (e.g., PDCP layer). In this case, DR may be referred to as "normal DR" hereinafter.

[0347] (3) Upon expiration of retxDR-Timer. For example, the UE starts retxDR-Timer after DR transmission. For DR triggered by expiration of retxDR-Timer, at least one of the logical channels (allowing reporting delay budget) belonging to the LCG contains UL data. In this case, DR may be referred to as "regular DR" hereinafter. The UE may consider the logical channel that triggers DR to be the highest priority logical channel (with or without data available for transmission) when DR is triggered.

[0348] (4) Upon expiration of periodicDR-Timer. For example, the UE starts the periodicDR-Timer after DR transmission. In this case, DR may be referred to as "periodic DR" hereinafter.

[0349] (5) When the delay corresponding to the PDU set is greater than or equal to the trigger threshold configured by the RRC message. In this case, DR may be referred to as "regular DR" hereinafter.

[0350] (6) UL resources are allocated and the number of padding bits is greater than or equal to the size of the DR MAC CE plus its MAC subheader, in which case the DR may be referred to as "padding DR" hereinafter.

[0351] (7) Requested by upper layers to report DR for LCH and for a direction (eg, UL) to the network. In this case, the DR may be referred to as "normal DR" hereinafter.

[0352] (8) For LCH (allowing reporting delay), UL data becomes available to the MAC entity. In this case, DR may be referred to as "normal DR" hereinafter.

[0353] - this UL data belongs to an LCH (allowing reporting delay budget) with a higher priority than any LCH (allowing reporting delay budget) containing available UL data; or

[0354] - All LCHs (allowing for reporting delay) do not contain any available UL data.

[0355] In some embodiments of the present application, the UE may cancel DR if at least one of the following conditions is met:

[0356] (1) The delay of a PDU set is greater than or equal to the cancellation threshold.

[0357] (2) The discard timer corresponding to the PDU set or the SDU corresponding to the PDU in the PDU set expires, that is, delay = the length of the discard timer.

[0358] (3) When a MAC PDU is transmitted, all DRs triggered before the MAC PDU assembly timing shall be canceled, and this PDU contains a DR containing the PDU set delay status until (and including) the last event that triggers a DR before the MAC PDU assembly timing.

[0359] (4) When the UL grant can accommodate all pending data available corresponding to the PDU set for transmission, but is not sufficient to additionally accommodate (padding) the DR MAC CE plus its MAC subheader.

[0360] (5) When the UL grant can accommodate all pending data available corresponding to the PDU set for transmission, but the UL grant is not sufficient to additionally accommodate (fill) the MAC CE of the DR plus its MAC subheader, and when the DR triggered with the highest logical channel priority is less than or equal to the logical channel priority corresponding to all pending data available for transmission.

[0361] Some embodiments of the present application relate to DR format design, for example, similar to Figures 6A to 7D The DBR format in the MAC PDU. A MAC PDU can contain at most one DR, even if multiple events have triggered DR. DR can be per LCH or per LCG.

[0362] In some embodiments, for each LCH (including for one LCH), the DR per LCH includes one DR. The MAC sub-PDU may include the following fields:

[0363] (1) Delay: This field indicates the delay of the PDU set (with maximum buffering delay) corresponding to the LCH (with or without data available for transmission) after the MAC PDU has been constructed. The LCH may have the highest logical channel priority in the MAC entity of the UE or in the UE. The PDU set may have the maximum delay in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCH may have or may not have data available for transmission. The definition of data available for transmission may be referenced in 3GPP TS38.322 and TS38.323. The delay may be:

[0364] - code index, for example, 1 for 2ms, 2 for 2.5ms, 3 for 3ms; or

[0365] - An absolute value, for example, 1ms, 1.5ms, 2ms, 2.5ms, or 3ms. ms means milliseconds.

[0366] (2) LCID (LCH Identification): This field identifies the LCH group whose delay is being reported.

[0367] (3) PDU set information, for example, PDU set ID (optional): This field indicates the PDU set corresponding to the delay. The PDU set ID can be:

[0368] -PDU Set Sequence Number (SN); or

[0369] - Code index, for example, 0 represents the current PDU set being transmitted, 1 represents the next PDU set to be transmitted.

[0370] In some other embodiments, the DR per LCH includes one DR per LCH within two or more LCHs having data available for transmission and / or DR for transmission in long DR format. In the event that the UL grant is insufficient to accommodate the DR for all LCHs, the DR per LCH includes one delay budget per LCH within the portion of all LCHs having data available for transmission and / or DR for transmission in long truncated DR format. The MAC sub-PDU may include the following fields:

[0371] (1) Delay: This field indicates the delay of the PDU set (with maximum buffering delay) corresponding to the LCH (with or without data available for transmission) after the MAC PDU has been constructed. The PDU set may have the maximum delay in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCH may or may not have data available for transmission. For the Long DR format and the Long Truncated DR format, the Delay field is included in ascending order based on the LCHi field.

[0372] (2) LCHi:

[0373] - For the Long DR format, the LCHi field indicates the presence of the Delay field for logical channel i. An LCHi field set to 1 indicates that the Delay field for logical channel i is reported. An LCHi field set to 0 indicates that the Delay field for logical channel i is not reported.

[0374] - For the long truncated DR format, the LCHi field indicates whether logical channel i has a buffer delay for transmission. An LCHi field set to 1 indicates that logical channel i has a buffer delay for transmission. An LCHi field set to 0 indicates that logical channel i does not have a buffer delay.

[0375] In some other embodiments, the DR of each LCH includes two or more DR fields for each LCH. For example, the MAC sub-PDU includes a MAC sub-header and a MAC CE, which includes an LCID and two or more DR fields for each LCH, such as PDU set delay 1 and PDU set delay 2, etc. Optionally, the MAC sub-PDU may further include PDU set information corresponding to the DR field, such as "PDU set delay 1+PDU set #i" or "PDU set delay 2+PDU set #i". Optionally, the number of the DR of the LCH is indicated in another field in the MAC sub-header or in the MAC CE payload.

[0376] In some embodiments, the DR per LCG may be one DR for one LCG, which includes the following fields:

[0377] (1) Delay: This field indicates the delay corresponding to the PDU set (with maximum buffering delay) with LCH (logical channel with highest priority) in the LCG (with or without data available for transmission). The LCG may have the highest logical channel priority in the MAC entity of the UE or in the UE. The LCH may have the highest logical channel priority in the LCG. The PDU set may have the maximum delay in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCG may or may not have data available for transmission. The definition of data available for transmission may be referenced in 3GPP TS38322 and TS38.323.

[0378] (2) LCG ID: This field identifies the logical channel group whose delay is being reported.

[0379] In some other embodiments, in the case where the UL grant is insufficient to accommodate the DRs for all LCGs, one DR for each LCG within all LCGs with data available for transmission and / or DRs for transmission with long DR format, or one DR for each LCG within a portion of all LCGs with data available for transmission and / or DRs for transmission with long truncated DR format. The DR may include the following fields:

[0380] (1) Delay: This field indicates the delay of the PDU set (with maximum buffering delay) corresponding to the LCH (with the highest priority logical channel) in the LCG (with or without data available for transmission) after the MAC PDU has been constructed. The LCH may have the highest logical channel priority in the LCG. The PDU set may have the maximum delay in the MAC entity of the UE or in the UE. After the MAC PDU has been constructed, the LCG may or may not have data available for transmission. For the long DR format and the long truncated DR format, the Delay field is included in ascending order based on the LCGi field.

[0381] (2)LCGi:

[0382] - For the Long DR format, the LCGi field indicates the presence of the Delay field for logical channel group i. An LCGi field set to 1 indicates that the Delay field for logical channel group i is reported. An LCGi field set to 0 indicates that the Delay field for logical channel group i is not reported.

[0383] - For the long truncated DR format, the LCGi field indicates whether the logical channel group i has a delay. An LCGi field set to 1 indicates that the logical channel group i has a delay. An LCGi field set to 0 indicates that the logical channel group i does not have a delay.

[0384] In some embodiments of the present application, there are two or more DRs for each LCG. For example, there are two DRs for one LCG in long DR format. Fig. 7A , the MAC sub-PDU includes a MAC sub-header and a MAC CE, which includes an LCG ID and two DRs, for example, PDU set delay 1 and PDU set delay 2. The DR may further include a PDU set ID corresponding to the DB, for example, "remaining PDU set delay 1 + PDU set #i" or "remaining PDU set delay 2 + PDU set #i". Optionally, the total number of DR fields for the LCG is indicated in another field in the MAC sub-header or in the MAC CE payload.

[0385] In some embodiments of the present application, the UE may report the DR that has not been cancelled to the network through at least one of the following operations.

[0386] (1) During the logical channel prioritization process, the UE prioritizes regular DR (e.g., regular DR, periodic DR) in a higher order than "data from any logical channel during the logical channel, except data from UL-CCCH".

[0387] (2) If the UL grant is not sufficient to include the DR for all LCGs (e.g., padding DR), the UE may prioritize delay reports in descending order of the highest logical channel priority in each of the LCGs; and in case of equal priority for some LCGs, the UE may prioritize delay reports in descending order of buffering delay.

[0388] (3) If the UL grant is not sufficient to include the DR for all LCHs (e.g., padding DR), the UE may prioritize the delayed reports in descending order of the highest logical channel priority; and in case of equal priority of some LCHs, the UE may prioritize the delayed reports in descending order of buffering delay.

[0389] In some embodiments, there may be the following operations:

[0390]

[0391]

[0392] In some embodiments of the present application, the UE (MAC entity or PDCP entity) determines the delay corresponding to the PDU set as "D) delay offset with the upper layer of the UE".

[0393] (1) The upper layer of the UE indicates a delay offset (e.g., +2ms or -2ms) when delivering a PDU set to the PDCP layer. For example, -2ms indicates that the PDU set arrives 2ms later than the UE's AS layer expects, and +2ms indicates that the PDU set arrives 2ms earlier than the AS layer expects.

[0394] (2) The PDCP entity of the UE may add a delay offset to the discard timer configured by the RRC message before starting the discard timer corresponding to the PDU set.

[0395] In some embodiments of the present application, the UE determines the delay corresponding to the PDU set according to "D) delay offset with the upper layer" and "C) delay between the first or last reception of the PDU belonging to the PDU set from the upper layer of the UE and the reference time". Figure 5A and 5B In the embodiment, the value of "C)" may be determined in any manner, for example, "C)" may be equal to (T2-T1) or (T3-T1).

[0396] In these embodiments, the reference time may be the timing when multiplexing or assembling the DR associated with the PDU set in the MAC PDU, or the transmission timing of the DR associated with the PDU set. For example, the UE may determine the delay corresponding to the PDU set by adding the delay offset to the delay between the first or last reception of the PDU belonging to the PDU set from the upper layer and the reference time, i.e., delay = D) + C).

[0397] In some embodiments of the present application, the UE (MAC entity or PDCP entity) determines the delay corresponding to the PDU set as "C) the delay between the first or last reception of the PDU belonging to the PDU set from the UE's upper layer and the reference time".

[0398] In some embodiments of the present application, the MAC CE priority between the DR and the BSR may be defined as follows:

[0399] (1) DR, for example, regular DR or periodic DR, which may be a MAC CE priority of a DR other than a DR included for padding higher than a MAC CE priority of a BSR other than a BSR included for padding; or

[0400] (2) DR, for example, regular DR or periodic DR, which may be a MAC CE of a DR other than a DR included for padding and a MAC CE of a regular BSR other than a BSR included for padding. The priority ordering among the MAC CEs depends on the implementation of the UE, for example, the same priority may be considered; or

[0401] (3) DR, for example, regular DR or periodic DR, which may be a MAC CE of a DR other than a DR included for padding has a lower priority than BSR, for example, regular DR or periodic DR, which may be a MAC CE of a DR other than a DR included for padding has a lower priority; or

[0402] (4) The priority of the MAC CE used to fill the DR is higher than the priority of the MAC CE used to fill the BSR; or

[0403] (5) The priority order among the MAC CE for filling the DR and the MAC CE for filling the BSR depends on the implementation of the UE. For example, the same priority may be considered; or

[0404] (6) The priority of the MAC CE used to fill the DR is lower than the priority of the MAC CE used to fill the BSR.

[0405] In some other embodiments of the present application, the UE may report the first timing (T1) of the first or last reception of a PDU corresponding to a PDU set from an upper layer in an arrival timing report (ATR), instead of reporting the remaining delay budget mentioned above or the delay corresponding to the PDU set. In these embodiments, the order of the earliest T1 corresponding to the PDU set may be applied instead of the descending order of the remaining delay budget or the ascending order of the delay mentioned above when necessary, for example, in the case of prioritizing reports if the UL grant is not sufficient to accommodate all (filling) reports, or in the case of selecting which PDU set is used for report triggering among more than one PDU set in one or more LCHs or LCGs. Based on the T1 received from the UE, the network may determine the remaining delay budget for the PDU set based on T1. Optionally, T1 is the first timing corresponding to the PDU set with the earliest arrival timing within the one or more PDU sets. Optionally, T1 is the first timing corresponding to a PDU set with the highest priority logical channel (in the LCG or in the MAC entity of the UE or in the UE) within one or more PDU sets, and wherein the highest priority logical channel is allowed to report the first timing in the LCG or in the MAC entity of the UE or in the UE. Optionally, T1 is the first timing corresponding to a PDU set within one or more PDU sets in the LCG or LCH with or without data available for transmission.

[0406] In some other embodiments of the present application, the UE may report delay information in an enhanced buffer status report (EBSR) (for transmission of the first arriving PDU of a PDU set), including the first timing (T1) mentioned above or the remaining delay budget or buffer delay, instead of transmitting ATR, DBR or DR.

[0407] In some embodiments of the present application, the periodicEBSR-Timer associated with the EBSR may be configured by the network independently of the periodicBSR-Timer of the traditional BSR in TS 38.321; or the retxEBSR-Timer associated with the EBSR may be configured by the network independently of the retxBSR-Timer of the traditional BSR in TS 38.321. The UE may start the periodicEBSR-Timer and / or the retxEBSR-Timer after the transmission of the EBSR. Optionally, the periodicEBSR-Timer and / or the retxEBSR-Timer may be configured individually per LCH or LCG or MAC entity of the UE or the UE.

[0408] In some embodiments of the present application, the triggering condition of EBSR and / or the cancellation condition of EBSR may be the same or similar to the triggering condition or cancellation condition of DBR or DR or ATR disclosed above in the present application. When EBSR is triggered for one LCG or LCH, the UE may determine the delay information and buffer size of the LCG or LCDH, and include both of them in the EBSR of the LCG or LCH.

[0409] In some embodiments of the present application, the configuration for EBSR can be the same as in the above Figure 2 The configuration related to the delay information determined in operation 201 disclosed in the embodiment is the same or similar.

[0410] In some embodiments of the present application, if the EBSR is configured by the network for the UE or the MAC entity of the UE or the LCG or LCH, the UE only uses the EBSR for transmission, even if only the traditional BSR is triggered for some LCGs or LCHs. In this case, the EBSR may indicate whether the delay information of one LCG or one LCH is presented in the EBSR. An LCID may be assigned to identify the EBSR format.

[0411] In some embodiments of the present application, if there is an EBSR triggered for an LCG or LCH, the UE only uses the EBSR for transmission, even if a conventional BSR is triggered for some other LCG or LCH. In this case, the EBSR may include both the delay information and the buffer size for the LCG or LCH. The EBSR may include only the buffer size without including the delay information for other LCGs or LCHs.

[0412] In some embodiments of the present application, if EBSR is configured by the network for the UE or the MAC entity of the UE or the LCG or LCH, then the UE may only use BSR for transmission, provided that the traditional BSR is triggered only for some LCG or LCH, but the EBSR is not triggered.

[0413] In some embodiments of the present application, both the traditional BSR and the EBSR are allowed to be triggered and transmitted separately in different MAC sub-PDUs. In these embodiments, the UE may perform a prioritization process for the EBSR and the BSR. In some embodiments, the MAC CE priority between the EBSR and the BSR may be defined as follows:

[0414] (1) EBSR, e.g., regular EBSR or periodic EBSR, which may be a MAC CE of an EBSR other than an EBSR included for padding that has a higher priority than a MAC CE of a BSR other than a BSR included for padding; or

[0415] (2) EBSR, e.g., regular EBSR or periodic EBSR, which may be a MAC CE of an EBSR other than an EBSR included for padding and a MAC CE of a BSR other than a BSR included for padding. The priority ordering among the MAC CEs depends on the implementation of the UE, e.g., the same priority may be considered; or

[0416] (3) EBSR, e.g., a regular EBSR or a periodic EBSR, which may be a MAC CE of an EBSR other than an EBSR included for padding has a lower priority than a MAC CE of a BSR other than a BSR included for padding; or

[0417] (4) The priority of the MAC CE used to fill the EBSR is higher than the priority of the MAC CE used to fill the BSR; or

[0418] (5) The priority order among the MAC CE for filling the EBSR and the MAC CE for filling the BSR depends on the implementation of the UE. For example, the same priority may be considered; or

[0419] (6) The priority of the MAC CE used to fill the EBSR is lower than the priority of the MAC CE used to fill the BSR.

[0420] In some embodiments of the present application, the UE may report to the network an EBSR that has not been cancelled by at least one of the following operations. These operations are similar to the operations for DBR or DR disclosed above in the present application. The definition of a regular EBSR, a periodic EBSR, or a padding EBSR is similar to the definition of a regular DBR, a periodic DBR, or a padding DBR disclosed above in the present application.

[0421] (1) During the logical channel prioritization procedure, the UE prioritizes regular EBSRs (e.g., regular EBSRs, periodic EBSRs) in a higher order than data from any logical channel during the logical channel, except data from UL-CCCH.

[0422] (2) If the UL grant is not sufficient to include the EBSRs of all LCGs (e.g., padding the EBSRs), the UE may prioritize the EBSRs in descending order of the highest logical channel priority in each of the LCGs; and in case of equal priority of some LCGs, the UE may prioritize the EBSRs in descending order of delay or in ascending order of delay budget or in ascending order of the first timing (i.e., T1 as disclosed above in the present application).

[0423] (3) If the UL grant is not sufficient to include the EBSRs of all LCHs (e.g., padding the EBSR), the UE may prioritize the EBSRs in descending order of highest logical channel priority; and in case of equal priority of some LCHs, the UE may prioritize the EBSRs in descending order of delay or in ascending order of delay budget or in ascending order of first timing (T1).

[0424] In some embodiments, there may be the following operations:

[0425]

[0426]

[0427] Those skilled in the art will appreciate that all other details described in all other embodiments of the present application (e.g., trigger conditions, cancellation conditions, configurations and / or operations related to ATR, DBR or DR) are applicable to the embodiments related to EBSR (e.g., trigger conditions, cancellation conditions and / or operations related to EBSR). In addition, trigger conditions, cancellation conditions, configurations and / or operations related to EBSR may be eliminated or modified without departing from the spirit and scope of the present disclosure.

[0428] Figure 8 An exemplary block diagram of an apparatus 800 for data discarding operation according to some embodiments of the present application is illustrated. Figure 8 , the apparatus 800 may include at least one non-transitory computer-readable medium 802, at least one receiving circuit system 804, at least one transmitting circuit system 806, and at least one processor 808, which is coupled to the non-transitory computer-readable medium 802, the receiving circuit system 804, and the transmitting circuit system 806. The at least one processor 808 may be a CPU, a DSP, a microprocessor, etc. The apparatus 800 may be a network node (e.g., a BS) or a UE configured to perform the methods described above, etc.

[0429] Although in this figure, elements such as at least one processor 808, receive circuitry 804, and transmit circuitry 806 are described in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, receive circuitry 804 and transmit circuitry 806 may be combined into a single device, such as a transceiver. In certain embodiments of the present application, apparatus 800 may further include an input device, a memory, and / or other components.

[0430] In some embodiments of the present application, the non-transitory computer-readable medium 802 may have computer-executable instructions stored thereon to cause the processor to implement the method for the UE or network node (e.g., BS) as described or illustrated above. For example, when the computer-executable instructions are executed, the processor 808 interacts with the receiving circuit system 804 and the transmitting circuit system 806 to perform the steps for the UE or network node (e.g., BS) as described or illustrated above.

[0431] Fig. 9 Another exemplary block diagram illustrating an apparatus 900 for data discarding operation according to some embodiments of the present application. Fig. 9 , the apparatus 900 (e.g., a BS or a UE) may include at least one processor 902 and at least one transceiver 904 coupled to the at least one processor 902. The transceiver 904 may include at least one separate receive circuit system 906 and transmit circuit system 908, or at least one integrated receive circuit system 906 and transmit circuit system 908. The at least one processor 902 may be a CPU, a DSP, a microprocessor, etc.

[0432] According to some other embodiments of the present application, when the device 900 is a UE, the processor 902 may be configured to: determine delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE, wherein the delay information includes at least one of the following: a remaining PDU set delay budget; a PDU set buffer delay; a PDU set delay budget offset; or a first timing when a PDU within one or more PDU sets is received from an upper layer; and transmit a report including the delay information, wherein the report is at least one of the following: a delay budget report (DBR); a delay report (DR); an arrival timing report (ATR); or an enhanced buffer status report (EBSR).

[0433] According to some embodiments of the present application, when the device 900 is a network node (e.g., a BS), the processor 902 is configured to: transmit a configuration related to delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE to a user equipment (UE) via a transceiver 904; and receive a report containing the delay information from the UE via the transceiver 904.

[0434] The method of the present disclosure can be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device, etc. In general, any device with a finite state machine capable of implementing the flow chart shown in the figure can be used to implement the processing functions of the present disclosure.

[0435] Although the present disclosure has been described with its specific embodiments, it is apparent that many alternatives, modifications and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessarily required for the operation of the disclosed embodiments. For example, it will enable a person of ordinary skill in the art to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as described herein are intended to be illustrative, not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0436] In this document, the term "includes, including" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only includes those elements, but also may include other elements that are not explicitly listed or inherent to such processes, methods, articles or equipment. In the absence of more constraints, the element starting with "a, an" or the like does not exclude the presence of additional identical elements in the process, method, article or equipment comprising the element. In addition, the term "another" is defined as at least the second or more. The term "having" and the like as used herein are defined as "including". For example, the expression of "A and / or B" or "at least one of A and B" may include any and all combinations of words listed together with the expression. For example, the expression "A and / or B" or "at least one of A and B" may include A, B or both A and B. The wording "first", "second" or the like is only used to clearly illustrate the embodiments of the present application, and is not used to limit the substantive content of the present application.

Claims

1. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: determining delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE, wherein the delay information comprises at least one of: Remaining PDU set delay budget; PDU set buffering delay; PDU Set Delay Budget Offset; or a first timing when a PDU in the one or more PDU sets is received from the upper layer; and transmitting a report including the delay information, wherein the report is at least one of: Delayed Budget Report DBR; Delayed reporting of DR; Arrival Timing Report (ATR); or Enhanced Buffer Status Report EBSR. 2 . The UE according to claim 1 , wherein the delay information comprises first delay information associated with a first arriving PDU or a last arriving PDU of a PDU set within the one or more PDU sets.

3. The UE according to claim 1 or claim 2, wherein: The remaining PDU set delay budget corresponds to a PDU set having a minimum delay budget among the one or more PDU sets; The PDU set buffering delay corresponds to a PDU set having a maximum buffering delay among the one or more PDU sets; or The first timing corresponds to a PDU set having an earliest arrival timing among the one or more PDU sets.

4. A UE according to any one of claims 1 to 3, wherein the delay information includes second delay information corresponding to a PDU set within the one or more PDU sets having the highest priority logical channel within the one or more PDU sets, and wherein the highest priority logical channel is allowed to report the second delay information in the LCG or in the MAC entity of the UE or in the UE.

5. The UE according to any one of claims 1 to 4, wherein the delay information comprises at least one of the following: third delay information corresponding to a PDU set within the one or more PDU sets in the logical channel LCH having or not having data available for transmission; or Fourth delay information corresponding to a PDU set within the one or more PDU sets in the LCG having or not having data available for transmission.

6. The UE according to claim 1, wherein the delay information is determined according to at least one of the following: PDU set delay budget; Packet delay budget; PDU set delay budget timer; PDU set discard timer; SDU discard timer; PDU set delay budget offset; a reference time associated with the PDU set; or The first timing.

7. The UE according to claim 1 or claim 6, wherein the one or more PDU sets are received by an access stratum (AS) layer of the UE, and wherein the first timing comprises at least one of the following: the arrival timing at the AS layer of a first arriving PDU within the one or more PDU sets from the upper layer; or the arrival timing at the AS layer of a certain PDU within the one or more PDU sets from the upper layer; or The arrival timing at the AS layer of a last arriving PDU in the one or more PDU sets from the upper layer.

8. The UE according to claim 6, wherein the reference time is: The timing of assembling the medium access control MAC PDU containing the delay information into a MAC PDU; or The timing of transmitting the report.

9. The UE of claim 1, wherein the processor of the UE is configured to receive a configuration related to the delay information from the network via the transceiver, and wherein the configuration includes at least one of: information for enabling transmission of said report; a trigger threshold associated with the trigger condition; a cancellation threshold associated with the cancellation condition; The PDU set delay budget; The length of the PDU set delay budget timer; The length of the PDU set discard timer; The length of the SDU discard timer; the length of a periodic timer associated with the report; or The length of the retransmission timer associated with the report.

10. The UE according to claim 9, wherein the configuration is associated with: an LCH allowing reporting of said delay information; LCG allowing reporting of said delay information; a data radio bearer (DRB) allowing reporting of said delay information; or A MAC entity of the UE is enabled to report the delay information.

11. The UE according to claim 1, wherein: In response to determining that the delay information includes one or more delay information for one or more LCHs or one or more LCGs, the processor of the UE is configured to prioritize the one or more delay information, and wherein the report includes all or part of the prioritized one or more delay information.

12. The UE according to claim 1, wherein: In response to padding bits of the allocated uplink (UL) resources being insufficient to accommodate one or more pieces of delay information included in the delay information for one or more LCHs or one or more LCGs, the processor of the UE is configured to: Prioritizing the one or more pieces of delay information in descending order of priority of the one or more LCHs; or prioritizing the one or more pieces of delay information in descending order of highest priority logical channels in each of the one or more LCGs; or In the case where the one or more pieces of delay information have equal logical channel priorities, the one or more pieces of delay information are prioritized in ascending or descending order of values ​​of the delay information, The report includes a portion of the prioritized one or more pieces of delay information.

13. The UE according to claim 1, wherein: The priority of the first MAC Control Element CE of the report of the first type is greater than or equal to the priority of the second MAC CE for the BSR of the first type; The priority of the first MAC CE is less than or equal to the priority of the second MAC CE; The relationship between the priority of the first MAC CE and the priority of the second MAC CE depends on the implementation of the UE; The priority of the third MAC CE of the report of the second type is greater than or equal to the priority of the fourth MAC CE for the BSR of the second type; The priority of the third MAC CE is less than or equal to the priority of the fourth MAC CE; or The relationship between the priority of the third MAC CE and the priority of the fourth MAC CE depends on the implementation of the UE.

14. A network node, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmitting, via the transceiver, to a user equipment (UE), a configuration related to delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE; and A report including the delay information is received from the UE via the transceiver.

15. A method performed by a user equipment UE, comprising: determining delay information associated with one or more protocol data unit (PDU) sets received from an upper layer of the UE, wherein the delay information comprises at least one of: Remaining PDU set delay budget; PDU set buffering delay; PDU Set Delay Budget Offset; or a first timing when a PDU in the one or more PDU sets is received from the upper layer; and transmitting a report including the delay information, wherein the report is at least one of: Delayed Budget Report DBR; Delayed reporting of DR; Arrival Timing Report (ATR); or Enhanced Buffer Status Report EBSR.

Images