Speed regulation method and communication device

Abstract

The invention discloses a speed regulation method and a communication device, relates to the field of communication, and can reduce task response time under an end-cloud collaborative architecture. The method comprises the following steps: receiving first information from access network equipment, acquiring a first message of terminal equipment, and sending a second message to an application server; wherein the first information is used for indicating that a first QoS demand corresponding to a first QoS flow needs to be adjusted to a second QoS demand, the first QoS demand and the second QoS demand correspond to different data transmission rates, and the second message carries second information; the second information is determined according to the first information, a first number of messages experiencing congestion in the first message, a first number of messages without congestion and a number of messages not supporting explicit congestion notification (ECN) feedback, and the second information is used for determining a first congestion proportion when the first QoS flow is transmitted according to the first QoS demand; the first congestion ratio is used for adjusting the data transmission rate of the first QoS flow.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a speed regulation method and a communication device. Background Art

[0002] In the service architecture of terminal-cloud collaboration, the terminal device and the cloud complete computing tasks through interaction and collaboration, such as video rendering services and deep neural network training / inference services, so as to achieve task division of labor and data interaction, and optimize system efficiency. In this architecture, the terminal device and the cloud are both involved in the computing task, and there is information interaction between the two. Therefore, it is necessary to consider the response time of completing the computing task, that is, the elapsed time from task initiation to execution completion. In order to meet the requirements of task response time, it is usually necessary to consider the computing power state and wireless communication state of the terminal device, and adjust the transmission rate at the application layer of the cloud according to the changes of these states. However, how to ensure that the task response time in the terminal-cloud collaboration architecture meets the requirements has become an urgent problem to be solved. Summary of the Invention

[0003] Embodiments of this application provide a speed regulation method and a communication device, which can improve the response speed of completing computing tasks in the terminal-cloud collaboration architecture and reduce the task response time.

[0004] To achieve the above object, this application adopts the following technical solutions:

[0005] In a first aspect, a speed regulation method is provided. This method can be executed by a user plane network element, or by a component of the user plane network element, such as a processor, a chip, or a chip system of the user plane network element, or can also be implemented by a logic module or software that can implement all or part of the user plane network element. The method includes: receiving first information from an access network device. The first information is used to indicate that it is necessary to adjust the first QoS requirement corresponding to the first QoS flow to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates. Obtaining a first message of the terminal device, where the first message includes a first quantity of messages that have experienced congestion, a first quantity of messages that have not experienced congestion, and a quantity of messages that do not support explicit congestion notification (ECN) feedback. Sending a second message to an application server, where the second message carries second information, and the second information is determined according to the first information, the first quantity of messages that have experienced congestion, the first quantity of messages that have not experienced congestion, and the quantity of messages that do not support ECN feedback. The second information is used to determine a first congestion ratio when the first QoS flow is transmitted at the first QoS requirement, and the first congestion ratio is used to adjust the data transmission rate of the first QoS flow.

[0006] Based on this speed regulation method, the user plane network element can obtain the latest network status changes and congestion status in real time according to the QoS requirement changes indicated by the first information sent by the access network device, and update the ECN feedback information in the obtained first packet according to the first information to obtain the second information, and then feedback the second information to the application server through the second packet, so that the application server can adjust the data transmission rate according to the second information. Thus, on the one hand, the user plane network element does not need to bypass the terminal device through the air interface twice to obtain the ECN feedback information, and there is no interval for the terminal device to count the ECN feedback information, which can improve the rate of ECN feedback, thereby reducing the task response time; on the other hand, the user plane network element feeds back the ECN feedback information adjusted by the first information to the application server through the second packet, so that the data transmission rate adjusted by the application server is also more matched with the real-time state of the network, thereby reducing the task response time.

[0007] In a possible design solution, the first information may include one of the following: the second congestion ratio when the first QoS flow transmits with the first QoS requirement, the identifier of the second QoS requirement, or the QoS parameters in the second QoS requirement, where the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement. Thus, the user plane network element can obtain the latest network status changes in real time according to the congestion ratio information, the identifier of the QoS requirement to be adjusted, or the QoS parameters in the QoS requirement to be adjusted, adjust the obtained ECN feedback information of the terminal device according to the network status changes, and feedback it to the application server, so that the data transmission rate adjusted by the application server is more matched with the real-time state of the network, thereby reducing the task response time. It should be understood that the QoS parameters in the second QoS requirement included in the first information may be one or more QoS parameters selected by the access network device from the second QoS requirement.

[0008] In a possible design solution, the QoS parameters may include at least one of the following: Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER). It should be understood that in addition to the above three QoS parameters, the QoS requirements in the embodiments of the present application may also include other QoS parameters for feedback of network status.

[0009] In a possible design solution, the first information may be carried and sent in the packet sent by the access network device. For example, the first information is carried and sent in the header of the General Packet Radio Service Tunneling Protocol - User Plane (GTP-U) packet.

[0010] In a possible design solution, the second information may include the second quantity of packets experiencing congestion, the second quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback; wherein, the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the first information, the second quantity of packets not experiencing congestion is determined according to the total quantity of statistical packets, the second quantity of packets experiencing congestion, and the quantity of packets not supporting ECN feedback, and the total quantity of statistical packets is equal to the sum of the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback. Thus, the user plane network element can update the quantity of packets experiencing congestion and the quantity of packets not experiencing congestion based on the ECN feedback information and the first information in the obtained first packet, so that the ECN feedback information fed back to the application server is more matched with the real-time state change of the network, and the task response time can be reduced.

[0011] In a possible design solution, the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the first information, which may include: the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the second congestion ratio when the first QoS flow transmits with the first QoS requirement, wherein the second congestion ratio is determined according to the first information. Thus, the user plane network element can determine the first congestion ratio according to the first information, and adjust the quantity of packets experiencing congestion according to the first congestion ratio and the ECN feedback information in the first packet, so that the ECN feedback information fed back to the application server is more matched with the real-time state change of the network, and the response time can be reduced.

[0012] In a possible design solution, the second quantity of packets not experiencing congestion is the maximum value between the third quantity and zero, and the third quantity is equal to the difference between the total quantity of statistical packets, the second quantity of packets experiencing congestion, and the quantity of packets not supporting ECN feedback. Thus, the user plane network element adjusts the quantity of packets not experiencing congestion according to the adjusted quantity of packets experiencing congestion, so as to ensure that the data transmission rate adjusted by the application server matches the real-time state change of the network.

[0013] In a possible design solution, the second packet can be obtained by modifying the first quantity of the congested packets in the first packet to the second quantity of the congested packets and modifying the first quantity of the non-congested packets in the first packet to the second quantity of the non-congested packets. For example, if the first packet is a Real-Time Transport Layer Feedback message (RTPFB) packet that supports Explicit Congestion Notification (ECN) feedback being sent by a terminal device, the user plane network element can modify the quantity of the congested packets and the quantity of the non-congested packets in the received first packet to obtain the second packet. Thus, by reusing the RTCP transmission scheme of L4S, the application server can adjust the transmission rate without special adaptation and adjustment, improving the compatibility of dynamic QoS for speed adjustment with existing devices and facilitating the evolution towards a dynamic QoS support system.

[0014] In a possible design solution, the payload in the second packet is empty, the packet sequence number in the second packet is one more than the packet sequence number in the first packet, and the sender identifier and the receiver identifier in the second packet are the same as the sender identifier and the receiver identifier in the first packet respectively. The sender identifier is used to identify the terminal device, and the receiver identifier is used to identify the application server. For example, the user plane network element can locally generate consecutive RTPFB packets that support ECN feedback transmitted by the terminal device, and by reusing the RTCP transmission scheme of L4S, the application server can adjust the transmission rate without special adaptation and adjustment, improving the compatibility of dynamic QoS for speed adjustment with existing devices and facilitating the evolution towards a dynamic QoS support system.

[0015] In a possible design solution, the second packet can be an RTPFB packet or a Quick UDP Internet Connections (QUIC) ACK packet.

[0016] In a second aspect, a speed adjustment method is provided. This method can be executed by an access network device, or by components of the access network device, such as the processor, chip, or chip system of the access network device, or can also be implemented by a logic module or software that can implement all or part of the access network device. The method includes: determining that it is necessary to adjust the first Quality of Service (QoS) requirement corresponding to the first QoS flow to a second QoS requirement, where the first QoS requirement and the second QoS requirement correspond to different data transmission rates. Sending a first message to the user plane network element. The first message is used to indicate that it is necessary to adjust the first QoS requirement to the second QoS requirement.

[0017] In a possible design solution, determining that it is necessary to adjust the first QoS requirement corresponding to the first QoS flow to a second QoS requirement may include: determining that it is necessary to adjust the first QoS requirement to the second QoS requirement according to the channel state, the radio interface transmission situation of the first QoS flow, and the first QoS requirement corresponding to the first QoS flow.

[0018] In a possible design solution, the first information may include one of the following: the second congestion ratio when the first QoS flow is transmitted with the first QoS requirement, the identifier of the second QoS requirement, or the QoS parameters in the second QoS requirement, where the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement.

[0019] In a possible design solution, the QoS parameters may include at least one of the following: Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER).

[0020] In a possible design solution, the first information may be carried and sent in a message sent by the access network device.

[0021] In a possible design solution, the speed regulation method provided by the embodiments of the present application may further include: receiving third information from the application server. The third information is used to indicate a third QoS requirement, and the third QoS requirement is the QoS requirement corresponding to the data transmission rate of the first QoS flow adjusted by the application server.

[0022] Wherein, for the technical effects of the method described in the second aspect, reference may be made to the technical effects described in the method of the first aspect above, and details will not be repeated here.

[0023] In a third aspect, a speed regulation method is provided. This method may be executed by the application server, or by components of the application server, such as the processor, chip, or chip system of the application server, etc., and may also be implemented by a logic module or software that can implement all or part of the application server. The method includes: receiving a second message from the user plane network element. The second message carries second information, and the second information is used to determine the first congestion ratio when the first Quality of Service (QoS) flow is transmitted with the first QoS requirement. Adjust the data transmission rate of the first QoS flow according to the second information.

[0024] In a possible design solution, adjusting the data transmission rate of the first QoS flow according to the second information may include: determining a third QoS requirement according to the second information and the first QoS requirement corresponding to the first QoS flow, where the first QoS requirement and the third QoS requirement correspond to different data transmission rates. Adjust the data transmission rate of the first QoS flow according to the third QoS requirement.

[0025] In a possible design, the speed regulation method provided in the embodiments of the present application may further include: sending third information to an access network device. The third information is used to indicate a third QoS requirement.

[0026] In a possible design, the second information may include the second quantity of packets experiencing congestion, the second quantity of packets not experiencing congestion, and the quantity of packets that do not support explicit congestion notification (ECN) feedback.

[0027] In a possible design, the payload in the second packet is empty.

[0028] Wherein, for the technical effects of the method described in the third aspect, reference may be made to the technical effects described in the method of the first aspect above, and details are not repeated here.

[0029] In a fourth aspect, a communication device is provided for implementing the above various methods. The communication device may be the user plane network element in the first aspect above, or a device including the above user plane network element, or a device included in the above user plane network element, such as a chip. The communication device includes corresponding modules, units, or means for implementing the method described in the first aspect above. The module, unit, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0030] In some possible designs, the communication device includes: a processing module and a transceiver module. The transceiver module receives first information from an access network device. The first information is used to indicate that the first QoS requirement corresponding to the first QoS flow needs to be adjusted to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates. The processing module is configured to obtain a first packet of a terminal device. The first packet includes the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets that do not support explicit congestion notification (ECN) feedback. The transceiver module is further configured to send a second packet to an application server. The second packet carries second information, and the second information is determined according to the first information, the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback. The second information is used to determine a first congestion ratio when the first QoS flow is transmitted at the first QoS requirement, and the first congestion ratio is used to adjust the data transmission rate of the first QoS flow.

[0031] In a possible design, the first information may include one of the following: a second congestion ratio when the first QoS flow is transmitted at the first QoS requirement, an identifier of the second QoS requirement, or QoS parameters in the second QoS requirement, where the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement.

[0032] In a possible design, the QoS parameter may include at least one of the following: Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER).

[0033] In a possible design, the first information may be carried and sent in a packet sent by an access network device.

[0034] In a possible design, the second information may include a second quantity of packets that have experienced congestion, a second quantity of packets that have not experienced congestion, and a quantity of packets that do not support ECN feedback; wherein, the second quantity of packets that have experienced congestion is determined according to the total quantity of counted packets and the first information, and the second quantity of packets that have not experienced congestion is determined according to the total quantity of counted packets, the second quantity of packets that have experienced congestion, and the quantity of packets that do not support ECN feedback, wherein the total quantity of counted packets is the sum of a first quantity of packets that have experienced congestion, a first quantity of packets that have not experienced congestion, and a quantity of packets that do not support ECN feedback.

[0035] In a possible design, the second quantity of packets that have experienced congestion is determined according to the total quantity of counted packets and the first information, and may include: the second quantity of packets that have experienced congestion is determined according to the total quantity of counted packets and a second congestion ratio when the first QoS flow is transmitted with the first QoS requirement, wherein the second congestion ratio is determined according to the first information.

[0036] In a possible design, the second quantity of packets that have not experienced congestion is the maximum value between a third quantity and zero, and the third quantity is equal to the difference between the total quantity of counted packets, the second quantity of packets that have experienced congestion, and the quantity of packets that do not support ECN feedback.

[0037] In a possible design, the second packet may be obtained by modifying the first quantity of packets that have experienced congestion in the first packet to the second quantity of packets that have experienced congestion, and modifying the first quantity of packets that have not experienced congestion in the first packet to the second quantity of packets that have not experienced congestion.

[0038] In a possible design, the payload in the second packet is empty, the packet sequence number in the second packet is one more than the packet sequence number in the first packet, and the sender identifier and the receiver identifier in the second packet are the same as the sender identifier and the receiver identifier in the first packet respectively, where the sender identifier is used to identify the terminal device and the receiver identifier is used to identify the application server.

[0039] In a possible design, the second packet may be a Real-time Transport Layer Feedback Message (RTPFB) packet.

[0040] In a possible design, the transceiver module may include a receiving module and a transmitting module. Among them, the transmitting module is used to implement the transmitting function of the communication device described in the first aspect, and the receiving module is used to implement the receiving function of the communication device described in the first aspect.

[0041] In a possible design, the communication device described in the fourth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instructions, the communication device described in the fourth aspect can execute the method described in the first aspect.

[0042] In the fifth aspect, a communication device is provided for implementing the above various methods. The communication device may be the access network device in the second aspect above, or a device including the above access network device, or a device included in the above access network device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the method described in the second aspect above. The module, unit, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0043] In some possible designs, the communication device includes: a processing module and a transceiver module. Among them, the processing module is used to determine that the first QoS requirement corresponding to the first quality of service (QoS) flow needs to be adjusted to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates. The transceiver module is used to send a first piece of information to the user plane network element. The first piece of information is used to indicate that the first QoS requirement needs to be adjusted to the second QoS requirement.

[0044] In a possible design, the processing module is used to determine that the first QoS requirement corresponding to the first QoS flow needs to be adjusted to a second QoS requirement, specifically including: the processing module is used to determine that the first QoS requirement needs to be adjusted to the second QoS requirement according to the channel state, the radio interface transmission situation of the first QoS flow, and the first QoS requirement corresponding to the first QoS flow.

[0045] In a possible design, the first piece of information may include one of the following: the second congestion ratio when the first QoS flow is transmitted with the first QoS requirement, the identifier of the second QoS requirement, or the QoS parameters in the second QoS requirement, where the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement.

[0046] In a possible design, the QoS parameters may include at least one of the following: guaranteed flow bit rate (GFBR), packet delay budget (PDB), or packet error rate (PER).

[0047] In a possible design, the first information may be carried and sent in a message sent by an access network device.

[0048] In a possible design, the transceiver module is further configured to receive third information from an application server. The third information is used to indicate a third QoS requirement, and the third QoS requirement is the QoS requirement corresponding to the data transmission rate of the first QoS flow adjusted by the application server.

[0049] In a sixth aspect, a communication device is provided for implementing the above various methods. The communication device may be the application server in the above third aspect, or a device including the above application server, or a device included in the above application server, such as a chip. The communication device includes corresponding modules, units, or means for implementing the method described in the above third aspect. The module, unit, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0050] In some possible designs, the communication device includes: a processing module and a transceiver module. The transceiver module is configured to receive a second message from a user plane network element. The second message carries second information, and the second information is used to determine a first congestion ratio when the first quality of service (QoS) flow is transmitted with a first QoS requirement. The processing module is configured to adjust the data transmission rate of the first QoS flow according to the second information.

[0051] In a possible design, the processing module is configured to adjust the data transmission rate of the first QoS flow according to the second information, specifically including: the processing module is configured to determine a third QoS requirement according to the second information and the first QoS requirement corresponding to the first QoS flow, and the first QoS requirement and the third QoS requirement correspond to different data transmission rates. The processing module is further configured to adjust the data transmission rate of the first QoS flow according to the third QoS requirement.

[0052] In a possible design, the transceiver module is further configured to send third information to an access network device. The third information is used to indicate the third QoS requirement.

[0053] In a possible design, the second information may include a second number of packets experiencing congestion, a second number of packets not experiencing congestion, and a number of packets that do not support explicit congestion notification (ECN) feedback.

[0054] In a possible design, the payload in the second message is empty.

[0055] In a seventh aspect, a speed regulation method is provided. The method includes: an access network device sending first information to a user plane network element. The first information is used to indicate that it is necessary to adjust a first Quality of Service (QoS) requirement corresponding to a first QoS flow to a second QoS requirement, where the first QoS requirement and the second QoS requirement correspond to different data transmission rates. The user plane network element receives the first information from the access network device and obtains a first packet of a terminal device. The first packet includes a first quantity of packets that have experienced congestion, a first quantity of packets that have not experienced congestion, and a quantity of packets that do not support explicit congestion notification (ECN) feedback. The user plane network element sends a second packet to an application server. The second packet carries second information, which is determined according to the first information, the first quantity of packets that have experienced congestion, the first quantity of packets that have not experienced congestion, and the quantity of packets that do not support ECN feedback. The second information is used to determine a first congestion ratio when the first QoS flow is transmitted at the first QoS requirement, and the first congestion ratio is used to adjust the data transmission rate of the first QoS flow.

[0056] In an eighth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided. The communication device includes: a processor for implementing the functions involved in the first aspect, the second aspect, or the third aspect described above.

[0057] In a possible design, the communication device may further include a memory for storing necessary program instructions and data. The processor is coupled to the memory, and the processor is configured to execute computer programs or instructions stored in the memory, so that the communication device executes the methods described in the first aspect, the second aspect, or the third aspect.

[0058] In a possible design, the communication device described in the eighth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the eighth aspect to communicate with other communication devices.

[0059] In a possible design, the processor may be integrated with the memory.

[0060] In some possible designs, when the device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0061] In a ninth aspect, a communication device is provided. The communication device includes a processor and an interface circuit. The interface circuit is configured to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device. The processor is configured to implement the methods described in the first aspect, the second aspect, or the third aspect through logic circuits or by executing code instructions.

[0062] In a tenth aspect, a communication device is provided. The communication device may be a user plane network element, or a module or unit (e.g., a chip, or a chip system, or a circuit) that respectively corresponds to the methods / operations / steps / actions described in the first aspect and executes them, or a device that can be used in matching with an access network device. Alternatively, the communication device may be an access network device, or a module or unit (e.g., a chip, or a chip system, or a circuit) that respectively corresponds to the methods / operations / steps / actions described in the second aspect and executes them, or a device that can be used in matching with an access network device. Alternatively, the communication device may be an application server, or a module or unit (e.g., a chip, or a chip system, or a circuit) that respectively corresponds to the methods / operations / steps / actions described in the third aspect and executes them, or a device that can be used in matching with an access network device.

[0063] It can be understood that when the communication device provided in any one of the eighth aspect or the tenth aspect is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0064] In an eleventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or instruction, and when it runs on the communication device, it enables the communication device to execute the methods described in the first aspect or the second aspect or the third aspect above.

[0065] In a twelfth aspect, a computer program product including instructions is provided, including computer program code. When the computer program code runs on the communication device, it enables the communication device to execute the methods described in the first aspect or the second aspect or the third aspect above.

[0066] In a thirteenth aspect, a communication system is provided, including: a communication device for implementing the method described in the first aspect above, a communication device for implementing the method described in the second aspect above, and a communication device for implementing the method described in the third aspect above. Description of the Drawings

[0067] Figure 1 It is a system architecture diagram for video rendering in a pure cloud mode and an edge-cloud collaboration mode;

[0068] Figure 2 It is a schematic architecture diagram of an L4S speed regulation mechanism;

[0069] Figure 3 It is a schematic architecture diagram of a speed regulation mechanism based on dynamic QoS;

[0070] Figure 4 It is a schematic architecture diagram of a communication system provided by an embodiment of the present application;

[0071] Figure 5 It is a schematic flowchart of a speed regulation method provided by an embodiment of the present application;

[0072] Figure 6 It is a schematic structural diagram of an RTPFB packet supporting ECN feedback provided by an embodiment of the present application;

[0073] Figure 7 It is a schematic flowchart of another speed regulation method provided by an embodiment of the present application;

[0074] Figure 8 It is a schematic flowchart of yet another speed regulation method provided by an embodiment of the present application;

[0075] Figure 9 It is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0076] Figure 10 It is a schematic structural diagram of another communication device provided by an embodiment of the present application. Detailed implementation manners

[0077] Embodiments of the present application will present various aspects, embodiments or features around a system that may include multiple devices, components, modules, etc. It should be understood and clear that each system may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the drawings. In addition, combinations of these solutions can also be used.

[0078] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless fidelity (Wi-Fi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle networking communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as 6th generation (6G) mobile communication systems, etc.

[0079] The following introduces the communication systems, applicable network elements, and related terms involved in the embodiments of the present application.

[0080] 1. End-to-end collaboration

[0081] With the continuous evolution of communication networks, the improvement of computing performance of terminal devices, and the development of machine learning algorithms, terminal devices are gradually participating in services handled by servers, such as cloud gaming and machine vision, and heavy computing services, gradually evolving from centralized cloud processing to a joint processing mode between terminal devices and the cloud (central cloud or edge cloud). As a result, a business architecture of end-cloud collaboration has emerged.

[0082] The end-cloud collaborative business architecture is mainly used in video rendering and deep neural network businesses. Typical applications of video rendering are virtual reality (VR) / augmented reality (AR) and cloud gaming. On the one hand, since such emerging video rendering businesses have high requirements for computing power, for example, at a 4K resolution and 60 frames per second (FPS), the computing power required for device video rendering is 13+ trillion (10 12 ) floating point operations per second (TFLOPS), while the computing power of mainstream terminal devices is only about 1.3TFLOPS. It is difficult to meet the computing power requirements of such video rendering services through local processing of terminal devices. At the same time, the power consumption of terminal devices is limited, and they do not support long-term large computing power calculations. On the other hand, although the cloud side has powerful computing power, this type of video rendering service has strong real-time interaction requirements. The terminal device sends operation instructions or posture information to the cloud to complete video rendering, and then sends the rendering results to the terminal device, and finally displays them on the screen of the terminal device. That is, the motion-to-photons (MTP) delay is required to be within 50ms. In mobile networks, due to the fluctuations in the communication quality of wireless channels, it is difficult for pure cloud-based video rendering to meet the MTP delay requirements. Therefore, it is necessary to make full use of the computing power on the terminal device side and the communication link between the end and the cloud to achieve task division and interaction, thereby optimizing system efficiency.

[0083] like Figure 1 As shown, Figure 1 (a) shows the system architecture diagram of video rendering in pure cloud mode. Figure 1Figure (b) shows the system architecture of joint video rendering in the end-cloud collaboration mode. By comparing the two, it can be seen that in the end-cloud collaboration mode, the terminal device uses local storage and algorithm models to execute part of the video rendering tasks. Tasks that are computationally insufficient or cannot be quickly processed locally are transmitted to the cloud and processed by a cluster with extremely strong computing power, and the rendered data stream is sent back to the terminal device. In this way, both the terminal device and the cloud participate in the computing tasks, and information interaction is carried out through the communication link between the two, thus realizing the joint processing of the computing tasks.

[0084] In addition, with the emergence of large language models and artificial intelligence (AI) generation models represented by chat generative pre-trained transformer (Chat GPT), how to provide services with large model functions to terminal devices has also received much attention. Among them, the most intuitive method is to deploy small models on the terminal side and perform collaborative learning with large models on the cloud side. The connection of end-cloud models is also similar to the architecture shown in Figure (b) above. Figure 1 The large and small models of the end and cloud are assigned different tasks, and joint training and inference are carried out through the interaction of intermediate data or models, so as to realize the intelligent service of end-cloud collaboration.

[0085] In the end-cloud collaboration mode, the key metric to focus on is the task response time, that is, the elapsed time from the task initiation to the execution completion, including the comprehensive time consumption of end-cloud computing and transmission. To meet the response time requirements of computing tasks, it is necessary to consider the computing power status and wireless communication status of the terminal device side, and perform task division adjustment or transmission rate adjustment at the application layer according to the changes of these statuses. Among them, due to the characteristics of time-varying and large fluctuations of the wireless channel, it is crucial to timely sense the changes in the wireless communication status and notify the application layer to ensure the timely completion of computing tasks. For this reason, the following two mechanisms are currently proposed to adjust the transmission rate to meet the response time requirements of computing tasks.

[0086] 2. Low latency, low loss, scalable throughput (L4S) speed regulation mechanism

[0087] As a speed regulation mechanism suitable for end-cloud collaboration, L4S has good ecological support and realizes congestion control and the adjustment of the sending rate of the application server (AS) through explicit congestion notification (ECN).

[0088] Exemplarily, Figure 2It is a schematic diagram of the architecture of an L4S speed regulation mechanism. As Figure 2 shown, the access network device performs congestion detection on the downlink Internet Protocol (IP) packets sent by the AS through the user plane function (UPF). The IP packet header includes an ECN field, and the ECN field has four state values: 00 indicates that ECN transmission is not supported and is marked as non-ECT (not ECN-capable transport, not-ECT); 10 indicates that ECN transmission is supported and is marked as ECT(0); 01 indicates that ECN transmission is supported and is marked as ECT(1); 11 indicates that congestion has occurred and is marked as congestion experienced (CE). When the access network device detects a congestion state, it marks the downlink IP packets in the congestion state as CE, so that the terminal device can count the received downlink IP packets with the CE label and feedback the congestion information through the explicit congestion notification echo (ECN-Echo, ECE) field in the header of the uplink Transmission Control Protocol (TCP) acknowledge (ACK) packet or Real-Time Transport Control Protocol (RTCP) packet. The ECE field is used for congestion control and sets the ECE to 1 when the ECN field in the received IP packet header is 1, indicating that there is congestion in the network from the other side to this side. Thus, the AS adjusts the application layer transmission rate according to the received congestion information to complete the entire speed regulation process.

[0089] However, in the above L4S-based speed regulation mechanism, there are certain deficiencies in the response speed and the accuracy of the feedback information. Specifically, in terms of the response speed, after the congestion information is generated at the access network device, it needs to experience two radio interface transmissions to be fed back to the AS, and the reporting interval for the terminal device to count the congestion information is usually greater than 20 ms, which results in a slower response speed; in terms of the feedback information, the granularity of the feedback congestion information is relatively coarse, and the AS cannot accurately judge the network state based on the feedback congestion information. Moreover, the AS usually makes rate adjustment decisions based on multiple congestion feedback reports, which introduces cumulative decision-making latency, not only resulting in inaccurate speed regulation but also slower response speed.

[0090] To address the above problems, the following dynamic Quality of Service (QoS) speed regulation mechanism has been proposed, as specifically described below.

[0091] 3. Speed Regulation Mechanism Based on Dynamic QoS

[0092] As shown Figure 3 in the figure, it is a schematic diagram of the architecture of a speed regulation mechanism based on dynamic QoS. In the initial configuration stage, the AS, 5G core network (5Gcore, 5GC) - control plane (control plane, C) and access network device perform QoS configuration negotiation, so that the access network device can obtain multiple sets of QoS configurations (QoS profiles) corresponding to the application, and configure one of the QoS profiles as the initial QoS profile. Different QoS profiles correspond to different transmission delay or transmission bandwidth requirements. In the speed regulation stage, the access network device performs congestion detection on the downlink IP packet and determines whether to switch the QoS profile. When it is necessary to switch the QoS profile, the access network device feeds back the index corresponding to the new QoS profile or the guaranteed flow bit rate (GFBR) to the UPF through the N3 interface between the access network device and the UPF. Specifically, the access network device carries the index or GFBR corresponding to the new QoS profile in the header of the uplink general packet radio service (GPRS) tunneling protocol - user plane (GTP-U) packet and sends it to the UPF. Correspondingly, after receiving the uplink GTP-U packet with the index or GFBR corresponding to the new QoS profile, the UPF feeds back the index or GFBR corresponding to the new QoS profile to the AS through the application programming interface (API) or in the form of user plane piggybacking. Thus, the AS adjusts the application layer transmission rate according to the received index or GFBR, and completes the entire speed regulation process.

[0093] The above speed regulation mechanism based on dynamic QoS reduces the delay of the feedback path bypassing the terminal device, the waiting report delay of the terminal device, and the AS cumulative decision delay, making the response speed of speed regulation faster and the adjustment target of feedback clearer. However, although the speed regulation scheme based on dynamic QoS largely solves the problems of feedback path bypassing, untimely feedback and decision-making in L4S speed regulation, the current standard does not support the content fed back to the AS being QoS index or GFBR, and it is difficult to achieve cross-vendor implementation, that is, there are ecological problems.

[0094] Therefore, to solve the problems under the above two speed regulation mechanisms, the embodiment of this application provides a speed regulation method, which can not only improve the response speed and speed regulation accuracy, but also has good ecological support.

[0095] To better understand the embodiments of the present application, before introducing the embodiments of the present application, the following points are explained as follows.

[0096] First, in the embodiments of the present application, "for indicating" may include for directly indicating and for indirectly indicating. When it is described that a certain "indication information" is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, and does not mean that the indication information must carry A.

[0097] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, it can directly indicate the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated, etc. It can also indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It can also only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, it can also achieve the indication of specific information by relying on the arrangement order of each information pre-agreed (such as protocol regulations), thereby reducing the indication overhead to a certain extent. At the same time, it can also identify the common parts of each information and uniformly indicate them to reduce the indication overhead caused by separately indicating the same information.

[0098] In addition, the specific indication method can also be various existing indication methods. For example, but not limited to, the above indication methods and their various combinations, etc. The specific details of various indication methods can refer to the prior art and will not be elaborated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods of different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiments of the present application do not limit the selected indication method. In this way, the indication methods involved in the embodiments of the present application should be understood to cover various methods that can enable the party to be indicated to know the information to be indicated.

[0099] The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending periods and / or sending timings of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending periods and / or sending timings of these sub-information can be predefined, for example, predefined according to a protocol, or can be configured by the transmitting device by sending configuration information to the receiving device. Among them, the configuration information can include, for example but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, MAC layer signaling, and physical layer signaling. Among them, MAC layer signaling includes, for example, MAC-CE; physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0100] Second, in the embodiments of this application, the first, second, and various numerical numbers are only for the convenience of description and are not used to limit the scope of the embodiments of this application. For example, to distinguish different indication information. For another example, the first indication information and the second indication information are only for distinguishing different regions and do not limit their order. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit being different.

[0101] Third, in the embodiments of this application, descriptions such as "when...", "in the case of...", "if", and "when" all refer to that the device (such as a terminal device or an access network device) will perform corresponding processing under a certain objective situation, not to limit the time, and it is not required that the device (such as a terminal device or an access network device) must have a judgment action when implementing, nor does it mean there are other limitations.

[0102] At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific way for easy understanding.

[0103] Finally, the network architecture and service scenarios described in the embodiments of this application are for more clearly explaining the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0104] Please refer to Figure 4 , Figure 4 , which is a schematic architecture diagram of a communication system to which the embodiments of the present application are applied. As an example, as shown in Figure 4 , the communication system includes an access network device, a user plane network element, and an application server, which can communicate directly or indirectly with each other in pairs.

[0105] Optionally, the communication system may further include a terminal device. In the embodiments of the present application, the terminal device can achieve end-cloud collaborative processing through the access network device, the user plane network element, and the application server. The application server can provide applications that require end-cloud collaboration, such as instant video rendering (extended reality, XR) / cloud gaming or end-cloud joint AI model training / inference, etc. The terminal device can use its own computing power to complete the processing of some tasks according to local data, and the remaining tasks or tasks that require higher computing power are handed over to the application server in the cloud for execution. The application server then transmits the processed tasks down to the terminal device, thereby achieving end-cloud collaborative processing. The devices or network elements participating in end-cloud collaborative processing will be described separately below.

[0106] 1. Terminal device

[0107] The terminal device(s) can be one or more, such as the first terminal device, the second terminal device, the third terminal device, etc. The terminal device can be a terminal device with transceiver functions, or it can also be a chip or chip system disposed in the terminal device. The terminal device can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile unit, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application can be a mobile phone, cellular phone, smart phone, tablet computer (Pad), wireless data card, personal digital assistant (PDA), wireless modem, handset, laptop computer, machine type communication (MTC) terminal, computer with wireless transceiver functions, virtual reality (VR) terminal, augmented reality (AR) terminal, smart home devices (such as refrigerators, TVs, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in self-driving, wireless terminals in industrial control, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, in-vehicle terminals, roadside units (RSUs) with terminal functions, etc., flying devices (such as smart robots, hot air balloons, drones, airplanes), etc. The terminal device in the present application can also be an in-vehicle module, in-vehicle component, in-vehicle chip or in-vehicle unit built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions. For example, the terminal device can also be a device that serves as a terminal function in D2D communication.

[0108] Embodiments of the present application do not limit the device form of the terminal. The device for implementing the functions of the terminal device may be the terminal device; or it may be a device capable of supporting the terminal device to implement the functions, such as a chip system. This device may be installed in the terminal device or used in matching with the terminal device. In the embodiments of the present application, the chip system may be composed of chips or may include chips and other discrete devices.

[0109] 2. Access network device

[0110] There can be multiple access network devices, such as a first access network device, a second access network device, a third access network device, etc. The access network device can also be referred to as an access network node, a radio access network (RAN) node, a RAN entity, or an access node, etc. It is located on the network side of the above communication system, used to help terminal devices achieve wireless access, and is a device with wireless transceiver functions or a chip or chip system that can be set in the device. The access network device includes but is not limited to: base station, evolved NodeB (eNodeB), access point (AP), transmission reception point (TRP or transmission point, TP), next generation NodeB (gNB), the next generation base station in a 6G mobile communication system, the base station in a future mobile communication system, or the access node in a Wi-Fi system, etc. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, an open radio access network (ORAN), or a radio controller in a centralized radio access network (CRAN) scenario. The access network device can also be one or a group (including multiple antenna panels) of antenna panels of a base station in 5G, or, it can also be a network node that constitutes a gNB, a TRP, a TP, or a transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), a road side unit (RSU) with base station functions. Optionally, the access network device can also be a server, a wearable device, a vehicle or an in-vehicle device, etc. For example, the access network device in V2X technology can be an RSU. All or part of the functions of the network device in this application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The access network device in this application can also be a logical node, a logical module, or software that can implement all or part of the functions of the access network device.

[0111] Among them, the CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as included in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It can be understood that the access network device can be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be classified as a network device in the radio access network (RAN), or the CU can be classified as a network device in the core network (CN), which is not limited here.

[0112] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be called an O-CU (Open CU), the DU can also be called an O-DU, the CU-CP can also be called an O-CU-CP, the CU-UP can also be called an O-CU-UP, and the RU can also be called an O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU, and RU are used as examples in this application. Any unit among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0113] In the embodiments of this application, the form of the access network device is not limited. The device for implementing the functions of the access network device can be the access network device; it can also be a device that can support the access network device to implement this function, such as a chip system. This device can be installed in the access network device or used in matching with the access network device.

[0114] 3. User plane network element

[0115] In the embodiments of this application, the user plane network element is used for packet routing and forwarding, and QoS processing of user plane data, etc. The user plane network element can forward user data packets according to the routing rules of the session management network element. For example, uplink data is sent to a data network or other user plane network elements, and downlink data is forwarded to other user plane network elements or access network devices. This user plane network element can be a UPF in 5G communication.

[0116] 4. Application server

[0117] The application server is located in the cloud and is used to provide application services for terminal devices and cooperate with terminal devices to complete computing task processing, etc. It can be an application (APP). The application server can also include an application layer service processing module and an application function (AF). That is to say, the AF can be deployed in the application server. In the embodiments of this application, the application server can be referred to as AS.

[0118] It should be understood that Figure 4 The shown communication system may also include other core network elements, other terminal devices, or other access network devices, etc., such as access and mobility management elements, data management elements, policy control elements, etc., which are not limited herein. Among them, the access and mobility management element can be the access and mobility management function (AMF) in the 5G system, the data management element can be the unified data management (UDM) in the 5G system, and the policy control element can be the policy control function (PCF) in the 5G system.

[0119] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can also be replaced with the corresponding function names in other communication systems.

[0120] Next, the speed regulation method provided by the embodiments of this application will be specifically described in conjunction with Figures 5 - 8 the following.

[0121] Exemplarily, Figure 5 is a schematic flowchart of a speed regulation method provided by the embodiments of this application. This speed regulation method takes the communication among the terminal device, access network device, user plane network element, and application server shown in Figure 4 as an example for illustration. Of course, the entity performing the actions of the terminal device in this method can also be a device / module in the terminal device, such as a chip, processor, processing unit, etc. in the terminal device; the entity performing the actions of the access network device in this method can also be a device / module in the access network device, such as a chip, processor, processing unit, etc. in the access network device; the entity performing the actions of the user plane network element in this method can also be a device / module in the user plane network element, such as a chip, processor, processing unit, etc. in the user plane network element; the entity performing the actions of the application server in this method can also be a device / module in the application server, such as a chip, processor, processing unit, etc. in the application server. The embodiments of this application do not make specific limitations on this.

[0122] Exemplarily, such as Figure 5As shown, the speed regulation method includes:

[0123] S501. The access network device sends a first piece of information to the user plane network element. Correspondingly, the user plane network element receives the first piece of information from the access network device.

[0124] In the embodiments of the present application, the first piece of information is used to indicate that the first QoS requirement corresponding to the first QoS flow needs to be adjusted to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates. Among them, the first QoS flow refers to a service data flow that meets the QoS requirement provided by the application server to the terminal device. One service corresponds to one QoS flow, and different services correspond to different QoS flows. The services interacted between the application server and the terminal device can be services related to computing services, such as video rendering, AI model training, etc., or can be services related to data services, such as sensing data, positioning data, measurement data, etc., which are not limited herein.

[0125] For each QoS flow, such as the first QoS flow, multiple QoS requirements can be configured. Each QoS requirement corresponds to an identifier, and different identifiers correspond to different QoS requirements. The identifier of the QoS requirement can be the 5G QoS identifier (5GQI) in 5G, or can be the index of the QoS requirement among multiple QoS requirements. Moreover, each QoS requirement also corresponds to a data transmission rate, and different QoS requirements correspond to different data transmission rates. The data transmission rate refers to the data transmission rate of the application server sending the first QoS flow, that is, the rate of the application server sending downlink data. In the embodiments of the present application, the higher the QoS requirement, the higher the corresponding data transmission rate.

[0126] For each QoS requirement, it includes different types of QoS parameters. The QoS parameters can include at least one of the following: GFBR, packet delay budget (PDB), or packet error rate (PER). It should be understood that the number and types of QoS parameters in the multiple QoS requirements configured for the first QoS flow are the same, but the values are different, to characterize different requirements for transmission delay, bandwidth, etc. of the first QoS flow. For example, the first QoS requirement includes GFBR1, PDB1, and PER1, and the second QoS requirement includes GFBR2, PDB2, and PER2. The values of GFBR1 and GFBR2 are different, the values of PDB1 and PDB2 are different, and the values of PER1 and PER2 are different.

[0127] In a possible scenario, the identification of QoS requirements can also be regarded as a type of QoS parameter. In other words, QoS requirements include the identification of QoS requirements. It should also be understood that in addition to the above three types of QoS parameters, QoS requirements may also include other types of QoS parameters used to characterize transmission requirements such as latency and bandwidth, which are not limited herein.

[0128] In the embodiments of the present application, QoS requirements may include, in addition to data transmission QoS requirement parameters, computing QoS requirement parameters, such as computing latency requirements, computing load requirements, computing accuracy requirements, or computing energy consumption requirements, etc., which are not limited herein. Additionally, in the embodiments of the present application, QoS requirements may also be referred to as QoS profiles, QoS information, QoS requirements, etc., which are not limited herein.

[0129] It should be understood that the QoS requirements described in the embodiments of the present application are equally applicable to uplink transmission, which is not limited herein.

[0130] For multiple QoS requirements corresponding to the first QoS flow, they can be configured or negotiated by the application server through the core network control plane and configured to the access network device. In a possible implementation, the application server can send a first correspondence relationship to the access network device through the core network control plane. Correspondingly, the access network device can receive the first correspondence relationship from the application server through the core network control plane. The first correspondence relationship includes the identification of the QoS requirements corresponding to the first QoS flow, the correspondence relationship between the QoS requirements corresponding to the first QoS flow and the data transmission rate, or the first correspondence relationship includes the identification of the QoS requirements corresponding to the first QoS flow and the QoS requirements corresponding to the first QoS flow, as well as the correspondence relationship between the QoS requirements corresponding to the first QoS flow and the data transmission rate. The first correspondence relationship can be configured in the form of a table. Exemplarily, the first correspondence relationship is shown in Table 1 below:

[0131] Table 1

[0132] Identifier of QoS requirements corresponding to the first QoS flow QoS requirements Data transfer rate 0 GFBR1, PDB1, PER1 V1 1 GFBR2, PDB2, PER1 V2 … … … N - 1 (N is a positive integer) GFBRN - 1, PDBN - 1, PERN - 1 VN - 1

[0133] At the initial configuration, the access network device may default that the initially used QoS requirement can be the QoS requirement with the highest transmission rate among multiple QoS requirements, or the application server may indicate which QoS requirement among multiple QoS requirements is the initially used QoS requirement, and there is no limitation on this. In addition, at the initial configuration, the application server may also send a quantized congestion notification (QCN) configuration to the access network device, and this QCN configuration is used to configure the access network device to perform congestion feedback. The QCN configuration may include a notification method configuration, and the notification method configuration is used to configure the method for the access network device to notify and feedback congestion information. In the embodiments of the present application, the notification method of the access network device is configured to notify through the user plane.

[0134] Optionally, the QCN configuration may further include a notification parameter configuration, and the notification parameter configuration is used to configure the notification parameters for the access network device to send to the user plane network element for feedback of congestion. The notification parameters may be a congestion ratio, an identifier of the adjusted QoS requirement, or QoS parameters in the adjusted QoS requirement, etc., and there is no limitation on this. In a possible implementation, the notification parameters may also be protocol-agreed or pre-configured, and in this case, the QCN configuration may not include a notification parameter configuration.

[0135] In the embodiments of the present application, the first QoS requirement is the QoS requirement currently used by the access network device. The first QoS requirement may be the initially configured QoS requirement or the adjusted QoS requirement, and there is no limitation on this. That is to say, the application server currently sends downlink data to the terminal device through the user plane network element and the access network device at the data transmission rate corresponding to the first QoS requirement.

[0136] Correspondingly, the access network device monitors the network status according to the first QoS requirement, and determines whether the currently used first QoS requirement needs to be adjusted. Exemplarily, the access network device may determine that the first QoS requirement needs to be adjusted to a second QoS requirement according to the channel state between the terminal device and itself, the radio interface transmission situation of the first QoS flow, and the first QoS requirement corresponding to the first QoS flow. Among them, the channel state between the terminal device and the access network device can be fed back by the signal to interference plus noise ratio (SINR), and the radio interface transmission situation of the first QoS flow can be fed back by the cache queue situation or the radio interface transmission rate, etc. That is to say, the access network device can judge whether the current QoS requirement needs to be adjusted based on the detected good or bad channel state and the fast or slow radio interface transmission. If adjustment is needed, it can determine which QoS requirement needs to be adjusted according to the channel state and the radio interface transmission situation, that is, whether to adjust to a QoS requirement with a higher delay requirement or a QoS requirement with a lower delay requirement. For example, if the channel state is good and there is no cache in the queue, indicating that the radio interface transmission is fast, the access network device determines that the QoS requirement needs to be adjusted to a QoS requirement with a higher delay requirement than the first QoS requirement (i.e., the second QoS requirement), indicating that the application server needs to increase the data transmission rate; if the channel state is poor and there is a large cache in the queue, indicating that the radio interface transmission is slow, the access network device determines that the QoS requirement needs to be adjusted to a QoS requirement with a lower delay requirement than the first QoS requirement (i.e., the second QoS requirement), indicating that the application server needs to reduce the data transmission rate.

[0137] Thus, the access network device determines that the first QoS requirement needs to be adjusted to the second QoS requirement, and indicates it to the user plane network element through the first information. At this time, the first information is the above-mentioned notification parameter. The first information may include one of the following: the second congestion ratio when the first QoS flow is transmitted with the first QoS requirement, the identifier of the second QoS requirement, or the QoS parameter in the second QoS requirement. The specific parameters included in the first information may be pre-configured by the application service, or may be protocol-agreed or pre-configured, and this is not limited. That is to say, the access network device can feedback the second congestion ratio, the identifier of the second QoS requirement, or the QoS parameter in the second QoS requirement to the user plane network element to indicate that the current QoS requirement needs to be adjusted. It should be understood that the QoS parameter in the second QoS requirement included in the first information may be one or more QoS parameters selected from the second QoS requirement.

[0138] Among them, the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement. That is, the access network device determines the second congestion ratio according to the first QoS requirement and the second QoS requirement. In a possible implementation, the access network device may determine the second congestion ratio according to the change of one or more QoS parameters in the first QoS requirement and the second QoS requirement.

[0139] In a specific example 1, the access network device may calculate the second congestion ratio according to GFBR1 in the first QoS requirement and GFBR2 in the second QoS requirement. For example, the second congestion ratio When GFBR2 is less than GFBR1, it indicates that there is congestion in the network and the data transmission rate needs to be reduced; when GFBR2 is greater than or equal to GFBR1, it indicates that there is no congestion in the network and the data transmission rate needs to be increased. At this time, the second congestion ratio k 2 is negative, then the access network device may set the second congestion ratio k 2 to zero, that is, k 2 = 0. Thus, the second congestion ratio can be further expressed as

[0140] Alternatively, the access network device may calculate the second congestion ratio according to PDB1 in the first QoS requirement and PDB2 in the second QoS requirement. For example, the second congestion ratio When PDB2 is greater than or equal to PDB1, it indicates that there is congestion in the network and the data transmission rate needs to be reduced; when PDB2 is less than PDB1, it indicates that there is no congestion in the network and the data transmission rate needs to be increased.

[0141] Alternatively, the access network device may calculate the second congestion ratio according to PER2 in the second QoS requirement. For example, the second congestion ratio k 2 = PER TH is the set PER threshold. When PER2 is greater than or equal to PER TH , it indicates that there is congestion in the network and the data transmission rate needs to be reduced; when PER2 is less than PER TH , it indicates that there is no congestion in the network and the data transmission rate needs to be increased.

[0142] In a specific example 2, the access network device may calculate the second congestion ratio according to GFBR1, PDB1, PER1 in the first QoS requirement and GFBR2, PDB2, PER2 in the second QoS requirement. For example, k 2 = k 2 '+ Δk 2 , Δk 2 = a·Δ GFBR+b·Δ PER +c·Δ PDB +d, where k 2 ′ is the reference value of the second congestion ratio, and Δk 2 is the change amount of the second congestion ratio, and Δ GFBR = GFBR2 - GFBR1, Δ PER = PER2 - PER1, Δ PDB = PDB2 - PDB1, and a, b, and c are the weight values of the influence of Δ GFBR , Δ PER , and Δ PDB on the second congestion ratio respectively, and d is a constant. That is to say, the access network device can establish a fitting relationship between the change amount of the second congestion ratio and the change amounts of each parameter in the new and old QoS requirements to determine the second congestion ratio.

[0143] The above k 2 ′, a, b, c, and d can be a set of pre-set values, which can be adjusted by the access network device in real time according to the network state, or can be a set selected by the access network device from multiple pre-set sets according to the network state, or can be set by the access network device in real time according to the network state, and no limitation is made thereto. It should be understood that there may be values of 0 among a, b, and c, but they cannot be 0 at the same time. If one of the three weight values is 0, it can be considered that the QoS parameter corresponding to the weight value of 0 does not participate in the calculation of the second congestion ratio, or it can be considered that the second congestion ratio is calculated according to at least one QoS parameter.

[0144] It should also be understood that in the embodiments of the present application, there can be various designs for the conversion algorithm of the access network device or the user plane network element to convert the identifier or QoS parameter of the second QoS requirement into the second congestion ratio. In addition to the simple conversion method and the linear fitting method of the change of a single QoS parameter mentioned above, it can also include, but is not limited to, a preset deterministic algorithm, statistical historical data, non-linear fitting, machine learning methods, etc. The network state inputs involved in the algorithm are not limited to the indicators such as GFBR, PER, and PDB mentioned above. For any conversion algorithm that can be implemented in the embodiments of the present application, it can satisfy the following relationship: The second congestion ratio, and its input can include one or more QoS parameters and their combinations, and no specific limitation is made thereto.

[0145] In a possible design solution, the access network device can carry the first information in the sent message and send it to the user plane network element. For example, the access network device carries the first information in the header of the GTP-U message and sends it.

[0146] Further, after receiving the first piece of information, the user plane network element may determine that the current QoS requirement needs to be adjusted based on the first piece of information, and then instruct the application server to adjust the data transmission rate. For the specific implementation, reference may be made to the relevant description in S503 below and will not be elaborated here. In the embodiments of the present application, the application server will also configure multiple QoS requirements corresponding to the first QoS flow for the user plane network element, as well as which QoS requirement is currently in use. In other words, both the application server and the access network device store multiple QoS requirements corresponding to the first QoS flow and know which QoS requirement is currently in use.

[0147] S502. The user plane network element obtains a first packet of the terminal device.

[0148] Among them, the first packet includes the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback. In the embodiments of the present application, the first packet may be a packet supporting the feedback of ECN information. It should be understood that the uplink data is carried in the first packet.

[0149] In a possible implementation manner, the first packet may adopt the RTCP feedback packet structure defined in Request for Comments (RFC) 4585, that is, the type of the first packet is a real-time transport layer feedback message (RTPFB) packet in the RTCP protocol. As Figure 6 shown, it is a schematic structural diagram of an RTPFB packet supporting ECN feedback. Among them, the PT field is used to identify the type of the packet, the FMT field is used to identify the specific subtype of the feedback packet, the synchronous source (SSRC) (SSRC of packet sender) field of the packet sender identifies the sending end of the RTPFB packet supporting ECN feedback, that is, the sending end identifier; the SSRC (SSRC of media source) field of the media source identifies the receiving end of the RTPFB packet supporting ECN feedback, that is, the receiving end identifier; the feedback control information (FCI) field is used to indicate the specific content of the feedback. The FCI field includes an ECN-CE quantity field for indicating the quantity of packets experiencing congestion, an ECT(0) quantity field or an ECT(1) quantity field for indicating the quantity of packets not experiencing congestion, a not-ECT quantity field for indicating the quantity of packets not supporting ECN feedback, a lost packets counter field, and a duplication counter field, etc.

[0150] In the embodiments of the present application, if the first message adopts the message structure as Figure 6 shown, the specific value meanings of each field in the first message are as follows: The PT field has a value of 205, indicating PT = 205, which is used to identify that the type of the first message is an RTPFB message; the FMT field has a value of 8, indicating FMT = 8, which is used to identify that the specific subtype of the first message whose message type is an RTPFB message is an ECN feedback message; the specific value of the SSRC field of the packet sender is used to identify the terminal device that sends the first message; the specific value of the SSRC field of the media source is used to identify the application server that receives the first message; in the FCI field, the specific value of the ECN-CE quantity field is equal to the first quantity of the packets that have experienced congestion, indicated as ECN-CE Counter1, the specific value of the ECT(0) quantity field or the ECT(1) quantity field is equal to the first quantity of the packets that have not experienced congestion, indicated as ECT Counter1, and the specific value of the not-ECT quantity field is equal to the quantity of the packets that do not support ECN feedback, indicated as not-ECT Counter.

[0151] In a possible design solution, the sum of the first quantity of the packets that have experienced congestion, the first quantity of the packets that have not experienced congestion, and the quantity of the packets that do not support ECN feedback in the first message, that is, the total number of statistical messages is equal to the sum of the first quantity of the packets that have experienced congestion, the first quantity of the packets that have not experienced congestion, and the quantity of the packets that do not support ECN feedback, indicated as S-Counter = ECN-CE Counter1 + ECT Counter1 + not-ECT Counter, which is usually based on pre-configuration or regulation, and usually, the quantity of the packets that do not support ECN feedback is constant.

[0152] It should be understood that in addition to the above fields, the first message further includes a base sequence number field, which is used to identify the sending sequence number of the message. In the embodiments of the present application, this field is used to identify that the first message is the Lth RTPFB message that supports ECN feedback sent by the terminal device, where L is a positive integer and less than or equal to M, and M is the maximum number of RTPFB messages that support ECN feedback that the terminal device supports sending.

[0153] In addition to the RTPFB message that supports ECN feedback, the first message can also be a quick UDP internet connections (QUIC) ACK message of the user datagram protocol (UDP) network connection. There is also count information of ECT(0), ECT(1), and ECN-CE in this type of message, which will not be elaborated here.

[0154] In a possible implementation, the terminal device sends a first message to the user plane network element. Correspondingly, the user plane network element receives the first message from the terminal device. That is to say, the first message is sent by the terminal device to the application server via the user plane network element. The first message can be an uplink message that the user plane network element is receiving from the terminal device, or an uplink message that the user plane network element stores as the most recent message sent by the terminal device, and this is not limited.

[0155] It should be understood that in the embodiments of the present application, the execution order of S501 and S502 is not limited. It can be that S501 is executed first and S502 is executed later, or it can be that S502 is executed first and S501 is executed later, and this is not limited.

[0156] S503. The user plane network element sends a second message to the application server. Correspondingly, the application server receives the second message from the user plane network element.

[0157] In the embodiments of the present application, the second message carries second information. The second information is used to determine a first congestion ratio when the first QoS flow transmits with a first QoS requirement. The first congestion ratio is used to adjust the transmission rate of the first QoS flow. Among them, the second information is determined according to the first information, the first number of messages that have experienced congestion, the first number of messages that have not experienced congestion, and the number of messages that do not support ECN feedback.

[0158] That is to say, after the user plane network element obtains the first message and the first information, it can determine the second information according to the first information, the first number of messages that have experienced congestion, the first number of messages that have not experienced congestion, and the number of messages that do not support ECN feedback in the first message, and then carry the second information in the second message and send it to the application server, so that the application server can determine the second congestion ratio according to the second information and adjust the data transmission rate.

[0159] In a possible implementation, the second information may include the second number of messages that have experienced congestion, the second number of messages that have not experienced congestion, and the number of messages that do not support ECN feedback.

[0160] Among them, the second number of messages that have experienced congestion can be determined according to the total number of statistical messages and the first information. That is to say, the user plane network element can determine the second number of messages that have experienced congestion according to the first information and the total number of statistical messages.

[0161] Further, the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the second congestion ratio when the first QoS flow is transmitted with the first QoS requirement, where the second congestion ratio is determined according to the first information. That is to say, the user plane network element determines the second congestion ratio existing when the first QoS flow is transmitted with the first QoS requirement according to the obtained first information, and determines the second quantity of packets experiencing congestion according to the second congestion ratio and the total quantity of statistical packets.

[0162] The following takes the second quantity of packets experiencing congestion being represented as ECN-CE Counter2 and the second quantity of packets not experiencing congestion being represented as ECT Counter2 as an example for description. The second congestion ratio (i.e., k 2 ), the total quantity of statistical packets (i.e., S-Counter), the first quantity of packets experiencing congestion (i.e., ECN-CE Counter1), the first quantity of packets not experiencing congestion (i.e., ECT Counter1), and the quantity of packets not supporting ECN feedback (i.e., not-ECT Counter) continue to refer to the above description for their representation forms.

[0163] In a specific example 1, the first information includes the second congestion ratio, which can be understood as the first information directly indicating the second congestion ratio k 2 . Thus, the user plane network element sums up the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback in the first packet to obtain the total quantity of statistical packets, that is, S-Counter = ECN-CE Counter1 + ECT Counter1 + not-ECT Counter, and then calculates the second quantity of packets experiencing congestion according to the second congestion ratio k 2 in the first information and the total quantity of statistical packets, that is, ECN-CECounter2 = k 2 ×S-Counter.

[0164] In a specific example 2, the first information includes an identifier of a second QoS requirement. Thus, the user plane network element can compare the identifier of the second QoS requirement with the stored identifier of the first QoS requirement. If they are inconsistent, it can determine that the QoS requirement needs to be adjusted, and determine the specific QoS parameter value of the second QoS requirement from the stored multiple QoS requirements according to the identifier of the second QoS requirement. Thus, the second congestion ratio can be calculated based on the QoS parameters in the first QoS requirement and the QoS parameters in the second QoS requirement. At this time, the user plane network element can calculate the second congestion ratio according to the change of the same QoS parameter in the first QoS requirement and the second QoS requirement. For example, for the change of the GFBR parameter, the specific calculation process of the user plane network element can refer to the relevant description of the access network device calculating the second congestion ratio in Example 1 of S501 above, which will not be elaborated here. Alternatively, the user plane network element can calculate the second congestion ratio according to the changes of multiple QoS parameters in the first QoS requirement and the second QoS requirement. The specific calculation process of the user plane network element can refer to the relevant description of the access network device calculating the second congestion ratio in Example 2 of S501 above, which will not be elaborated here. Thus, the user plane network element can calculate the second quantity of the packets that have experienced congestion according to the second congestion ratio and the total number of statistical packets. The specific implementation can refer to the calculation method of the second quantity of the packets that have experienced congestion in Example 1 of S503, which will not be elaborated here.

[0165] In a specific example 3, the first information includes the QoS parameters in the second QoS requirement. If the QoS parameter in the second QoS requirement is one, such as the GFBR parameter, the specific implementation process of the user plane network element calculating the second congestion ratio can refer to the relevant description of the access network device calculating the second congestion ratio in Example 1 of S501 above, which will not be elaborated here; if the QoS parameters in the second QoS requirement are multiple, the specific implementation process of the user plane network element calculating the second congestion ratio can refer to the relevant description of the access network device calculating the second congestion ratio in Example 2 of S501 above, which will not be elaborated here. Thus, the user plane network element can calculate the second quantity of the packets that have experienced congestion according to the second congestion ratio and the total number of statistical packets. The specific implementation can refer to the calculation method of the second quantity of the packets that have experienced congestion in Example 1 of S503, which will not be elaborated here.

[0166] The second quantity of the packets that have not experienced congestion can be determined according to the total number of statistical packets, the second quantity of the packets that have experienced congestion, and the number of packets that do not support ECN feedback. Exemplarily, ECT Counter2 = S - Counter - ECN - CECounter2 - not - ECT Counter.

[0167] Further, since the number of re-determined non-congested packets may be negative, the second number of non-congested packets can be the maximum of the third number and zero, where the third number is equal to the difference between the total number of statistical packets, the second number of congested packets, and the number of packets that do not support ECN feedback. In other words, the user plane network element determines the difference between the total number of statistical packets, the second number of congested packets, and the number of packets that do not support ECN feedback as the third number, and determines the maximum of the third number and zero as the second number of non-congested packets.

[0168] Exemplarily, ECT Counter2 = max{S-Counter-ECN-CE Counter2-not-ECT Counter, 0}, that is, S-Counter-ECN-CE Counter2-not-ECT Counter is equal to the third number.

[0169] That is to say, the user plane network element updates the number of congested packets and the number of non-congested packets fed back by the terminal device in combination with the first information (feedback on network state change) fed back by the access network device, and feeds back the updated number of congested packets, the number of non-congested packets, and the unchanged number of packets that do not support ECN feedback to the application server through the second packet.

[0170] In a possible implementation, the second packet can be an RTPFB packet or a QUIC ACK packet that supports ECN feedback.

[0171] In a possible design, the second packet can be obtained by modifying the first number of congested packets in the first packet to the second number of congested packets and modifying the first number of non-congested packets in the first packet to the second number of non-congested packets. At this time, the first packet is a packet being sent by the terminal device received by the user plane network element, and the user plane network element modifies the number of congested packets and the number of non-congested packets in the first packet to obtain the second packet.

[0172] Exemplarily, the first packet is an RTPFB packet that supports ECN feedback. The user plane network element modifies the specific value of the ECN-CE quantity field in the first packet from ECN-CE Counter1 to ECN-CE Counter2, and modifies the specific value of the ECT(0) quantity field or the ECT(1) quantity field from ECT Counter1 to ECT Counter2 to obtain the second packet.

[0173] In a possible design solution, the user plane network element can locally generate a second packet, and the payload in the second packet is empty. At this time, the first packet can be regarded as the most recent uplink packet sent by the terminal device received by the user plane network element. It can be understood that when the user plane network element currently feeds back the second information, it does not receive the latest uplink packet sent by the terminal device in time, and locally generates a second packet as the latest uplink packet sent by the terminal device to carry the second information, and there is no uplink service data sent by the terminal device in the locally generated second packet. Therefore, the second information in the second packet locally generated by the user plane network element is determined according to the first information, the number of non-congested packets in the uplink packet of the terminal device received most recently, the number of non-congested packets, and the number of packets that do not support ECN feedback. At the same time, to ensure the continuity of packet transmission, the packet sequence number in the second packet is the packet sequence number in the first packet plus one, and the sender identifier and receiver identifier in the second packet are the same as the sender identifier and receiver identifier in the first packet respectively. The sender identifier is used to identify the terminal device, and the receiver identifier is used to identify the application server. For example, if the base sequence number in the first packet is L, the base sequence number in the second packet is L + 1, and the specific values of the SSRC field of the packet sender and the SSRC field of the media source in the second packet are the same as those in the first packet.

[0174] In the embodiments of the present application, in addition to the above implementation manners, the user plane network element can also add a new field in the second packet to indicate the second information, or reuse an existing field to indicate the second information, which is not limited herein. In addition, in addition to being indicated by the number of packets in the above three states, the second information can also be indicated in other ways, such as directly indicating the first congestion ratio by the second information, which is not limited herein.

[0175] Thus, by modifying or generating ECN packets, the user plane network element reuses the RTCP transmission scheme of L4S, improving the compatibility of dynamic QoS for speed regulation with existing devices, enabling the application server to adjust the transmission rate without special adaptation and adjustment, having ecological support, and contributing to the evolution towards a dynamic QoS support system.

[0176] S504. The application server adjusts the data transmission rate of the first QoS stream according to the second information.

[0177] In the embodiments of the present application, after obtaining the second packet, the application server parses the second packet to obtain the second information, and determines the first congestion ratio according to the second information, so as to adjust the data transmission rate of the first QoS stream according to the first congestion ratio.

[0178] In a possible implementation, the application server determines a third QoS requirement according to the second information and the first QoS requirement corresponding to the first QoS flow, and adjusts the data transmission rate of the first QoS flow according to the third QoS requirement. The third QoS requirement is one of the multiple configured QoS requirements other than the first QoS requirement. The third QoS requirement may be the same as or different from the second QoS requirement above. The first QoS requirement and the third QoS requirement also correspond to different data transmission rates.

[0179] Exemplarily, the second information includes the second quantity ECN-CE Counter2 of packets experiencing congestion, the second quantity ECT Counter2 of packets not experiencing congestion, and the quantity not-ECT Counter of packets not supporting ECN feedback. The first congestion ratio is denoted as k 1 , and the first congestion ratio satisfies the following relationship:

[0180] Thus, after the application server calculates the first congestion ratio according to the second information, it determines which QoS requirement to adjust to, that is, the third QoS requirement, according to the first congestion ratio and the currently used first QoS requirement. For example, the application server calculates the GFBR value to be adjusted, that is, GFBR X (which can be called the reference value of GFBR), through the following formula according to the first congestion ratio and GFBR1 in the first QoS requirement: GFBR X = GFBR1×(1 - k 1 ). The QoS requirement with the GFBR value closest to and less than GFBR X among the multiple configured QoS requirements is used as the third QoS requirement. The data transmission rate corresponding to the third QoS requirement is the adjusted data transmission rate. That is, the application server adjusts the data transmission rate from the data transmission rate corresponding to the first QoS requirement (such as V1) to the data transmission rate corresponding to the third QoS requirement (such as V3) to transmit the first QoS flow.

[0181] It should be understood that the adjustment formula in the above example is for reducing the data transmission rate. GFBR X (equivalent to GFBR3) is at most equal to GFBR1. That is, when GFBRX or GFBR3 is less than GFBR1, it means that the data transmission rate can be reduced. In addition, in some possible situations, GFBRX or GFBR3 can be greater than or equal to GFBR1, indicating that the data transmission rate can be increased.

[0182] Further, after the application server completes speed regulation, it can inform the user plane network element and the access network device of the QoS requirements corresponding to the adjusted data transmission rate (i.e., the third QoS requirements). Exemplarily, the application server sends the third information to the access network device and the user plane network element respectively. Correspondingly, the access network device receives the third information from the application server, and the user plane network element receives the third information from the application server. The third information is used to indicate the third QoS requirements. Thus, the access network device can switch the first QoS requirements to the third QoS requirements according to the third information to ensure the transmission of the first QoS flow, and the user plane network element can know that the currently used QoS requirements are switched to the third QoS requirements according to the third information, so as to perform the next speed regulation feedback.

[0183] Based on Figure 5 The speed regulation method shown, the user plane network element can know the latest network state change and congestion status in real time according to the QoS requirement change indicated by the first information sent by the access network device, and update the ECN feedback information in the obtained first packet according to the first information to obtain the second information, so as to feedback the second information to the application server through the second packet, so that the application server can adjust the data transmission rate according to the second information. Thus, on the one hand, the user plane network element does not need to bypass the terminal device twice through the air interface to obtain the ECN feedback information, and there is no interval for the terminal device to count the ECN feedback information, which can improve the rate of ECN feedback, thereby reducing the task response time; on the other hand, the user plane network element feeds back the ECN feedback information adjusted by the first information to the application server through the second packet, so that the data transmission rate that the application server can adjust is also more matched with the real-time state of the network, thereby reducing the task response time.

[0184] The following combines specific scenarios to Figure 5 describe the speed regulation method shown in detail. Among them, the application server is AS, the user plane network element is UPF, the access network device is gNB, the first QoS requirement is QoS requirement 1, and the second QoS requirement is QoS requirement 2 as an example for description.

[0185] Exemplarily, Figure 7 is a schematic flow chart of a speed regulation method provided by an embodiment of the present application. As Figure 7 shown, the speed regulation method includes the following steps:

[0186] S701. The AS performs initial QoS configuration with the UPF and the gNB.

[0187] Exemplarily, the AS can negotiate and configure multiple QoS requirements, such as QoS requirements 1 to 6, with the UPF and the gNB respectively for the first QoS flow it transmits. Different QoS requirements correspond to different data transmission rates for transmitting the first QoS flow. Each QoS requirement includes QoS parameters such as GFBR, PDB, and PER. And, QoS requirement 1 among QoS requirements 1 to 6 is used as the initially used QoS requirement, that is, the AS currently transmits the first QoS flow at the data transmission rate corresponding to QoS requirement 1.

[0188] In a possible implementation, the AS can trigger the 5GC to send a protocol data unit (PDU) session resource establishment request or adjustment message to the gNB, and carry multiple QoS requirements corresponding to the first QoS flow in the PDU session resource establishment request or adjustment message. Optionally, the PDU session resource establishment request or adjustment message can also carry a QCN configuration. Among them, the specific descriptions of the QoS requirements and the QCN configuration can refer to the relevant descriptions in S501 above, and will not be elaborated here.

[0189] S702. The gNB monitors the network status and the radio interface transmission situation of the first QoS flow.

[0190] During the transmission of the first QoS flow with QoS requirement 1, the gNB monitors the change of the network status in real time and the radio interface transmission situation when the first QoS flow is transmitted with QoS requirement 1, and judges whether the current network status and the radio interface transmission situation match QoS requirement 1. If not, the gNB determines a matching QoS requirement, such as QoS requirement 2, from the configured multiple QoS requirements according to the current network condition and the radio interface transmission situation. For example, if the gNB monitors that the network status is poor and there is congestion in the radio interface transmission, the gNB can select a QoS requirement with a lower delay requirement than QoS requirement 1; if the gNB monitors that the network status is good and there is no congestion in the radio interface transmission, the gNB can select a QoS requirement with a higher delay requirement than QoS requirement 1. Among them, the specific implementation process of S702 can refer to the relevant descriptions in S501 above, and will not be elaborated here.

[0191] S703. The gNB sends a GTP-U message to the UPF. Correspondingly, the UPF receives the GTP-U message from the gNB.

[0192] Among them, the first information is carried in the header of the GTP-U message, and the first information is used to indicate the congestion ratio 1 of the first QoS flow transmitted with QoS requirement 1. That is to say, after determining that the QoS requirement needs to be adjusted according to S702 above, the gNB can determine the congestion ratio 1 according to the determined new QoS requirement (i.e., QoS requirement 2) and the old QoS requirement (i.e., QoS requirement 1), and carry the congestion ratio 1 in the form of the first information in the header of the GTP-U message and send it to the UPF.

[0193] For example, GFBR1 = 6 kb / s in QoS requirement 1, GFBR2 = 4 kb / s in QoS requirement 1, and the gNB can calculate the congestion ratio 1 according to GFBR1 and GFBR2, that is, the congestion ratio Indicates that there may be congestion and the data transmission rate needs to be reduced.

[0194] For another example, GFBR1 = 4 kb / s in QoS requirement 1, GFBR2 = 6 kb / s in QoS requirement 1, and the gNB can calculate the congestion ratio 1 according to GFBR1 and GFBR2, that is, the congestion ratio Indicates that there is no congestion and the data transmission rate needs to be increased. At this time, the congestion ratio 1 can be set to zero, that is, the congestion ratio 1 = 0.

[0195] S704. The UPF obtains the RTPFB message 1.

[0196] Among them, the RTPFB message 1 includes the ECN feedback information of the UE. The ECN feedback information includes the first quantity of the packets experiencing congestion such as ECN-CE Counter1 = 150, the first quantity of the packets not experiencing congestion such as ECT Counter1 = 200, and the quantity of the packets not supporting ECN feedback such as not-ECT Counter = 50. That is to say, the value of the ECN-CE quantity field in the RTPFB message 1 is 150, the value of the ECT(1) quantity field is 200, and the value of the not-ECT quantity field is 50.

[0197] Exemplarily, the UPF receives the RTPFB message 1 from the UE, and the RTPFB message 1 is the message currently sent by the UE to the AS.

[0198] It should be understood that the present application embodiment does not limit the execution order of S703 and S704.

[0199] S705. The UPF sends the RTPFB message 2 to the AS. Correspondingly, the AS receives the RTPFB message 2 from the UPF.

[0200] Among them, the RTPFB packet 2 includes second information, which is determined according to the first information in the GTP-U packet and the ECN feedback information in the RTPFB packet 1. The second information includes the second quantity ECN-CECounter2 of the packets experiencing congestion, the second quantity ECT Counter2 of the packets not experiencing congestion, and the quantity not-ECT Counter of the packets not supporting ECN feedback.

[0201] Exemplarily, after the UPF obtains the ECN feedback information from the RTPFB packet 1, it sums up the first quantity of the packets experiencing congestion, the first quantity of the packets not experiencing congestion, and the quantity of the packets not supporting ECN feedback in the ECN feedback information to obtain the total number of statistical packets 1, that is, S_Counter1 = 150 + 200 + 50 = 400.

[0202] Further, the UPF calculates the second quantity of the packets experiencing congestion according to the total number of statistical packets 1 and the congestion ratio 1 (such as 33% in the above example). For example, the congestion ratio 1 = 33%, ECN-CE Counter2 = 400 × 33% = 132, and then calculates ECT Counter2 = max{S_Counter1 - ECN-CE Counter2 - not-ECTCounter, 0} = max{400 - 132 - 50, 0} = 218. Thus, when the RTPFB packet 1 is the packet currently sent by the UE to the AS, the UPF can directly modify the value of the ECN-CE quantity field in the RTPFB packet 1 from 150 to 132, and modify the value of the ECT(1) quantity field in the RTPFB packet 1 from 200 to 218. The modified RTPFB packet 1 is then sent to the AS as the RTPFB packet 2.

[0203] For another example, referring to the congestion ratio 1 = 0 in the above example, ECN-CE Counter2 = 400 × 0 = 0, ECTCounter2 = max{S_Counter1 - ECN-CE Counter2 - not-ECT Counter, 0} = max{400 - 0 - 50, 0} = 350. Thus, when the RTPFB packet 1 is the packet currently sent by the UE to the AS, the UPF can directly modify the value of the ECN-CE quantity field in the RTPFB packet 1 from 150 to 0, and modify the value of the ECT(1) quantity field in the RTPFB packet 1 from 200 to 350. The modified RTPFB packet 1 is then sent to the AS as the RTPFB packet 2.

[0204] S706. The AS adjusts the data transmission rate for transmitting the first QoS flow according to the second information.

[0205] After the AS obtains the RTPFB packet 2, according to the second information in the RTPFB packet 2, including the ECN-CE Counter2 indicated by the ECN-CE quantity field, the ECT Counter2 indicated by the ECT(1) quantity field, and the not-ECT Counter indicated by the not-ECT quantity field, it calculates the congestion ratio 2, and selects the adjusted QoS requirement according to the congestion ratio 2 to adjust the data transmission rate of the first QoS flow.

[0206] Continuing to refer to the above example, GFBR1 = 6 kb / s, ECN-CE Counter2 = 132, ECT Counter2 = 218, not-ECT Counter = 50, congestion ratio Thus, the AS calculates the reference value of the adjusted GFBR according to the congestion ratio 2 and GFBR1 in the QoS requirement 1. For example, the reference value of GFBR = 6×(1 - 33%) = 4.02 kb / s, and takes the QoS requirement in the configured multiple QoS requirements whose GFBR value is closest to and less than the reference value of GFBR as the adjusted QoS requirement. For example, GFBR2 = 4 kb / s in the QoS requirement 2 is closest to 4.02 kb / s, so the AS adjusts the data transmission rate corresponding to the QoS requirement 1 to the data transmission rate corresponding to the QoS requirement 2.

[0207] Continuing to refer to another above example, GFBR1 = 4 kb / s, ECN-CE Counter2 = 0, ECT Counter2 = 350, not-ECT Counter = 50, congestion ratio 2 = 0%. Thus, the AS calculates the reference value of the adjusted GFBR according to the congestion ratio 2 and GFBR1 in the QoS requirement 1. For example, the reference value of GFBR = 4×(1 - 0%) = 4 kb / s. At this time, the reference value of the adjusted GFBR is equal to GFBR1 in the QoS requirement 1. The AS can maintain the data transmission rate corresponding to the QoS requirement 1 to transmit the first QoS flow, or select the QoS requirement in the multiple QoS requirements whose GFBR value is higher than the reference value of GFBR as the QoS requirement for adjusting the data transmission rate. For example, GFBR2 = 6 kb / s in the QoS requirement 2, that is, the AS adjusts the data transmission rate corresponding to the QoS requirement 1 to the data transmission rate corresponding to the QoS requirement 2.

[0208] In the above example, the adjusted QoS requirement determined by the AS and the gNB is the same. It should be understood that in some cases, the adjusted QoS requirements determined by the AS and the gNB may also be different.

[0209] S707. The AS sends the third information to the gNB. Correspondingly, the gNB receives the third information from the AS.

[0210] Among them, the third information is used to indicate the QoS requirements corresponding to the adjusted data transmission rate. That is to say, after the AS determines the adjusted data transmission rate, it informs the gNB of the QoS requirements corresponding to the adjusted data transmission rate, such as QoS requirement 2, so that the gNB transmits the first QoS flow with QoS requirement 2. It should be understood that the AS can also send the third information to the UPF.

[0211] In Figure 7 In the scenario shown, the gNB monitors the network status and switches according to the QoS requirement level, and timely feeds back the congestion ratio information to the UPF. Then, the UPF processes the obtained ECN feedback information of the UE according to the congestion ratio information, and then transmits the processed ECN feedback information to the application server with the ECN feedback message for speed regulation. Thus, the UPF does not need to detour through the UE and does not need to wait for the UE to perform statistics on the packet congestion status for a period of time window to obtain congestion information, and the UPF rewrites or directly generates the ECN feedback information uploaded by the UE to make it compatible with the existing L4S application ecosystem. Therefore, a more immediate, accurate and compatible speed regulation mechanism can be realized.

[0212] Another example is Figure 8 which is a schematic flowchart of a speed regulation method provided by an embodiment of the present application. As Figure 8 shown, the speed regulation method includes the following steps:

[0213] S801. The AS performs initial QoS configuration with the UPF and the gNB.

[0214] S802. The gNB monitors the network status and the radio interface transmission situation of the first QoS flow.

[0215] For the specific implementation processes of S801 and S802, reference can be made to the relevant descriptions in S701 and S702 above, which will not be elaborated here.

[0216] S803. The gNB sends a GTP-U message to the UPF. Correspondingly, the UPF receives the GTP-U message from the gNB.

[0217] Among them, the header of the GTP-U message carries the first information, and the first information is used to indicate the identifier of QoS requirement 2. That is to say, after the gNB determines that the QoS requirement needs to be adjusted (i.e., QoS requirement 2) according to S802 above, it carries the identifier of the QoS requirement to be adjusted in the form of the first information in the header of the GTP-U message and sends it to the UPF.

[0218] S804. The UPF obtains the RTPFB message 1.

[0219] Among them, the RTPFB message 1 includes the ECN feedback information of the UE. The ECN feedback information includes the first quantity of packets experiencing congestion, such as ECN-CE Counter1 = 150, the first quantity of packets not experiencing congestion, such as ECT Counter1 = 200, and the quantity of packets not supporting ECN feedback, such as not-ECT Counter = 50. That is to say, the value of the ECN-CE quantity field in the RTPFB message 1 is 150, the value of the ECT(1) quantity field is 200, and the value of the not-ECT quantity field is 50.

[0220] Exemplarily, the RTPFB message 1 is a message that the UPF stores as the most recent message sent by the UE to the AS, and the message sequence number of the RTPFB message 1 is 4.

[0221] S805. The UPF sends the RTPFB message 2 to the AS. Correspondingly, the AS receives the RTPFB message 2 from the UPF.

[0222] Among them, the RTPFB message 2 includes second information, which is determined according to the first information in the GTP-U message and the ECN feedback information in the RTPFB message 1. The second information includes the second quantity of packets experiencing congestion, ECN-CE Counter2, the second quantity of packets not experiencing congestion, ECT Counter2, and the quantity of packets not supporting ECN feedback, not-ECT Counter.

[0223] Exemplarily, the RTPFB message 2 is a message generated locally by the UPF, which does not carry the uplink data sent by the UE, that is, the payload is empty. The values of the ECN-CE quantity field and the ECT(1) quantity field in the RTPFB message 2 are calculated and determined by the UPF according to the first information in the GTP-U message and the ECN feedback information in the RTPFB message 1. Specifically, the UPF determines the QoS requirement 2 from multiple QoS requirements according to the identifier of the QoS requirement 2 indicated by the first information, and calculates the congestion ratio 1 by using GFBR1 in the QoS requirement 1 and GFBR2 in the QoS requirement 2. The congestion ratio Furthermore, the UPF calculates the second quantity of packets experiencing congestion, ECN-CE Counter2, and the second quantity of packets not experiencing congestion, ECT Counter2, according to the congestion ratio 1, the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets not supporting ECN feedback. The specific implementation process can refer to the relevant description in S705 above, and will not be elaborated here.

[0224] Accordingly, the UPF writes the ECN-CE Counter2 into the ECN-CE quantity field in the RTPFB packet 2, writes the ECT Counter2 into the ECT(1) quantity field, and writes the not-ECT Counter into the not-ECT quantity field.

[0225] Since the RTPFB packet 2 is a packet locally generated by the UPF, to ensure the continuity of the RTPFB packets, the RTPFB packets locally generated by the UPF need to be continuous with the RTPFB packets sent by the UE. For example, if the RTPFB packet 1 sent by the UE that the UPF last received has a packet sequence number of 4, then the packet sequence number of the RTPFB packet 2 is 5, and the specific values of the SSRC fields of the packet sender and the SSRC field of the media source in the RTPFB packet 2 and the RTPFB packet 1 are the same.

[0226] S806. The AS adjusts the data transmission rate for transmitting the first QoS flow according to the second information.

[0227] S807. The AS sends the third information to the gNB. Correspondingly, the gNB receives the third information from the AS.

[0228] Among them, the third information is used to indicate the QoS requirements corresponding to the adjusted data transmission rate.

[0229] For the specific implementation processes of the above S806 and S807, reference can be made to the relevant descriptions of the above S706 and S707, which will not be elaborated here.

[0230] In Figure 8 the scenario shown, the difference from the scenario shown above Figure 7 is that the gNB transfers the identifier of the QoS requirements to be updated to the UPF, and then the UPF can more comprehensively perceive the network status and fluctuations by virtue of the changes in the new and old QoS requirements and the corresponding various QoS parameter indicators. Through designing algorithms or using the training of historical data, the mapping relationship between the changes in each QoS parameter indicator and the congestion ratio is obtained, so as to determine the congestion ratio, process the obtained ECN feedback information of the UE, and transmit the processed ECN feedback information to the application server through the ECN feedback packet for speed adjustment.

[0231] It should be understood that Figure 7 and Figure 8 in the scenario, a simple example of converting the change of a QoS parameter in the new and old QoS requirements into the congestion ratio is given. The embodiments of the present application do not limit the conversion algorithm and the setting of the QoS parameters. The conversion algorithm can satisfy the following relationship: Congestion ratio 1, whose input can include one or more QoS parameters and their combinations. In addition, in Figure 8In the shown scenario, the first information is used to indicate the identifier of QoS requirement 2, or it can be replaced by the first information being used to indicate at least one QoS parameter in QoS requirement 2, such as GFBR2, PER2, and PDB2. The way UPF converts the QoS parameters of QoS requirement 2 into a congestion ratio is similar to the way it converts the identifier of QoS requirement 2 into a congestion ratio, and this will not be elaborated here.

[0232] It should also be understood that in addition to the downlink transmission introduced in the embodiments, the adjustment of the uplink data rate in the embodiments of the present application is also applicable. In addition, the embodiments of the present application are not limited to the adjustment of the data transmission rate on the application server side, and can be compatible with specific end-cloud collaborative applications, such as the adjustment of the video rendering frame rate or the split interaction of the AI application model by the application server.

[0233] In each of the above embodiments, the methods and / or steps implemented by the user plane network element can also be implemented by components (such as processors, chips, chip systems, circuits, logic modules, or software) available for the user plane network element; the methods and / or steps implemented by the access network device can also be implemented by components (such as processors, chips, chip systems, circuits, logic modules, DUs, or software) available for the access network device. Exemplarily, when the execution entity in each of the above embodiments is the DU in the access network device, the sending or receiving steps executed by the access network device can be replaced by the sending or receiving of this DU, and further can be the sending from the DU to the RU or the receiving by the DU from the RU; the methods and / or steps implemented by the application server can also be implemented by components (such as processors, chips, chip systems, circuits, logic modules, or software) available for the application server.

[0234] The above mainly introduced the solutions provided by the present application. Correspondingly, the present application also provides a communication device, which is used to implement various methods in the above method embodiments. This communication device can be the user plane network element in the above method embodiments, or a device including the user plane network element, or a component available for the user plane network element, such as a chip or a chip system. Or, this communication device can be the access network device in the above method embodiments, or a device including the access network device, or a component available for the access network device, such as a chip or a chip system. Or, this communication device can be the application server in the above method embodiments, or a device including the application server, or a component available for the application server, such as a chip or a chip system.

[0235] In some embodiments, to implement the above functions, the communication device includes the corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should easily realize that, for each example of the units and algorithm steps described in combination with the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0236] The embodiments of the present application can divide the communication device into functional modules according to the above method embodiments. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0237] Taking the communication device as the user plane network element or access network device or application server in the above method embodiments as an example, Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As Figure 9 shown, the communication device 900 includes: a processing module 901 and a transceiver module 902. Among them, the processing module 901 is used to execute the processing functions of the user plane network element or access network device or application server in the above method embodiments. The transceiver module 902 is used to execute the transceiver functions of the user plane network element or access network device or application server in the above method embodiments.

[0238] Among them, all relevant contents of each step involved in the above method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0239] Since the communication device 900 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments, and will not be elaborated here.

[0240] In a possible design solution, in the embodiments of the present application, the transceiver module 902 may include a receiving module and a sending module ( Figure 9 not shown in the figure). Among them, the sending module and the receiving module are respectively used to implement the sending function and the receiving function of the communication device 900.

[0241] In a possible design solution, the communication device 900 may further include a storage module ( Figure 9(not shown in the figure), the storage module stores programs or instructions. When the processing module 901 executes the programs or instructions, the communication device 900 can execute Figure 5 the functions of the user plane network element, access network device, or application server in the method shown.

[0242] In some embodiments, the processing module 901 involved in the communication device 900 may be implemented by a processor or processor-related circuit components, and may be a processor or a processing unit; the transceiver module 902 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or a transceiver unit.

[0243] Exemplarily, Figure 10 FIG. 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application. The communication device may be a user plane network element, an access network device, or an application server, or may be a chip (system), other components, or assemblies that can be disposed in a user plane network element, an access network device, or an application server. As Figure 10 shown, the communication device 1000 may include a processor 1001. In a possible design, the communication device 1000 may further include a memory 1002 and / or a transceiver 1003. Among them, the processor 1001 is coupled to the memory 1002 and the transceiver 1003, and may be connected through a communication bus, for example.

[0244] Next, in conjunction with Figure 10 each component of the communication device 1000 will be specifically introduced:

[0245] Among them, the processor 1001 is the control center of the communication device 1000, and may be a single processor or a collective term for multiple processing elements. For example, the processor 1001 includes one or more central processing units (CPUs), and may also be an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, for example: one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0246] In a possible design, the processor 1001 may execute various functions of the communication device 1000 by running or executing software programs stored in the memory 1002 and calling data stored in the memory 1002.

[0247] In a specific implementation, as an example, the processor 1001 may include one or more CPUs, such as Figure 10 the CPU0 and CPU1 shown in

[0248] In a specific implementation, as an example, the communication device 1000 may also include multiple processors, such as Figure 10 the processor 1001 and the processor 1004 shown in. Each of these processors may be a single-core processor or a multi-core processor. The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0249] Among them, the memory 1002 is used to store the software program for executing the solution of this application and is controlled by the processor 1001 for execution. The specific implementation manner may refer to the above method embodiments and will not be elaborated here.

[0250] In a possible design, the memory 1002 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1002 may be integrated with the processor 1001 or exist independently and is coupled to the processor 1001 through the interface circuit of the communication device 1000 ( Figure 10 not shown in), and this application embodiment does not make specific limitations on this.

[0251] The transceiver 1003 is used for communication with other communication devices. For example, when the communication device 1000 is a terminal device, the transceiver 1003 can be used for communication with an access network device or with another terminal device. Another example is that when the communication device 1000 is a network device, the transceiver 1003 can be used for communication with a terminal device or with another network device.

[0252] In a possible design solution, the transceiver 1003 may include a receiver and a transmitter ( Figure 10 not shown separately in the figure). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0253] In a possible design solution, the transceiver 1003 may be integrated with the processor 1001, or may exist independently, and is coupled to the processor 1001 through an interface circuit ( Figure 10 not shown in the figure) of the communication device 1000. The embodiments of the present application do not make specific limitations on this.

[0254] It should be noted that Figure 10 the structure of the communication device 1000 shown in the figure does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements.

[0255] In addition, the technical effects of the communication device 1000 may refer to the technical effects of the method described in the above method embodiments, and will not be elaborated here.

[0256] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed by the computer, the functions of the above method embodiments are implemented.

[0257] The embodiments of the present application also provide a computer program product, which implements the functions of the above method embodiments when executed by the computer.

[0258] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access, or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0259] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0260] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0261] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

[0263] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0264] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0265] Although the present application has been described in connection with various embodiments, those skilled in the art will recognize other variations of the disclosed embodiments while practicing the claimed present application by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the singular "a" or "an" does not exclude a plurality. A single processor or other unit may implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not indicate that these measures cannot be combined to produce favorable effects.

[0266] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the present application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A speed regulation method, characterized in that, the method includes: receiving first information from an access network device, where the first information is used to indicate that it is necessary to adjust a first QoS requirement corresponding to a first Quality of Service (QoS) flow to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates; obtaining a first message of a terminal device, where the first message includes a first quantity of messages that have experienced congestion, a first quantity of messages that have not experienced congestion, and a quantity of messages that do not support explicit congestion notification (ECN) feedback; sending a second message to an application server, where the second message carries second information determined according to the first information, the first quantity of messages that have experienced congestion, the first quantity of messages that have not experienced congestion, and the quantity of messages that do not support ECN feedback, and where the second information is used to determine a first congestion ratio when the first QoS flow is transmitted at the first QoS requirement, and the first congestion ratio is used to adjust the data transmission rate of the first QoS flow.

2. A speed regulation method, characterized in that, the method includes: an access network device sending first information to a user plane network element, where the first information is used to indicate that it is necessary to adjust a first QoS requirement corresponding to a first QoS flow to a second QoS requirement, and the first QoS requirement and the second QoS requirement correspond to different data transmission rates; the user plane network element receiving the first information from the access network device and obtaining a first message of a terminal device, where the first message includes a first quantity of messages that have experienced congestion, a first quantity of messages that have not experienced congestion, and a quantity of messages that do not support ECN feedback; the user plane network element sending a second message to an application server, where the second message carries second information determined according to the first information, the first quantity of messages that have experienced congestion, the first quantity of messages that have not experienced congestion, and the quantity of messages that do not support ECN feedback, and where the second information is used to determine a first congestion ratio when the first QoS flow is transmitted at the first QoS requirement, and the first congestion ratio is used to adjust the data transmission rate of the first QoS flow.

3. The method according to claim 1 or 2, characterized in that, the first information includes one of the following: a second congestion ratio when the first QoS flow is transmitted at the first QoS requirement, an identifier of the second QoS requirement, or QoS parameters in the second QoS requirement, where the second congestion ratio is determined according to the first QoS requirement and the second QoS requirement.

4. The method according to claim 3, characterized in that, the QoS parameters include at least one of the following: Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER).

5. The method according to any one of claims 1-4, characterized in that, the first information is sent carried in a message sent by the access network device.

6. The method according to any one of claims 1-5, characterized in that, the second information includes a second quantity of packets experiencing congestion, a second quantity of packets not experiencing congestion, and the quantity of packets that do not support ECN feedback; wherein, the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the first information, the second quantity of packets not experiencing congestion is determined according to the total quantity of statistical packets, the second quantity of packets experiencing congestion, and the quantity of packets that do not support ECN feedback, and the total quantity of statistical packets is equal to the sum of the first quantity of packets experiencing congestion, the first quantity of packets not experiencing congestion, and the quantity of packets that do not support ECN feedback.

7. The method according to claim 6, characterized in that, the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and the first information, including: the second quantity of packets experiencing congestion is determined according to the total quantity of statistical packets and a second congestion ratio when the first QoS flow transmits with the first QoS requirement, wherein the second congestion ratio is determined according to the first information.

8. The method according to claim 6 or 7, characterized in that, the second quantity of packets not experiencing congestion is the maximum value between a third quantity and zero, and the third quantity is equal to the difference between the total quantity of statistical packets, the second quantity of packets experiencing congestion, and the quantity of packets that do not support ECN feedback.

9. The method according to any one of claims 6-8, characterized in that, the second packet is obtained by modifying the first quantity of packets experiencing congestion in the first packet to the second quantity of packets experiencing congestion, and modifying the first quantity of packets not experiencing congestion in the first packet to the second quantity of packets not experiencing congestion.

10. The method according to any one of claims 1-8, characterized in that, the payload in the second packet is empty, the packet sequence number in the second packet is one more than the packet sequence number in the first packet, the sending end identifier and the receiving end identifier in the second packet are respectively the same as the sending end identifier and the receiving end identifier in the first packet, the sending end identifier is used to identify the terminal device, and the receiving end identifier is used to identify the application server.

11. The method according to any one of claims 1-10, characterized in that, the second packet is a Real-time Transport Layer Feedback Message (RTPFB) packet.

12. A communication device, characterized in that, it includes a module for executing the method according to any one of claims 1, 3-11.

13. A communication device, characterized in that, it includes: a processor; the processor is used to run a computer program or instruction so that the method according to any one of claims 1, 3-11 is implemented.

14. A communication chip, characterized in that, instructions are stored therein, and when the chip runs on a communication device, the method according to any one of claims 1, 3-11 is implemented.

15. A computer-readable storage medium, characterized in that, the storage medium stores a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method described in any one of claims 1, 3-11 is implemented.

16. A computer program product, characterized in that, it includes computer program code, and when the computer program code runs on a communication device, the communication device implements the method described in any one of claims 1, 3-11.

Images