Processing method for delay status report, user equipment, and base station

Abstract

A processing method for a delay status report (DSR). A user equipment generates a DSR and reports same, wherein when a buffer status report (BSR) is configured, the DSR is first generated and / or reported. On the basis of the DSR generated by the user equipment, when the BSR is configured, the user equipment first generates the DSR and reports same, and a network node receives the BSR or the DSR.

Description

Processing method for delay status report, user equipment and base station Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method for processing a delay status report, a user equipment, and a base station. Background Art

[0002] 5G wireless communication systems are designed to provide enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC) services. For 5G New Radio (NR), extended reality (XR) services are a general term encompassing augmented reality (AR), virtual reality (VR), and mixed reality (MR). XR services and applications typically have the characteristics and requirements of high throughput and low latency, and cloud gaming is an application with the same requirements. XR and cloud gaming are important applications that 5G will support. According to the research outputs of the 3GPP RAN, SA, and CT technical working groups, in general, due to the unique characteristics of XR services, current 5G systems may not be able to well support XR services.

[0003] XR is a service with high real-time requirements, high and variable data rates, low latency, and high reliability. Failure to meet these real-time and low-latency requirements can significantly impact the user experience. For example, for certain types of video data, a frame can only be correctly decoded and reconstructed after the client's XR application has correctly received all relevant data packets for that frame within the required time window. Otherwise, all data packets for a frame may be outdated and useless. This can lead to a significant decrease in video display quality.

[0004] To support the aforementioned features and requirements of XR services, comprehensive discussions and consensus were held at the recent Third Generation Partnership Project (3GPP) RAN1 and RAN2 meetings. In Release 18, an XR work item was proposed for uplink data transmission from user equipment (UE) to gNB. This work item introduces a feature that allows the UE to report the delay status of buffered data packets to the gNB, helping the gNB to schedule uplink XR services in a timely manner.

[0005] The UE's Medium Access Control (MAC) layer entity reports the delay status information of buffered data packets to the base station via a newly defined MAC control element (CE). This report includes the remaining time and the corresponding data volume, and is referred to as a Delay Status Report (DSR). The remaining time information corresponds to a discard timer associated with a service data unit (SDU) or protocol data unit (PDU). When an SDU or PDU arrives at the Packet Data Convergence Protocol (PDCP) or Radio Link Control (RLC) entity, a discard timer is started, starting at 0, and a timeout value is set for the discard timer. When the discard timer's value is greater than or equal to the set timeout value, the discard timer is considered to have expired. The remaining time before the timeout typically refers to a time range. For example, the remaining time can be 0 to 10 milliseconds (ms), or 10 to 20 milliseconds. The corresponding data volume refers to the sum of the data volumes of all SDUs or PDUs within a certain remaining time range, commonly referred to as the buffer size, such as 1000 bits or 200 bytes. According to the latest technical discussions, DSR-related delay information and data volume are typically calculated in units of logical channel groups (LCGs).

[0006] The existing technology has the following problems: there is no certain coordination mechanism between DSR and BSR, which leads to information redundancy and waste of resources.

[0007] When a large number of DSRs are generated, there are outdated or unnecessary DSRs, which causes waste of uplink resources.

[0008] Summary of the Invention

[0009] An object of the present disclosure is to provide a method for processing a delay status report, a user equipment, and a base station.

[0010] In a first aspect, an embodiment of the present invention provides a method for processing a delay status report, executed in a wireless communication device, and characterized by comprising:

[0011] Generate and report a Delay Status Report (DSR), wherein when a BSR is configured, the DSR is generated and / or reported first.

[0012] In a second aspect, an implementation of an embodiment of the present invention provides a user device, comprising a processor and a memory, wherein the processor is configured to call and execute a computer program stored in the memory so that the device equipped with the processor performs the disclosed method.

[0013] In a third aspect, a method for processing a delay status report in an embodiment of the present invention is executed in a network node, and is characterized in that it includes: based on a delay status report (DSR) generated by a user equipment, when a buffer status report (BSR) is configured, the user equipment preferentially generates and reports the DSR, and the network node receives the BSR or the DSR.

[0014] In a fourth aspect, an implementation of an embodiment of the present invention provides a base station, comprising a processor and a memory, wherein the processor is configured to call and execute a computer program stored in the memory so that a device equipped with the processor executes the disclosed method.

[0015] The disclosed method can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer-readable medium, when loaded into a computer, instructs the processor of the computer to execute the disclosed method.

[0016] The non-transitory computer-readable medium may include at least one of the group consisting of a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory.

[0017] The disclosed method can be programmed as a computer program product, which causes a computer to perform the disclosed method.

[0018] The disclosed method may be programmed as a computer program, which causes a computer to perform the disclosed method.

[0019] Technical effect:

[0020] The technical advantages and effects of coordinating buffer size reporting (BSR) and delay status reporting (DSR) in the embodiments of the present invention are as follows:

[0021] BSR and DSR enable efficient utilization of wireless resources, improving system throughput and user experience. BSR allows base stations to dynamically allocate resources based on user buffer sizes, avoiding resource waste and congestion. DSR allows base stations to prioritize latency-sensitive services based on user latency requirements, reducing latency and jitter.

[0022] Coordinating BSR and DSR reduces signaling overhead and conserves network resources. BSR and DSR are event-triggered reporting mechanisms that report only when a user's buffer size or latency status changes. They also provide periodic reporting and fill-in reporting. This reduces unnecessary signaling transmission, signaling interference, and load. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] One or more embodiments are exemplarily illustrated by the figures in the corresponding drawings. These exemplifications do not limit the embodiments. Elements with the same reference numerals in the drawings represent similar elements. Unless otherwise specified, the figures in the drawings are not intended to be proportional. The following divisions of the various embodiments are for ease of description and should not constitute any limitations on the specific implementation of the embodiments of the present invention. The various embodiments may be combined and referenced with each other as long as there is no contradiction.

[0024] FIG. 1 is a schematic diagram illustrating data packet sets with different PDU set importance indicators (PSI).

[0025] FIG2 is a schematic diagram showing a communication system.

[0026] FIG3 is a schematic diagram showing the layers of the communication protocol.

[0027] FIG4 is a schematic diagram showing the method according to an embodiment of the present invention.

[0028] FIG5 is a schematic diagram showing the method according to an embodiment of the present invention.

[0029] FIG. 6 is a schematic diagram showing a chip according to an embodiment of the present invention.

[0030] FIG. 7 is a schematic diagram showing a chip according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of this application more clear, some embodiments of this application are further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain this application and are not used to limit this application.

[0032] Embodiments of the present invention relate to a wireless communication system, and more specifically, to a 5G New Radio (NR) wireless communication system in which user equipment (UE) reports delay status report information of uplink data packets to a gNB to support extended reality (XR) services, including typical forms such as augmented reality (AR), virtual reality (VR), or mixed reality (MR).

[0033] In addition to DSR, a buffer status report (BSR) mechanism already exists for uplink service data transmission and resource scheduling. In the BSR mechanism, the gNB configures the following information to the UE via RRC messages:

[0034] -Periodic BSR timer (periodicBSR-Timer);

[0035] -BSR retransmission timer (retxBSR-Timer);

[0036] -Logical channel group (logicalChannelGroup);

[0037] -Logical channel SR delay timer (logicalChannelSR-DelayTimer);

[0038] -Apply logical channel SR delay timer (logicalChannelSR-DelayTimerApplied);

[0039] -mask logical channel SR (logicalChannelSR-Mask);

[0040] The UE counts the sum of the data volumes of all logical channel packets in the buffer in LCG units, which is usually called the buffer size. The sum is then reported to the gNB via the BSR MAC CE. The gNB then schedules and allocates resources based on the amount of data to be transmitted on the UE side.

[0041] On the other hand, XR services usually have multiple service data streams, and the Quality of Service (QoS) requirements of different data streams may be different. Among them, for some video data streams, there may be integrity requirements between multiple SDUs or PDUs, that is, these SDUs or PDUs are required to be transmitted correctly, otherwise they will all be discarded. For example, a frame is split into multiple SDUs or PDUs during transmission. For data streams with integrity requirements (corresponding to QoS flow), the Data Packet Set Integrity Indication (PSIHI) is defined to configure and indicate that a QoS flow has a PDU set (PDU Set) integrity transmission requirement. The PDU Set (PDU Set) refers to a set of multiple SDUs or PDUs or packets with a certain association, such as a set of multiple SDUs or PDUs or packets that are split into when a video frame is transmitted. In addition, the same QoS flow may include multiple different types of PDU sets, which may differ in some aspects. For example, when the network is congested, different types of PDU sets may have different discard priorities. The PDU Set Importance Indicator (PSI) is defined to dynamically indicate the importance of a PDU set.

[0042] DSR is a new concept, and its related processes and mechanisms are still under research and discussion. There are no detailed documents discussing the coordination between DSR and BSR, nor are there any detailed technologies or solutions for controlling DSR triggering.

[0043] For the PSI-based discard mechanism, the currently determined solutions are: (1) a solution based on a PSI threshold, and (2) a solution based on a PSI and a discard timer (PSI+discard timer).

[0044] (1) PSI threshold-based solution: Based on up to 16 levels of PSI values, when congestion occurs, the gNB indicates a PSI threshold to the UE per logical channel group (LCG). Based on this PSI threshold, the UE discards all PDU sets with low importance (PSI below or above the PSI threshold).

[0045] (2) PSI + discard timer-based solution: One example of this solution is to configure three different timeout values ​​for the discard timer, such as timeout value 1, timeout value 2, and timeout value 3. On the UE side, the discard timer normally uses timeout value 1. When the gNB indicates network congestion to the UE, it also indicates a PSI threshold. The discard timer of PDU sets with low importance (PSI lower or higher than the PSI threshold) uses timeout value 2; the discard timer of PDU sets with high importance (PSI lower or higher than the PSI threshold) uses timeout value 3.

[0046] One example of this solution configures two timeout values ​​for the discard timer at each PSI level: timeout value 4 and timeout value 5. On the UE side, the discard timer uses timeout value 4 under normal circumstances; when the gNB indicates network congestion to the UE, the discard timer uses timeout value 5.

[0047] To better support gNB uplink resource scheduling and UE-side uplink data discarding during network congestion, this embodiment of the present invention proposes three mechanisms for coordinating Delay Status Reports (DSRs) and Buffer Status Reports (BSRs) to ensure information consistency and avoid redundant information and resource waste. The DSR and BSR coordination mechanisms specifically include:

[0048] ●Optionally configure DSR or BSR;

[0049] ●DSR and BSR are configured at the same time, and DSR triggers the cancellation of the corresponding BSR;

[0050] ●DSR and BSR are configured simultaneously, and DSR and BSR are triggered simultaneously and their information is complementary.

[0051] At the same time, to reduce unnecessary DSR reports, based on the DSR triggering rules, embodiments of the present invention propose a DSR shielding mechanism based on data attributes and a DSR shielding mechanism based on remaining time. Furthermore, embodiments of the present invention propose uplink data discarding and a packet integrity indication for distinguishing the Quality of Service (QoS) flows corresponding to service data units (SDUs) or protocol data units (PDUs). Different discarding schemes can be selected based on configuration information and different discarding schemes can be selected based on different congestion levels.

[0052] As explained above, both the DSR and BSR contain data volume information, namely, the cache size. If both the DSR and BSR target the same LCG, a coordination mechanism is clearly required to ensure information consistency and avoid redundant information that wastes resources.

[0053] Triggering DSR based on the decreasing remaining time is the most basic DSR triggering method. Since the remaining time of each buffered SDU or PDU in a PDU Set is constantly decreasing, the UE will always be triggered to perform DSR. This may result in a large number of DSRs, some of which may be outdated or unnecessary. If all these DSR MAC CEs are reported to the gNB, uplink resources may be wasted.

[0054] For uplink transmission, when network congestion occurs, the current multiple discarding schemes based on PSI have certain defects. In particular, the discarding scheme that does not consider the requirements of PHISI is not very perfect. As shown in Figure 1, multiple QoS flows with different packet set integrity indication (PDU Set Integrated Handling Indication, PSIHI) configurations are mapped to the same data radio bearer (DRB), and the DRB corresponds to the same logical channel (LCH) and PDCP entity. Each QoS flow transmits a PDU set (PDU Set) with a different PSI. If the PSIHI requirement is configured in the PDCP entity, if the discarding mechanism is simply enhanced based on PSI, the PDU or SDU of the QoS flow (QoS flow) with the packet set integrity requirement will be discarded, thereby actively violating the packet set integrity requirement.

[0055] Because DSR and BSR essentially report the cache size, but DSR reports more finely, the DSR and BSR mechanisms need to be coordinated with each other, including:

[0056] ●Optionally configure DSR or BSR;

[0057] ●DSR and BSR are configured at the same time, and DSR triggers the cancellation of the corresponding BSR;

[0058] ●DSR and BSR are configured simultaneously, and DSR and BSR are triggered simultaneously and their information is complementary.

[0059] These schemes are described in detail in Embodiments 1, 2 and 3, respectively.

[0060] At the same time, in order to reduce unnecessary DSR, based on the triggering rules of DSR, a DSR shielding mechanism based on data attributes and a DSR shielding mechanism based on remaining time are designed.

[0061] On the other hand, the PSI-based SDU or PDU discard solution needs to distinguish the configuration information of the packet integrity indicator of the QoS flow corresponding to the SDU or PDU, including:

[0062] For QoS flows with packet integrity requirements, retain the existing discard mechanism based on a discard timer, or configure a discard mechanism based on a PSI and a discard timer with a specific timeout value;

[0063] For QoS flows without packet integrity requirements, a PSI-based enhanced drop mechanism is used, which is described in Embodiment 7. Furthermore, different PSI-based drop schemes are selected based on different congestion levels, which is described in Embodiment 8.

[0064] The method for processing delay status reports may be executed in a telecommunication system.

[0065] Referring to Figure 2, a telecommunications system including UE 10a, UE 10b, base station (BS) 20a, and network entity device 30 performs the method disclosed in accordance with an embodiment of the present invention. Figure 2 is illustrative and non-limiting, and the system may include more UEs, BSs, and CN entities. Connections between devices and device components are shown as lines and arrows in the figure. User equipment 10a may include a processor 11a, a memory 12a, and a transceiver 13a. User equipment 10b may include a processor 11b, a memory 12b, and a transceiver 13b. Base station 20a may include a processor 21a, a memory 22a, and a transceiver 23a. Network entity device 30 may include a processor 31, a memory 32, and a transceiver 33. Each of processors 11a, 11b, 21a, and 31 may be configured to implement the functions, procedures, and / or methods described herein. The various layers of the radio interface protocol may be implemented in processors 11a, 11b, 21a, and 31. Each of the memories 12a, 12b, 22a, and 32 is operable to store various programs and information to operate the connected processor. Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled to the connected processor to transmit and / or receive radio signals or wired signals. The UE 10a can communicate with the UE 10b via a side link. The base station 20a can be an eNB, gNB, or other type of radio node and can configure radio resources for the UEs 10a and 10b.

[0066] Each of the processors 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Each of the memories 12a, 12b, 22a, and 32 may include a read-only memory (ROM), a random access memory (RAM), flash memory, a storage card, a storage medium, and / or other storage devices. Each of the transceivers 13a, 13b, 23a, and 33 may include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When this embodiment is implemented in software, the techniques described herein may be implemented using modules, programs, functions, entities, and the like that perform the functions described herein. These modules may be stored in a memory and executed by a processor. The memory may be implemented within the processor or externally, wherein the memory may be communicatively coupled to the processor in various ways known in the art.

[0067] The network entity device 30 may be a node in a CN. The CN may include an LTE CN or a 5G core (5GC), which includes a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane (CP) / user plane (UP) separation (CUPS), an authentication server (AUSF), a network slice selection function (NSSF), and a network exposure function (NEF).

[0068] Examples of UEs described herein may include one of the UE 10a or UE 10b. Examples of base stations described herein may include the base station 20a. Uplink (UL) transmission of control signals or data may be a transmission operation from a UE to a base station. Downlink (DL) transmission of control signals or data may be a transmission operation from a base station to a UE. DL control signals may include downlink control information (DCI) or radio resource control (RRC) signals from a base station to a UE.

[0069] 3 , an example of a user device is shown as user device 10, and an example of a base station is shown as base station 20. User device 10 includes a user plane protocol stack and a control plane protocol stack. The control plane includes a physical layer (PHY layer or L1 layer) 14c, a MAC layer 15c, an RLC layer 16c, a PDCP layer 17c, an RRC layer 18-1c, and a NAS layer 19-1c. The user plane includes a physical layer (PHY layer or L1 layer) 14c, a MAC layer 15c, an RLC layer 16c, a PDCP layer 17c, an SDAP layer 18-2c, an IP layer 19-2c, and an application layer 19-3c.

[0070] Base station 20 includes a user plane protocol stack and a control plane protocol stack. The control plane includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, and an RRC layer 18-1d. The user plane includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, an SDAP layer 18-2d, an IP layer 19-2d, and an application layer 19-3d.

[0071] For example, when the application layer 19-3c of the user equipment 10 sends a PDU to the application layer 19-3d of the base station 20 through the lower layers (i.e., the IP layer 19-2c, the SDAP layer 18-2c, the PDCP layer 17c, the RLC layer 16c, the MAC layer 15c, and the physical layer 14c), the layer in the user equipment 10 acts as a sending protocol layer entity at the sending end, and the layer in the base station 20 acts as a receiving protocol layer entity at the receiving end. The disclosed embodiments can be implemented in the MAC layer. One or more steps (or modules) in the embodiments of the present disclosure can be implemented as a computer program, an instruction, a software module stored in a memory of the user equipment 10 or the base station 20, or a circuit or hardware module in a processor of the user equipment 10 or the base station 20, or an integrated circuit chip, circuit, or plug-in of a sending device. The layer entities here provide examples of the layers mentioned in the description.

[0072] The layers in FIG3 may conform to the NR (New Radio) radio communication system defined by the 3GPP standard.

[0073] Referring to Figures 4 and 5 , a gNB 20 performs a wireless communication method. The gNB 20 may include an embodiment of the base station 20a. Note that while the gNB 20 is described as an example, the wireless communication method may be performed by a base station, such as another gNB, an eNB, a base station integrating an eNB and a gNB, or a base station beyond 5G technology. A UE 10 performs a wireless communication method. The UE 10 may include an embodiment of a UE 10a or a UE 10b.

[0074] 4 , the UE 10 generates and reports a Delay Status Report (DSR). When a BSR is configured, the UE 10 preferentially generates and / or reports the DSR, such as DSR 404 (S001) shown in FIG4 . The DSR includes remaining time information related to at least one data packet and data volume information corresponding to the remaining time information, and is reported via a Media Access Control Element (MAC CE). The MAC CE is a DSR MAC CE. The data packet includes at least one Protocol Data Unit (PDU) or Service Data Unit (SDU).

[0075] Based on a Delay Status Report (DSR) generated by UE 10, when a Buffer Status Report (BSR) is configured, UE 1 preferentially generates and reports a DSR, and gNB 20 receives the BSR or the DSR (e.g., DSR 404 shown in FIG. 4 ) ( S002 ). In one embodiment, UE 10 receives configuration information for a Delay Status Report (DSR), wherein the DSR is generated or reported based on the configuration information.

[0076] In some embodiments of the present invention, the configuration information is received via a Radio Resource Control (RRC) message.

[0077] In some embodiments of the present invention, all configuration information includes one or more of the following information:

[0078] Periodic DSR timer;

[0079] DSR retransmission timer;

[0080] Logical channel group LCG;

[0081] DSR logical channel scheduling request (SR) delay timer;

[0082] Apply DSR logical channel SR delay timer;

[0083] Shield the DSR logical channel SR;

[0084] Information about at least one remaining timeframe; and

[0085] At least one data volume threshold.

[0086] In some embodiments of the present invention, the at least one remaining time range related information corresponds to one or more remaining time ranges, and the remaining time ranges correspond to the levels of the remaining time ranges one by one. It is characterized in that, for a logical channel group LCG, the triggering condition of the conventional DSR is at least one of the following:

[0087] When there are multiple remaining time ranges, the minimum remaining time range corresponding to the data packet of the LCG is reduced to a smaller level of remaining time range, indicating that the level of the remaining time range corresponding to the data packet of the LCG is reduced;

[0088] When there are multiple remaining time ranges, the minimum remaining time range corresponding to the data packet of the LCG is reduced to a smaller level of remaining time range, indicating that the level of the remaining time range corresponding to the data packet of the LCG is reduced, and the amount of data corresponding to the minimum remaining time range reaches a predefined or preconfigured threshold;

[0089] When there are multiple remaining time ranges, the remaining time range corresponding to the data packet of the LCG is reduced to the minimum level remaining time range;

[0090] When there are multiple remaining time ranges, the remaining time range corresponding to the data packet of the LCG is reduced to the level of the minimum remaining time range, and the amount of data corresponding to the level of the minimum remaining time range reaches a predefined or preconfigured threshold;

[0091] When there is only one remaining time range, the remaining time range corresponding to the data packet of the LCG is reduced to the remaining time range;

[0092] When there is only one remaining time range, the remaining time range corresponding to the data packet of the LCG is reduced to the remaining time range, and the amount of data corresponding to the remaining time range reaches a predefined or preconfigured threshold;

[0093] A change in the amount of data corresponding to a remaining time range corresponding to the data packet of the LCG reaches a certain threshold;

[0094] A data packet corresponding to a logical channel having a higher priority than the logical channel corresponding to the existing data packet arrives; and

[0095] The logical channel group (LCG) buffer area changes from non-empty to empty.

[0096] In some embodiments of the present invention, the DSR shares a periodic BSR timer to trigger the periodic DSR; or the DSR uses the periodic DSR timer.

[0097] In some embodiments of the present invention, the configuration information of the DSR includes a first data attribute of the periodic DSR timer, and the periodic DSR timer is configured according to the first data attribute, and the first data attribute includes one or more of the following: LCG, LCH, QoS flow, protocol data unit set importance indication (PDU Set Importance Indicator, PSI) and protocol data unit set integrity indication (PDU Set Integrated Handling Indication, PSIHI).

[0098] In some embodiments of the present invention, in the padded DSR, when the user equipment is allocated uplink resources, if the padding bits of a media access control MAC PDU are loaded with a DSR MAC CE and a MAC subheader of the DSR MAC CE, the user equipment generates a DSR and transmits it through the MAC PDU.

[0099] In some embodiments of the present invention, the DSR shares a retransmission timer of the BSR for retransmitting the DSR; or the DSR uses the DSR retransmission timer to trigger retransmission of the DSR.

[0100] In some embodiments of the present invention, the remaining time information includes at least one remaining time range, the data amount is expressed as a buffer size, and the buffer size corresponding to the remaining time range is determined based on a second data attribute of the SDU or PDU included in the configuration information of the DSR, where the second data attribute includes at least one of the following:

[0101] The SDUs or PDUs of one or more logical channels are included in the buffer size calculation of the remaining time range;

[0102] The SDUs or PDUs of one or more QoS flows are included in the buffer size calculation for the remaining time range;

[0103] The SDUs or PDUs of one or more PSIs are included in the buffer size calculation for the remaining time range;

[0104] One or more SDUs or PDUs with PSIHI values ​​are included in the buffer size calculation for the remaining time range;

[0105] The SDUs or PDUs of one or more logical channels are excluded from the buffer size calculation of the remaining time range;

[0106] The SDUs or PDUs of one or more QoS flows are excluded from the buffer size calculation of the remaining time range;

[0107] One or more SDUs or PDUs of the PSI are excluded from the calculation of the buffer size of the remaining time range;

[0108] One or more SDUs or PDUs with PSIHI values ​​are excluded from the buffer size calculation for the remaining time range.

[0109] In some embodiments of the present invention, the configuration information of the DSR includes a third data attribute for triggering or prohibiting triggering the DSR, and the SDU or PDU corresponding to the third data attribute is configured to trigger or prohibit triggering the DSR, including one or more of the following:

[0110] Changes in the remaining time of SDUs or PDUs in the buffer corresponding to one or more LCGs will prohibit triggering DSR or prohibit the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR;

[0111] The remaining time change of the SDU or PDU of one or more logical channels (LCHs) is prohibited from triggering DSR or prohibiting the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR;

[0112] The change in the remaining time of the SDU or PDU of one or more QoS flows is prohibited from triggering DSR or is prohibited from including operations related to the remaining time and / or buffer size calculation that would trigger DSR;

[0113] The change in the remaining time of the SDU or PDU of one or more PSIs is prohibited from triggering a DSR or is prohibited from incorporating operations related to the remaining time and / or buffer size calculation that would trigger a DSR; and

[0114] The change in the remaining time of an SDU or PDU of one or more PSIHI values ​​is prohibited from triggering a DSR or from incorporating operations related to the remaining time and / or buffer size calculation that would trigger a DSR.

[0115] Changes in the remaining time of SDUs or PDUs in the buffer corresponding to one or more LCGs may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR;

[0116] Changes in the remaining time of the SDUs or PDUs of one or more logical channels (LCHs) may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR;

[0117] Changes in the remaining time of the SDU or PDU of one or more QoS flows may trigger DSR or include operations related to the remaining time and / or buffer size calculation that may trigger DSR;

[0118] Changes in the remaining time of one or more PSI SDUs or PDUs may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR; and

[0119] A change in the remaining time of an SDU or PDU of one or more PSIHI values ​​may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR.

[0120] In some embodiments of the present invention, the configuration information of the DSR includes the remaining time range information for enabling the DSR function. When the remaining time of an SDU or PDU is reduced to the remaining time range and the DSR function is enabled, the DSR is triggered; otherwise, the triggering of the DSR is prohibited.

[0121] In some embodiments of the present invention, the configuration information of the DSR includes a fourth data attribute for enabling the remaining time range of the DSR; according to the configured fourth data attribute, when the remaining time of the SDU or PDU corresponding to the fourth data attribute is reduced to the remaining time range, if the DSR function is enabled, the DSR is triggered, otherwise the triggering of the DSR is prohibited, and the fourth data attribute includes at least one of the following: LCG, LCH, QoS flow, PSI, and PSIHI.

[0122] In some embodiments of the present invention, the DSR configuration information includes the timeout value of the DSR shielding timer. When the user equipment generates a DSR information in the MAC entity, the DSR shielding timer is started. No new DSR is generated before the DSR shielding timer times out.

[0123] In some embodiments of the present invention, the DSR configuration information includes a timeout value of the DSR masking timer configured according to a fifth data attribute. When an SDU or PDU of the fifth data attribute triggers the generation of a DSR message, the DSR masking timer is started. Before the DSR masking timer times out, the fifth data attribute or the LCG corresponding to the fifth data attribute does not generate a new DSR. The timeout value of the DSR masking timer configured according to the fifth data attribute includes one or more of the following:

[0124] Configuring a timeout value of the DSR masking timer according to a logical channel group;

[0125] The timeout value of the DSR masking timer is configured according to the logical channel; that is, when the SDU or PDU of the LCH triggers the generation of a DSR message, the DSR masking timer is started, and before the DSR masking timer times out, the LCH or the LCG corresponding to the LCH does not generate a new DSR;

[0126] The timeout value of the DSR shielding timer is configured according to the QoS flow; that is, when the SDU or PDU of the QoS flow triggers the generation of a DSR information, the DSR shielding timer is started. Before the DSR shielding timer times out, the QoS flow or the LCG corresponding to the QoS flow does not generate a new DSR;

[0127] The timeout value of the DSR shielding timer is configured according to a certain PSI; that is, when the SDU or PDU identified as the PSI triggers the generation of a DSR information, the DSR shielding timer is started, and before the DSR shielding timer times out, the PSI or the LCG corresponding to the PSI does not generate a new DSR; or

[0128] The timeout value of the DSR shielding timer is configured according to PSIHI; that is, when the SDU or PDU configured as the PSIHI triggers the generation of a DSR information, the DSR shielding timer is started. Before the DSR shielding timer times out, the PSIHI value or the LCG corresponding to the PSIHI value does not generate a new DSR.

[0129] 5 , the gNB 20 provides Delay Status Report (DSR) configuration 402 , where the DSR configuration includes at least DSR and Buffer Status Report (BSR) coordination mechanism configuration ( S011 ). In this embodiment of the present invention, the DSR and BSR coordination mechanism configuration includes:

[0130] DSR and BSR configurations are mutually exclusive;

[0131] DSR and BSR are configured at the same time and DSR is reported first; or

[0132] DSR and BSR are generated simultaneously.

[0133] The UE 10 receives the delay status reporting configuration 402 ( S012 ).

[0134] The UE 10 performs a delay status report (DSR) according to a delay status report (DSR) configuration 402 , wherein the DSR configuration at least includes a coordination mechanism configuration for DSR and buffer status report (BSR) ( S013 ). The delay status report includes DSR information 404 .

[0135] The gNB 20 receives a latency status report including DSR information 404, wherein the latency status report is based on the latency status reporting configuration, and the DSR information 404 includes remaining time information of a plurality of data packets and data volume information corresponding to the remaining time information (S014). The plurality of data packets include a plurality of protocol data units (PDUs) or service data units (SDUs).

[0136] In an embodiment of the present invention, the DSR includes: a regular DSR, a periodic DSR, or a filling DSR according to a DSR triggering mode.

[0137] In an embodiment of the present invention, in the periodic DSR, the DSR and the BSR have a common timer for triggering the periodic DSR; or the DSR and the BSR have different timers, and the periodic DSR is triggered according to the DSR-specific timer.

[0138] DSR and BSR mutual coordination mechanism:

[0139] Implementation method 1: configured to perform only DSR or BSR operation.

[0140] For an uplink LCG, a gNB (e.g., gNB 20) uses a Radio Resource Control (RRC) message to configure and instruct a UE (e.g., UE 10) to perform a BSR or DSR operation. Specifically, the gNB (e.g., gNB 20) sends an RRC message to the UE (e.g., UE 10). The UE (e.g., UE 10) receives the RRC message. The RRC message may include configuration information or instructions related to the DSR operation. Specifically, Method 1: In the case where only DSR and BSR operations are configured, if the RRC message contains configuration information related to the DSR operation, the user equipment performs the DSR operation in the Medium Access Control (MAC) entity; if the RRC message does not contain configuration information related to the DSR operation, the user equipment performs the BSR operation in the MAC entity. Method 2: The RRC message configures an information element indicating that only DSR reporting is performed for the LCG. That is, if an uplink LCG is configured to perform DSR operation, a BSR operation is not performed for that LCG, and only DSR operation is performed. At the same time, the gNB also configures DSR-related information through RRC messages, including at least one of the following:

[0141] Periodic DSR timer (periodicDSR-Timer);

[0142] DSR retransmission timer (retxDSR-Timer);

[0143] Logical Channel Group (LCG);

[0144] DSR logical channel SR delay timer (dSRLogicalChannelSR-DelayTimer);

[0145] Apply DSR logical channel SR delay timer (dSRLogicalChannelSR-DelayTimerApplied);

[0146] Mask DSR logical channel SR (dSRLogicalChannelSR-Mask);

[0147] At least one remaining time or remaining time range;

[0148] Optionally, at least one data volume threshold;

[0149] For an uplink LCG, a DSR MAC CE needs to consider reporting all the data corresponding to the LCG or the data required by predefined / configured rules, i.e., the buffer size. The specific method for calculating the data volume can be found in Section 5.5 of 3GPP standard 38.322 and Section 5.6 of 38.323. The predefined / configured rules include:

[0150] The remaining time is less than a predefined / configured threshold; or,

[0151] The Packet Set Importance (PSI) is above a predefined / configured threshold; or,

[0152] The logical channel priority is above a predefined / configured threshold; or

[0153] There is a packet set integrity transmission requirement (PSIHI is set to 1 or 0).

[0154] For example, the buffer size in the LCG can be divided into several parts according to the remaining time information of all SDUs or PDUs in the LCG buffer, and then reported in a DSR MAC CE. A DSR MAC CE includes one or more of the following information:

[0155] (1) Remaining time information;

[0156] (2) Data volume information corresponding to the remaining time information; and

[0157] (3) Indication information of a cache size table corresponding to the cache size information.

[0158] (1) Remaining time information:

[0159] When configuring DSR information for a UE (e.g., UE 10), a gNB (e.g., gNB 20) may include:

[0160] One or more absolute time values; or

[0161] an index into a predefined table; or

[0162] Multiple time range information.

[0163] One or more absolute time values ​​representing a time range, such as configuring a 10ms time value to represent a time range of 0-10ms. Alternatively, you can configure three time values: 10ms, 20ms, and 30ms to represent the time ranges of 0-10ms, 10ms-20ms, and 20ms-30ms, respectively. One or more time range information, such as one or more time information groups [0,10] and [10,20] representing the time ranges of 0-10ms and 10ms-20ms, respectively.

[0164] In the reported DSR, the remaining time information corresponds to a configured time value, indicating a time range. For example, according to the above configuration information, 10 represents 0-10ms; 20 represents 10ms-20ms; and 30 represents 20ms-30ms. Alternatively, according to the above configuration information, the remaining time information can be indexed from small to large based on the time range value. For cache sizes that are not within the configured time range, other corresponding remaining time information can be indicated by a predefined special value, such as 0.

[0165] Predefined tables:

[0166] In some embodiments of the present invention, the Delay Status Report DSR further includes indication information related to a cache size table corresponding to the cache size information.

[0167] A predefined table includes a remaining time range index (Index) and a remaining time range, as shown in the following table.

[0168] Table 1

[0169] This predefined table may be called a remaining time range table. In the reported DSR, the remaining time information may be an index corresponding to a time range in the table.

[0170] (2) Data volume information corresponding to the remaining time information, i.e., cache size information: Optionally, the sum of cache sizes corresponding to multiple pieces of remaining time information is the total cache size corresponding to the LCG.

[0171] In particular, for an LCG, whether a data attribute is included in the cache size calculation for the remaining time range can be further configured according to a certain data attribute. If a data attribute is configured to be prohibited from being included in the cache size calculation for the remaining time range, then when calculating the cache size for a certain time range, the SDU or PDU corresponding to the data attribute is not included in the cache size calculation for the remaining time range. The remaining time information includes multiple remaining time ranges, and the configuration of the DSR includes a first data attribute for including or prohibiting the inclusion of the multiple data packets in the cache size calculation for each remaining time range. The first data attribute indicates one or more of the following:

[0172] Logical channel (LCH): that is, the SDU or PDU of one or more logical channels is included or prohibited from being included in the buffer size calculation of the remaining time range;

[0173] QoS flow: the SDUs or PDUs of one or more QoS flows are included or prohibited from being included in the buffer size calculation of the remaining time range;

[0174] PSI: that is, SDUs or PDUs identified as one or more PSIs are included or prohibited from being included in the buffer size calculation of the remaining time range; and

[0175] PSIHI: that is, one or more SDUs or PDUs configured as PSIHIs are included or prohibited from being included in the buffer size calculation of the remaining time range.

[0176] (3) Indication information of the remaining time range table corresponding to the cache size information: If there are two or more time range tables corresponding to the cache size information, the time range table indication information is used to identify or indicate one of the time range tables.

[0177] In particular, the types of DSR include:

[0178] (1) Regular DSR;

[0179] (2) Periodic DSR; and

[0180] (3) Padding DSR.

[0181] Regular DSR, triggered by one of the following:

[0182] ●The first trigger is triggered when the remaining time level changes. For example, the remaining time level of 0-10ms is 1, the remaining time level of 10ms-20ms is 2, and the remaining time level of 20ms-30ms is 3; the remaining time of some uplink data SDUs or PDUs in the buffer area of ​​a certain LCG is reduced to a smaller level of remaining time range. For example, when three time values ​​of 10ms, 20ms, and 30ms are configured, representing the three time ranges of 0-10ms, 10ms-20ms, and 20ms-30ms respectively, the time range is reduced from 20ms-30ms to 10ms-20ms; further, when the remaining time is reduced to a smaller level, the data volume of multiple data packets (SDUs or PDUs) in the remaining time range reaches a predefined or preconfigured threshold.

[0183] The second trigger is triggered only when the minimum remaining time range is reached, where the minimum remaining time range is 0-10ms. The remaining time of some uplink data SDUs or PDUs in the buffer area of ​​a certain LCG is reduced to the minimum remaining time range. For example, when three time values ​​of 10ms, 20ms, and 30ms are configured, representing the time ranges of 0-10ms, 10ms-20ms, and 20ms-30ms, respectively, the time range is reduced to 0ms-10ms. Furthermore, when the remaining time is reduced to the minimum remaining time range, the amount of data in the SDUs or PDUs reaches a predefined or preconfigured threshold.

[0184] The third type is when the data volume change for a certain remaining time range reaches a certain threshold. This happens when the data volume change for a certain remaining time range in an LCG buffer reaches a predetermined or preconfigured threshold. For example, when three time values, 10ms, 20ms, and 30ms, are configured, representing the time ranges of 0-10ms, 10ms-20ms, and 20ms-30ms, respectively, the data volume of the SDU or PDU corresponding to the remaining time range of 10ms-20ms increases or decreases by a predetermined or preconfigured threshold.

[0185] ● A data packet corresponding to a higher priority logical channel arrives relative to the logical channel corresponding to the existing data packet; further, the amount of data corresponding to the higher priority logical channel reaches a predefined or preconfigured threshold.

[0186] ●An LCG cache area changes from non-empty to empty.

[0187] Periodic DSR: In the periodic DSR, the DSR and the BSR have a common timer for triggering the periodic DSR; or the DSR and the BSR have different timers, and the periodic DSR is triggered according to the DSR-specific timer. The BSR shares the periodic BSR timer (period) configured by the gNB through RRC messages. When the DSR periodic timer expires, the DSR is triggered. The DSR periodic timer can share the periodic BSR timer (periodicBSR-Timer) and its configuration information configured by the gNB (e.g., gNB 20) through RRC messages with the BSR, or the gNB (e.g., gNB 20) can separately configure the periodic DSR timer (periodicDSR-Timer) and its configuration information through RRC messages.

[0188] Furthermore, the periodic DSR timer may be defined and configured based on data attributes of the SDU and PDU, wherein the second data attribute includes:

[0189] LCG: Configure the periodic DSR timer according to the logical channel group; that is, when the SDU or PDU of one or more LCGs indicated by the LCG attribute triggers the generation of a DSR information, start the periodic DSR timer. Before the periodic DSR timer expires, the LCG does not generate a new DSR;

[0190] LCH: Configure the periodic DSR timer according to the logical channel; that is, when the SDU or PDU of one or more LCHs indicated by the LCH attribute triggers the generation of a DSR message, start the periodic DSR timer. Before the periodic DSR timer expires, the LCH or the LCG corresponding to the LCH does not generate a new DSR;

[0191] QoS flow: Configure the periodic DSR timer according to the QoS flow; that is, when the SDU or PDU of one or more QoS flows indicated by the QoS flow attribute triggers the generation of a DSR message, start the periodic DSR timer. Before the periodic DSR timer expires, the QoS flow or the LCG corresponding to the QoS flow does not generate a new DSR;

[0192] PSI: configure the periodic DSR timer according to a certain PSI; that is, when an SDU or PDU of one or more PSIs identified as the PSI attribute triggers the generation of a DSR message, start the periodic DSR timer, and before the periodic DSR timer expires, the PSI or the LCG corresponding to the PSI does not generate a new DSR; or

[0193] PSIHI: Configure the periodic DSR timer according to PSIHI; that is, when an SDU or PDU configured with a PSIHI value indicated by the PSIHI triggers the generation of a DSR message, the periodic DSR timer is started. Before the periodic DSR timer expires, the PSIHI value or the LCG corresponding to the PSIHI value does not generate a new DSR.

[0194] Padding DSR: In the padding DSR, when the user equipment (e.g., UE 10) is allocated uplink resources, if the padding bits of a Medium Access Control (MAC) PDU can carry a DSR MAC control element (CE) and the MAC subheader of the DSR MAC CE, the user equipment (e.g., UE 10) generates a DSR and transmits it through the MAC PDU.

[0195] In some embodiments of the present invention, the DSR and the BSR have a shared retransmission timer for retransmitting the DSR. Alternatively, the DSR and the BSR have different retransmission timers, and retransmission of the periodic DSR is triggered based on the DSR-specific retransmission timer. For example, the gNB (e.g., gNB 20) configures a retransmission timer (retxDSR-Timer) for the DSR operation via an RRC message, or the DSR operation shares the BSR retransmission timer (retxBSR-Timer) configured by the gNB (e.g., gNB 20) via an RRC message. DSR retransmission can use a dedicated retransmission timer (retxDSR-Timer) or a shared BSR retransmission timer (retxBSR-Timer). When a UE (e.g., UE 10) sends a DSR, it starts a retransmission timer (retxDSR-Timer or retxBSR-Timer). If the UE (e.g., UE 10) does not receive a corresponding reception confirmation message for the DSR from the gNB (e.g., gNB 20) before the retransmission timer expires, such as a hybrid automatic repeat request (HARQ) confirmation message, the UE (e.g., UE 10) will retransmit the DSR.

[0196] In some embodiments of the present invention, when a UE (e.g., UE 10) generates a DSR, if no uplink resources are allocated to transmit the DSR, the DSR will further trigger an SR (Scheduling Request) to request the gNB (e.g., gNB 20) to allocate uplink resources to the UE (e.g., UE 10).

[0197] In some embodiments of the present invention, for DSR, a gNB (e.g., gNB 20) configures a UE (e.g., UE 10) via an RRC message to apply a DSR logical channel SR delay timer (dSRLogicalChannelSR-DelayTimerApplied), a DSR logical channel SR delay timer (dSRLogicalChannelSR-DelayTimer), and mask DSR logical channel SR (dSRLogicalChannelSR-Mask). These configurations can be dedicated to DSR or shared by DSR and BSR. A UE (e.g., UE 10) can share the DSR logical channel SR delay timer (dSRLlogicalChannelSR-DelayTimerApplied), a DSR logical channel SR delay timer (dSRLlogicalChannelSR-DelayTimer), and mask DSR logical channel SR (dSRLlogicalChannelSR-Mask) configured by a gNB (e.g., gNB 20). Based on these configurations, the UE (e.g., UE 10) performs the following operations:

[0198] When the shielded DSR logical channel SR is set to true (true), the DSR corresponding to the logical channel associated with the shielded DSR logical channel SR is prohibited from triggering SR;

[0199] When the SR delay timer for the DSR logical channel is set to true (true), when a DSR corresponding to the logical channel associated with the DSR logical channel SR delay timer occurs, the DSR logical channel SR delay timer is started; when the DSR logical channel SR delay timer times out, an SR is triggered;

[0200] ●When the SR delay timer of the DSR application logical channel is set to false, an SR is triggered when a DSR corresponding to the logical channel associated with the SR delay timer of the DSR application logical channel occurs.

[0201] In some embodiments of the present invention, a UE (eg, UE 10) may include DSR information of one or more LCGs in one DSR MAC CE.

[0202] In some embodiments of the present invention, it is characterized in that a DSR MAC CE includes DSRs of multiple LCGs, and for the DSR of each LCG, the cache size and remaining time information corresponding to the multiple remaining time range values ​​are preferentially loaded according to the size of the remaining time range value.

[0203] Furthermore, the UE (e.g., UE 10) may preferentially load the cache size and remaining time information of the multiple LCGs with less remaining time in a DSR MAC CE; the UE (e.g., UE 10) may preferentially load the cache size and remaining time information of the logical channels with higher priority corresponding to the cache sizes in the multiple LCGs.

[0204] In some embodiments of the present invention, a UE (e.g., UE 10) may select different DSR MAC CE formats to generate different types of DSR MAC CEs; for example, a short DSR MAC CE (short DSR MAC CE), in which the buffer size information occupies a relatively small bit width, such as 5 bits; or a long DSR MAC CE, in which the buffer size information occupies a relatively large bit width, such as 8 bits.

[0205] In some embodiments of the present invention, when an SDU or PDU in a buffer corresponding to a DSR is successfully transmitted or discarded, the DSR and the corresponding SR are cancelled.

[0206] In some embodiments of the present invention, for an LCG, after triggering the generation of a DSR related to the LCG and an SR corresponding to the DSR, when the SR is in a pending state and a new DSR related to the LCG is triggered, the DSR generated before the new DSR and the SR corresponding to the generated DSR are canceled.

[0207] In particular, for a UE (eg, UE 10), when a normal DSR, a periodic DSR, and a padding DSR need to be transmitted at the same time, the normal DSR has the highest priority, the periodic DSR takes the second place, and the padding DSR has the lowest priority.

[0208] In particular, only one DSR can be carried in one MAC PDU.

[0209] Implementation method 2: DSR and BSR are configured at the same time, but DSR is generated and reported first.

[0210] For an uplink LCG, the UE (e.g., UE 10) performs a BSR operation by default. Specifically, the gNB (e.g., gNB 20) sends an RRC message to the UE (e.g., UE 10). The UE (e.g., UE 10) receives the RRC message. The RRC message may include configuration information or instructions related to the DSR operation. The UE (e.g., UE 10) performs the DSR operation according to the configuration of the gNB (e.g., gNB 20) through the RRC message. In the configuration where DSR and BSR are configured simultaneously and DSR is reported first, if the RRC message contains configuration information related to DSR and BSR operations, the user equipment performs DSR and BSR operations in the Medium Access Control (MAC) entity; if the RRC message does not contain configuration information related to DSR operations, the user equipment performs a BSR operation in the MAC entity. It should be noted that the generation method and triggering cause of DSR are as described above, the information contained in the DSR MAC CE is as described above, and the configuration of DSR is also as described above.

[0211] For an uplink LCG, if DSR operation is configured, the UE (e.g., UE 10) performs BSR and DSR operations simultaneously and coordinates them. A DSR MAC CE needs to consider reporting the total amount of data corresponding to the LCG or the amount of data required by predefined / configured rules (the specific calculation method of the data amount can be found in Section 5.5 of 3GPP Standard 38.322 and Section 5.6 of 3GPP Standard 38.323), i.e., the buffer size. The predefined / configured rules include:

[0212] The remaining time is less than a predefined / configured threshold; or,

[0213] The Packet Set Importance (PSI) is above a predefined / configured threshold; or,

[0214] The logical channel priority is above a predefined / configured threshold; or

[0215] There is a packet set integrity transmission requirement (PSIHI is set to 1 or 0).

[0216] For example, the total buffer size in the LCG can be divided into several parts based on the remaining time information of all SDUs or PDUs in the LCG's buffer, and then reported in a DSR MAC CE. The information included in the DSR MAC CE and the specific DSR operation can refer to the corresponding content in Implementation 1. The BSR reports according to the existing mechanism, that is, reports the corresponding total data volume information in the LCG buffer. At the same time, the BSR and DSR coordinate with each other according to one or more of the following methods:

[0217] For an LCG, after the BSR information of the LCG and the SR corresponding to the BSR information are triggered, when the SR is in a suspended state and a new DSR is triggered for the LCG, the BSR information generated before the new DSR and the SR corresponding to the generated DSR are canceled.

[0218] For an LCG, after the DSR information of the LCG and the SR corresponding to the DSR information have been triggered, when the SR is in a suspended state and new BSR information is triggered for the LCG, the new BSR information and the SR corresponding to the new BSR information are canceled.

[0219] Implementation 3: DSR and BSR are configured simultaneously, and DSR and BSR are generated and reported simultaneously.

[0220] For an uplink LCG, the UE (e.g., UE 10) performs a BSR by default. The UE (e.g., UE 10) performs a DSR according to the configuration of the gNB (e.g., gNB 20). If the gNB (e.g., gNB 20) is not configured for DSR, the UE (e.g., UE 10) does not perform DSR. If the gNB (e.g., gNB 20) is configured for DSR, the UE (e.g., UE 10) performs DSR. It should be noted that the generation method and triggering cause of DSR are as described above, the information contained in the DSR MAC CE is as described above, and the configuration of DSR is also as described above.

[0221] Specifically, the gNB (e.g., gNB 20) sends an RRC message to the UE (e.g., UE 10). The UE (e.g., UE 10) receives the RRC message. The RRC message may include configuration information or instructions related to the DSR operation. The UE (e.g., UE 10) performs the DSR operation according to the configuration of the gNB (e.g., gNB 20) through the RRC message. In the configuration in which the DSR and BSR are generated simultaneously, if the RRC message contains configuration information related to the DSR operation and the BSR operation, the user equipment performs the DSR operation and the BSR operation in the Medium Access Control (MAC) entity; if the RRC message does not contain configuration information related to the DSR operation, the user equipment performs the BSR operation in the MAC entity.

[0222] If an uplink LCG is configured with DSR operation, the UE (e.g., UE 10) generates both DSR and BSR information. The DSR only reports the amount of data in the LCG buffer and the corresponding remaining time information. For information on the DSR MAC CE and the specific DSR operation, please refer to the corresponding content in Implementation 1. The BSR is reported according to the existing mechanism, that is, the corresponding data amount information in the LCG buffer is reported. Specifically:

[0223] ●When DSR is triggered, a DSR MAC CE and a corresponding BSR MAC CE are triggered simultaneously.

[0224] ●When BSR is triggered, a DSR MAC CE and a corresponding BSR MAC CE are triggered simultaneously.

[0225] When the DSR MAC CE and the corresponding BSR MAC CE can be transmitted in the same MAC PDU, transmitting the DSR MAC CE and the corresponding BSR MAC CE simultaneously;

[0226] When the DSR MAC CE and the corresponding BSR MAC CE cannot be transmitted in one MAC PDU, preferentially transmitting the DSR MAC CE;

[0227] ●When a generated BSR is canceled, the corresponding DSR generated at the same time is also canceled.

[0228] It can be understood that when a MAC PDU transmits the DSR MAC CE and the BSR MAC CE simultaneously and the MAC PDU resources are sufficient, the DSR MAC CE and the BSR MAC CE are transmitted simultaneously. When a MAC PDU transmits the DSR MAC CE and the BSR MAC CE simultaneously but there is insufficient resources, the DSR MAC CE is transmitted first.

[0229] Implementation 4: DSR shielding based on data attributes

[0230] For an uplink LCG, the gNB (e.g., gNB 20) can configure the DSR masking parameter to the UE (e.g., UE 10) via an RRC message. The DSR masking parameter can be configured based on data attributes of the SDU or PDU. For SDUs or PDUs corresponding to the configured data attributes, the MAC entity on the UE (e.g., UE 10) will not trigger DSR. The data attributes corresponding to the DSR masking parameter include one or more of the following:

[0231] (1) Logical Channel Group (LCG): If the logical channel group (LCG) DSR mask parameter (logicalChannelGroupDSR-mask) of a logical channel group is set to "needs to be masked", then at the MAC entity on the UE (e.g., UE 10), the remaining time range and / or data volume changes of the SDU or PDU in the cache corresponding to the LCG associated with the logical channel group (LCG) DSR mask parameter (logicalChannelGroupDSR-mask) will not trigger DSR. Furthermore, operations related to the calculation of the remaining time and data volume are not performed for the SDU or PDU mapped to the LCG. Alternatively, the remaining time of the SDU or PDU mapped to the LCG is set to a special value, such as infinity, 0, etc., to control that DSR will not be triggered.

[0232] (2) Logical channel (LCH): If the logical channel DSR mask parameter (logicalChannelDSR-Mask) of a logical channel is set to "needs to be masked", then at the MAC entity on the UE (e.g., UE 10) side, the remaining time range and / or data volume change of the SDU or PDU mapped to the logical channel (LCH) associated with the logical channel (LCH) mask DSR parameter will not trigger DSR. Furthermore, operations related to the calculation of the remaining time and data volume are not performed on the SDU or PDU mapped to the LCH. Alternatively, the remaining time of the SDU or PDU mapped to the LCH is set to a special value, such as infinity, 0, etc., to control that DSR will not be triggered.

[0233] (3) QoS flow: If the QoS flow mask DSR parameter (qosFlowDSR-Mask) of a QoS flow is set to "masking required", then at the MAC entity on the UE (e.g., UE 10) side, the remaining time range and / or data volume change of the SDU or PDU from the QoS flow associated with the QoS flow mask DSR parameter will not trigger DSR. Furthermore, operations related to the calculation of the remaining time and data volume are not performed for the SDU or PDU from the QoS flow. Alternatively, the remaining time of the SDU or PDU from the QoS flow is set to a special value, such as infinity, 0, etc., to control that DSR will not be triggered.

[0234] (4) PSI: If the PSI mask DSR parameter (psiDSR-Mask) of a PSI is set to "masking required", then at the MAC entity on the UE (e.g., UE 10), the remaining time range and / or data volume change of the SDU or PDU identified as the PSI associated with the PSI mask DSR parameter will not trigger DSR. Furthermore, operations related to the calculation of the remaining time and data volume are not performed for the SDU or PDU identified as the PSI. Alternatively, the remaining time of the SDU or PDU identified as the PSI is set to a special value, such as infinity, 0, etc., to control that DSR will not be triggered.

[0235] (5) PSIHI: If the PSIP mask DSR parameter (PSIHIDSR-Mask) of a PSIHI is set to "masking required", then at the MAC entity on the UE (e.g., UE 10), the remaining time range and / or data volume changes of the SDU or PDU from the QoS flow associated with the PSIHI mask DSR parameter will not trigger DSR. Furthermore, operations related to the calculation of the remaining time and data volume are not performed for the SDU or PDU from the QoS flow. Alternatively, the remaining time of the SDU or PDU from the QoS flow is set to a special value, such as infinity, 0, etc., to control that DSR will not be triggered.

[0236] Similarly, DSR triggering parameters can also be configured to the UE (e.g., UE 10) via an RRC message. The DSR triggering parameters can be configured based on the data attributes of the SDU or PDU. For the SDU or PDU corresponding to the configured data attributes, the MAC entity on the UE (e.g., UE 10) side will trigger DSR. The data attributes corresponding to the DSR triggering parameters and their usage are similar to those for the DSR shielding parameters described above.

[0237] It is worth noting that the data attribute-based DSR shielding of Implementation Method 4 can be combined with any one of Implementation Method 1, Implementation Method 2 or Implementation Method 3 to achieve flexible control of DSR.

[0238] Implementation 5: DSR shielding based on remaining time.

[0239] To report more detailed DSR information, the gNB (e.g., gNB 20) configures multiple remaining time ranges for the UE (e.g., UE 10). The UE (e.g., UE 10) then reports the multiple remaining time range information and its corresponding buffer size information in the DSR MAC CE. However, to reduce the number of DSR reports, an Enable DSR parameter for each remaining time range can be further configured for one or more remaining time ranges to indicate whether the remaining time range triggers DSR or not. For example, when three time values ​​of 10ms, 20ms, and 30ms are configured, representing the three time ranges of 0ms to 10ms, 10ms to 20ms, and 20ms to 30ms, respectively, the Enable DSR parameter for each event range configures the time range of 0ms to 10ms to trigger DSR, while the time ranges of 10ms to 20ms and 20ms to 30ms are configured not to trigger DSR. Based on the enable DSR parameter of the remaining time range, the MAC entity on the UE (e.g., UE 10) side will not trigger DSR when the remaining time of an SDU or PDU decreases to the range of 10ms to 20ms and 20ms to 30ms; however, when the remaining time of an SDU or PDU decreases to the range of 0ms to 10ms, DSR will be triggered. In particular, when the enable DSR parameter based on the remaining time range is optionally configured, it can be based on one or more of the following data attributes:

[0240] (1) Logical Channel Group (LCG): The LCG-based DSR enable parameter indicates whether DSR is triggered or not when the remaining time of the SDU or PDU mapped to the corresponding logical channel group decreases and enters the remaining time range of the DSR shield;

[0241] (2) Logical Channel (LCH): The LCH-based DSR enabling parameter indicates whether DSR is triggered or not when the remaining time of the SDU or PDU mapped to the corresponding logical channel decreases and enters the remaining time range of the DSR shield;

[0242] (3) QoS flow: The QoS flow-based DSR enable parameter indicates whether DSR is triggered or not when the remaining time of the SDU or PDU from the corresponding QoS flow decreases and enters the remaining time range of the DSR shield;

[0243] (4) PDU Set Importance Indicator (PSI): The PSI-based DSR enabling parameter indicates whether DSR is triggered or not when the remaining time of an SDU or PDU identified by the corresponding PSI value decreases and enters the remaining time range of the DSR mask;

[0244] (5) PDU Set Integrated Handling Indication (PSIHI): When the remaining time of the SDU or PDU configured with the corresponding PSIHI value decreases and enters the remaining time range of the DSR shield, DSR is triggered or not triggered.

[0245] It is worth noting that the DSR shielding based on the remaining time in Implementation 5 can be combined with any one of Implementation 1, Implementation 2 or Implementation 3 to achieve flexible control of DSR.

[0246] Implementation 6: Timer-based DSR blocking

[0247] For an uplink LCG, the system defines a DSR blocking timer (dsrProhibit-timer). The gNB (e.g., gNB 20) can configure the timeout value of the DSR blocking timer to the UE (e.g., UE 10) through an RRC message. The timer can be used multiple times in different scenarios, including simultaneous use, and the timeout values ​​when used can be the same or different. The MAC entity on the UE (e.g., UE 10) side starts the DSR blocking timer whenever a DSR message is generated. No new DSR is generated before the blocking timer expires; further, no new BSR is generated before the timer expires. For example, the DSR configuration information includes the timeout value of the DSR blocking timer configured according to the fifth data attribute. When the SDU or PDU of the fifth data attribute triggers the generation of a DSR message, the DSR blocking timer is started. Before the DSR blocking timer expires, the fifth data attribute or the LCG corresponding to the fifth data attribute does not generate a new DSR. Optionally, the timeout value configuration of the DSR blocking timer can be based on one or more of the following data attributes:

[0248] (1) Logical Channel Group (LCG): The DSR masking timer is used and the DSR masking timer timeout value is configured according to the logical channel group; that is, when the SDU or PDU of the LCG triggers the generation of a DSR message, the DSR masking timer is started. Before the DSR masking timer times out (corresponding to the timeout value), the LCG does not generate a new DSR;

[0249] (2) Logical Channel (LCH): that is, the DSR masking timer is used and the DSR masking timer timeout value is configured according to the logical channel; that is, when the SDU or PDU of the LCH triggers the generation of a DSR message, the DSR masking timer is started. Before the DSR masking timer times out (corresponding to the timeout value), the LCH or the LCG corresponding to the LCH does not generate a new DSR;

[0250] (3) QoS flow: that is, the DSR shielding timer is used and the DSR shielding timer timeout value is configured according to the QoS flow; that is, when the SDU or PDU of the QoS flow triggers the generation of a DSR message, the DSR shielding timer is started. Before the DSR shielding timer times out (corresponding to the timeout value), the QoS flow or the LCG corresponding to the QoS flow does not generate a new DSR;

[0251] (4) PSI: that is, using the DSR shielding timer and configuring the DSR shielding timer timeout value according to a certain PSI; that is, when an SDU or PDU identified as the PSI triggers the generation of a DSR message, the DSR shielding timer is started, and before the DSR shielding timer times out (corresponding to the timeout value), the PSI or the LCG corresponding to the PSI does not generate a new DSR; and

[0252] (5) PSIHI: that is, using the DSR shielding timer and configuring the DSR shielding timer timeout value according to PSIHI; that is, when the SDU or PDU configured as the PSIHI triggers the generation of a DSR message, the DSR shielding timer is started, and before the DSR shielding timer times out (corresponding to the timeout value), the PSIHI value or the LCG corresponding to the PSIHI value does not generate a new DSR.

[0253] It is worth noting that the timer-based DSR shielding of Implementation 6 can be combined with any one of Implementation 1, Implementation 2 or Implementation 3 to achieve flexible control of DSR.

[0254] PSI-based discarding:

[0255] Implementation 7: Discarding Based on PSI and / or PSIHI

[0256] When network congestion occurs, the gNB (e.g., gNB 20) sends congestion indication information to the UE (e.g., UE 10) via an RRC message or a control protocol unit (e.g., PDCP control PDU, RLC control PDU, or MAC CE), and optionally indicates a PSI threshold at the same time. The PDCP entity on the UE (e.g., UE 10) side needs to perform a discard operation based on the PSIHI information of the QoS flow. For example, discarding PDUs or SDUs of a PDU set (PDU Set) for a QoS flow (QoS flow) that does not require integrity transmission, if the packet set integrity indicator PSIHI information indicates that the PDU or SDU is discarded, takes precedence over discarding PDUs or SDUs of a PDU set (PDU Set) for a QoS flow (QoS flow) that requires integrity transmission, if the packet set integrity indicator PSIHI information indicates that the PDU or SDU is discarded. Specifically, the PDCP entity of the UE (e.g., UE 10) discards SDUs or PDUs of a PDU set (PDU Set) in one of the following ways:

[0257] (1) According to data radio bearers (DRBs), for PDU sets (PDU Sets) of QoS flows that require integrity transmission and for which the packet set integrity indicator (PSIHI) information is set, SDU or PDU discard is performed based on the normal discard timer mechanism; for PDU sets (PDU Sets) of QoS flows that do not require integrity transmission, the enhanced discard mechanism based on PSI is applied to discard SDU or PDU. The enhanced discard mechanism based on PSI includes:

[0258] PSI threshold-based schemes, and

[0259] A solution based on PSI and discard timer (PSI+discard timer).

[0260] In some embodiments of the present invention, the configuration may also be performed on an LCG basis, and the configuration information of the LCG will be applicable to all DRBs mapped to the LCG.

[0261] The gNB (e.g., gNB 20) configures (including explicit or implicit configuration) through an RRC message sent to the UE (e.g., UE 10): for QoS flows (QoS flows) for which the Packet Integrity Indicator (PSIHI) information is set to not requiring integrity transmission, the PSI-based enhanced discard mechanism is applied; for QoS flows (QoS flows) for which the Packet Integrity Indicator (PSIHI) information is set to require integrity transmission, the existing basic discard timer mechanism is used for discarding.

[0262] Example 1: For example, QoS flows 1 and QoS flows 2 are mapped to the same logical channel, DRB1. The PSIHI for QoS flow 1 is configured as requiring integrity transmission, while the PSIHI for QoS flow 2 is configured as not requiring integrity transmission. For DRB1, the following configurations are implemented: QoS flows with a PSIHI indicating that integrity transmission is not required are discarded using a PSI threshold + discard timer scheme; QoS flows with a PSIHI indicating that integrity transmission is required are discarded using the existing basic discard timer mechanism. Furthermore, the discard timer is configured with a timeout value of 1 = 50ms for non-congested states, 2 = 20ms for congested states, and 3 = 30ms for congested states. On the UE side, the PDCP entity corresponding to DRB1 uses a timeout value of 1 = 50ms for SDUs or PDUs from both QoS flows 1 and 2 when in a non-congested state (i.e., when no congestion indication is received or the congestion indication is canceled). When congestion indication information is received, the indication information includes a PSI threshold. For SDUs or PDUs from QoS flow 1, the discard timers of all SDUs or PDUs still use the timeout value 1 = 50ms, without distinguishing the PSI information of different SDUs or PDUs; for QoS flow 2, if the PSI of the SDU or PDU is greater than and / or equal to the PSI threshold, the discard timer uses the timeout value 2 = 20ms; if the PSI of the SDU or PDU is less than and / or equal to the PSI threshold, the discard timer uses the timeout value 3 = 30ms.

[0263] (2) According to the QoS flow, the packet set integrity indication PSIHI information is set to the PDU or SDU of the QoS flow (QoS flow) that needs to be transmitted with integrity, and a specific discard timer timeout value is configured, including: configuring a discard timer timeout value that applies to all PDUs or SDUs of the QoS flow (QoS flow) without distinguishing the PSI information of the PDU or SDU; such as the configuration and usage method of QoS flow 1 in Example 1.

[0264] Example 2: For example, if the PSIHI information of QoS flow 4 indicates that integrity transmission is required, the discard timer timeout value 1 = 50ms is configured for this QoS flow; the PSIHI information of QoS flow 5 indicates that integrity transmission is not required. For this QoS flow, a PSI threshold-based solution is configured, and the discard timer timeout value 1 = 40ms is configured; at the same time, QoS flow 4 and QoS flow 5 are configured to be mapped to the same DRB2. On the PDCP entity corresponding to DRB2 on the UE side, in a non-congested state, the SDUs or PDUs from QoS flow 1 and QoS flow 2 use timeout values ​​of 1 = 50ms and 1 = 40ms, respectively. When a congestion indication is received, the indication includes a PSI threshold. For SDUs or PDUs from QoS flow 1, the discard timers of all SDUs or PDUs still use a timeout value of 1 = 50ms, regardless of the PSI information of different SDUs or PDUs. For QoS flow 2, if the PSI of the SDU or PDU is greater than and / or equal to the PSI threshold, it is immediately discarded. If the PSI of the SDU or PDU is less than and / or equal to the PSI threshold, the discard timer uses a timeout value of 1 = 40ms. For the PSI and discard timer (PSI + discard timer) discard scheme, one or more specific discard timer timeout values ​​are configured for the QoS flow.

[0265] Example 3: QoS flow 3's PSIHI information requires integrity transmission, and two timeout values ​​are configured: timeout 4 = 50ms and timeout 5 = 60ms. For the PDCP entity on the UE side, in a non-congested state, the discard timer for the SDU or PDU of QoS flow 3 uses a timeout of 4 = 50ms. Upon receiving a network congestion indication, the discard timer for the SDU or PDU of QoS flow 3 uses a timeout of 5 = 60ms. However, for QoS flow 3, the PSI information of different SDUs or PDUs is not differentiated.

[0266] The gNB (e.g., gNB 20) implements the above configuration process by sending an RRC message to the UE (e.g., UE 10), which includes one or more of the following configuration information:

[0267] Packet integrity indication PSIHI information related to QoS flow;

[0268] Dropping method and / or its related parameters based on QoS flow and / or corresponding PSIHI information;

[0269] Dropping method and / or related parameters based on DRB and / or QoS flow PSIHI information;

[0270] Dropping method based on LCH and / or QoS flow PSIHI information and / or its related parameters.

[0271] If the network recovers from congestion, the gNB (e.g., gNB 20) sends a decongestion indication to the UE (e.g., UE 10) via an RRC message or a PDCP control PDU. The PDCP entity on the UE (e.g., UE 10) discards the SDU or PDU based on the normal discard timer mechanism, regardless of the PSIHI information of the QoS flow and the PSI information of the PDU or SDU.

[0272] Implementation 8: Dropping based on congestion level and PSI

[0273] When network congestion occurs, the gNB (e.g., gNB 20) sends congestion indication information to the UE (e.g., UE 10) via an RRC message or a control protocol element (e.g., PDCP control PDU, RLC control PDU, or MAC CE). The congestion indication information further includes one or more of the following information:

[0274] Congestion level indication information,

[0275] Application scenario information;

[0276] Business type information;

[0277] Optionally, a PSI threshold is indicated at the same time. Corresponding to the PDCP entity on the UE (e.g., UE 10), different discard mechanisms are selected based on the congestion level indication information, and / or application scenario information, and / or service type information. Specifically, the PDCP entity of the UE (e.g., UE 10) discards the SDU or PDU of the PDU Set (PDU Set) according to one of the following implementation methods:

[0278] (1) If the congestion level is high, packets are discarded based on the PSI threshold. Otherwise, packets are discarded based on the PSI and discard timer (PSI + discard timer).

[0279] (2) If the service type during congestion is delay-sensitive, the service is discarded based on the PSI threshold; otherwise, the service is discarded based on the PSI + discard timer solution;

[0280] (3) If the application scenario has high security requirements, the scheme based on PSI threshold is used for discarding; otherwise, the scheme based on PSI and discard timer (PSI+discard timer) is used for discarding;

[0281] If the network recovers from the congested state to the normal state, the gNB (e.g., gNB 20) sends a congestion relief indication to the UE (e.g., UE 10) through an RRC message or a PDCP control PDU. The PDCP entity on the UE (e.g., UE 10) discards the SDU or PDU based on the normal discard timer mechanism, without distinguishing between the PSIHI information of the QoS flow and the PSI information of the PDU or SDU.

[0282] 6 , an embodiment of the present application further provides a chip 700. This chip 700 may correspond to the user device 10 in the embodiment of the present application, and this chip 700 may implement the corresponding processes implemented by the user device 10 in each method in the embodiment of the present application. The chip 700 includes a processor 701, which may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0283] Optionally, the chip 700 may further include a memory 702. The processor 701 may call and execute a computer program from the memory 702 to implement the method in the embodiment of the present application.

[0284] The memory 702 may be a separate device independent of the processor 701 , or may be integrated into the processor 701 .

[0285] Optionally, the chip 700 may further include an input interface 703. The processor 701 may control the input interface 703 to communicate with other devices or chips, and specifically, may obtain messages or data sent by other devices or chips.

[0286] Optionally, the chip 700 may further include an output interface 704. The processor 701 may control the output interface 704 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0287] Referring to Figure 7 , another embodiment of the present application provides another chip 800. This chip 800 may correspond to the gNB 20 in the embodiments of the present application and may implement the corresponding processes implemented by the gNB 20 in the various methods of the embodiments of the present application. This chip 800 includes a processor 801, which may call and execute computer programs from a memory 802 to implement the methods of the embodiments of the present application.

[0288] Optionally, the chip 800 may further include a memory 802. The processor 801 may call and execute a computer program from the memory 802 to implement the method in the embodiment of the present application.

[0289] The memory 802 may be a separate device independent of the processor 801 , or may be integrated into the processor 801 .

[0290] Optionally, the chip 800 may further include an input interface 803. The processor 801 may control the input interface 803 to communicate with other devices or chips, and specifically, may obtain messages or data sent by other devices or chips.

[0291] Optionally, the chip may further include an output interface 804. The processor 801 may control the output interface 804 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0292] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-described method embodiment may be completed through hardware integrated logic circuits in the processor or through software instructions. The above-described processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above-described method.

[0293] It is understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronized DRAM (SLDRAM), and direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0294] It should also be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0295] The embodiments of the present application also provide a computer program product, including computer program instructions.

[0296] Optionally, the computer program product can be applied to the gNB 20 in the implementation mode of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the gNB 20 in the various methods of the implementation mode of the present application. For the sake of brevity, they are not repeated here.

[0297] Optionally, the computer program product can be applied to the user device 10 in the implementation mode of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the user device 10 in the various methods of the implementation mode of the present application. For the sake of brevity, they are not repeated here.

[0298] The embodiments of the present application also provide a computer program.

[0299] Optionally, the computer program can be applied to the gNB 20 in the implementation mode of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the gNB 20 in the various methods of the implementation mode of the present application. For the sake of brevity, they are not repeated here.

[0300] Optionally, the computer program can be applied to the user device 10 in the implementation mode of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the user device 10 in the various methods of the implementation mode of the present application. For the sake of brevity, they are not repeated here.

[0301] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0302] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the aforementioned method implementation methods and will not be repeated here.

[0303] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of the unit is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0304] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of this embodiment.

[0305] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist as a separate entity, or two or more units may be integrated into one unit.

[0306] If this function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of each embodiment of the present application. The aforementioned storage medium is a non-volatile storage medium, including: a flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes.

[0307] Those skilled in the art will appreciate that the above-mentioned embodiments are specific embodiments for implementing the present application, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present application.

Claims

1. A method for processing a delay status report, executed in a user equipment, characterized in that: Include: Generate and report a Delay Status Report (DSR), wherein when the BSR is configured, the DSR is preferentially generated and / or reported.

2. The method for processing a delay status report according to claim 1, characterized in that: Also includes: Receive configuration information of a delay status report DSR, wherein the DSR is generated or reported according to the configuration information.

3. The method for processing a delay status report according to claim 1, characterized in that: The delay status report DSR includes remaining time information related to at least one data packet and data volume information corresponding to the remaining time information, and is reported through a medium access control element MAC CE, wherein the MAC CE is a DSR MAC CE.

4. The method for processing a delay status report according to claim 3, characterized in that: The data packet includes at least one protocol data unit (PDU) or service data unit (SDU).

5. The method for processing a delay status report according to claim 2, characterized in that: The configuration information is received via a Radio Resource Control (RRC) message; All configuration information includes one or more of the following: Periodic DSR timer; DSR retransmission timer; Logical channel group LCG; DSR logical channel scheduling request (SR) delay timer; Apply DSR logical channel SR delay timer; Shield the DSR logical channel SR; at least one remaining time frame; and At least one data volume threshold.

6. The method for processing a delay status report according to claim 5, characterized in that: The preset DSR triggering modes include: regular DSR, periodic DSR or filling DSR.

7. The method for processing a delay status report according to claim 6, characterized in that: The at least one remaining time range related information corresponds to one or more remaining time ranges, and the remaining time ranges correspond to the levels of the remaining time ranges in a one-to-one correspondence.

8. The method for processing a delay status report according to claim 7, characterized in that: For a logical channel group LCG, the triggering condition of the conventional DSR is at least one of the following: When there are multiple remaining time ranges, the minimum remaining time range corresponding to the data packet of the LCG is reduced to a smaller level of remaining time range, indicating that the level of the remaining time range corresponding to the data packet of the LCG is reduced; When there are multiple remaining time ranges, the minimum remaining time range corresponding to the data packet of the LCG is reduced to a smaller level of remaining time range, indicating that the level of the remaining time range corresponding to the data packet of the LCG is reduced, and the amount of data corresponding to the minimum remaining time range reaches a predefined or preconfigured threshold; When there are multiple remaining time ranges, the remaining time range corresponding to the data packet of the LCG is reduced to the minimum level remaining time range; When there are multiple remaining time ranges, the remaining time range corresponding to the data packet of the LCG is reduced to the level of the minimum remaining time range, and the amount of data corresponding to the level of the minimum remaining time range reaches a predefined or preconfigured threshold; When there is only one remaining time range, the remaining time range corresponding to the data packet of the LCG is reduced to the remaining time range; When there is only one remaining time range, the remaining time range corresponding to the data packet of the LCG is reduced to the remaining time range, and the amount of data corresponding to the remaining time range reaches a predefined or preconfigured threshold; A change in the amount of data corresponding to a remaining time range corresponding to the data packet of the LCG reaches a certain threshold; A data packet corresponding to a logical channel having a higher priority than the logical channel corresponding to the existing data packet arrives; and The logical channel group (Logic Channel Group, LCG) buffer area changes from non-empty to empty.

9. The method for processing a delay status report according to claim 6, characterized in that: The DSR shares a periodic BSR timer to trigger the periodic DSR; or the DSR uses the periodic DSR timer.

10. The method for processing a delay status report according to claim 9, characterized in that: The configuration information of the DSR includes a first data attribute of the periodic DSR timer, and the periodic DSR timer is configured according to the first data attribute. The first data attribute includes one or more of the following: LCG, LCH, QoS flow, protocol data unit set importance indication (PDU Set Importance Indicator, PSI) and protocol data unit set integrity indication (PDU Set Integrated Handling Indication, PSIHI).

11. The method for processing a delay status report according to claim 6, characterized in that: In the padding DSR, when the user equipment is allocated uplink resources, if the padding bits of a media access control MAC PDU are loaded with a DSR MAC CE and a MAC subheader of the DSR MAC CE, the user equipment generates a DSR and transmits it through the MAC PDU.

12. The method for processing a delay status report according to claim 5, characterized in that: The DSR shares the retransmission timer of the BSR to retransmit the DSR; or the DSR uses the DSR retransmission timer to trigger retransmission of the DSR.

13. The method for processing a delay status report according to claim 1, characterized in that: When the user equipment generates the DSR and no uplink resources for transmitting the DSR are allocated, the DSR triggers a scheduling request SR.

14. The method for processing delay status report according to claims 5 and 13, characterized in that: The user equipment is configured with an application DSR logical channel SR delay timer, a DSR logical channel SR delay timer, and a shielded DSR logical channel SR. Based on the application DSR logical channel SR delay timer, the DSR logical channel SR delay timer, and the shielded DSR logical channel SR, the user equipment performs the following operations: When the shielded DSR logical channel SR is set to true (true), the DSR corresponding to the logical channel associated with the shielded DSR logical channel SR is prohibited from triggering SR; When the application DSR logical channel SR delay timer is set to true (true), when a DSR corresponding to a logical channel associated with the application DSR logical channel SR delay timer is generated, the DSR logical channel SR delay timer is started; when the DSR logical channel SR delay timer times out, an SR is triggered; When the SR delay timer of the DSR application logical channel is set to false, an SR is triggered when a DSR corresponding to the logical channel associated with the SR delay timer of the DSR application logical channel occurs.

15. The method for processing a delay status report according to claim 13, characterized in that: When the SDU or PDU in the buffer corresponding to the DSR is successfully transmitted or discarded, the DSR and the SR corresponding to the DSR are cancelled.

16. The method for processing a delay status report according to claim 5, characterized in that: For an LCG, after the DSR related to the LCG and the SR corresponding to the DSR are triggered, when the SR is in a suspended state and a new DSR related to the LCG is triggered, the DSR generated before the new DSR and the SR corresponding to the generated DSR are canceled.

17. The method for processing a delay status report according to claim 3, characterized in that: One DSR MAC CE includes DSRs of multiple LCGs. For the DSR of each LCG, the cache sizes and remaining time information corresponding to the multiple remaining time range values ​​are loaded preferentially according to the size of the remaining time range values.

18. The method for processing a delay status report according to claim 3, characterized in that: Different DSR MAC CE formats are selected to generate different types of DSR MAC CEs, wherein the types of the DSR MAC CEs include: Short DSR MAC CE and long DSR MAC CE.

19. The method for processing a delay status report according to claim 3, characterized in that: The delay status report DSR also includes indication information related to the cache size table corresponding to the cache size information.

20. The method for processing a delay status report according to claim 5, characterized in that: The configuration information includes indication information for reporting only the DSR, and the indication information includes at least one of the following: DSR configuration information configured to LCG in RRC message; The indication configured to the LCG in the RRC message only reports the information element of the DSR.

21. The method for processing a delay status report according to claim 20, characterized in that: If the configuration information only reports the indication information of the DSR, the user equipment only triggers the generation and reporting of the DSR, and is prohibited from triggering the generation and reporting of the BSR.

22. The method for processing a delay status report according to claim 1, characterized in that: When BSR is configured, priority generation and / or reporting of DSR includes: for an LCG, after triggering the generation of BSR information of the LCG and the SR corresponding to the BSR information, when the SR is in a suspended state and a new DSR is triggered for the LCG, canceling the BSR information that has been generated before the new DSR and the SR that has been generated corresponding to the DSR.

23. The method for processing a delay status report according to claim 1, characterized in that: When BSR is configured, priority generation and / or reporting of DSR includes: for an LCG, after the DSR information of the LCG and the SR corresponding to the DSR information have been triggered, when the SR is in a suspended state and new BSR information is triggered for the LCG, the new BSR information and the SR corresponding to the new BSR information are canceled.

24. The method for processing a delay status report according to claim 1, characterized in that: When DSR is triggered, a DSR MAC CE and a BSR MAC CE are triggered simultaneously; When the BSR is triggered, a DSR MAC CE and a BSR MAC CE are triggered simultaneously; and When the BSR is cancelled, the DSR generated is also cancelled at the same time.

25. The method for processing a delay status report according to claim 24, characterized in that: When the BSR is configured, the DSR is preferentially generated and / or reported, including: when a MAC PDU transmits the DSR MAC CE and the BSR MAC CE simultaneously and the MAC PDU resources are sufficient, the DSR MAC CE and the BSR MAC CE are transmitted simultaneously; and When a MAC PDU has insufficient resources when transmitting the DSR MAC CE and the BSR MAC CE at the same time, the DSR MAC CE is transmitted preferentially.

26. The method for processing a delay status report according to claim 3, characterized in that: The remaining time information includes at least one remaining time range, the data amount is expressed as a cache size, and the cache size corresponding to the remaining time range is determined based on a second data attribute of an SDU or a PDU included in the configuration information of the DSR, wherein the second data attribute includes at least one of the following: The SDUs or PDUs of one or more logical channels are included in the calculation of the buffer size of the remaining time range; The SDUs or PDUs of one or more QoS flows are included in the calculation of the cache size of the remaining time range; The SDU or PDU of one or more PSIs is included in the calculation of the buffer size of the remaining time range; One or more SDUs or PDUs with PSIHI values ​​are included in the calculation of the buffer size for the remaining time range; The SDUs or PDUs of one or more logical channels are excluded from the calculation of the buffer size of the remaining time range; The SDUs or PDUs of one or more QoS flows are excluded from the cache size calculation of the remaining time range; The SDUs or PDUs of one or more PSIs are excluded from the calculation of the buffer size of the remaining time range; One or more SDUs or PDUs with PSIHI values ​​are excluded from the buffer size calculation for the remaining time range.

27. The method for processing a delay status report according to claim 1, characterized in that: The configuration information of the DSR further includes a third data attribute for triggering or prohibiting triggering the DSR, and the SDU or PDU corresponding to the third data attribute is configured to trigger or prohibit triggering the DSR, including one or more of the following: The change of the remaining time of the SDU or PDU in the buffer corresponding to one or more LCGs will prohibit the triggering of DSR or prohibit the inclusion of operations related to the remaining time and / or buffer size calculation that will trigger DSR; The remaining time change of the SDU or PDU of one or more logical channels (LCH) is prohibited from triggering DSR or the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR; The remaining time change of the SDU or PDU of one or more QoS flows is prohibited from triggering DSR or the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR; The remaining time change of the SDU or PDU of one or more PSIs is prohibited from triggering DSR or is prohibited from incorporating operations related to the remaining time and / or buffer size calculation that would trigger DSR; and A change in the remaining time of an SDU or PDU of one or more PSIHI values ​​is prohibited from triggering a DSR or from incorporating operations related to the remaining time and / or buffer size calculation that would trigger a DSR. Changes in the remaining time of SDUs or PDUs in the buffer corresponding to one or more LCGs may trigger a DSR or include operations related to remaining time and / or buffer size calculation that may trigger a DSR; Changes in the remaining time of the SDU or PDU of one or more logical channels (LCHs) may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR; Changes in the remaining time of the SDU or PDU of one or more QoS flows may trigger DSR or include operations related to remaining time and / or buffer size calculation that may trigger DSR; Changes in the remaining time of one or more PSI SDUs or PDUs may trigger DSR or include operations related to remaining time and / or buffer size calculation that may trigger DSR; and A change in the remaining time of an SDU or PDU of one or more PSIHI values ​​may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR.

28. The method for processing a delay status report according to claim 1, characterized in that: The configuration information of the DSR includes the remaining time range information for enabling the DSR function. When the remaining time of an SDU or PDU is reduced to the remaining time range and the DSR function is enabled, the DSR is triggered, otherwise the triggering of the DSR is prohibited.

29. The method for processing a delay status report according to claim 28, characterized in that: The configuration information of the DSR includes a fourth data attribute for enabling the remaining time range of the DSR; according to the configured fourth data attribute, when the remaining time of the SDU or PDU corresponding to the fourth data attribute is reduced to the remaining time range, if the DSR function is enabled, the DSR is triggered, otherwise the triggering of the DSR is prohibited, and the fourth data attribute includes at least one of the following: LCG, LCH, QoS flow, PSI, and PSIHI.

30. The method for processing a delay status report according to claim 5, characterized in that: The configuration information of the DSR includes the timeout value of the DSR shielding timer. When the user equipment generates a DSR information in the MAC entity, the DSR shielding timer is started. Before the DSR shielding timer times out, no new DSR is generated.

31. The method for processing a delay status report according to claim 30, characterized in that: The configuration information of the DSR further includes a timeout value of the DSR shielding timer configured according to the fifth data attribute. When the SDU or PDU of the fifth data attribute triggers the generation of a DSR information, the DSR shielding timer is started. Before the DSR shielding timer times out, the fifth data attribute or the LCG corresponding to the fifth data attribute does not generate a new DSR. The timeout value of the DSR shielding timer configured according to the fifth data attribute includes one or more of the following: Configuring a timeout value of the DSR masking timer according to a logical channel group; Configure the timeout value of the DSR masking timer according to the logical channel; Configure the timeout value of the DSR shielding timer according to the QoS flow; Configure the timeout value of the DSR masking timer according to a certain PSI; or The timeout value of the DSR masking timer is configured according to PSIHI.

32. A user equipment, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that the device installed with the above-mentioned program executes the above-mentioned method of any one of claims 1 to 31.

33. A chip, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that the device installed with the above-mentioned program executes the above-mentioned method of any one of claims 1 to 31.

34. A computer-readable storage medium, characterized in that A computer program is stored therein, wherein the computer program enables a computer to execute the method of any one of claims 1 to 31.

35. A computer program product, characterized in that Comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 31.

36. A method for processing a delay status report, executed in a network node, characterized in that: Include: Based on a Delay Status Report (DSR) generated by a user equipment, when a Buffer Status Report (BSR) is configured, the user equipment preferentially generates and reports the DSR, and the network node receives The BSR or the DSR.

37. The method for processing a delay status report according to claim 36, characterized in that: Also includes: Configuration information for sending a Delay Status Report (DSR), wherein the DSR is generated or reported according to the configuration information.

38. The method for processing a delay status report according to claim 36, characterized in that: The delay status report DSR includes remaining time information related to at least one data packet and data volume information corresponding to the remaining time information, and is reported through a medium access control element MAC CE, wherein the MAC CE is a DSR MAC CE.

39. The method for processing a delay status report according to claim 38, characterized in that: The data packet includes at least one protocol data unit (PDU) or service data unit (SDU).

40. The method for processing a delay status report according to claim 37, characterized in that: The configuration information is sent via a Radio Resource Control (RRC) message; All configuration information includes one or more of the following: Periodic DSR timer; DSR retransmission timer; Logical channel groups; DSR logical channel scheduling request (SR) delay timer; Apply DSR logical channel SR delay timer; Shield the DSR logical channel SR; at least one remaining time frame; and At least one data volume threshold.

41. The method for processing a delay status report according to claim 40, characterized in that: The configuration information of the DSR also includes a first data attribute of the periodic DSR timer, and the periodic DSR timer is configured according to the first data attribute. The first data attribute includes one or more of the following: LCG, LCH, QoS flow, protocol data unit set importance indication (PDU Set Importance Indicator, PSI) and protocol data unit set integrity indication (PDU Set Integrated Handling Indication, PSIHI).

42. The method for processing a delay status report according to claim 36, characterized in that: The configuration information includes indication information for reporting only the DSR, and the indication information includes at least one of the following: DSR configuration information configured to LCG in RRC message; The indication configured to the LCG in the RRC message only reports the information element of the DSR.

43. The method for processing a delay status report according to claim 36, characterized in that: The remaining time information includes at least one remaining time range, the data amount is expressed as a cache size, and the cache size corresponding to the remaining time range is determined based on a second data attribute of an SDU or a PDU included in the configuration information of the DSR, wherein the second data attribute includes at least one of the following: The SDUs or PDUs of one or more logical channels are included in the calculation of the buffer size of the remaining time range; The SDUs or PDUs of one or more QoS flows are included in the calculation of the cache size of the remaining time range; The SDU or PDU of one or more PSIs is included in the calculation of the buffer size of the remaining time range; One or more SDUs or PDUs with PSIHI values ​​are included in the calculation of the buffer size for the remaining time range; The SDUs or PDUs of one or more logical channels are excluded from the calculation of the buffer size of the remaining time range; The SDUs or PDUs of one or more QoS flows are excluded from the cache size calculation of the remaining time range; The SDUs or PDUs of one or more PSIs are excluded from the calculation of the buffer size of the remaining time range; One or more SDUs or PDUs with PSIHI values ​​are excluded from the buffer size calculation for the remaining time range.

44. The method for processing a delay status report according to claim 36, characterized in that: The configuration information of the DSR includes a third data attribute for triggering or prohibiting triggering the DSR, and the SDU or PDU corresponding to the third data attribute is configured to trigger or prohibit triggering the DSR, including one or more of the following: The change of the remaining time of the SDU or PDU in the buffer corresponding to one or more LCGs will prohibit the triggering of DSR or prohibit the inclusion of operations related to the remaining time and / or buffer size calculation that will trigger DSR; The remaining time change of the SDU or PDU of one or more logical channels (LCH) is prohibited from triggering DSR or the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR; The remaining time change of the SDU or PDU of one or more QoS flows is prohibited from triggering DSR or the inclusion of operations related to the remaining time and / or buffer size calculation that would trigger DSR; The remaining time change of the SDU or PDU of one or more PSIs is prohibited from triggering DSR or is prohibited from incorporating operations related to the remaining time and / or buffer size calculation that would trigger DSR; and A change in the remaining time of an SDU or PDU of one or more PSIHI values ​​is prohibited from triggering a DSR or from incorporating operations related to the remaining time and / or buffer size calculation that would trigger a DSR. Changes in the remaining time of SDUs or PDUs in the buffer corresponding to one or more LCGs may trigger a DSR or include operations related to remaining time and / or buffer size calculation that may trigger a DSR; Changes in the remaining time of the SDU or PDU of one or more logical channels (LCHs) may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR; The remaining time of the SDU or PDU of one or more QoS flows changes, triggering DSR or including the remaining time of the SDU or PDU that triggers DSR. Operations related to timing and / or cache size calculations; Changes in the remaining time of one or more PSI SDUs or PDUs may trigger DSR or include operations related to remaining time and / or buffer size calculation that may trigger DSR; and A change in the remaining time of an SDU or PDU of one or more PSIHI values ​​may trigger a DSR or include operations related to the remaining time and / or buffer size calculation that may trigger a DSR.

45. The method for processing a delay status report according to claim 36, characterized in that: The configuration information of the DSR includes the remaining time range information for enabling the DSR function. When the remaining time of an SDU or PDU is reduced to the remaining time range and the DSR function is enabled, the DSR is triggered, otherwise the triggering of the DSR is prohibited.

46. ​​The method for processing a delay status report according to claim 45, characterized in that: The configuration information of the DSR includes a fourth data attribute for enabling the remaining time range of the DSR; according to the configured fourth data attribute, when the remaining time of the SDU or PDU corresponding to the fourth data attribute is reduced to the remaining time range, if the DSR function is enabled, the DSR is triggered, otherwise the triggering of the DSR is prohibited, and the fourth data attribute includes at least one of the following: LCG, LCH, QoS flow, PSI, and PSIHI.

47. The method for processing a delay status report according to claim 36, characterized in that: The configuration information of the DSR includes the timeout value of the DSR shielding timer. When the user equipment generates a DSR information in the MAC entity, the DSR shielding timer is started. Before the DSR shielding timer times out, no new DSR is generated.

48. The method for processing a delay status report according to claim 47, It is characterized in that The configuration information of the DSR further includes a timeout value of the DSR shielding timer configured according to the fifth data attribute. When the SDU or PDU of the fifth data attribute triggers the generation of a DSR information, the DSR shielding timer is started. Before the DSR shielding timer times out, the fifth data attribute or the LCG corresponding to the fifth data attribute does not generate a new DSR. The timeout value of the DSR shielding timer configured according to the fifth data attribute includes one or more of the following: Configuring a timeout value of the DSR masking timer according to a logical channel group; Configure the timeout value of the DSR masking timer according to the logical channel; Configure the timeout value of the DSR shielding timer according to the QoS flow; Configure the timeout value of the DSR masking timer according to a certain PSI; or The timeout value of the DSR masking timer is configured according to PSIHI.

49. A base station, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that the device installed with the above-mentioned program executes the above-mentioned method of any one of claims 36 to 48.

50. A chip, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that the device installed with the above-mentioned program executes the above-mentioned method of any one of claims 36 to 48.

51. A computer-readable storage medium, characterized in that A computer program is stored therein, wherein the computer program enables a computer to execute the method of any one of claims 36 to 48.

52. A computer program product, characterized in that Comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 36 to 48.

Images