Communication method, device and system

Abstract

This application provides a communication method, apparatus, and system, relating to the field of communications. The method includes: suppressing the transmission of Delay Status Reports (DSRs) corresponding to a first type of LCG (Limited Time Group) when the network device is in a congested state. The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream. The data stream types corresponding to different LCGs include delay-sensitive streams and non-delay-sensitive streams. Therefore, when the network device is in a congested state, the transmission frequency of DSRs corresponding to the first type of LCG can be reduced, thereby reducing the signaling overhead of the terminal device, lowering the consumption of signaling resources, and reducing the power consumption of the terminal device.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method, apparatus, and system. Background Technology

[0002] Terminal devices can report delay status reports (DSRs) to the base station, allowing the base station to understand the buffer status and data latency of the terminal devices based on the information in the reports. This enables the base station to perform resource scheduling more rationally, preventing data from being discarded due to long waiting times for resource scheduling, and improving the transmission efficiency and reliability of the system.

[0003] However, base station resources are limited, and there may be situations where resource allocation is insufficient, making it impossible to schedule data transmission resources for terminal devices. In such cases, the DSRs continuously sent by the terminal device to the base station will consume excessive signaling resources of the terminal device, resulting in unnecessary signaling overhead and increased power consumption of the terminal device. Summary of the Invention

[0004] This application provides a communication method, apparatus, and system that can suppress the transmission of Delay Status Reports (DSRs) corresponding to a first type of LCG (Limited Time Group) when network devices are in a congested state. The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream. Therefore, when network devices are in a congested state, the transmission frequency of DSRs corresponding to the first type of LCG can be reduced, thereby reducing the signaling overhead of the terminal device, lowering the consumption of signaling resources, and reducing the power consumption of the terminal device.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a communication method is provided. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this. The following description uses a terminal device as an example. The method includes:

[0007] When a terminal device receives a notification indicating that a network device is in a congested state, it can suppress the transmission of Delay Status Reports (DSRs) corresponding to the first type of LCG, that is, it can suppress DSRs corresponding to non-delay-sensitive flows. The data flow types corresponding to different LCGs include delay-sensitive flows and non-delay-sensitive flows.

[0008] Based on the method in the first aspect, upon receiving notification information, the terminal device can determine that the network device is in a congested state. In this state, even if the terminal device sends a DSR (Data Source Retrieval), the network device may be unable to allocate resources to respond. In this case, continuous DSR transmission by the terminal device increases signaling overhead and wastes signaling resources. However, in this application, when the terminal device determines that the network device is congested, since the data stream corresponding to the first type of LCG is a non-delay-sensitive stream with low real-time requirements, it can suppress DSR transmissions corresponding to the first type of LCG. Since the data stream corresponding to the second type of LCG is a delay-sensitive stream with high real-time requirements, ensuring DSR transmissions for the second type of LCG reduces the frequency and number of DSR transmissions, thereby reducing the signaling resources and overhead occupied by DSR transmissions and ultimately reducing the power consumption of the terminal device.

[0009] In one possible implementation of the first aspect, before receiving notification information, the terminal device may send the DSR corresponding to the LCG when a first triggering condition is met; upon receiving notification information, the network device is in a congested state and sends the DSR of the first type of LCG corresponding to a non-delay-sensitive flow when a second triggering condition is met. The frequency of sending the DSR of the first type of LCG corresponding to the non-delay-sensitive flow based on the first triggering condition is a first transmission frequency, and the frequency of sending the DSR of the first type of LCG corresponding to the non-delay-sensitive flow based on the second triggering condition is a second transmission frequency, and the second transmission frequency is less than the first transmission frequency.

[0010] Therefore, when network devices are in a congested state, terminal devices will suppress the transmission of DSRs of the first type of LCG corresponding to non-delay-sensitive flows. That is, DSRs of the first type of LCG corresponding to non-delay-sensitive flows will only be transmitted when the second triggering condition is met, so that the second transmission frequency is less than the first transmission frequency, thereby reducing the transmission frequency of DSRs of the first type of LCG corresponding to non-delay-sensitive flows, reducing signaling overhead, reducing the occupation of signaling resources, and avoiding signaling redundancy in transmitting DSRs.

[0011] In one possible implementation of the first aspect, the triggering condition includes one or more of the following triggering parameters: a buffer data volume threshold, a data remaining duration threshold, or a DSR transmission period. The triggering condition may include a first triggering condition, a second triggering condition, or a third triggering condition.

[0012] Therefore, terminal devices can configure the DSR triggering conditions by configuring any one or more of the buffer data volume threshold, the remaining data duration threshold, or the DSR transmission cycle, thereby triggering the DSR reporting, enabling network devices to allocate network resources and complete data transmission.

[0013] In one possible implementation of the first aspect, when the network device is in a congested state, the terminal device sends a DSR of the second type of LCG corresponding to the delay-sensitive flow when a first triggering condition or a third triggering condition is met. The data flow type of the second type of LCG corresponding to the delay-sensitive flow includes delay-sensitive flow. The frequency at which the DSR of the second type of LCG corresponding to the delay-sensitive flow is sent based on the third triggering condition is a third sending frequency, and the third sending frequency is greater than the second sending frequency.

[0014] Therefore, when network devices are in a congested state, terminal devices can keep the triggering conditions of DSR for the second type of LCG corresponding to the delay-sensitive flow unchanged. That is, when the first triggering condition is met, the terminal device sends the DSR of the second type of LCG corresponding to the delay-sensitive flow, thereby ensuring that the DSR of the second type of LCG corresponding to the delay-sensitive flow can be reported in a timely manner, avoiding the inability to obtain network resources in a timely manner.

[0015] When network devices are congested, terminal devices can also reduce the frequency of DSR transmission for the second type of LCG corresponding to delay-sensitive flows. That is, when the third triggering condition is met, the terminal device transmits the DSR for the second type of LCG corresponding to the delay-sensitive flow, thereby reducing the signaling overhead of transmitting the DSR for the second type of LCG corresponding to the delay-sensitive flow and reducing the waste of signaling resources.

[0016] Furthermore, when the third triggering condition is met, the frequency at which the terminal device sends the DSR of the second type of LCG corresponding to the delay-sensitive flow is greater than the frequency at which the terminal device sends the DSR of the second type of LCG corresponding to the delay-sensitive flow when the second triggering condition is met. That is, the third frequency is greater than the second frequency, thereby ensuring that the DSR of the second type of LCG corresponding to the delay-sensitive flow can be reported in a timely manner, avoiding the inability to obtain network resources in a timely manner.

[0017] In one possible implementation of the first aspect, each LCG corresponds to its own first triggering condition, which includes multiple sets of triggering thresholds with different levels of urgency, and the second triggering condition is the set of triggering thresholds with the highest level of urgency among the multiple sets of triggering thresholds.

[0018] Therefore, terminal devices can dynamically adjust the number of DSR triggering conditions when network devices are congested. When the LCG has a low priority or the data flow type corresponding to the LCG is a non-delay-sensitive flow, the terminal device can trigger DSR based on the highest urgency trigger threshold configured by the network device. That is, when the second triggering condition is met, the terminal device sends the DSR for the first type of LCG corresponding to the non-delay-sensitive flow, thereby reducing the number of DSR reports, reducing control signaling overhead, and avoiding unnecessary resource waste. Furthermore, when the LCG has a high priority or the data flow type corresponding to the LCG is a delay-sensitive flow, the DSR triggering conditions remain unchanged. That is, when the first triggering condition is met, the terminal device sends the DSR for the corresponding LCG, thereby ensuring that the terminal device's data can be scheduled and processed in a timely manner.

[0019] In one possible implementation of the first aspect, the trigger threshold includes a buffer data volume threshold and a remaining time threshold, and the second trigger condition is the set of trigger thresholds with the largest buffer data volume threshold and the smallest remaining time threshold among multiple sets of trigger thresholds.

[0020] Therefore, the terminal device can send the DSR corresponding to the LCG while meeting the maximum buffer data volume threshold or the minimum remaining duration threshold, thereby suppressing the frequency of the terminal device sending the DSR corresponding to the LCG to the greatest extent and reducing signaling overhead.

[0021] In one possible implementation of the first aspect, the first triggering condition includes a first DSR transmission period, the second triggering condition includes a second DSR transmission period, and the second DSR transmission period is greater than the first DSR transmission period.

[0022] Therefore, compared with related technologies, the terminal device in this embodiment increases the reporting period of DSR for non-delay-sensitive flows and reduces the reporting frequency of DSR when the network device is in a congested state, thereby reducing terminal signaling overhead and avoiding unnecessary resource waste. Furthermore, when the network device is in a congested state, the terminal device maintains the reporting period of DSR for delay-sensitive flows unchanged, thereby ensuring that delay-sensitive flows or high-priority data can be transmitted in a timely manner, guaranteeing the effectiveness of data transmission.

[0023] In one possible implementation of the first aspect, the third triggering condition includes a preset first buffer data volume threshold, and the second triggering condition includes a preset second buffer data volume threshold, wherein the second buffer data volume threshold is greater than the first buffer data volume threshold.

[0024] Therefore, when the network device is in a congested state, a third triggering condition can be configured when the LCG corresponds to the second LCG. The third triggering condition includes a first buffer data volume threshold. When the LCG corresponds to the first LCG, a second triggering condition can be configured. The second triggering condition includes a second buffer data volume threshold, which is greater than the first buffer data volume threshold. This reduces the frequency of DSR transmission by the network device in a non-congested state when the LCG corresponds to the first LCG, thereby reducing signaling overhead, reducing resource consumption, and reducing the power consumption of the terminal device.

[0025] In one possible implementation of the first aspect, the third triggering condition includes a preset first effective remaining time, and the second triggering condition includes a preset second effective remaining time, wherein the second effective remaining time is less than the first effective remaining time.

[0026] Therefore, when the network device is in a congested state, a third triggering condition can be configured when the LCG corresponds to the second LCG. The third triggering condition includes the first valid remaining duration. When the LCG corresponds to the first LCG, a second triggering condition can be configured. The second triggering condition includes the second valid remaining duration, which is less than the first valid remaining duration. This reduces the frequency of DSR transmission by the network device in a non-congested state when the LCG corresponds to the first LCG, thereby reducing signaling overhead, reducing resource consumption, and reducing the power consumption of the terminal device.

[0027] In one possible implementation of the first aspect, each LCG corresponds to its own first triggering condition; when the network device is in a congested state, the DSR of the second type of LCG corresponding to the delay-sensitive flow is sent when the first triggering condition is met; the second triggering condition includes a preset second buffer data volume threshold.

[0028] Therefore, when network devices are congested, if the LCG is the second LCG corresponding to a delay-sensitive flow, a first trigger condition can be configured. Each LCG corresponds to its own first trigger condition, thereby ensuring the timeliness of data transmission for delay-sensitive flows and ensuring that the trigger conditions for service requirements corresponding to different LCGs are different, thus improving data transmission efficiency. If the LCG is the first LCG corresponding to a non-delay-sensitive flow, the DSR corresponding to the first LCG is sent if the second buffer data volume threshold is met, thereby reducing the signaling overhead of the terminal device.

[0029] In one possible implementation of the first aspect, each LCG corresponds to its own first triggering condition; when the network device is in a congested state, the DSR of the second type of LCG corresponding to the delay-sensitive flow is sent when the first triggering condition is met; the second triggering condition includes a preset second valid remaining duration.

[0030] Therefore, when a network device is in a congested state and the LCG corresponds to the second LCG of a delay-sensitive flow, a first trigger condition can be configured. Each LCG corresponds to its own first trigger condition, thereby ensuring the timeliness of data transmission for delay-sensitive flows and ensuring that the trigger conditions for service requirements corresponding to different LCGs are different, thus improving data transmission efficiency. When the LCG corresponds to the first LCG of a non-delay-sensitive flow, the DSR corresponding to the first LCG is sent if the second valid remaining duration is satisfied, thereby reducing the signaling overhead of the terminal device.

[0031] In one possible implementation of the first aspect, when the network device is in a congested state, the terminal device will also determine whether the amount of data in the buffer has changed significantly. If the increase in the amount of buffer data of the first type of LCG corresponding to the non-delay-sensitive flow is greater than or equal to a first threshold, and / or the amount of buffer data is greater than or equal to a second threshold, the DSR will be sent.

[0032] Therefore, when the network device is in a congested state and the LCG corresponds to the first LCG, if the increase in the buffer data volume of the first type of LCG corresponding to the non-delay-sensitive flow is greater than or equal to the first threshold, or the buffer data volume is greater than or equal to the second threshold, that is, the data of the terminal device has changed significantly, the terminal device will immediately trigger DSR and report its own data status even if the terminal device does not meet the triggering conditions of DSR, thereby facilitating the network device to discover the data status of the terminal device in a timely manner and perform resource scheduling.

[0033] In one possible implementation of the first aspect, the second threshold is twice the amount of buffer data required to trigger DSR transmission when the network device is in a congested state.

[0034] Therefore, when the network device is in a congested state and the LCG corresponds to the first LCG, if the buffer data volume is greater than or equal to the second threshold, that is, the buffer data volume is greater than or equal to twice the buffer data volume threshold used to trigger DSR transmission when the network device is in a congested state, the terminal device will immediately trigger DSR and report its own data status, thereby facilitating the network device to promptly discover the data status of the terminal device and perform resource scheduling.

[0035] In one possible implementation of the first aspect, the data flow type corresponding to the LCG is determined based on the Quality of Service (QoS) identifier corresponding to the LCG. The QoS identifier may include a packet delay budget. When the packet delay budget is less than a third threshold, the data flow type corresponding to the LCG is a delay-sensitive flow, and the LCG is a Type II LCG; when the packet delay budget is greater than or equal to the third threshold, the data flow type corresponding to the LCG is a non-delay-sensitive flow, and the LCG is a Type I LCG. The QoS identifier may also include a resource type. When the resource type is a delay-critical guaranteed bit rate, the data flow type corresponding to the LCG is a delay-sensitive flow, and the LCG is a Type II LCG; when the resource type is a guaranteed bit rate or a non-guaranteed bit rate, the data flow type corresponding to the LCG is a non-delay-sensitive flow, and the LCG is a Type I LCG.

[0036] Therefore, the data flow type corresponding to LCG can be determined based on the packet delay budget or resource type in the service quality identifier corresponding to LCG, which makes it easier for terminal devices to determine whether the data flow type corresponding to LCG is a delay-sensitive flow or a non-delay-sensitive flow, and thus facilitates triggering the DSR corresponding to LCG.

[0037] In one possible implementation of the first aspect, the latency-sensitive stream includes real-time communication data streams, such as voice communication data streams, video communication data streams, or audio data streams; the latency-sensitive stream also includes interactive service data streams or high-priority data streams, such as game data streams, virtual reality data streams, or extended reality data streams.

[0038] Therefore, delay-sensitive flows are data flows with high real-time requirements or high data transmission reliability. Consequently, when configuring the triggering conditions of DSRs corresponding to delay-sensitive flows, network devices take into account the real-time nature of delay-sensitive flows to facilitate the timely transmission of DSRs.

[0039] In one possible implementation of the first aspect, the terminal device may receive configuration information configuring the first trigger condition and the second trigger condition; the terminal device may also receive configuration information configuring the first trigger condition, the second trigger condition and the third trigger condition.

[0040] Therefore, the terminal device can receive configuration information to determine the first trigger condition and the second trigger condition, or determine the first trigger condition, the second trigger condition and the third trigger condition, so that the network device can be configured with different trigger conditions when it is in different states and when the LCG corresponds to different data streams, thereby flexibly controlling the transmission of DSR and reducing signaling overhead.

[0041] Secondly, a communication method is provided, applied to a network device. The method includes: when the network device is in a congested state, sending notification information to a terminal device to indicate that the network device is in a congested state, so that the terminal device suppresses the transmission of DSR of a first type LCG corresponding to a non-delay-sensitive flow, wherein the data flow type of the first type LCG corresponding to the non-delay-sensitive flow is a non-delay-sensitive flow; wherein the data flow types corresponding to different LCGs include delay-sensitive flows and non-delay-sensitive flows.

[0042] In one possible implementation of the second aspect, before sending notification information to the terminal device, the method further includes: the network device receiving a DSR corresponding to an LCG sent by the terminal device when a first triggering condition is met; after sending notification information to the terminal device, the network device receiving a DSR of a first type of LCG corresponding to a non-delay-sensitive flow sent by the terminal device when a second triggering condition is met, wherein the frequency of sending the DSR of the first type of LCG corresponding to the non-delay-sensitive flow based on the first triggering condition is a first sending frequency, the frequency of sending the DSR of the first type of LCG corresponding to the non-delay-sensitive flow based on the second triggering condition is a second sending frequency, and the second sending frequency is less than the first sending frequency.

[0043] In one possible implementation of the second aspect, after sending notification information to the terminal device, the method further includes: receiving a DSR of a second type of LCG corresponding to a delay-sensitive stream from the terminal device; the data stream type of the second type of LCG corresponding to the delay-sensitive stream includes a delay-sensitive stream, and the DSR of the second type of LCG corresponding to the delay-sensitive stream is sent by the terminal device when a first triggering condition is met; or, the DSR of the second type of LCG corresponding to the delay-sensitive stream is sent by the terminal device when a third triggering condition is met, and the frequency of sending the DSR of the second type of LCG corresponding to the delay-sensitive stream based on the third triggering condition is a third sending frequency, and the second sending frequency is less than the third sending frequency.

[0044] In one possible implementation of the second aspect, after sending notification information to the terminal device, the method further includes: receiving a DSR of a first type LCG corresponding to a non-delay-sensitive stream from the terminal device, wherein the DSR is sent by the terminal device when the increase in the buffer data volume of the first type LCG corresponding to the non-delay-sensitive stream is greater than or equal to a first threshold, and / or the buffer data volume is greater than or equal to a second threshold.

[0045] In one possible implementation of the second aspect, the method further includes: sending configuration information to a terminal device; the configuration information is used to configure a first triggering condition and a second triggering condition, or the configuration information is used to configure a first triggering condition, a second triggering condition, and a third triggering condition.

[0046] In one possible implementation of the second aspect, if the increase in the buffer data volume of the first type LCG corresponding to the non-delay-sensitive flow is greater than or equal to a first threshold, and / or the buffer data volume is greater than or equal to a second threshold, after sending the DSR to the network device, the execution continues to send the DSR of the first type LCG corresponding to the non-delay-sensitive flow to the network device when the second triggering condition is met.

[0047] In one possible implementation of the second aspect, if the increase in the buffer data volume of the first type LCG corresponding to the non-delay-sensitive stream is greater than or equal to a first threshold, and / or the buffer data volume is greater than or equal to a second threshold, after receiving the DSR from the terminal device, the DSR from the first type LCG corresponding to the non-delay-sensitive stream sent by the terminal device under the second triggering condition is received.

[0048] Thirdly, a communication device is provided for use in a terminal device, the device comprising: a module for performing the method of any of the above aspects and any possible implementation thereof.

[0049] Fourthly, a communication system is provided, comprising: a network device and a terminal device, wherein the terminal device is configured to execute the methods of the first aspect and any possible implementation thereof, and the network device is configured to execute the methods of the second aspect and any possible implementation thereof.

[0050] Fifthly, a communication device is provided, comprising: at least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement any of the above aspects and any possible implementation of the above aspects through logic circuits or execution code instructions.

[0051] Optionally, the communication device further includes a memory for storing program instructions. The processor is coupled to the memory via an interface.

[0052] In a sixth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions configured to perform a method of any of the foregoing aspects and any possible implementation thereof.

[0053] In a seventh aspect, a chip is provided, comprising: an interface circuit and a logic circuit, wherein the interface circuit is used to receive signals from other chips outside the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other chips outside the chip, and the logic circuit is used to implement any of the above aspects and any possible implementation of the above aspects.

[0054] Eighthly, a computer program product is provided, comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform any of the foregoing aspects and any possible implementation thereof. Attached Figure Description

[0055] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0056] Figure 2 A signaling interaction diagram of a communication method provided in an embodiment of this application;

[0057] Figure 3 An interactive schematic diagram of a communication method provided in an embodiment of this application;

[0058] Figure 4 A comparative diagram illustrating the reporting cycle of a DSR provided in this application embodiment;

[0059] Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0060] Figure 6 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0061] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. "Multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items."

[0062] In embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0063] In the embodiments of this application, "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0064] In the embodiments of this application, it should be noted that, unless otherwise explicitly specified and limited, the terms "set", "connected", and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection. Those skilled in the art can understand the specific meaning of the above terms in the embodiments of this application based on the specific circumstances.

[0065] In the uplink scheduling request mechanism, the base station supports configuring different numbers of reporting thresholds for different logical channel groups (LCGs), thereby finely controlling the service triggering scheduling request conditions of terminal devices. Terminal devices can trigger DSRs based on the reporting thresholds configured by the base station and report them to the base station. The base station can understand the buffer status and data latency of the terminal devices based on the information in the DSRs, thus enabling more rational resource scheduling and preventing data from being discarded due to prolonged waiting for resource scheduling, thereby improving the system's transmission efficiency and reliability.

[0066] However, base stations have limited allocated resources, which may lead to insufficient resource scheduling. In this situation, even if the base station receives DSRs sent by the terminal device, it cannot allocate resources to the terminal device. If the terminal device continues to send DSRs to the base station, it will consume signaling resources, resulting in unnecessary signaling overhead and increased power consumption of the terminal device.

[0067] Based on this, this application provides a communication method that, when network devices are in a congested state due to insufficient resource scheduling, allows terminal devices to suppress DSR triggering, reduce the frequency and number of DSR reports, thereby reducing the signaling overhead and power consumption of the terminal devices.

[0068] For example, in satellite communication scenarios, such as low Earth orbit satellite networks, network latency is high and resources are limited, making it crucial to reduce uplink signaling overhead. The communication method provided in this application can reduce the communication burden between satellites and improve data transmission efficiency.

[0069] For example, in an IoT environment, multiple devices need to frequently exchange data. The communication method provided in this application can reduce the frequency and content of data reported by devices, reduce communication overhead, and ensure the effectiveness and timeliness of data transmission.

[0070] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. It is understood that the illustrative flowcharts provided in this application mainly use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of the interaction to illustrate the method, but this application does not limit the execution subjects of the interaction. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of the method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0071] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0072] The technical solutions provided in this application can be applied to various communication systems. These communication systems may include, but are not limited to, the following systems: Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), non-terrestrial network (NTN), 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems may include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not impose any limitations on this.

[0073] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 1 As shown, the communication system provided in this application embodiment may include a network device 10 and a terminal device 20. The network device 10 and the terminal device 20 may communicate via a physical downlink control channel (PDCCH) or a physical uplink shared channel (PUSCH).

[0074] The aforementioned network equipment can be devices that make decisions and process data for terminal devices. For example, network equipment 10 can perform resource scheduling, such as allocating resources to terminal device 20 to enable terminal device 20 to transmit data. The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted devices. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). Multiple access network equipment in a communication system can be base stations of the same type or different types. Base stations can communicate with terminal devices or through relay stations. Terminal devices can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, access network equipment is referred to as network equipment.

[0075] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0076] The terminal device 20 in this embodiment can suppress the number of delay status reports triggered by non-delay-sensitive flows or non-urgent flows based on the indication information sent by the network device 10. The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and indication information. The wireless terminal device can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, aircraft (such as drones, helicopters, and airplanes), hot air balloons, ships, robots, robotic arms, or smart home devices. The embodiments in this application do not limit the form of the terminal device.

[0077] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0078] Access network equipment and / or terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and these examples will not be listed here.

[0079] In practical applications, multiple network devices can collaborate to assist terminal devices in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0080] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0081] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanation in the standard protocol.

[0082] 1. Buffer data size threshold

[0083] The buffer data volume threshold, also known as the buffer size threshold or simply the buffer threshold, is a trigger threshold for the DSR (Data Scheduler) configured on network devices. When the amount of data transmitted in the terminal device's buffer is greater than or equal to the buffer data volume threshold, the terminal device triggers the DSR, reporting its data status to the network device, thereby facilitating resource scheduling and allocation by the network device.

[0084] 2. Remaining time threshold

[0085] The remaining time threshold, also known as the data validity remaining time threshold or remaining time threshold, is another trigger threshold for the DSR configured on network devices. When the validity remaining time of the data in the terminal device's buffer is less than or equal to the remaining time threshold, the terminal device triggers the DSR to report its data status to the network device. This allows the network device to more accurately manage data transmission, such as the data transmission of latency-sensitive streaming services.

[0086] 3. Delay-sensitive traffic

[0087] Delay-sensitive flows are traffic with high real-time requirements for data transmission. Excessive delay (the time difference between sending and receiving) or delay jitter (the magnitude of delay variation) can significantly impact service quality. Delay-sensitive flows typically have high priority, ensuring they occupy network resources first and complete data transmission in a short time, thus requiring high latency.

[0088] Latency-sensitive streams can be real-time communication data streams, such as voice communication data streams, video communication data streams, or audio data streams. Latency-sensitive stream services can also be interactive service data streams, such as game data streams, virtual reality (VR) data streams, extended reality (XR) data streams, and remote control data streams. Latency-sensitive streams can also be other data streams, such as high-priority data streams. This application does not limit the types of latency-sensitive streams in its embodiments.

[0089] 4. Non-delay sensitive traffic

[0090] Non-delay-sensitive flows are those with lower real-time requirements for data transmission, allowing for some delay or latency jitter, and focusing more on the integrity and reliability of data transmission. Non-delay-sensitive flows typically have lower priority, a higher tolerance for data latency, and do not require real-time transmission.

[0091] Non-latency-sensitive streams can be file transfer data streams, such as file upload or download data streams, cloud storage service data streams, etc. Non-latency-sensitive services can also be non-real-time streaming media data streams, such as video caching data streams, audio download data streams, etc. Non-latency-sensitive data stream services can also be other data streams; this application embodiment does not limit the types of non-latency-sensitive streams.

[0092] Below, embodiments of this application will be used to illustrate the concept of having Figure 1 Taking the network device 10 and terminal device 20 of the illustrated architecture as examples, and in conjunction with the accompanying drawings and application scenarios, the communication method provided in this application embodiment will be described in detail. This method is executed by the network device and the terminal device. The network device can be... Figure 1 The network device 10 or the device within the network device 10. The terminal device may be... Figure 1 The method is described using terminal device 20 or a device within terminal device 20. For simplicity, the method will be explained using the example of it being performed by a network device and a terminal device.

[0093] Please see Figure 2 , Figure 2 This is a signaling interaction diagram of a communication method provided in an embodiment of this application. For example... Figure 2 As shown, the communication method provided in this application embodiment may include:

[0094] S101. The network device sends a notification message to the terminal device. Correspondingly, the terminal device receives the notification message from the network device.

[0095] The notification information is used to indicate that the network device is in a congested state. For example, the notification information can be sent via media access control (MAC) signaling, or it can be sent via radio resource control (RRC) signaling. This application embodiment does not limit the specific method of sending the notification information.

[0096] Network devices send this notification when they determine that they are in a congested state. Network devices can determine that they are in a congested state in several ways.

[0097] In one implementation, when the network device's time-domain and frequency-domain resource allocation reaches its resource limit, meaning the network device has no resources left to be scheduled and allocated, the network device is in a congested state.

[0098] In another implementation, network devices can track resource scheduling via MAC addresses. If a network device fails to schedule resources, its state becomes congested.

[0099] In another implementation, network devices can monitor the status of buffers and queues, and monitor the cached data. For example, monitoring the cache status of the radio link control layer (RLC) or packet data convergence protocol layer (PDCP) indicates that the network device cannot transmit data in a timely manner, and the network device is in a congested state.

[0100] In another implementation, the network device can monitor the length of the transmission queue. If the length of the transmission queue of the network device continues to increase, the network device is in a congested state.

[0101] Network devices can also determine their own congestion status through other means, which are not limited in this embodiment.

[0102] S102. When the network equipment is in a congested state, the terminal equipment suppresses the transmission of DSR corresponding to the first type LCG.

[0103] The terminal device is configured with multiple LCGs. In some embodiments, when an application is launched each time, the terminal device can configure one or more LCGs for transmitting the data stream corresponding to the application's service. Different LCGs can correspond to different data stream types. For example, the data stream type can include latency-sensitive streams and non-latency-sensitive streams. The LCGs configured on the terminal device can include a first type of LCG and a second type of LCG. The data stream type corresponding to the first type of LCG is a non-latency-sensitive stream. The data stream type corresponding to the second type of LCG is a latency-sensitive stream.

[0104] The first type of LCG may include one or more LCGs, and the second type of LCG may also include one or more LCGs. This application embodiment does not limit the number of the first type of LCG and the second type of LCG.

[0105] In summary, upon receiving a notification, the terminal device can determine that the network device is in a congested state. When the network device is congested, even if the terminal device sends a DSR (Data Source Retrieval), the network device may be unable to allocate resources to respond. In this situation, continuous DSR transmission by the terminal device increases signaling overhead and wastes signaling resources. However, in this application, when the terminal device determines that the network device is congested, since the data stream corresponding to the first type of LCG is a non-delay-sensitive stream with low real-time requirements, it can suppress DSRs corresponding to the first type of LCG. Since the data stream corresponding to the second type of LCG is a delay-sensitive stream with high real-time requirements, ensuring DSRs corresponding to the second type of LCG reduces the frequency and number of DSR transmissions, thereby reducing the signaling resources occupied by DSR transmissions, reducing signaling overhead, and ultimately reducing the power consumption of the terminal device.

[0106] In some embodiments, the terminal device can determine the data stream type corresponding to the LCG based on the quality of service identifier (QI) corresponding to the LCG.

[0107] The quality of service identifier may include packet delay budget, resource type, and other content such as packet error rate (PER). This application embodiment does not limit this.

[0108] In one implementation, the Quality of Service (QoS) identifier includes the packet delay budget (PDB). When the PDB is less than a third threshold, it indicates that the packet delay budget is small, packet transmission is urgent, and timely transmission is required. The data stream type corresponding to the LCG is a delay-sensitive stream, and the LCG is a type II LCG. When the PDB is greater than or equal to the third threshold, it indicates that the packet delay budget is large, packet transmission can have a certain delay, and the real-time requirements for packet transmission are lower. The data stream type corresponding to the LCG is a non-delay-sensitive stream, and the LCG is a type I LCG.

[0109] Among them, the packet delay budget refers to the maximum end-to-end delay time allowed for a data packet to travel from the sender to the receiver.

[0110] The third threshold can be a threshold configured by the core network equipment or a threshold configured by the terminal equipment. In this embodiment, the configuration subject of the third threshold is not limited.

[0111] For example, the third threshold can be 50ms. When the packet delay budget is less than 50ms, the data stream type corresponding to the LCG is a delay-sensitive stream, and the LCG is a second-type LCG. When the packet delay budget is greater than or equal to 50ms, the data stream type corresponding to the LCG is a non-delay-sensitive stream, and the LCG is a first-type LCG.

[0112] In another implementation, the Quality of Service (QoS) identifier includes the resource type. When the resource type is delay critical guaranteed bit rate (GBR), the data stream type corresponding to the LCG is a delay-sensitive stream, and the LCG is a second type of LCG. When the resource type is guaranteed bit rate (GBR) or non-GBR, the data stream type corresponding to the LCG is a non-delay-sensitive stream, and the LCG is a first type of LCG.

[0113] Resource type is used to differentiate the network resource demand patterns of different services, and it determines the resource allocation strategy. Resource types can include GBR, non-GBR, and delay critical GBR.

[0114] GBR services require network equipment to reserve fixed bandwidth resources to ensure a minimum bit rate guarantee. They are suitable for services with stable bandwidth and high real-time requirements. Non-GBR services do not require network equipment to reserve fixed bandwidth resources; network equipment can dynamically allocate resources according to availability. They are suitable for services with some latency or bandwidth fluctuations. Delay-critical GBR requires network equipment to guarantee both bandwidth resources and extremely low latency. It is suitable for services with low latency and high reliability requirements.

[0115] In other embodiments, the network device can determine the data flow type corresponding to the LCG based on the quality of service identifier (QI) corresponding to the LCG, and indicate the data flow type corresponding to the LCG to the terminal device. Alternatively, the network device can predefine the data flow type corresponding to the LCG and indicate it to the terminal device. This application does not limit the method for determining the data flow type corresponding to the LCG.

[0116] In summary, the data flow type corresponding to LCG can be determined based on the packet delay budget or resource type in the service quality identifier corresponding to LCG. The data flow type corresponding to LCG can also be predefined by the network device, which makes it easier for the terminal device to determine whether the data flow type corresponding to LCG is a delay-sensitive flow or a non-delay-sensitive flow, thereby making it easier to trigger the DSR corresponding to LCG.

[0117] The above describes how the terminal device suppresses the DSR corresponding to the first type of LCG when the network is congested. When the network is not congested, the terminal device will still send the DSR corresponding to the LCG, and will do so normally.

[0118] The following section provides a detailed description of how terminal devices send DSRs corresponding to LCGs when the network device is in both a non-congested and congested state.

[0119] In some embodiments, please refer to Figure 3 , Figure 3 This is an interactive schematic diagram of a communication method provided in an embodiment of this application. For example... Figure 3 As shown in (a), before the terminal device receives the notification information, the network device is in a non-congested state. When the first triggering condition is met, the terminal device sends the DSR corresponding to the LCG to the network device. Correspondingly, the network device receives the DSR corresponding to the LCG from the terminal device.

[0120] The first triggering condition is used by the terminal device to trigger the DSR corresponding to each LCG. This first triggering condition is configured when the network device is in a non-congested state. In the non-congested state, the terminal device normally sends the DSR corresponding to each LCG based on the first triggering condition.

[0121] The first triggering condition can be a triggering condition configured by the network device or a triggering condition configured by the core network device. In this embodiment, the configuration subject of the first triggering condition is not limited.

[0122] When the network equipment is in a non-congested state, the terminal equipment does not identify or distinguish the data stream type corresponding to the LCG. The LCG can actually be either a first-type LCG or a second-type LCG. Regardless of whether the data stream type corresponding to the LCG is a delay-sensitive stream or a non-delay-sensitive stream, as long as the first triggering condition is met, the terminal equipment will trigger and send the DSR corresponding to that LCG.

[0123] like Figure 3 As shown in (b), in some embodiments, when the network device is in a congested state, the terminal device sends the DSR corresponding to the first type of LCG to the network device when the second triggering condition is met. Correspondingly, the network device receives the DSR corresponding to the first type of LCG from the terminal device.

[0124] The second triggering condition is used by the terminal device to trigger the DSR corresponding to the first type of LCG. The second triggering condition is a triggering condition configured when the network device is in a congested state.

[0125] The second triggering condition can be a triggering condition configured by the network device or a triggering condition configured by the core network device. In this embodiment, the configuration subject of the second triggering condition is not limited.

[0126] When the network device is in a congested state, the terminal device will consider the data flow type corresponding to the LCG. When the LCG is a type 1 LCG, the data flow type corresponding to the LCG is a non-delay-sensitive flow. The terminal device will suppress the transmission of DSR. That is, the terminal device will configure a second trigger condition. When the second trigger condition is met, the terminal device will send the DSR corresponding to the type 1 LCG to the network device.

[0127] In one implementation, when the network device is in a non-congested state, the terminal device sends the DSR corresponding to the first type of LCG at a first sending frequency based on a first triggering condition. When the network device is in a congested state, the terminal device sends the DSR corresponding to the first type of LCG at a second sending frequency based on a second triggering condition, and the second sending frequency is less than the first sending frequency. This reduces the frequency at which the terminal device sends the DSR corresponding to the first type of LCG when the network device is in a congested state, thereby reducing signaling overhead.

[0128] In summary, when network devices are in a congested state, terminal devices will suppress the transmission of DSRs corresponding to the first type of LCG. That is, DSRs corresponding to the first type of LCG will only be transmitted when the second triggering condition is met, thereby reducing the transmission frequency of DSRs corresponding to the first type of LCG. This makes the second transmission frequency less than the first transmission frequency, thereby reducing signaling overhead, reducing the occupation of signaling resources, and avoiding signaling redundancy in transmitting DSRs.

[0129] The above describes the DSR transmission method for each LCG when the network device is in a non-congested state, and the DSR transmission method for the first type of LCG when the network device is in a congested state. Below, the DSR transmission method for the second type of LCG when the network device is in a congested state will be described in detail.

[0130] In some embodiments, when the network device is in a congested state, the terminal device can keep the triggering conditions of the DSR corresponding to the second type of LCG unchanged. For example, as Figure 3 As shown in (b), when the network device is in a congested state, the terminal device sends the DSR corresponding to the second type of LCG when the first triggering condition is met. Correspondingly, the network device receives the DSR corresponding to the second type of LCG from the terminal device, thereby ensuring that the DSR corresponding to the second type of LCG can be reported in a timely manner, avoiding the problem of data accumulation caused by the inability to obtain network resources in a timely manner.

[0131] In other embodiments, the transmission method of the DSR corresponding to the second type of LCG may also differ from that in the non-congestion state. For example, as Figure 3 As shown in (b), when the network device is in a congested state, the DSR corresponding to the second type LCG is sent when the third triggering condition is met. Correspondingly, the network device receives the DSR corresponding to the second type LCG from the terminal device.

[0132] The third triggering condition is different from the first triggering condition. The third triggering condition is used by the terminal device to trigger the DSR corresponding to the second type of LCG. The third triggering condition is a triggering condition configured by the network device. The third triggering condition can also be a triggering condition configured by the core network device. The embodiments of this application do not limit the configuration subject of the third triggering condition.

[0133] In one implementation, when the network device is in a congested state, the terminal device sends the DSR corresponding to the second type of LCG at a third sending frequency based on a third triggering condition, and the third sending frequency is greater than the second sending frequency. Therefore, when the network device is in a congested state, the terminal device sends the DSR corresponding to the second type of LCG more frequently than the terminal device sends the DSR corresponding to the first type of LCG, thereby transmitting data in a timely manner and avoiding data congestion caused by the inability to transmit data corresponding to delay-sensitive flows in a timely manner.

[0134] In some other embodiments, when the network device is in a congested state, the terminal device can also suppress the transmission of DSRs corresponding to the second type of LCG, and the suppression degree is less than that of the transmission of DSRs corresponding to the first type of LCG. That is, the third transmission frequency is less than the first transmission frequency, and the third transmission frequency is greater than the second transmission frequency. When the third triggering condition is met, the terminal device transmits the DSRs corresponding to the second type of LCG, thereby suppressing the transmission frequency of the DSRs corresponding to the second type of LCG and reducing the signaling overhead of the DSRs corresponding to the second type of LCG.

[0135] In summary, when network devices are in a congested state, terminal devices can keep the triggering conditions of the DSR corresponding to the second type of LCG unchanged. That is, when the first triggering condition is met, the terminal device sends the DSR corresponding to the second type of LCG, thereby ensuring that the DSR corresponding to the second type of LCG can be reported in a timely manner and avoiding the inability to obtain network resources in a timely manner.

[0136] When network devices are in a congested state, terminal devices can also reduce the frequency of sending DSRs corresponding to the second type of LCG. That is, when the third triggering condition is met, the terminal device sends the DSR corresponding to the second type of LCG, thereby reducing the signaling overhead of sending the DSR corresponding to the second type of LCG and reducing the waste of signaling resources.

[0137] Furthermore, when the third triggering condition is met, the frequency at which the terminal device sends the DSR corresponding to the second type of LCG is greater than the frequency at which the terminal device sends the DSR corresponding to the second type of LCG when the second triggering condition is met. That is, the third frequency is greater than the second frequency, thereby ensuring that the DSR corresponding to the second type of LCG can be reported in a timely manner and avoiding the inability to obtain network resources in a timely manner.

[0138] The above describes the DSR transmission method corresponding to the second type of LCG when the network device is in a congested state. Below, the three triggering conditions mentioned above will be described in detail.

[0139] In some embodiments, the triggering conditions include one or more of the following triggering parameters: a buffer data volume threshold, a data remaining duration threshold, or a DSR transmission period. The triggering conditions may include a first triggering condition, a second triggering condition, or a third triggering condition.

[0140] The threshold for buffer data volume and the threshold for remaining data duration can be found in the descriptions in the simple terms above, and will not be repeated here.

[0141] The DSR transmission period refers to the fixed time interval between two consecutive DSR transmissions.

[0142] For example, the DSR transmission period can be 10ms, 50ms, or 100ms. This application does not limit the size of the DSR transmission period in its embodiments.

[0143] In summary, terminal devices can configure the DSR triggering conditions by configuring any one or more of the following: buffer data volume threshold, data remaining duration threshold, or DSR transmission cycle. This will trigger the DSR reporting, enabling network devices to allocate network resources and complete data transmission.

[0144] Based on the above triggering conditions (such as the first triggering condition, the second triggering condition, or the third triggering condition), there are multiple ways for the terminal device to send the DSR corresponding to the LCG. Below, we will describe in detail the method of the terminal device sending the DSR corresponding to the LCG using several specific embodiments as examples.

[0145] like Figure 3 As shown in (a), when the network equipment is in a non-congested state, and the terminal equipment meets the first triggering condition, it sends the DSR corresponding to each LCG. Figure 3 As shown in (b), when the network device is in a congested state, the terminal device sends the DSR corresponding to the first type of LCG if the second triggering condition is met, and sends the DSR corresponding to the second type of LCG if either the first or third triggering condition is met. The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream, and the data stream type corresponding to the second type of LCG is a delay-sensitive stream.

[0146] The second triggering condition can be described from multiple dimensions. In one implementation, the second triggering condition can be the most urgent triggering threshold among multiple triggering thresholds corresponding to the LCG. In another implementation, the second triggering condition can be the triggering period, for example, increasing the triggering period. In yet another implementation, the second triggering condition can be a triggering threshold value, for example, increasing the buffer threshold or decreasing the remaining duration threshold.

[0147] The following section provides a detailed description of the DSR corresponding to the LCG sent by the terminal device, based on the first, second, and third triggering conditions.

[0148] In some embodiments, when the network device is in a non-congested state, each LCG corresponds to its own first triggering condition, which includes multiple sets of triggering thresholds with different levels of urgency. When the network device is in a congested state, the second triggering condition is the set of triggering thresholds with the highest level of urgency among the multiple sets of triggering thresholds.

[0149] When the network device is in a non-congested state, each LCG corresponds to its own first triggering condition. For example, logical channel group 1 is configured with one triggering threshold, and logical channel group 2 is configured with another triggering threshold. The triggering thresholds configured for each logical channel group can be the same or different. This application embodiment does not limit this.

[0150] For example, taking logical channel group 1 as an example, assume that the first triggering condition is configured with three triggering thresholds (T1, T2 and T3) with different urgency levels for logical channel group 1, as shown below:

[0151] LCG ID=01 (Logical Channel Group 1)

[0152] Report Bitmap=00 (Trigger threshold T1)

[0153] T1 Remaining Time = 100ms

[0154] T1 Buffer Size = 100KB

[0155] Report Bitmap=01 (Trigger threshold T2)

[0156] T2 Remaining Time = 50ms

[0157] T2 Buffer Size = 200KB

[0158] Report Bitmap=10 (Trigger threshold T3)

[0159] T3 Remaining Time = 10ms

[0160] T3 Buffer Size = 500KB

[0161] Terminal devices can trigger DSR based on the reporting thresholds configured by network devices.

[0162] If the terminal device meets the reporting threshold T1, that is, if the remaining time for the terminal device to transmit data is 100ms and / or the buffer data size of the terminal device is 100KB, the terminal device triggers DSR and sends it to the network device.

[0163] If the terminal device meets the reporting threshold T2, that is, the remaining time for the terminal device to transmit data is 50ms, and / or the buffer data size of the terminal device is 200KB, the terminal device triggers DSR and sends it to the network device.

[0164] When the terminal device meets the reporting threshold T3, that is, when the remaining time for the terminal device to transmit data is 10ms and / or the buffer data size of the terminal device is 500KB, the terminal device triggers DSR and sends it to the network device.

[0165] Therefore, each time a terminal device meets a reporting threshold, it triggers a DSR and uses signaling to send the DSR to the network device. Assuming that each DSR report by the terminal device consumes 12 bits, and the network device is in a congested state and cannot respond or allocate resources in a timely manner, the terminal device will continuously send DSRs to the network device, triggering three DSRs and consuming 36 bits of signaling resources, thus increasing the consumption of signaling resources.

[0166] The above describes the specific implementation of the terminal device sending the DSR corresponding to the LCG when the network device is in a non-congested state and the first triggering condition is met. Below, we will describe in detail the terminal device sending the DSR corresponding to the LCG when the network device is in a congested state and the second triggering condition is met.

[0167] When the network equipment is in a congested state and the LCG is a type 1 LCG, the terminal device can trigger the DSR corresponding to the type 1 LCG when the second triggering condition is met.

[0168] In some embodiments, the trigger threshold includes a buffer data volume threshold and a remaining time threshold, and the second trigger condition is the set of trigger thresholds with the highest urgency among multiple sets of trigger thresholds, that is, the set of trigger thresholds with the largest buffer data volume threshold and the smallest remaining time threshold.

[0169] For example, among the three sets of trigger thresholds T1, T2, and T3 mentioned above, the set of trigger thresholds with the largest buffer data volume threshold and the smallest remaining duration threshold is T3. Therefore, the terminal device can configure the second trigger condition as T3, as shown below:

[0170] LCG ID=01 (Logical Channel Group 1)

[0171] Report Bitmap=10 (Report Threshold T3)

[0172] T3 Remaining Time = 10ms

[0173] T3 Buffer Size = 500KB

[0174] When the terminal device meets trigger condition T3, that is, when the remaining time for data transmission on the terminal device is 10ms and / or the data size in the terminal device's buffer is 500KB, the terminal device triggers a DSR and sends it to the network device. In other words, the terminal device will only report a DSR when the remaining time for data transmission is the shortest, or when the amount of data buffered on the terminal device is the largest.

[0175] When the second triggering condition is met, the terminal device only needs to report DSR once, consuming 12 bits of signaling resources. Compared with reporting DSR three times when the first triggering condition is met, the signaling resource consumption is reduced from 36 bits to 12 bits, which reduces the consumption of signaling resources, reduces resource occupation, and reduces the power consumption of the terminal device.

[0176] In summary, considering both scenarios, if the network is not congested, or if the network is congested and the data flow type corresponding to the LCG is a latency-sensitive flow, the terminal device can trigger the reporting of the DSR corresponding to the LCG when the first triggering condition is met. If the network is congested and the data flow type corresponding to the LCG is a non-latency-sensitive flow, the terminal device can trigger the reporting of the DSR corresponding to the LCG when the second triggering condition is met.

[0177] For example, as shown in Table 1, when the network device is in a non-congested state, the terminal device keeps the DSR triggering conditions unchanged, that is, the first triggering conditions of the DSR are T1, T2, and T3; when the network device is in a congested state, the terminal device will determine whether to reduce the number of DSR triggering conditions according to the data flow type corresponding to the LCG. When the data flow type corresponding to the LCG is a delay-sensitive flow, in order to ensure the timeliness of data transmission of the terminal device, the DSR triggering conditions are kept unchanged, that is, the first triggering conditions of the DSR are T1, T2, and T3; when the data flow type corresponding to the LCG is a non-delay-sensitive flow, in order to reduce unnecessary signaling overhead, the terminal device reduces the number of DSR triggering conditions and selects the triggering threshold with the highest urgency among multiple sets of triggering thresholds, that is, the second triggering condition of the DSR is T3.

[0178] Table 1

[0179]

[0180] In summary, terminal devices can dynamically adjust the number of DSR trigger conditions when network devices are congested. When the LCG has a low priority or the data flow type corresponding to the LCG is a non-delay-sensitive flow, the terminal device can reduce the number of DSR trigger conditions. That is, when the second trigger condition is met, the DSR corresponding to the first type of LCG is sent, thereby reducing the number of DSR reports, reducing control signaling overhead, and avoiding unnecessary resource waste. Furthermore, when the LCG has a high priority or the data flow type corresponding to the LCG is a delay-sensitive flow, the number of DSR trigger conditions remains unchanged. That is, when the first trigger condition is met, the DSR corresponding to the LCG is sent, thereby ensuring that the terminal device's data can be scheduled and processed in a timely manner.

[0181] The above describes the triggering conditions as the number of triggering thresholds. Below, we will describe them in detail from the perspective of triggering conditions as triggering threshold values ​​(buffer data volume threshold and / or remaining duration threshold).

[0182] In some embodiments, LCG corresponds to a unified third triggering condition; the terminal device may send the DSR corresponding to the second type of LCG when the network device is in a congested state and the third triggering condition is met; and send the DSR corresponding to the first type of LCG when the second triggering condition is met.

[0183] In other embodiments, each LCG corresponds to its own first triggering condition; when the network device is in a congested state, the DSR corresponding to the second type of LCG is sent when the first triggering condition is met; when the second triggering condition is met, the DSR corresponding to the first type of LCG is sent.

[0184] Below, we will describe in detail several possible implementation methods of the embodiments of this application, taking the above two embodiments as examples and using three implementation methods as examples.

[0185] In one implementation, the third triggering condition includes a preset first buffer data volume threshold, and the second triggering condition includes a preset second buffer data volume threshold, wherein the second buffer data volume threshold is greater than the first buffer data volume threshold.

[0186] When the network device is in a congested state and the data flow type corresponding to the LCG is a non-latency-sensitive flow, the buffer data volume threshold is the second buffer data volume threshold; when the network device is in a congested state and the data flow type corresponding to the LCG is a latency-sensitive flow, the buffer data volume threshold is the first buffer data volume threshold or the first triggering condition is maintained.

[0187] As shown in Table 2, when the network device is in a non-congested state, the terminal device reports the DSR corresponding to the LCG if the first triggering condition is met. When the network device is in a congested state, the buffer data size threshold of the DSR varies depending on the data flow type corresponding to the LCG. When the data flow type corresponding to the LCG is a delay-sensitive flow, in order to ensure the timeliness of data transmission by the terminal device, the first triggering condition of the DSR remains unchanged, or a smaller buffer data size threshold is configured, i.e., the first buffer data size threshold. When the data flow type corresponding to the LCG is a non-delay-sensitive flow, in order to reduce unnecessary signaling overhead, the buffer data size threshold of the DSR is increased, and a larger buffer data size threshold is configured for the terminal device, i.e., the second buffer data size threshold.

[0188] Table 2

[0189]

[0190] For example, when the network device is in a non-congested state, or when the network is in a congested state and the data flow type corresponding to the LCG is a delay-sensitive flow, the terminal device can trigger DSR and report it if the first triggering condition is met.

[0191] For example, as shown below, the terminal device can trigger DSR based on reporting thresholds T1, T2, and T3.

[0192] Report Bitmap=00 (Report Threshold T1)

[0193] T1 Remaining Time = 100ms

[0194] T1 Buffer Size = 100KB

[0195] Report Bitmap=01 (Report Threshold T2)

[0196] T2 Remaining Time = 50ms

[0197] T2 Buffer Size = 200KB

[0198] Report Bitmap=10 (Report Threshold T3)

[0199] T3 Remaining Time = 10ms

[0200] T3 Buffer Size = 500KB

[0201] When the network is congested and the data flow type corresponding to the LCG is a non-delay-sensitive flow, the second triggering condition is the second buffer data size threshold. The terminal device can trigger DSR and report the data when the second triggering condition is met. For example, if the second buffer data size threshold is 2000KB, the terminal device will trigger DSR and report the data when the buffer data size reaches 2000KB.

[0202] For example, as shown below, the terminal device can trigger DSR based on a buffer data size threshold of 2000KB.

[0203] T Buffer Size = 2000KB

[0204] For example, suppose the first buffer data size threshold configured for the network device is 1000KB.

[0205] When the network equipment is in a non-congested state, the terminal equipment can trigger DSR according to the first triggering condition, such as the T1, T2 and T3 thresholds mentioned above.

[0206] When the network is in a congested state and the data stream type corresponding to LCG is a delay-sensitive stream, the terminal device can use the first buffer data volume threshold. When the buffer data of the terminal device reaches 1000KB, the terminal device will trigger DSR and report it.

[0207] For example, as shown below, the terminal device can trigger DSR based on a buffer data size threshold of 1000KB.

[0208] T Buffer Size = 1000KB

[0209] When the network is in a congested state and the data stream type corresponding to the LCG is a non-delay-sensitive stream, the terminal device can use a second buffer data size threshold, for example, a second buffer data size threshold of 2000KB. When the buffer data of the terminal device reaches 2000KB, the terminal device will trigger DSR and report it.

[0210] For example, as shown below, the terminal device can trigger DSR based on a buffer data size threshold of 2000KB.

[0211] T Buffer Size = 2000KB

[0212] When the network is congested and the data flow type corresponding to the LCG is a non-latency-sensitive flow, the network device can also dynamically adjust the buffer data volume threshold. When the buffer data volume is large, the buffer data volume threshold is decreased; when the buffer data volume is small, the buffer data volume threshold is increased.

[0213] In summary, when the network equipment is in a non-congested state, the terminal device sends the DSR corresponding to the LCG when the first triggering condition is met. When the network equipment is in a congested state, the terminal device sends the DSR corresponding to the second type of LCG when the third triggering condition (the first buffer data volume threshold) is met, or sends the DSR corresponding to the second type of LCG when the first triggering condition is met. When the network equipment is in a congested state, the terminal device sends the DSR corresponding to the first type of LCG when the second triggering condition (the second buffer data volume threshold) is met. This reduces the frequency at which the terminal device sends the DSR corresponding to the first type of LCG compared to when the network equipment is in a non-congested state, thus reducing the signaling overhead of the DSR corresponding to the first type of LCG.

[0214] In another implementation, the third triggering condition includes a preset first valid remaining duration, and the second triggering condition includes a preset second valid remaining duration, where the second valid remaining duration is less than the first valid remaining duration. When the network device is in a congested state and the data flow type corresponding to the LCG is a non-latency-sensitive flow, the remaining duration threshold is the second valid remaining duration. When the network device is in a congested state and the data flow type corresponding to the LCG is a latency-sensitive flow, the remaining duration threshold is the first valid remaining duration or the first triggering condition is maintained.

[0215] As shown in Table 3, when the network device is in a non-congested state, the terminal device reports the DSR corresponding to the LCG if the first triggering condition is met. When the network device is in a congested state, the buffer data volume threshold of the DSR varies depending on the data stream type corresponding to the LCG. When the data stream type corresponding to the LCG is a delay-sensitive stream, the network device maintains the first triggering condition of the DSR unchanged or configures a first effective remaining duration to ensure the timeliness of data transmission from the terminal device. When the data stream type corresponding to the LCG is a non-delay-sensitive stream, the remaining duration threshold of the DSR is reduced to decrease unnecessary signaling overhead, i.e., a second effective remaining duration is configured for the terminal device. The network device can also dynamically adjust the remaining duration threshold of the DSR according to the data volume in the buffer, which is not limited in this embodiment.

[0216] Table 3

[0217]

[0218] For example, when the network device is in a non-congested state, or when the network is in a congested state and the data flow type corresponding to the LCG is a delay-sensitive flow, the terminal device can trigger DSR and report it if the first triggering condition is met.

[0219] For example, the terminal device can trigger DSR based on the aforementioned reporting thresholds T1, T2, and T3.

[0220] When the network is congested and the data stream type corresponding to the LCG is a non-delay-sensitive stream, the terminal device can trigger DSR and report it if the second triggering condition (second valid remaining time) is met. For example, if the second valid remaining time is 10ms, the terminal device will trigger DSR and report it when the remaining data transmission time is 10ms.

[0221] For example, as shown below, the terminal device can trigger DSR based on the valid remaining duration of the buffer data being 10ms.

[0222] T Remaining Time = 10ms

[0223] For example, suppose the network device is configured with a first valid remaining time of 50ms.

[0224] When the network equipment is in a non-congested state, the terminal equipment can trigger DSR according to the first triggering condition, such as the T1, T2 and T3 thresholds mentioned above.

[0225] When the network is congested and the data stream type corresponding to the LCG is a delay-sensitive flow, the terminal device can trigger DSR and report it if the third triggering condition (first valid remaining time) is met. For example, when the terminal device has 50ms of data transmission remaining time, the terminal device will trigger DSR and report it.

[0226] For example, as shown below, the terminal device can trigger DSR based on the valid remaining duration of the buffer data being 50ms.

[0227] T Remaining Time = 50ms

[0228] When the network is congested and the data flow type corresponding to the LCG is a non-delay-sensitive flow, the terminal device can trigger DSR and report it if the second triggering condition (second valid remaining time) is met. For example, if the remaining time threshold is 10ms, the terminal device will trigger DSR and report it when the remaining data transmission time is 10ms.

[0229] For example, as shown below, the terminal device can trigger DSR based on the valid remaining duration of the buffer data being 10ms.

[0230] T Remaining Time = 10ms

[0231] In summary, when the network equipment is in a non-congested state, the terminal device sends the DSR corresponding to the LCG when the first triggering condition is met. When the network equipment is in a congested state, the terminal device sends the DSR corresponding to the second type of LCG when the third triggering condition (first valid remaining time), or sends the DSR corresponding to the second type of LCG when the first triggering condition is met. When the network equipment is in a congested state, the terminal device sends the DSR corresponding to the first type of LCG when the second triggering condition (second valid remaining time) is met. This reduces the frequency at which the terminal device sends the DSR corresponding to the first type of LCG compared to when the network equipment is in a non-congested state, thus reducing the signaling overhead of the DSR corresponding to the first type of LCG.

[0232] In another implementation, when the network device is in a congested state and the data flow type corresponding to the LCG is a non-latency sensitive flow, the terminal device can trigger DSR based on the buffer data volume threshold and remaining duration threshold configured by the network device and report it.

[0233] As shown in Table 4, when the network device is in a non-congested state, the terminal device reports the DSR corresponding to the LCG when the first triggering condition is met. When the network device is in a congested state, the buffer data volume threshold of the DSR varies depending on the data flow type corresponding to the LCG. When the network device is in a congested state, the network device configures the buffer data volume threshold and the remaining duration threshold of the DSR according to the data flow type corresponding to the LCG. When the data flow type corresponding to the LCG is a delay-sensitive flow, in order to ensure the timeliness of data transmission by the terminal device, the first triggering condition of the DSR remains unchanged, or the first buffer data volume threshold and the first effective remaining duration are configured. When the data flow type corresponding to the LCG is a non-delay-sensitive flow, in order to reduce unnecessary signaling overhead, the network device increases the buffer data volume threshold and decreases the remaining duration threshold, that is, configures the second buffer data volume threshold and the second effective remaining duration for the terminal device. The network device can also dynamically adjust the buffer data volume threshold and the remaining duration threshold of the DSR according to the data volume in the buffer, which is not limited in this embodiment.

[0234] Table 4

[0235]

[0236] For example, when the network device is in a non-congested state, or when the network is in a congested state and the data stream type corresponding to the LCG is a delay-sensitive stream, the terminal device sends the DSR corresponding to the LCG when the first triggering condition is met.

[0237] For example, the terminal device can trigger DSR based on the above reporting thresholds T1, T2 and T3, and then report it.

[0238] When the network is congested and the data stream type corresponding to the LCG is a non-delay-sensitive stream, the terminal device triggers DSR and reports it if the second triggering conditions (second valid remaining time and second buffer data size threshold) are met. For example, if the second valid remaining time is 10ms and the second buffer data size threshold is 2000KB, the terminal device will trigger DSR and report it when the remaining data transmission time is 10ms and / or the buffer data size reaches 2000KB.

[0239] For example, as shown below, the terminal device can trigger DSR based on a remaining duration threshold of 10ms and / or a buffer data volume of 2000KB.

[0240] T Remaining Time = 10ms

[0241] T Buffer Size = 2000KB

[0242] For example, suppose the network device is configured with a first valid remaining time of 50ms and a first buffer data size threshold of 1000KB.

[0243] When the network equipment is in a non-congested state, the terminal equipment can trigger DSR according to the first triggering condition, such as the T1, T2 and T3 thresholds mentioned above.

[0244] When the network is congested and the data stream type corresponding to the LCG is a delay-sensitive stream, the terminal device sends the DSR corresponding to the LCG if the third triggering condition (first effective remaining time and first buffer data volume threshold) is met. When the terminal device has 50ms of remaining data transmission time and / or the buffer data volume reaches 1000KB, the terminal device will trigger the DSR and report it.

[0245] For example, as shown below, the terminal device can trigger DSR based on a remaining duration threshold of 50ms and / or a buffer data volume of 1000KB.

[0246] T Remaining Time = 50ms

[0247] T Buffer Size = 1000KB

[0248] When the network is congested and the data stream type corresponding to the LCG is a non-delay-sensitive stream, the terminal device sends the DSR corresponding to the LCG if the second triggering conditions (second effective remaining time and second buffer data size threshold) are met. For example, if the remaining time threshold is 10ms and the buffer data size threshold is 2000KB, the terminal device will trigger the DSR and report it when the remaining data transmission time of the terminal device is 10ms and / or the data size of the buffer reaches 2000KB.

[0249] For example, as shown below, the terminal device can trigger DSR based on a remaining duration threshold of 10ms and / or a buffer data volume of 2000KB.

[0250] T Remaining Time = 10ms

[0251] T Buffer Size = 2000KB

[0252] In summary, under non-congested conditions, network devices can configure a first trigger condition to trigger the DSR corresponding to the LCG. Under congested conditions, when the LCG corresponds to the second LCG, network devices can configure a third trigger condition, which includes a first buffer data volume threshold and / or a first effective remaining duration. When the LCG corresponds to the first LCG, network devices can configure a second trigger condition, which includes a second buffer data volume threshold and / or a second effective remaining duration. The second buffer data volume threshold is greater than the first buffer data volume threshold, and the second effective remaining duration is less than the first effective remaining duration. This reduces the frequency of DSR transmission by the network device under non-congested conditions when the LCG corresponds to the first LCG, thereby reducing signaling overhead, resource consumption, and power consumption of terminal devices.

[0253] In addition, when the network device is in a congested state, when the LCG corresponds to the second LCG, a first trigger condition can be configured. Each LCG corresponds to its own first trigger condition, thereby ensuring the timeliness of the transmission of delay-sensitive flow data, ensuring that the trigger conditions for the service requirements corresponding to different LCGs are different, and improving data transmission efficiency.

[0254] Furthermore, when the network device is in a congested state and the LCG corresponds to the first LCG, the terminal device can also dynamically configure the second buffer data volume threshold and / or the second effective remaining time according to the size of the buffer data volume. When the buffer data volume is large, the second buffer data volume threshold can be reduced or the second effective remaining time can be increased. When the buffer data volume is small, the second buffer data volume threshold can be increased or the second effective remaining time can be decreased, thereby monitoring and controlling the transmission of DSR in real time and improving the data transmission efficiency.

[0255] The above description focuses on the triggering conditions as triggering thresholds (buffer data volume threshold and / or remaining duration threshold). The following description focuses on the triggering conditions as triggering cycles.

[0256] In some embodiments, the first triggering condition includes a first DSR transmission period, the second triggering condition includes a second DSR transmission period, and the second DSR transmission period is greater than the first DSR transmission period.

[0257] The first or second triggering condition may include a triggering threshold (a buffer data volume threshold and / or a remaining duration threshold), or it may not include a triggering threshold. This application embodiment does not limit the first or second triggering condition.

[0258] As shown in Table 5, when the network device is in a non-congested state, the terminal device maintains the DSR reporting period unchanged and can periodically report DSR according to the reporting period configured by the network device, i.e., the first DSR sending period. When the network device is in a congested state, the network device configures the DSR reporting period according to the data flow type corresponding to the LCG. When the data flow type corresponding to the LCG is a delay-sensitive flow, in order to ensure the timeliness of data transmission by the terminal device, the DSR reporting period remains unchanged, i.e., the terminal device reports DSR using the first DSR sending period. When the data flow type corresponding to the LCG is a non-delay-sensitive flow, in order to reduce unnecessary signaling overhead, the network device configures the DSR reporting period to be the second DSR sending period, i.e., the terminal device reports DSR using the second DSR sending period. The second DSR sending period is longer than the first DSR sending period, thereby causing the terminal device to suppress the frequency of DSR transmission.

[0259] Table 5

[0260]

[0261] For example, taking a network device configured with two logical channel groups, LCG0 and LCG1, the reporting period for triggering DSR by the terminal device is described in detail. Here, LCG0 corresponds to the second type of LCG, and LCG1 corresponds to the first type of LCG.

[0262] Please see Figure 4 , Figure 4 This is a comparative diagram illustrating the reporting cycle of a DSR as provided in an embodiment of this application. Figure 4 As shown, the DSR reporting cycle of LCG1 differs from that of related technologies and embodiments of this application.

[0263] In related technologies, when network devices are in a congested state, the DSR reporting period of terminal devices in LCG0 or LCG1 is the same, which is 20ms.

[0264] In this embodiment of the application, the DSR reporting period of the terminal device in LCG0 is 20ms and the DSR reporting period in LCG1 is 80ms.

[0265] In summary, compared with related technologies, the terminal device in this application embodiment increases the reporting period of DSR for non-delay-sensitive flows and reduces the reporting frequency of DSR when the network device is in a congested state, thereby reducing terminal signaling overhead and avoiding unnecessary resource waste. Furthermore, when the network device is in a congested state, the terminal device maintains the reporting period of DSR for delay-sensitive flows unchanged, thereby ensuring that delay-sensitive flows or high-priority data can be transmitted in a timely manner, guaranteeing the effectiveness of data transmission.

[0266] In the schemes corresponding to Tables 1-4, the DSR corresponding to LCG can be triggered based on the triggering period configured in the non-congestion state of the network device. Alternatively, the triggering period configured in the non-congestion state of the network device can be increased, that is, the scheme of increasing the triggering period in Table 5 can be combined with the schemes corresponding to Tables 1-4. In this way, when the network device is in a congestion state, the transmission frequency of the DSR corresponding to LCG can be better suppressed, and the signaling overhead can be reduced.

[0267] Terminal devices can also determine data changes. When network devices are congested and the LCG corresponds to the first LCG, if the terminal device's data changes significantly, even if the terminal device does not meet the DSR triggering conditions, the terminal device will immediately trigger DSR and report its own data status. This allows network devices to promptly detect the terminal device's data status and perform resource scheduling.

[0268] In some embodiments, if the increase in the amount of buffer data corresponding to the first type of LCG is greater than or equal to the first threshold, the terminal device can determine that the data has changed significantly and send DSR.

[0269] The first threshold is a predefined value used to characterize the percentage increase in the amount of data in the buffer. The first threshold can be a threshold configured by the network device or a threshold configured by the terminal device; this application embodiment does not limit the source of the first threshold configuration.

[0270] For example, the first threshold is 50%, the buffer data volume starts at 1000 bytes, and grows to 1600 bytes at a certain moment or within a certain period of time. The growth rate of the buffer data volume is 60%. If it is greater than 50%, the terminal can determine that the data has changed significantly. The terminal device will immediately trigger DSR and report its own data status to the network device.

[0271] In other embodiments, if the amount of data in the buffer is greater than or equal to a second threshold, the terminal device can determine that the data has changed significantly and send a DSR.

[0272] The second threshold can be a predefined value. For example, the second threshold can also be twice the buffer data size threshold used to trigger DSR transmission when the network device is in a congested state. This application embodiment does not limit the size of the second threshold. For example, the second threshold can be twice the second buffer data size threshold in Table 2. When the buffer data size is greater than or equal to twice the second buffer data size threshold, the terminal device transmits the DSR corresponding to the LCG.

[0273] The second threshold can be a threshold configured by the network device or a threshold configured by the terminal device. In this application embodiment, the configuration source of the second threshold is not limited.

[0274] For example, if the buffer data size threshold is 1000 bytes, then the second threshold is 2000 bytes. When the buffer data size is greater than or equal to 2000 bytes, the terminal can determine that the data has changed significantly, and the terminal device will immediately trigger DSR to report its own data status to the network device.

[0275] In summary, when network devices are in a congested state and the LCG corresponds to the first LCG, if the data of the terminal device changes significantly, that is, the increase in the buffer data volume corresponding to the first type of LCG is greater than or equal to the first threshold, or the buffer data volume is greater than or equal to the second threshold, the terminal device will immediately trigger DSR and report its own data status, even if the terminal device does not meet the triggering conditions of DSR. This facilitates the network device to promptly detect the data status of the terminal device and perform resource scheduling.

[0276] When a network device receives a Data Service Request (DSR), if it has available resources, it will send resource configuration information to the terminal device, indicating on which resources the terminal device can send data. If the network device has no available resources, it will not respond or will send an indication that no resources are available.

[0277] After receiving the resource configuration information sent by the network device, the terminal device sends the data cached in the buffer to the network device on the configured resources.

[0278] The above describes the specific implementation method of the terminal device sending the DSR corresponding to the LCG when the first triggering condition, the second triggering condition, or the third triggering condition is met. The configuration of the first triggering condition, the second triggering condition, or the third triggering condition is described in detail below.

[0279] In some embodiments, the triggering conditions described above can be configured using configuration information. The terminal device and the network device send configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information sent by the network device.

[0280] The configuration information is used to configure the first trigger condition and the second trigger condition; or, the configuration information is used to configure the first trigger condition, the second trigger condition, and the third trigger condition.

[0281] The terminal device can receive multiple configuration information messages, each with a different trigger condition. For example, the first configuration information is used to configure a first trigger condition, the second configuration information is used to configure a second trigger condition, and the third configuration information is used to configure a third trigger condition. The terminal device can also receive a single configuration information message, which can simultaneously configure the first and second trigger conditions, or simultaneously configure the first, second, and third trigger conditions. This application embodiment does not limit the number or content of the configuration information messages.

[0282] Network devices can comprehensively consider various factors, such as network load, quality of service requirements, service latency requirements, and terminal device capabilities, to configure buffer data volume thresholds and / or remaining duration thresholds, thereby controlling the first, second, or third triggering conditions of the DSR corresponding to the LCG.

[0283] Network load factors: When the network load is high, network devices can set a larger buffer data volume threshold and / or a smaller remaining time threshold to avoid frequent DSR reporting by terminal devices and reduce control signaling overhead. When the network load is low or the network is idle, there are more available network resources, so a smaller buffer data volume threshold and / or a larger remaining time threshold can be set to enable terminal devices to report DSR in a timely manner and transmit data in real time.

[0284] Service Quality Requirements Factors: For services with high service quality requirements, such as real-time traffic services (e.g., voice, video), network devices can be configured with a smaller buffer data size threshold and / or a larger remaining duration threshold to ensure timely response and avoid data overflow. For services with low service quality requirements, such as low-priority traffic services, network devices can be configured with a larger buffer data size threshold and / or a smaller remaining duration threshold, thereby reducing reporting frequency.

[0285] Service latency requirements: For services with high latency requirements, such as latency-sensitive streaming services, network devices can be configured with a smaller buffer data size threshold and / or a larger remaining duration threshold to ensure timely data transmission and avoid delays. For services with low latency requirements, network devices can be configured with a larger buffer data size threshold and / or a smaller remaining duration threshold, thereby reducing reporting frequency.

[0286] Terminal device capability factors: For low-power devices or terminal devices with limited resources, network devices can be configured with a larger buffer data volume threshold and / or a smaller remaining duration threshold to reduce the reporting frequency of terminal devices and avoid frequent signaling transmissions from affecting battery and processing capabilities.

[0287] In summary, the terminal device can receive configuration information to determine the first and second trigger conditions, or the first, second, and third trigger conditions, thereby configuring different trigger conditions when the network device is in different states and when the LCG corresponds to different data streams, thus flexibly controlling the transmission of DSR and reducing signaling overhead.

[0288] It should be understood that Figures 1 to 4 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 4 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0289] The above text combined Figures 1 to 4 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figure 5 and Figure 6 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0290] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0291] By way of example, embodiments of this application also provide a communication device.

[0292] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0293] The communication device 500 may include a communication module 520. The communication module 520 can implement corresponding communication functions, which can be internal communication functions of the communication device 500 or communication functions between the communication device 500 and other devices. Optionally, the communication module 520 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 500 also includes a processing module 510. The processing module 510 can implement corresponding processing functions.

[0294] Optionally, the communication device 500 further includes a storage module, which can be used to store instructions and / or data; the processing module 510 can read the instructions and / or data in the storage module so that the communication device 500 can implement the aforementioned method embodiments.

[0295] In one possible design, the communication device 500 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 500 can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0296] In some embodiments, the communication module 520 receives notification information, which is used to indicate that the network device is in a congested state.

[0297] When the network device is in a congested state, the processing module 510 suppresses the transmission of the delay status report (DSR) corresponding to the first type of logical channel group (LCG). The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream. Among them, the data stream types corresponding to different LCGs include delay-sensitive streams and non-delay-sensitive streams.

[0298] In some embodiments, before receiving notification information, the communication module 520 sends the DSR corresponding to the LCG when the first triggering condition is met;

[0299] Suppressing the transmission of Delay Status Reports (DSRs) corresponding to the first logical channel group (LCG), including:

[0300] When the second triggering condition is met, the processing module 510 sends the DSR corresponding to the first type of LCG, and the second sending frequency is less than the first sending frequency. The second sending frequency is the frequency at which the DSR corresponding to the first type of LCG is sent based on the second triggering condition, and the first sending frequency is the frequency at which the DSR corresponding to the first type of LCG is sent based on the first triggering condition.

[0301] In some embodiments, the triggering conditions include one or more of the following triggering parameters: buffer data volume threshold, data remaining duration threshold, or DSR transmission cycle.

[0302] In some embodiments, when the network device is in a congested state, the communication module 520 sends the DSR corresponding to the second type of LCG when a first triggering condition is met. The data stream type corresponding to the second type of LCG includes a delay-sensitive stream; or...

[0303] When the third triggering condition is met, the communication module 520 sends the DSR corresponding to the second type of LCG, and the second sending frequency is less than the third sending frequency. The third sending frequency is the frequency at which the DSR corresponding to the second type of LCG is sent based on the third triggering condition.

[0304] In some embodiments, each LCG corresponds to its own first triggering condition, which includes multiple sets of triggering thresholds with different levels of urgency, and the second triggering condition is the set of triggering thresholds with the highest level of urgency among the multiple sets of triggering thresholds.

[0305] In some embodiments, the trigger threshold includes a buffer data volume threshold and a remaining time threshold, and the second trigger condition is the set of trigger thresholds with the largest buffer data volume threshold and the smallest remaining time threshold among multiple sets of trigger thresholds.

[0306] In some embodiments, the first triggering condition includes a first DSR transmission period, the second triggering condition includes a second DSR transmission period, and the second DSR transmission period is greater than the first DSR transmission period.

[0307] In some embodiments, the third triggering condition includes a preset first buffer data volume threshold, and the second triggering condition includes a preset second buffer data volume threshold, wherein the second buffer data volume threshold is greater than the first buffer data volume threshold; or...

[0308] The third triggering condition includes a preset first valid remaining time, and the second triggering condition includes a preset second valid remaining time, wherein the second valid remaining time is less than the first valid remaining time.

[0309] In some embodiments, each LCG corresponds to its own first triggering condition; when the network device is in a congested state, the communication module 520 sends the DSR corresponding to the second type of LCG when the first triggering condition is met; the second triggering condition includes a preset second buffer data volume threshold; or...

[0310] Each LCG corresponds to its own first triggering condition; when the network device is in a congested state, the communication module 520 sends the DSR corresponding to the second type of LCG when the first triggering condition is met; the second triggering condition includes a preset second valid remaining duration.

[0311] In some embodiments, when the network device is in a congested state, the communication module 520 sends DSR when the increase in the buffer data volume corresponding to the first type of LCG is greater than or equal to a first threshold, and / or when the buffer data volume is greater than or equal to a second threshold.

[0312] In some embodiments, the data stream type corresponding to an LCG is determined based on the quality of service identifier corresponding to the LCG;

[0313] The Quality of Service (QoS) identifier includes a packet delay budget. When the packet delay budget is less than a third threshold, the data flow type corresponding to the LCG is a delay-sensitive flow, and the LCG is a Type II LCG; when the packet delay budget is greater than or equal to the third threshold, the data flow type corresponding to the LCG is a non-delay-sensitive flow, and the LCG is a Type I LCG; or...

[0314] The Quality of Service (QoS) identifier includes the resource type. When the resource type is a delay-critical guaranteed bit rate, the data flow type corresponding to the LCG is a delay-sensitive flow, and the LCG is a second-type LCG. When the resource type is a guaranteed bit rate or a non-guaranteed bit rate, the data flow type corresponding to the LCG is a non-delay-sensitive flow, and the LCG is a first-type LCG.

[0315] In some embodiments, latency-sensitive streams include one or more of real-time communication data streams, interactive service data streams, or high-priority data streams.

[0316] Among them, real-time communication data streams include one or more of voice communication data streams, video communication data streams, or audio data streams, and interactive service data streams include one or more of game data streams, virtual reality data streams, or extended reality data streams.

[0317] In some embodiments, the communication module 520 is used to receive configuration information, which is used to configure a first triggering condition and a second triggering condition; or...

[0318] The configuration information is used to configure the first trigger condition, the second trigger condition, and the third trigger condition.

[0319] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0320] In one possible design, the communication device 500 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 500 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0321] In some embodiments, the communication module 520 is used to send a notification message to the terminal device when the network device is in a congested state; the notification message is used to indicate that the network device is in a congested state so that the terminal device suppresses the transmission of DSR corresponding to the first type of LCG, the data stream type corresponding to the first type of LCG is a non-delay-sensitive stream; wherein, the data stream types corresponding to different LCGs include delay-sensitive streams and non-delay-sensitive streams.

[0322] In some embodiments, before sending notification information to the terminal device, the communication module 520 is used to receive the DSR corresponding to the LCG from the terminal device, wherein the DSR is sent by the terminal device when the first triggering condition is met.

[0323] After sending notification information to the terminal device, the communication module 520 is used to receive the DSR corresponding to the first type of LCG from the terminal device. The DSR corresponding to the first type of LCG is sent by the terminal device when the second trigger condition is met, and the second sending frequency is less than the first sending frequency. The second sending frequency is the frequency of sending the DSR corresponding to the first type of LCG based on the second trigger condition, and the first sending frequency is the frequency of sending the DSR corresponding to the first type of LCG based on the first trigger condition.

[0324] In some embodiments, after sending notification information to the terminal device, the communication module 520 is used to receive the DSR corresponding to the second type of LCG from the terminal device;

[0325] The data stream types corresponding to the second type of LCG include delay-sensitive streams. The DSR corresponding to the second type of LCG is sent by the terminal device when the first trigger condition is met; or, the DSR corresponding to the second type of LCG is sent by the terminal device when the third trigger condition is met, and the second sending frequency is less than the third sending frequency, and the third sending frequency is the frequency of sending the DSR corresponding to the second type of LCG based on the third trigger condition.

[0326] In some embodiments, after sending notification information to the terminal device, the communication module 520 is used to receive a DSR corresponding to the first type of LCG from the terminal device. The DSR is sent by the terminal device when the increase in the buffer data volume corresponding to the first type of LCG is greater than or equal to a first threshold, and / or when the buffer data volume is greater than or equal to a second threshold.

[0327] In some embodiments, the communication module 520 is used to send configuration information to the terminal device, the configuration information being used to configure a first triggering condition and a second triggering condition.

[0328] In some embodiments, when the increase in the amount of buffer data corresponding to the first type of LCG is greater than or equal to a first threshold, and / or the amount of buffer data is greater than or equal to a second threshold, after sending a DSR to the network device, the communication module 520 is used to continue to send the DSR corresponding to the first type of LCG to the network device when the second triggering condition is met.

[0329] In some embodiments, when the increase in the amount of buffer data corresponding to the first type of LCG is greater than or equal to a first threshold, and / or the amount of buffer data is greater than or equal to a second threshold, after receiving the DSR from the terminal device, the communication module 520 is used to receive the DSR corresponding to the first type of LCG from the terminal device, wherein the DSR is sent by the terminal device under the condition of satisfying the second triggering condition.

[0330] By way of example, embodiments of this application also provide a communication device.

[0331] Please see Figure 6 , Figure 6 This is a schematic diagram of another communication device provided in an embodiment of this application.

[0332] like Figure 6 As shown, the communication device 500 can be a chip, chip system, or processor, etc., used in terminal devices or network devices to implement the above methods. This communication device 500 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0333] The communication device 500 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 500 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0334] In an alternative design, the processor 610 may also store instructions and / or data, which can be executed by the processor 610 to cause the communication device 500 to perform the methods described in the above method embodiments.

[0335] In another alternative design, the communication device 500 may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0336] Optionally, the communication device 500 may include one or more memories 630, which may store instructions that can be executed on the processor 610, causing the communication device 500 to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.

[0337] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This 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 method. To avoid repetition, detailed descriptions are not provided here.

[0338] In one implementation, the communication device 500 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0339] In another implementation, the communication device 500 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0340] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0341] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as 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 linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0342] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0343] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0344] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0345] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0346] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0347] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0348] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0349] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

[0350] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0351] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0352] In summary, the above are merely preferred embodiments of the technical solutions of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method includes: Receive notification information, the notification information being used to indicate that the network device is in a congested state; When the network device is in a congested state, upon meeting a second triggering condition, a Delay Status Report (DSR) corresponding to the first type of LCG is sent at a second sending frequency; upon meeting a third triggering condition, a DSR corresponding to the second type of LCG is sent at a third sending frequency. The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream, and the data stream type corresponding to the second type of LCG includes a delay-sensitive stream. The second sending frequency is less than the third sending frequency. The data stream types corresponding to different LCGs include delay-sensitive streams and non-delay-sensitive streams.

2. The method according to claim 1, characterized in that, Prior to receiving the notification information, the method further includes: When the first triggering condition is met, the DSR corresponding to the LCG is sent; the second sending frequency is less than the first sending frequency, and the first sending frequency is the frequency at which the DSR corresponding to the first type of LCG is sent based on the first triggering condition.

3. The method according to claim 2, characterized in that, The triggering conditions include one or more of the following triggering parameters: buffer data volume threshold, data remaining duration threshold, or DSR transmission cycle.

4. The method according to claim 2 or 3, characterized in that, When the network device is in a congested state, the method further includes: When the first triggering condition is met, send the DSR corresponding to the second type of LCG.

5. The method according to claim 2 or 3, characterized in that, Each LCG corresponds to its own first triggering condition. The first triggering condition includes multiple sets of triggering thresholds with different levels of urgency. The second triggering condition is the set of triggering thresholds with the highest level of urgency among the multiple sets of triggering thresholds.

6. The method according to claim 5, characterized in that, The trigger threshold includes a buffer data volume threshold and a remaining time threshold. The second trigger condition is the set of trigger thresholds with the largest buffer data volume threshold and the smallest remaining time threshold among the multiple sets of trigger thresholds.

7. The method according to claim 2 or 3, characterized in that, The first triggering condition includes a first DSR transmission period, and the second triggering condition includes a second DSR transmission period, wherein the second DSR transmission period is greater than the first DSR transmission period.

8. The method according to claim 4, characterized in that, The third triggering condition includes a preset first buffer data volume threshold, and the second triggering condition includes a preset second buffer data volume threshold, wherein the second buffer data volume threshold is greater than the first buffer data volume threshold; or... The third triggering condition includes a preset first valid remaining time, and the second triggering condition includes a preset second valid remaining time, wherein the second valid remaining time is less than the first valid remaining time.

9. The method according to claim 4, characterized in that, Each of the LCGs corresponds to its respective first trigger condition; when the network device is in a congested state, the DSR corresponding to the second type of LCG is sent when the first trigger condition is met; the second trigger condition includes a preset second buffer data volume threshold; or... Each of the LCGs corresponds to its respective first triggering condition; When the network device is in a congested state, the DSR corresponding to the second type of LCG is sent when the first triggering condition is met; the second triggering condition includes a preset second valid remaining duration.

10. The method according to any one of claims 1-3, characterized in that, When the network device is in a congested state, the method further includes: The DSR is sent when the increase in the buffer data volume corresponding to the first type of LCG is greater than or equal to the first threshold, and / or the buffer data volume is greater than or equal to the second threshold.

11. The method according to any one of claims 1-3, characterized in that, The data stream type corresponding to the LCG is determined based on the service quality identifier corresponding to the LCG; The Quality of Service (QoS) identifier includes a packet latency budget. When the packet latency budget is less than a third threshold, the data flow type corresponding to the LCG is the latency-sensitive flow, and the LCG is a second-type LCG. When the packet latency budget is greater than or equal to the third threshold, the data flow type corresponding to the LCG is the non-latency-sensitive flow, and the LCG is a first-type LCG. Or... The Quality of Service (QoS) identifier includes a resource type. When the resource type is a latency-critical guaranteed bit rate, the data stream type corresponding to the LCG is the latency-sensitive stream, and the LCG is a second type of LCG. When the resource type is a guaranteed bit rate or a non-guaranteed bit rate, the data stream type corresponding to the LCG is the non-latency-sensitive stream, and the LCG is a first type of LCG.

12. The method according to any one of claims 1-3, characterized in that, The latency-sensitive stream includes one or more of the following: real-time communication data stream, interactive service data stream, or high-priority data stream; The real-time communication data stream includes one or more of voice communication data streams, video communication data streams, or audio data streams, and the interactive service data stream includes one or more of game data streams, virtual reality data streams, or extended reality data streams.

13. The method according to claim 4, characterized in that, The method further includes: Receive configuration information; the configuration information is used to configure the first trigger condition and the second trigger condition; or, The configuration information is used to configure the first triggering condition, the second triggering condition, and the third triggering condition.

14. A communication method, characterized in that, The method includes: When a network device is in a congested state, a notification message is sent to the terminal device. The notification message indicates that the network device is in a congested state, so that the terminal device, when a second triggering condition is met, sends the DSR corresponding to the first type of LCG at a second sending frequency, and when a third triggering condition is met, sends the DSR corresponding to the second type of LCG at a third sending frequency. The data stream type corresponding to the first type of LCG is a non-delay-sensitive stream, and the data stream type corresponding to the second type of LCG includes a delay-sensitive stream. The second sending frequency is less than the third sending frequency. The data stream types corresponding to different LCGs include delay-sensitive streams and non-delay-sensitive streams.

15. The method according to claim 14, characterized in that, Before sending the notification information to the terminal device, the method further includes: The terminal device receives a DSR corresponding to an LCG, which is sent by the terminal device when a first trigger condition is met; the second sending frequency is less than the first sending frequency, and the first sending frequency is the frequency at which the DSR corresponding to the first type of LCG is sent based on the first trigger condition.

16. The method according to claim 15, characterized in that, After sending the notification information to the terminal device, the method further includes: The terminal device receives a DSR corresponding to the second type of LCG; the DSR corresponding to the second type of LCG is sent by the terminal device when the first triggering condition is met.

17. The method according to claim 15, characterized in that, After sending the notification information to the terminal device, the method further includes: The terminal device receives a DSR corresponding to a first type of LCG, wherein the DSR is sent by the terminal device when the increase in the buffer data volume corresponding to the first type of LCG is greater than or equal to a first threshold, and / or the buffer data volume is greater than or equal to a second threshold.

18. The method according to claim 16, characterized in that, The method further includes: Send configuration information to the terminal device; the configuration information is used to configure the first trigger condition and the second trigger condition, or... The configuration information is used to configure the first triggering condition, the second triggering condition, and the third triggering condition.

19. A communication system, characterized in that, include: A terminal device and a network device, wherein the terminal device is configured to perform the method as described in any one of claims 1-13, and the network device is configured to perform the method as described in any one of claims 14-18.

20. A communication device, characterized in that, include: At least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 1-18 via logic circuits or execution code instructions.

21. A computer-readable storage medium, characterized in that, This includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-13; and / or cause the computer to perform the method as described in any one of claims 14-18.

22. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-13; and / or cause the computer to perform the method as described in any one of claims 14-18.

Images